Meter reading schema to enhance system functionality

[0001] This application is a continuation of U.S. application Ser. No. 16/910,492, filed Jun. 24, 2020, which is a continuation of U.S. application Ser. No. 15/718,638 filed Sep. 28, 2017, now U.S. Pat. No. 10,704,924 which is based on, and claims the benefit of, U.S. provisional patent application 62/402,099 filed Sep. 30, 2016, each of which is incorporated herein by reference.

[0002] This invention relates to communications in electric and other utilities; and, more particularly, to a method and improvements for enhanced communications between disparate installations in a utility's distribution system under a wide variety of operational conditions.

[0003] A utility supplies a particular commodity (electricity, gas, water) through a distribution system to numerous end users. Each utility has a dedicated supply network or grid by which the commodity is routed from a central site or sites to the location of the respective end users. Itis now commonplace for a measuring device or meter such as a “smart meter” to be installed at each using facility's location, the meter measuring the amount of the commodity dispensed to and/or used at that particular site. Over time communication systems have been developed which enable a central location of the utility to link with and access the user location through the meter to, for example, obtain current commodity usage rates, control use rates of the commodity under certain conditions, etc. Examples of such communication systems include a two-way automatic communications system for a power line carrier or power line communications system (i.e. Aclara Technologies, TWACS®), as well as a radio frequency (RF) system and landline communications systems.

[0004] Referring to FIG. 1, a utility U, for example an electric utility, generates electricity which is propagated through power lines L from a central location such as a sub-station S to numerous end user sites such as residential, commercial, or manufacturing establishments or facilities F. It will be understood that while many sites F rely solely on the electricity transmitted over the power lines to operate machinery, systems, and appliances at the facility, some facilities such as facilities F1 and F2 may use local, alternate power sources in addition to the power supplied by the utility. So, for example, facility F1 employs solar panels SP as a primary or secondary source of power; while facility F2 has its own generator G used for this purpose. Regardless, each facility connected to the utility has a meter such as a smart meter M installed at the facility to measure the amount of usage of the commodity (i.e., electricity) supplied to the facility. A communications link C enables correspondence between the utility and each facility connected in the utility's power grid.

[0005] Sometimes disruptions occur which prevent the commodity provided by a utility from reaching some or all of the using sites. For example, in an electrical grid, a power line may be downed during a storm or a transformer may be struck by lightning resulting in a power outage. In such instances, querying by the utility's communications system helps identify the location of the outage as well as its extent, so service can be quickly restored.

[0006] One problem with today's utility systems is their vulnerability to natural and manmade catastrophes. Computer hackers, for example, have tried to, and in some instances succeeded, in disrupting a utility's operations. Also, there is the increasing threat of terrorists damaging vital portions of the utility's infrastructure incapacitating the utility. It has been known for years that high energy electrical impulses produced by a nuclear explosion can destroy integrated circuit chips which are the heart of the electronics now universally employed throughout homes and industries, including utility systems, causing massive power disruptions.

[0007] With respect to natural causes, there is, for example, the susceptibility to solar flares such as those responsible for the so-called Carrington Event of 1859. In that instance, a geomagnetic storm was produced by an intense solar flare. The resulting coronal mass ejection from the sun reached the earth in less than 18 hours and among other things resulted in the failure of telegraph systems throughout North America and Europe. A similar geomagnetic storm in March 1989 disrupted power across large sections of the Quebec province in Canada. Another “Carrington-class” storm occurred in July, 2012, but missed the earth's orbit. Significantly, in 2013, a joint venture including both insurance companies and scientific groups estimated that the current cost of a Carrington event affecting the U.S. could exceed over $1 trillion in damages. (See www.wikipedia.org under the heading “Solar storm of 1859”).

[0008] There is, accordingly, a need to provide operational safeguards to utilities to protect from, or ameliorate, the effects from the possible occurrence of these events.

[0009] In addition to the above, utilities currently employ versions of open communications interconnection (OSI) protocols for communications throughout their communications system to obtain operational data, control operations at particular sites, and confirm that the requested operations are performed. An OSI is characterized by its ability to provide communication functions without regard to a utility's underlying internal structure and the technology employed in the system. As understood by those skilled in the art, an OSI classifies the communications process into a series of interconnected layers defined as follows:

• • [0010] Layer 1—physical layer;
  • [0011] Layer 2—data link layer;
  • [0012] Layer 3—network layer;
  • [0013] Layer 4—transport layer;
  • [0014] Layer 5—session layer;
  • [0015] Layer 6—presentation layer; and,
  • [0016] Layer 7—application layer.

[0017] A brief overview of an OSI and each of these layers is found at www.wikipedia.org under the heading “OSI model”. A more detailed description of each layer, its functions and operations is found in, for example, Computer Networks, 5th ed., by Tanenbaum and Wetherall.

[0018] Those skilled in the art understand that, at each layer, two entities exchange information/data using an established protocol for that layer. The particular characteristics for each layer and the protocols employed thereat are available in the above references, as well as elsewhere, and are not described herein. It is understood, however, that current protocols available to systems' users are adaptable to a particular system application.

[0019] As one example, an International Electrotechnical Commission standard; i.e., IEC 61968-0:2013 is used in utility RF communication systems, at the applications layer, to communicate between a central utility location C, as indicated in FIG. 1, and meters M installed at using sites or facilities F. The IEC 61968-0:2013 standard has different schema (i.e., 48 schema) defined for respective purposes of a communication. One such schema is, for example, to request a meter reading at a site F, and to report the meter reading back to the central location.

[0020] A problem with the present schema is that even though some of them are quite large, they are still not necessarily adequate to meet a utility's need for certain applications. Also, the current schema is somewhat cumbersome. For example, a “read meter” request in the IEC 61968-0:2013 format is formulated as a string, and an extensive technique (not described) is required to build an identifier which describes the unit of measure for an electric meter M's measurement. The format uses both whole numbers (integers) and dots (“.”).

[0021] Thus, to request a typical dial reading off the face of a residential electricity meter M, the identifier used in an Application Programming Interface (API) would be, for example,

• • [0022] 0.0.0.1.4.1.12.0.0.0.0.0.0.0.0.3.72.0,
    the construction rules specifying 18 fields composed of characters; i.e., the digits and the dots.

[0023] The present invention is directed to improvements in electric utility meter reading schema to enhance the functionality of a utility's communication system. The improvements facilitate the creation of appropriate messages sent to facilities using programming techniques which both simplify the message as well as increase the number and types of messages transmitted; the latter enabling a utility to define custom “parameters” which are read, written, and interpreted in the same manner as with other standardized message formats.

[0024] The improvements include conversion of a device's native language (the language with which the device was programmed) into a neutral language for carrying messages from a point of origination or Head End to a receiving location or End Point so devices having different native languages can readily communicate with each other. This creates an opportunity for an “Internet of Things” capability.

[0025] The improvements enable facilities within a local area; i.e., a micro-grid, of a utility to employ alternate channels of communications between them in the event regular communications fail for some reason so that these facilities can reliably communicate back-and-forth separately from the utility's normal communications channels until normal communications are restored. Facilities within the locale (micro-grid) are now able to check on each other's status, carry out emergency operations at a particular site, if necessary, and otherwise assist each other during the event without having to be routed through the utility's central communication facility. Doing so permits de-centralized communications.

[0026] The improvements enable “end point” configurability; i.e., the ability to set up a communications module within a smart meter located at a particular site (an end point) while not affecting either normal communications at that site, or communications with other meters at other locations.

[0027] Further, the improvements facilitate communications between dissimilar devices; e.g., meters made by different manufacturers or which use different language protocols so to eliminate problems resulting from the use of dissimilar equipment within the system.

[0028] The improvements, which are facilitated by a device located at a “head end” location such as a substation of a utility's distribution grid, enhance OSI communications protocols at the applications level of the utility's communications system.

[0029] Corresponding reference characters indicate corresponding parts throughout the several views of the drawings.

[0032] The following detailed description illustrates the invention by way of example and not by way of limitation. This description clearly enables one skilled in the art to make and use the invention, and describes several embodiments, adaptations, variations, alternatives and uses of the invention, including what is presently believed to be the best mode of carrying out the invention. Additionally, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The invention is capable of other embodiments and of being practiced or carried out in various ways. Also, it will be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting.

