Network-enabled, extensible metering system

Abstract

To allow meter data users to have access to needed information and at the same time address the rapidly shifting requirements of the deregulated marketplace, a new business model, apparatus and system are provided. A common metering device measures raw data and a system composed of independent services or applications collect and process raw metered data and then make that data available to interested parties. This new model removes the dependence upon an automatic meter reading (AMR) system provider, as the sole provider, by creating a system to enable a competitive environment where services (applications, information, networking, etc.) rather than systems are selected and paid for on a leased or pay-per-use basis. One example of such a networked-based, extensible metering system comprises a network server, a wide area network coupled to the network server, and a plurality of network-enabled meters coupled to the network. The meters collect data and the network server provides at least one metering application to the meters. In addition, the meters may be programmed to communicate via a predefined protocol and to deliver a protocol interface to a storage medium on the network, which enables the network to provide the protocol interface to users or applications requiring information from the meters and the users/applications to communicate with the meters to access the required information.

Description

FIELD OF THE INVENTION

The present invention relates generally to the field of utility metering (including gas, electric, water and energy metering). More particularly, the present invention relates to the integration of network systems and utility meters.

BACKGROUND OF THE INVENTION

The above-cited U.S. patent application Ser. No. 09/022,718 discloses a system generally involving electronic meters and automatic meter reading, and more particularly TCP/IP-enabled electronic utility meters for remote two-way access over local and wide area networks. The present invention is related in that it involves the use of TCP/IP-enabled, extensible utility meters in a new business model and system. Further background information about the business model aspect of the present invention is provided below.

Business Models

Currently, meter manufacturers sell meters to make money. Some revenue is generated from metering system sales, but these systems are generally viewed as just another mechanism for selling additional meters. Meter manufacturers compete by providing better metering capabilities and functionality at a lower price.

Any given type of meter, whether it is water, electric, energy, or gas, measures a bounded set of quantities. These quantities represent the raw data collected by the device. Meter manufacturers cannot use this raw metered data as a way to differentiate themselves from their competitors. Therefore, at the factory, they load their meter's firmware with embedded capabilities, improved accuracy, or other applications (e.g., time of use (TOU), power quality (PQ) and/or alarm monitoring). These firmware applications use the meter's core set of data to compute the information that their meter data users (MDUs) need. To hedge against the uncertainty of deregulation, meter data users (such as utility distribution companies (UDC), energy service providers (ESP), or meter data management agencies (MDMA), etc.) often purchase, at a low price, fully capable meters with all or some of their capabilities disabled (i.e., “turned off”). When additional functionality is needed, the MDU must purchase a license (or “key”) that gives it the ability to enable (“turn on”) the desired function in a meter. This method of selectively turning on meter functions allows the meter manufacturer to create new license-based pricing models to make its product more cost competitive. Thus, in reality, the meter must still be manufactured with all of the necessary hardware and applications in order to support the fullest possible range of functionality in an effort to more efficiently address possible future metering needs.

This business model has several drawbacks:

• • 1) increased functionality in the meter requires an increase in processing power (e.g., ROM, RAM, EEPROM, etc.) and a commensurate increase in cost;
  • 2) the memory available “under the glass” in a meter is finite (i.e., in order to add an option you must remove another option or increase the memory);
  • 3) to upgrade or re-program a meter requires that a meter technician drive to the location, physically remove the meter (or switch it out with a replacement meter) and then return it to the “meter shop” where the upgrade can occur; after the upgrade is complete, the meter must be returned and re-installed;
  • 4) different meters require different interfaces and different communications protocols for retrieving data;
  • 5) increased application complexity in the firmware of the meter leads to a higher probability of errors that may require upgrades;
  • 6) increased application functionality housed in the firmware of the meter typically requires complex configuration or programming of the end-device, which greatly increases the system management, coordination, and synchronization; and
  • 7) meter inventory must be increased in order to accommodate different configurations, functionalities, and versions of metering devices.

