Metering System Tamper Detection

A metering system for metering consumption of a commodity. The metering system comprising a meter socket and a meter. The meter comprising a memory, a plurality of sensors, and a processor. Each of the plurality of sensors is configured to detect a different condition of the meter. The processor is configured to determine a plurality of events that have occurred based on the conditions detected by the sensors; compare the plurality of events to a table stored in the memory of the meter, the table defining an action to be performed by the meter for each of a plurality of different combinations of the plurality of events; select an action from the table for which the plurality of events match a corresponding combination of events stored in the table; and perform the selected action.

TECHNICAL FIELD

The present invention relates to a metering system and method, and more particularly, to systems and methods for detecting abnormal conditions in a metering device.

BACKGROUND

Metering systems are subject to tamper events. Tamper events may include anything from bypassing a disconnect switch within a meter to interchanging meters from one consumer location to another. Because metering systems can be tampered with in many ways, there are many ways in which a meter can react. Current metering systems have a variety of tamper detection methods available; however, generally a single tamper sensor results in a single meter response.

The foregoing background discussion is intended solely to aid the reader. It is not intended to limit the innovations described herein. Thus, the foregoing discussion should not be taken to indicate that any particular element of a prior system is unsuitable for use with the innovations described herein, nor is it intended to indicate that any element is essential in implementing the innovations described herein. The implementations and application of the innovations described herein are defined by the appended claims.

SUMMARY

An improved metering system for determining whether a tamper condition is present in a metering device is desired to more effectively determine what corrective actions to carry out.

An aspect of the present disclosure provides a metering system comprising a meter socket and a meter. The meter is configured to couple to the meter socket. The meter comprises a memory, a plurality of sensors, and a processor. Each of the plurality of sensors are configured to detect a different condition of the meter. The processor is configured to: determine a plurality of events that have occurred based on the conditions detected by the sensors; compare the plurality of events to a table stored in the memory of the meter, the table defining an action to be performed by the meter for each of a plurality of different combinations of the plurality of events; select an action from the table for which the plurality of events match a corresponding combination of events stored in the table; and perform the selected action.

Another aspect of the present disclosure provides a method for controlling a meter. The meter and a meter socket composing a metering system. The method comprising: detecting a plurality of different conditions of the meter; determining a plurality of events that have occurred based on the detected plurality of different conditions; comparing the plurality of events to a table stored in a memory of the meter, the table defining an action to be performed by the meter for each of different combinations of the plurality of events; selecting an action from the table for which the plurality of events match a corresponding combination of events stored in the table; and performing the selected action.

Another aspect of the present disclosure provides a meter comprising a memory, a plurality of sensors, and a processor. Each of the plurality of sensors is configured to detect a different condition of the meter. The processor is configured to: determine a plurality of events that have occurred based on the conditions detected by the sensors; compare the plurality of events to a table stored in the memory of the meter, the table defining an action to be performed by the meter for each of a plurality of different combinations of the plurality of events; select an action from the table for which the plurality of events match a corresponding combination of events stored in the table; and perform the selected action.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Description of the Invention section. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not constrained to limitations that solve any or all disadvantages noted in any part of this disclosure.

DESCRIPTION OF THE INVENTION

The disclosure relates generally to metering systems and methods for monitoring consumption of a commodity, such as electricity. Although the system and methods are described herein in the context of a system for metering electrical energy consumption, it is understood that the system and methods described herein may be implemented in systems that monitor consumption of other commodities, such as, for example, water or gas. In one embodiment, the metering system includes a meter and a meter socket located at a customer location. The metering system includes a means for obtaining information from the meter and meter socket. This could be a physical connection such as a cable between the meter and device in the socket, a wireless RF connection, or other means. In this description, the meter includes at least one sensor, and the meter socket includes an information storage device comprising identification information. As used herein, the term “information storage device” will be understood to include a means to store identification information in the meter socket and a means to communicate that information to the meter as described in further detail below. When the meter is coupled to the meter socket, at least one sensor may obtain information from the metering system, such as the identification information from the information storage device, a movement of the meter, a magnetic field, a power interruption, a reverse energy, an excessive number of security access failures, a current transformer saturation, or still other meter information. Based on the information obtained from the at least one sensor, the metering system may determine an appropriate response or action.

