Patent Grant
8203463
Automated systems exist for collecting data from meters that measure usage of resources, such as gas, water and electricity. Such systems may employ a number of different infrastructures for collecting this meter data from the meters. For example, some automated systems obtain data from the meters using a fixed wireless network that includes, for example, a central node in communication with a number of endpoint nodes (e.g., meter reading devices (MRDs) connected to meters). At the endpoint nodes, the wireless communications circuitry may be incorporated into the meters themselves, such that each endpoint node in the wireless network comprises a meter connected to an MRD that has wireless communication circuitry that enables the MRD to transmit the meter data of the meter to which it is connected. The endpoint nodes may either transmit their meter data directly to the central node, or indirectly though one or more intermediate bi-directional nodes which serve as repeaters for the meter data of the transmitting node. Some networks operating in this manner are referred to as “mesh” networks.
Although the fixed wireless network infrastructure is an efficient infrastructure for collecting data from MRDs, there are a number of scenarios in which a fixed wireless network may, at least temporarily, not be an optimal infrastructure for collecting data from at least some of the MRDs in a particular metering system. In particular, for an operator of a metering system, setting up, expanding, and/or maintaining a large fixed wireless network may require a significant investment of financial capital. Additionally, setting up or expanding a large fixed wireless network may require time to plan the location of each node in the network, time to build up and/or access each location, and time to actually install the necessary wireless communications equipment at each location. Thus, for example, in some scenarios, a metering system operator may simply not yet have enough financial capital or the necessary time to build a new wireless network or expand an existing wireless network to include certain MRDs within the system. This is especially true for outlying MRDs that are located along the geographic boundaries of the system or in sparsely populated or sparsely developed areas. These MRDs may be located too far away to transmit their metering data to any of the existing repeater nodes in an existing fixed wireless network. Thus, it may be advantageous to defer building or expanding a wireless network to include these outlying MRDs until the outlying locations become more populated or developed or until the costs associated with building or expanding the wireless network can be otherwise incurred.
In these and other scenarios, until the fixed wireless network is built or expanded to include these MRDs, other network infrastructures may be at least temporarily employed to collect the meter data from the MRDs. One such other network infrastructure, which will hereinafter be referred to as the “mobile data collection” infrastructure, involves the use of a mobile data collection device, or interrogator, that can be transported to the site of each MRD to collect the meter data from each MRD. The mobile infrastructure may employ data collection techniques that are commonly referred to as “walk by” or “drive by.” The “walk by” techniques may involve the use of a smaller size mobile data collection device which can be transported by one or more people on foot. The “drive by” techniques may involve the use of a somewhat larger mobile data collection device that is transported by a vehicle such as a van or small truck. The “walk by” techniques are thus more suitable for MRDs that are dispersed throughout smaller areas or areas that cannot be accessed using a vehicle. The “drive by” techniques are thus more suitable for MRDs that are dispersed throughout larger areas that are vehicle accessible.
In order to enable MRDs in mobile data collection networks to send out a higher powered transmission signal while still conserving the long term power supply of the meters, some conventional mobile data collection networks have employed a sleep/wake cycle to regulate transmission of meter data from the MRDs. The idea behind the sleep/wake cycle is that it is only necessary for an MRD to transmit its meter data while the mobile data collection device is within the transmission range of the MRD. Thus, the mobile data collection device will transmit a “wake signal” to notify a particular MRD that the mobile data collection device is approaching the physical proximity of the MRD. Accordingly, the MRD will typically begin its operation in the low power sleep mode in which it does not transmit meter data. Then, when the mobile data collection device approaches the MRD, the MRD will receive the wake signal from the mobile device. The wake signal will cause the MRD to “wake up” and transition into a higher power wake mode in which it transmits its meter data to the mobile device. Then, after transmitting its meter data, the MRD will transition back into the sleep mode, thereby once again conserving its power supply.
In some conventional mobile data collection networks that employ sleep/wake cycles as described above, the mobile data collection device transmits the wake signal to the MRD using an unlicensed frequency band, such as an Industrial, Scientific, and Medical (ISM) band. Examples of ISM bands include frequency bands having respective center frequencies of 915 MHz and 2.4 GHz. Using unlicensed frequency bands affords certain advantages for battery-powered MRDs. For instance, unlicensed frequency bands generally support wide bandwidths and, therefore, high bitrates for communication of large blocks of data, as may be collected in MRDs. Further, the regulatory rules for unlicensed frequency bands are written to allow a large number of devices to coexist. This feature may be particularly advantageous in the context of networks in which many MRDs are deployed, such as, for example, networks operated by large electric, gas, or water utilities.
Although using an unlicensed frequency band to wake MRDs through carrier-sensed radio receivers results in some advantages, this technique also suffers from certain drawbacks. For example, unlicensed frequency bands are often crowded with large numbers of communication devices of many different manufacturers and types. As a result, particularly in densely populated areas, any particular channel of the unlicensed frequency band may have large amounts of traffic. This traffic can cause interference that results in false wakeups. That is, MRDs may transition to the higher power wake mode even when no mobile data collection device, or interrogator, is within range. These false wakeups may increase power consumption and adversely affect the battery life of the MRDs.
Even so-called spread spectrum devices can be affected by false wakeups. Further, spread spectrum techniques, such as direct sequence spreading or frequency hopping, add another challenge for operating battery-powered MRDs in unlicensed frequency bands. Spread spectrum techniques typically require lengthy and complex methods for the receiver in the MRD to become frequency-, time-, and/or code-synchronized with the transmitter in the interrogator. These methods put an undesirable drain on battery-powered MRDs, especially if the process has to be repeated due to false wakeups.
Thus, there is a need in the art for a meter data collection system in which false wakeups and interrogator-MRD synchronization time are reduced while maintaining communication throughput.
A meter data collection system in which a licensed narrowband frequency channel is used to wake up carrier-sensed, battery-powered meter reading devices (MRDs) is disclosed herein. In the meter data collection system disclosed herein, an unlicensed wideband channel is used to transmit data replies from the MRDs to a mobile data collection device. In another embodiment disclosed herein, a meshed network of MRDs communicating on the unlicensed channel is combined with a roaming interrogator that uses the licensed channel to send commands or to perform on-demand reads.
In one embodiment, a meter reading device includes a transceiver configured and arranged to transmit and receive radio signals. A processor is in electrical communication with the transceiver and is configured and arranged to execute processor-executable instructions to control operation of the meter reading device. A memory is in electrical communication with the processor and storing processor-executable instructions. When the instructions are executed by the processor, the instructions cause the processor to control the operation of the meter reading device to operate in one of four selected modes: (1) sleep mode, in which the transceiver periodically listens on a licensed channel for a carrier signal; (2) rouse mode in which the transceiver receives data via the licensed channel; (3) wake mode in which the meter reading device processes the data received via the licensed channel in the rouse mode, and (4) reply mode in which the transceiver transmits a reply on an unlicensed channel having a broader bandwidth than the licensed channel. The selected mode in which the meter reading device operates is reconfigurable.
Another embodiment is directed to a method of operating an interrogator device comprising a transceiver. The transceiver is caused to emit a carrier signal (with or without a preamble pattern modulated on the carrier) on a licensed channel. The carrier signal causes a meter reading device to transition from a sleep mode to a rouse mode. Data is transmitted from the interrogator device to the meter reading device using the licensed channel. The data comprises a preamble, an address of the meter reading device, a command, and a plurality of checksum bits. A reply is received from the meter reading device on an unlicensed channel having a broader bandwidth and therefore higher bitrate than the licensed channel, allowing a large amount of collected data in the MRD to be returned in a short time.
According to yet another embodiment, a method of operating a meter reading device comprising a transceiver is disclosed. The method comprises operating the meter reading device in a sleep mode in which the transceiver periodically listens on a licensed channel for a carrier signal from an interrogator. When a carrier signal is received from the interrogator, the meter reading device is commanded by its internal processor to transition to operation in a rouse mode in which the transceiver receives data from the interrogator via the licensed channel. If it is determined that the data received from the interrogator is addressed to the meter reading device, the meter reading device transitions to operation in a wake mode in which the meter reading device processes the data received from the interrogator via the licensed channel. If it is determined that the data received from the interrogator requires a reply, the meter reading device transitions to operation in a reply mode in which the meter reading device transmits the reply to the interrogator using an unlicensed channel having a broader bandwidth than the licensed channel. After the transmission of the reply, the MRD may transition back to either wake mode or sleep mode, according to the command received and/or the MRD configuration stored in its memory.
Various embodiments may realize certain advantages. For example, the licensed channel used for waking up MRDs typically has much lower levels of traffic than the unlicensed channel used in some conventional mobile data collection networks. As a result, false wakeups that are attributable to interference are reduced. The time involved in synchronizing the interrogator with the MRDs is also reduced. At the same time, because the unlicensed channel that is used for transmitting replies from the MRDs to the interrogator has a wider bandwidth than the licensed channel, communication throughput is high.
Other features and advantages of the invention may become apparent from the following detailed description and accompanying drawings.
The foregoing summary, as well as the following detailed description of various embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there are shown in the drawings exemplary embodiments of various aspects of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:
Exemplary systems and methods for gathering meter data are described below with reference to
Generally, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water, and gas, are operable to wirelessly communicate. One or more devices, referred to herein as “collectors,” are provided that “collect” data transmitted by the other meter devices so that it can be accessed by other computer systems, such as a metering automation server (MAS). The collectors receive and compile metering data from a plurality of meter devices via wireless communications. A metering automation server may communicate with the collectors to retrieve the compiled meter data, and communicate with computer systems that prepare customer billing.
System 110 further comprises collectors 116. In one embodiment, collectors 116 are also meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. In another embodiment, collectors 116 may be standalone communication nodes, without the capability of metering of service or commodity. In addition, collectors 116 are operable to send data to and receive data from meters 114. Thus, like the meters 114, the collectors 116 may comprise both circuitry for measuring the consumption of a service or commodity and for generating data reflecting the consumption and circuitry for transmitting and receiving data. In one embodiment, collector 116 and meters 114 communicate with and amongst one another using any one of several wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS).
A collector 116 and the meters 114 with which it communicates define a subnet/LAN 120 of system 110. As used herein, meters 114 and collectors 116 may be referred to as “nodes” in the subnet 120. In each subnet/LAN 120, each meter transmits data related to consumption of the commodity being metered at the meter's location. The collector 116 receives the data transmitted by each meter 114, effectively “collecting” it, and then periodically transmits the data from all of the meters in the subnet/LAN 120 to a metering automation server 206. The metering automation server 206 stores the data for analysis and preparation of bills, for example. The metering automation server 206 may be a specially programmed general purpose computing system and may communicate with collectors 116 via a network 112. The network 112 may comprise any form of network, including a wireless network or a fixed-wire network, such as a local area network (LAN), a wide area network, the Internet, an intranet, a telephone network, such as the public switched telephone network (PSTN), a public wireless (cellular) network, a Frequency Hopping Spread Spectrum (FHSS) radio network, a mesh network, a Wi-Fi (802.11) network, a Wi-Max (802.16) network, a land line (POTS) network, or any combination of the above.
Referring now to
Each of the meters 114 and collectors 116 is assigned an identifier (LAN ID) that uniquely identifies that meter or collector on its subnet/LAN 120. In this embodiment, communication between nodes (i.e., the collectors and meters) and the system 110 is accomplished using the LAN ID. However, it is preferable for operators of a utility to query and communicate with the nodes using their own identifiers. To this end, a marriage file 208 may be used to correlate a utility's identifier for a node (e.g., a utility serial number) with both a manufacturer serial number (i.e., a serial number assigned by the manufacturer of the meter) and the LAN ID for each node in the subnet/LAN 120. In this manner, the utility can refer to the meters and collectors by the utilities identifier, while the system can employ the LAN ID for the purpose of designating particular meters during system communications.
A device configuration database 210 stores configuration information regarding the nodes. For example, in the metering system 200, the device configuration database may include data regarding time of use (TOU) switchpoints, etc. for the meters 114 and collectors 116 communicating in the system 110. A data collection requirements database 212 contains information regarding the data to be collected on a per node basis. For example, a utility may specify that metering data such as load profile, demand, TOU, etc. is to be collected from particular meter(s) 114a. Reports 214 containing information on the network configuration may be automatically generated or in accordance with a utility request.
The network management system (NMS) 204 maintains a database describing the current state of the global fixed network system (current network state 220) and a database describing the historical state of the system (historical network state 222). The current network state 220 contains data regarding current meter-to-collector assignments, etc. for each subnet/LAN 120. The historical network state 222 is a database from which the state of the network at a particular point in the past can be reconstructed. The NMS 204 is responsible for, amongst other things, providing reports 214 about the state of the network. The NMS 204 may be accessed via an API 220 that is exposed to a user interface 216 and a Customer Information System (CIS) 218. Other external interfaces may also be implemented. In addition, the data collection requirements stored in the database 212 may be set via the user interface 216 or CIS 218.
The metering automation server 206 collects data from the nodes (e.g., collectors 116) and stores the data in a database 224. The data includes metering information, such as energy consumption and may be used for billing purposes, etc. by a utility provider.
The network management server 202, network management system 204 and metering automation server 206 communicate with the nodes in each subnet/LAN 120 via network 110.
As shown in
In one embodiment, the metering circuitry 304, processor 305, display 310 and memory 312 are implemented using an A3 ALPHA meter available from Elster Electricity, Inc. In that embodiment, the wireless LAN communications circuitry 306 may be implemented by a LAN Option Board (e.g., a 900 MHz two-way radio) installed within the A3 ALPHA meter, and the network interface 308 may be implemented by a WAN Option Board (e.g., a telephone modem) also installed within the A3 ALPHA meter. In this embodiment, the WAN Option Board 308 routes messages from network 112 (via interface port 302) to either the meter processor 305 or the LAN Option Board 306. LAN Option Board 306 may use a transceiver (not shown), for example a 900 MHz radio, to communicate data to meters 114. Also, LAN Option Board 306 may have sufficient memory to store data received from meters 114. This data may include, but is not limited to the following: current billing data (e.g., the present values stored and displayed by meters 114), previous billing period data, previous season data, and load profile data.
LAN Option Board 306 may be capable of synchronizing its time to a real time clock (not shown) in A3 ALPHA meter, thereby synchronizing the LAN reference time to the time in the meter. The processing necessary to carry out the communication functionality and the collection and storage of metering data of the collector 116 may be handled by the processor 305 and/or additional processors (not shown) in the LAN Option Board 306 and the WAN Option Board 308.
The responsibility of a collector 116 is wide and varied. Generally, collector 116 is responsible for managing, processing and routing data communicated between the collector and network 112 and between the collector and meters 114. Collector 116 may continually or intermittently read the current data from meters 114 and store the data in a database (not shown) in collector 116. Such current data may include but is not limited to the total kWh usage, the Time-Of-Use (TOU) kWh usage, peak kW demand, and other energy consumption measurements and status information. Collector 116 also may read and store previous billing and previous season data from meters 114 and store the data in the database in collector 116. The database may be implemented as one or more tables of data within the collector 116.
Referring again to
Each level one meter 114a typically will only be in range to directly communicate with only a subset of the remaining meters 114 in the subnet 120. The meters 114 with which the level one meters 114a directly communicate may be referred to as level two meters 114b. Level two meters 114b are one “hop” from level one meters 114a, and therefore two “hops” from collector 116. Level two meters 114b operate as repeaters for communications between the level one meters 114a and meters 114 located further away from collector 116 in the subnet 120.
While only three levels of meters are shown (collector 116, first level 114a, second level 114b) in
As mentioned above, each meter 114 and collector 116 that is installed in the system 110 has a unique identifier (LAN ID) stored thereon that uniquely identifies the device from all other devices in the system 110. Additionally, meters 114 operating in a subnet 120 comprise information including the following: data identifying the collector with which the meter is registered; the level in the subnet at which the meter is located; the repeater meter at the prior level with which the meter communicates to send and receive data to/from the collector; an identifier indicating whether the meter is a repeater for other nodes in the subnet; and if the meter operates as a repeater, the identifier that uniquely identifies the repeater within the particular subnet, and the number of meters for which it is a repeater. Collectors 116 have stored thereon all of this same data for all meters 114 that are registered therewith. Thus, collector 116 comprises data identifying all nodes registered therewith as well as data identifying the registered path by which data is communicated from the collector to each node. Each meter 114 therefore has a designated communications path to the collector that is either a direct path (e.g., all level one nodes) or an indirect path through one or more intermediate nodes that serve as repeaters.
Information is transmitted in this embodiment in the form of packets. For most network tasks such as, for example, reading meter data, collector 116 communicates with meters 114 in the subnet 120 using point-to-point transmissions. For example, a message or instruction from collector 116 is routed through the designated set of repeaters to the desired meter 114. Similarly, a meter 114 communicates with collector 116 through the same set of repeaters, but in reverse.
In some instances, however, collector 116 may need to quickly communicate information to all meters 114 located in its subnet 120. Accordingly, collector 116 may issue a broadcast message that is meant to reach all nodes in the subnet 120. The broadcast message may be referred to as a “flood broadcast message.” A flood broadcast originates at collector 116 and propagates through the entire subnet 120 one level at a time. For example, collector 116 may transmit a flood broadcast to all first level meters 114a. The first level meters 114a that receive the message pick a random time slot and retransmit the broadcast message to second level meters 114b. Any second level meter 114b can accept the broadcast, thereby providing better coverage from the collector out to the end point meters. Similarly, the second level meters 114b that receive the broadcast message pick a random time slot and communicate the broadcast message to third level meters. This process continues out until the end nodes of the subnet. Thus, a broadcast message gradually propagates outward from the collector to the nodes of the subnet 120.
The flood broadcast packet header contains information to prevent nodes from repeating the flood broadcast packet more than once per level. For example, within a flood broadcast message, a field might exist that indicates to meters/nodes which receive the message, the level of the subnet the message is located; only nodes at that particular level may re-broadcast the message to the next level. If the collector broadcasts a flood message with a level of 1, only level 1 nodes may respond. Prior to re-broadcasting the flood message, the level 1 nodes increment the field to 2 so that only level 2 nodes respond to the broadcast. Information within the flood broadcast packet header ensures that a flood broadcast will eventually die out.
Generally, a collector 116 issues a flood broadcast several times, e.g. five times, successively to increase the probability that all meters in the subnet 120 receive the broadcast. A delay is introduced before each new broadcast to allow the previous broadcast packet time to propagate through all levels of the subnet.
Meters 114 may have a clock formed therein. However, meters 114 often undergo power interruptions that can interfere with the operation of any clock therein. Accordingly, the clocks internal to meters 114 cannot be relied upon to provide an accurate time reading. Having the correct time is necessary, however, when time of use metering is being employed. Indeed, in an embodiment, time of use schedule data may also be comprised in the same broadcast message as the time. Accordingly, collector 116 periodically flood broadcasts the real time to meters 114 in subnet 120. Meters 114 use the time broadcasts to stay synchronized with the rest of the subnet 120. In an illustrative embodiment, collector 116 broadcasts the time every 15 minutes. The broadcasts may be made near the middle of 15 minute clock boundaries that are used in performing load profiling and time of use (TOU) schedules so as to minimize time changes near these boundaries. Maintaining time synchronization is important to the proper operation of the subnet 120. Accordingly, lower priority tasks performed by collector 116 may be delayed while the time broadcasts are performed.
In an illustrative embodiment, the flood broadcasts transmitting time data may be repeated, for example, five times, so as to increase the probability that all nodes receive the time. Furthermore, where time of use schedule data is communicated in the same transmission as the timing data, the subsequent time transmissions allow a different piece of the time of use schedule to be transmitted to the nodes.
Exception messages are used in subnet 120 to transmit unexpected events that occur at meters 114 to collector 116. In an embodiment, the first 4 seconds of every 32-second period are allocated as an exception window for meters 114 to transmit exception messages. Meters 114 transmit their exception messages early enough in the exception window so the message has time to propagate to collector 116 before the end of the exception window. Collector 116 may process the exceptions after the 4-second exception window. Generally, a collector 116 acknowledges exception messages, and collector 116 waits until the end of the exception window to send this acknowledgement.
In an illustrative embodiment, exception messages are configured as one of three different types of exception messages: local exceptions, which are handled directly by the collector 116 without intervention from metering automation server 206; an immediate exception, which is generally relayed to metering automation server 206 under an expedited schedule; and a daily exception, which is communicated to the communication server 122 on a regular schedule.
Exceptions are processed as follows. When an exception is received at collector 116, the collector 116 identifies the type of exception that has been received. If a local exception has been received, collector 116 takes an action to remedy the problem. For example, when collector 116 receives an exception requesting a “node scan request” such as discussed below, collector 116 transmits a command to initiate a scan procedure to the meter 114 from which the exception was received.
If an immediate exception type has been received, collector 116 makes a record of the exception. An immediate exception might identify, for example, that there has been a power outage. Collector 116 may log the receipt of the exception in one or more tables or files. In an illustrative example, a record of receipt of an immediate exception is made in a table referred to as the “Immediate Exception Log Table.” Collector 116 then waits a set period of time before taking further action with respect to the immediate exception. For example, collector 116 may wait 64 seconds. This delay period allows the exception to be corrected before communicating the exception to the metering automation server 206. For example, where a power outage was the cause of the immediate exception, collector 116 may wait a set period of time to allow for receipt of a message indicating the power outage has been corrected.
If the exception has not been corrected, collector 116 communicates the immediate exception to metering automation server 206. For example, collector 116 may initiate a dial-up connection with metering automation server 206 and download the exception data. After reporting an immediate exception to metering automation server 206, collector 116 may delay reporting any additional immediate exceptions for a period of time such as ten minutes. This is to avoid reporting exceptions from other meters 114 that relate to, or have the same cause as, the exception that was just reported.
If a daily exception was received, the exception is recorded in a file or a database table. Generally, daily exceptions are occurrences in the subnet 120 that need to be reported to metering automation server 206, but are not so urgent that they need to be communicated immediately. For example, when collector 116 registers a new meter 114 in subnet 120, collector 116 records a daily exception identifying that the registration has taken place. In an illustrative embodiment, the exception is recorded in a database table referred to as the “Daily Exception Log Table.” Collector 116 communicates the daily exceptions to metering automation server 206. Generally, collector 116 communicates the daily exceptions once every 24 hours.
In the present embodiment, a collector assigns designated communications paths to meters with bi-directional communication capability, and may change the communication paths for previously registered meters if conditions warrant. For example, when a collector 116 is initially brought into system 110, it needs to identify and register meters in its subnet 120. A “node scan” refers to a process of communication between a collector 116 and meters 114 whereby the collector may identify and register new nodes in a subnet 120 and allow previously registered nodes to switch paths. A collector 116 can implement a node scan on the entire subnet, referred to as a “full node scan,” or a node scan can be performed on specially identified nodes, referred to as a “node scan retry.”
A full node scan may be performed, for example, when a collector is first installed. The collector 116 must identify and register nodes from which it will collect usage data. The collector 116 initiates a node scan by broadcasting a request, which may be referred to as a Node Scan Procedure request. Generally, the Node Scan Procedure request directs that all unregistered meters 114 or nodes that receive the request respond to the collector 116. The request may comprise information such as the unique address of the collector that initiated the procedure. The signal by which collector 116 transmits this request may have limited strength and therefore is detected only at meters 114 that are in proximity of collector 116. Meters 114 that receive the Node Scan Procedure request respond by transmitting their unique identifier as well as other data.
For each meter from which the collector receives a response to the Node Scan Procedure request, the collector tries to qualify the communications path to that meter before registering the meter with the collector. That is, before registering a meter, the collector 116 attempts to determine whether data communications with the meter will be sufficiently reliable. In one embodiment, the collector 116 determines whether the communication path to a responding meter is sufficiently reliable by comparing a Received Signal Strength Indication (RSSI) value (i.e., a measurement of the received radio signal strength) measured with respect to the received response from the meter to a selected threshold value. For example, the threshold value may be −60 dBm. RSSI values above this threshold would be deemed sufficiently reliable. In another embodiment, qualification is performed by transmitting a predetermined number of additional packets to the meter, such as ten packets, and counting the number of acknowledgements received back from the meter. If the number of acknowledgments received is greater than or equal to a selected threshold (e.g., 8 out of 10), then the path is considered to be reliable. In other embodiments, a combination of the two qualification techniques may be employed.
If the qualification threshold is not met, the collector 116 may add an entry for the meter to a “Straggler Table.” The entry includes the meter's LAN ID, its qualification score (e.g., 5 out of 10; or its RSSI value), its level (in this case level one) and the unique ID of its parent (in this case the collector's ID).
If the qualification threshold is met or exceeded, the collector 116 registers the node. Registering a meter 114 comprises updating a list of the registered nodes at collector 116. For example, the list may be updated to identify the meter's system-wide unique identifier and the communication path to the node. Collector 116 also records the meter's level in the subnet (i.e. whether the meter is a level one node, level two node, etc.), whether the node operates as a repeater, and if so, the number of meters for which it operates as a repeater. The registration process further comprises transmitting registration information to the meter 114. For example, collector 116 forwards to meter 114 an indication that it is registered, the unique identifier of the collector with which it is registered, the level the meter exists at in the subnet, and the unique identifier of its parent meter that will server as a repeater for messages the meter may send to the collector. In the case of a level one node, the parent is the collector itself. The meter stores this data and begins to operate as part of the subnet by responding to commands from its collector 116.
Qualification and registration continues for each meter that responds to the collector's initial Node Scan Procedure request. The collector 116 may rebroadcast the Node Scan Procedure additional times so as to insure that all meters 114 that may receive the Node Scan Procedure have an opportunity for their response to be received and the meter qualified as a level one node at collector 116.
The node scan process then continues by performing a similar process as that described above at each of the now registered level one nodes. This process results in the identification and registration of level two nodes. After the level two nodes are identified, a similar node scan process is performed at the level two nodes to identify level three nodes, and so on.
Specifically, to identify and register meters that will become level two meters, for each level one meter, in succession, the collector 116 transmits a command to the level one meter, which may be referred to as an “Initiate Node Scan Procedure” command. This command instructs the level one meter to perform its own node scan process. The request comprises several data items that the receiving meter may use in completing the node scan. For example, the request may comprise the number of timeslots available for responding nodes, the unique address of the collector that initiated the request, and a measure of the reliability of the communications between the target node and the collector. As described below, the measure of reliability may be employed during a process for identifying more reliable paths for previously registered nodes.
The meter that receives the Initiate Node Scan Response request responds by performing a node scan process similar to that described above. More specifically, the meter broadcasts a request to which all unregistered nodes may respond. The request comprises the number of timeslots available for responding nodes (which is used to set the period for the node to wait for responses), the unique address of the collector that initiated the node scan procedure, a measure of the reliability of the communications between the sending node and the collector (which may be used in the process of determining whether a meter's path may be switched as described below), the level within the subnet of the node sending the request, and an RSSI threshold (which may also be used in the process of determining whether a registered meter's path may be switched). The meter issuing the node scan request then waits for and receives responses from unregistered nodes. For each response, the meter stores in memory the unique identifier of the responding meter. This information is then transmitted to the collector.
For each unregistered meter that responded to the node scan issued by the level one meter, the collector attempts again to determine the reliability of the communication path to that meter. In one embodiment, the collector sends a “Qualify Nodes Procedure” command to the level one node which instructs the level one node to transmit a predetermined number of additional packets to the potential level two node and to record the number of acknowledgements received back from the potential level two node. This qualification score (e.g., 8 out of 10) is then transmitted back to the collector, which again compares the score to a qualification threshold. In other embodiments, other measures of the communications reliability may be provided, such as an RSSI value.
If the qualification threshold is not met, then the collector adds an entry for the node in the Straggler Table, as discussed above. However, if there already is an entry in the Straggler Table for the node, the collector will update that entry only if the qualification score for this node scan procedure is better than the recorded qualification score from the prior node scan that resulted in an entry for the node.
If the qualification threshold is met or exceeded, the collector 116 registers the node. Again, registering a meter 114 at level two comprises updating a list of the registered nodes at collector 116. For example, the list may be updated to identify the meter's unique identifier and the level of the meter in the subnet. Additionally, the collector's 116 registration information is updated to reflect that the meter 114 from which the scan process was initiated is identified as a repeater (or parent) for the newly registered node. The registration process further comprises transmitting information to the newly registered meter as well as the meter that will serve as a repeater for the newly added node. For example, the node that issued the node scan response request is updated to identify that it operates as a repeater and, if it was previously registered as a repeater, increments a data item identifying the number of nodes for which it serves as a repeater. Thereafter, collector 116 forwards to the newly registered meter an indication that it is registered, an identification of the collector 116 with which it is registered, the level the meter exists at in the subnet, and the unique identifier of the node that will serve as its parent, or repeater, when it communicates with the collector 116.
The collector then performs the same qualification procedure for each other potential level two node that responded to the level one node's node scan request. Once that process is completed for the first level one node, the collector initiates the same procedure at each other level one node until the process of qualifying and registering level two nodes has been completed at each level one node. Once the node scan procedure has been performed by each level one node, resulting in a number of level two nodes being registered with the collector, the collector will then send the Initiate Node Scan Response command to each level two node, in turn. Each level two node will then perform the same node scan procedure as performed by the level one nodes, potentially resulting in the registration of a number of level three nodes. The process is then performed at each successive node, until a maximum number of levels is reached (e.g., seven levels) or no unregistered nodes are left in the subnet.
It will be appreciated that in the present embodiment, during the qualification process for a given node at a given level, the collector qualifies the last “hop” only. For example, if an unregistered node responds to a node scan request from a level four node, and therefore, becomes a potential level five node, the qualification score for that node is based on the reliability of communications between the level four node and the potential level five node (i.e., packets transmitted by the level four node versus acknowledgments received from the potential level five node), not based on any measure of the reliability of the communications over the full path from the collector to the potential level five node. In other embodiments, of course, the qualification score could be based on the full communication path.
At some point, each meter will have an established communication path to the collector which will be either a direct path (i.e., level one nodes) or an indirect path through one or more intermediate nodes that serve as repeaters. If during operation of the network, a meter registered in this manner fails to perform adequately, it may be assigned a different path or possibly to a different collector as described below.
As previously mentioned, a full node scan may be performed when a collector 116 is first introduced to a network. At the conclusion of the full node scan, a collector 116 will have registered a set of meters 114 with which it communicates and reads metering data. Full node scans might be periodically performed by an installed collector to identify new meters 114 that have been brought on-line since the last node scan and to allow registered meters to switch to a different path.
In addition to the full node scan, collector 116 may also perform a process of scanning specific meters 114 in the subnet 120, which is referred to as a “node scan retry.” For example, collector 116 may issue a specific request to a meter 114 to perform a node scan outside of a full node scan when on a previous attempt to scan the node, the collector 116 was unable to confirm that the particular meter 114 received the node scan request. Also, a collector 116 may request a node scan retry of a meter 114 when during the course of a full node scan the collector 116 was unable to read the node scan data from the meter 114. Similarly, a node scan retry will be performed when an exception procedure requesting an immediate node scan is received from a meter 114.
The system 110 also automatically reconfigures to accommodate a new meter 114 that may be added. More particularly, the system identifies that the new meter has begun operating and identifies a path to a collector 116 that will become responsible for collecting the metering data. Specifically, the new meter will broadcast an indication that it is unregistered. In one embodiment, this broadcast might be, for example, embedded in, or relayed as part of a request for an update of the real time as described above. The broadcast will be received at one of the registered meters 114 in proximity to the meter that is attempting to register. The registered meter 114 forwards the time to the meter that is attempting to register. The registered node also transmits an exception request to its collector 116 requesting that the collector 116 implement a node scan, which presumably will locate and register the new meter. The collector 116 then transmits a request that the registered node perform a node scan. The registered node will perform the node scan, during which it requests that all unregistered nodes respond. Presumably, the newly added, unregistered meter will respond to the node scan. When it does, the collector will then attempt to qualify and then register the new node in the same manner as described above.
Once a communication path between the collector and a meter is established, the meter can begin transmitting its meter data to the collector and the collector can transmit data and instructions to the meter. As mentioned above, data is transmitted in packets. “Outbound” packets are packets transmitted from the collector to a meter at a given level. In one embodiment, outbound packets contain the following fields, but other fields may also be included:
“Inbound” packets are packets transmitted from a meter at a given level to the collector. In one embodiment, inbound packets contain the following fields, but other fields may also be included:
For example, suppose a meter at level three initiates transmission of a packet destined for its collector. The level three node will insert in the RptAddr field of the inbound packet the identifier of the level two node that serves as a repeater for the level three node. The level three node will then transmit the packet. Several level two nodes may receive the packet, but only the level two node having an identifier that matches the identifier in the RptAddr field of the packet will acknowledge it. The other will discard it. When the level two node with the matching identifier receives the packet, it will replace the RptAddr field of the packet with the identifier of the level one packet that serves as a repeater for that level two packet, and the level two packet will then transmit the packet. This time, the level one node having the identifier that matches the RptAddr field will receive the packet. The level one node will insert the identifier of the collector in the RptAddr field and will transmit the packet. The collector will then receive the packet to complete the transmission.
A collector 116 periodically retrieves meter data from the meters that are registered with it. For example, meter data may be retrieved from a meter every 4 hours. Where there is a problem with reading the meter data on the regularly scheduled interval, the collector will try to read the data again before the next regularly scheduled interval. Nevertheless, there may be instances wherein the collector 116 is unable to read metering data from a particular meter 114 for a prolonged period of time. The meters 114 store an indication of when they are read by their collector 116 and keep track of the time since their data has last been collected by the collector 116. If the length of time since the last reading exceeds a defined threshold, such as for example, 18 hours, presumably a problem has arisen in the communication path between the particular meter 114 and the collector 116. Accordingly, the meter 114 changes its status to that of an unregistered meter and attempts to locate a new path to a collector 116 via the process described above for a new node. Thus, the exemplary system is operable to reconfigure itself to address inadequacies in the system.
In some instances, while a collector 116 may be able to retrieve data from a registered meter 114 occasionally, the level of success in reading the meter may be inadequate. For example, if a collector 116 attempts to read meter data from a meter 114 every 4 hours but is able to read the data, for example, only 70 percent of the time or less, it may be desirable to find a more reliable path for reading the data from that particular meter. Where the frequency of reading data from a meter 114 falls below a desired success level, the collector 116 transmits a message to the meter 114 to respond to node scans going forward. The meter 114 remains registered but will respond to node scans in the same manner as an unregistered node as described above. In other embodiments, all registered meters may be permitted to respond to node scans, but a meter will only respond to a node scan if the path to the collector through the meter that issued the node scan is shorter (i.e., less hops) than the meter's current path to the collector. A lesser number of hops is assumed to provide a more reliable communication path than a longer path. A node scan request always identifies the level of the node that transmits the request, and using that information, an already registered node that is permitted to respond to node scans can determine if a potential new path to the collector through the node that issued the node scan is shorter than the node's current path to the collector.
If an already registered meter 114 responds to a node scan procedure, the collector 116 recognizes the response as originating from a registered meter but that by re-registering the meter with the node that issued the node scan, the collector may be able to switch the meter to a new, more reliable path. The collector 116 may verify that the RSSI value of the node scan response exceeds an established threshold. If it does not, the potential new path will be rejected. However, if the RSSI threshold is met, the collector 116 will request that the node that issued the node scan perform the qualification process described above (i.e., send a predetermined number of packets to the node and count the number of acknowledgements received). If the resulting qualification score satisfies a threshold, then the collector will register the node with the new path. The registration process comprises updating the collector 116 and meter 114 with data identifying the new repeater (i.e. the node that issued the node scan) with which the updated node will now communicate. Additionally, if the repeater has not previously performed the operation of a repeater, the repeater would need to be updated to identify that it is a repeater. Likewise, the repeater with which the meter previously communicated is updated to identify that it is no longer a repeater for the particular meter 114. In other embodiments, the threshold determination with respect to the RSSI value may be omitted. In such embodiments, only the qualification of the last “hop” (i.e., sending a predetermined number of packets to the node and counting the number of acknowledgements received) will be performed to determine whether to accept or reject the new path.
In some instances, a more reliable communication path for a meter may exist through a collector other than that with which the meter is registered. A meter may automatically recognize the existence of the more reliable communication path, switch collectors, and notify the previous collector that the change has taken place. The process of switching the registration of a meter from a first collector to a second collector begins when a registered meter 114 receives a node scan request from a collector 116 other than the one with which the meter is presently registered. Typically, a registered meter 114 does not respond to node scan requests. However, if the request is likely to result in a more reliable transmission path, even a registered meter may respond. Accordingly, the meter determines if the new collector offers a potentially more reliable transmission path. For example, the meter 114 may determine if the path to the potential new collector 116 comprises fewer hops than the path to the collector with which the meter is registered. If not, the path may not be more reliable and the meter 114 will not respond to the node scan. The meter 114 might also determine if the RSSI of the node scan packet exceeds an RSSI threshold identified in the node scan information. If so, the new collector may offer a more reliable transmission path for meter data. If not, the transmission path may not be acceptable and the meter may not respond. Additionally, if the reliability of communication between the potential new collector and the repeater that would service the meter meets a threshold established when the repeater was registered with its existing collector, the communication path to the new collector may be more reliable. If the reliability does not exceed this threshold, however, the meter 114 does not respond to the node scan.
If it is determined that the path to the new collector may be better than the path to its existing collector, the meter 114 responds to the node scan. Included in the response is information regarding any nodes for which the particular meter may operate as a repeater. For example, the response might identify the number of nodes for which the meter serves as a repeater.
The collector 116 then determines if it has the capacity to service the meter and any meters for which it operates as a repeater. If not, the collector 116 does not respond to the meter that is attempting to change collectors. If, however, the collector 116 determines that it has capacity to service the meter 114, the collector 116 stores registration information about the meter 114. The collector 116 then transmits a registration command to meter 114. The meter 114 updates its registration data to identify that it is now registered with the new collector. The collector 116 then communicates instructions to the meter 114 to initiate a node scan request. Nodes that are unregistered, or that had previously used meter 114 as a repeater respond to the request to identify themselves to collector 116. The collector registers these nodes as is described above in connection with registering new meters/nodes.
Under some circumstances it may be necessary to change a collector. For example, a collector may be malfunctioning and need to be taken off-line. Accordingly, a new communication path must be provided for collecting meter data from the meters serviced by the particular collector. The process of replacing a collector is performed by broadcasting a message to unregister, usually from a replacement collector, to all of the meters that are registered with the collector that is being removed from service. In one embodiment, registered meters may be programmed to only respond to commands from the collector with which they are registered. Accordingly, the command to unregister may comprise the unique identifier of the collector that is being replaced. In response to the command to unregister, the meters begin to operate as unregistered meters and respond to node scan requests. To allow the unregistered command to propagate through the subnet, when a node receives the command it will not unregister immediately, but rather remain registered for a defined period, which may be referred to as the “Time to Live”. During this time to live period, the nodes continue to respond to application layer and immediate retries allowing the unregistration command to propagate to all nodes in the subnet. Ultimately, the meters register with the replacement collector using the procedure described above.
One of collector's 116 main responsibilities within subnet 120 is to retrieve metering data from meters 114. In one embodiment, collector 116 has as a goal to obtain at least one successful read of the metering data per day from each node in its subnet. Collector 116 attempts to retrieve the data from all nodes in its subnet 120 at a configurable periodicity. For example, collector 116 may be configured to attempt to retrieve metering data from meters 114 in its subnet 120 once every 4 hours. In greater detail, in one embodiment, the data collection process begins with the collector 116 identifying one of the meters 114 in its subnet 120. For example, collector 116 may review a list of registered nodes and identify one for reading. The collector 116 then communicates a command to the particular meter 114 that it forward its metering data to the collector 116. If the meter reading is successful and the data is received at collector 116, the collector 116 determines if there are other meters that have not been read during the present reading session. If so, processing continues. However, if all of the meters 114 in subnet 120 have been read, the collector waits a defined length of time, such as, for example, 4 hours, before attempting another read.
If during a read of a particular meter, the meter data is not received at collector 116, the collector 116 begins a retry procedure wherein it attempts to retry the data read from the particular meter. Collector 116 continues to attempt to read the data from the node until either the data is read or the next subnet reading takes place. In an embodiment, collector 116 attempts to read the data every 60 minutes. Thus, wherein a subnet reading is taken every 4 hours, collector 116 may issue three retries between subnet readings.
Meters 114 are often two-way meters—i.e. they are operable to both receive and transmit data. However, one-way meters that are operable only to transmit and not receive data may also be deployed.
While the collection of data from one-way meters by the collector has been described above in the context of a network of two-way meters 114 that operate in the manner described in connection with the embodiments described above, it is understood that the present invention is not limited to the particular form of network established and utilized by the meters 114 to transmit data to the collector. Rather, the present invention may be used in the context of any network topology in which a plurality of two-way communication nodes are capable of transmitting data and of having that data propagated through the network of nodes to the collector.
According to various embodiments described herein, an automated meter data collection system uses a narrowband licensed channel, such as a UHF land-mobile band, to wake carrier-sensed, battery-powered meter reading devices (MRDs) such as the collectors 116 of
In some embodiments, MRDs are awakened and interrogated using a licensed channel, but reply and may further communicate using a high bitrate unlicensed channel. Other embodiments combine a meshed, unlicensed network of MRDs with a roaming interrogator device using the licensed channel to send commands or perform on-demand reads of the MRDs. Such embodiments may realize the lower power consumption associated with using a licensed channel for waking the MRDs by reducing false wakeups and by reducing the amount of time required to synchronize an interrogator device with the MRDs. At the same time, using the unlicensed channel for data replies can realize higher data throughput rates than are commonly associated with the narrowband licensed channel. These benefits are generally mutually exclusive under conventional techniques that use an unlicensed channel for both wakeup and replies.
Using a single licensed channel to communicate with the MRDs may realize certain additional benefits. For example, commands can be sent to the MRDs either individually, in groups, or en masse as a broadcast, quickly and efficiently because interference is minimized. In addition, if the MRD transmits its reply on the unlicensed channel a fixed amount of time after the MRD receives a wakeup message on the licensed channel, a number of additional benefits can be realized. Specifically, the interrogator device is synchronized in time with the MRD as soon as the wakeup message is received without the need to employ frequency-search or code-search schemes that drain battery power. Further, since there is essentially no other traffic on the licensed channel, synchronization is effective the first time, avoiding the need to repeat the synchronization process and further conserving battery power. By contrast, synchronization using an unlicensed channel can require multiple tries due to interference caused by other devices occupying the same unlicensed channel.
Using a combination of a licensed channel and an unlicensed channel also promotes efficient use of the available bandwidth on each channel by placing appropriate loads on each channel. In particular, the narrowband licensed channel carries a very small wakeup/interrogation packet whose size is appropriate for the low bitrate available on the licensed channel. By contrast, the wideband unlicensed channel has a high bitrate that allows the MRD to reply with a large packet of stored data in a short time.
If, during a listening period, the MRD detects a carrier signal whose power is above a fixed or programmable threshold, the MRD transitions to a rouse state 504, as depicted by an edge 506. The rouse state 504 indicates that a mobile interrogator device has entered the detection range of the MRD or that a fixed interrogator device has begun transmitting. In the rouse state 504, the MRD continues with its receiver on to receive data from the interrogator device. This data may include at least one of a preamble, an address, one or more command bits, and a plurality of checksum bits. If the address matches a unique address associated with the MRD and the checksum is correct, the MRD transitions to a wake state 508, as indicated by an edge 510. If either the received address does not match the address of the MRD or the checksum is not correct, the MRD determines that the data received from the interrogator device is not addressed to the MRD and returns to the sleep state 502, as indicated by an edge 512.
The wake state 508 indicates that the MRD has been successfully addressed. In the wake state 508, the MRD processes the command bits. If the command bits do not require a response to the interrogator device, the MRD performs the action or actions indicated by the command bits. For example, the MRD may set a memory register in response to the command bits. After performing the indicated actions, the MRD returns to the sleep state 502, as indicated by an edge 514.
On the other hand, if the command bits do require a response to the interrogator device, the MRD performs the action or actions indicated by the command bits and enters a relatively high power reply state 516, as indicated by an edge 518. In the reply state 516, the MRD transmits a reply to the interrogator device on an unlicensed band in the manner required by wireless agency rules. Because the bandwidth, and therefore the bitrate, are much greater on the unlicensed band as compared with the licensed band used for waking the MRD, a large amount of data, such as meter readings, stored within the MRD can be transmitted to the interrogator device. After the MRD transmits its data to the interrogator device, the MRD returns to the sleep state 502, as indicated by an edge 520.
The carrier signal causes the MRD to enter a rouse portion 606 in which the MRD receives data from the interrogator device. This data may include at least one of a preamble, an address, one or more command bits, and one or more checksum bits. Assuming the address matches a unique address associated with the MRD (or a predetermined group address or broadcast address) and the checksum is correct, the MRD transitions to a wake portion 608. If either of these conditions is not met, the MRD instead returns to the sleep portion 602. The sleep/wake cycle depicted in
During the wake portion 608, the MRD processes the command bits. If the command bits do not require a response to the interrogator device, the MRD performs the action or actions indicated by the command bits and returns to the sleep state 602. The sleep/wake cycle depicted in
It will be appreciated that the lengths of the sleep, rouse, wake, and reply portions of the cycle may vary from cycle to cycle depending on a variety of factors such as, for example, but not limited to, time of year, time of day, and the amount of time since the meter data was last collected by the interrogator device. For example, it may be desirable for the MRD to enter an extended sleep state for the cycle immediately after the MRD's data has been collected by the interrogator device. The lengths of the sleep, wake, rouse, and reply portions of the sleep/wake cycle, including their relative lengths with respect to one another, may vary depending upon a variety of factors such as, for example, but not limited to, the anticipated velocity of the interrogator device, the power required to operate the MRD's transceiver, and the desired battery life for the MRD. For example, the longer the sleep portion is in comparison to the wake portion, the longer the MRD's battery will last. However, the wake portion should be long enough to allow the MRD to properly receive and detect the wake signal. Additionally, it is desirable for the wake portion to repeat frequently enough to ensure that it will occur at least once during the period that the MRD is within the transmission range of the interrogator device.
Next, the MRD determines whether the data received from the interrogator is addressed to the MRD, as depicted at a step 806. If not, the MRD returns to the sleep mode at step 802. If the received data is addressed to the MRD, the MRD enters a wake mode at a step 808. In the wake mode, the MRD processes the data received from the interrogator via the licensed channel, as shown at a step 810. The MRD then determines, at a step 812, whether the data received from the interrogator device requires a reply to be transmitted back to the interrogator device. If not, the MRD performs any actions required by the received data and returns at a step 814 and returns to the sleep mode at step 802. If the received data does require a reply, the MRD performs any actions required by the received data at a step 816 and enters a reply mode at a step 818. In the reply mode, the MRD transmits the reply to the interrogator device using an unlicensed channel having a broader bandwidth than the licensed channel at a step 820. After the reply is transmitted, the MRD returns to the sleep mode at step 802.
In operation, the processor 904 retrieves instructions from the memory 906. The instructions cause the processor 904 to control the operation of the MRD 900 to operate in a mode selected from four operational modes. The selected mode is reconfigurable. In a sleep mode, the transceiver 902 periodically listens on a licensed channel for a carrier signal from an interrogator device (not shown in
In another embodiment, which can be conceived as a “hybrid fixed/mobile” embodiment, the MRD uses the wideband unlicensed band to communicate with a meter or other device in a meshed network that is always listening. Once the MRD has transmitted data and the meter receives the transmission, synchronization is achieved. Two-way communication of commands as well as of stored MRD data can commence. In addition, the MRD continues to power up its licensed channel receiver periodically as described above in connection with
While systems and methods have been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles described above and set forth in the following claims. For example, although in the embodiments described above, the systems and methods of the present invention are described in the context of a network of metering devices, such as electricity, gas, or water meters, it is understood that the present invention can be implemented in any kind of network in which it is necessary to obtain information from or to provide information to end devices in the system, including without limitation, networks comprising meters, in-home displays, in-home thermostats, load control devices, or any combination of such devices. Accordingly, reference should be made to the following claims as describing the scope of the present invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3445815 | Saltzberg et al. | May 1969 | A |
| 3858212 | Tompkins et al. | Dec 1974 | A |
| 3878512 | Kobayashi et al. | Apr 1975 | A |
| 3973240 | Fong | Aug 1976 | A |
| 4031513 | Simciak | Jun 1977 | A |
| 4056107 | Todd et al. | Nov 1977 | A |
| 4066964 | Costanza et al. | Jan 1978 | A |
| 4132981 | White | Jan 1979 | A |
| 4190800 | Kelly, Jr. et al. | Feb 1980 | A |
| 4204195 | Bogacki | May 1980 | A |
| 4218737 | Buscher et al. | Aug 1980 | A |
| 4250489 | Dudash et al. | Feb 1981 | A |
| 4254472 | Juengel et al. | Mar 1981 | A |
| 4319358 | Sepp | Mar 1982 | A |
| 4321582 | Banghart | Mar 1982 | A |
| 4322842 | Martinez | Mar 1982 | A |
| 4328581 | Harmon et al. | May 1982 | A |
| 4361851 | Asip et al. | Nov 1982 | A |
| 4361890 | Green, Jr. et al. | Nov 1982 | A |
| 4396915 | Farnsworth et al. | Aug 1983 | A |
| 4405829 | Rivest et al. | Sep 1983 | A |
| 4415896 | Allgood | Nov 1983 | A |
| 4466001 | Moore et al. | Aug 1984 | A |
| 4504831 | Jahr et al. | Mar 1985 | A |
| 4506386 | Ichikawa et al. | Mar 1985 | A |
| 4513415 | Martinez | Apr 1985 | A |
| 4525861 | Freeburg | Jun 1985 | A |
| 4600923 | Hicks et al. | Jul 1986 | A |
| 4608699 | Batlivala et al. | Aug 1986 | A |
| 4611333 | McCallister et al. | Sep 1986 | A |
| 4614945 | Brunius et al. | Sep 1986 | A |
| 4617566 | Diamond | Oct 1986 | A |
| 4628313 | Gombrich et al. | Dec 1986 | A |
| 4631538 | Carreno | Dec 1986 | A |
| 4638298 | Spiro | Jan 1987 | A |
| 4644321 | Kennon | Feb 1987 | A |
| 4653076 | Jerrim et al. | Mar 1987 | A |
| 4672555 | Hart et al. | Jun 1987 | A |
| 4680704 | Konicek et al. | Jul 1987 | A |
| 4688038 | Giammarese | Aug 1987 | A |
| 4692761 | Robinton | Sep 1987 | A |
| 4707852 | Jahr et al. | Nov 1987 | A |
| 4713837 | Gordon | Dec 1987 | A |
| 4724435 | Moses et al. | Feb 1988 | A |
| 4728950 | Hendrickson et al. | Mar 1988 | A |
| 4734680 | Gehman et al. | Mar 1988 | A |
| 4749992 | Fitzemeyer et al. | Jun 1988 | A |
| 4757456 | Benghiat | Jul 1988 | A |
| 4769772 | Dwyer | Sep 1988 | A |
| 4783748 | Swarztrauber et al. | Nov 1988 | A |
| 4792946 | Mayo | Dec 1988 | A |
| 4799059 | Grindahl et al. | Jan 1989 | A |
| 4804938 | Rouse et al. | Feb 1989 | A |
| 4804957 | Selph et al. | Feb 1989 | A |
| 4811011 | Sollinger | Mar 1989 | A |
| 4827514 | Ziolko et al. | May 1989 | A |
| 4833618 | Verma et al. | May 1989 | A |
| 4839645 | Lill | Jun 1989 | A |
| 4841545 | Endo et al. | Jun 1989 | A |
| 4860379 | Schoeneberger et al. | Aug 1989 | A |
| 4862493 | Venkataraman et al. | Aug 1989 | A |
| 4868877 | Fischer | Sep 1989 | A |
| 4884021 | Hammond et al. | Nov 1989 | A |
| 4912722 | Carlin | Mar 1990 | A |
| 4922518 | Gordon et al. | May 1990 | A |
| 4939726 | Flammer et al. | Jul 1990 | A |
| 4940974 | Sojka | Jul 1990 | A |
| 4940976 | Gastouniotis et al. | Jul 1990 | A |
| 4958359 | Kato | Sep 1990 | A |
| 4964138 | Nease et al. | Oct 1990 | A |
| 4965533 | Gilmore | Oct 1990 | A |
| 4972507 | Lusignan | Nov 1990 | A |
| 5007052 | Flammer | Apr 1991 | A |
| 5018165 | Sohner et al. | May 1991 | A |
| 5022046 | Morrow, Jr. | Jun 1991 | A |
| 5032833 | Laporte | Jul 1991 | A |
| 5053766 | Ruiz-del-Portal et al. | Oct 1991 | A |
| 5053774 | Schuermann et al. | Oct 1991 | A |
| 5056107 | Johnson et al. | Oct 1991 | A |
| 5067136 | Arthur et al. | Nov 1991 | A |
| 5079715 | Venkataraman et al. | Jan 1992 | A |
| 5079768 | Flammer | Jan 1992 | A |
| 5086292 | Johnson et al. | Feb 1992 | A |
| 5086385 | Launey | Feb 1992 | A |
| 5090024 | Vander Mey et al. | Feb 1992 | A |
| 5111479 | Akazawa | May 1992 | A |
| 5115433 | Baran et al. | May 1992 | A |
| 5115448 | Mori | May 1992 | A |
| 5129096 | Burns | Jul 1992 | A |
| 5130987 | Flammer | Jul 1992 | A |
| 5132985 | Hashimoto et al. | Jul 1992 | A |
| 5136614 | Hiramatsu et al. | Aug 1992 | A |
| 5142694 | Jackson et al. | Aug 1992 | A |
| 5151866 | Glaser et al. | Sep 1992 | A |
| 5155481 | Brennan, Jr. et al. | Oct 1992 | A |
| 5160926 | Schweitzer, III | Nov 1992 | A |
| 5166664 | Fish | Nov 1992 | A |
| 5177767 | Kato | Jan 1993 | A |
| 5179376 | Pomatto | Jan 1993 | A |
| 5189694 | Garland | Feb 1993 | A |
| 5194860 | Jones et al. | Mar 1993 | A |
| 5197095 | Bonnet | Mar 1993 | A |
| 5204877 | Endo et al. | Apr 1993 | A |
| 5214587 | Green | May 1993 | A |
| 5225994 | Arinobu et al. | Jul 1993 | A |
| 5228029 | Kotzin | Jul 1993 | A |
| 5229996 | Bäckström et al. | Jul 1993 | A |
| 5239575 | White et al. | Aug 1993 | A |
| 5239584 | Hershey et al. | Aug 1993 | A |
| 5243338 | Brennan, Jr. et al. | Sep 1993 | A |
| 5252967 | Brennan et al. | Oct 1993 | A |
| 5260943 | Comroe et al. | Nov 1993 | A |
| 5270704 | Sosa Quintana et al. | Dec 1993 | A |
| 5280498 | Tymes et al. | Jan 1994 | A |
| 5280499 | Suzuki | Jan 1994 | A |
| 5285469 | Vanderpool | Feb 1994 | A |
| 5287287 | Chamberlain et al. | Feb 1994 | A |
| 5289497 | Jacobson et al. | Feb 1994 | A |
| 5295154 | Meier et al. | Mar 1994 | A |
| 5307349 | Shloss et al. | Apr 1994 | A |
| 5311541 | Sanderford, Jr. | May 1994 | A |
| 5311542 | Eder | May 1994 | A |
| 5315531 | Oravetz et al. | May 1994 | A |
| 5319679 | Bagby | Jun 1994 | A |
| 5329547 | Ling | Jul 1994 | A |
| 5345225 | Davis | Sep 1994 | A |
| 5359625 | Vander Mey et al. | Oct 1994 | A |
| 5377222 | Sanderford, Jr. | Dec 1994 | A |
| 5381462 | Larson et al. | Jan 1995 | A |
| 5383134 | Wrzesinski | Jan 1995 | A |
| 5384712 | Oravetz et al. | Jan 1995 | A |
| 5387873 | Muller et al. | Feb 1995 | A |
| 5390360 | Scop et al. | Feb 1995 | A |
| 5406495 | Hill | Apr 1995 | A |
| 5416917 | Adair et al. | May 1995 | A |
| 5420799 | Peterson et al. | May 1995 | A |
| 5428636 | Meier | Jun 1995 | A |
| 5430759 | Yokev et al. | Jul 1995 | A |
| 5432507 | Mussino et al. | Jul 1995 | A |
| 5432815 | Kang et al. | Jul 1995 | A |
| 5438329 | Gastouniotis et al. | Aug 1995 | A |
| 5448230 | Schanker et al. | Sep 1995 | A |
| 5448570 | Toda et al. | Sep 1995 | A |
| 5450088 | Meier et al. | Sep 1995 | A |
| 5452465 | Geller et al. | Sep 1995 | A |
| 5455533 | Köllner | Oct 1995 | A |
| 5455544 | Kechkaylo | Oct 1995 | A |
| 5455569 | Sherman et al. | Oct 1995 | A |
| 5455822 | Dixon et al. | Oct 1995 | A |
| 5457713 | Sanderford, Jr. et al. | Oct 1995 | A |
| 5461558 | Patsiokas et al. | Oct 1995 | A |
| 5463657 | Rice | Oct 1995 | A |
| 5473322 | Carney | Dec 1995 | A |
| 5475742 | Gilbert | Dec 1995 | A |
| 5475867 | Blum | Dec 1995 | A |
| 5479442 | Yamamoto | Dec 1995 | A |
| 5481259 | Bane | Jan 1996 | A |
| 5488608 | Flammer, III | Jan 1996 | A |
| 5491473 | Gilbert | Feb 1996 | A |
| 5493287 | Bane | Feb 1996 | A |
| 5495239 | Ouellette | Feb 1996 | A |
| 5497424 | Vanderpool | Mar 1996 | A |
| 5499243 | Hall | Mar 1996 | A |
| 5500871 | Kato et al. | Mar 1996 | A |
| 5511188 | Pascucci et al. | Apr 1996 | A |
| 5519388 | Adair, Jr. | May 1996 | A |
| 5521910 | Matthews | May 1996 | A |
| 5522044 | Pascucci et al. | May 1996 | A |
| 5524280 | Douthitt et al. | Jun 1996 | A |
| 5525898 | Lee, Jr. et al. | Jun 1996 | A |
| 5526389 | Buell et al. | Jun 1996 | A |
| 5528507 | McNamara et al. | Jun 1996 | A |
| 5528597 | Gerszberg et al. | Jun 1996 | A |
| 5539775 | Tuttle et al. | Jul 1996 | A |
| 5541589 | Delaney | Jul 1996 | A |
| 5544036 | Brown, Jr. et al. | Aug 1996 | A |
| 5546424 | Miyake | Aug 1996 | A |
| 5548527 | Hemminger et al. | Aug 1996 | A |
| 5548633 | Kujawa et al. | Aug 1996 | A |
| 5553094 | Johnson et al. | Sep 1996 | A |
| 5555508 | Munday et al. | Sep 1996 | A |
| 5559870 | Patton et al. | Sep 1996 | A |
| 5566332 | Adair et al. | Oct 1996 | A |
| 5570084 | Ritter et al. | Oct 1996 | A |
| 5572438 | Ehlers et al. | Nov 1996 | A |
| 5574657 | Tofte | Nov 1996 | A |
| 5590179 | Shincovich et al. | Dec 1996 | A |
| 5592470 | Rudrapatna et al. | Jan 1997 | A |
| 5594740 | LaDue | Jan 1997 | A |
| 5602744 | Meek et al. | Feb 1997 | A |
| 5617084 | Sears | Apr 1997 | A |
| 5619192 | Ayala | Apr 1997 | A |
| 5619685 | Schiavone | Apr 1997 | A |
| 5621629 | Hemminger et al. | Apr 1997 | A |
| 5627759 | Bearden et al. | May 1997 | A |
| 5631636 | Bane | May 1997 | A |
| 5636216 | Fox et al. | Jun 1997 | A |
| 5640679 | Lundqvist et al. | Jun 1997 | A |
| 5659300 | Dresselhuys et al. | Aug 1997 | A |
| 5668803 | Tymes et al. | Sep 1997 | A |
| 5668828 | Sanderford, Jr. et al. | Sep 1997 | A |
| 5673252 | Johnson et al. | Sep 1997 | A |
| 5684472 | Bane | Nov 1997 | A |
| 5684799 | Bigham et al. | Nov 1997 | A |
| 5691715 | Ouellette | Nov 1997 | A |
| 5692180 | Lee | Nov 1997 | A |
| 5696501 | Ouellette et al. | Dec 1997 | A |
| 5696765 | Safadi | Dec 1997 | A |
| 5696903 | Mahany | Dec 1997 | A |
| 5699276 | Roos | Dec 1997 | A |
| 5714931 | Petite et al. | Feb 1998 | A |
| 5715390 | Hoffman et al. | Feb 1998 | A |
| 5717604 | Wiggins | Feb 1998 | A |
| 5719564 | Sears | Feb 1998 | A |
| 5745901 | Entner et al. | Apr 1998 | A |
| 5748104 | Argyroudis et al. | May 1998 | A |
| 5748619 | Meier | May 1998 | A |
| 5751914 | Coley et al. | May 1998 | A |
| 5751961 | Smyk | May 1998 | A |
| 5754772 | Leaf | May 1998 | A |
| 5754830 | Butts et al. | May 1998 | A |
| 5757783 | Eng et al. | May 1998 | A |
| 5768148 | Murphy et al. | Jun 1998 | A |
| 5778368 | Hogan et al. | Jul 1998 | A |
| 5787437 | Potterveld et al. | Jul 1998 | A |
| 5790789 | Suarez | Aug 1998 | A |
| 5790809 | Holmes | Aug 1998 | A |
| 5801643 | Williams et al. | Sep 1998 | A |
| 5805712 | Davis | Sep 1998 | A |
| 5808558 | Meek et al. | Sep 1998 | A |
| 5809059 | Souissi et al. | Sep 1998 | A |
| 5822521 | Gartner et al. | Oct 1998 | A |
| 5850187 | Carrender et al. | Dec 1998 | A |
| 5862391 | Salas et al. | Jan 1999 | A |
| 5872774 | Wheatley, III et al. | Feb 1999 | A |
| 5874903 | Shuey et al. | Feb 1999 | A |
| 5875183 | Nitadori | Feb 1999 | A |
| 5875402 | Yamawaki | Feb 1999 | A |
| 5884184 | Sheffer | Mar 1999 | A |
| 5892758 | Argyroudis | Apr 1999 | A |
| 5896382 | Davis et al. | Apr 1999 | A |
| 5897607 | Jenney et al. | Apr 1999 | A |
| 5898387 | Davis et al. | Apr 1999 | A |
| 5907491 | Canada et al. | May 1999 | A |
| 5907540 | Hayashi | May 1999 | A |
| 5910799 | Carpenter et al. | Jun 1999 | A |
| 5914673 | Jennings et al. | Jun 1999 | A |
| 5923269 | Shuey et al. | Jul 1999 | A |
| 5926103 | Petite | Jul 1999 | A |
| 5926531 | Petite | Jul 1999 | A |
| 5943375 | Veintimilla | Aug 1999 | A |
| 5944842 | Propp et al. | Aug 1999 | A |
| 5953319 | Dutta et al. | Sep 1999 | A |
| 5958018 | Eng et al. | Sep 1999 | A |
| 5959550 | Giles | Sep 1999 | A |
| 5960074 | Clark | Sep 1999 | A |
| 5963146 | Johnson et al. | Oct 1999 | A |
| 5974236 | Sherman | Oct 1999 | A |
| 5986574 | Colton | Nov 1999 | A |
| 6000034 | Lightbody et al. | Dec 1999 | A |
| 6028522 | Petite | Feb 2000 | A |
| 6034988 | VanderMey et al. | Mar 2000 | A |
| 6035201 | Whitehead | Mar 2000 | A |
| 6041056 | Bigham et al. | Mar 2000 | A |
| 6061604 | Russ et al. | May 2000 | A |
| 6067029 | Durston | May 2000 | A |
| 6073169 | Shuey et al. | Jun 2000 | A |
| 6073174 | Montgomerie et al. | Jun 2000 | A |
| 6078251 | Landt et al. | Jun 2000 | A |
| 6078909 | Knutson | Jun 2000 | A |
| 6088659 | Kelley et al. | Jul 2000 | A |
| 6091758 | Ciccone et al. | Jul 2000 | A |
| 6100817 | Mason, Jr. et al. | Aug 2000 | A |
| 6112192 | Capek | Aug 2000 | A |
| 6124806 | Cunningham et al. | Sep 2000 | A |
| 6128276 | Agee | Oct 2000 | A |
| 6137423 | Glorioso et al. | Oct 2000 | A |
| 6150955 | Tracy et al. | Nov 2000 | A |
| 6154487 | Murai et al. | Nov 2000 | A |
| 6160993 | Wilson | Dec 2000 | A |
| 6172616 | Johnson et al. | Jan 2001 | B1 |
| 6195018 | Ragle et al. | Feb 2001 | B1 |
| 6199068 | Carpenter | Mar 2001 | B1 |
| 6208266 | Lyons et al. | Mar 2001 | B1 |
| 6218953 | Petite | Apr 2001 | B1 |
| 6233327 | Petite | May 2001 | B1 |
| 6246677 | Nap et al. | Jun 2001 | B1 |
| 6249516 | Brownrigg et al. | Jun 2001 | B1 |
| 6333975 | Brunn et al. | Dec 2001 | B1 |
| 6363057 | Ardalan et al. | Mar 2002 | B1 |
| 6373399 | Johnson et al. | Apr 2002 | B1 |
| 6393341 | Lawrence et al. | May 2002 | B1 |
| 6396839 | Ardalan et al. | May 2002 | B1 |
| 6421731 | Ciotti, Jr. et al. | Jul 2002 | B1 |
| 6430268 | Petite | Aug 2002 | B1 |
| 6437692 | Petite et al. | Aug 2002 | B1 |
| 6446192 | Narasimhan et al. | Sep 2002 | B1 |
| 6643278 | Panasik et al. | Nov 2003 | B1 |
| 6657549 | Avery | Dec 2003 | B1 |
| 6684245 | Shuey et al. | Jan 2004 | B1 |
| 6751563 | Spanier et al. | Jun 2004 | B2 |
| 6867707 | Kelley et al. | Mar 2005 | B1 |
| 6996215 | MacConnell | Feb 2006 | B2 |
| 7412235 | Larson et al. | Aug 2008 | B2 |
| 20010002210 | Petite | May 2001 | A1 |
| 20010024163 | Petite | Sep 2001 | A1 |
| 20020012323 | Petite et al. | Jan 2002 | A1 |
| 20020013679 | Petite | Jan 2002 | A1 |
| 20020019712 | Petite et al. | Feb 2002 | A1 |
| 20020019725 | Petite | Feb 2002 | A1 |
| 20020026957 | Reyman | Mar 2002 | A1 |
| 20020027504 | Davis et al. | Mar 2002 | A1 |
| 20020031101 | Petite et al. | Mar 2002 | A1 |
| 20020094799 | Elliott et al. | Jul 2002 | A1 |
| 20020125998 | Petite et al. | Sep 2002 | A1 |
| 20020145537 | Mueller et al. | Oct 2002 | A1 |
| 20020159426 | Kanemoto et al. | Oct 2002 | A1 |
| 20020169643 | Petite et al. | Nov 2002 | A1 |
| 20030036810 | Petite | Feb 2003 | A1 |
| 20030036822 | Davis et al. | Feb 2003 | A1 |
| 20030123442 | Drucker et al. | Jul 2003 | A1 |
| 20030202512 | Kennedy | Oct 2003 | A1 |
| 20040001008 | Shuey et al. | Jan 2004 | A1 |
| 20040113810 | Mason, Jr. et al. | Jun 2004 | A1 |
| 20050121526 | Stewart et al. | Jun 2005 | A1 |
| 20050184881 | Dusenberry et al. | Aug 2005 | A1 |
| 20050270173 | Boaz | Dec 2005 | A1 |
| 20080259844 | Richeson et al. | Oct 2008 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20100207784 A1 | Aug 2010 | US |