With the advent of improved communication technology, manufacturers are now able to add modem, network, and radio-frequency (RF) connectivity to their meters, thus permitting remote communications between meters and various meter data retrieval systems (e.g., automated meter reading (AMR) systems). However, there are limitations associated with these methods of remote communications:

• • 1) wireless communication with the meter is often limited to off peak hours determined by the various network providers;
  • 2) satellite-based communications are limited to line of sight communication between the meter and the satellite, thus limiting the times when the meter may be contacted;
  • 3) wireless and orbital satellite networks are costly, often billing per byte of data transmitted, thus limiting the amount of data which can effectively be transmitted.

Existing AMR systems are also limited in that they require several layers of applications and interfaces in order to communicate with connected meters. These layers implement the various communications protocols used by the numerous meter manufacturers and the various communications technologies that can be used to communicate with a meter (e.g., RF communication, satellite-based communication, etc.). As these meters are constantly revised, so are their communications protocols, requiring similar modifications to the AMR system. Industry standards intended to unify the communication and device protocols typically fall short by setting minimum requirements for compliance and/or providing manufacturer-specific mechanisms to allow variability and customizations. Therefore, AMR systems still often require meter-specific knowledge (e.g., communications and device protocols) to read the required data from meters offered by different manufacturers. Even with the current metering standards, the addition of a new or different meter would typically require additions and/or modifications to an AMR system. The increasing variety of meters presents an almost insurmountable challenge to the automated meter reading industry.

Deregulation of the electricity metering industry has created even more challenges. Prior to deregulation, a utility was responsible for generating, distributing, and transmitting electricity as well as purchasing, storing and installing metering devices, collecting metered data and processing customer billing. Now, with deregulation slowly being implemented throughout the United States, those duties and responsibilities that were the exclusive responsibility of the utility can now be divided among several service companies and providers who all need access to the meter and the meter data. All of these companies require access to either the data collected from the metering devices (e.g., power quality, outage, etc.) or to the calculated/processed data (e.g., quadrant data; validated, estimated, and edited (VEE) data, etc.) for their internal use (load management and monitoring, forecasting, etc.).

Today there are two prevailing AMR System business models. We refer to these as: 1) the exclusive ownership model (depicted in FIGS. 1), and 2) the service bureau model (depicted in FIG. 2). Certain AMR System deployments utilize a mixture of these two models in order to establish a workable business case, but we will discuss these models individually. FIG. 1 depicts the exclusive ownership business model and shows two scenarios for AMR Systems that utilize public communication networks and private communication networks, or so-called fixed networks. FIG. 2 depicts the service bureau business model and shows two scenarios for AMR Systems that utilize public communication networks and private communication networks. A key difference between the public and private type communication networks is that the private network requires additional up-front cost to deploy the infrastructure of the fixed network to blanket one or more service areas. Although FIGS. 1 and 2 separate the public and private communications, AMR Systems exist that can utilize a combination or mix between public communication networks and private communication networks.

In the exclusive owner business model (FIG. 1), the meter data users (MDUs) (i.e., ESPs, UDCs, MDMAs, etc.) purchase an AMR system with a significant up-front cost. In this business model, a particular MDU that is purchasing an AMR System is typically only interested in how the purchased AMR System will address its specific needs as identified in its business case. The MDU typically develops a business case that justifies the initial AMR System cost based on both measurable and non-measurable benefits. Some of the measurable benefits include:

• • 1) meter reading staff and infrastructure reductions,
  • 2) cost reductions for hard-to-access meter reading,
  • 3) connect/disconnect staff reductions,
  • 4) accurate and timely outage restoration,
  • 5) reduction in theft or tampering.

Some of the non-measurable benefits include:

• • 1) faster and more frequent meter readings, thus yielding a higher level of customer service/retention,
  • 2) better positioned for competition in a deregulated energy market,
  • 3) ability to provide other types of services (i.e., new rates, flexible billing, etc.),
  • 4) other future uses for the metered information.

Taken alone, the measurable benefits listed above typically do not justify the expense incurred by purchasing an AMR system. Consequently, the number of large AMR System deployments has not reached expectations.