FIG. 1provides a perspective view of a metering system90having a meter100and a meter socket112that may be installed at a utility customer location. The meter socket112may, in turn, be connected to one or more electrical loads at the customer location. In one embodiment, the meter socket112is configured to receive and electrically connect with blades101of the meter100. Meter100may include a meter cover103and may be any type of meter configured to measure and indicate the amount of energy consumption at a customer location, such as a residence, industry or business.

Meter100may be part of a metering network in which the methods, systems, and apparatus disclosed herein may be employed. The metering network may comprise a plurality of meters100, which are operable to sense and record consumption or usage of a service or commodity. Meters100may be located at customer premises, such as a home or place of business. Meters100comprise circuitry for measuring the consumption of the service or commodity being consumed at their respective locations and for generating data reflecting the consumption, as well as other data related thereto. Meters100may also comprise circuitry for wirelessly transmitting data generated by the meter to a remote location. Meters100may further comprise circuitry for receiving data, commands or instructions wirelessly as well. Meters that are operable to both receive and transmit data may be referred to as “two-way” meters, while meters that are only capable of transmitting data may be referred to as “transmit-only” or “one-way” meters. In bi-directional meters, the circuitry for transmitting and receiving may comprise a transceiver.

The meter socket112may further comprise an information storage device or tag116. The tag116may be attached to any part of the meter socket112with adhesive glue, double-sided or single-sided tape, soldering, or other similar adhesive commonly used by those skilled in the art.

The tag116may be a radio frequency identification (RFID) tag, such as a near field communication (NFC) tag. The tag116may contain electronically stored identification information that is unique to tag116and may be identified by using radio waves at, for example, a 13.56 MHz frequency. The tag116may contain an induction coil (not shown), that through excitation generated by a variable electromagnetic field generated by a reader, powers a small circuit (not shown) that is read by the reader through RF waves. In one embodiment, the tag116comprises an NFC tag, which is a subset of RFID tags. In one embodiment, the tag116is a passive device. In other embodiments, the tag116may be an active device.

In an aspect, every meter socket112within a metering network may be equipped with a tag116that includes identification information that uniquely identifies that meter socket. The identification information may include, for example, a geographic location of the meter socket112. Each tag116may be supplied in bulk, supplied with every meter100, or pre-installed in the meter socket112. For example, the tag116may be taped onto a cover of the meter100using a peel-off sticker. When a meter technician installs the meter100with the socket112, the tag116may be peeled off and coupled to the socket112. Each tag116may be pre-encoded or may be encoded by a technician installing the tag116.

FIG. 2illustrates an embodiment of a meter100, according to an aspect of this disclosure. The meter100is interposed into electricity distribution lines120, and the meter100is disposed between an electrical energy source102and an electrical load(s)114at a utility customer location. In the embodiment shown, the meter100meters electrical energy delivered from the source102to the load114via distribution lines120. In particular, the meter100connects to a source-side of the distribution lines at contacts120A and120B and to a load-side at contacts120C and120D. The meter100measures the consumption of electrical energy by the load114.

As further shown, the meter100comprises a disconnect switch104, a controller140, and an optional communications interface150. The meter100may further comprise other components commonly used in metering devices. This description is specific to a single phase meter, but the principles are also applicable to polyphase electricity meters as well.