[0033] In accordance with the present invention, a smart meter M utilizes the IEC 61968-9:2013 (hereinafter “Part-9”) schema standard as a neutral language. As such, the Part-9 standard supports operation of any smart meter M, regardless of its source of manufacture, including system control and data acquisition (i.e., SCADA) operations. The Part-9 standard can be extended as required and is used to define or “map” each meter in the original or “native” language with which the meter was programmed during its manufacture. An example of the use of the Part-9 schema for reading a meter, for example, is shown in FIGS. 2-4.

[0034] In accordance with the invention, a translation protocol or device D converts the native language of a meter into the neutral language which, once implemented, provides a common semantic understanding between a message's sender, which is sometimes referred to as the “Head End” or “HE”, and the message's receiver, which is sometimes referred to as the “End Point” or “EP”. As previously noted, this neutral language is employed at the application layer of a protocol stack. Device D may be located at a substation S as shown in FIG. 1 or other convenient Head End location.

[0035] In operation, translating device D services one or more native languages including: ANSI C12, IEC-61850, DNP, SEP, DLMS/COSEM, other standard application-layer languages, and other proprietary application-layer languages.

[0036] Translating device D is installed outside of the equipment; e.g., meters M, which are issuing or receiving messages; and, it can be integrated into a communication module located at a Head End facility, substation S, for example, to provide translation within a communications channel. Further, each meter has a communications module programmable to communicate with meters programmed for a different native language.

[0037] In FIG. 1, be bi-directional communications over a grid G of the utility are routed through a central controller located at the substation. In such a communications scheme, translation is also bi-directional. Accordingly, an end point or meter M is able to communicate back to a central controller located at substation S and can also route traffic to other devices connected via the same central controller. This is done using Internet Protocols versions 4 or 6 (1Pv4, 1Pv6) or a Network Address Translation (NAT) protocol to communicate back to the central controller and be backhauled to a Head End. Data acquired by a meter M or other equipment is routed to a back office advanced metering interface (AMI) Head End as well as to a back office SCADA Head End or a centralized or back office energy management system (EMS).

[0038] An advantage of the above is that in addition to communications over the utility's grid G, it is now possible for communications within a localized area such as the micro-grid MG designated in FIG. 1 to be performed. Situations where communications within a micro-grid are desirable include those where network wide communications are halted due to a storm or other natural causes as well as manmade incidents. In such instances, the improvements of the invention now allow the facilities F1-F5 in FIG. 1 to communicate with each other, but not necessarily to substation S or other sections of the utility grid, so to determine the operational status at each facility, any configuration changes needed at a facility in order for continued functioning of equipment at the facility, and data acquisition. Since the meters or other equipment at one facility may not necessarily be the same as that at other facilities within micro-grid MG, the ability to go from a native language to a neutral language allows communications to timely occur locally without requiring communication backhaul to a central office such as substation S.

[0039] Within micro-grid MG, the local communications are point-to-point or peer-to-peer, and are routed through the micro-grid's communication infrastructure without reaching a Head End. The communications are routed through the meters M at the various facilities F1-F5 to, for example, consumer appliances, in-home displays, utility distribution automation including, for example:

• • [0040] capacitor bank controllers, transformer tap changers, switch reclosers, micro-grid controllers, inverters, and distributed generation equipment;
  • [0041] demand response applications for load control and price response, etc.;
  • [0042] outage detection and power restoration management equipment including lineman diagnostic tools; and,
  • [0043] health monitoring equipment.

[0044] A distributed micro-grid controller, for example, allows inputs for a locally determined action such as distribution-side voltage sag so to inform a storage battery array that it needs to begin to provide an output to meet load demands.

[0045] With regard to mapping, as previously noted, the IEC 61968-9 standard has been selected as the neutral language. Mappings created between the neutral language and the equipment's native language entail an equivalency between a “restful” architecture and the equipment's native architecture. On the restful side, a resource and a verb are identified to perform a particular action. On the equipment side, this involves a process workflow usually including “reading” or “writing” data elements, and possibly the creation and close-out of secure sessions. Further on the restful side, parameters are supplied to specify exactly what is to be done; i.e., acquire data, perform a function, etc. On the equipment side, specific neutral parameters are mapped to specific native parameters. The formats of both are specified, along with a conversion formula.