In the service bureau business model (FIG. 2), a service bureau (e.g., MDMA) purchases an AMR system with a significant up-front cost, and then provides access to the collected meter data to subscriber MDUs. This business case is built on the value of the metered information. It assumes the service bureau will recoup the cost of the AMR system by selling meter reads or metered information to multiple MDUs (ESPs, UDCs, etc.). From the perspective of the MDU, many of the quantifiable and non-quantifiable benefits discussed above can be met using this model, with timely access to the correct set of metered information. In this model, the MDUs do not own and operate the AMR System, which is the responsibility of the service bureau operator. In this model, the MDUs must pay for the information they require. This reduces the up-front costs for the MDUs over purchasing their own AMR System and provides them with a pay-per-use model. The service bureau model could create some conflicts, or perceived conflicts, when competing MDUs utilize the same service bureau for metered information. E.g., how can “MDU 1” differentiate its end-user offerings and services from a competitor, “MDU 2,” that utilizes the same service bureau and consequently has access to the same type of metered information? In the service bureau model, the MDUs need to be able to add value by developing or buying applications that allow them to differentiate themselves from their competitors.

In both business models, the AMR supplier's business case is to develop and sell AMR Systems and maintenance agreements. This business case assumes that the development investment for an AMR System can be recouped through many AMR System sells. In the exclusive owner business model, the AMR System supplier is typically confronted with a customer who wants an AMR System customized to handle his/her specific business processes. These types of AMR System sales usually require the AMR supplier to perform customer specific development. AMR System sells of this type, made by an AMR supplier, increase the AMR supplier's overall development costs, deployment costs, long-term maintenance costs, and upgrade costs. In the service bureau business model, the AMR supplier is confronted with a customer who requires an AMR System that has a different set of requirements from the AMR System of the exclusive ownership model. The AMR System sold to operate as a service bureau must accommodate many different MDUs and their business processes, and must also control access to the metered data. E.g., “ESP A” cannot read the metered information for a customer of “ESP B.” The service bureau AMR System is more complex because this system must accommodate all of the MDU's needs while controlling or limiting access in a secure manner. The AMR System suppliers have a problem in creating a workable business case because they make a significant development investment and cannot afford financially or from a risk management point of view to limit their systems to one business model or the other. In today's uncertain environment, it is not clear if both business models will survive the deregulation evolution. The AMR System suppliers, therefore, must identify a way to develop a system that covers all requirements for both business models, is customizable, flexible, easily adaptable, etc.

In either of the above business models, the MDUs and the service bureau operators are dependent upon the sole AMR System supplier to react quickly to solve system problems, and address new requirements that may evolve from the evolving deregulation process. Since the AMR Systems developed today are proprietary and closed, this dependency upon a sole provider is a weak link in terms of risk management for the MDUs and service bureau operators. Competition within the volatile deregulated environment hinges upon AMR System providers' ability to respond rapidly to customer needs.

SUMMARY OF THE INVENTION

To allow meter data users to have access to needed information and at the same time address the rapidly shifting requirements of the deregulated marketplace, there is a need for a new business model, and a new apparatus and system for implementing such a business model. The present invention meets this need by providing a common metering device that measures raw data and a system composed of independent services or applications that can collect and process raw metered data and then make that data available to interested parties. This new model is intended to remove the dependence upon an AMR System provider, as the sole provider, by creating a system concept to enable a competitive environment where services (applications, information, networking, etc.) rather than systems are selected and paid for on a leased or pay-per-use basis.

A networked-based, extensible metering system in accordance with the present invention comprises a network server, a wide area network coupled to the network server, and a plurality of network-enabled meters coupled to the network. The meters collect data and the network server provides at least one metering application to the meters. In addition, the meters may be programmed to communicate via a predefined protocol and to deliver a protocol interface to a storage medium on the network, which enables the network to provide the protocol interface to users or applications requiring information from the meters and the users/applications to communicate with the meters to access the required information.

Other aspects of the present invention are described below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically depicts two business scenarios that reflect current business models for exclusively-owned AMR systems.