The disconnect switch104is interposed into the distribution lines120and is configured to switch between an open position, in which electrical energy is not supplied to the electrical load114, and a closed position, in which electrical energy is supplied to the electrical load114. Electrical energy (at meter inputs “L1 IN” and “L2 IN”) is supplied by the source102and delivered, via source side distribution lines120A and120B, through meter100, to the electrical load at the customer location114(via meter outputs “L1 OUT” and “L2 OUT”). Disconnect switch or electrical relay104is interposed into the distribution lines120, effectively separating the distribution lines into source side distribution lines120A and120B, and load-side distribution lines120C and120D. As shown, in this embodiment, the disconnect switch or relay104comprises two switches106,108—one for each distribution line. When disconnect switch104is closed, electrical energy should be supplied to customer location114, and when disconnect switch104is open, no electrical energy should be supplied to customer location114. The switches106,108may be driven by a motor, a solenoid, or other means commonly used to drive a disconnect switch.

The optional communications interface150may be configured to communicate with the controller140and a remote utility monitoring location170. The optional communications interface150may be a two-way communications interface to the remote utility monitoring location170(e.g. head-end system) and may comprise any suitable communications interface technology, such as a radio frequency (RF) transceiver, or an interface to the telephone lines or power lines at the customer location114, etc. The optional communication interface150may communicate with remote utility monitoring location170via communications link175. Communications link175may be a private or public network, such as a subnet/LAN.

The controller140may be configured to record data reflecting energy consumption measured by the meter100and to control various internal functions of the meter100. The controller140may be an electronic control unit, computing device, central processing unit, or other data manipulation device that may be used to facilitate control and coordination of any of the methods or procedures described herein.

In one embodiment, the controller140comprises a processor142, such as a microprocessor, microcontroller, or the like, a memory144, and sensors146. The processor142may be operatively coupled to the sensors146, the disconnect switch104, the memory144, and the optional communications interface150. The processor142may be configured to receive signals from the sensors146, the disconnect switch104, the memory144, and the optional communications interface150, to process the signals, and to store the signals in memory144.

The utility monitoring station170may send and receive commands to and from the meter100via communications link175. In response to a command, the controller140may operate the meter100by, for example, operating the disconnect switch104to open or close position, reading measured current or voltage information within the distribution lines120, or performing other metering operations. Information received by the controller140from the utility monitoring station170, sensors146, or other metering components may be stored in memory144. Information received by the controller140may also be provided to the remote utility monitoring location170to be stored remotely.

FIG. 3illustrates a block diagram of an embodiment of the components that may comprise the controller140. Sensors146may include a current sensor302, a voltage sensor,304, an identification sensor306, a motion sensor308, a cover removal sensor310, a magnetic sensor312, or still other sensors. While the controller140is represented as a single unit, in other aspects the controller140may be distributed as a plurality of distinct but interoperating units, incorporated into another component, or located at different locations on or off the meter100.

The current sensor302and the voltage sensor304are configured to measure current flow and voltage, respectively, at contacts120A and120B on the source-side of the distribution lines120. In alternative aspects, the current sensor302and the voltage sensor304may be further configured to measure current and voltage, respectively, at contacts120C and120D on the load-side of the distribution lines120. The current sensor302and the voltage sensor304may provide signals to the processor142indicative of the current flow and voltage, respectively.

The identification sensor306, also referred to as a reader, may be coupled to the processor142. The identification sensor306is configured to obtain (e.g., read) the identification information from the tag116and provide a signal indicative of the identification information to the processor142. The sensor306may be an RFID reader and/or a NFC reader.

The motion sensor308may be coupled to the processor142and configured to sense a motion of the meter100. For example, the motion sensor308may be configured to sense a tilt or vibration of the meter100relative to the meter socket112due to, for instance, removal of the meter100from the socket112or an external force applied to the meter100. The motion sensor308may provide a signal indicative of the motion to the processor142.

The cover removal sensor310and the magnetic field sensor312may be coupled to the processor142and configured to sense whether the meter cover103has been removed from the meter100and whether a magnetic field exists at the meter100location, respectively.

Sensors146may further include devices capable of sensing reverse energy, detecting excessive security access failures, power interruption, detecting current transformer saturation, or still other metering parameters.

