Patent Grant
7274305
This invention pertains generally to a control and monitoring system for a plurality of end user companies such as utility companies, surveillance companies, railroad companies and the like, and particularly to a system for monitoring and controlling various parameters and functions related to utilities and these other services. Data related to the services may be automatically collected and sent via control channels of the cellular network to a central data location, where the data is provided to the end user companies. This system also incorporates apparatus for remote electrical power connect/disconnect functions and notification to the user of impending termination of electrical service in an electrical power prepay environment, electrical power outage monitoring, power factor control, phase fault detection, preventative power outage maintenance and power outage maintenance.
In general, utility companies, for the most part, have eliminated the practice of manually collecting water, gas and electricity meter readings. Instead, utility usage sensors and a small electronics package including a low-power radio transmitter, which is battery powered in the case of water and gas meters, is coupled to the meter for sending the meter reading wirelessly to a nearby meter reading collector. In some instances, collecting the meter readings simply involves driving a vehicle equipped with a combined radio triggering device and electronic memory storage for the meter readings past a meter, such as a water or gas meter, so that the radio triggering device causes the meter transmitter to “burst” the meter reading out in the form of a wireless transmission. This transmission is picked up by the receiver and stored in memory for later retrieval. Thus, a meter reader simply drives past a meter to obtain the reading. In other implementations, a meter reader is required to walk up to the meter and touch it with a wand or the like, which incorporates a radio triggering device and memory storage for the meter readings, to likewise obtain the meter readings.
In addition to these so-called “automatic” meter reading systems, prepaid electrical power systems are becoming increasingly common as cost and demand of electricity continues to increase. In instances of individuals who have marginal ability to pay and/or may have dubious credit history, situations where an electrical power technician is sent to disconnect electrical power from a residence of such an individual may become volatile. There have been instances where utility workers have been attacked, and even killed, in confrontations with electrical power users over disconnection of electrical service. Further, notification laws have been passed in areas where disconnection of electrical power may result in direct harm to individuals due to severe inclement conditions, such as from cold weather. In these areas, disconnection of electrical power may not be done without prior notification, which may be a week or more. During that notification period, the individual may continue to use electrical power that may never be paid for. Other problems related to connecting/disconnecting electrical power are that a trained technician must be sent to the site to perform the electrical connection or disconnection of service.
Due to these problems, limited prepaid systems have been implemented. In one such system devised by COMVERGE™, an adapter is plugged into the electrical meter base, with the electrical meter plugged into the adapter. A 200 amp switch coupled to a VHF radio receiver makes or breaks electrical connection between the meter and the user responsive to an ON/OFF VHF signal on a channel reserved for utilities communications (139-174 Mhz). As such, all this system is capable of doing is performing connections and disconnects of electrical power responsive to the VHF signal from the electrical utilities office. In this application, there may be a collection point every square mile or so, depending on topography where houses and collection points are situated.
In addition to the foregoing, other problems are present in management of electrical utilities. For instance, with respect to three phase power, which is common in industrial applications, it is not particularly uncommon for one phase to lose power. When this happens, unprotected equipment, such as motors, may be destroyed.
Utility companies typically attempt to balance loading on three phase circuits so that generators are not overly strained and subject to damage. Here, power factor of each of the three phases is monitored, and if it becomes unbalanced, then capacitor banks consisting of large capacitors are coupled between respective phase lines and a neutral line to connect a large amount of capacitance to the power lines.
In other instances, utility companies use reclosers, which are designed to burn off small limbs, animals such as squirrels and other things that may short out a power line. Here, a recloser functions initially as a circuit breaker to remove power from a shorted power line, but after a brief delay, such as 2 seconds or so, will typically make three attempts to reapply power to the line in order to burn off the object shorting the line. After the third attempt, if the short is still present, the recloser will remain open, requiring utility service personnel to remove the object and possibly repair the line. Where reclosers are operating more frequently than normal, such as in a neighborhood, it may indicate to the utility company that trees in the neighborhood are in need of trimming. In addition, where a recloser is unable to burn off the short, a utility company currently has no way of knowing that power downstream of that recloser is out until people begin to call the utility company to complain.
In related situations, a recloser may be put on a service line to a neighborhood of a hundred or more residences, while every 10 houses or so in the neighborhood may be protected by a fuse in the power line. Here, the recloser may be applying power to the line but a fuse may have blown. Again, the utility company has no way of knowing the fuse is blown until people call to complain that their electrical power is out.
In view of the foregoing, Applicant proposes an integrated system wherein, in a basic embodiment, electrical power connect/disconnect capability is integrated with automatic meter reading wherein the meter reading and connect/disconnect commands are conveyed over control channels of the cellular network and the Internet between the power user and a central location. In an enhancement of the basic embodiment, a prepaid electrical power system is disclosed that automatically provides notification to the user of an impending termination of electrical power. In another embodiment, water, gas and electric meter readings are transmitted by a low-power transmitter to a collection point, which then transmits the readings to a central location over the control channels of the cellular network and the Internet. Any of Applicant's electrical power systems may be configured to transmit data related to power outages so that a utility company may determine in real time exactly where a power outage has occurred. In addition, Applicant proposes a data collection system wherein a data center receives all the data from a diverse variety of sources, such as those described above, and from other sources such as surveillance systems, railroad switch heater systems and others. The data center integrates data from the various sources and allows customer users to access their respective data.
a is a block diagram of one possible interface for a water or gas meter of a meter reading system.
a is a block diagram showing details of construction of the pre-pay electrical utilities system of
b, 6c and 6d are schematic illustrations showing how various electrical utilities devices may be interfaced to a data collection system.
a, 9b and 9c are block diagrams showing detailed architecture of a data collection system of my invention.
a is a flowchart of another of the processes initialized in the flowchart of
b is a continuation of the flowchart of
c is a flowchart of another of the processes initialized in the flowchart of
d is a flowchart of another of the processes initialized in the flowchart of
e is a flowchart of another of the processes initialized in the flowchart of
f is a flowchart of another of the processes initialized in the flowchart of
g is a flowchart showing processing in the data center of remote unit MIN numbers.
a is an image of a continuation of the screen of
a is an image of a screen accessible from the screens of
a is an image of a screen showing a pop-up menu in the screen of
As stated, Applicant's system is a communications, monitoring and control system that may be used in almost any situation where it is desirable to monitor switch closures, or to cause switch closures. As such, Applicant's system is applicable to a wide range of other systems such as, but not limited to, surveillance systems, sewage systems, water and gas utilities systems, and others. In this application, it is to be understood that while a communications system for electrical utilities is disclosed, such disclosure is by way of example only and those skilled in the art should easily understand how Applicant's system may be interfaced with many other systems.
Referring initially to
Within collar 10 are two shorter terminals 20 that receive corresponding prong-type terminals 22 of a 200 amp or so solid state contactor 24, which functions as a relay, and to which 230 volt power is applied from the electrical utilities meter. As such, contactor 24 is positioned to make or break electrical power between the meter and base 13 that in turn provides electrical power to the residence or facility to which it is connected. Extending from terminals 22 of contactor 24 are a pair of extension terminals 26 (only 1 shown) that respectively carry each of the 115 volt phases as controlled by the contactor and which extend upward through the collar to a level of terminals 12. With this construction, prongs 9 of meter 11 that connect to the ground and neutral connections of base 13 are connected to terminals 12 of collar 10, while the two prongs of the meter that each connect to a respective 115 volt phase are each connected to a respective extension terminal 26, the electrical power through which being controlled by contactor 24.
Also connected to contactor 24, as by a “pigtail” and connector 25, is an electronics package 28 mounted within collar 10. Electronic package 28 may be mounted within collar 10 by mounting strips 30 attached to the electronics package and which slidably fit within corresponding interior grooves 32 (only 1 shown) of collar 10. One or two antenna leads (not shown), and depending on configuration of the electronics package, extend from the electronics package to corresponding small antennas (similar in size to cell phone antennas) positioned within the meter 11 so they are generally next to the glass or transparent portion of the meter where radio signals propagate best. These antennae may also be located within an upper portion of collar 10 in instances where the existing electrical meters are not modified, but installation of an automatic meter reading system and/or remote connection/reconnection system is implemented.
The electronics package 28 is shielded against EMF radiation from the adjacent power conductors to prevent interference of its operation, and is connected via 2 or 3 wires, which may be shielded, to a meter-reading device in a mechanical meter, or to KYZ outputs of a digital meter, as will be further described. In some applications, only the electronics package 28 may be installed in collar 10 where only an automated meter reading is performed. Here, the terminals 26 may simply plug into terminals 20, or collar 10 may be constructed so that all the terminals are the same length as terminals 12 so that the collar simply houses electronics package 28 and plugs into respective terminals that carry power through the collar.
In a complete utilities automatic meter reading system, sensors such as those manufactured by BADGER METERS, Inc. of Houston, Tex., may be installed on water meters of residences or businesses, and a similar sensor, such as those manufactured by ITRON, Inc. of Boise, Id., may be installed on gas meters of residences or businesses. These sensors include an encoder that provides a stream of pulses indicative of a current meter reading. Coupled to each of these sensors is a corresponding electronics package including a wireless radio transmitter and control circuitry, as will be further described.
With respect to the electrical meter electronics package 24, reference is made to
Power from power supply 34 or battery 36 is provided to a circuit board 38, which as a significant feature of the invention, is a universal circuit board that may be used in many different applications, as will be explained. Board 38 includes a CELLEMETRY™ radio transmitter and receiver, with an antenna 40 connected to the radio portion of circuit board 38. A switch I/O board 42 is connected between circuit board 38 and contactor 24, and generally conditions and latches the holding currents required to reliably maintain the state of contactor 24.
Referring now to
In a simplest system, information gathered by a remote unit may be sent to a central data center by transmitting a cellular registration number containing at least one bit position for a flag. Likewise, information sent to a remote unit from a central data center may be done by sending a pair of cellular MIN numbers (similar to a page) wherein the first MIN number wakes up the remote unit and the second MIN number is a command for the remote unit to perform a function. Such commands may be configured as software masks in the PROM associated with the COP8 microprocessor.
Still referring to
As an optional feature of the invention, and still referring to
The mechanical-type electrical meter may be read by software that instructs CPU 50 to keep a running total of the number of rotations of rotor 72. The number of rotations is correlated with a quantity of electricity used, such as 1 kilowatt/hour per rotation of the shaft, with the number of rotations fed via lines 82, 84 to CPU 50. A software counter maintains a count of the number of rotations and stores the count in memory until the meter is read. At that time, the number of rotations is retrieved by CPU 50 from memory and transmitted by CELLEMETRY™ radio 62 to the central data location. Where an electronic meter 11 is used, the meter KYZ outputs, which are a series of pulses similar to those provided by rotor 74, is coupled via an I/O port configured as an input to CPU 50 as represented by dashed lines 81. Here, the pulses are counted and a running total stored, in a similar manner as a mechanical meter, to maintain a meter reading from which consumed electrical power may be calculated, which typically occurs at the data center.
During operation, when the meter is fabricated or modified for installation, port 66 may be used to install software and masks into RAM memory, and provide a serial number to the electronics package for identification purposes. After installation, the CELLEMETRY information for that meter is activated at the local cellular switch so that CELLEMETRY™ commands may be passed between the meter and local switch. When first connected, the contactor may be closed by providing a command from the central data location to the CELLEMETRY™ receiver, the command being passed through data selector 64, which functions as a multiplexer to switch serial data sources input to microprocessor 50 between the radio 62 and tranceiver 66.
Responsive to the CELLEMETRY™ command, CPU 50 provides a CLS (close) command to latch 60 via respective I/O ports, which in turn provides the CLS signal to optical coupler and triac 58 to close contactor 24 (
In the instance of a power outage, power control 56 functions as an uninterruptable power supply, automatically switching the components of
Once the unit is installed and electrical power provided to the user, the usage wheel begins to rotate, also rotating rotor 72. As the vanes 74 interrupt the beam of light between transmitters 76 and 80, pairs of pulses are provided to microprocessor 50, each pair being in a sequence indicating proper direction of rotation of the meter wheel. If the meter is tampered with in such a way so as to cause the meter wheel to rotate backwards, then the pairs of pulses occur in the wrong sequence, prompting a message from microprocessor 50 and passed by CELLEMETRY™ to the data center that tampering of the meter has occurred.
Other messages to the data center may also be generated by CPU 50 as needed, such as health messages related to condition or status of the system, including “battery low or inoperable” conditions. In addition, routine meter readings are collected from meter 11 and provided to CPU 50, which are formatted into a CELLEMETRY™ message and transmitted to the data center according to a preset schedule or responsive to a request from the data center to obtain the reading.
Referring to
Referring to
The system of
In another embodiment of an automatic meter reading system suitable for a densely populated area, and referring to
The RF transmitters for water and gas may be constructed as shown and described in
In a prepaid system, and referring to
Referring to
In the prepaid system of
Other features associated with a remote Neuron configuration of the instant invention, and as stated, are a “NOTIFICATION ACKNOWLEDGEMENT” pushbutton available to the resident that provides indication that the customer has received a message related to remaining estimated days of service that will be provided prior to disconnection of electrical service. A “TEST” pushbutton is also provided so that when depressed, a message is applied to the LCD display indicative that the “TEST” button is depressed. Such a test button may be installed within the meter housing or collar, or within another housing, so as to only be available to service personnel. Also coupled to main Neuron 120 is a “NEURON RUNNING” LED to indicate to service personnel that the neuron is operational. Neuron 122 periodically transmits a status message to neuron 120, which in turn communicates the status message to microprocessor 50, the status message including health status of the neuron.
Main Neuron 120 is interfaced to microprocessor 50 via 6 discrete I/O pins, four of which providing the display to LCD display 124. A fifth of these pins indicates operational state of the neuron, and the sixth pin is used to indicate that the resident has pressed the “NOTIFICATION ACKNOWLEDGE” pushbutton associated with the LCD display 124. This indication is in turn transmitted to the data center VIA cellemetry™. Typically, as determined by the data center, whenever a last day/dollar received is less than five days or $50 on the utility account/billing, a warning message will be applied to LCD display 124 to request that the resident press the “NOTIFICATION ACKNOWLEDGE” pushbutton. In the event the occupant does not press the “NOTIFICATION ACKNOWLEDGE” pushbutton when funds are almost depleted, an indication may be provided to personnel in the data center that the “NOTIFICATION ACKNOWLEDGE” at that residence or establishment has not been pressed. Responsive to this indication, a telephone call, or other physical check of the establishment or residence may be made. When the resident pushes the “NOTIFICATION ACKNOWLEDGE” pushbutton, neuron 122 detects this action and returns the LCD display to the dollar/day display. Also, if “4/5 DAYS REMAINING” is the last update to display 124, the software will send a “NOTIFICATION ACKNOWLEDGE” message to neuron 120. If either of the “TEST” buttons (not shown) are pressed, a “TEST MESSAGE” signal will be provided to display 124 on a first line thereof and an indication of which neuron on which the “TEST” button was pressed. The first 4 pins are polled by neuron 120 on a continuous basis, and whenever the value changes to non-zero, the new setting will be communicated to neuron 122 over the power lines of the residence or other establishment and displayed on LCD display 124. When neuron 122 receives a day or dollar setting message, it will output the indicated “DAYS REMAINING” value on a top line of display 124 and indicate “FUNDS REMAINING” on the bottom line. If neuron 122 receives an all 0 message, it will toggle the display between the last dollar/day display and a display indicating that there is a problem in the system and the resident needs to call for service. If neuron 122 has not received a dollar or day update in accordance with a predetermined schedule, a warning message is provided to warn the resident to call for service. The interface between neuron 122 and LCD display 124 is in an asynchronous serial RS-232 format as designated by the LCD manufacturer.
With respect to other applications within an electrical utility, phase fault detection may be accomplished simply by monitoring conventional indicator lamps coupled to each of the respective phases, these lamps typically mounted on a transformer for the phases. As shown in
With respect to reclosers,
d shows connection of I/O lines of microprocessor 50 of circuit board 38 to a motor 117 controlling switching of a capacitor bank for power factor control. While a simple parallel connection is shown, it is to be understood that appropriate isolation of motor current and voltage from the microprocessor would be done, as should be understood by those skilled in the art. In instances where operation is automatic, a CELLEMETRY™ signal is developed that is sent to the data center indicating operation of the capacitor switch motor 117. Where the capacitor motor 117 is not automated, CELLEMETRY™ signals are sent to the remote unit associated with motor 117 to cause operation of the motor.
In any of the above embodiments, indications of operation may be stored in memory for future transmission, or transmitted immediately.
Referring now to
From the cellular telephone system 144, the data is interfaced to the Internet 146 by a conventional cellular gateway 148, which converts and aggregates registrations from the remote units 140 into IP packets and sends the packets to Internet 146. From Internet 146 the IP packets carrying registrations are picked up by Applicant's data center 142, one function of which being a central collection point of registrations, and thus data, from the remote units 140.
In general, there may be two types of remote units, a first type being bidirectional in that data may be generated and forwarded to data center 18 as a registration. Responses or requests for an action may also then be sent from the data center as one or more pages to the remote units, which then act on the request or response. Likewise, pages conveying data may be sent from the main data center to the remote systems, which may respond by sending one or more registrations back to the data center. Examples of uses of the remote units which are illustrative and not intended to be limiting, are to read electrical, water or gas meters, the modules also having a capability of disconnecting water, gas or electricity responsive to commands from the data center. In addition, in areas where electricity is billed at a higher rate during certain times of the day, i.e. peak hours, time of use of electric meter readings may be taken before and after such peak hours in order to meter electrical usage during such peak hours. Further, Applicant's system may be used to perform conservation functions, such as electrical disconnections of hot water tanks at residences during peak hours of electrical usage. Such conservation techniques assist in preventing “brown outs” during the peak usage hours. Power outages may also be reported to the data center, which may then notify a resident via a cellular page or Internet communication, such as email. These communications indicative of power outages may also be sent directly to the resident from the cellular system. Also, the utility company may be notified of such an outage. In addition, notification may be made when power is turned “on” at a residence or other establishment after a power outage. This is useful, for example, in commercial processes such as tire manufacturing wherein a power outage and subsequent restoration may result in defects in a batch of tires being processed when the outage occurs. Other applications include remote switching of capacitor banks in electrical utilities systems, monitoring operation of recloser switches, fault detection in electrical utilities systems, reading transducers of any kind, mobile asset monitoring using GPS, automatic meter reading, prepaid meter reading, and commercial meter reading. As should be apparent, some of these functions may be grouped together; for instance electrical failures may be reported in areas where prepaid or automatic meter reading systems are already in place. This would allow efficient localization of power failures, with utility companies being almost immediately notified of power failures when and where they occur.
Another type of remote module also collects data and sends the data back to the data center, but it may be programmed to act on its own. Illustrative examples of this type remote module are those that may be coupled to capacitor control banks utilized by electrical utility companies. Here, capacitor banks may be connected or disconnected by remote modules automatically, and messages related to such connection and disconnection developed by the remote module and sent back to the data center. Either type module may be used in surveillance applications wherein an illuminating light, which may include visible and infrared illumination, a camera and recording device may be activated automatically responsive to a motion sensor or intrusion type, and a registration indicative of such activation sent to the data center. The video may then be put on a monitor or sent over the Internet to interested parties. This is advantageous inasmuch as while it is obvious that a camera may be readily disabled by a terrorist or other intruder, the registration indicates a time (timestamp from cellular system) that the event occurred so that, for instance, water in a water storage tank may be isolated from a municipal water system until the water in the tank is tested to ensure there have been no hazardous materials introduced therein.
In order to observe the functions performed by the remote units or to command one or more of them to implement a specific task, a user application interface 150 is provided. Application interface 150 may be in the form of an interactive web page displayed any suitable Internet browser, or in any other form usable by a customer. Also, where the interface 150 is loaded into a remote client system, as where Applicant provides a monitoring or surveillance service, the end user may connect to data center 142 via Internet 146 for accessing a respective Web page containing information related to remote units 140.
Also connected to data center 142 is a web server 152 that is provided with a public URL for general public access, and which may contain links for users that are password protected.
Referring now to
With respect to meter reading and funding, the last meter reading of each remote system, including time and date of the reading as well as the meter face value is maintained so that in these systems there is no need to store the meter readings in a memory at the meter, except for buffering purposes. The date and time of the last activation of the “WARNING ACKNOWLEDGE” pushbutton for each remote system is maintained. Also, the last “DOLLAR/DAY REMAINING” value sent to each remote system is maintained, along with the date and time of such sending.
Coupled to the database, and represented by boxes, are software routines and hardware labeled DEVICE MAINTENANCE (box 156), USER INTERFACE SERVER (box 158) and USER MANAGEMENT (box 160). As shown, data flows between the database 154 and routines 156, 158, and 160. The DEVICE MAINTENANCE software 156 maintains a device model library and configuration information library for all devices. As stated, these devices may be electrical, gas or water meters, RF devices, remote modules, mobile assets locatable via GPS, or any other similar devices. Devices internal to a residence or business may include security alarms, HVAC controls, smoke alarms and other devices, and may be connected to the communications module (RM 140 of
Data also flows to and from boxes marked SYSTEM MANAGEMENT 160, BILLING MANAGEMENT 162, CUSTOMER MANAGEMENT 164, and the GATEWAY SERVERS 166a-166c. SYSTEM MANAGEMENT 160 serves to assume responsibility for managing and configuring the data center system. The BILLING MANAGEMENT 162 module associates usage, i.e. issued pages from the data center and received messages from remote modules to a customer, such as a utility company, for purposes of billing. CUSTOMER MANAGEMENT box 164 creates and maintains customer information in the database. As stated, the customer is typically an organization responsible for being responsive to the remote units in one or more aspects, such as billing, meter reading, surveillance, emergency services or any other such billable service. The GATEWAY SERVERS 166a-166c interface the data center to different communications networks, such as the Internet and cellular IS-41 telephone system networks. These servers send control packets to or receive response/status packets from the IS-41 communication network gateway. The gateway server also checks ownership of the incoming packets using an identification embedded in the packets, and relays the packets to respective remote module servers for further processing. The gateway servers transform operation requests from the remote module servers into outgoing packets recognizable by the communications network. Remote module servers process all packets from remote units 10 so that data in the packets is either stored in the database or fed back to the central data system users.
As stated, Applicant's system uses the CELLEMETRY™ short messaging system over control channels of the cellular telephone system through the NUMEREX™ gateway in Atlanta, Ga. NUMEREX™ maintains an almost 100 percent coverage in the United States, and in some areas has dual channel capability. Within this system, Applicants use a 3-watt radio transceiver to communicate with the cellular telephone system.
The CELLEMETRY™ data service uses the overhead control channels of the cellular telephone system for transport of messages. These control channels are typically used, in both directions, to transfer information necessary for call initiations between the cellular customer and base station. There are two types of control channels, each named according to direction of data flow. The forward control channel conveys messages from a base station to a cellular customer, while the reverse control channel conveys messages from the cellular customer to the base station. Since the control channels are underused even during the busiest times of cellular telephone use, there is sufficient bandwidth for Applicant's system to operate concurrently with cellular telephone use. Data from NUMEREX™ indicates that typically during the busiest times of cell phone use, the control channels are only used to about 10 percent capacity.
With respect to the overhead control channels, when a roaming, i.e. out of its home cell system, cellular telephone is first turned “on”, it recognizes the fact that it is out of its home cellular system, and sends its mobile identification number (MIN) and its electronic serial number (ESN) to the system it is in via the reverse control channel. The cellular system the phone is currently in recognizes that the mobile identification number is a roaming number and routes the mobile identification number and electronic serial number of the roaming cell phone to the roaming phone's home system via the Intersystem Signaling Network (ISN-41), which links all cell phone networks in the United States and in most foreign countries together.
In the CELLEMETRY™ system, the CELLEMETRY™ radio functions as a roaming cellular telephone, except that the mobile identification numbers and electronic serial numbers of the CELLEMETRY™ radios are routed to a CELLEMETRY™ gateway coupled to the ISN-41 network. The CELLEMETRY™ mobile identification number identifies the CELLEMETRY™ radio to the system, and the electronic serial number is used, in Applicant's system as a data message to carry meter readings and indicate events such as activation of motion sensors, etc. The CELLEMETRY™ gateway provides a timestamp to the electronic serial numbers and the ISN-41 network adds a coarse indication as to location of the origin of the message. The CELLEMETRY™ gateway and SS7 cellular switch may also be configured to prioritize the messages, with messages such as alarm messages being immediately processed, and other messages such as meter readings being stored and transmitted all at once as a batch file, possibly once a day.
A significant advantage of use of the overhead control channels is that the CELLEMETRY™ data service never employs a voice channel for communication, and is transparent to all cellular telephone users. CELLEMETRY™ transmission utilizes an existing system throughout the United States and requires no modification or extra equipment installations to the cellular system, only standard database translations similar to those of a cellular telephone. Thus, a CELLEMETRY™ remote device may be installed wherever Cellemetry™ service is present (>99% of US) and be operational from the first day, and in many instances within 30 minutes, of installation. Since control channel transmissions are digital by design, they are inherently more reliable. This reliability is increased by each transmission being transmitted five times, with three identical received messages of these five causing acceptance of the message as correct. Also, frequency reuse for the control channels is enhanced so that it is more robust than for the voice channels. Further yet, radio transmissions over the control channels is at higher power levels so that the control channels are operational when the voice channels are not.
The data elements that are conveyed between the remote units and the CELLEMETRY™ gateway are the mobile identity number, which is sent to the remote unit over the forward control channel by the data center, and the electronic serial number, which is sent to be data center by the remote unit over the reverse control channel. The mobile identity number is a 10-digit telephone number very similar to a standard telephone number, while the electronic serial number is a 32-bit binary number. For CELLEMETRY™ applications, the mobile identification number becomes an equipment identification number and the electronic serial number becomes a data packet. Particularly with respect to Applicant's system, each remote unit such as units 140 (
Referring now to the following tables, structure of messages sent between data center 154 (
In one contemplated scheme, the universal mobile identification numbers are used in command sequences to command a particular remote unit or a plurality of remote units within a particular area. The universal mobile identification numbers are allocated once for a cellular switch, and may be allocated so that the base number starts at an even hundred (last three digits of 100, 200, 400, 600, 800) and consumes 160 consecutive mobile identification numbers. The universal mobile identification numbers are used in sets of mobile identification numbers. Each set provides a specific command to the remote unit, and starts at a mobile identification number relative to the universal mobile identification number base number. This allocation is required due to limited RAM space in the remote unit microprocessor. The universal mobile identification number sets, how many mobile identification numbers are required in each set and offset of set from the base are shown in the following Table 1.
For commanded meter reading, when a remote unit receives a page including its unique mobile identification number and a page including a commanded meter read mobile identification number set, the remote unit registers the indicated meter's face value and if enabled, the period time of use (TOU) reading, as shown in the following Table 2 of unique mobile identification numbers followed by respective universal mobile identification numbers.
For prepaid metering with connect/disconnect capabilities, the following Table 3 shows a mobile identification set that may be used for such a prepaid system.
Table 4 shows a mobile identification number set that may be used for controlling opening and closing load control relays.
The following Tables 5 and 6 indicate mobile identification sets for enablement of time of use readings and time of use sequence command mobile identification numbers respectively.
For scheduling time of use readings, i.e. time of use month/day and the schedule number, mobile identification number set of 100 mobile identification numbers is provided in the following Table 7.
Time of use periods end mobile identification numbers, interpretation for the “set weekly schedule command” and “set weekend/holiday schedule command is shown in the following Table 8.
Month/day mobile identification numbers, interpretation for the “set holiday month/day command” mobile identification numbers and “set active month/day command” mobile identification numbers are shown in the following Table 9.
Eight mobile identification number mask registers in the remote units are used. Assignments for these registers are as shown below.
1. RM default (unique) mobile identification number.
2. RM status and disconnect mobile identification number group.
3. Meter reading mobile identification number group.
4. Load control close mobile identification number group.
5. Load control open mobile identification number group.
6. Toggle meter TOU enablement mobile identification number group.
7. TOU schedule definition mobile identification number group.
8. TOU schedule period, month/day, and schedule number mobile identification number group.
Paging sequences for performing the indicated functions are shown in the following Table 10.
The following Tables 11-14 show bit structures of the electronic serial number registrations sent from the remote units.
In the above tables 11-14, the various fields for the 32 bit electronic serial numbers are shown. In these 32-bit fields, the four most significant digits signify a function to be performed. For instance, in Table 11, where the four most significant digits are all zeros, this indicates to the remote unit that a meter reading operation is to be performed. In Table 12, where three ones and one zero is present, this is indicative of a time of use period value to be read. In Table 13, where all ones are present in the four most significant digit positions and a zero is present at bit 27, this is indicative of a detailed status request of the remote unit. In Table 14, where the four most significant digits are ones and bit 27 is also one, this is indicative of a request for the remote unit to transmit its version and model number.
In Table 11, which as indicated is an electronic serial number for transmitting a meter reading, bit positions 24-27 are used to indicate which of up to four meters (electricity, gas, and up to two water meters) are to be read. As stated above, these four bit positions could be used to indicate which of up to 16 meters are being read. Bit positions 0-23 are used to indicate the meter face value (in a 6 digit BCD format) of the meter being read. In Table 12, as indicated, where bit 31 is zero, bit positions 28-30 are used to indicate a time of use period number, and bits 24-27 indicate which meter is to be read. As described, bit positions 0-23 contain a six digit BCD number indicative of the face value of the meter.
Table 13 shows bit positions for a detailed status report of the remote unit. Here, bits 0-23 indicate the following information:
bit 0: FRAM (ferrous random access memory) currently bad.
bit 1: FRAM currently or was bad.
Bit 2: DS1305 (timing chip) currently bad.
Bit 3: DS 1305 is currently or was bad.
Bit 4: CRAD (remote unit) handling software just have a bad step.
Bit 5: CRAD handling software just had or previously had a bad step.
Bit 6: spare.
Bit 7: new problem detected.
Bit 8: AC power condition, 1-on, 0-off.
Bit 9: AC power changed, 1-on, 0-off.
Bit 10: connect/disconnect switch condition, 0-closed, 1-open.
Bit 11: connect/disconnect desired condition, 0-closed, 1-open.
Bit 12: battery low current condition, 1-low, 0-not low.
Bit 13: battery low accumulated condition, 1-was low.
Bit 14: load control actual positions, 0-closed, 1-open.
Bit 15: power outage enabled, 1-yes, 0-no.
Bit 16: page sequence bad-current.
Bit 17: page sequence bad-accumulated.
Bit 18: service available (always 1).
Bit 19: power outage reporting timing, 1-immediate, 0-with delay based on remote module mobile identification number.
Bit 20: bit 0 of AC offs count.
Bit 21: bit 1 of AC offs count.
Bit 22: bit 2 of AC offs count.
Bit 23: bit 3 of AC offs count.
In the remote module detailed status electronic serial number format, bits 24-26 are spares, although these bit positions are used in other electronic serial number formats. Bits 7-15 should be self-explanatory to one skilled in the art, while bit 16 it is indicative of status of a series of global mobile identification numbers issued in a particular sequence. A problem indication here would typically indicate that one of the pages of the sequence of pages was not received. Bit 18 is indicative of a bad sequence since a last report. Bit 18 indicates status of Cellemetry™ service. With respect to bit 19, a power outage is a high-priority event that demands immediate transmission when the bit is set, and a lesser priority when not set. Bits 20-23 indicate a duration of time AC power is off at a monitored site.
It is contemplated that there are to be about nine message types transmitted over the power line network subsystem. The Echelon network addressing scheme is used for addressing each message. Whenever a domain/subnet/node type messages received by a node, an acknowledge message is returned to the sending node. If it the sender does not receive and acknowledge the message within two seconds of the transmission, then the sender will retransmit the message. Two retries are attempted if there is no response from the addressed node. The following Table 15 indicates the type of message, name of the message, originator of the message call when the messages sent, and address type.
Since there are typically more than one residences or establishments coupled to a power line transformer, there will be several sets of neurons coupled to the power line network. Thus, each set of neurons associated with a particular residence or establishment using power from a power line transformer common to other residences/establishments must be uniquely addressed so the messages between any set of neurons will only be seen by that set. The Echelon domain/subnet/node addressing scheme is used to solve this problem. All main neuron modules will be given a unique domain/subnet/node value, with the node value always being an even number, this number set during manufacture. During installation, verification is made via a test set that the power line interface is functioning, and that communications between the two neurons and communications with the test set are enabled. This ensures that the neurons are able to communicate with each other without interference with/from other neuron sets operating on the same power line transformer.
During this installation test, the test set is plugged into an AC wall outlet, and the SERVICE PIN pushbutton pressed, after which, if the neurons are functioning correctly, an ACKNOWLEDGEMENT is received by the test set. If no ACKNOWLEDGEMENT is received, this is an indication that the neurons are not functioning properly. Setting of the domain/subnet/node address of a main neuron is to be done with a test/install test set device. The domain/subnet/node address given to the remote neuron of the pair of neurons is the same as its companion main neuron coupled to the power line interface except the node value of the remote neuron will be the next higher value, i.e. an odd value, with respect to the even number of the main neuron value.
The LCD display 124 is manufactured by MATRIX ORBITAL Inc.™, part number LK162-12. The display is interfaced to the remote neuron via an RS-232 serial port at 2400 baud. As the display is set during manufacture at 9600 baud, the baud rate must be changed as set forth in the display user's manual. This change must be performed prior to integration with the remote neuron.
As earlier stated, the meter reading RF subsystem may include nominally up to three units per residence or establishment, with a fourth of these units mounted in the electrical meter along with the circuit board containing microprocessor 54 and CELLEMETRY™ to radio 50. This remote unit is required regardless of whether any other remote RF subsystems are installed. The RF subsystems monitoring water and gas meters communicate with the remote module over an 837-916 MHz radio link.
As the remote RF units are battery-powered, the remote RF units will be in a “sleep” mode most of the time, with an on-chip timer waking the chip once each hour, or at any other predetermined interval, for a meter reading and transmission cycle. Each reading is transmitted three times to provide redundancy.
Since all RF transmissions are on the same frequency, each remote unit must detect whether there is data currently being transmitted by another remote unit in a nearby residence or establishment. Here, before each transmission from a remote water or gas RF unit to a main remote unit, a check is made as to whether no other water or gas remote within reception range is transmitting. If a transmission from another water or gas remote RF unit is detected, the remote RF unit attempting to transmit will wait a random number of seconds prior to attempting another transmission. This sequence of waiting until no transmission is detected will repeatedly occur until no other transmission is detected, after which the remote unit in need of transmitting will transmit to the respective remote RF unit. Typically, microprocessor 54 is programmed to transmit the meter readings once a day back to the data center where the readings are associated with a customer in the database. Where a meter fails to report, as where the signal is blocked, then a report is generated that is put in a maintenance queue that indicates to service personnel that the meter may need servicing. In other instances, such as where “peak usage” is monitored, one or more meter readings may be made and transmitted back to the data center, or the microprocessor may be programmed to read the meter at the beginning and end of the peak hours and send a single message indicating usage during peak hours.
In other electrical utility applications, remote units coupled to capacitor banks of small and large substations and on electrical poles may be used to control capacitor switching in order to adjust power factor at various points in an electrical distribution system. Related to this and to the prepaid/automatic meter reading system as described supra, is a fault detection system wherein remote units may be located to monitor automatic reclosers and circuit breakers on electrical utility substations and individual electrical branch lines on utility poles or underground electrical systems servicing neighborhoods or other similar localized areas. Here, any information related to electrical power failure or repeated automatic attempts to reconnect electrical power may be reported back to the data center via the overhead control channels of the cellular telephone system. Likewise, with respect to water systems, motion detectors used in conjunction with remote systems similar to that disclosed may be used to detect intrusion upon water storage tanks or areas proximate water intakes for water systems, these intakes many times located to draw water from rivers, lakes or other surface water reservoirs. Again, any intrusion into these areas or onto a water tank would result in an alarm signal transmitted over the overhead control channels of the cellular telephone network and through the Cellemetry™ to gateway to the Internet and ultimately to the data center.
In another similar application, remote monitoring of utility crews or other emergency personnel during severe weather, earthquakes or other natural or manmade disasters may be undertaken in conjunction with the GPS (Global Positioning Service). Here, each service vehicle is equipped with a GPS receiver capable of providing an electronic output indicative of its location, this output coupled to a remote unit as described herein. During an emergency or at other times, a global page may be sent out from the data center, over the Internet and forward control channel instructing all mobile units to report their position, with each mobile unit reporting its position in an electronic serial number via the reverse control channel and back to the data center as described. As this occurs in near real time, crews most proximate a location in need of service may be dispatched posthaste to the location.
As should be apparent from Applicant's disclosure, practically any monitoring service may be accomplished by installation of a remote unit as disclosed herein, with communications to/from the remote units being strictly over the overhead control channels. As no voice communication channels are involved, communication costs are greatly reduced (as low as 0.3 cents/message), and the remote units are relatively inexpensive, in the $100.00-$200.00 range at today's prices. Installation is generally simple, and the system may be operational within 30 minutes of installation, with the only modification to the cellular system being simple software translation tables for correctly routing the mobile identification numbers and electronic serial numbers to the cellular gateway. Further, notifications of alarms or reporting of meter readings or the like may occur by pages, email or otherwise transmitted over the Internet.
With respect to the data center of
For web server 170, VISUAL STUDIO™ ASP NE™ may be used as a programming language. VISUAL C#™ may be used to develop remote module server 172. VISUAL C++™ may be used to develop the gateway server, and MICROSOFT™ SQL SERVER 2000 may be used for the database. For database access, ADO.NET may be used, and HYPERTEXT MARKUP LANGUAGE™ (HTML) may be used for generating reports. Of course, other programming languages may be used, as would be determined by the particular computers and server systems of other applications.
Graphical user interface 168 communicates with web server 170, which also contains service routines or modules for system management 174. System management 174 generally performs management functions, such as system parameter configuration, i.e. TCP/IP port setting, maintenance of lookup tables, system timer control, monitors system performance and manages logs and alarms.
Device configuration 176 provides for adding and deleting discrete remote units, such as electrical meters, collection units, capacitor bank switches, remote units configured for surveillance and any other application. Typically, these functions are performed at an administrative level. User management module 178 allows management of users by administrators and provides administrative privilege control so that operators may be added and deleted and passwords for operators and administrators selected or assigned.
Operational control and monitor module 180 relates to routine functions of the system, such as sending commands that connect and disconnect electrical power, operate capacitor bank switches and perform other functions. Also, this module handles alarms that are presented to operators, and handles other requests from operators of the utility or other company. For issuing commands, module 180 communicates with command queue 182 of the message queue 184. The command queue 182 in turn provides queued command information to web messenger 186. Messenger 186 aggregates MIN numbers so that up to 8 transactions (MIN default numbers for particular remote units or a single global MIN number) may be sent in a single page, with a command MIN (connect, disconnect, etc.) being the ninth MIN number. As such, up to 8 remote units may be “awakened” by the default MIN numbers, with these activated remote units commanded to perform the transaction defined by the ninth MIN number. Here, a transaction is defined as the process of causing a remote unit to perform an action, and receive and process a response from that remote device indicating that the action was accomplished. As such, each transaction is assigned an ID number that includes identification of the remote unit associated with that transaction, given a time stamp and includes a status flag that is used to indicate the transaction's status to various components of the system.
As it generally takes a minute or so for a page to be sent, pages containing the same MIN number, as where a command or request is incorporated into two pages and the pages must be received by the remote unit sequentially, must be spaced apart in time to avoid the possibility of the second page being transmitted prior to the first page. Also, one or more bit positions in the MIN number may be used to indicate to the cellular system where in a sequence a page is to be inserted. Further, the commands may be prioritized in remote module server 172, as where a command or request for data relating to a surveillance system or a request for data relating to an electrical power outage is tagged as a higher-priority message. Such a priority code may range from low, medium and high, thus requiring only two bits to transmit priority information. In other instances, priority may be either low or high, requiring only one bit to transmit priority information. As such, lower priority commands, such as a request to read a meter or obtain daily usage, may be sent when there are no existing higher priority commands to be sent.
The transactions are stored in a transaction hash table 188, after which the commands are obtained by page issuer 190. Hash table 188 incorporates several algorithms such as sorting pages in accordance with a priority scheme, for searching for one or more transactions that generate an error in the system and passing the error to registration handler 192, associating a received registration to a respective sent command and determining an origin, i.e. a source, of commands in the instance where multiple diverse systems are used. Page issuer 190 communicates the commands to the gateway server communicator 194, which in turn issues the pages, as by a conventional TCP/IP socket interface, to gateway server 196 (
Alarm and transaction monitor 198 in web server 170 receives alarms, alerts and similar messages from remote modules and the system in general and provides them to operators of the system. These alarms may be generally indicative of failures of devices connected to a respective remote module, such as a railroad switch heater, a water, gas or electrical meter or surveillance device. In addition, responses to inquires, such as status requests, are provided to operators via alarm and transaction monitor 198. Further, software and hardware errors of the system are reported via alarm and transaction monitor 198. These alarms, inquiries and error messages are provided to monitor 198 by event dispatcher 200. Generally, event dispatcher 200 obtains event data from event queue 202, which temporarily stores transaction results and alarm messages, and associates transaction results messages with a respective MIN number and transaction ID obtained from data base 204. In addition, the event dispatcher correlates a result with a user in the event where multiple, diverse systems to are incorporated in a single service company system.
Event data received by event dispatcher 200 is generated by event generator 206 (
Registration handler 192, responsive to an incoming registration, provides an indication of such to event generator 206 that a registration has been received. Incoming registrations from gateway server 196 that are solicited, i.e. responsive to commands and inquiries, are received by gateway communicator 194 and passed to registration queue 214. From queue 214 the registrations are passed to registration handler 192. Here, operation response 218 associates a transaction in hash table 188 with the registration for the MIN of that transaction and changes status of the transaction to “completed”. This results in the transaction being deleted from hash table 188, although the transaction may be stored in a log or history file in the database. Where the registration is unsolicited, i.e. from an alarm or status change, the registration is compared by autonomous registration module 216 with previous readings to determine what the change of status is, as in a surveillance system where a motion detector is tripped. This change of status is then provided to an operator. Where the registration contains an error message, then the information is sent to event generator 206 to be provided to an operator. In registration handler 192 are temporary storage areas for storing information related to remote units of the system. For example, status is an area where status information of remote units is stored, this information related to power, battery levels and relay and switch positions. MDL/VER is storage for the model numbers and versions of the remote units. ERROR is temporary storage for error messages, and which may generate a warning and store the error message in a log file.
Diagnosis engine 210, containing status tracer 220 and transaction tracer 222, traces transactions to insure they are acted upon and monitors health of the remote modules and network communications. Here, transaction tracer 222 periodically polls transaction hash table 188 for transactions that have been marked as completed by operation response 218, and deletes completed transactions from the hash table. Where a transaction has been acted on in server 172 but no acknowledgement of such was sent by either the cellular system or the gateway server, then transaction tracer 222 waits for a predetermined period of time, such as 2 minutes, and if a confirmation has still not been received, then it causes the transaction to be resent. This delay and resending occurs twice, and if no confirmation is received after the last resending, then transaction tracer 222 causes an alarm to be generated via event generator 206. Status tracer 220 monitors health of the remote units, each of which being typically programmed to transmit a health signal at predetermined intervals, i.e. once a day or once a week or so for remote modules such as in a meter reading application, or at other intervals depending on the application.
MIN register 224 provides temporary storage for adding and deleting MIN numbers for devices in the field that are added or removed. In this instance, when a new device is fielded, a new MIN number is assigned to that device. This new MIN number may be added by an administrator of the service company, or by an operator or administrator of the end user company. The new MIN number is added through device configuration 176, from which the MIN number is added to MIN register 224 and database 204. Register 224 is periodically polled by web server messenger 186, and obtains the MIN number and places it in register MIN queue 226. When a MIN number is found in queue 226 by MIN register or hash table 229, as by polling, the new MIN number is picked up and passed to gateway communicator 194. Communicator 194 in turn passes the new MIN number to gateway server 196 where it is stored in MIN hash table 229. MIN register 224 is also used during initialization of the system. Here, all MIN numbers for all remote devices associated with fielded systems, such as the meter reading systems, capacitor bank switching and surveillance systems, are obtained from database 204 by MIN register 228 and passed to MIN hash table 229 in gateway server 196.
While a direct pathway is shown (for clarity) for transferring MIN numbers from register 224 to register 228, the actual data pathway is through command queue 182, web messenger 186, transaction hash table 188 and registration handler 192. Here, the new MIN number from device configuration 176 is inserted into command queue 182 by MIN register 224. Web messenger 186 then notifies MIN register 228 that a new MIN is being added. MIN register 228 then passes the new MIN number to gateway communicator 194, from which the Min number is passed to gateway server 196 and stored in MIN hash table 229. Such new MINs, when added to server 196, are acknowledged by register min ACK signal 230, which notifies MIN register 228 that the new MIN was successfully registered in hash table 229.
The remote module server health check signal from box 232 to health check module 234, while also shown as a direct connection from remote module system heart 232 for clarity, is in fact sent through event generator 206 and event queue 202 to health check module 234. This signal is provided from the remote module server 172 to rms heart module 232, and indicates health of the remote module server. Health check module 234 in web server 170 monitors general health of the remote modules. Gateway server health checker 236 monitors health of the gateway server, and receives health information via gateway server messenger 212 and health acknowledgement signal 238. In this system, upstream components check health of downstream components, i.e. web server 170 checks health of remote module server 172, server 172 checks health of gateway server 196, etc. If there is a problem with any of the components then an error message is sent to an administrator via event generator 206.
As described, transaction information for sending a page is developed in operational control module 180, as when a command, such as to energize or de-energize one or more heaters, read particular water, gas or electrical meters, etc., may be initiated by a user logged into graphics interface 168. In other instances, operational control module 180 may be programmed to automatically send pages to the remote devices, as where meters are being read. The transaction information for a page is passed to command queue 182 where it is held until called by web messenger 186 and passed to hash table 188, where it is stored until called by page issuer 190. Page issuer 190 issues a page to gateway communicator 194, which in turn passes the page information to gateway server 196. In addition, page issuer 190 provides notification to event generator 206 that a page was issued, and event generator 206 in turn provides notification to the operator as to whether the page was successful or not. Gateway server 196 receives commands and inquiries from remote module server 172, and passes these commands and requests through the Internet to the CELLEMETRY™ gateway. From the other direction, responses and registrations are transmitted by the IS-41 and cellular phone system to the CELLEMETRY™ gateway and through the Internet where they are passed to gateway server 196.
Server 196 receives page requests from remote module server 172 via a socket manager 240 (
The pages are configured into pages at page construction 246, and placed in one of queues 248, or priority page queue 250.
These queues receive the pages as determined by the priority scheme in hash table 188. Here, pages stored in priority page queue 250 are sent first, and when empty, pages from normal page queue 248 are sent. Page transmitter 252 passes the pages to the CELLEMETRY™ gateway to the Internet, from which the page is routed by the IS-41 and cellular system to the remote module associated with the MIN number of the page. If an error occurs, page transmitter 252 provides the MIN number associated with the error to registration router 254, which in turn associates the error with the MIN number of the remote device from hash table 229. Hash table 229 maintains a record of all MIN numbers associated with the socket resources of all remote modules of the system. Registration receiver 256 receives registrations from the remote modules, and passes them to registration router 254, which associates the registration with a corresponding remote server by looking up the default MIN of the remote server in hash table 229. The registration is then passed to socket manager 240 for transmission to remote module server 172 to be processed as described.
A series of flowcharts will now be described, with functions of these flowcharts being generally related to remote server 172 in the block diagram of
Here,
If the command type is a register MIN (box 304), as where a new remote module is added to the system, a MIN number is added to database 204 (
a illustrates, by way of example, one possible logic flow for handling registrations, i.e. the registration handler thread 286 of
More specifically, at box 324 the registration is buffered in registration queue 214, and gateway server 196 (
At box 332 (
At box 336 the registration information is saved to a transaction table in database 204, and at box 338 the registration error message is deleted from the transaction status list (a data structure in hash table 188). Where the answer at box 332 is NO, then the program loops to the beginning to run again at box 324.
As stated, this logic module runs in an endless loop. If, at box 328 a registration was received instead of an error, then at box 340 the ESN number is parsed by gateway server messenger 212 to obtain registration information, i.e whether the command was solicited or unsolicited, the corresponding command type and operation result. At box 342 the question is asked as to whether the registration was solicited, and if so then at box 344 the question is asked whether the corresponding MIN that solicited the registration is located in transaction hash table 188. If so, then at box 346 “TRANSACTION SUCCESSFUL” is reported to web server 170 via a calling function in event generator 206. At box 348 the registration information, i.e. time that the registration was received, status, ESN result, exception, etc., is saved to the transaction table in database 204, and at box 350 the MIN number that solicited the registration is deleted from hash table 188 and the program falls through to inquiry box 352. At box 352 the question is posed as to whether the registration was solicited or unsolicited, i.e. response to “get status”, and if the registration was unsolicited then the logic falls through to box 354 (
At box 356, the ESN value of the registration is compared, bit by bit, with the ESN value retrieved from database 204. If there is a bit change then at box 358 an alarm is generated and sent to web server 170 to be displayed, as by providing an alarm indication in field 476 of
At box 360 the new status value is saved in database 204. Where the answer at box 352 is no, then the program exits and runs again.
c illustrates the process of gateway server messenger 212, which also runs in an endless loop. As stated, this component receives messages from gateway server 196 (
d depicts a flowchart relating to insertion of event messages into event queue 202. Again, this logic runs in an endless loop, and occurs when registration handler 192 generates an alarm, event or transaction message. The logic may also be called by page issuer 190, diagnosis engine 210, health center 208, or MIN register 228 whenever these components detect an error. As shown, at box 378 transaction information for the next transaction to be performed is obtained from hash table 188. Where there are a number of transactions to be acted upon, the next action may be selected using the priority scheme as described. At box 380 an inquiry is made as to whether the transaction has timed out, such as when the two minute delay has expired after a page is issued. If the transaction has not timed out in the logic flow loops back to box 378 to obtain the next transaction from hash table 188. Where the transaction has timed out, then at box 382 the question is asked as to whether the maximum number of retries for the transaction has occurred, as where an attempt to send a page to gateway server 196 has been retried twice. If the maximum number of retries has occurred, then at box 384 the transaction is deleted from hash table 188 and the logic falls through to box 386 where the inquiry is made as to whether or not the transaction was issued. If the transaction issued, then at box 388 a report “transaction timeout” is sent to web server 170 (
e illustrates logic for a functional interface for the remote module server 172 to send pages and receive registrations to and from gateway server 196. Here, at box 400, a message length is calculated according to the message type, i.e. as different type messages may have different length, the length of the message is calculated and memory for the message allocated accordingly. At box 402 the gateway server request message is assembled in the allocated memory, and includes message length, message type, priority, sequential, SID and SYSNO field. Here, with respect to respective positions in fields of the message, priority=1 may represent a high priority level, while priority=0 may represents a low priority level. “Sequential” indicates whether the pages in a transaction are to be issued in sequence or not. Sequential=true may require the gateway server to keep the sequence of the pages in the MIN transaction of in order, while “sequential=false” does not. SID is the mobile switching center system identification number, and is used by the gateway server to construct and route outgoing packets. Thus, all pages in the MIN set for an area served by a common mobile switching center share the same SID. SYSNO defines the mobile switching center switch number, i.e. which service provider, and is also used by the gateway server to construct and route outgoing packets. All pages in the MIN set share the same SYSNO. At box 404 the command MIN and RM MIN/MINSET are converted to binary coded decimal format and at box 406 the query is made as to whether or not to send the page or transaction to the gateway server socket. If the answer is fail, then an exception is developed at box 408 and a corresponding message displayed in the SYSTEMS EXCEPTIONS REPORT field 478 of the screen of
If the answer at box 406 is success, the page is sent to gateway server 196 and the program loops back to the beginning and runs in an endless loop.
f shows logic flow that develops error codes when one or more of a plurality of errors occur. These errors may include gateway internal errors such as buffer overflow, authentication failure, and others related to the gateway server. Other failures that develop error codes are a general modem error, sequence rejected due to an invalid MIN number, an invalid meter ID, an invalid meter number, a bad sequence, an excessive number of dial retries, an excessive number of modem retries, a connection failure, no TLDN allocated (no available modem) and an IS page failure. In the flowchart of
g is a flowchart representative of logic flow of remote object calling for web server 170 to register or unregister a single or a batch of MINs in the gateway server. Accordingly, at box 420 all the remote MINs, in BCD format, that belong to the service, such as the automatic meter reading system, are retrieved from database 204 and buffered in MIN register 228. At box 422 the MIN numbers are sent to gateway server 196 through gateway server communicator 194. To remove the MIN numbers from the gateway server, the same path is used as when a new MIN number is registered. At box 424 a wait period is initiated in order to receive a signal by gateway server messenger 212, such signal indicating that the gateway server register MIN ack signal was received. When this signal is received, at box 426 the message “register RM MINS successfully” is returned, meaning that the MIN numbers were successfully registered in gateway server 196. If the ack message is not received then the logic falls through to box 428 where a retry occurs, this retry looping back to box 422. After three retries, the logic falls through from box 428 to box 430 where the error message “register RM mins fail” is stored in an exception log table, and at box 432 “register RM mins fail” is returned and displayed in field 478 of the screen of
As stated, my system may be easily adapted to multiple applications in addition to automated meter reading systems simply by connecting my circuit board 38 including a CELLEMETRY™ radio, microprocessor 50 with appropriate software configuration, and in some instances a GPS receiver, to a sensor or switch. Some of such applications include automatic surveillance systems of all types where an individual is not actually watching a monitored area, personal security and location devices, control and monitoring of systems such as capacitor banks for power factor balancing, quickly determining areas affected by electrical power outages and others, as should be apparent to one skilled in the arts from my disclosure.
While CELLEMETRY™ is disclosed herein as being a preferred way of communicating between meters and other devices, and a data center via the Internet, other wireless forms of transmission are workable. For instance, other systems of voice and/or data communications channels may be used, such as cellular digital packet data (CDPD), code division multiple access (CDMA) and time division/domain multiple access (TDMA), which use packetized systems for data communications. In addition, another data transmission system similar to CELLEMETRY™ is used by AERIS™, and which also may be used in Applicant's system. Further, satellite communications systems are available for use in Applicant's system, such as ORBSCOM® and the global system for mobile communications (GSM). In these systems, the appropriate communications radio would substitute for the CELLEMETRY™ radio.
A series of screen images (screen shots) will now be described that generally illustrate by way of example operation of a user interface of Applicant's invention. These screens should be taken by way of example only, it being understood that a skilled programmer would know how various sequences of screens would be arranged and what fields should be included in each screen from the foregoing disclosure. Further, it should be understood that for each of the products, i.e a snow melter system, an automated meter reading system, a surveillance system, etc, the arrangements of icons and fields within screens for different products are generally very similar. For instance, a STATUS page would be similar for all the products, with fields similarly labeled, and wherever possible labeled similarly or identically, with these similar or identical fields being to the extent possible in the same locations on the screen between screens for different products.
In general, a customer user selects a product associated with that company by selecting with a pointing device the appropriate radio button. Here, the radio buttons AMR-G, AMR-W and AMR-E refer to automatic gas, water and electric meter reading systems, respectively, while “melter” refers to a snow melter system as disclosed in Applicant's copending patent application Ser. No. 10/613,430, filed Jul. 3, 2003. CCU refers to the capacitor coupling application, and RECLOSER refers to the electrical reclosing system described above. It is to be noted that the products are not necessarily related to a particular utility or customer user, rather, several customer companies may use the automatic meter reading products, surveillance products and/or other products. With respect to other of Applicant's products, CIDS refers to a surveillance system product and GPS refers to a system wherein mobile assets outfitted with GPS units may be accessed, after which particular mobile units may be located and status parameters obtained.
The highest level users, designated for this application as system operators, administrators and users, manage the highest level of software and database operations, and add and delete customer administrators and users. In addition, other system maintenance personnel maintain computers, computer servers and networks associated with the system, in addition to monitoring the network associated with the CELLEMETRY™ gateway.
Lower level customer users may be utility companies, railroad companies and the like. For example, a system administrator or other system operator may add or delete customers such as water, electric and gas utility companies, railroad companies, etc. In general, it is contemplated that that the software and computer system be located at and operated from a central location, although in some instances a diversified system may easily be implemented, for example to implement redundancy, efficiency, to have a de-centralized system less vulnerable to terrorist or “software hack” attacks, or any combination of these and other factors.
Initially, a system user, who as stated may be a system administrator or the like, may access the system from a general purpose computer having loaded therein any conventional browser such as Internet Explorer™, Netscape™, Mozilla™ or other Internet browsers. Here, the URL for the system is entered into the browser (or a shortcut selected), and the system user is presented with a login screen that may be configured as shown in
As seen at the left of the screen of
With respect to a system user, to add, delete or modify customer configurations, on screen 13 the system user selects ADMINISTRATION, CUSTOMERS, after which the screen of
In general, system users add new customers and provide logistics and maintenance support for the system. Customer users may be given privileges so they may add or delete their own administrative customer users and other customer users, in addition to adding information to newly installed remote unit devices and new models of remote units. Thus, both system users and customer users may have access to screens under the selection of ADMINISTRATION, USERS, which brings up the screen of
When ADD NEW MODEL is selected, the screen of
Where a device is to be deleted, the DELETE selection for that device is selected in field 458 of the screen of
When a user selects CONFIGURATION, GROUPS of the screen of
Editing of the groups is accomplished by selecting EDIT for a particular group shown in field 460 of
Where a group is to be deleted, the DELETE selection in field 460 of the screen of
Where particular remote units in a group are to be configured or reconfigured, such as remote units that control switching of capacitor banks in a particular group of capacitor banks, a user selects CONFIGURATION, GROUPS, UNITS to bring up the screen of
In this screen, a user may add a new capability or change configuration of a remote unit. This screen is used, for instance, where a different or updated remote unit is installed as a replacement for an older remote unit. In addition, capabilities of remote units may be changed, as where an electrical connect/disconnect device is added to an existing meter reading remote unit to provide remote connect/disconnect capability to the existing remote meter reading capability. Where a new remote unit for capacitor control, or as stated any other remote unit, is to be added, the field ADD NEW CAPACITOR (or any other device) is selected to bring up the screen of
Where EDIT is selected for a particular device in field 462 of
For entering a market configuration, for example a market configuration for capacitors, CONFIGURATION, CAPACITORS, MARKETS is selected in the screen of
For monitoring operation of remote units, OPERATION, MONITOR of the screen of
The device status screen of
When OPERATION, ALARMS of the screen of
New incoming alarms are displayed in fields labeled EVENT CODE, which indicates severity of the alarm, and a RM MIN field indicating the remote unit MIN number that generated the alarm. After being acknowledged, as by selecting the ACKNOWLEDGE box, the respective alarm indication ACK box in field 476 for the alarm is either grayed out or a check is placed in the box. Where a plurality of alarms arrive simultaneously or too fast for a user to acknowledge them, they simply are placed in order in field 476 with the ACK box blank until a user has an opportunity to act on them. In some instances, as with alarms above a selected severity, the software may be configured so that the user may not place a check in an alarm box until the alarm is opened from within field 476. In the event that a user, such as a customer user, wishes to view system exceptions, then SYSTEM, EXCEPTIONS of the screen of
For viewing command configuration, SYSTEM, COMMANDS of the screen of
Where an existing command is to be edited, then EDIT is selected for a particular command within field 482 of the screen of
To delete a command, then in field 482 of
Having thus described my invention and the manner of its use, it should be apparent to those skilled in the arts that incidental modifications may be made thereto that fairly fall within the scope of the following appended claims,
This application is a continuation-in-part of Applicant's patent application Ser. No. 10/613,430, filed Jul. 3, 2003 now U.S. Pat. No. 6,995,666, which claims the benefit of provisional application No. 60/418,922, filed 10/16/2002.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4638314 | Keller | Jan 1987 | A |
| 4977482 | Langdon et al. | Dec 1990 | A |
| 5767790 | Jovellana | Jun 1998 | A |
| 5873043 | Comer et al. | Feb 1999 | A |
| 6014089 | Tracy et al. | Jan 2000 | A |
| 6072874 | Shin et al. | Jun 2000 | A |
| 6078785 | Bush | Jun 2000 | A |
| 6108537 | Comer et al. | Aug 2000 | A |
| 6178337 | Spartz et al. | Jan 2001 | B1 |
| 6393297 | Song | May 2002 | B1 |
| 6538577 | Ehrke et al. | Mar 2003 | B1 |
| 6571093 | Jarrett, Jr. | May 2003 | B1 |
| 6681110 | Crookham et al. | Jan 2004 | B1 |
| 6718177 | Comer et al. | Apr 2004 | B1 |
| 6734663 | Fye et al. | May 2004 | B2 |
| 7091878 | Holle et al. | Aug 2006 | B2 |
| 20030167178 | Jarman et al. | Sep 2003 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 60418922 | Oct 2002 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10613430 | Jul 2003 | US |
| Child | 10882931 | US |