FIG. 2 schematically depicts two business scenarios that reflect current business models for service bureau AMR systems.

FIG. 3 illustrates a business model provided by the present invention.

FIG. 4 illustrates revenue flow as a result of the sale/lease of metering services developed to work in a business model provided by the present invention.

FIG. 5 illustrates an exemplary embodiment of a Network-enabled, Extensible Metering System in accordance with the present invention.

FIG. 6 is a data flow diagram that illustrates the data flow in the Network-enabled, Extensible Metering System.

FIG. 7 illustrates the components of an embedded, network-enabled metering device and communications adapters used to connect the device to a network.

FIG. 8 schematically depicts various methods for connecting legacy metering devices to the Network-enabled, Extensible Metering System.

FIG. 9 depicts an end-user (“outside the fence”) to Network-enabled, Extensible Metering System (“inside the fence”) scenario.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention introduces a new method for generating metering revenue using new, faster and improved communication and device technologies. In this system and business model, a new meter apparatus for collecting and storing metered data and information is part of a virtual machine as is the network application system of which it is a part. By residing on the network, the meter information becomes readily accessible to other devices, applications, and users on the network. Using new object-oriented, embedded networking technologies (e.g., Sun Microsystems' Java®/Jini®, Microsoft's Universal Plug and Play®, etc.), service discovery protocols, and security mechanisms, devices (i.e., meters) and services (i.e., data collection, storage, validation, TOU, etc.) are accessible to MDUs (such as, ESP, UDC, and MDMA) that need access to raw or metered information.

An exemplary embodiment of the present invention will now be described from the perspectives of the business model and the system.

Business Model

FIGS. 3 and 4 illustrate how application services may be purchased (at a one-time cost), leased (on a time-of-use or pay-per-use basis), or developed in-house for processing raw and/or real-time meter data. In the system shown in FIG. 3, MDUs use metering service applications to process raw data collected from networked meters. The MDUs are denoted as follows in the various scenarios depicted in FIG. 3: “ESP1,” “UDC,” “ESP2” in the Service Bureau model; “MDMA” in the Purchased Services model; and “UDC” in the Leased Services model. Also, in FIG. 3, the suite of services applications are:

• • 1) CS—Collection Services
  • 2) TOU—Time of Use Services
  • 3) DF—Data Formatting Services
  • 4) DR—Data Repository Services
  • 5) VEE—Validated, Estimated and Edited Data Services
  • 6) BS—Billing Services
  • 7) MS—Monitoring Services
  • 8) PQ—Power Quality Analysis Services
  • 9) FC—Forecasting Services.

FIG. 4 shows the revenue flow as services that process meter data are leased or purchased. This business model allows MDUs to have secure access, via application programming interfaces (APIs), to data collected by networked meters. With the deregulation of the electricity metering industry, metering data processing protocols are becoming standardized. This invention provides an open, standardized system that permits the high degree of customization and flexibility demanded by a deregulated metering environment. This enables vendors and meter data users to develop standardized data processing applications and value-added applications for sale, lease or in-house usage. FIGS. 3 and 4 show a sample of the type of services that benefit from defined/standardized APIs to address AMR operations. As shown in FIG. 4, some of the applications are developed in-house by the respective MDUs whereas others are leased or purchased for a fee (as indicated by the “$” signs and arrows).

Thus, the present invention may be implemented in a system that comprises network-based applications and network-enabled meters (electrical, gas, energy and water) that can provide full or part-time, secure connectivity between the meters and layered business applications using the Internet. Moreover, by employing object-oriented inter-networking technologies for embedded devices technology, this system provides a suite of products including meters, core services and networked applications that make meter information available to interested parties. The inter-network services are expected to provide common communications protocols, discovery protocols, namespace management (i.e., Directory or Lookup Service), leasing/pay-per-use services, and security (especially secure access to network-enabled meters).

System and Apparatus