In accordance with an aspect of the system and method described herein, during installation of meter100into the meter socket112at a given customer location, the meter100may be paired with identification information of the tag116of the meter socket112. In one embodiment, a technician may use an installation tool (not shown) equipped with a tag reader to read the tag116of the meter socket and then112to input the identification information to the meter100. In other embodiments, the sensor302of the meter100may automatically read the identification information from the tag116upon insertion of the meter100into the socket112during initial installation. The meter100may then store information indicative of its pairing with the identification information for the socket112. In this respect, the stored identification information obtained from the tag116of the meter becomes the “expected” identification information for that meter. This pairing of the meter100with the identification information of the tag116may also be recorded by the technician using the installation tool, or the pairing may be reported by the meter100to the remote utility monitoring location170via the communication interface150.

Thereafter, in operation, upon power up of the meter100, the sensor302may read the tag116attached to the meter socket112to obtain its identification information and may compare the identification information read from the tag116to the “expected” identification information recorded during the initial meter pairing.

FIG. 4illustrates a method400for determining a meter response based on conditions of the meter100(e.g. a tamper event), according to an aspect of this disclosure. The method400may begin by power cycling the meter100(e.g., power up after a power down). At step402, the meter100determines whether the motion sensor308is enabled. If the motion sensor308is enabled, then at step404, a condition of the meter100is sensed, for example, a motion of the meter100, by the motion sensor308. The condition of the meter100may be stored in memory144. At step406, the processor142determines whether a motion of the meter100has been detected. Determining whether motion has been detected may include a motion test. The motion test may include, for example, sensing a frequency of the motion (e.g. 4 movements/tilts) of the meter100over a certain time period (e.g. 2 minutes). If 4 movements/tilts of the meter100are sensed within the 2 minute time period, the meter100fails the motion test, indicating that motion of the meter100has been detected. At step408, if motion has been detected, the processor142may log this in memory144as a ‘fail’ event and may send an alert to the remote utility monitoring location170. Conversely, if motion of the meter100has not been detected, the processor142may log this in memory122as a ‘pass’ event.

If the motion sensor308has not been enabled, or after motion detection has occurred, then at step410, the meter100determines whether the identification sensor306is enabled. If the identification sensor306is enabled, then at step412, the identification information is read from tag116by the identification sensor306. The identification sensor306provides a signal to the processor142indicative of the identification information. The processor142may store the identification information from the tag116in memory144. At step414, the processor142compares the signal indicative of the identification information read from the tag116with the expected tag116identification information stored during the initial pairing of the meter100with the socket112. At step416, if the signal indicative of the identification information read from the tag116of the meter socket112does not match the expected identification information recorded during the pairing process, or the identification sensor306fails to read the tag116of the meter socket112, then the processor142may log this condition as a ‘fail’ event in memory144and may send an alert to the remote utility monitoring location170. Conversely, if the identification information read from the tag116does match the expected identification information recorded during the pairing process, the processor142may log this condition as a ‘pass’ event in memory144.

If the identification sensor306has not been enabled, or after identification detection has occurred, then at step418, the meter100determines whether the voltage sensor304is enabled. If the voltage sensor304is enabled, then at step420, a condition (e.g. a source-side voltage or a load-side voltage) at the meter100is detected by the voltage sensor304and stored in memory144. At step422, the processor142determines whether a voltage of the meter100has been detected. Determining whether voltage has been detected may include a power fail test. The power fail test may include, for example, sensing a source-side voltage of the meter100over a certain time period (e.g. 2 minutes). If there is no source-side voltage sensed for more than the 2 minute time period, the meter100fails the power fail test, indicating that voltage has not been detected at the meter100. At step424, if voltage has not been detected, the processor142may log this event in memory144and may send an alert to the remote utility monitoring location170.

If the voltage sensor304has not been enabled, or after voltage detection has occurred, then at step426, the meter100determines whether the cover removal sensor310is enabled. If the cover removal sensor310is enabled, then at step428, the cover removal sensor310senses a condition (e.g. whether the meter cover103has been removed from the meter100) and stores an indication of whether the cover113has been removed from the meter100in memory144. If the processor142determines the cover113has been removed (430) from the meter, at step432, the processor142may log this event in memory144and may send an alert to the remote utility monitoring location170.

