Abstract:
Disclosed are apparatus and methodology subject matters for providing an interface between a meter in an advanced metering system and an application running on such a system. The interface operates effectively as a device driver to translate communication protocols so that plug-n-play functionality (interchangeability) may be provided for meters provided from various venders in an open operational framework, such as for ANSI standard C12.22 meters. The interface provides a plug-in based library that interfaces between the user interface and a data collection engine that is designed to optimize data collection functionality. Optimization is achieved, at least in part, by providing data request processing separately from response processing. Separate response processing allows for the possibility of unsolicited messages being processed for later association with other possible jobs.

Description:
PRIORITY CLAIM  
       [0001]     This application claims the benefit of previously filed U.S. Provisional Patent Application entitled “INTERFACE BETWEEN METER AND APPLICATION,” assigned U.S. Ser. No. 60/841,622, filed Aug. 31, 2006, and which is hereby incorporated herein by reference in its entirety for all purposes. 
     
    
     FIELD OF THE INVENTION  
       [0002]     The present technology relates to utility meters. More particularly, the present technology relates to methodologies and apparatus for providing plug-n-play, interchangeability of ANSI standard C12.22 meters within an open operational framework.  
       BACKGROUND OF THE INVENTION  
       [0003]     The general object of metrology is to monitor one or more selected physical phenomena to permit a record of monitored events. Such basic purpose of metrology can be applied to a variety of metering devices used in a number of contexts. One broad area of measurement relates, for example, to utility meters. Such role may also specifically include, in such context, the monitoring of the consumption or production of a variety of forms of energy or other commodities, for example, including but not limited to, electricity, water, gas, or oil.  
         [0004]     More particularly concerning electricity meters, mechanical forms of registers have been historically used for outputting accumulated electricity consumption data. Such an approach provided a relatively dependable field device, especially for the basic or relatively lower level task of simply monitoring accumulated kilowatt-hour consumption.  
         [0005]     The foregoing basic mechanical form of register was typically limited in its mode of output, so that only a very basic or lower level metrology function was achieved. Subsequently, electronic forms of metrology devices began to be introduced, to permit relatively higher levels of monitoring, involving different forms and modes of data.  
         [0006]     In the context of electricity meters specifically, for a variety of management and billing purposes, it became desirable to obtain usage data beyond the basic kilowatt-hour consumption readings available with many electricity meters. For example, additional desired data included rate of electricity consumption, or date and time of consumption (so-called “time of use” data). Solid state devices provided on printed circuit boards, for example, utilizing programmable integrated circuit components, have provided effective tools for implementing many of such higher level monitoring functions desired in the electricity meter context.  
         [0007]     In addition to the beneficial introduction of electronic forms of metrology, a variety of electronic registers have been introduced with certain advantages. Still further, other forms of data output have been introduced and are beneficial for certain applications, including wired transmissions, data output via radio frequency transmission, pulse output of data, and telephone line connection via such as modems or cellular linkups.  
         [0008]     The advent of such variety and alternatives has often required utility companies to make choices about which technologies to utilize. Such choices have from time to time been made based on philosophical points and preferences and/or based on practical points such as, training and familiarity of field personnel with specific designs.  
         [0009]     Another aspect of the progression of technology in such area of metrology is that various retrofit arrangements have been instituted. For example, some attempts have been made to provide basic metering devices with selected more advanced features without having to completely change or replace the basic meter in the field. For example, attempts have been made to outfit a basically mechanical metering device with electronic output of data, such as for facilitating radio telemetry linkages.  
         [0010]     Another aspect of the electricity meter industry is that utility companies have large-scale requirements, sometimes involving literally hundreds of thousands of individual meter installations, or data points. Implementing incremental changes in technology, such as retrofitting new features into existing equipment, or attempting to implement changes to basic components which make various components not interchangeable with other configurations already in the field, can generate considerable industry problems.  
         [0011]     Electricity meters typically include input circuitry for receiving voltage and current signals at the electrical service. Input circuitry of whatever type or specific design for receiving the electrical service current signals is referred to herein generally as current acquisition circuitry, while input circuitry of whatever type or design for receiving the electrical service voltage signals is referred to herein generally as voltage acquisition circuitry.  
         [0012]     Electricity meter input circuitry may be provided with capabilities of monitoring one or more phases, depending on whether monitoring is to be provided in a single or multiphase environment. Moreover, it is desirable that selectively configurable circuitry may be provided so as to enable the provision of new, alternative or upgraded services or processing capabilities within an existing metering device. Such variations in desired monitoring environments or capabilities, however, lead to the requirement that a number of different metrology configurations be devised to accommodate the number of phases required or desired to be monitored or to provide alternative, additional or upgraded processing capability within a utility meter.  
         [0013]     More recently a new ANSI protocol, ANSI C12.22, is being developed that may be used to permit open protocol communications among metrology devices from various manufacturers. C12.22 is the designation of the latest subclass of the ANSI C12.xx family of Meter Communication and Data standards presently under development. Presently defined standards include ANSI C12.18 relating to protocol specifications for Type 2 optical ports; ANSI C12.19 relating to Utility industry Meter Data Table definitions; and ANSI C12.21 relating to Plain Old Telephone Service (POTS) transport of C12.19 Data Tables definition. It should be appreciated that while the remainder of the present discussion may describe C12.22 as a standard protocol, that, at least at the time of filing the present application, such protocol is still being developed so that the present disclosure is actually intended to describe an open protocol that may be used as a communications protocol for networked metrology and is referred to for discussion purposes as the C12.22 standard or C12.22 protocol.  
         [0014]     C12.22 is an application layer protocol that provides for the transport of C12.19 data tables over any network medium. Current standards for the C12.22 protocol include: authentication and encryption features; addressing methodology providing unique identifiers for corporate, communication, and end device entities; self describing data models; and message routing over heterogeneous networks.  
         [0015]     Much as HTTP protocol provides for a common application layer for web browsers, C12.22 provides for a common application layer for metering devices. Benefits of using such a standard include the provision of: a methodology for both session and session-less communications; common data encryption and security; a common addressing mechanism for use over both proprietary and non-proprietary network mediums; interoperability among metering devices within a common communication environment; system integration with third-party devices through common interfaces and gateway abstraction; both 2-way and 1-way communications with end devices; and enhanced security, reliability and speed for transferring meter data over heterogeneous networks.  
         [0016]     To understand why utilities are keenly interested in open protocol communications; consider the process and ease of sending e-mails from a laptop computer or a smart phone. Internet providers depend on the use of open protocols to provide e-mail service. E-mails are sent and received as long as e-mail addresses are valid, mailboxes are not full, and communication paths are functional. Most e-mail users have the option of choosing among several Internet providers and several technologies, from dial-up to cellular to broadband, depending mostly on the cost, speed, and mobility. The e-mail addresses are in a common format, and the protocols call for the e-mail to be carried by communication carriers without changing the e-mail. The open protocol laid out in the ANSI C.12.22 standard provides the same opportunity for meter communications over networks.  
         [0017]     In addition, the desire for increased processing capabilities as well as other considerations including, but not limited to, a desire to provide plug-n-play (that is, interchangeable) capabilities for individual metrology components in an open operational framework, leads to requirements for interfacing such components with system applications.  
         [0018]     As such, it is desired to provide an improved interface for coupling utility meters to system applications in an open operational framework.  
         [0019]     While various aspects and alternative embodiments may be known in the field of utility metering, no one design has emerged that generally encompasses the above-referenced characteristics and other desirable features associated with utility metering technology as herein presented.  
       SUMMARY OF THE INVENTION  
       [0020]     In view of the recognized features encountered in the prior art and addressed by the present subject matter, an improved apparatus and methodology allowing plug-n-play compatibility (that is, interchangeability) of metrology devices in an open operational framework has been provided.  
         [0021]     In an exemplary arrangement, a methodology has been provided to permit transmission of information between a utility meter and an operational application through a network.  
         [0022]     In one of its simpler forms, the present technology provides an interface to provide communication translations between network protocols and meter protocols.  
         [0023]     One positive aspect of such interface is that it functions as a device driver for meters within an ANSI standard C12.22/C12.19 system to provide read functionality for the devices and allow for plug-n-play (interchangeable) insertion of C12.22 meters within an open framework.  
         [0024]     Another positive aspect of such present type of interface is that by supporting a single library in differing interfaces, optimized functionality for the Collection Engine from within the user interface may be achieved.  
         [0025]     Yet another positive aspect of the methodology of the present subject matter is that processing of Collection Engine requests may be conducted differently than response processing.  
         [0026]     Yet a further positive aspect of the present subject matter is that Collection Engine request processing can allow a request for data from a device to be formatted without prior knowledge of the configured functionality of the end device.  
         [0027]     In further present exemplary aspects, there is the provision of an interface between an electricity meter and an application that functions effectively as a “device driver” to provide plug-and-play functionality for C12.22 meters. Such interface preferably may provide a plug-in based library that interfaces between the user interface and a data collection engine that is designed to optimize data collection functionality. Optimization is achieved, at least in part, by providing data request processing separately from response processing. Separate response processing allows for the possibility of unsolicited messages being processed for later association with other possible jobs.  
         [0028]     One exemplary present embodiment relates to a utility meter for use within an advanced metering system operating relative to a network and having other utility meters, user interfaces, and central collection functionality. Such an exemplary utility meter preferably includes metrology for monitoring the consumption or production of a commodity; at least one communications module configured to effect bi-directional communications between such utility meter and other networked devices using an open standard meter communication protocol; and an interface for permitting transmission of information between such metrology and one or more operational applications associated with such utility meter. In such arrangement, such interface preferably functions as a device driver for the utility meter that is capable of interfacing with a user interface and central collection functionality.  
         [0029]     In present variations of the foregoing embodiment, such interface may further employ a message manager for an open standard meter communication protocol, with such message manager configured to create message objects merged with one or more destination addresses and wrapped in an application layer format. Still further, such message manager may be configured to parse received communications by extracting message objects and destination addresses from the received communications.  
         [0030]     In still other present variations, such interface may comprise a plug-in based library that allows for interchangeable inclusion of the utility meter in an advanced metering system comprising other utility meters and central collection functionality and/or such interface may be configured to separately customize request processing and response processing for central collection functionality, so as to optimize functionality for the central collection functionality from within the user interface.  
         [0031]     Another present exemplary embodiment relates to an advanced metering system. In some embodiments thereof, such system may make use advantageously of the above-described various embodiments of utility meters.  
         [0032]     In other present exemplary advanced metering systems, such systems may include a plurality of end devices, at least some of which end devices comprise metrology devices, a network, and an interface. Such network may preferably include central collection functionality comprising a collection engine, with such network being configured for bi-directional communications between such central collection functionality and each of such plurality of end devices, and with such bi-directional communications occurring at least in part based on an open standard meter communication protocol. Such exemplary interface may be provided at selected end devices for permitting transmission of information between such metrology devices associated with each of such selected end devices and one or more operational applications associated with each of such selected end devices. Such interface may preferably function as a device driver for each of such selected end devices, while being configured for interfacing with a user interface and central collection functionality.  
         [0033]     Alternatively, for some present exemplary embodiments such interface may include message manager features, such as the exemplary such features referenced above. Still further alternatively, such interface may process exception requests defining whether power outages have occurred at locations within a metering system.  
         [0034]     Still further, it is to be understood that various present exemplary embodiments may equally relate to present methodologies, one example of which relates to a method of permitting transmission of information between utility meter metrologies and one or more operational applications associated with a utility meter. Such an exemplary method may include steps of providing a network including central collection functionality and a plurality of end devices; configuring such network for bi-directional communications between the central collection functionality and each of the plurality of end devices using an open standard meter communication protocol; and providing an interface at each of the plurality of end devices that is capable of interfacing with a user interface and central collection functionality.  
         [0035]     Alternatively, such exemplary present methodology may further include various message manager features, such as the exemplary features referenced above. Other present alternatives of the foregoing methodology may include adding a step of processing exception requests defining whether power outages have occurred at locations within a metering system.  
         [0036]     Additional objects and advantages of the present subject matter are set forth in, or will be apparent to, those of ordinary skill in the art from the detailed description herein. Also, it should be further appreciated that modifications and variations to the specifically illustrated, referred and discussed features, elements, and steps hereof may be practiced in various embodiments and uses of the present subject matter without departing from the spirit and scope of the subject matter. Variations may include, but are not limited to, substitution of equivalent means, features, or steps for those illustrated, referenced, or discussed, and the functional, operational, or positional reversal of various parts, features, steps, or the like.  
         [0037]     Still further, it is to be understood that different embodiments, as well as different presently preferred embodiments, of the present subject matter may include various combinations or configurations of presently disclosed features, steps, or elements, or their equivalents including combinations of features, parts, or steps or configurations thereof not expressly shown in the figures or stated in the detailed description of such figures. Additional embodiments of the present subject matter, not necessarily expressed in the summarized section, may include and incorporate various combinations of aspects of features, components, or steps referenced in the summarized objects above, and/or other features, components, or steps as otherwise discussed in this application. Those of ordinary skill in the art will better appreciate the features and aspects of such embodiments, and others, upon review of the remainder of the specification. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0038]     A full and enabling disclosure of the present subject matter, including the best mode thereof, directed to one of ordinary skill in the art, is set forth in the specification, which makes reference to the appended figures, in which:  
         [0039]      FIG. 1  is a block diagram overview illustration of an Advanced Metering System (AMS) and a representation of corresponding methodology thereof, in accordance with the present subject matter;  
         [0040]      FIG. 2  illustrates a block diagram of an exemplary meter incorporating interface features in accordance with the present subject matter; and  
         [0041]      FIG. 3  illustrates an exemplary Advanced Metering System deployment incorporating various of both apparatus and methodology aspects of the present subject matter. 
     
    
       [0042]     Repeat use of reference characters throughout the present specification and appended drawings is intended to represent same or analogous features, elements, or steps of the present subject matter.  
       DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0043]     As discussed in the Summary of the Invention section, the present subject matter is particularly concerned with the provision of improved corresponding apparatus and methodology allowing plug-n-play compatibility (i.e., interchangeability) of metrology devices in an open operational framework.  
         [0044]     Selected combinations of aspects of the disclosed technology correspond to a plurality of different embodiments of the present subject matter. It should be noted that each of the exemplary embodiments presented and discussed herein should not insinuate limitations of the present subject matter. Features or steps illustrated or described as part of one embodiment may be used in combination with aspects of another embodiment to yield yet further embodiments. Additionally, certain features may be interchanged with similar devices or features not expressly mentioned which perform the same or similar function.  
         [0045]     Reference will now be made in detail to presently preferred embodiments of the subject methodology and apparatus. Referring to the drawings,  FIG. 1  is a block diagram overview illustration of an Advanced Metering System (AMS) in accordance with the present subject matter.  
         [0046]     Advanced Metering System (AMS) generally  100  in accordance with the present subject matter is designed to be a comprehensive system for providing advanced metering information and applications to utilities. AMS  100  in pertinent part is designed and built around industry standard protocols and transports, and therefore is intended to work with standards compliant components from third parties.  
         [0047]     Major components of AMS  100  include exemplary respective meters  142 ,  144 ,  146 ,  148 ,  152 ,  154 ,  156 , and  158 ; one or more respective radio-based networks including RF neighborhood area network (RF NAN)  162  and its accompanying Radio Relay  172 , and power line communications neighborhood area network (PLC NAN)  164  and its accompanying PLC Relay  174 ; an IP (internet protocol) based Public Backhaul  180 ; and a Collection Engine  190 . Other components within exemplary AMS  100  may include a utility LAN (local area network)  192  and firewall  194  through which communications signals to and from Collection Engine  190  may be transported from and to respective exemplary meters  142 ,  144 ,  146 ,  148 ,  152 ,  154 ,  156 , and  158  or other devices including, but not limited to, Radio Relay  172  and PLC Relay  174 .  
         [0048]     AMS  100  is configured to be transparent in a transportation context, such that exemplary respective meters  142 ,  144 ,  146 ,  148 ,  152 ,  154 ,  156 , and  158  may be interrogated using Collection Engine  190  regardless of what network infrastructure exists inbetween or among such components. Moreover, due to such transparency, the meters may also respond to Collection Engine  190  in the same manner.  
         [0049]     As represented by the illustration in  FIG. 1 , Collection Engine  190  is capable of integrating Radio, PLC, and IP connected meters. To facilitate such transparency, AMS  100  operates and/or interfaces with ANSI standard C12.22 meter communication protocol for networks. C12.22 is a network transparent protocol, which allows communications across disparate and asymmetrical network substrates. C12.22 details all aspects of communications, allowing C12.22 compliant meters produced by third parties to be integrated into a single advanced metering interface (AMI) solution. AMS  100  is configured to provide meter reading as well as load control/demand response, in home messaging, and outage and restoration capabilities. All data flowing across the system is sent in the form of C12.19 tables. The system provides full two-way messaging to every device; however, many of its functions may be provided through broadcast or multicast messaging and session-less communications.  
         [0050]     With present reference to  FIG. 2 , there is illustrated a block diagram of an exemplary meter  200  incorporating interface features in accordance with the present subject matter. Meter  200  preferably incorporates several major components including Metrology  210 , a Register Board  220 , and one or more communications devices. In the presently illustrated exemplary configuration, meter  200  may include such as an RF LAN Interface  230  and accompanying antenna  232 , and a Zigbee Interface  240  and its accompanying antenna  242 . In addition, an Option Slot  250  may be provided to accommodate a third party network or communications module  252 .  
         [0051]     Metrology  210  may correspond to a solid-state device configured to provide (internal to the meter) C12.18 Blurt communications with Register Board  220 . Communications within meter  200  are conducted via C12.22 Extended Protocol Specification for Electronic Metering (EPSEM) messages. The meter Register Board  220  is configured to fully support C12.19 tables and C12.22 extensions. While all meter data will be accessible via standard C12.19 tables, in order to facilitate very low bandwidth communications, manufacturers tables or stored procedures are included which provide access to specific time-bound slices of data, such as the last calendar day&#39;s worth of interval data or other customized “groupings” of data.  
         [0052]     Meter  200  may be variously configured to provide differing communications capabilities. In exemplary configurations, one or more of GPRS, Ethernet, and RF LAN communications modules may be provided. GPRS will allow meters to be IP addressable over a public backhaul and provide more bandwidth than the meter will likely ever require, but may incur ongoing subscription costs. Ethernet connectivity can be used to bridge to third party technologies, including WiFi, WiMax, in-home gateways, and BPL (Broadband over Power Lines), without integrating any of these technologies directly into the metering device, but with the tradeoff of requiring external wiring and a two part solution. Ethernet devices may be used primarily in pilots and other special applications, and they additionally may be ideal for certain high-density RF-intolerant environments, such as meter closets.  
         [0053]     Due to the increased complexity of managing a WAN interface, with its more sophisticated link negotiation requirements and TCP/IP (Transmission Control Protocol/Internet Protocol) stack, WAN connected meters may include an additional circuit board dedicated to WAN connectivity. Such board if used would preferably interface with meter  200  using EPSEM messages and Option Slot  250 .  
         [0054]     The availability of Option Slot  250  within meter  200  provides the advantage that it will make meter  200  available for integration with third party backhauls, such as PLC (Power Line Communications). In order for such third party devices to be integrated into AMS  100 , on the other hand, third party devices will need to include both a communications board and a C12.22 compliant relay to couple communications signals from any proprietary network of the third party to an IP connection. Alternatively, third parties could integrate meter  200  into their own end-to-end solution.  
         [0055]     The communications protocol between meter  200  and respective communications modules  230 ,  240 , and WAN module or optional third party communications module  250 , follow the C12.22 standards, allowing any third party to design to the standard and be assured of relatively straightforward integration.  
         [0056]     Communication with the Collection Engine  190  is performed over an Internet Protocol connection. The Wide-Area-Network is a fully routable, addressable, IP network that may involve a variety of different technologies including, but not limited to, GPRS, WiFi, WiMax, Fiber, Private Ethernet, BPL, or any other connection with sufficiently high bandwidth and ability to support full two-way IP communication. Several assumptions (that is, criteria of the present subject matter) may be made regarding the IP WAN. Collection Engine  190  is preferably implemented so as to be able to communicate directly with other respective nodes on the IP WAN. While communications may be conducted through a firewall  194 , it is not necessary that such be proxied, unless the proxy is itself a C12.22 node functioning as a relay between a private IP network and the public IP WAN.  
         [0057]     Further in accordance with the present subject matter, the interface between meters and applications manager (IMA Manager) provided by the present technology facilitates communications between upper level devices including, but not limited to, Collection Engine  190  and the various respective meters and other devices within AMS  100 . More particularly, the IMA Manager uses a C12.22 manager to create an Extended Protocol Specification for Electronic Meters (EPSEM) message object wrapped in an Application Control Service Element (ACSE) object, to send the message to a native network, to receive a response from the native network, and to return an ACSE object with the EPSEM response embedded. The IMA Manager preferably would then utilize the IMA for the device class in order to build an EPSEM message to be sent to the meters.  
         [0058]     The IMA Manager will merge the EPSEM message with any necessary ApTitles to form an ACSE message and then will pass the ACSE message to the C12.22 Manager. The C12.22 Manager will then send the ACSE message to the appropriate meters. A response from a meter may be received from the network into the C12.22 Manager, which will parse the ACSE message so as to extract the ApTitle and EPSEM message. Later, the C12.22 Manager receives a response from the previous ACSE message, parses the ACSE response and sends it to the IMA Manager.  
         [0059]     The IMA Manager processes an exception response and submits it to an exception manager, which delivers the exception to all systems that have subscribed to that exception type. The IMA Manager utilizes a Metadata store to retrieve any information about the calling ApTitle, such as the device class and EDL configuration file, and then utilizes the IMA for the device class to interpret, for example, that an outage has occurred.  
         [0060]     The IMA Manager will inform the Exception Manager which respective meter has experienced an outage. The Exception Manager obtains a list of subscribers for the supplied Exception Type from the Metadata Store API, and then sends the message to every notification system that has subscribed to notifications of the exception&#39;s type.  
         [0061]     The Advanced Metering System of the present technology provides a series (or plurality) of services (functionalities) to utilities. In its most basic implementation, it provides daily feeds of residential interval or TOU (Time of Use) data. Beyond such functionality, it provides power outage and restoration notifications, on-demand readings, firmware updates, load control/demand response, gas meter readings, and in-home display messages. All of such functions (services) are communicated via the C12.22 protocol. In order to optimize use of the low-bandwidth RF LAN, selected operations assume use of manufacturer procedures within the meter; however, the general C12.22 communication engine of the system is not specific to any particular tables, devices, or manufacturers. In the future, in accordance with the present subject matter, as alternate network substrates may become available, the RF LAN can very easily be swapped out with other technologies.  
         [0062]     With present reference to  FIG. 3 , it will be seen that an exemplary Advanced Metering System (AMS) generally  300  deployment has been illustrated.  FIG. 3  illustrates for exemplary purposes only a single RF LAN cell, with twelve respective member nodes organized into three levels, as well as four directly connected IP meters  370 ,  372 ,  374 , and  376 . In such system, all respective meter devices  310 ,  320 ,  330 ,  332 ,  340 ,  342 ,  350 ,  352 ,  354 ,  356 ,  360 ,  362 ,  364 ,  466 ,  370 ,  372 ,  374 , and  376 , Cell Relay  302 , and Collection Engine  390 , have C12.22 network addresses. Collection Engine  390  may in accordance with the present subject matter have multiple C12.22 addresses to allow for separate addressing between different services (functionalities). Meter or master data management system  391  is not part of the C12.22 network, but preferably it will be implemented so as to communicate over the Utility LAN  392  to Collection Engine  390  via Web Services. Communications between Cell Relay  302  and Utility LAN  392  variously involve Public Backhaul  380  and firewall  394 , in a manner analogous to that discussed above in conjunction with Public Backhaul  180  and firewall  194  ( FIG. 1 ), as well understood by those of ordinary skill in the art.  
         [0063]     The meter data acquisition process begins with the Meter (or Master) Data Management System  391  initiating a request for data. Such operation is done through a web services call to Collection Engine  390  and may be performed without knowledge of the configured functionality of the end-device. Collection Engine  390  analyzes the request for data, and formulates a series of C12.22 multicast (or broadcast) data requests. Such requests are then sent out either directly to the device (in the case of an IP connected meter, such as  370 ), or to Cell Relay  302  that relays the message out to all appropriate nodes. Broadcast and multicast messages are sent by Cell Relay  302  to all members of the cell, either via an AMS RF LAN-level broadcast, or by the Cell Relay repeating the message. For efficiency sake, the use of an RF LAN level broadcast may be preferred.  
         [0064]     Typically these requests are sent as a call to a manufacturer&#39;s stored procedure. In C12.22, stored procedure calls are performed as writes to a predetermined table, e.g. “table  7 .” The stored procedure will send the default upload configured for such device. For example, a given meter may be configured to upload two channels of hourly interval data, plus its event history. Another meter might be programmed to send up its TOU registers. The stored procedure will require four parameters to be fully operative in accordance with the present subject matter: data start time, data end time, response start time, and response end time. The data start and end time are be used to select which data to send. The response start time and end time are used to determine the window within which the upstream system wants to receive the data. The various AMS enabled meters of  FIG. 3  are preferably field programmable, via C12.22 tables, as to the type data to be included in a default upload.  
         [0065]     When data is sent to Collection Engine  390 , is it sent as C12.19 table self-write with the notification bit set, and the do-not-respond bit set. The result is that per the present subject matter no C12.22 acknowledgement is sent in response to the Collection Engine&#39;s broadcast, nor does the Collection Engine  390  in response to the notify-write send any response; however, the notify-write effectively serves per the present subject matter as an acknowledgement to the receipt of the broadcast.  
         [0066]     The response processing section can use the configured data about an end device and the response message from the end device to determine the results from the device. The response processing section begins operation associated with a specific job in a task list, but can be switched between any active job that is awaiting a response. Such operation allows responses that contain logs from the device to be parsed by each job that could be waiting for an action to be completed within the end-device. Such also would allow unsolicited messages to be parsed by the IMA code and then later associated with any possible jobs, as determined by the IMA, all in accordance with the present subject matter.  
         [0067]     While most operations will not require this, the AMS meters will support chaining a series of EPSEM messages, such as multiple table reads and writes in a single request. This is functionality that is required in the C12.22 specification, and will assist in improving the efficiency of the system, as it avoids the overhead of sending a separate message for each EPSEM command. AMS enabled devices will process each request sequentially, allowing a series of operations to be handled in a single command, each building on the next, such that a read subsequent to a write would reflect the results of the request write. If a command in an EPSEM chain cannot be completed, remaining commands in the chain are rejected with appropriate error messages, per the present subject matter.  
         [0068]     When a respective device receives a request, it evaluates the multi-cast address specified. If the device is a member of the multicast group, it responds to the request; otherwise, it discards it. Membership in different multicast groups is determined via use of C12.22 standard table  122 .  
         [0069]     On-demand reading per the present subject matter is similar to the Daily Meter Data Acquisition Process; however, rather than sending a broadcast or multicast request, the on-demand reading process in accordance with the present subject matter communicates directly to desired respective meters. Such process begins with a user initiated on-demand read through an AMS User Interface, or through a web services call from an upstream system. Per the present subject matter, an orchestration layer of the Collection Engine  390  begins by evaluating the current system load of the communications substrate through which the respective device is connected. Requests for an on-demand read from a saturated cell may be rejected.  
         [0070]     Once Collection Engine  390  determines that the request can be honored, it selects per the present subject matter an appropriate communication server within the Collection Engine, and submits the command to retrieve data from the device and return it. The communications server forms a C12.22 table read request, encrypts it, and sends it to the device directly, if IP connected, or to Cell Relay  302  for RF LAN connected devices. In cases where traffic flows through the RF LAN, the Cell Relay software retrieves the message from the IP backhaul  380 , and evaluates the message. The destination address (in C12.22 terminology, the so-called ApTitle) may be stripped off to save bandwidth on the network, relying instead on the underlying RF LAN addressing scheme for delivering the message. The Cell Relay software must also examine whether the destination ApTitle is still valid within the cell. If the destination ApTitle is no longer valid, the Cell Relay rejects the message, returning an error packet to the Collection Engine. Provided that the destination is still valid, the Cell Relay software sends the message to the device across the RF LAN, per the present subject matter.  
         [0071]     A protocol stack for the RF LAN advantageously takes the message and constructs a node path for the message to take before actually transmitting the packet. Such pre-constructed node path allows Cell Relay  302  per the present subject matter to push a message down through the tree of the cell without creating redundant radio messages. If Collection Engine  390  wants to do an on-demand read to meter  356 , it starts by sending the message to Cell Relay  302 . Cell Relay  302  in turn sends out a transmission that will be heard by both respective meters  310  and  320  (in the exemplary configuration of present  FIG. 3 ). Meter  320  could go ahead and retransmit the message, but this wouldn&#39;t get the message to meter  356 . Instead, it would simply waste bandwidth. With the node path provided to by the RF LAN protocol stack, meters  310  and  320  will hear the message, but per the present subject matter only meter  310  will retransmit the message. The retransmitted message of meter  310  will be heard by both meters  330  and  332 , but only meter  332  will be in the node path, again meaning other parts of the cell (such as meters  350  and  352 ) won&#39;t receive a message that would be useless to them. Both meters  354  and  356  will hear the message, but it is only addressed to meter  356 . As such, meter  354 , per the present subject matter, will simply ignore it.  
         [0072]     Once the message is received at the subject (i.e., intended) meter, whether via RF LAN or via IP, such meter must unpack the request and act on it. The communications module within the device will pull the C12.22 message off the network substrate and provide it to the Register Board  220  ( FIG. 2 ). Register Board  220  will decrypt the message based on shared keys, and then respond to the request, encrypting it and returning it to the calling ApTitle. In the case of the RF LAN, the message is simply forwarded to the next layer up in the cell. Messages are forwarded from one layer to the next until they finally reach Cell Relay  302 , which relays it across the IP backhaul  380  to the communications server that initiated the transaction.  
         [0073]     While the present subject matter has been described in detail with respect to specific embodiments thereof, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing may readily produce alterations to, variations of, and equivalents to such embodiments. Accordingly, the scope of the present disclosure is by way of example rather than by way of limitation, and the subject disclosure does not preclude inclusion of such modifications, variations and/or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art.