FIG. 5 schematically depicts an exemplary embodiment of a Network-enabled, Extensible Metering System in accordance with the present invention. As shown, metering devices 1 collect data on a metered service 2 and communicate the collected data via various communications devices 3 and 4 (antenna and modem, respectively) to a TCP/IP network 5. Also on the network 5 are various network devices for storing and processing the meter data; network servers 6; a directory server 7 for device location and interface location; and a database server 8 for storing raw and processed meter data and the meters' communication interfaces. This system allows the metering devices to upload raw metered data (e.g., kVARh, kWh, load profile, etc.) to the network 5 for processing and storage in the database 8 and the network servers to download real-time applications (e.g., power quality monitoring, alarm management, etc.) directly to a meter's leased/reserved memory and, based upon meter memory constraints, on a per-lease or on an as-needed basis.

FIG. 6 depicts data flow in the system. Instead of the system having embedded knowledge of meter protocols and specific communications access methods, the meter device itself delivers its protocol interface to the network-side Directory Service. As shown, in this system, a meter data user, or MDU, installs a meter (with an embedded networking device) at a customer's location. When the meter is connected to the network, it notifies the network's Directory Service that it is connected and ready to communicate (step S1). At the same time, the meter uploads its communications interface to the network database (step S2). A user or an application (e.g., a data retrieval system) requiring information from the meter asks for the meter's location from the Directory Service (step S3) and downloads the meter's communications interface (step S4). Now able to communicate directly with the meter without having prior meter-specific protocol knowledge, the user or application communicates directly with the meter and accesses the needed information (step S5). Access to the applications necessary to process the meter's information may be made available to the MDU on a pay-per-use and/or pay-by-time lease basis. This process allows meter data users to purchase a simple meter (with embedded networking technology) with little to no embedded applications. Applications needed to extend the functionality of a meter can then be developed, leased or purchased on an as-needed basis and executed at the network level. This system could also push needed applications out to the meter for execution at the meter level (e.g., real-time functions such as power quality monitoring, alarm monitoring, etc). Since the traditional in-meter applications are removed from the meter and placed at the network level, new applications can be easily developed and quickly implemented via the network to support future functionality and features that are not yet needed in today's deregulated environment. These applications may be purchased or leased from a third party vendor or developed by the meter data user. Applications developed by the meter data user could be sold or leased to other meter data users to generate additional revenue. This changes the business model for metering from a model where money is made on the meter device itself to a service-based model where the information is paid for each time it is accessed or used. In this model, the metered information becomes the revenue generator.

FIG. 7 depicts the components of an embedded, network-enabled metering device and the possible communications adapters used to connect the device to a network (LAN or WAN). As shown, such a metering device could include a measuring device, an accumulator for collecting the metered data, memory for storage, and some type of connector or port for connecting to a communications adapter. The various communications adapters would accommodate telephony, WAN CDPD, wireless Ethernet, and LAN Ethernet. Such a system would be easily expanded as communications technologies improve and are expanded. The network-enabled meter becomes a simple metering device that collects and stores raw (unprocessed) meter data (i.e., the quantities that can be measured are finite). The variety of communications adapters provide the meter with the means to communicate with the users and applications on the network system.

FIG. 8 illustrates various methods for connecting legacy metering devices (e.g., electromechanical or electronic meters that are not network-enabled) to the system. One manner of enabling a meter to interface with a network would be composed of either an internal or external hardware adapter that would provide the embedded network connectivity. Another way involves an interface application located on the system's network end. The adapters and system application would contain the necessary communications and device interface information that would enable any user or device connected to the network to communicate with the legacy metering device.

FIG. 9 illustrates an end-user to Network-enabled, Extensible Metering System scenario. In this scenario, network-enabled applications residing on a meter data user's (such as an energy service provider) network would have direct access (via radio-frequency, Internet, etc.) to the metered data of an end-user (e.g., a residential or a commercial/industrial customer). The meter data user side of the system would store the metered data in either independent or cumulative data repositories. Additionally, the meter data user side may is able to download or push real-time meter applications out to the metering device as needed. On the end-user side of the system (furnished with various network-enabled devices: a display, a meter, home automation devices, etc.), the user may lease or purchase a service package of applications from the meter data user that enables the user to perform a variety of functions, e.g., TOU analysis, load shedding, power quality monitoring, etc.

