Source: https://patents.google.com/patent/US8019836B2/en
Timestamp: 2019-04-21 14:33:30+00:00

Document:
2011-11-04 US case 3:11-cv-00621 filed litigation Critical https://portal.unifiedpatents.com/litigation/Kentucky%20Western%20District%20Court/case/3%3A11-cv-00621 Source: District Court Jurisdiction: Kentucky Western District Court "Unified Patents Litigation Data" by Unified Patents is licensed under a Creative Commons Attribution 4.0 International License.
2011-11-04 First worldwide family litigation filed litigation https://patents.darts-ip.com/?family=39476401&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US8019836(B2) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
2013-05-08 Assigned to GARRARD, KENNETH W. reassignment GARRARD, KENNETH W. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TELEMETRY TECHNOLOGIES, INC.
2013-05-08 Assigned to MESH COMM, LLC reassignment MESH COMM, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GARRARD, KENNETH W.
2013-05-08 Assigned to TELEMETRY TECHNOLOGIES, INC. reassignment TELEMETRY TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ELLIOTT, KARL E., GARRARD, KENNETH W.
2013-07-19 Assigned to ENDEAVOR IP, INC. reassignment ENDEAVOR IP, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: FINISHING TOUCHES HOME GOODS, INC.
2013-07-22 Assigned to ENDEAVOR MESHTECH, INC. reassignment ENDEAVOR MESHTECH, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ENDEAVOR IP, INC.
A meter enabled for wireless communication and a wireless communication network are disclosed. A meter enabled for wireless communication comprises a metering device, a wireless communication system and an interface between the two. Meter data can be read, and the meter can be controlled via communication with a wireless network using, e.g., the Bluetooth™ protocol A self-configuring wireless network is also disclosed. The wireless network includes a number of vnodes, and one or more VGATES. The vnodes are devices that are enabled for wireless communication using, e.g., the Bluetooth™ protocol. Vnodes are operative to form ad hoc piconet connections. The one or more VGATES comprise computer network gateways that are enabled for wireless communication using, e.g., the Bluetooth™ protocol. Thus, the VGATES enable the wireless array of vnodes to communicate with a private or public computer network to transmit data or receive commands. The network may also communicate with a VNOC system. VNOC is a universal communications adapter that enables the wireless array of vnodes to communicate (either directly or through a VGATE) with a central control facility via various wireless or wired communication media.
The present application is a continuation of non-provisional U.S. application Ser. No. 10/040,150, filed Jan. 2, 2002, which is a continuation of non-provisional application No. 09/774,121, filed Jan. 31, 2001 and a continuation in part of non-provisional application No. 09/621,965, filed Jul. 21, 2000. Non-provisional application No. 09/774,121 claims priority to provisional application No. 60/179,046, filed Jan. 31, 2000, and provisional application No. 60/179,041, filed Jan. 31, 2000.
The subject matter of this application is related to the subject matter of copending U.S. Patent application Ser. Nos. 60/179,041, 60/179,046 and 09/621,965, entitled “Wireless Communication Enabled Meter and Network,” “Wireless Communication Enabled Meter and Network,” and “System and Method for a Virtual Network Operations Center,” respectively, each having the same inventors as this application, each being assigned or under obligation of assignment to the same assignee as this application and each incorporated herein by reference.
This invention relates to a meter that is enabled for wireless communication More specifically, this invention relates to a meter, such as a utility meter, that is enabled for wireless communication. The invention also relates to a self-configuring, wireless network that enables data capture at a plurality of metering sites and wireless transmission of the captured data from the plurality of metering sites to one or more collection points.
Remote communication with meters is known, for example, for home load control and for usage monitoring. Commands for home load control are typically transmitted over telephone lines or power lines. Communicating via power lines or telephone lines is slow and subject to physical disruption. Moreover, communicating via power lines or telephone lines presents the possibility of spurious signals, cross-talk, and other interference. One-way or two-way radios are also sometimes used. Both are expensive and two-way radios also require a license.
According to another embodiment, a self-configuring wireless network is disclosed. The wireless network comprises a number of virtual nodes (“vnodes”), and one or more virtual gates (“VGATES”). Vnodes are operative to form ad hoc piconet connections. Vnodes can comprise a variety of devices. Data traveling through the network is passed from one or more ad hoc piconets to one or more of the vnodes or an uploading point, e.g., a VGATE. If a vnode is not connected to a piconet, or if its connection to a piconet has been disturbed, the vnode executes a self-configuration routine to connect itself with another piconet. This self configuration process is based on a set of rules. The one or more VGATES comprise computer network gateways enabled for communication.
FIG. 2 is a schematic depiction of a self-configuring wireless network according to another embodiment of the present invention.
FIG. 3 is a schematic depiction of a self-configuring wireless network according to another embodiment of the present invention.
FIG. 4 is a schematic depiction of a self-configuring wireless network according to another embodiment of the present invention.
FIG. 5 is a schematic diagram showing a self-configuration process according to one embodiment of the present invention.
Metering device 2 operates to measure and regulate the usage of some utility, e.g., natural gas, electricity, or water. According to one embodiment, metering device 2 comprises any known metering device capable of producing an analog or digital output signal indicative of utility usage. In another embodiment, metering device 2 comprises a metering device capable of accepting an analog or digital input signal and for monitoring and controlling utility usage. For example, metering device 2 is operative to monitor utility usage. Utility usage data is useful in the electrical industry, for example, to control future generation in order to avoid over generation or under generation of electricity. According to another example, metering device 2 is operative to monitor power quality, The power factor of electrical power, for example, may vary with usage. Metering device 2 can monitor this variance. In turn, household devices that are also enabled for wireless communication can be controlled to change the load and correct the power factor. According to one particular embodiment, metering device 2 comprises the Altimus™ produced and sold by Landis & Gyr Utilities Services, Inc.
Briefly, Bluetooth™ is a wireless communication protocol operating in the unlicensed ISM band at 2.4 GHz that enables wireless communication of data and voice. The Bluetooth™ system operates through a collection of short-range radio links, built into 9×9 mm microchips, i.e., Bluetooth™ chips. The short-range radio links enable ad hoc groupings of connected devices away from fixed network infrastructures.
Bluetooth™ uses an acknowledgment and frequency hopping scheme to make network links robust. Specifically, Bluetooth™ radio modules avoid interference from other signals by hopping to a new frequency after transmitting or receiving a packet of data. The Bluetooth™ radio uses faster hopping and shorter packets than other systems operating in the same frequency band Short packages and fast hopping make the Bluetooth™ system robust, e.g., by limiting the impact of domestic and professional microwave ovens and other potential sources of interference.
The Bluetooth™ baseband protocol is a combination of circuit and packet switching. Slots can be reserved for synchronous data packets. Each data packet is transmitted in a different hop frequency. A packet nominally covers a single slot, but can be extended to cover up to five slots. Bluetooth™ supports an asynchronous data channel, up to three simultaneous synchronous voice channels, or a channel which simultaneously supports asynchronous data and synchronous voice. Each voice channel supports 64 kb/s synchronous (voice) link. The asynchronous channel can support an asymmetric link of maximally 721 kb/s in either direction while permitting 57.6 kb/s in the return direction, or a 432.6 kb/s symmetric link.
Using Bluetooth™, meter 1 transmits data to, for example, a central collection point via other Bluetooth™ enabled devices (e.g., other Bluetooth™ enabled meters) forming an ad hoc network. Moreover, meter 1 receives data from a central controller via other Bluetooth™ enabled devices through a similar type of ad hoc network.
Vnodes 23 comprise individually addressable entities enabled for wireless communication. Vnodes 23 can be originators, recipients or routers of data. According to one embodiment, each vnode 23 has its own IP address so that commands can be sent to and data can be collected from individual vnodes through VGATE 22. As will be explained in more detail below, VGATE 22 may be a computer gateway that enables communications between public or private computer networks 26 and network 20. According to one embodiment, vnodes 23 maintain a routing table with information about two separate groups of entities. The first group comprises vnodes 23 that are potential gateways for this vnode. Typically, one of the vnodes in this list has an acknowledged active route to a gateway such as VGATE 22. According to one embodiment, this route is stored in non-volatile memory so that a vnode may attempt to establish a connection with VGATE 22 without going through the self-configuration process described below. The second group comprises vnodes 23 that have a confirmed route to a gateway using this vnode as an intermediate hop. The concept of hops to a gateway is explained in more detail below in conjunction with the self-configuring process.
As schematically depicted in FIG. 2, each of the rows of vnodes 23 may form a piconet 21. Data passing through the network 20 “hops” from one piconet 21 to another piconet 21 via wireless connections as shown in FIG. 2. These wireless connections are depicted at a particular instant in time and may change as piconets 21 are reconfigured. Data travels until it reaches the appropriate destination which may be VGATE 22 for data traveling upstream or one or more of vnodes 23 (or another Bluetooth™ enabled device) for data traveling downstream.
According to another embodiment, VGATE 22 may be enabled to communicate using a number of separate wireless devices. Thus, the number of vnodes 23 that any VGATE 22 may act as a gateway for is increased. According to one embodiment, VGATE 22 is equipped with two or more Bluetooth™ chips and its capacity is at least doubled.
VGATE 22 may also act as an administrator for network 22. Specifically, VGATE 22 may comprise intelligence about the configuration of network 20. According to one embodiment, VGATE 22 comprises an intelligence module that contains the geographic location of all vnodes 23 within a certain distance of VGATE 22 and a list of all vnodes 23 that are presently communicating with VGATE 22. This is useful for example for locating specific vnodes 23, for example, for service purposes. For example, assume each vnode 23 represents a utility meter 21 in a residential neighborhood. If one of the meters 21 is not functioning properly, a repair person can determine the location of the vnode 23 from VGATE 22. Alternatively, if a repair person is driving through the neighborhood, that person can connect to network 20 using the self configuring process (explained below) as a vnode 23 would. Once connected, the repair person can use VGATE 22 to locate the non-functional vnode 23.
In another embodiment, networks 31-38 need not create a daisy chain path to communicate to a VGATE 22 through the geographically nearest network. For example, a network 38 may communicate to a VGATE 22 through a network 35 although network 3D is not the geographically nearest network to network 38.
As discussed above, VGATE 22 facilitates communication between network 20 and other public or private computer networks using, e.g., conventional wired networking. In contrast, VNOC 25 comprises a virtual network operation center. According to one embodiment, VNOC 25 comprises a universal communication adapter that is enabled to transmit and receive using a variety of communication protocols and media. VNOC 25 is capable of communicating using RF, cellular, microwave, satellite and other communication protocol. According to one embodiment, VNOC 25 communicates with VGATE 22 in order to facilitate communication between network 20 and other non-wired networks. For example, VNOC 25 can receive command data for network 20 via satellite communication and retransmit the command data to VGATE 22 for distribution to vnodes 23. According to one particular embodiment, VNOC 25 comprises the VNOC system sold by Telemetry Technologies, Inc.
According to another embodiment, VNOC 25 may communicate directly with vnodes 23. In this embodiment, VNOC 25 is enabled for communication using the Bluetooth™ communication protocol. For example, VNOC 25 may receive command data for any of vnodes 23 via any of its enabled communication protocols. VNOC 25 may then retransmit the command data to the appropriate vnode using the Bluetooth™ protocol. Conversely, VNOC 25 may receive collected data from one or more of vnodes 23 via network 20 using the Bluetooth protocol and then retransmit the collected data to another location using an appropriate one of its enabled communication protocols. Accordingly, VNOC 25 enables communication with devices forming part of network 20 using a number of different communication protocol or media. VNOC 25 is especially useful for networks 20 installed in remote or rural areas where hard wire connections are uneconomical. A detailed description of VNOC 25 is provided in conjunction with FIGS. 7-12 below.
In another embodiment, shown in FIG. 4, the network 20 may be a wide area network to optimize communication in rural areas. Network 20 may include piconets 21 a, 21 z. As shown, piconet 21 z is a distance D from its geographically nearest piconet 21 a in network 20. High gain, directional antennas 41-42 may be used to provide a line of sight point to point connection between vnode 23 a of piconet 21 a and vnode 23 z of piconet 21 z. Antennas 41-42 form fixed links, and boost decibel gain and power in the network 20. Use of antennas 41-42 to form connections between vnodes 23 a, 23 z allows the range from the Bluetooth™ equipment to be increased to at least approximately 17 miles.
VNOC 25 will now be explained in conjunction with FIGS. 9-14. Typically, the VNOC system is intended to provide seamless service for the customer. For example, the following description of one embodiment of the VNOC system is provided with reference to a remote water meter controller. The water metering customer has a remotely located water supply implementing a remotely controllable water metering valve. The customer desires to control the metering valve, monitor its status, and collect other data pertaining to the valve (e.g., daily throughput, average water temperature, or other data). If a particular circumstance should occur (e.g., the water flow drops below a predetermined level), the water valve meter sends a signal in whichever format the remote controller implements (e.g., cellular, wireline, Internet, or other format). The VNOC system provides the interface to receive data from the remote valve in that format and records the occurrence of an incoming event. The VNOC translates the incoming event into the outgoing event format (or formats) pre-selected by the customer. If the incoming event is one that the customer designated as requiring notification, the selected notification report is sent to the customer over the appropriate customer interface (e.g., facsimile, pager, email, etc.).
The various customer interfaces communicate with VNOC 25 over an appropriate network. For example, computer related customer interfaces (e.g., web browser, email interface, or custom IP application) communicate with VNOC 25 over a computer network 31 such as the Internet or a local intranet. Other computer networks (WANs, LANs, etc.) are possible. Similarly, telephone related customer interfaces (e.g., modem, IR, fax machine, or pager) communicate with VNOC 25 over a telephone network 32 and custom devices communicate with VNOC 25 over a suitable custom network 33 (e.g., X.25, VSAT, SCADA, wireless, etc.).
As shown in FIG. 10, the various customer and network interfaces communicate through the transmission of events through VNOC 25. Inbound events may originate at the customer interface (e.g., inbound event 200), or the network interface (e.g., inbound event 206). These inbound events are processed into corresponding outbound events (e.g., outbound events 204 and 202). As noted above, events correspond to occurrences (or the lack of an occurrence) pre-selected for customer monitoring. In other words, the events are situations for which the customer desires to be notified. Thus, events may comprise physical occurrences (eg, a meter records a certain value, a pre-selected inventory item is shipped, etc.) or other less tangible occurrences (e.g., a pre-selected stock price is reached, a certain sales volume is reached, a particular email message is received, a particular time period has expired, a dat file has been transferred, a point-to-point message is received, etc.).
FIG. 12 is a schematic representation of internal structure of VNOC 25. VNOC manager 100 manages communication between customer interfaces and network interfaces. Event manager 102 enables the management of events passing through VNOC 25. For example, events such as incharge, onset to offload, dependencies, concurrence, and others may be managed by event manager 102. Publication/subscription manager 104 enables the management of customer subscription to, and network publication of events. Configuration manager 106 manages the configuration of various VNOC 25 components by enabling, for example, customer specification of interfaces, protocols, services and other criteria. Security manager 108 enables management of various security measures implemented in the VNOC system. For example, security measures such as access rights, revocation, auditing, and other security functions may be managed by security manager 108. Error and recovery management manager 110 enables the management of error detection and recovery from errors. For example, error and recovery functions such as, notification, logging, recovery, backups, secondary paths, and other functions may be managed by error and recovery manager 110. Replication redundancy manager 112 enables various replication features. For example, redundancies between machines and locations, hot failure switchovers, persistence, rollovers, and other replication features may be managed by replication redundancy manager 112. Customer billing module 114 enables, among other things, the tracking and billing of customer usage. For example, customer billing module 114 may manage the tracking of the level of usage, accumulation of bills, charges to third party interfaces, and other billing functions. Audit and log module 116 enables auditing and logging of various information. For example, location, levels, access, presentation, historical presence, and other information may be managed by audit and log module 116. Event naming module 118 manages the naming of events and may communicate with event database 120. For example, using an extensible markup language (XML) style event naming.
The systems explained in conjunction with FIGS. 1-4 and 9-14 can be employed in a variety of different applications which are suited for remote monitoring. For example, in addition to monitoring devices such as meters and wireless networks as discussed in FIGS. 1-4, the system of FIGS. 1-4 and 9-14 may be employed to monitor devices such as vending machines, drop boxes, sewer and water treatment facilities, flood control systems, railroad systems, waste management systems, environmental management systems, oil and gas pipelines, traffic systems, electric, gas and water utility systems, and medical alert systems. The system of FIGS. 1-4 and 9-14 may also be employed as part of a quality management system. Other applications will be apparent to persons skilled in the art.
The present invention may also be employed as part of a waste management system to monitor such things as the need for pick-up at a particular dumpster, the truck count at a dumpster and/or to determine whether a particular truck is full and needs to unload. This could be done by interfacing conventional sensors at dumpster sites with a wireless communication system such as the Bluetooth™ system. In this manner, trucks can be more efficiently deployed to make pick-ups where needed and to avoid unnecessary pick ups. This may permit a reduction in the number of trucks required to service a particular area and/or allow alterations of the size or placement of dumpsters to efficiently accommodate the need for same.
(ii) a gateway being communicatively coupled to said group of virtual network nodes and configured to provide a communication access point between said group of virtual network nodes and an external network, wherein access by an additional virtual network node, which is separate from said group of virtual network nodes, to said external network is facilitated by a route that includes a wireless communication link between said additional virtual network node and a first of said group of virtual network nodes and a path from said first of said group of virtual network nodes to said virtual gate defined by said organized network.
2. The self configuring wireless network of claim 1, wherein each of said group of virtual network nodes is configured to execute a self configuration cycle to establish said organized network.
3. The self configuring wireless network of claim 2, wherein said self configuration cycle is executed upon initialization and/or upon a detected disruption in connectivity.
4. The self configuring wireless network of claim 2, wherein said self configuration cycle includes a determination of whether a number of hops to said virtual gate exceeds a maximum number of hops.
5. The self configuring wireless network of claim 2, wherein said self configuration cycle includes an examination of a measure of redundancy in connections.
6. The self configuring wireless network of claim 2, wherein said self configuration cycle includes a determination of whether a connection is made only to a group of virtual network nodes that is searching for another virtual network node.
7. The self configuring wireless network of claim 2, wherein said self configuration cycle includes a determination of signal strength.
8. The self configuring wireless network of claim 2, wherein said self configuration cycle is based on request messages that are sent after pseudo random delays.
9. The self configuring wireless network of claim 1, wherein each of said group of virtual network nodes store information regarding the identities and/or location of at least one other virtual network node.
10. The self configuring wireless network of claim 1, wherein each of said group of virtual network nodes stores a routing table that comprises routing information about at least one other virtual network node.
11. The self configuring wireless network of claim 1, wherein each of said group of virtual network nodes is configured to execute a polling procedure to poll at least one other virtual network nodes.
12. The self configuring wireless network of claim 1, wherein each of said group of virtual network nodes is configured with encryption capability to encrypt communications with at least one other virtual network node.
13. The self configuring wireless network of claim 1, wherein said virtual gate comprises a computer network gateway.
14. The self configuring wireless network of claim 1, wherein said virtual gate stores geographic location of all virtual network nodes within a pre-specified distance of said virtual gate.
15. The self configuring wireless network of claim 1, wherein said wireless communication link employs at least one multiplexed communication channel.
16. The self configuring wireless network of claim 1, wherein said wireless communication link includes a first channel used for upstream communication and a second channel used for downstream communication.
(iii) an interface module configured to facilitate communication of event information between said virtual network nodes and said external network.
a communication management module configured to manage communication of the pre-specified events between the virtual network nodes and said external network.
19. The self configuring wireless network of claim 18, wherein said communication interface facilitates remote monitoring of at least one of said virtual network nodes.
20. The self configuring wireless network of claim 18, wherein said communication interface includes a customer interface.
21. The self configuring wireless network of claim 20, wherein said customer interface comprises a web browser interface, electronic mail interface, a customized Internet Protocol application interface, a telephone interface, a modem interface, and/or a paging device interface.
22. The self configuring wireless network of claim 18, wherein said communications interface includes a network interface.
23. The self configuring wireless network of claim 22, wherein said network interface comprises a Bluetooth interface, a cellular communication interface, a satellite communication interface, a MicroBurst interface, an Internet communication interface, an OrbComm interface, a GSM interface, and/or a Cellemetry interface.
24. The self configuring wireless network of claim 17, wherein said interface module further comprises a configuration management module that specifies one or more of interface information, protocol information, and pre-specified services.
25. The self configuring wireless network of claim 17, wherein said interface module further comprises a security management module that manages security of communications.
26. The self configuring wireless network of claim 17, wherein said interface module further comprises an error and recovery management module that manages detection of, and recovery from, communication errors.
27. The self configuring wireless network of claim 17, wherein said interface module further comprises a replication redundancy management module that replicates attribute information regarding the self configuration wireless communication network.
28. The self configuring wireless network of claim 17, wherein said interface module further comprises a billing module that tracks and bills usage of services provided by the self configuring wireless communication network.
29. The self configuring wireless network of claim 17, wherein said interface module further comprises an audit and logging module.
30. The self configuring wireless network of claim 17, wherein said interface module further comprises a publication and subscription management module that manages the publication of the occurrences of the pre-specified events.
B. Miller, "Mapping Salutation Architecture API's to Bluettooth Service Discovery Layer, Version 1.0," Bluetooth White Paper, Jul. 1, 1999.
J. Haartsen, Bluetooth—The universal radio interfade for ad hoc, wireless connectivity, Ericsson Review No. 3, 1998.
Mesh Comm, LLC v. Pepco Energy Services. et al., Case No. 1:09-cv-02804-RDB, Declaration of David B. Schumann in Support of Silver Spring Network, Inc.'s Responsive Claim Construction Brief, Aug. 30, 2010.
Metricom, Radio Command Reference Guide, Phase 2 Alpha, Version 1, Oct. 7, 1998.
Specification of the Bluetooth System, Bluetooth, Version 1.0B, vol. 2, Dec. 1, 1999. (remainder viewable at http://grouper.ieee.org/groups/802/15/Bluetooth/profile—10—b.pdf).
This is Ricochet Mobile Internet Access. Metricom, 1998.
What's Behind Ricochet: A Network Overview, Metricom. 2000.

References: application No. 09
 application No. 09
 application No. 09
 application No. 60
 application No. 60
 v.