US20110273308A1 - Systems and Methods for Auto-Configuration of a Generic Data Device on a Wireless Network - Google Patents

Abstract

Systems and methods are provided for the automatic configuration of digital utility meters. One embodiment provides for pre-producing digital devices, the digital devices comprising integrated module components, configured for communication with a data management system via a wireless network and further configured for monitoring capability, producing a list file associated with the digital devices and including identities for each integrated module component, activating a digital devices using the wireless network, and distributing deployment information to the digital device from at least one configuration server via the wireless network, including customer data for configuring the digital device and for registering the digital device with a transaction management system.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Patent Application Ser. No. 60/864,196, entitled “Systems and Methods for Auto-Configuration of a Generic Data Device on a Wireless Network,” filed Nov. 3, 2006, which is incorporated herein by reference as if set forth herein in its entirety.
TECHNICAL FIELD
• The present invention relates generally to electricity meters, and more particularly, to utilizing radio-based telemetry for communications between data management systems and remote sensors or data devices.
BACKGROUND
• Wireless data devices are usually pre-programmed with customer configuration information at the time of manufacturing or delivery. This includes such information as unique serial identifiers of the device, messaging destinations (e.g., IP addresses), wireless carrier networks, device passwords or encryption keys, clock settings, calendar settings, time zone settings, embedded software applications and/or updates, and device phone numbers. If appropriate for the wireless technology used, i.e., cellular devices are one example, among others, the devices sometimes also include active or inactive SIM cards.
SUMMARY
• The present invention provides systems and methods for automatic configuration of distributed digital devices that utilize wireless communication. One embodiment provides a method for automatic configuration of digital devices, comprising: pre-producing digital devices comprising integrated module components configured for communication with a data management system via a wireless network and further configured for monitoring capability, producing a list file associated with the digital devices and including identities for each integrated module component, activating a digital device using the wireless network, and distributing deployment information to the digital device from at least one configuration server via the wireless network, further including customer data for configuring the digital device and for registering the digital device with a transaction management system.
• Another embodiment provides a system for automatic configuration of digital devices, comprising: a pre-production server configured for receiving a request for the digital devices from a customer, creating a customer profile, submitting a request for module components, and committing to manufacture the digital devices integrating the module components; a device manufacture server configured for associating the module components with respective end-users; an activation server configured for activating the digital devices via a wireless network; and a configuration server for distributing deployment information corresponding to the digital devices.
• Yet another embodiment provides a system for automatic configuration of digital devices, comprising: a pre-production server configured for receiving a request for the digital devices from a customer, creating a customer profile, submitting a request for module components, and committing to manufacture the digital devices integrating the module components; a device manufacture server configured for associating the digital devices with respective end-users; an activation server configured for activating the digital devices via a wireless network; and a configuration server for distributing deployment information corresponding to the digital devices.
• Other systems, methods, features and advantages of the present invention will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description and be within the scope of the present disclosure.
BRIEF DESCRIPTION OF THE DRAWINGS
• Many aspects of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
• FIG. 1 is a data flow diagram illustrating one embodiment of the auto-configuration of a digital device on a wireless network.
• FIG. 2 is a diagram illustrating the pre-production phase of the auto-configuration of a digital device according toFIG. 1.
• FIG. 3 is a is a diagram illustrating the production phase of the auto-configuration of a digital device according toFIG. 1.
• FIG. 4 is a is a diagram illustrating the activation phase of the auto-configuration of a digital device according toFIG. 1.
• FIG. 5 is a is a diagram illustrating the deployment phase of the auto-configuration of a digital device according toFIG. 1.
DETAILED DESCRIPTION
• Reference is now made in detail to the description of the embodiments of systems and methods for automatic configuration of a generic digital device on a wireless network as illustrated in the drawings. The invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are intended to convey the scope of the invention to those skilled in the art. Furthermore, all “examples” given herein are intended to be non-limiting.
• FIG. 1 is a data flow diagram illustrating asystem100 for the automatic configuration of a utility meter ordigital device22 on a wireless network. One of skill in the art will readily note that other type devices may be configured utilizing the systems and methods described herein.
• The diagram inFIG. 1 illustrates acustomer10 having access to anapplication12, and theapplication12 accessing acomponent production server14, adevice manufacturer server16, alocal operation server18, aconfiguration server20 and a wirelesscarrier activation server24. Adigital device22, such as a digital utility meter for example, is placed by the customer and communicates through a wireless network with theconfiguration server20, and also communicates with acustomer communications server26. Various types of purchase orders (PO), files and requests are passed through thesystem100 and processed within theapplication12 and servers of thesystem100. These purchase orders, files, and requests are discussed in greater detail below. Additionally, the status of thedigital device22, i.e., configuration data, may be ascertained by theconfiguration server20 through the wireless network.
• One embodiment comprises the auto-configuration of adigital device22, such as a digital utility meter. Advanced utility meters, i.e., electricity meters are one non-limiting example, may use a variety of wireless technologies, such as but not limited to General Packet Radio Service (GPRS) based telemetry, to communicate with data management systems to configure various monitoring functions (monitoring of power usage, etc.), carry out load control, meter activation and deactivation, serve as a communications conduit to other devices in the area, or meter data acquisition for both residential and commercial applications. It should be noted that technologies such as CDMA, WiFi, and WiMAX, among others, could also be utilized by advanced electricity meters or other digital devices.
• Implementation of a central configuration server concept allows manufactured or off-the-shelf devices to be predefined, for example, in a database, with the customer's unique identity information based, for example, on a sales order or sales receipt. An order can be filled with a generically manufactureddigital device22. Once adigital device22 is powered on for the first time, it contacts acentral configuration server20 and receives configuration data and other customer-unique programming via a wireless network. Since wireless data devices need not be preconfigured at a factory or sales office, increased flexibility in the manufacture, distribution and activation of thedigital devices22 is attained.
• Typically, thedigital device22 may also contact thecentral configuration server20 during normal operations. Function and feature upgrades are also provided via the wireless network, as well as deactivation or reassignment to a new ordifferent customer10.
• One embodiment of a method for automatic configuration of adigital device22 on a wireless network is meter programming, activation and deployment (MPAD), as illustrated inFIG. 1. The MPAD process data flow is composed of (1) a pre-production phase (FIG. 2), (2) a production phase (FIG. 3), (3) an activation phase (FIGS. 4) and (4) a deployment phase (FIG. 5), each of which is further described below.
• Acustomer10 typically submits a purchase order via a customer PO28 atapplication12. Some activities thecustomer10 performs include placing thedigital device22 into operation, performing anactivation request40 from thecarrier activation server24 via theapplication12, and receiving theactivation file42 resulting from theactivation request40.
• Theapplication12 is responsible for receiving information from and providing information to thecustomer10 regarding the ordering and activation ofdigital devices22. Among other functionalities, theapplication12 is configured for receiving and processing orders, creating a customer profile as part of anorder file30, submitting purchase orders to thecomponent production server14, thedevice manufacturer server16, and thelocal operation server18. Additionally, theapplication12 performsactivation requests40 from thecarrier activation server24 on behalf of thecustomer10.
• Thecomponent production server14 ensures that sufficient inventory of components are available for manufacturingdigital devices22. Additionally, thecomponent production server14 generates asupplier file38 that identifies the components designated for integration into adigital device22.
• Thedevice manufacturer server16 performs the integration of the components to manufacturedigital devices22. The components designated and/or requested by thecomponent production server14 are combined to produce thedigital devices22. Thedevice manufacturer server16 generates aship file46 identifying thedigital devices22 shipped, for example, from thedevice manufacturer server16 to a utility customer.
• It should be noted that the integration of the components could also be sourced out to a third party or assembled locally. In this instance, alocal operations server18 performs the integration of the components to manufacture thedigital devices22, and also generates aship file46 identifying thedigital devices22 provided.
• Theconfiguration server20 receives information identifying thecustomer10, thedigital devices22, activation, and allows for over-the-air activation and programming of thedigital devices22. Aconfiguration server20 can exist as an array of servers allowing for configuration of a large number ofdigital devices22 simultaneously.
• Thedigital device22 is a data device such as, for example, a digital utility meter. One example of adigital device22 is an Itron CENTRON GPRS SmartMeter device manufactured by SmartSynch, Inc. Advanced electricity meters can use wireless technologies and can communicate with data management systems to configure power monitoring functions, carry out load control, meter activation and deactivation, serve as a communications conduit to other devices, and allow for meter data acquisition in residential and commercial applications. It will be readily understood by those of skill in the art, that adigital device22 is not limited to electricity meters, but rather is also applicable for utility meters and other devices that require, for example, monitoring functions, device control, device activation and deactivation, and for communications with other devices.
• Thecarrier activation server24 receives customer requests for activation ofdigital devices22. Typically, acustomer10 would request activation of one or more integrated circuit card IDs (ICCID). Activation information is transmitted back to thecustomer10 in anactivation file42, and is also loaded into theconfiguration server20 where it is typically stored in a database.
• An activateddigital device22 typically registers with acustomer communications server26, such as for example, a customer transaction management.Customers10 can then communicate withdigital devices22 to acquire status and other information as well as programming thedigital devices22.
• FIG. 2 illustrates thepre-production phase200 relating to sales and ordering activities, loading customer information and the manufacture of module components for thedigital device22. Thepre-production phase200 typically involves acustomer10 submitting a request or customer PO28, for example a purchase order, for adigital device22 such as, for example a digital utility meter. One example of adigital device22 is an Itron CENTRON GPRS Smart Meter device manufactured by SmartSynch, Inc. The customer PO28 is submitted using theapplication12.
• After receiving the customer PO28 requesting adigital device22, theapplication12 creates a customer profile. The customer profile identifies thecustomer10 and defines relevant points of contact such as, for example, encryption keys and transaction management system (TMS) destination addresses, among others. The customer profile becomes part of anorder file30 that is sent to theconfiguration server20.
• After creating the customer profile, theapplication12 submits a request for module components by sending a mod PO32 (module purchase order) to thecomponent production server14. The request could be, for example, a purchase order submitted to a component manufacturer. Module components are integrated into thedigital devices22 by thedevice manufacturer server16.
• Typically, requests for module components are utilized to ensure that the inventory is sufficient to producedigital devices22 such as, for example, digital utility meters. If available, the necessary components are designated for the ordereddigital devices22. Of course, if the necessary components are not available, they are procured. The requests are typically based on sales forecasts. Often the requests are fulfilled with previously manufactureddigital devices22 and the automatic configuration process determines the ultimate customer configuration.
• Upon designation of the module components, a commitment is made to manufacturedigital devices22 integrating the module components. A device PO34 (device purchase order) is submitted to adevice manufacturer server16. Thedevice manufacturer server16 utilizes the components—availability ensured by thecomponent production server14—to manufacturedigital devices22.
• Alternatively, theapplication12 need not wait for a customer PO28, but rather may submit amod PO32 based on an estimate, such as a sales projection, to ensure adequate inventory for expected future demand.
• It should be noted that somedigital devices22 may already exist in the inventory, having been produced prior to receiving customer requests. For example, adevice PO34 could be submitted to adevice manufacturer server16 to produce integrated digital utility meters such as SmartSynch SmartMeter devices. The components previously requested via themod PO32 may then be combined to produce the digital devices22 (integrated digital utility meters in this instance).
• It should be noted also, that the integrations could be sourced out to a third party or assembled locally. Awork order36 would be used to document local activities. For example, in some instances alocal operation server18 is utilized to perform the integration of components intodigital devices22. Theapplication12 in such an instance, sends awork order36 to thelocal operation server18. Thus, thework order36 serves to document the integration activities.
• FIG. 3 illustrates theproduction phase300 providing for the actual manufacture and integration ofdigital devices22 such as digital utility meters. For each product delivered, files are generated listing the identities of each integrated component. Alternatively, a file could list the identities of the device itself.
• The generated files are imported into aconfiguration server20, and thedigital devices22 and/or components are typically associated with acustomer10 having a standing order.Digital devices22 not associated with acustomer10 are typically placed in storage for future sale.
• Files are typically created in XML format and delivered to theconfiguration server20 via FTP. Of course, those of skill in the art will recognize that other file formats and delivery methods could be utilized within the scope of the disclosed inventions.
• Alternatively, it should also be noted thatdigital devices22 could be produced prior to receiving a customer PO28. In such circumstances, a file still lists the components and identities of the various components of thedigital device22 as well as the identities of thedigital device22 itself. Once an order is received from acustomer10, thedigital device22 and/or components are then associated with a particular customer orcustomers10. As noted above, this allows for fulfilling customer orders with generically manufactureddigital devices22.
• Additionally, since thedigital devices22 are produced with unique identities, those identities are typically referenced by other components within thesystem100. Similarly, the unique identities of individual components within adigital device22 are typically also referenced by other components within thesystem100.
• Some exemplary file types for providing component information are asupplier file38, aship file46 and anRMA file44. Of course, it should be evident that other file types could be utilized within the scope of this invention.
• Thecomponent production server14 generates asupplier file38 identifying the components designated for integration into adigital device22. Thesupplier file38 is provided to thedevice manufacturer server16 and is used in the production ofdigital devices22. Thesupplier file38 includes identifying information for the components that are shipped to thedevice manufacturer server16 for integration.
• Thedevice manufacturer server16 integrates the components intodigital devices22 and then generates aship file46 that includes identifying information for thedigital devices22 that are manufactured and shipped, for example, to a utility customer. (Although not shown inFIG. 3, a copy of theship file46 is also sent to thecustomer10 upon order delivery.) After theship file46 is imported into theconfiguration server20, thedigital device22 has a status designated as ‘shipped’, for example, in the configuration server.
• Information identifyingdigital devices22 that fail during integration is included in anRMA file44. TheRMA file44 is forwarded to a local operations server and suchdigital devices22 are typically returned for repair.
• Alternatively, alocal operation server18 could assembledigital devices22 locally from the designated module components. In such an instance, thelocal operation server18 generates aship file46 that includes identifying information for thedigital devices22 that are assembled locally. Theship file46, is created in the same manner as by thedevice manufacturer server16 above. Similarly, after theship file46 is imported into theconfiguration server20, thedigital device22 has a status designated as ‘shipped’, for example, in the configuration server.
• FIG. 4 illustrates theactivation phase400 providing for activation of adigital device22, such as a digital utility meter, on a carrier's wireless network. Activation occurs prior to deploying thedigital device22. Once deployed, the digital device communicates with theconfiguration server20 and with acustomer communication server26, such as a TMS.
• As shown inFIG. 4, acustomer10 requests activation of a digital device22 (or group of digital devices) by submitting anactivation request40, for example a customer support form in anapplication12. Theactivation request40 is submitted by theapplication12 to thecarrier activation server24 of the wireless network carrier. For example, acustomer10 would submit anactivation request40 to have an integrated circuit card ID (ICCID) or group of ICCIDs activated. The associated 15-digit mobile station integrated services digital network (MSISDNs) identification number is returned from thecarrier activation server24 of the wireless carrier in anactivation file42. Theactivation file42 is sent to thecustomer10 and is also loaded into theconfiguration server20. Upon importing theactivation file42 into theconfiguration server20, the digital device22 (a digital utility meter in this instance) has a status of ‘Activated’ in the configuration server.
• FIG. 5 illustrates thedeployment phase500 providing for configuration of thedigital device22 via a wireless network. The deployment information may be distributed from theconfiguration server20 to multiple destinations utilizing standard and/or customized interfaces. Customer data is provided and thedigital device22 is registered on the customer's data and transaction management system at thecustomer communications server26.
• As illustrated inFIG. 5, acustomer10 places thedigital device22 in operation in the field. Upon being turned on, or powered up, thedigital device22 performs a network discovery and selection algorithm, performs the appropriate authentication methods for the network to be used, and registers itself over the corresponding wireless network.
• Upon initial power-up, thedigital device22 is in a generic pre-configured state. Thedigital device22 utilizes a default destination address and encryption key to request customer configuration data from theconfiguration server20. The configuration data to be supplied is determined from thesupplier file38, theship file46, theactivation file42, and other information as appropriate.
• Customer configuration is applied to thedigital device22 by theconfiguration server20 passing the customer data (with encryption) to thedigital device22. Theconfiguration server20 waits for an acknowledgment of receipt by thedigital device22. Upon successful configuration, thedigital device22 shows a status of ‘Configured’ within the configuration server and thus, thedigital device22 is in a configured state. If configuration of thedigital device22 fails, the status is shown as ‘Configuration Failed’ in the configuration server and thedigital device22 remains in a pre-configured state.
• After successful configuration, the digital device registers on the customer's data and TMS system at thecustomer communications server26 by using the customer's destination address and encryption key. Acknowledgment from thecustomer communications server26 is passed to thedigital device22 and the digital device status changes to ‘Registered’. An acknowledgment is sent from thedigital device22 to theconfiguration server20, and the digital device status is changed to ‘Registered’ in the configuration server. If registration fails, the status of the device is shown as ‘Registration Failed’ in the configuration server, and the device status remains as ‘Configured’.
• Upon configuration of thedigital device22, theconfiguration server20 may retrieve the customer data, as programmed, from thedigital device22. The data retrieved from thedigital device22 may be compared with the configuration server data, for example, to confirm digital device status. Further, the activities and quality of the deployment process may be managed by utilizing the information derived from theconfiguration server20.
• As noted above, theconfiguration server20 may exist as an array of servers such that a large number ofdigital devices22 may be configured simultaneously.
• Accordingly, it will be understood that various embodiments of the present invention described herein are preferably implemented as a special purpose or general-purpose computer including various computer hardware as discussed in greater detail below. Embodiments within the scope of the present invention also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media which can be accessed by a general purpose or special purpose computer, or downloadable to through wireless communication networks. By way of example, and not limitation, such computer-readable media can comprise physical storage media such as RAM, ROM, flash memory, EEPROM, CD-ROM, DVD, or other optical disk storage, magnetic disk storage or other magnetic storage devices, any type of removable non-volatile memories such as secure digital (SD), flash memory, memory stick etc., or any other medium which can be used to carry or store computer program code in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer, or a mobile device.
• When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such a connection is properly termed and considered a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media. Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device such as a mobile device processor to perform one specific function or a group of functions.
• Those skilled in the art will understand the features and aspects of a suitable computing environment in which aspects of the invention may be implemented. Although not required, the inventions will be described in the general context of computer-executable instructions, such as program modules, being executed by computers in networked environments. Such program modules are often reflected and illustrated by flow charts, sequence diagrams, exemplary screen displays, and other techniques used by those skilled in the art to communicate how to make and use such computer program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types, within the computer. Computer-executable instructions, associated data structures, and program modules represent examples of the program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
• Those skilled in the art will also appreciate that the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, networked PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
• An exemplary system for implementing the inventions, which is not illustrated, includes a general purpose computing device in the form of a conventional computer, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The computer will typically include one or more magnetic hard disk drives (also called “data stores” or “data storage” or other names) for reading from and writing to. The drives and their associated computer-readable media provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data for the computer. Although the exemplary environment described herein employs a magnetic hard disk, a removable magnetic disk, removable optical disks, other types of computer readable media for storing data can be used, including magnetic cassettes, flash memory cards, digital video disks (DVDs), Bernoulli cartridges, RAMs, ROMs, and the like.
• Computer program code that implements most of the functionality described herein typically comprises one or more program modules may be stored on the hard disk or other storage medium. This program code, as is known to those skilled in the art, usually includes an operating system, one or more application programs, other program modules, and program data. A user may enter commands and information into the computer through keyboard, pointing device, or other input devices (not shown), such as a microphone, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit through known electrical, optical, or wireless connections.
• The main computer that affects many aspects of the inventions will typically operate in a networked environment using logical connections to one or more remote computers or data sources, which are described further below. Remote computers may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically include many or all of the elements described above relative to the main computer system in which the inventions are embodied. The logical connections between computers include a local area network (LAN), a wide area network (WAN), and wireless LANs (WLAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets and the Internet.
• When used in a LAN or WLAN networking environment, the main computer system implementing aspects of the invention is connected to the local network through a network interface or adapter. When used in a WAN or WLAN networking environment, the computer may include a modem, a wireless link, or other means for establishing communications over the wide area network, such as the Internet. In a networked environment, program modules depicted relative to the computer, or portions thereof, may be stored in a remote memory storage device. It will be appreciated that the network connections described or shown are exemplary and other means of establishing communications over wide area networks or the Internet may be used.
• In view of the foregoing detailed description of preferred embodiments of the present invention, it readily will be understood by those persons skilled in the art that the present invention is susceptible to broad utility and application. While various aspects have been described in the context of a preferred embodiment, additional aspects, features, and methodologies of the present invention will be readily discernable therefrom. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications, and equivalent arrangements and methodologies, will be apparent from or reasonably suggested by the present invention and the foregoing description thereof, without departing from the substance or scope of the present invention. Furthermore, any sequence(s) and/or temporal order of steps of various processes described and claimed herein are those considered to be the best mode contemplated for carrying out the present invention. It should also be understood that, although steps of various processes may be shown and described as being in a preferred sequence or temporal order, the steps of any such processes are not limited to being carried out in any particular sequence or order, absent a specific indication of such to achieve a particular intended result. In most cases, the steps of such processes may be carried out in a variety of different sequences and orders, while still falling within the scope of the present inventions. In addition, some steps may be carried out simultaneously. Accordingly, while the present invention has been described herein in detail in relation to preferred embodiments, it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made merely for purposes of providing a full and enabling disclosure of the invention. The foregoing disclosure is not intended nor is to be construed to limit the present invention or otherwise to exclude any such other embodiments, adaptations, variations, modifications and equivalent arrangements, the present invention being limited only by the claims appended hereto and the equivalents thereof.

Claims (18)

1. A method for automatic configuration of digital devices, comprising steps of:

pre-producing a plurality of digital devices, comprising integrated module components, configured for communication with a data management system via a wireless network and further configured for monitoring capability;

producing a list file, the list file associated with the plurality of digital devices and including identities for each integrated module component;

activating a digital device, from the plurality of digital devices, using the wireless network; and

distributing deployment information to the digital device from at least one configuration server via the wireless network, the deployment information including customer data for configuring the digital device and for registering the digital device with a transaction management system.

2. The method ofclaim 1, the pre-producing initiated by a request from a customer for the digital devices.

3. The method ofclaim 2, further comprising creating a customer profile, the customer profile including customer identification, encryption keys and destination addresses.

4. The method ofclaim 1, further comprising requesting a plurality of module components that are necessary for manufacture of the digital devices.

5. The method ofclaim 4, further comprising committing to manufacture of the digital devices that integrate the plurality of module components.

6. The method ofclaim 1, wherein the digital devices are telemetry devices.

7. The method ofclaim 1, wherein the digital devices are meters.

8. The method ofclaim 1, wherein the digital devices are electric meters.

9. The method ofclaim 1, wherein the monitoring capability includes power monitoring functions.

10. The method ofclaim 1, wherein the activating is responsive to a request from a customer for activation of at least one integrated circuit card ID (ICCID).

11. The method ofclaim 9, wherein an associated 15-digit mobile station integrated services digital network (MSISDN) identification number is transmitted to a customer in an activation file and imported to the at least one configuration server.

12. The method ofclaim 1, wherein the distributing deployment information uses parallel configuration servers.

13. The method ofclaim 1, wherein the distributing deployment information uses standard interfaces.

14. The method ofclaim 1, wherein the distributing deployment information uses customized interfaces.

15. The method ofclaim 1, further comprising, retrieving the customer data and status information from the digital device to the at least one configuration server.

16. The method ofclaim 1, the distributing deployment information further comprising requesting configuration data from the at least one configuration server.

17. A system for automatic configuration of digital devices, comprising:

a pre-production server configured for receiving a first request for the digital devices from a customer, creating a customer profile, submitting a second request for module components, and committing to manufacture the digital devices integrating the module components;

a device manufacture server configured for associating the module components with respective end-users;

an activation server configured for activating the digital devices via a wireless network; and

a configuration server for distributing deployment information corresponding to the digital devices.

18. A system for automatic configuration of digital devices, comprising:

a pre-production server configured for receiving a first request for the digital devices from a customer, creating a customer profile, submitting a second request for module components, and committing to manufacture the digital devices integrating the module components;

a device manufacture server configured for associating the digital devices with respective end-users;

an activation server configured for activating the digital devices via a wireless network; and

a configuration server for distributing deployment information corresponding to the digital devices.

Images