In the inventive system, the network-enabled meter ceases to be the sole revenue-generating commodity for manufacturers. Instead, the meter and the software systems that access and process its data become a continuous source of revenue. The meter becomes a simple device that requires no programming and fewer upgrades. The meter's functionality is no longer limited by the volume “under the glass” but becomes virtually unlimited by having the functionality residing on the network and accessed on an as-needed basis by the networked applications. Networked applications use the same service infrastructure as the networked meter. E.g., the networked applications use the network discovery, join and lookup services to find other application services just as applications use network infrastructure to find meter services. Networked applications register the services they offer with the Lookup services, just as the meter does. This allows both networked meters and networked applications to work in a transparent federation of services. In order for applications and meters to cooperate in a federation of services, the service interfaces must be predefined into a set of Open APIs. These applications can include storage of metered information, load profiling, data aggregation, power quality monitoring, tariff calculations, outage notifications, etc. Meter data users may decide which applications they need and either choose the application provider or develop the needed application in-house. If an application provider were selected, then the application would be paid for on either a per-use basis or leased for a set period of time. New or expanded functions and features could be easily added to the system and just as easily implemented by the meter data users. An additional benefit of having the applications residing on the network rather than in the meter is that feature upgrades or meter updates or maintenance occurs at the network level rather that in the meter at the customer's site. Thus, by decreasing the complexity of the meter, the probability for errors at the meter level is decreased, making maintenance and upgrades easier and more efficient.

Using the virtually unlimited processing power and capacity of a network, the capabilities of a meter also become virtually unlimited. When a meter requires an upgrade or patch, a Meter Service Provider could “push” the new code to all affected meters with a single command instead of physically removing each and every affected meter and transporting them to the meter shop for firmware/software upgrades. The upgrades would take effect immediately, making the new functionality instantaneously available to meter data users.

In addition to allowing meter data users to directly access and process meter data, the system allows meter data users to provide certain end user processes (e.g., service disconnect, on-site usage display, etc.), as shown in FIG. 9. End users (i.e., energy consumers) could lease or purchase applications from a meter data user, which would enable on-site control and monitoring of energy consumption, usage, etc. Appliances that implement embedded network-enabling devices can be managed and monitored by the meter data user and/or the end-user. An added feature for the end-user is in the field of home or business automation for building and energy management. Currently, end-user devices and applications designed for home/business automation must implement one of a variety of protocols (e.g., LonWorks, CEBus, X10, etc.). In the present system, a common communication protocol (TCP/IP) unifies development of automation devices and applications. Such a system would enable end-user pre-payment, real-time and “energy exchanges” pricing, and even on-site payment via a card reader. Energy management applications (like demand management or load shedding) could be easily monitored and configured by both the meter data user and the end-user.

Conclusion

With this invention, the meter data user, or MDU, that decides upon an exclusive ownership business model will be capable of assembling services provided by many suppliers to create the AMR System that best suits their business case. In addition, the MDU can elect to develop certain services to add value or lease to other MDUs. This increases a MDU's flexibility to generate revenue, reduces their dependence upon a sole AMR System provider, and reduces their overall risk. This invention also strengthens the service bureau business model by allowing a service bureau operator to assemble and/or develop different services for different MDU subscribers. These MDU subscribers can in turn develop value-added services of their own in order to gain competitive advantage. Finally, this invention helps the AMR Suppliers by creating well-defined services that makeup an AMR System. The AMR Suppliers can decide which services they can best develop to generate an ongoing revenue stream, not a series of one time, customized AMR System sales.

In sum, the present invention provides a novel system based on a network-enabled, extensible meter. It is understood, however, that the invention is susceptible to various modifications and alternative constructions. There is no intention to limit the invention to the specific constructions described herein. E.g., the various techniques described herein may be implemented in a variety of hardware or software, or a combination of both. Preferably, the techniques are implemented in utility metering components having programmable processors, a storage medium readable by the processor (including volatile and non-volatile memory and/or disk storage elements), and various application programs. Each program may be implemented in assembly or machine language. However, the programs can be implemented in a high level procedural or object oriented programming language to communicate with a computer system. In any case, the language may be a compiled or interpreted language. Each such computer program is preferably stored on a storage medium or device (e.g., ROM or magnetic disk) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform the procedures described above. The system may also be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner.