[0046] An example of a mapping from an end point's native language to and from the neutral language is provided below. Preferably, mappings are maintained in a tabular form but can be expressed in BPEL (Business Process Execution Language), OWL (Ontology Web Language), as well as other means.

[0047]

Neutral Language	Native Language
Reading Type ID	Reading Type Description	Format	ANSI C12.19 Location
0.0.0.1.1.1.12.o.o.o.o.o.	bulkQuantity forward	Decimal	TOTAL_DEL_KWH (MFG Table 19,
0.0.0.3.72.0	electricitySecondaryMetered energy (kWh)		Length 4B, Offset 4B)
0.0.0.1.20.1.12.o.o.o.o	bulkQuantity total electricitySecondaryMetered	Decimal	TOTAL_DEL_PLUS_RCVD_KWH (MFG
0.0.0.0.3.72.0	energy (kWh)		Table 19, Length 4B, Offset 8B)
0.0.0.1.4.1.12.0.0.0.0.0.	bulkQuantity net electricitySecondaryMetered	Decimal	TOTAL_DEL_MINUS_RCVD_KWH (MFG
0.0.0.3. 72.0	energy (kWh)		Table 19, Length 4B, Offset 12B)
0.0.0.1.19.1.12.0.0.0.0.	bulkQuantity reverse electricitySecondaryMetered	Decimal	TOTAL_REC_KWH (MFG Table 19, Length
0.0.0.0.3.72.0	energy (kWh)		4B, Offset 16B)

[0048] The following example is for a meter reading definition. A conversion formula is also supplied in Y56109FDS:

[0049] $\begin{array}{cc}\frac{\mathrm{Ke}=\mathrm{Mp}\times \mathrm{Kh}}{1000},& \mathrm{Equation}I\end{array}$
The definition of Ke for Metered Usage (Secondary Reading)

[0050] $\begin{array}{cc}\mathrm{EnergykWh},=\left({\mathrm{Energy}}_{\mathrm{pulses}}\times \mathrm{Kex}\mathrm{Rp}\right)+\mathrm{lnitia}/\mathrm{Offset}\mathrm{kwh},& \mathrm{Equation}2\end{array}$
BulkQuantity Energy Pulses to kWh conversion Where,

[0051] $\mathrm{EnergykWh}=\mathrm{Energy}\mathrm{in}\mathrm{its}\mathrm{finished}\mathrm{form}\mathrm{as}a\mathrm{useable}\mathrm{business}\mathrm{value}.$ $\mathrm{Energypulses}=\mathrm{Energy}\mathrm{in}a\mathrm{raw}\mathrm{form}\mathrm{from}\mathrm{the}\mathrm{meter}$
Mp, is the number of meter disk revolutions per pulse. (This value may be used to normalize pulses. For electromechanical meters it is customarily computed as the 1/“the number of stripes on the disk”. For solid-state meters, this is ratio of normalized pulses to actual pulses).

[0052] Kh, is the number of Watt-hours per disk revolution.

[0053] $\mathrm{Rp}=\mathrm{AMR}\mathrm{decompression}\mathrm{scalar}.(\mathrm{Normally},\mathrm{for}\mathrm{usage}\mathrm{calculations}\mathrm{Rp}=1).l\mathrm{nitialOffsetkWh}=\mathrm{The}\mathrm{value}\mathrm{determined}\mathrm{at}\mathrm{time}\mathrm{of}\mathrm{integration}\mathrm{which}\mathrm{defines}$
the difference between the dial reading and the corresponding register reading expressed in kWh.

[0054] Importantly, use of a neutral language to carry messages creates opportunities for an Internet of Things capability. To achieve this, adapters or translating devices D are built at each end of a communications network to convert the neutral language to the local or native language. An exception to this would be a utility's back office since the language chosen as the neutral language is the language of the back office. Future developments include developing an enclosure that contains a device D and a communications synergization module that allows almost any distribution automation (DA) device to be connected into the system. The DA devices would have autonomous analysis capabilities to communicate with meters M so to obtain field environment conditions such as voltage or demand.

[0055] In view of the above, it will be seen that the several objects and advantages of the present disclosure have been achieved and other advantageous results have been obtained.