The method400only illustrates one example of detecting an abnormal condition. Fewer sensors146may be used, or more sensors146may be used, for example, the magnetic field sensor312. Additionally, the order in which the sensors are checked to determine whether they are enabled may vary. For example, the status of the cover removal sensor310may be checked prior to the status of the motion sensor308.

If the magnetic field sensor312is enabled, the magnetic field sensor312may sense a condition (e.g. a magnetic field) at the meter100. The processor142may determine whether a magnetic field has been detected using a magnetic field test. The magnetic field test may include, for example, a magnetic field sensor threshold (e.g. 1.2 Volts) and a time duration that the magnetic field sensor's output is above the threshold (e.g. 10 seconds). If the sensed magnetic field sensor's output is above 1.2 Volts for more than 10 seconds, the meter100fails the magnetic field test. An indication of this failure event may also be used in determining whether an appropriate response of the meter100.

Each of the sensors146may be configured to provide a set of inputs to the processor142. For example, the following indicators for the conditions detected by the sensors146may be provided to the processor142during the method400: an indication of whether the sensor146is enabled, whether a threshold has been exceeded, a frequency with which the threshold has been exceeded, and the time duration the threshold has been exceeded. Each of the indicators provided to the processor142may be used to determine whether each test (e.g. motion test, power fail test, identification test, cover removal test, and magnetic field test) has failed or passed. The result of each test or the status of the particular sensor146(e.g. pass, fail, or not enabled) may be stored in memory144as an event.

Based on each of the indicators for the conditions sensed by the sensors146logged in memory144, at step434, the meter100may determine an appropriate response. For example, the meter may respond by recording billing information to an alternate register, taking a billing snapshot, logging the abnormal condition in memory144, disabling the optional communications module150, controlling the disconnect switch104to the open position, sending alarms to the remote utility monitoring location170, or still other responses.

FIG. 5illustrates a table500stored in the memory144of the meter100in accordance with one embodiment. As shown, the table comprises a plurality of entries502,503,504,505, and506, each of which defines an action to be performed. For example, for a particular combination of detected events, the detected events are compared to the events stored in table500, and an action is selected for the meter100to perform based on how the detected events align with the stored events. Table500is merely exemplary and only shows an example of five different combinations of events stored in memory144and their corresponding meter100responses.

Each sensor146may either be enabled or not enabled. If the sensor146is enabled, then the processor142may determine whether the test corresponding to the particular sensor146has passed or failed. For example, the first entry502of the table500illustrates a first plurality of events that indicate that the motion detect test, tag detection, voltage detection, and cover removal tests have all been enabled and have all passed. The magnetic field test has not been enabled, and therefore, has neither passed nor failed. Based on the results of each enabled test, the first entry502indicates that the meter100has no response and continues to monitor consumption. The second entry503of the table500illustrates a second plurality of events that indicates that the motion detect test and the voltage detection have been enabled and have both failed. The tag detection, cover removal, and magnetic field detection tests have not been enabled, and therefore, have neither passed nor failed. Based on the results of each enabled test, the second entry503indicates that the meter100response is to send an alarm to the remote utility monitoring location170. The remaining entries504through506in table500each illustrate additional examples of various events of test results and corresponding meter responses.

It will be appreciated that the list of scenarios502through506is merely demonstrative, and more scenarios and corresponding responses may be contemplated and stored in memory144. Further, additional or fewer tests may be incorporated into each scenario in order to determine the appropriate meter100response.

It will be appreciated that the method400may be repeated at a desired frequency. For example, the method400may repeat after every power cycle of the meter100, or the method400may repeat on an hourly, daily, or weekly basis.

While the disclosure is described herein using a limited number of embodiments, these specific embodiments are for illustrative purposes and are not intended to limit the scope of the disclosure as otherwise described and claimed herein. Modification and variations from the described embodiments exist. The scope of the invention is defined by the appended claims.