Although exemplary embodiments of the invention have been described in detail above, those skilled in the art will readily appreciate that many additional modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the invention. Accordingly, these and all such modifications are intended to be included within the scope of this invention as defined in the following claims.

Claims

1. A networked-based, extensible metering system, comprising: (a) a plurality of networked servers executing a network of interoperable services including a directory service that comprises a plurality of networked device or application interface locations;(b) a TCP/IP network coupled to the networked servers; and(c) a network-enabled meter coupled to the TCP/IP network;

2. A system as recited in claim 1, wherein the meter is programmed to publish its interface data to the directory service.

3. A system as recited in claim 1, wherein the meter includes a network communicating device.

4. A system as recited in claim 1, wherein the directory service provides interface data for the meter to a meter data user (MDU), whereby the MDU is provided with services and data by the meter through an interface associated with the interface data.

5. A system as recited in claim 1, wherein the network comprises the Internet.

6. A system as recited in claim 1, wherein the network comprises an intranet.

7. A system as recited in claim 1, wherein the network comprises a wide area network.

8. A system as recited in claim 1, wherein the directory service is accessible to a meter data user (MDU) and provides interface data to the MDU.

9. A system as recited in claim 1, wherein applications reside on a storage medium on the network and are upgradeable on the network.

10. A system as recited in claim 1, wherein applications are activated on the meter on a real-time basis.

11. A system as recited in claim 1, wherein multiple meter data users can access the same or different services and/or data for the same meter.

12. A system as recited in claim 1, wherein the meter consists of a reduced set of internal hardware and firmware required for traditional metering devices.

13. A system as recited in claim 1, further comprising embedded network-enabling adaptors to allow legacy metering devices to interface with network-level users and applications.

14. A system as recited in claim 1, further comprising communications adaptors to allow protocol-dependent communication between users and applications and the network-enabled meter.

15. A system as recited in claim 1, wherein the meter is programmed to communicate via an interface associated with an interface location, and delivers interface data to a storage medium on the network, whereby the network is able to provide the interface data to a user or application requiring information from the meter and the user or application is enabled to communicate with the meter to access the required information; wherein the directory service is enabled to provide the interface data to a meter data user (MDU), whereby the MDU is provided with metered data by the meter and the MDU is provided with metering applications by the server; wherein applications reside on the network and are upgradeable on the network; wherein applications are activated on the meter on a real-time basis; wherein multiple MDUs can access the same or different applications and/or data for the same meter; and further comprising communications adaptors to allow protocol-dependent communication between users and applications and the network-enabled meter.

16. A networked-based, extensible metering system, comprising a wide area network comprising a plurality of networked servers executing a network of interoperable services including a directory service that comprises a plurality of networked device or application interface locations, and a plurality of network-enabled meters coupled to the network; wherein the meters collect data and the meters are programmed to communicate data and services via a service interface to a networked device or application using the associated networked device or application interface location and receive new services from the networked device or application using the associated networked device or application interface location and to deliver interface data to a storage medium on the network, whereby the network is able to provide the interface data to users or applications requiring information from the meters and the users or applications are able to communicate with the meters to access the required information through an interface associated with the interface data.

17. A system as recited in claim 16, wherein applications reside on the network and are upgradeable on the network.

18. A system as recited in claim 17, wherein applications are activated on the meters on a real-time basis.

19. A system as recited in claim 18, wherein multiple meter data users (MDUs) can access the same or different services and/or data for the same meter.

20. A system as recited in claim 19, further comprising communications adaptors to allow protocol-dependent communication between users and applications and the network-enabled meters.

21. A system as recited in claim 16, wherein the directory service provides interface data for an application to at least one of the meters, whereby the at least one meter is provided with data and services by the application through an interface associated with the interface data.