WO2009067254A1 - System and method for operating mesh devices in multi-tree overlapping mesh networks - Google Patents
System and method for operating mesh devices in multi-tree overlapping mesh networks Download PDFInfo
- Publication number
- WO2009067254A1 WO2009067254A1 PCT/US2008/013022 US2008013022W WO2009067254A1 WO 2009067254 A1 WO2009067254 A1 WO 2009067254A1 US 2008013022 W US2008013022 W US 2008013022W WO 2009067254 A1 WO2009067254 A1 WO 2009067254A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mesh
- network
- hop
- mesh network
- message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D4/00—Tariff metering apparatus
- G01D4/002—Remote reading of utility meters
- G01D4/004—Remote reading of utility meters to a fixed location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/04—Interdomain routing, e.g. hierarchical routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/34—Source routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/64—Distributing or queueing
- H04Q3/66—Traffic distributors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y02B90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
- Y02B90/20—Smart grids as enabling technology in buildings sector
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S20/00—Management or operation of end-user stationary applications or the last stages of power distribution; Controlling, monitoring or operating thereof
- Y04S20/30—Smart metering, e.g. specially adapted for remote reading
Definitions
- serial number 61/025,270 entitled “Application Layer Device Agnostic Collector Utilizing Standardized Utility Metering Protocol Such As ANSI C 12.22,” filed January 31, 2008 (TR0031-PRO); serial number 61/025,276 entitled “System And Method For Real-Time Event Report Generation Between Nodes And Head End Server In A Meter Reading Network Including From Smart And Dumb Meters," filed January 31, 2008 (TR0032-PRO); serial number 61/025,282 entitled “Method And System for Creating And Managing Association And Balancing Of A Mesh Device In A Mesh Network,” filed January 31 , 2008 (TR0035-PRO); • serial number 61/025,271 entitled “Method And System for Creating And Managing Association And Balancing Of A Mesh Device In A Mesh Network,” filed January 31 , 2008 (TR0037-PRO);
- This invention pertains generally to methods and systems that allow a mesh device to participate in multiple mesh networks.
- a mesh network is a wireless network configured to route data between mesh device nodes within the network.
- a mesh network allows for continuous connections and reconfigurations around broken or blocked paths by retransmitting messages from node to node until a destination is reached.
- Mesh networks differ from other networks in that nodes can connect to each other via multiple hops. Thus, mesh networks are self-healing: the network remains operational when a node or a connection fails.
- Advanced Metering Infrastructure or Advanced Metering Management
- AMI Advanced Metering Infrastructure
- AMM Advanced Metering Management
- This infrastructure includes hardware, software, communications, customer associated systems and meter data management software.
- the infrastructure collects and distributes information to customers, suppliers, utility companies and service providers. This enables these businesses to either participate in, or provide, demand response solutions, products and services.
- Customers may alter energy usage patterns from normal consumption patterns in response to demand pricing. This improves system load and reliability.
- a mesh gate is an interface between the mesh network and a server over a wide area network (WAN).
- WAN wide area network
- Each mesh device may associate with a mesh network and a mesh gate, leaving the mesh network vulnerable to a failure in the mesh gate.
- Methods, systems, and devices described herein can allow a mesh device to participate in multiple mesh networks.
- a plurality of mesh devices can each associate with a mesh network, each mesh network managed by an access point.
- Mesh devices exchange neighbor information with neighboring mesh devices, including information about mesh devices associated with a different mesh network.
- Communication paths can include mesh devices of multiple mesh networks. This provides path diversity among mesh devices and improves bandwidth and reliability. In addition, this provides access diversity in case of mesh network or mesh gate failures.
- the mesh device can also be located on a boundary between two mesh networks and participate in both mesh networks. This provides path diversity among mesh devices and improves in-premise communication. In addition, this provides access diversity in case of a mesh gate failure.
- the mesh device may exchange neighbor information with nearby mesh devices of a different mesh network, thus allow a two-hop penetration into the neighboring mesh network.
- a method for a first mesh device to communicate in an overlapping mesh network environment comprises associating with a first access point over a first mesh network, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcast from a neighboring mesh device, updating a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determining a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmitting the message to the next device.
- a system for communicating in an overlapping mesh network environment comprises a plurality of access points, each access point managing a mesh network; and a plurality of mesh devices, each mesh device associated with a mesh network, wherein each mesh device is configured to: (i) responsive to receiving a neighbor information broadcast from a neighboring mesh device, update a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; (ii) responsive to a request to transmit a message to a destination, determine a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and (iii) transmit the message to the next device.
- a mesh device for communicating in an overlapping mesh network environment comprises a radio for communicating on a predetermined mesh network channel; a memory for storing a neighborhood table; a processor configured to: associate with a first access point over a first mesh network via the radio, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcasted from a neighboring mesh device, update the neighborhood table stored in the memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determine a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmit the message to the next device via the radio.
- a data structure defined in a computer readable medium comprises a plurality of entries, each of the plurality of entries representing at least one device and storing at least one characteristic of the device; and each of the plurality of entries including a plurality of fields for storing characteristics of at least one neighboring device.
- a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; and forwarding a message from the one-hop mesh device to the first mesh network.
- a method comprises associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
- a device comprises a neighborhood table, the neighborhood table storing mesh network device information; and a radio configured to communicate with a first mesh network and a second mesh network, wherein the device is configured to, in operation, associate with a first mesh gate over the first mesh network, exchange neighbor information stored in the neighborhood table with an accessible same-network mesh device over the first mesh network, detect an accessible one-hop mesh device on the second mesh network, exchange neighbor information stored in the neighborhood table with the one-hop mesh device, and forward a message from the one-hop mesh device to the first mesh network.
- a computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; and forwarding a message from the one-hop mesh device to the first mesh network.
- a computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method comprises associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
- a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; forwarding a message from the one-hop mesh device to the first mesh network; associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
- a computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; forwarding a message from the one-hop mesh device to the first mesh network; associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
- FIG. IA illustrates a system for providing communications in an AMI system, according to an exemplary embodiment.
- FIG. IB illustrates a system for providing communications in an AMI system, according to another exemplary embodiment.
- FIG. 2A illustrates a mesh device for use within a mesh network, according to an exemplary embodiment.
- FIG. 2B illustrates a mesh gate for use within a mesh network, according to an exemplary embodiment.
- FIG. 3 illustrates a network stack for use within a mesh radio, according to an exemplary embodiment.
- FIG. 4 illustrates a process for a mesh device to communicate in a multi-mesh network environment, according to an exemplary embodiment.
- FIG. 5A illustrates a data structure for storing a neighborhood table, according to an exemplary embodiment.
- FIG. 5B illustrates a data entry for storing neighborhood table information, according to an exemplary embodiment.
- FIG. 6A illustrates a process for a zero-hop device to forward communications between a first mesh network and a second mesh network, according to an exemplary embodiment.
- FIG. 6B illustrates a process for a one-hop device to forward communications between a first mesh network and a second mesh network, according to an exemplary embodiment.
- FIG. IA illustrates an exemplary system for providing communications in an AMI system 100.
- the AMI system may include a plurality of mesh networks, such as mesh network A 102 and mesh network B 104. While only two mesh networks are depicted, any number of mesh networks may exist in the AMI system.
- Mesh network A 102 includes a mesh gate A 106 and mesh devices A 110, B 112, C 114, D 116 and E 118.
- Mesh network B 104 includes mesh gate B 108 and mesh devices U 120, V 122, W 124, X 126, Y 128 and Z 130.
- the mesh devices A 110, B 112, and C 114 may perform required functions within the mesh network A 102.
- a mesh device may be a meter, a user interface such as for example a thermostat, an output device such as a utilities usage display, or any other device or subsystem required or benefited by the AMI system.
- the mesh gate 106 and the mesh devices function as nodes in the mesh network, which dynamically creates and maintains links between the nodes. Each mesh device may transmit messages to the mesh gate A 106 and other mesh devices within the mesh network A 102. Only mesh devices A 110 and C 114 are in direct communication with the mesh gate A 106.
- a mesh gate may also be referred to as an access point or a Neighborhood Area Network to Wide Area Network (NAN- WAN) gate.
- the mesh gate may perform any one or more of many different functions including, for example, but not limited to, one or any combination of: relaying information from a server (such as to a head end server) to the mesh network nodes, routing information, aggregating information from the nodes and microportals within any sub-network that may be configured for transmission to a server (such as to the head end server), acting as a home area network (HAN) sometimes also referred to as a premise area network (PAN) coordinator, acting as a NAN- WAN gate, transmitting firmware upgrades, and/or multicasting messages.
- HAN home area network
- PAN premise area network
- the mesh gate may also be referred to as a collector because it collects information from the NAN-associated nodes or other nodes and/or microportals in its subnetwork.
- a mesh gate may include a mesh radio to communicate with mesh devices over the mesh network and a WAN communication interface to communicate with the server over the WAN 131.
- the mesh gate A 106 may provide a gateway between the mesh network A 102 and a server 132.
- the server 132 can also act as a head end.
- the server 132 can provide services to mesh devices within the AMI system, such as commissioning devices, providing software updates, providing metering pricing updates, receiving metering information, etc.
- the mesh gate A 106 may aggregate information from mesh devices (e.g., meters) within the mesh network and transmit the information to the server 132.
- the mesh gate A 106 may further forward messages from the mesh devices to the server 132, for example, status reports and meter readings.
- the mesh gate A 106 may further forward messages from the server 132 to the mesh devices, for example, instructions and queries.
- the server 132 may be a computing device configured to receive information, such as meter readings, from a plurality of mesh networks and meters.
- the server 132 may also be configured to transmit instructions to the mesh networks, mesh gates, and meters. It will be appreciated that while only one server is depicted, any number of servers may be used in the AMI system. For example, servers may be distributed by geographical location. Redundant servers may provide backup and failover capabilities in the AMI system.
- the mesh devices may also exchange neighbor information with neighboring mesh devices from another mesh network. Neighbor information may for example include one or more of mesh device identifiers, a signal quality indicator or value, a distance to mesh gate indicator or value, and any other information necessary or advantageous to calculate a route from the mesh device. In one embodiment, the neighbor information includes each of these information items.
- the mesh devices may exchange neighbor information with each other, where the neighbor information is propagated throughout the mesh network and used to determine a best path to the mesh gate.
- mesh device A 110 knows it is a neighbor of the mesh gate. It will send the information to mesh device D 116, which then knows that in order to send a message to the mesh gate, it may ask mesh device A 110 to forward the message.
- the mesh gate A 106 can manage the mesh network A 102 by maintaining an association (registration) table which can include information about in-network and out of network nodes and a neighborhood table which includes information about the nodes in the network and their neighbors (which may include out of network nodes) and other information for each mesh device within the mesh network A 102.
- a mesh device association can include a registration for application service at the mesh gate A 102 or the server 132.
- the mesh gate A 102 and the server 132 can maintain a table of available applications and services and requesting mesh devices. More particularly, an exemplary neighborhood table is structured as described with respect to Tables 1 and 2 below:
- the mesh network B 104 may similarly include a mesh gate B 108 and at least one mesh device.
- the mesh network B 104 may neighbor or be adjacent to the mesh network A 102 and therefore some of the mesh devices of mesh network B 104 may be in radio transmit/receive range of mesh devices of the mesh network A 102.
- the mesh networks may overlap and therefore provide path diversity among the mesh devices.
- device Y 128 is a thermostat and needs to transmit a message to device E 118, such as a utilities control unit, it is not necessary to transmit the instruction to mesh gate B 108 via mesh network B 104, which is then transmitted to mesh gate A 106 via a WAN 131, which is then transmitted to the device E 118 via mesh network A 102.
- device Y 128 receives neighbor information from device E 118 and realizes they are neighbors. Direct communication between the mesh devices is possible.
- the mesh devices can utilize other accessible mesh gates as a secondary mesh gate in case of failure by the primary mesh gate with which the mesh device is associated.
- mesh devices of mesh network B 104 may transmit messages to mesh gate A 106 if mesh gate B 108 fails to respond.
- neighboring mesh networks can operate on different channels or radio frequencies. This can improve wireless bandwidth within a mesh network and decrease interference from neighboring mesh network transmissions.
- the channels or radio frequencies can be predetermined.
- a mesh device can allow penetration of any number of hops into a neighboring mesh network.
- a path of each mesh device forwarding a message can be stored in the message header, a path length can be limited by a size of the message header. In one example embodiment, the path length can be limited to nine hops, thus allowing a penetration of nine-hops into neighboring mesh networks.
- the mesh devices D 116 and E 118 may function as zero-hop devices.
- Zero-hop devices may be on the boundary of the mesh network, with children nodes that are mesh devices belonging to a second mesh network.
- Zero- hop devices may communicate with the mesh gate directly or through intermediate mesh devices.
- the mesh device D 116 may reach the mesh gate A 106 via mesh device A 110.
- the mesh device E 118 may reach the mesh gate A 106 via mesh device C 114.
- the neighborhood tables of zero-hop devices may include neighbors within mesh network A 102 as well as mesh network B 104.
- the mesh devices Y 128 and Z 130 may function as one-hop devices.
- One-hop devices may be on the boundary of the mesh network B 104 and be neighbors with zero-hop devices of mesh network A 102. Thus, one-hop devices may communicate with the associated mesh gate B 108 or with mesh gate A 106 via the zero-hop devices.
- the neighborhood tables of one-hop devices may include neighbors within mesh network B 104 as well as mesh network A 102.
- the mesh devices W 124 and X 126 may function as two-hop devices. Two-hop devices may be neighbors with one-hop devices, and therefore are two hops away from a neighboring mesh network. Thus, two-hop devices may communicate with the associated mesh gate B 108 or with mesh gate A 106 via the one-hop and zero-hop devices as well as mesh network A 102.
- the mesh devices U 120 and V 122 may not include information on mesh devices of mesh network A 102 in neighborhood tables. However, messages may be forwarded to two-hop devices for forwarding to mesh network A 102.
- the one-hop and two-hop devices may utilize mesh gate A 106 as a secondary mesh gate in case of failure by mesh gate B 108. Over time, mesh device U 120 and mesh device V 122 may re-associate with a new mesh gate, but the one-hop and two-hop devices may utilize their secondary mesh gate immediately and suffer no downtime.
- mesh devices may also serve as conduits between two networks. For example, in FIG. IB, system 150 includes conduit device J 172 associated with mesh network C 160 and mesh network D 162. Mesh network C 160 includes device G 168, device H 170, and mesh gate C 164.
- Mesh network D 162 includes device K 174, device L 176, and mesh gate D 166.
- the mesh networks, mesh gates, and mesh devices shown in FIG. IB are merely representative and alternate systems may include additional numbers and arrangements of mesh networks, mesh gates, and mesh devices.
- the mesh devices illustrated in FIG. IB can serve a variety of functions and may be, for example, meters, thermostats, output devices such as displays, or any other device or subsystem required or benefited by the AMI system.
- Mesh gate C 164 and mesh gate D 162 communicate with server 180 via WAN 178. Except for mesh device J 172, the mesh devices and mesh gates can operate in a similar fashion to those mesh gates and mesh devices illustrated and described in connection with FIG. IA.
- mesh device J 172 this device may associate with mesh network C 160 and mesh network D 162 and act as a conduit between the two networks.
- Mesh device J 172 may allow mesh devices and mesh gates in one network to communicate with mesh devices and mesh gates in the other network. For example, if mesh gate C 164 was not available to receive communications from mesh devices in mesh network C 160, mesh device H 170 may communicate a message to mesh gate D 166 via mesh device J 172.
- Mesh device J 172 may be similar to the other mesh devices illustrated in FIG. IB except that it may have additional software allowing it to serve as a conduit between the two networks.
- FIG. 2A illustrates an exemplary mesh device 200 for use within a mesh network.
- Mesh device 200 may include a radio 202, a communication card 204, a metering sensor 206, and a battery or other power or energy storage device or source 208.
- the radio 202 may include a memory 210, a processor 212, a transceiver 214, and a microcontroller unit (MCU) 216 or other processor or processing logic.
- MCU microcontroller unit
- the mesh device 200 can be any device configured to participate as a node within a mesh network.
- Mesh device 200 can be a mesh repeater, which can be a wired device configured to retransmit received mesh transmissions.
- the mesh repeater can extend over a range of a mesh network and provide mesh network functionality to mesh devices that enter sleep cycles.
- the mesh device 200 may communicate with a mesh gate and other mesh devices over a mesh network.
- the mesh device 200 may be a gas, water, electricity, or other utility meter installed in a residential, commercial, or industrial building or other location to monitor utilities usage.
- the mesh device 200 may also control access to utilities on receipt of instructions such as instructions or control signals received from a server, for example, by reducing or stopping the flow of gas, water or electricity.
- the mesh device 200 may be a mobile asset that needs to be tracked by the AMI system.
- the radio 202 may be a mesh radio configured to communicate with a mesh network.
- the radio 202 may transmit, receive, and forward messages to the mesh network. Any meter within the mesh network may thus communicate with any other meter or mesh gate by communicating with its neighbor and requesting a message be forwarded.
- the radio 202 may also communicate with an off-network device not associated with the mesh network.
- the communication card or circuit 204 may interface between the radio and the sensor. Sensor readings or other data may be converted to radio signals for transmission over the radio.
- the communication card 204 may optionally but advantageously include encryption/decryption functionality or other security measures to protect the transmitted data.
- the communication card 204 may also decode instructions received from the server.
- the optional metering sensor 206 may be a gas, water, electricity, media content or information meter sensor, or another sensor.
- digital flow sensors may be used to measure a quantity of water or gas flowing into a residence or building.
- the sensor 206 may be an electricity meter configured to measure a quantity of electricity flowing over a power line.
- the optional metering sensor 206 may be replaced by another component for performing functions within the AMI system.
- the mesh device may provide a user interface, such as a thermostat or other utilities control or display.
- the metering sensor may be replaced with a thermostat interface.
- the mesh device may provide a display screen, such as an LCD display screen that displays information for the user.
- the mesh device may be a simple repeater for extending the range of the mesh network. In this example, the mesh device may simply receive and re-transmit mesh transmissions on the mesh network.
- the battery or other energy storage device 208 may be configured to independently power the mesh device 200 during a power outage.
- the battery 208 may be a large capacitor storing electricity to power the mesh device 200 for at least five minutes after a power outage.
- Small compact but high capacity capacitors known as super capacitors are known in the art and may advantageously be used.
- One exemplary super capacitor is the SESSCAP 50f 2.7v 18x30mm capacitor manufactured by NESSCAP Co., Ltd. of Wonchun-Dong 29-9, Paldal-Ku, Soowon, Kyonggi-Do 442-380, Korea.
- Alternative battery technologies may be used, for example, galvanic cells, electrolytic cells, fuel cells, flow cells, and voltaic cells.
- the memory 210 may store instructions and run-time variables for execution.
- the memory 210 may include both volatile and non- volatile memory.
- the memory 210 may also store a history of sensor readings from the metering sensor 206 and an incoming queue of server instructions.
- the mesh device 200 may also include a memory in additional to memory 210.
- a neighborhood table may be stored in a memory accessible by the mesh device 200.
- the neighborhood table may store a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field.
- the neighborhood table information may be transmitted to other mesh devices in a neighbor exchange and may also be transmitted to a mesh gate.
- the neighborhood table may be used to determine a best route on the mesh network for a message to be transmitted. Alternatively, the neighborhood table can include other fields.
- Information from the neighborhood table can be used to calculate a path to an access point.
- a calculated path can have a good connection to a mesh gate as defined by signal quality, number of hops, and a mesh gate load. It will be appreciated that various weightings can be used to compute a calculated path value, and a best valued path is selected for use.
- the processor 212 may execute instructions, for example, stored in the memory.
- Instructions stored in memory 210 may be ordinary instructions, for example, provided at time of meter installation, or special instructions received from the server during run time.
- the transceiver 214 may transmit to and receive from a mesh network wireless signals.
- the transceiver 214 may be configured to transmit sensor readings and status updates under control of the processor.
- the transceiver 214 may receive server instructions from a server, which are communicated to the memory and the processor.
- the MCU 216 can execute firmware or software required by the mesh device 200.
- the firmware or software can be installed at manufacture or via a mesh network over the radio 202.
- any number of MCUs can exist in the mesh device 200.
- two MCUs can be installed, a first MCU for executing firmware handling communication protocols, and a second MCU for handling applications.
- a mesh device and a mesh gate can share the architecture of mesh device 200.
- the radio 202 and the MCU 216 provide the necessary hardware, and the
- MCU 216 executes any necessary firmware or software.
- Each component may be modular and configured for easy removal and replacement.
- Meters may be located in geographically dispersed locations within an AMI system.
- a meter may be located near a gas line, an electric line, or a water line entering a building or premise to monitor a quantity of gas, electricity, or water flowing through the line.
- the meter may communicate with other meters, even with meters of different types, and mesh gates through a mesh network.
- the meter may transmit meter readings and receive instructions via the mesh network.
- the mesh device 200 may communicate over a mesh network and directly with an off-network device via the radio 202.
- the communication card or circuit 204 may interface between the metering sensor 206 and the radio 202.
- sensor readings may be transmitted to and instructions received from a server.
- the mesh device 200 may participate in the mesh network by forwarding any messages that require forwarding to a next mesh device on a dynamically determined or pre-determined path.
- mesh devices may be similar to meters except the metering sensor is replaced by whatever component is necessary to perform the mesh device's function.
- a user display may include an output screen or set of indicator lights.
- a thermostat may include a dial or other user interface or mechanism for receiving user input and an analog/digital converter to produce an input signal.
- FIG. 2B is a block diagram that illustrates an exemplary mesh gate 230 for use within a mesh network.
- the mesh gate 230 may include a mesh radio 232, a wide area network interface
- the mesh radio 232 may include a memory 242, a processor 244, and a transceiver 246.
- the mesh gate 230 may interface between mesh devices such as meters over a mesh network and a server over a WAN.
- the mesh gate 230 may be installed in a central location relative to the meters and also communicate with a server over a WAN.
- the mesh radio 232 may be a mesh radio configured to communicate with meters over a mesh network.
- the radio 232 may transmit, receive, and forward messages to the mesh network.
- the WAN interface 234 may communicate with a server over a WAN.
- the WAN may be a cellular network, a private network, a dial up connection, or any other network.
- the WAN interface 234 may optionally include encryption/decryption functionality or other security measures to protect data being transmitted to and from the server.
- the battery or other energy or power source 236 may be configured to independently power the mesh gate 230 during a power outage.
- the battery 236 may be a large capacitor storing electricity to power the mesh gate 230 for at least five minutes after a power outage. While not limitations of embodiments of the invention, a capacitor may advantageously be used in a meter that may have access to a power source such as an electric utility meter, and a battery may be a more suitable power source for a gas meter which may not frequently be connected to a continuous or even intermittent source of power or energy.
- the processor or processing logic 238 may control the mesh radio 232 and the WAN interface 234. Meter information received from the meters over the mesh radio 232 may be compiled into composite messages for transmission to the server. Server instructions may be received from the WAN interface 234 and transmitted to meters in the mesh network for execution. Server instructions may also be received from the WAN interface 234 for execution by the processor 238.
- the mesh radio 232, WAN interface 234, battery 236, and processor 238 may be modular and configured for easy removal and replacement. This facilitates component upgrading over a lifetime of the mesh gate 230.
- an accessible memory of each mesh device may store neighbor information for all mesh devices within the mesh network (and within communication range of the mesh device regardless of association with a specific mesh network) and associated with the mesh device.
- the neighborhood table information may be exchanged between mesh devices and also transmitted to the mesh gate.
- the mesh gate may be configured to calculate various routing based on the compiled neighborhood table.
- the memory 242 of the mesh radio 232 may store instructions and run-time variables of the mesh radio 232.
- the memory 242 may include both volatile and non- volatile memory.
- the memory 242 may also store a history of meter communications and a queue of incoming server instructions.
- meter communications may include past sensor readings and status updates.
- the mesh gate may include an additional memory configured to store values in the execution of mesh gate functions. For example, a history of meter readings or status updates may be stored for future retrieval.
- the processor 244 of the mesh radio 232 may execute instructions, for example, stored in memory 242. Instructions stored in memory 242 may be ordinary instructions, for example, provided at time of mesh gate installation, or special instructions received from the server during run-time.
- the transceiver 246 of the mesh radio 232 may transmit and receive wireless signals to a mesh network.
- the transceiver 246 may be configured to receive sensor readings and status updates from a plurality of meters in the mesh network.
- the transceiver 246 may also receive server instructions, which are communicated to the memory 242 and the processor 244.
- the mesh gate may interface between a mesh network and a server.
- the mesh gate may communicate with meters in the mesh network and communicate with the server over a WAN network. By acting as a gateway, the mesh gate forwards information and instructions between the meters in its mesh network and the server.
- the mesh gate may also function as a node within the mesh network, by forwarding messages between mesh devices.
- FIG. 3 illustrates an exemplary network stack for use within a mesh radio 300.
- the application process 302 may communicate with an application layer 304, a transport layer 306, a network layer 308, a data link layer 310 and a physical layer 312.
- the radio 300 may be a mesh radio installed in a mesh gate, a mesh device, or an off- network device.
- the radio 300 may be a component in a meter, a mesh gate, or any other mesh device configured to participate in a mesh network or communicate with other mesh devices.
- the radio 300 may be configured to transmit wireless signals over a predetermined or dynamically determined frequency to other radios.
- the application process 302 may be an executing application that requires information to be communicated over the network stack.
- the application process 302 may be software supporting an AMI system, such as software or firmware executing in some processor or processing logic on an electricity meter or a mesh gate.
- the application layer 304 interfaces directly with and performs common application services for application processes. Functionality may include semantic conversion between associated application processes.
- the application layer may be implemented as ANSI C 12.12/22, which standard as of the filing date of this application is hereby incorporated by reference.
- the transport layer 306 responds to service requests from the application layer and issues service requests to the Internet layer. It delivers data to the appropriate application on the host computers.
- the layer may be implemented as TCP (Transmission Control Protocol), and UDP (User Datagram Protocol), or according to other known or convenient protocols.
- the network layer 308 is responsible for end to end (source to destination) packet delivery.
- the network layer's functionality may advantageously include transferring variable length data sequences from a source to a destination via one or more networks while maintaining the quality of service, and error control functions. Data will be transmitted from its source to its destination, even if the transmission path involves multiple hops or relays.
- the network layer 308 may translate a short address into a network address.
- a short address may for example be a two byte address used to identify mesh devices within a mesh network.
- the short address may be assigned by the access point.
- a network address may be an eight byte unique address used to identify the mesh device from among other mesh devices.
- the network address may be assigned at manufacture or by a server. Short addresses may be used within a mesh network to shorten messages that are addressed to another mesh device within the same mesh network. Long addresses may be used to address mesh devices of another mesh network or whose short address is not known to a message sender.
- the data link layer 310 transfers data between adjacent network nodes in a network, wherein the data is in the form of packets.
- the layer provides functionality including transferring data between network entities and error correction/detection.
- the layer may be implemented as IEEE 802.15.4, which standard as of the filing date of this application is hereby incorporated by reference.
- the physical layer 312 may be the most basic network layer, transmitting bits over a data link connecting network nodes. No packet headers or trailers are included.
- the bit stream may be grouped into code words or symbols and converted to a physical signal, which is transmitted over a transmission medium, such as radio waves.
- the physical layer provides an electrical, mechanical, and procedural interface to the transmission medium.
- the layer may be implemented as IEEE 802.15.4.
- the network stack provides different levels of abstraction for programmers within an AMI system. Abstraction reduces a concept to only information which is relevant for a particular purpose. Thus, each level of the network stack may assume the functionality below it on the stack is implemented. This facilitates programming features and functionality for the AMI system.
- the illustrated network stack may facilitate intra-mesh network communication by utilizing a short address to identify addressees.
- FIG. 4 illustrates an exemplary process 400 for a mesh device to communicate in a multiple mesh network environment. It should be understood that process 400 and the other exemplary processes described herein may be performed in different sequences or certain steps may be performed in parallel in alternate embodiments.
- the procedure may execute on a mesh device associated with a first mesh network and within radio range of neighboring mesh devices, some of which are associated to a second mesh network. The procedure may allow mesh devices of the two mesh networks to communicate amongst each other and provide network overlap.
- the mesh device can associate with a first access point. Recall that an access point may also be referred to as mesh gate or a NAN- W AN gate. Associating with the first access point includes transmitting an association request to the first access point and awaiting a confirmation. If the first access point is not within radio range of the mesh device, the message is transmitted via a mesh network.
- the mesh network includes neighboring mesh devices, as shown in FIG. 1, which can forward the association request towards the access point.
- the neighboring mesh devices will also forward the confirmation back to the mesh devices.
- the association can happen periodically after a predetermined or dynamically determined time interval or according to some other policy, at a mesh device start up, or when communication with the first access point is lost. If there is no neighboring mesh device associated with the first mesh network within radio range, the mesh device can retry association after a predetermined or dynamically determined time interval or according to some other policy.
- the mesh device can test whether neighbor information has been received.
- neighboring mesh devices will periodically broadcast mesh device information and neighbor information.
- Neighbor information may include one or any combination of mesh device identifiers, signal strength, distance from access point, and other information helpful in determining a path through a mesh network.
- the neighbor information includes each of these.
- step or process 406 If neighbor information is received, the mesh device proceeds to step or process 408.
- the neighbor information will include preferred routes over a plurality of mesh networks to various destinations.
- the mesh device can update a neighborhood table in accessible memory.
- the mesh device can be configured with an accessible memory which stores a neighborhood table.
- the neighborhood table stores mesh device information and neighbor information of neighboring mesh devices.
- Filters can be used to restrict a size of the neighborhood table.
- the neighborhood tables can be configured to only store mesh device information of mesh devices within a predetermined number of hops from the mesh device or have specified signal quality.
- the mesh device can test whether a message transmit request has been received.
- the message transmit request can be received from the mesh device when a message must be sent via the mesh network.
- the message can be intended for a server, the first access point, or another mesh device.
- the message transmit request can be received from a received message.
- the received message can be received from a neighboring mesh device for transmitting.
- a message destination will be included in the received message, which is parsed by the mesh device.
- the mesh device If no transmit message request is received, the mesh device returns to step or process 404.
- the mesh device can determine a next device on a path to the destination.
- the next device can be the destination of the message, such as a neighboring mesh device or an access point within radio range. Alternatively, the next device can be the neighboring mesh device to which the mesh device must transmit the message for forwarding.
- the destination is a server or another device not on the mesh network, the message can be received by an access point or another device configured to interface between the mesh network and the off-mesh network device.
- the next device can be determined from a next device table stored in accessible memory, where the mesh device stores a list of destinations and a next device associated with each destination.
- the next device can be calculated by the first access point and stored in the next device table.
- the next device can be calculated by the mesh device as required.
- the mesh device can transmit the message to the next device.
- the message can be broadcast on a radio channel used by the mesh network and addressed to the next device by including a next device identifier in a message header. All other mesh devices will ignore the message because they are not the next device and thus not required to receive and forward the message.
- the mesh device can optionally detect whether there is a problem mesh network within communication range.
- a problem mesh network can be a mesh network whose bandwidth usage is near or at its limit and cannot service requests from outside the mesh network.
- step or process 416 If a problem mesh network is detected, the mesh device proceeds to step or process 416.
- the mesh device proceeds to step or process 418.
- the mesh device can optionally delete entries related to the problem mesh network from the neighborhood table. Because each entry in the neighborhood table includes a network identifier, all entries associated with the problem mesh network can be easily located and deleted.
- the mesh device can optionally test whether a neighbor information request has been received.
- the neighbor information request can be triggered at a predetermined time by the mesh device.
- a randomizing component can be added to the predetermined time so that not all neighboring mesh devices attempt to broadcast neighbor information at the same time.
- the neighbor information request can be received over the mesh network.
- the first access point can periodically initiate neighbor information exchanges by transmitting neighbor information requests to each mesh device within its mesh network.
- the mesh device proceeds to step or process 420. If no neighbor information request has been received, the mesh device proceeds to step or process 422.
- the mesh device can optionally broadcast neighbor information.
- the neighbor information can be retrieved from the neighborhood table and include information as discussed above.
- step or process 422 the mesh device can exit the procedure. It will be appreciated the procedure can be repeatedly executed by the mesh device while powered.
- FIG. 5A illustrates an exemplary data structure 500 for storing a neighborhood table.
- the data structure can be stored in accessible memory on a mesh device or an access point.
- the data structure 500 includes entries 502, each data entry 502 representing a mesh device and mesh device characteristics.
- FIG. 5B illustrates an exemplary data entry 502 for storing neighborhood table information.
- the data entry 502 may include one or include a plurality of fields for storing characteristics of a neighboring device, some of which fields may be optional.
- a tree PAN identifier 504 may be provided and can be a binary two byte data field for identifying a network tree associated with the mesh device.
- the tree PAN identifier 504 can refer to foreign networks.
- a neighbor address 506 may be provided and can be a binary two byte data field for identifying an address of the mesh device.
- a neighbor PAN identifier 508 may be provided and can be a binary two byte data field for identifying a membership of the mesh device.
- An average quality 510 may be provided and can be an unsigned 8-bit data field for specifying an average quality of the mesh device's path to an access point.
- a number of hops 512 may be provided and can be an unsigned 8-bit data field for specifying a number of hops between the mesh device and an access point.
- a minimum quality 514 may be provided and can be an unsigned 8-bit data field for specifying a minimum quality of the mesh device's path to an access point.
- a freshness indicator 516 may be provided and can be an unsigned 8-bit data field for specifying how recently the mesh device information was received.
- FIG. 6A illustrates an exemplary process 600 for a zero-hop mesh device to forward communications between a first mesh network and a second mesh network.
- the procedure may execute on a mesh device on the border of a first mesh network and within radio range of a mesh device of a second mesh network.
- the procedure may allow mesh devices of the two mesh networks to communicate and provide network overlap.
- the zero-hop device may be a mesh device associated with the first mesh network but storing neighbor information of at ieast one one-hop device associated with the second mesh network. Thus, the zero-hop device may facilitate communications between the first mesh network and the one-hop device.
- the mesh device may associate with a first mesh gate.
- the mesh device may execute a search routine on power-up or when communication with an associated mesh gate is lost.
- the mesh device may search for nearby mesh gates and select one for association based on a variety of factors such as signal strength, number of hops to the mesh gate, and mesh gate load.
- the mesh device may transmit an association request to the mesh gate via the mesh network and receive an acknowledgement.
- the mesh device may participate in the first mesh network as a node and communicate with a server over a WAN via the mesh gate. It may also communicate with other mesh devices in the mesh network.
- the mesh device may exchange neighbor information with one or more same-network mesh devices.
- neighbor information may include a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field.
- the neighbor information may be compiled by the mesh device for every neighboring mesh device with which it is in communication, and used to determine a path for messages to be transmitted.
- the exchange of neighbor information may occur at a pseudo-random periodic interval, for example, once every hour at a random time. This allows all mesh devices in the mesh network to exchange neighbor information and build up a stored neighbor information table.
- the zero-hop mesh device may test whether a one-hop mesh device is accessible.
- the one-hop mesh device may be associated with a second mesh network and communicate on a second mesh radio channel.
- the mesh device may scan alternate mesh radio channels until an accessible one-hop mesh device is found.
- the mesh networks may communicate on different frequencies. If an accessible one- hop mesh device is not found, the mesh device may assume no one-hop mesh devices are within radio range and wait a time-out period before re-testing.
- the procedure may proceed to 604 and continue functioning as a node in the first mesh network.
- the zero-hop mesh device may periodically check whether a one-hop mesh device has become accessible.
- the zero-hop mesh device may exchange neighbor information with the one-hop mesh device.
- the neighbor information may be compiled from neighbor information exchanges as discussed above.
- the neighbor information may include, in addition to the contents discussed above, a mesh network identifier for each mesh device indicating the mesh devices are associated with the first mesh network.
- the mesh device may receive a message for forwarding from the one-hop mesh device.
- the one-hop device may desire to transmit a message to a neighbor of the zero-hop device on the first network. Instead of transmitting the message to the mesh gate associated with the second mesh network, forwarding the message to the mesh gate associated with the first mesh network over the WAN, and forwarding the message to the correct mesh device, the one-hop device may request the zero-hop device forward the message. This reduces network load and improves network performance.
- the message may be addressed to a server.
- the one-hop mesh device may lose communications with its associated mesh gate.
- the one-hop mesh device may transmit the message to the zero-hop device for forwarding to the associated mesh gate via the first mesh network.
- the procedure may remain in process or step 610.
- the zero-hop mesh device may continue to function as a node within the first mesh network and periodically check whether a message has been received from the one-hop mesh device for forwarding on the first mesh network.
- the zero-hop mesh device may optionally transmit a status to a server.
- the status may include neighbor information including the one-hop mesh devices.
- the neighbor information may allow the server to better route message traffic considering the mesh network overlap between the first mesh network and the second mesh network.
- the zero-hop mesh device may optionally test whether a response has been received from the server. For example, the message forwarded on behalf of the one- hop mesh device may require a response from the recipient, whether a mesh device within the first mesh network or the server. The response may be transmitted to the zero-hop mesh device via the first mesh gate and the first mesh network.
- the server may transmit the message to the mesh device when the mesh gate associated with the one-hop mesh device has failed. This provides path diversity in case of mesh gate failure.
- the mesh device may optionally forward the received response to the one-hop mesh device.
- the mesh device may check that the one-hop mesh device is in its neighborhood table and forward the message to the one-hop mesh device. If the second mesh network is on a different mesh radio channel or frequency, the mesh device may utilize the correct mesh radio channel or frequency. For example, the second mesh network mesh radio channel or frequency may be stored in the neighbor information.
- the mesh device may optionally exchange neighbor information with a third mesh network one-hop device. Similar to the second mesh network one-hop device, the mesh device may attempt to detect and exchange neighbor information with a one-hop mesh device on a third mesh network. This creates a network overlap between the first and third mesh networks. In addition, the third mesh network one-hop device may also reach the second mesh network one-hop device via the zero-hop mesh device.
- the zero-hop mesh device may optionally forward a message from the third mesh network one-hop device to the first mesh network. Similar to the second mesh network one-hop device, the zero-hop mesh device may receive messages from the third mesh network one-hop device and forward the message to the first mesh network, and possibly the first mesh gate and the server.
- any number of one-hop mesh devices from any number of mesh networks may be supported within the first mesh network, limited only by the radio range and memory capacity of the mesh device. This creates path diversity and network overlap between the mesh networks.
- the mesh device may interface between the first mesh network and at least one one-hop mesh device.
- the one-hop mesh device may be associated with another mesh network and mesh gate. By providing an interface between the first mesh network and the one- hop mesh device, network overlap is created and path diversity is provided. This improves mesh network performance and reduces WAN load by allowing mesh network-level communications between mesh networks, instead of requiring all such communications to be forwarded through the WAN.
- FIG. 6B illustrates an exemplary process 650 for a one-hop device to forward communications between a first mesh network and a second mesh network.
- the procedure may execute on a mesh device on the border of a second mesh network and within radio range of a mesh device of a first mesh network.
- the procedure may allow mesh devices of the two mesh networks to communicate and provide network overlap.
- a one-hop device may be a mesh device associated with the second mesh network and storing neighbor information of at least one zero-hop mesh device associated with the first mesh network.
- the one-hop device may facilitate communications between the second mesh network and the zero-hop mesh device.
- the one-hop mesh device may associate with a second mesh gate.
- the one-hop mesh device may execute a search routine on power-up or when communication with an associated mesh gate is lost.
- the one-hop mesh device may search for nearby mesh gates and select one for association based on a variety of factors such as signal strength, number of hops to the mesh gate, and mesh gate load.
- the one-hop mesh device may transmit an association request to the mesh gate via the mesh network and receive an acknowledgement.
- the one-hop mesh device may participate in the second mesh network as a node and communicate with a server over a WAN via the second mesh gate. It may also communicate with other mesh devices in the second mesh network.
- the one-hop mesh device may exchange neighbor information with a two-hop mesh device.
- the two-hop mesh device may be a mesh device within the second mesh network that is one hop further from the second mesh network border.
- the two-hop mesh device may be a parent of the one-hop mesh device.
- Neighbor information may include a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field.
- the neighbor information may be compiled by the one-hop mesh device for every neighboring mesh device with which it is in communication, and used to determine a path for messages to be transmitted.
- the neighbor information may occur at a pseudo-random periodic interval, for example, once every hour at a random time. This allows all mesh devices in the mesh network to exchange neighbor information and build up a stored neighbor information table.
- the one-hop mesh device may test whether a zero-hop mesh device is accessible.
- the zero-hop mesh device may be associated with a first mesh network and communicate on a first mesh radio channel.
- the one-hop mesh device may scan alternate mesh radio channels until an accessible zero-hop mesh device is found.
- the mesh networks may communicate on different frequencies. If an accessible zero- hop mesh device is not found, the mesh device may assume no zero-hop mesh devices are within radio range and wait a time-out period before re-testing.
- the procedure may proceed to process or step 658. If a zero-hop mesh device is not accessible, the procedure may proceed to process or step 654 and continue functioning as a node in the second mesh network.
- the one-hop mesh device may periodically check whether a zero-hop mesh device has become accessible.
- the one-hop mesh device may exchange neighbor information with the zero-hop mesh device. For example, the neighbor information may be compiled from neighbor information exchanges as discussed above.
- the neighbor information may include, in addition to the contents discussed above, a mesh network identifier for each mesh device indicating the mesh devices are associated with the second mesh network.
- the one-hop mesh device may receive a message for forwarding to the zero-hop mesh device.
- the one-hop mesh device may desire to transmit a message to a neighbor of the zero-hop device on the first network.
- the one-hop device may request the zero-hop device forward the message. This reduces network load and improves network performance.
- the message may be addressed to a server.
- the one-hop mesh device may lose communication with its associated mesh gate.
- the one-hop mesh device may transmit the message to the zero-hop device for forwarding to the associated mesh gate via the first mesh network.
- the message may be received from a two-hop mesh device for forwarding to the first mesh network.
- the two-hop mesh device may be a parent of the one-hop mesh device on the second mesh network and desire to transmit a message to the first mesh network.
- the one-hop and zero-hop mesh devices may forward the message to the first mesh network.
- the procedure may proceed to process or step 662. If no message is received for forwarding, the procedure may remain in process or step 660.
- the one-hop mesh device may continue to function as a node within the second mesh network and periodically check whether a message has been received from the two-hop mesh device for forwarding to the first mesh network.
- the one-hop mesh device may optionally transmit a status to a server via the zero-hop mesh device.
- the status may include neighbor information including the two-hop mesh devices.
- the neighbor information may allow the server to better route message traffic considering the mesh network overlap between the first mesh network and the second mesh network.
- the one-hop mesh device may optionally test whether a response has been received from the server. For example, the message forwarded on behalf of the two- hop mesh device may require a response from the recipient, whether a mesh device within the first mesh network or the server. The response may be transmitted to the mesh device via the zero-hop mesh device.
- the server may transmit the message to the mesh device when the second mesh gate has failed. This provides path diversity in case of mesh gate failure.
- the one-hop mesh device may optionally forward the received response to the two-hop mesh device.
- the one-hop mesh device may check that the two-hop mesh device is in its neighborhood table and forward the message to the two-hop mesh device.
- the first mesh network may be on a different mesh radio channel or frequency.
- the one-hop mesh device may utilize the correct mesh radio channel or frequency when communicating with the zero-hop device.
- the first mesh network mesh radio channel or frequency may be stored in the neighbor information.
- the one-hop mesh device may optionally exchange neighbor information with a third mesh network zero-hop device. Similar to the first mesh network zero- hop device, the one-hop mesh device may attempt to detect and exchange neighbor information with a zero-hop mesh device on a third mesh network. This creates a network overlap between the second and third mesh networks.
- the one-hop mesh device may optionaiiy forward a message to the third mesh network zero-hop device. Similar to the first mesh network zero-hop device, the one-hop mesh device may receive messages from the third mesh network zero-hop device.
- any number of first-hop mesh devices from any number of mesh networks may be supported within the second mesh network, limited only by the radio range and memory capacity of the mesh device. This creates path diversity and network overlap between the mesh networks.
- the mesh device may interface between any number of mesh networks and the second mesh network.
- the zero-hop mesh device may be associated with another mesh network and mesh gate.
- network overlap is created and path diversity is provided. This improves mesh network performance and reduces WAN load by allowing mesh network-level communications between mesh networks, instead of requiring all such communications to be forwarded through the WAN.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
- Arrangements For Transmission Of Measured Signals (AREA)
Abstract
Methods, systems, and devices described herein can allow a mesh device to participate in multiple mesh networks. A plurality of mesh devices can each associate with a mesh network, each mesh network managed by an access point. Mesh devices exchange neighbor information with neighboring mesh devices, including information of mesh devices associated with a different mesh network. Communication paths can include mesh devices of multiple mesh networks. This provides path diversity among mesh devices and improves bandwidth and reliability. In addition, this provides access diversity in case of mesh network or mesh gate failures.
Description
SYSTEM AND METHOD FOR OPERATING MESH DEVICES IN MULTI-TREE
OVERLAPPING MESH NETWORKS
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of priority to the following United States provisional patent applications which are incorporated herein by reference in their entirety:
• serial number 60/989,957 entitled "Point-to-Point Communication within a Mesh Network", filed November 25, 2007 (TR0004-PRO);
• serial number 60/989,967 entitled "Efficient And Compact Transport Layer And Model For An Advanced Metering Infrastructure (AMI) Network," filed November 25, 2007 (TR0003-PRO);
• serial number 60/989,958 entitled "Creating And Managing A Mesh Network Including Network Association," filed November 25, 2007 (TR0005-PRO);
• serial number 60/989,964 entitled "Route Optimization Within A Mesh Network," filed November 25, 2007 (TR0007-PRO);
• serial number 60/989,950 entitled "Application Layer Device Agnostic Collector Utilizing ANSI C 12.22," filed November 25, 2007 (TR0009-PRO);
• serial number 60/989,953 entitled "System And Method For Real Time Event Report Generation Between Nodes And Head End Server In A Meter Reading Network Including From Smart And Dumb Meters," filed November 25, 2007 (TROOlO-PRO);
• serial number 60/989,975 entitled "System and Method for Network (Mesh) Layer And Application Layer Architecture And Processes," filed November 25, 2007 (TROO 14-PRO);
• serial number 60/989,959 entitled "Tree Routing Within a Mesh Network," filed November 25, 2007 (TROO 17-PRO);
• serial number 60/989,961 entitled "Source Routing Within a Mesh Network," filed November 25, 2007 (TROO 19-PRO);
• serial number 60/989,962 entitled "Creating and Managing a Mesh Network," filed November 25, 2007 (TR0020-PRO);
serial number 60/989,951 entitled "Network Node And Collector Architecture For Communicating Data And Method Of Communications," filed November 25, 2007 (TR0021-PRO); serial number 60/989,955 entitled "System And Method For Recovering From Head End Data Loss And Data Collector Failure In An Automated Meter Reading Infrastructure," filed November 25, 2007 (TR0022-PRO); serial number 60/989,952 entitled "System And Method For Assigning Checkpoints To A Plurality Of Network Nodes In Communication With A Device Agnostic Data Collector," filed November 25, 2007 (TR0023-PRO); serial number 60/989,954 entitled "System And Method For Synchronizing Data In An Automated Meter Reading Infrastructure," filed November 25, 2007 (TR0024-PRO); serial number 60/992,312 entitled "Mesh Network Broadcast," filed December 4, 2007 (TR0027-PRO); serial number 60/992,313 entitled "Multi Tree Mesh Networks", filed December 4, 2007 (TR0028-PRO); serial number 60/992,315 entitled "Mesh Routing Within a Mesh Network," filed December 4, 2007 (TR0029-PRO); serial number 61/025,279 entitled "Point-to-Point Communication within a Mesh Network", filed January 31, 2008 (TR0030-PRO), and which are incorporated by reference. serial number 61/025,270 entitled "Application Layer Device Agnostic Collector Utilizing Standardized Utility Metering Protocol Such As ANSI C 12.22," filed January 31, 2008 (TR0031-PRO); serial number 61/025,276 entitled "System And Method For Real-Time Event Report Generation Between Nodes And Head End Server In A Meter Reading Network Including From Smart And Dumb Meters," filed January 31, 2008 (TR0032-PRO); serial number 61/025,282 entitled "Method And System for Creating And Managing Association And Balancing Of A Mesh Device In A Mesh Network," filed January 31 , 2008 (TR0035-PRO);
• serial number 61/025,271 entitled "Method And System for Creating And Managing Association And Balancing Of A Mesh Device In A Mesh Network," filed January 31 , 2008 (TR0037-PRO);
• serial number 61/025,287 entitled "System And Method For Operating Mesh Devices In Multi-Tree Overlapping Mesh Networks", filed January 31, 2008 (TR0038-PRO);
• serial number 61/025,278 entitled "System And Method For Recovering From Head End Data Loss And Data Collector Failure In An Automated Meter Reading Infrastructure," filed January 31, 2008 (TR0039-PRO);
• serial number 61/025,273 entitled "System And Method For Assigning Checkpoints to A Plurality Of Network Nodes In Communication With A Device- Agnostic Data Collector," filed January 31, 2008 (TR0040-PRO);
• serial number 61/025,277 entitled "System And Method For Synchronizing Data In An Automated Meter Reading Infrastructure," filed January 31, 2008 (TR0041-PRO);
• serial number 61/094,116 entitled "Message Formats and Processes for Communication Across a Mesh Network," filed September 4, 2008 (TR0049-PRO).
[0002] This application hereby references and incorporates by reference each of the following United States patent applications filed contemporaneously herewith:
• serial number entitled "Point-to-Point Communication within a Mesh
Network", filed November 21, 2008 (TR0004-US);
• serial number entitled "Efficient And Compact Transport Layer And Model
For An Advanced Metering Infrastructure (AMI) Network," filed November 21, 2008 (TR0003-US);
• serial number entitled "Communication and Message Route Optimization and Messaging in a Mesh Network," filed November 21, 2008 (TR0007-US);
• serial number entitled "Collector Device and System Utilizing Standardized
Utility Metering Protocol," filed November 21, 2008 (TR0009-US);
• serial number entitled "Method and System for Creating and Managing
Association and Balancing of a Mesh Device in a Mesh Network," filed November 21, 2008 (TR0020-US); and
• serial number entitled "System And Method For Operating Mesh Devices In
Multi-Tree Overlapping Mesh Networks", filed November 21, 2008 (TR0038-US).
BACKGROUND
Field of the Invention
[0003] This invention pertains generally to methods and systems that allow a mesh device to participate in multiple mesh networks. Description of the Related Art
[0004] A mesh network is a wireless network configured to route data between mesh device nodes within the network. A mesh network allows for continuous connections and reconfigurations around broken or blocked paths by retransmitting messages from node to node until a destination is reached. Mesh networks differ from other networks in that nodes can connect to each other via multiple hops. Thus, mesh networks are self-healing: the network remains operational when a node or a connection fails.
[0005] Advanced Metering Infrastructure (AMI) or Advanced Metering Management (AMM) are systems that measure, collect and analyze utility usage, from mesh devices such as electricity meters, gas meters, and water meters, through a network on request or a pre-defined schedule. This infrastructure includes hardware, software, communications, customer associated systems and meter data management software. The infrastructure collects and distributes information to customers, suppliers, utility companies and service providers. This enables these businesses to either participate in, or provide, demand response solutions, products and services. Customers may alter energy usage patterns from normal consumption patterns in response to demand pricing. This improves system load and reliability.
[0006] A mesh gate is an interface between the mesh network and a server over a wide area network (WAN). Each mesh device may associate with a mesh network and a mesh gate,
leaving the mesh network vulnerable to a failure in the mesh gate. In addition, there may be limited paths between mesh devices within the mesh network.
SUMMARY
[0007] Methods, systems, and devices described herein can allow a mesh device to participate in multiple mesh networks. A plurality of mesh devices can each associate with a mesh network, each mesh network managed by an access point. Mesh devices exchange neighbor information with neighboring mesh devices, including information about mesh devices associated with a different mesh network. Communication paths can include mesh devices of multiple mesh networks. This provides path diversity among mesh devices and improves bandwidth and reliability. In addition, this provides access diversity in case of mesh network or mesh gate failures.
[0008] The mesh device can also be located on a boundary between two mesh networks and participate in both mesh networks. This provides path diversity among mesh devices and improves in-premise communication. In addition, this provides access diversity in case of a mesh gate failure. The mesh device may exchange neighbor information with nearby mesh devices of a different mesh network, thus allow a two-hop penetration into the neighboring mesh network.
[0009] In one aspect, a method for a first mesh device to communicate in an overlapping mesh network environment comprises associating with a first access point over a first mesh network, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcast from a neighboring mesh device, updating a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determining a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmitting the message to the next device.
[0010] In another aspect, a system for communicating in an overlapping mesh network environment comprises a plurality of access points, each access point managing a mesh network; and a plurality of mesh devices, each mesh device associated with a mesh network, wherein each mesh device is configured to: (i) responsive to receiving a neighbor information broadcast from a
neighboring mesh device, update a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; (ii) responsive to a request to transmit a message to a destination, determine a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and (iii) transmit the message to the next device.
[0011] In another aspect, a mesh device for communicating in an overlapping mesh network environment comprises a radio for communicating on a predetermined mesh network channel; a memory for storing a neighborhood table; a processor configured to: associate with a first access point over a first mesh network via the radio, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcasted from a neighboring mesh device, update the neighborhood table stored in the memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determine a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmit the message to the next device via the radio.
[0012] In another aspect, a computer-readable medium including instructions adapted to execute a method for a first mesh device to communicate in an overlapping mesh network environment comprises associating with a first access point over a first mesh network, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcasted from a neighboring mesh device, updating a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determining a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmitting the message to the next device.
[0013] In another aspect, a data structure defined in a computer readable medium comprises a plurality of entries, each of the plurality of entries representing at least one device and storing at least one characteristic of the device; and each of the plurality of entries including a plurality of fields for storing characteristics of at least one neighboring device.
[0014] In another aspect, a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; and forwarding a message from the one-hop mesh device to the first mesh network.
[0015] In another aspect, a method comprises associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
[0016] In another aspect, a device comprises a neighborhood table, the neighborhood table storing mesh network device information; and a radio configured to communicate with a first mesh network and a second mesh network, wherein the device is configured to, in operation, associate with a first mesh gate over the first mesh network, exchange neighbor information stored in the neighborhood table with an accessible same-network mesh device over the first mesh network, detect an accessible one-hop mesh device on the second mesh network, exchange neighbor information stored in the neighborhood table with the one-hop mesh device, and forward a message from the one-hop mesh device to the first mesh network. [0017] In another aspect, a computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; and forwarding a message from the one-hop mesh device to the first mesh network. [0018] In another aspect, a computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method comprises associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
[0019] In another aspect, a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; forwarding a message from the one-hop mesh device to the first mesh network; associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
[0020] In another aspect, a computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method comprises associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; forwarding a message from the one-hop mesh device to the first mesh network; associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network. [0021] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0022] FIG. IA illustrates a system for providing communications in an AMI system, according to an exemplary embodiment.
[0023] FIG. IB illustrates a system for providing communications in an AMI system, according to another exemplary embodiment.
[0024] FIG. 2A illustrates a mesh device for use within a mesh network, according to an exemplary embodiment.
[0025] FIG. 2B illustrates a mesh gate for use within a mesh network, according to an exemplary embodiment.
[0026] FIG. 3 illustrates a network stack for use within a mesh radio, according to an exemplary embodiment.
[0027] FIG. 4 illustrates a process for a mesh device to communicate in a multi-mesh network environment, according to an exemplary embodiment.
[0028] FIG. 5A illustrates a data structure for storing a neighborhood table, according to an exemplary embodiment.
[0029] FIG. 5B illustrates a data entry for storing neighborhood table information, according to an exemplary embodiment.
[0030] FIG. 6A illustrates a process for a zero-hop device to forward communications between a first mesh network and a second mesh network, according to an exemplary embodiment.
[0031] FIG. 6B illustrates a process for a one-hop device to forward communications between a first mesh network and a second mesh network, according to an exemplary embodiment.
DETAILED DESCRIPTION
[0032] Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. [0033] FIG. IA illustrates an exemplary system for providing communications in an AMI system 100. The AMI system may include a plurality of mesh networks, such as mesh network A 102 and mesh network B 104. While only two mesh networks are depicted, any number of mesh networks may exist in the AMI system. Mesh network A 102 includes a mesh gate A 106 and mesh devices A 110, B 112, C 114, D 116 and E 118. Mesh network B 104 includes mesh gate B 108 and mesh devices U 120, V 122, W 124, X 126, Y 128 and Z 130. Although FIG. 1 depicts only five mesh devices in the mesh network A 102, any number of mesh devices may be used in the mesh network A 102. The mesh devices A 110, B 112, and C 114 may perform required functions within the mesh network A 102. For example, a mesh device may be a meter, a user interface such as for example a thermostat, an output device such as a utilities usage display, or any other device or subsystem required or benefited by the AMI system. [0034] The mesh gate 106 and the mesh devices function as nodes in the mesh network, which dynamically creates and maintains links between the nodes. Each mesh device may transmit
messages to the mesh gate A 106 and other mesh devices within the mesh network A 102. Only mesh devices A 110 and C 114 are in direct communication with the mesh gate A 106. However, mesh device B 112 may reach the mesh gate via mesh device A 110. [0035] A mesh gate may also be referred to as an access point or a Neighborhood Area Network to Wide Area Network (NAN- WAN) gate. The mesh gate may perform any one or more of many different functions including, for example, but not limited to, one or any combination of: relaying information from a server (such as to a head end server) to the mesh network nodes, routing information, aggregating information from the nodes and microportals within any sub-network that may be configured for transmission to a server (such as to the head end server), acting as a home area network (HAN) sometimes also referred to as a premise area network (PAN) coordinator, acting as a NAN- WAN gate, transmitting firmware upgrades, and/or multicasting messages. The mesh gate may also be referred to as a collector because it collects information from the NAN-associated nodes or other nodes and/or microportals in its subnetwork. A mesh gate may include a mesh radio to communicate with mesh devices over the mesh network and a WAN communication interface to communicate with the server over the WAN 131.
[0036] The mesh gate A 106 may provide a gateway between the mesh network A 102 and a server 132. The server 132 can also act as a head end. The server 132 can provide services to mesh devices within the AMI system, such as commissioning devices, providing software updates, providing metering pricing updates, receiving metering information, etc. The mesh gate A 106 may aggregate information from mesh devices (e.g., meters) within the mesh network and transmit the information to the server 132. The mesh gate A 106 may further forward messages from the mesh devices to the server 132, for example, status reports and meter readings. The mesh gate A 106 may further forward messages from the server 132 to the mesh devices, for example, instructions and queries. The server 132 may be a computing device configured to receive information, such as meter readings, from a plurality of mesh networks and meters. The server 132 may also be configured to transmit instructions to the mesh networks, mesh gates, and meters. It will be appreciated that while only one server is depicted, any number of servers may be used in the AMI system. For example, servers may be distributed by geographical location. Redundant servers may provide backup and failover capabilities in the AMI system.
[0037] The mesh devices may also exchange neighbor information with neighboring mesh devices from another mesh network. Neighbor information may for example include one or more of mesh device identifiers, a signal quality indicator or value, a distance to mesh gate indicator or value, and any other information necessary or advantageous to calculate a route from the mesh device. In one embodiment, the neighbor information includes each of these information items.
[0038] The mesh devices may exchange neighbor information with each other, where the neighbor information is propagated throughout the mesh network and used to determine a best path to the mesh gate. For example, mesh device A 110 knows it is a neighbor of the mesh gate. It will send the information to mesh device D 116, which then knows that in order to send a message to the mesh gate, it may ask mesh device A 110 to forward the message. [0039] The mesh gate A 106 can manage the mesh network A 102 by maintaining an association (registration) table which can include information about in-network and out of network nodes and a neighborhood table which includes information about the nodes in the network and their neighbors (which may include out of network nodes) and other information for each mesh device within the mesh network A 102. When a new mesh device attempts to join mesh network A 102, it sends an association request to the mesh gate A 106, which will add the new mesh device to its neighborhood table. It will be appreciated that a mesh device association can include a registration for application service at the mesh gate A 102 or the server 132. The mesh gate A 102 and the server 132 can maintain a table of available applications and services and requesting mesh devices. More particularly, an exemplary neighborhood table is structured as described with respect to Tables 1 and 2 below:
Table 1
When the number of Neighbors exceeds the capacity of the Neighborhood table, the radio applies the following order in its selection of Neighbors to keep: Best 5 Parents per network tree; Children using this Node as preferred route; Children or Sibling using this Node as second
preferred route; and Remaining Nodes are included in the table in a round robin fashion to give the chance to every node to flag the current Node as preferred or second preferred route. [0040] The mesh network B 104 may similarly include a mesh gate B 108 and at least one mesh device. The mesh network B 104 may neighbor or be adjacent to the mesh network A 102 and therefore some of the mesh devices of mesh network B 104 may be in radio transmit/receive range of mesh devices of the mesh network A 102.
[0041] In operation, the mesh networks may overlap and therefore provide path diversity among the mesh devices. For example, if device Y 128 is a thermostat and needs to transmit a message to device E 118, such as a utilities control unit, it is not necessary to transmit the instruction to mesh gate B 108 via mesh network B 104, which is then transmitted to mesh gate A 106 via a WAN 131, which is then transmitted to the device E 118 via mesh network A 102. Instead, device Y 128 receives neighbor information from device E 118 and realizes they are neighbors. Direct communication between the mesh devices is possible.
[0042] The mesh devices can utilize other accessible mesh gates as a secondary mesh gate in case of failure by the primary mesh gate with which the mesh device is associated. For example, mesh devices of mesh network B 104 may transmit messages to mesh gate A 106 if mesh gate B 108 fails to respond.
[0043] In one exemplary embodiment, neighboring mesh networks can operate on different channels or radio frequencies. This can improve wireless bandwidth within a mesh network and decrease interference from neighboring mesh network transmissions. The channels or radio frequencies can be predetermined.
[0044] It will be appreciated that a mesh device can allow penetration of any number of hops into a neighboring mesh network. However, because a path of each mesh device forwarding a message can be stored in the message header, a path length can be limited by a size of the message header. In one example embodiment, the path length can be limited to nine hops, thus allowing a penetration of nine-hops into neighboring mesh networks.
[0045] As shown in the exemplary illustrated embodiment, the mesh devices D 116 and E 118 may function as zero-hop devices. Zero-hop devices may be on the boundary of the mesh network, with children nodes that are mesh devices belonging to a second mesh network. Zero- hop devices may communicate with the mesh gate directly or through intermediate mesh devices. For example, the mesh device D 116 may reach the mesh gate A 106 via mesh device A 110.
Similarly, the mesh device E 118 may reach the mesh gate A 106 via mesh device C 114. The neighborhood tables of zero-hop devices may include neighbors within mesh network A 102 as well as mesh network B 104.
[0046] The mesh devices Y 128 and Z 130 may function as one-hop devices. One-hop devices may be on the boundary of the mesh network B 104 and be neighbors with zero-hop devices of mesh network A 102. Thus, one-hop devices may communicate with the associated mesh gate B 108 or with mesh gate A 106 via the zero-hop devices. The neighborhood tables of one-hop devices may include neighbors within mesh network B 104 as well as mesh network A 102. [0047] The mesh devices W 124 and X 126 may function as two-hop devices. Two-hop devices may be neighbors with one-hop devices, and therefore are two hops away from a neighboring mesh network. Thus, two-hop devices may communicate with the associated mesh gate B 108 or with mesh gate A 106 via the one-hop and zero-hop devices as well as mesh network A 102.
[0048] In the exemplary embodiment of system 100, the mesh devices U 120 and V 122 may not include information on mesh devices of mesh network A 102 in neighborhood tables. However, messages may be forwarded to two-hop devices for forwarding to mesh network A 102.
[0049] In operation, the one-hop and two-hop devices may utilize mesh gate A 106 as a secondary mesh gate in case of failure by mesh gate B 108. Over time, mesh device U 120 and mesh device V 122 may re-associate with a new mesh gate, but the one-hop and two-hop devices may utilize their secondary mesh gate immediately and suffer no downtime. [0050] In an alternative embodiment of the AMI as shown in FIG. IB, mesh devices may also serve as conduits between two networks. For example, in FIG. IB, system 150 includes conduit device J 172 associated with mesh network C 160 and mesh network D 162. Mesh network C 160 includes device G 168, device H 170, and mesh gate C 164. Mesh network D 162 includes device K 174, device L 176, and mesh gate D 166. The mesh networks, mesh gates, and mesh devices shown in FIG. IB are merely representative and alternate systems may include additional numbers and arrangements of mesh networks, mesh gates, and mesh devices. The mesh devices illustrated in FIG. IB can serve a variety of functions and may be, for example, meters, thermostats, output devices such as displays, or any other device or subsystem required or benefited by the AMI system. Mesh gate C 164 and mesh gate D 162 communicate with
server 180 via WAN 178. Except for mesh device J 172, the mesh devices and mesh gates can operate in a similar fashion to those mesh gates and mesh devices illustrated and described in connection with FIG. IA.
[0051] With respect to mesh device J 172, this device may associate with mesh network C 160 and mesh network D 162 and act as a conduit between the two networks. Mesh device J 172 may allow mesh devices and mesh gates in one network to communicate with mesh devices and mesh gates in the other network. For example, if mesh gate C 164 was not available to receive communications from mesh devices in mesh network C 160, mesh device H 170 may communicate a message to mesh gate D 166 via mesh device J 172. Mesh device J 172 may be similar to the other mesh devices illustrated in FIG. IB except that it may have additional software allowing it to serve as a conduit between the two networks.
[0052] FIG. 2A illustrates an exemplary mesh device 200 for use within a mesh network. Mesh device 200 may include a radio 202, a communication card 204, a metering sensor 206, and a battery or other power or energy storage device or source 208. The radio 202 may include a memory 210, a processor 212, a transceiver 214, and a microcontroller unit (MCU) 216 or other processor or processing logic.
[0053] The mesh device 200 can be any device configured to participate as a node within a mesh network. Mesh device 200 can be a mesh repeater, which can be a wired device configured to retransmit received mesh transmissions. The mesh repeater can extend over a range of a mesh network and provide mesh network functionality to mesh devices that enter sleep cycles.
[0054] The mesh device 200 may communicate with a mesh gate and other mesh devices over a mesh network. For example, the mesh device 200 may be a gas, water, electricity, or other utility meter installed in a residential, commercial, or industrial building or other location to monitor utilities usage. The mesh device 200 may also control access to utilities on receipt of instructions such as instructions or control signals received from a server, for example, by reducing or stopping the flow of gas, water or electricity. In an alternative, the mesh device 200 may be a mobile asset that needs to be tracked by the AMI system.
[0055] The radio 202 may be a mesh radio configured to communicate with a mesh network. The radio 202 may transmit, receive, and forward messages to the mesh network. Any meter within the mesh network may thus communicate with any other meter or mesh gate by
communicating with its neighbor and requesting a message be forwarded. The radio 202 may also communicate with an off-network device not associated with the mesh network. [0056] The communication card or circuit 204 may interface between the radio and the sensor. Sensor readings or other data may be converted to radio signals for transmission over the radio. The communication card 204 may optionally but advantageously include encryption/decryption functionality or other security measures to protect the transmitted data. The communication card 204 may also decode instructions received from the server.
[0057] The optional metering sensor 206 may be a gas, water, electricity, media content or information meter sensor, or another sensor. For example, digital flow sensors may be used to measure a quantity of water or gas flowing into a residence or building. Alternatively, the sensor 206 may be an electricity meter configured to measure a quantity of electricity flowing over a power line.
[0058] In an alternative embodiment, the optional metering sensor 206 may be replaced by another component for performing functions within the AMI system. For example, the mesh device may provide a user interface, such as a thermostat or other utilities control or display. In this example, the metering sensor may be replaced with a thermostat interface. For example, the mesh device may provide a display screen, such as an LCD display screen that displays information for the user. In another example, the mesh device may be a simple repeater for extending the range of the mesh network. In this example, the mesh device may simply receive and re-transmit mesh transmissions on the mesh network.
[0059] The battery or other energy storage device 208 may be configured to independently power the mesh device 200 during a power outage. For example, the battery 208 may be a large capacitor storing electricity to power the mesh device 200 for at least five minutes after a power outage. Small compact but high capacity capacitors known as super capacitors are known in the art and may advantageously be used. One exemplary super capacitor is the SESSCAP 50f 2.7v 18x30mm capacitor manufactured by NESSCAP Co., Ltd. of Wonchun-Dong 29-9, Paldal-Ku, Soowon, Kyonggi-Do 442-380, Korea. Alternative battery technologies may be used, for example, galvanic cells, electrolytic cells, fuel cells, flow cells, and voltaic cells. [0060] The memory 210 may store instructions and run-time variables for execution. For example, the memory 210 may include both volatile and non- volatile memory. The memory 210
may also store a history of sensor readings from the metering sensor 206 and an incoming queue of server instructions.
[0061] The mesh device 200 may also include a memory in additional to memory 210. A neighborhood table may be stored in a memory accessible by the mesh device 200. For example, the neighborhood table may store a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field. The neighborhood table information may be transmitted to other mesh devices in a neighbor exchange and may also be transmitted to a mesh gate. The neighborhood table may be used to determine a best route on the mesh network for a message to be transmitted. Alternatively, the neighborhood table can include other fields.
[0062] Information from the neighborhood table can be used to calculate a path to an access point. For example, a calculated path can have a good connection to a mesh gate as defined by signal quality, number of hops, and a mesh gate load. It will be appreciated that various weightings can be used to compute a calculated path value, and a best valued path is selected for use.
[0063] The processor 212 may execute instructions, for example, stored in the memory.
Instructions stored in memory 210 may be ordinary instructions, for example, provided at time of meter installation, or special instructions received from the server during run time.
[0064] The transceiver 214 may transmit to and receive from a mesh network wireless signals.
The transceiver 214 may be configured to transmit sensor readings and status updates under control of the processor. The transceiver 214 may receive server instructions from a server, which are communicated to the memory and the processor.
[0065] The MCU 216 can execute firmware or software required by the mesh device 200. The firmware or software can be installed at manufacture or via a mesh network over the radio 202.
[0066] In one embodiment, any number of MCUs can exist in the mesh device 200. For example, two MCUs can be installed, a first MCU for executing firmware handling communication protocols, and a second MCU for handling applications.
[0067] It will be appreciated that a mesh device and a mesh gate can share the architecture of mesh device 200. The radio 202 and the MCU 216 provide the necessary hardware, and the
MCU 216 executes any necessary firmware or software.
[0068] Each component may be modular and configured for easy removal and replacement.
This facilitates component upgrading over a lifetime of the meter as new functionality are developed and deployed in the AMI system.
[0069] Meters may be located in geographically dispersed locations within an AMI system.
For example, a meter may be located near a gas line, an electric line, or a water line entering a building or premise to monitor a quantity of gas, electricity, or water flowing through the line.
The meter may communicate with other meters, even with meters of different types, and mesh gates through a mesh network. The meter may transmit meter readings and receive instructions via the mesh network.
[0070] In operation, the mesh device 200 may communicate over a mesh network and directly with an off-network device via the radio 202. The communication card or circuit 204 may interface between the metering sensor 206 and the radio 202. For example, sensor readings may be transmitted to and instructions received from a server. In addition, the mesh device 200 may participate in the mesh network by forwarding any messages that require forwarding to a next mesh device on a dynamically determined or pre-determined path.
[0071] In an alternative, mesh devices may be similar to meters except the metering sensor is replaced by whatever component is necessary to perform the mesh device's function. For example, a user display may include an output screen or set of indicator lights. For example, a thermostat may include a dial or other user interface or mechanism for receiving user input and an analog/digital converter to produce an input signal.
[0072] FIG. 2B is a block diagram that illustrates an exemplary mesh gate 230 for use within a mesh network. The mesh gate 230 may include a mesh radio 232, a wide area network interface
234, a battery 236, and a processor or processing logic 238. The mesh radio 232 may include a memory 242, a processor 244, and a transceiver 246. The mesh gate 230 may interface between mesh devices such as meters over a mesh network and a server over a WAN. The mesh gate 230 may be installed in a central location relative to the meters and also communicate with a server over a WAN.
[0073] The mesh radio 232 may be a mesh radio configured to communicate with meters over a mesh network. The radio 232 may transmit, receive, and forward messages to the mesh network.
[0074] The WAN interface 234 may communicate with a server over a WAN. For example, the WAN may be a cellular network, a private network, a dial up connection, or any other network. The WAN interface 234 may optionally include encryption/decryption functionality or other security measures to protect data being transmitted to and from the server. [0075] The battery or other energy or power source 236 may be configured to independently power the mesh gate 230 during a power outage. For example, the battery 236 may be a large capacitor storing electricity to power the mesh gate 230 for at least five minutes after a power outage. While not limitations of embodiments of the invention, a capacitor may advantageously be used in a meter that may have access to a power source such as an electric utility meter, and a battery may be a more suitable power source for a gas meter which may not frequently be connected to a continuous or even intermittent source of power or energy. [0076] The processor or processing logic 238 may control the mesh radio 232 and the WAN interface 234. Meter information received from the meters over the mesh radio 232 may be compiled into composite messages for transmission to the server. Server instructions may be received from the WAN interface 234 and transmitted to meters in the mesh network for execution. Server instructions may also be received from the WAN interface 234 for execution by the processor 238.
[0077] The mesh radio 232, WAN interface 234, battery 236, and processor 238 may be modular and configured for easy removal and replacement. This facilitates component upgrading over a lifetime of the mesh gate 230.
[0078] As described more specifically above, an accessible memory of each mesh device may store neighbor information for all mesh devices within the mesh network (and within communication range of the mesh device regardless of association with a specific mesh network) and associated with the mesh device. The neighborhood table information may be exchanged between mesh devices and also transmitted to the mesh gate. The mesh gate may be configured to calculate various routing based on the compiled neighborhood table.
[0079] The memory 242 of the mesh radio 232 may store instructions and run-time variables of the mesh radio 232. For example, the memory 242 may include both volatile and non- volatile memory. The memory 242 may also store a history of meter communications and a queue of incoming server instructions. For example, meter communications may include past sensor readings and status updates.
[0080] The mesh gate may include an additional memory configured to store values in the execution of mesh gate functions. For example, a history of meter readings or status updates may be stored for future retrieval.
[0081] The processor 244 of the mesh radio 232 may execute instructions, for example, stored in memory 242. Instructions stored in memory 242 may be ordinary instructions, for example, provided at time of mesh gate installation, or special instructions received from the server during run-time.
[0082] The transceiver 246 of the mesh radio 232 may transmit and receive wireless signals to a mesh network. The transceiver 246 may be configured to receive sensor readings and status updates from a plurality of meters in the mesh network. The transceiver 246 may also receive server instructions, which are communicated to the memory 242 and the processor 244. [0083] In operation, the mesh gate may interface between a mesh network and a server. The mesh gate may communicate with meters in the mesh network and communicate with the server over a WAN network. By acting as a gateway, the mesh gate forwards information and instructions between the meters in its mesh network and the server. The mesh gate may also function as a node within the mesh network, by forwarding messages between mesh devices. [0084] FIG. 3 illustrates an exemplary network stack for use within a mesh radio 300. The application process 302 may communicate with an application layer 304, a transport layer 306, a network layer 308, a data link layer 310 and a physical layer 312.
[0085] The radio 300 may be a mesh radio installed in a mesh gate, a mesh device, or an off- network device. For example, the radio 300 may be a component in a meter, a mesh gate, or any other mesh device configured to participate in a mesh network or communicate with other mesh devices. The radio 300 may be configured to transmit wireless signals over a predetermined or dynamically determined frequency to other radios.
[0086] The application process 302 may be an executing application that requires information to be communicated over the network stack. For example, the application process 302 may be software supporting an AMI system, such as software or firmware executing in some processor or processing logic on an electricity meter or a mesh gate.
[0087] The application layer 304 interfaces directly with and performs common application services for application processes. Functionality may include semantic conversion between associated application processes. For example, the application layer may be implemented as
ANSI C 12.12/22, which standard as of the filing date of this application is hereby incorporated by reference.
[0088] The transport layer 306 responds to service requests from the application layer and issues service requests to the Internet layer. It delivers data to the appropriate application on the host computers. For example, the layer may be implemented as TCP (Transmission Control Protocol), and UDP (User Datagram Protocol), or according to other known or convenient protocols.
[0089] The network layer 308 is responsible for end to end (source to destination) packet delivery. The network layer's functionality may advantageously include transferring variable length data sequences from a source to a destination via one or more networks while maintaining the quality of service, and error control functions. Data will be transmitted from its source to its destination, even if the transmission path involves multiple hops or relays. For example, the network layer 308 may translate a short address into a network address. A short address may for example be a two byte address used to identify mesh devices within a mesh network. The short address may be assigned by the access point. A network address may be an eight byte unique address used to identify the mesh device from among other mesh devices. The network address may be assigned at manufacture or by a server. Short addresses may be used within a mesh network to shorten messages that are addressed to another mesh device within the same mesh network. Long addresses may be used to address mesh devices of another mesh network or whose short address is not known to a message sender.
[0090] The data link layer 310 transfers data between adjacent network nodes in a network, wherein the data is in the form of packets. The layer provides functionality including transferring data between network entities and error correction/detection. For example, the layer may be implemented as IEEE 802.15.4, which standard as of the filing date of this application is hereby incorporated by reference.
[0091] The physical layer 312 may be the most basic network layer, transmitting bits over a data link connecting network nodes. No packet headers or trailers are included. The bit stream may be grouped into code words or symbols and converted to a physical signal, which is transmitted over a transmission medium, such as radio waves. The physical layer provides an electrical, mechanical, and procedural interface to the transmission medium. For example, the layer may be implemented as IEEE 802.15.4.
[0092] In operation, the network stack provides different levels of abstraction for programmers within an AMI system. Abstraction reduces a concept to only information which is relevant for a particular purpose. Thus, each level of the network stack may assume the functionality below it on the stack is implemented. This facilitates programming features and functionality for the AMI system. The illustrated network stack may facilitate intra-mesh network communication by utilizing a short address to identify addressees.
[0093] FIG. 4 illustrates an exemplary process 400 for a mesh device to communicate in a multiple mesh network environment. It should be understood that process 400 and the other exemplary processes described herein may be performed in different sequences or certain steps may be performed in parallel in alternate embodiments. The procedure may execute on a mesh device associated with a first mesh network and within radio range of neighboring mesh devices, some of which are associated to a second mesh network. The procedure may allow mesh devices of the two mesh networks to communicate amongst each other and provide network overlap. [0094] In step or process 402, the mesh device can associate with a first access point. Recall that an access point may also be referred to as mesh gate or a NAN- W AN gate. Associating with the first access point includes transmitting an association request to the first access point and awaiting a confirmation. If the first access point is not within radio range of the mesh device, the message is transmitted via a mesh network.
[0095] The mesh network includes neighboring mesh devices, as shown in FIG. 1, which can forward the association request towards the access point. The neighboring mesh devices will also forward the confirmation back to the mesh devices. Once the mesh device is associated with the first access point, it will participate in the mesh network and forward messages from its neighbors, as required.
[0096] For example, the association can happen periodically after a predetermined or dynamically determined time interval or according to some other policy, at a mesh device start up, or when communication with the first access point is lost. If there is no neighboring mesh device associated with the first mesh network within radio range, the mesh device can retry association after a predetermined or dynamically determined time interval or according to some other policy.
[0097] In step or process 404, the mesh device can test whether neighbor information has been received. In a mesh network, neighboring mesh devices will periodically broadcast mesh device
information and neighbor information. Neighbor information may include one or any combination of mesh device identifiers, signal strength, distance from access point, and other information helpful in determining a path through a mesh network. In one non-limiting example, the neighbor information includes each of these.
[0098] If neighbor information is received, the mesh device proceeds to step or process 406. If no neighbor information is received, the mesh device proceeds to step or process 408.
[0099] In one example, the neighbor information will include preferred routes over a plurality of mesh networks to various destinations.
[00100] In step or process 406, the mesh device can update a neighborhood table in accessible memory. The mesh device can be configured with an accessible memory which stores a neighborhood table. The neighborhood table stores mesh device information and neighbor information of neighboring mesh devices.
[00101] Filters can be used to restrict a size of the neighborhood table. For example, the neighborhood tables can be configured to only store mesh device information of mesh devices within a predetermined number of hops from the mesh device or have specified signal quality.
[00102] In step or process 408, the mesh device can test whether a message transmit request has been received. For example, the message transmit request can be received from the mesh device when a message must be sent via the mesh network. For example, the message can be intended for a server, the first access point, or another mesh device.
[00103] Alternatively, the message transmit request can be received from a received message.
The received message can be received from a neighboring mesh device for transmitting. A message destination will be included in the received message, which is parsed by the mesh device.
[00104] If a transmit message request is received, the mesh device proceeds to step or process
410. If no transmit message request is received, the mesh device returns to step or process 404.
[00105] In step or process 410, the mesh device can determine a next device on a path to the destination. The next device can be the destination of the message, such as a neighboring mesh device or an access point within radio range. Alternatively, the next device can be the neighboring mesh device to which the mesh device must transmit the message for forwarding.
[00106] If the destination is a server or another device not on the mesh network, the message can be received by an access point or another device configured to interface between the mesh network and the off-mesh network device.
[00107] The next device can be determined from a next device table stored in accessible memory, where the mesh device stores a list of destinations and a next device associated with each destination. Alternatively, the next device can be calculated by the first access point and stored in the next device table. In another alternative embodiment, the next device can be calculated by the mesh device as required.
[00108] In step or process 412, the mesh device can transmit the message to the next device.
The message can be broadcast on a radio channel used by the mesh network and addressed to the next device by including a next device identifier in a message header. All other mesh devices will ignore the message because they are not the next device and thus not required to receive and forward the message.
[00109] In step or process 414, the mesh device can optionally detect whether there is a problem mesh network within communication range. A problem mesh network can be a mesh network whose bandwidth usage is near or at its limit and cannot service requests from outside the mesh network.
[00110] If a problem mesh network is detected, the mesh device proceeds to step or process 416.
If no problem mesh network is detected, the mesh device proceeds to step or process 418.
[00111] In step or process 416, the mesh device can optionally delete entries related to the problem mesh network from the neighborhood table. Because each entry in the neighborhood table includes a network identifier, all entries associated with the problem mesh network can be easily located and deleted.
[00112] In step or process 418, the mesh device can optionally test whether a neighbor information request has been received. For example, the neighbor information request can be triggered at a predetermined time by the mesh device. A randomizing component can be added to the predetermined time so that not all neighboring mesh devices attempt to broadcast neighbor information at the same time.
[00113] Alternatively, the neighbor information request can be received over the mesh network.
For example, the first access point can periodically initiate neighbor information exchanges by transmitting neighbor information requests to each mesh device within its mesh network.
[00114] If a neighbor information request has been received, the mesh device proceeds to step or process 420. If no neighbor information request has been received, the mesh device proceeds to step or process 422.
[00115] In step or process 420, the mesh device can optionally broadcast neighbor information.
The neighbor information can be retrieved from the neighborhood table and include information as discussed above.
[00116] In step or process 422, the mesh device can exit the procedure. It will be appreciated the procedure can be repeatedly executed by the mesh device while powered.
[00117] FIG. 5A illustrates an exemplary data structure 500 for storing a neighborhood table.
The data structure can be stored in accessible memory on a mesh device or an access point.
[00118] The data structure 500 includes entries 502, each data entry 502 representing a mesh device and mesh device characteristics.
[00119] FIG. 5B illustrates an exemplary data entry 502 for storing neighborhood table information. The data entry 502 may include one or include a plurality of fields for storing characteristics of a neighboring device, some of which fields may be optional.
[00120] A tree PAN identifier 504 may be provided and can be a binary two byte data field for identifying a network tree associated with the mesh device. The tree PAN identifier 504 can refer to foreign networks.
[00121] A neighbor address 506 may be provided and can be a binary two byte data field for identifying an address of the mesh device.
[00122] A neighbor PAN identifier 508 may be provided and can be a binary two byte data field for identifying a membership of the mesh device.
[00123] An average quality 510 may be provided and can be an unsigned 8-bit data field for specifying an average quality of the mesh device's path to an access point.
[00124] A number of hops 512 may be provided and can be an unsigned 8-bit data field for specifying a number of hops between the mesh device and an access point.
[00125] A minimum quality 514 may be provided and can be an unsigned 8-bit data field for specifying a minimum quality of the mesh device's path to an access point.
[00126] A freshness indicator 516 may be provided and can be an unsigned 8-bit data field for specifying how recently the mesh device information was received.
[00127] FIG. 6A illustrates an exemplary process 600 for a zero-hop mesh device to forward communications between a first mesh network and a second mesh network. The procedure may execute on a mesh device on the border of a first mesh network and within radio range of a mesh device of a second mesh network. The procedure may allow mesh devices of the two mesh networks to communicate and provide network overlap. The zero-hop device may be a mesh device associated with the first mesh network but storing neighbor information of at ieast one one-hop device associated with the second mesh network. Thus, the zero-hop device may facilitate communications between the first mesh network and the one-hop device. [00128] In process or step 602, the mesh device may associate with a first mesh gate. For example, the mesh device may execute a search routine on power-up or when communication with an associated mesh gate is lost. The mesh device may search for nearby mesh gates and select one for association based on a variety of factors such as signal strength, number of hops to the mesh gate, and mesh gate load. The mesh device may transmit an association request to the mesh gate via the mesh network and receive an acknowledgement. After the mesh device is associated with a mesh gate, it may participate in the first mesh network as a node and communicate with a server over a WAN via the mesh gate. It may also communicate with other mesh devices in the mesh network.
[00129] In process or step 604, the mesh device may exchange neighbor information with one or more same-network mesh devices. For example, neighbor information may include a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field. The neighbor information may be compiled by the mesh device for every neighboring mesh device with which it is in communication, and used to determine a path for messages to be transmitted. The exchange of neighbor information may occur at a pseudo-random periodic interval, for example, once every hour at a random time. This allows all mesh devices in the mesh network to exchange neighbor information and build up a stored neighbor information table.
[00130] In process or step 606, the zero-hop mesh device may test whether a one-hop mesh device is accessible. For example, the one-hop mesh device may be associated with a second mesh network and communicate on a second mesh radio channel. The mesh device may scan alternate mesh radio channels until an accessible one-hop mesh device is found. In an alternative, the mesh networks may communicate on different frequencies. If an accessible one-
hop mesh device is not found, the mesh device may assume no one-hop mesh devices are within radio range and wait a time-out period before re-testing.
[00131] If a one-hop mesh device is accessible, the procedure may proceed to process or step
608. If a one-hop mesh device is not accessible, the procedure may proceed to 604 and continue functioning as a node in the first mesh network. The zero-hop mesh device may periodically check whether a one-hop mesh device has become accessible.
[00132] In process or step 608, the zero-hop mesh device may exchange neighbor information with the one-hop mesh device. For example, the neighbor information may be compiled from neighbor information exchanges as discussed above. The neighbor information may include, in addition to the contents discussed above, a mesh network identifier for each mesh device indicating the mesh devices are associated with the first mesh network.
[00133] In process or step 610, the mesh device may receive a message for forwarding from the one-hop mesh device. For example, the one-hop device may desire to transmit a message to a neighbor of the zero-hop device on the first network. Instead of transmitting the message to the mesh gate associated with the second mesh network, forwarding the message to the mesh gate associated with the first mesh network over the WAN, and forwarding the message to the correct mesh device, the one-hop device may request the zero-hop device forward the message. This reduces network load and improves network performance.
[00134] In an alternative embodiment, the message may be addressed to a server. In this example, the one-hop mesh device may lose communications with its associated mesh gate. The one-hop mesh device may transmit the message to the zero-hop device for forwarding to the associated mesh gate via the first mesh network.
[00135] If a message is received for forwarding, the procedure may proceed to process or step
612. If no message is received for forwarding, the procedure may remain in process or step 610.
The zero-hop mesh device may continue to function as a node within the first mesh network and periodically check whether a message has been received from the one-hop mesh device for forwarding on the first mesh network.
[00136] In process or step 614, the zero-hop mesh device may optionally transmit a status to a server. For example, the status may include neighbor information including the one-hop mesh devices. The neighbor information may allow the server to better route message traffic
considering the mesh network overlap between the first mesh network and the second mesh network.
[00137] In process or step 616, the zero-hop mesh device may optionally test whether a response has been received from the server. For example, the message forwarded on behalf of the one- hop mesh device may require a response from the recipient, whether a mesh device within the first mesh network or the server. The response may be transmitted to the zero-hop mesh device via the first mesh gate and the first mesh network.
[00138] In an alternative embodiment, the server may transmit the message to the mesh device when the mesh gate associated with the one-hop mesh device has failed. This provides path diversity in case of mesh gate failure.
[00139] In process or step 618, the mesh device may optionally forward the received response to the one-hop mesh device. The mesh device may check that the one-hop mesh device is in its neighborhood table and forward the message to the one-hop mesh device. If the second mesh network is on a different mesh radio channel or frequency, the mesh device may utilize the correct mesh radio channel or frequency. For example, the second mesh network mesh radio channel or frequency may be stored in the neighbor information.
[00140] In process or step 620, the mesh device may optionally exchange neighbor information with a third mesh network one-hop device. Similar to the second mesh network one-hop device, the mesh device may attempt to detect and exchange neighbor information with a one-hop mesh device on a third mesh network. This creates a network overlap between the first and third mesh networks. In addition, the third mesh network one-hop device may also reach the second mesh network one-hop device via the zero-hop mesh device.
[00141] In process or step 622, the zero-hop mesh device may optionally forward a message from the third mesh network one-hop device to the first mesh network. Similar to the second mesh network one-hop device, the zero-hop mesh device may receive messages from the third mesh network one-hop device and forward the message to the first mesh network, and possibly the first mesh gate and the server.
[00142] In an alternative embodiment, any number of one-hop mesh devices from any number of mesh networks may be supported within the first mesh network, limited only by the radio range and memory capacity of the mesh device. This creates path diversity and network overlap between the mesh networks.
[00143] In operation, the mesh device may interface between the first mesh network and at least one one-hop mesh device. The one-hop mesh device may be associated with another mesh network and mesh gate. By providing an interface between the first mesh network and the one- hop mesh device, network overlap is created and path diversity is provided. This improves mesh network performance and reduces WAN load by allowing mesh network-level communications between mesh networks, instead of requiring all such communications to be forwarded through the WAN.
[00144] FIG. 6B illustrates an exemplary process 650 for a one-hop device to forward communications between a first mesh network and a second mesh network. The procedure may execute on a mesh device on the border of a second mesh network and within radio range of a mesh device of a first mesh network. The procedure may allow mesh devices of the two mesh networks to communicate and provide network overlap. A one-hop device may be a mesh device associated with the second mesh network and storing neighbor information of at least one zero-hop mesh device associated with the first mesh network. Thus, the one-hop device may facilitate communications between the second mesh network and the zero-hop mesh device. [00145] In process or step 652, the one-hop mesh device may associate with a second mesh gate. For example, the one-hop mesh device may execute a search routine on power-up or when communication with an associated mesh gate is lost. The one-hop mesh device may search for nearby mesh gates and select one for association based on a variety of factors such as signal strength, number of hops to the mesh gate, and mesh gate load. The one-hop mesh device may transmit an association request to the mesh gate via the mesh network and receive an acknowledgement. After the one-hop mesh device is associated with the second mesh gate, it may participate in the second mesh network as a node and communicate with a server over a WAN via the second mesh gate. It may also communicate with other mesh devices in the second mesh network.
[00146] In process or step 654, the one-hop mesh device may exchange neighbor information with a two-hop mesh device. The two-hop mesh device may be a mesh device within the second mesh network that is one hop further from the second mesh network border. For example, the two-hop mesh device may be a parent of the one-hop mesh device.
[00147] Neighbor information may include a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field.
The neighbor information may be compiled by the one-hop mesh device for every neighboring mesh device with which it is in communication, and used to determine a path for messages to be transmitted. The neighbor information may occur at a pseudo-random periodic interval, for example, once every hour at a random time. This allows all mesh devices in the mesh network to exchange neighbor information and build up a stored neighbor information table. [00148] In process or step 656, the one-hop mesh device may test whether a zero-hop mesh device is accessible. For example, the zero-hop mesh device may be associated with a first mesh network and communicate on a first mesh radio channel. The one-hop mesh device may scan alternate mesh radio channels until an accessible zero-hop mesh device is found. In an alternative, the mesh networks may communicate on different frequencies. If an accessible zero- hop mesh device is not found, the mesh device may assume no zero-hop mesh devices are within radio range and wait a time-out period before re-testing.
[00149] If a zero-hop mesh device is accessible, the procedure may proceed to process or step 658. If a zero-hop mesh device is not accessible, the procedure may proceed to process or step 654 and continue functioning as a node in the second mesh network. The one-hop mesh device may periodically check whether a zero-hop mesh device has become accessible. [00150] In process or step 658, the one-hop mesh device may exchange neighbor information with the zero-hop mesh device. For example, the neighbor information may be compiled from neighbor information exchanges as discussed above. The neighbor information may include, in addition to the contents discussed above, a mesh network identifier for each mesh device indicating the mesh devices are associated with the second mesh network. [00151] In process or step 660, the one-hop mesh device may receive a message for forwarding to the zero-hop mesh device. For example, the one-hop mesh device may desire to transmit a message to a neighbor of the zero-hop device on the first network. Instead of transmitting the message to the second mesh gate associated with the second mesh network, forwarding the message to the first mesh gate associated with the first mesh network over the WAN, and forwarding the message to the correct mesh device on the first mesh network, the one-hop device may request the zero-hop device forward the message. This reduces network load and improves network performance.
[00152] In an alternative embodiment, the message may be addressed to a server. In this example, the one-hop mesh device may lose communication with its associated mesh gate. The
one-hop mesh device may transmit the message to the zero-hop device for forwarding to the associated mesh gate via the first mesh network.
[00153] In an alternative embodiment, the message may be received from a two-hop mesh device for forwarding to the first mesh network. For example, the two-hop mesh device may be a parent of the one-hop mesh device on the second mesh network and desire to transmit a message to the first mesh network. The one-hop and zero-hop mesh devices may forward the message to the first mesh network.
[00154] If a message is received for forwarding, the procedure may proceed to process or step 662. If no message is received for forwarding, the procedure may remain in process or step 660. The one-hop mesh device may continue to function as a node within the second mesh network and periodically check whether a message has been received from the two-hop mesh device for forwarding to the first mesh network.
[00155] In process or step 664, the one-hop mesh device may optionally transmit a status to a server via the zero-hop mesh device. For example, the status may include neighbor information including the two-hop mesh devices. The neighbor information may allow the server to better route message traffic considering the mesh network overlap between the first mesh network and the second mesh network.
[00156] In process or step 666, the one-hop mesh device may optionally test whether a response has been received from the server. For example, the message forwarded on behalf of the two- hop mesh device may require a response from the recipient, whether a mesh device within the first mesh network or the server. The response may be transmitted to the mesh device via the zero-hop mesh device.
[00157] In an alternative embodiment, the server may transmit the message to the mesh device when the second mesh gate has failed. This provides path diversity in case of mesh gate failure. [00158] In process or step 668, the one-hop mesh device may optionally forward the received response to the two-hop mesh device. The one-hop mesh device may check that the two-hop mesh device is in its neighborhood table and forward the message to the two-hop mesh device. [00159] The first mesh network may be on a different mesh radio channel or frequency. The one-hop mesh device may utilize the correct mesh radio channel or frequency when communicating with the zero-hop device. For example, the first mesh network mesh radio channel or frequency may be stored in the neighbor information.
[00160] In process or step 670, the one-hop mesh device may optionally exchange neighbor information with a third mesh network zero-hop device. Similar to the first mesh network zero- hop device, the one-hop mesh device may attempt to detect and exchange neighbor information with a zero-hop mesh device on a third mesh network. This creates a network overlap between the second and third mesh networks.
[00161] In process or step 672, the one-hop mesh device may optionaiiy forward a message to the third mesh network zero-hop device. Similar to the first mesh network zero-hop device, the one-hop mesh device may receive messages from the third mesh network zero-hop device. [00162] In an alternative embodiment, any number of first-hop mesh devices from any number of mesh networks may be supported within the second mesh network, limited only by the radio range and memory capacity of the mesh device. This creates path diversity and network overlap between the mesh networks.
[00163] In operation, the mesh device may interface between any number of mesh networks and the second mesh network. The zero-hop mesh device may be associated with another mesh network and mesh gate. By providing an interface between the second mesh network and the zero-hop mesh devices, network overlap is created and path diversity is provided. This improves mesh network performance and reduces WAN load by allowing mesh network-level communications between mesh networks, instead of requiring all such communications to be forwarded through the WAN.
[00164] Although the above embodiments have been discussed with reference to specific example embodiments, it will be evident that the various modification, combinations and changes can be made to these embodiments. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than in a restrictive sense. The foregoing specification provides a description with reference to specific exemplary embodiments. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
Claims
1. A method comprising: associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; and forwarding a message from the one-hop mesh device to the first mesh network.
2. The method of claim 1 , further comprising: transmitting a status to a server via the first mesh network and the first mesh gate.
3. The method of claim 2, wherein the status includes neighbor information.
4. The method of claim 1 , further comprising: forwarding the message from the one-hop mesh device to a server via the first mesh network and the first mesh gate.
5. The method of claim 1, wherein each neighbor information includes a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field.
6. The method of claim 1, further comprising: forwarding a response from a first mesh network mesh device to the one-hop mesh device.
7. The method of claim 1, further comprising: exchanging neighbor information with a third mesh network one-hop device; and forwarding a message from the third mesh network one-hop device to the first mesh network.
8. The method of claim 1 , wherein the first mesh network and the second mesh network communicate on different radio channel frequencies.
9. A method comprising: associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
10. The method of claim 9, further comprising: transmitting a status to a server via the zero-hop mesh device and the first mesh network.
11. The method of claim 10, wherein the status includes neighbor information.
12. The method of claim 9, further comprising: forwarding a transmission from the two-hop mesh device to the zero-hop mesh device.
13. The method of claim 9, wherein each neighbor information includes a best parent field, a best five parents field, a mesh gate load field, a number of hops to the mesh gate field, and a mesh gate path signal quality field.
14. The method of claim 9, further comprising: receiving a response from the first mesh network via the zero-hop mesh device.
15. The method of claim 9, further comprising: exchanging neighbor information with a third mesh network zero-hop device; and transmitting a message to third mesh network zero-hop device.
16. The method of claim 9, wherein the first mesh network and the second mesh network communicate on different radio channel frequencies.
17. A device comprising: a neighborhood table, the neighborhood table storing mesh network device information; and a radio configured to communicate with a first mesh network and a second mesh network, wherein the device is configured to, in operation: associate with a first mesh gate over the first mesh network, exchange neighbor information stored in the neighborhood table with an accessible same-network mesh device over the first mesh network, detect an accessible one-hop mesh device on the second mesh network, exchange neighbor information stored in the neighborhood table with the one-hop mesh device, and forward a message from the one-hop mesh device to the first mesh network.
18. The device of claim 17, the device further configured to transmit a status to a server via the first mesh network and the first mesh gate.
19. The device of claim 18, wherein the status includes neighbor information.
20. The device of claim 17, the device further configured to forward the message from the one-hop mesh device to a server via the first mesh network and the first mesh gate.
21. A computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method, the method comprising: associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; and forwarding a message from the one-hop mesh device to the first mesh network.
22. A computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method, the method comprising: associating with a second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on a first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
23. A method comprising: associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; forwarding a message from the one-hop mesh device to the first mesh network; associating with the second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on the first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
24. A computer program stored in a computer readable form for execution in a processor and processor coupled memory to execute a method, the method comprising: associating with a first mesh gate over a first mesh network; exchanging neighbor information with an accessible same-network mesh device over the first mesh network; detecting an accessible one-hop mesh device on a second mesh network; exchanging neighbor information with the one-hop mesh device; forwarding a message from the one-hop mesh device to the first mesh network; associating with the second mesh network; exchanging neighbor information with a two-hop mesh device over the second mesh network; detecting an accessible zero-hop mesh device on the first mesh network; exchanging neighbor information with the zero-hop mesh device; and transmitting a message to the zero-hop mesh device for forwarding to the first mesh network.
25. A method for a first mesh device to communicate in an overlapping mesh network environment, the method comprising: associating with a first access point over a first mesh network, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcast from a neighboring mesh device, updating a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determining a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmitting the message to the next device.
26. The method of claim 25, wherein the calculated path is calculated by at least one of: the first mesh device and the first access point.
27. The method of claim 25, wherein the next device is one hop closer to the destination.
28. The method of claim 25, wherein the first access point manages the first mesh network by handling association requests from mesh devices of the first mesh network and maintaining a mesh device information table of mesh devices within the first mesh network.
29. The method of claim 25, wherein the destination is at least one of: a server, an access point, and another mesh device.
30. The method of claim 25, further comprising: responsive to detecting a problem mesh network, deleting entries in the neighborhood table associated with the problem mesh network.
31. The method of claim 25, wherein the calculated path includes mesh devices associated with any number of mesh networks.
32. The method of claim 31, wherein the first mesh device is associated with the first access point when it is included in a neighborhood table of the first access point and utilizes services provided by the first access point.
33. The method of claim 25, wherein the request to transmit is received from at least one of: the first mesh device, and a message received from the neighboring mesh device for forwarding.
34. The method of claim 33, wherein the destination is any access point reachable from the first mesh device.
35. The method of claim 25, wherein an access point is reachable from the first mesh device when there exists a bidirectional path between the access point and the first mesh device over the mesh network.
36. The method of claim 33, wherein the message is received from any access point reachable from the first mesh device.
37. The method of claim 25, wherein the calculated path is received from the first access point and stored in the accessible memory.
38. The method of claim 25, further comprising: responsive to a neighbor request or predetermined trigger, broadcasting neighbor information to neighboring mesh devices.
39. A system for communicating in an overlapping mesh network environment, comprising: a plurality of access points, each access point managing a mesh network; and a plurality of mesh devices, each mesh device associated with a mesh network, wherein each mesh device is configured to:
(i) responsive to receiving a neighbor information broadcast from a neighboring mesh device, update a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier;
(ii) responsive to a request to transmit a message to a destination, determine a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and
(iii) transmit the message to the next device.
40. The system of claim 39, wherein the destination is at least one of: a server, an access point, and another mesh device.
41. The system of claim 39, wherein each mesh device is further configured to: responsive to detecting a problem mesh network, delete entries in the neighborhood table associated with the problem mesh network.
42. The system of claim 39, wherein the calculated path includes mesh devices associated with at least two mesh networks.
43. The system of claim 39, wherein the request to transmit is received from at least one of: the mesh device, and a message received from the neighboring mesh device for forwarding.
44. The system of claim 43, wherein the destination is any access point reachable from the mesh device.
45. The system of claim 43, wherein the message is received from any access point reachable from the mesh device.
46. The system of claim 45, wherein an access point is reachable from the first mesh device when there exists a bidirectional path between the access point and the first mesh device over the mesh network.
47. The system of claim 39, wherein the calculated path is received from an access point and stored in the accessible memory.
48. The system of claim 39, where each mesh device is further configured to: responsive to a neighbor request or predetermined trigger, broadcast the neighbor information to neighboring mesh devices.
49. The system of claim 39, wherein different mesh networks communicate on different predetermined radio frequencies.
50. A mesh device for communicating in an overlapping mesh network environment, comprising: a radio for communicating on a predetermined mesh network channel; a memory for storing a neighborhood table; a processor configured to: associate with a first access point over a first mesh network via the radio, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcasted from a neighboring mesh device, update the neighborhood table stored in the memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determine a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmit the message to the next device via the radio.
51. A computer-readable medium including instructions adapted to execute a method for a first mesh device to communicate in an overlapping mesh network environment, the method comprising: associating with a first access point over a first mesh network, wherein the first access point manages the first mesh network; responsive to receiving a neighbor information broadcasted from a neighboring mesh device, updating a neighborhood table stored in an accessible memory, wherein the neighbor information includes a neighboring mesh device information and a neighboring mesh device network identifier; responsive to a request to transmit a message to a destination, determining a next device, wherein the next device is on a calculated path towards the destination, the path including mesh devices from a plurality of mesh networks; and transmitting the message to the next device.
52. A data structure defined in a computer readable medium, the data structure comprising: a plurality of entries, each of the plurality of entries representing at least one device and storing at least one characteristic of the device; and each of the plurality of entries including a plurality of fields for storing characteristics of at least one neighboring device.
53. The data structure in claim 52, wherein the device comprises a mesh network device.
54. The data structure in claim 52, wherein the plurality of entries are selected to include at least one of and any combination of two or more of the following:: a tree PAN identifier identifying a network tree associated with the mesh device; a neighbor address identifying an address of the mesh device; a neighbor PAN identifier identifying a membership of the mesh device; an average quality specifying an average quality of the mesh device's path to an access point; a number of hops specifying a number of hops between the mesh device and an access point; a minimum quality specifying a minimum quality of the mesh device's path to an access point; and a freshness specifying how recently the mesh device information was received.
55. The data structure in claim 52, wherein the plurality of entries comprise: a tree PAN identifier identifying a network tree associated with the mesh device; a neighbor address identifying an address of the mesh device; a neighbor PAN identifier identifying a membership of the mesh device; an average quality specifying an average quality of the mesh device's path to an access point; a number of hops specifying a number of hops between the mesh device and an access point; a minimum quality specifying a minimum quality of the mesh device's path to an access point; and a freshness indicator specifying how recently the mesh device information was received.
56. The data structure in claim 52, wherein the data structure is stored in an accessible memory on a mesh device or on an access point.
57. The data structure in claim 52, wherein the data structure stores a neighborhood table.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2705090A CA2705090A1 (en) | 2007-11-25 | 2008-11-21 | System and method for operating mesh devices in multi-tree overlapping mesh networks |
EP08851869A EP2215555A4 (en) | 2007-11-25 | 2008-11-21 | System and method for operating mesh devices in multi-tree overlapping mesh networks |
Applications Claiming Priority (54)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US98996107P | 2007-11-25 | 2007-11-25 | |
US98996207P | 2007-11-25 | 2007-11-25 | |
US98996407P | 2007-11-25 | 2007-11-25 | |
US98995707P | 2007-11-25 | 2007-11-25 | |
US98995207P | 2007-11-25 | 2007-11-25 | |
US98995907P | 2007-11-25 | 2007-11-25 | |
US98995107P | 2007-11-25 | 2007-11-25 | |
US98995307P | 2007-11-25 | 2007-11-25 | |
US98995507P | 2007-11-25 | 2007-11-25 | |
US98995407P | 2007-11-25 | 2007-11-25 | |
US98997507P | 2007-11-25 | 2007-11-25 | |
US98995807P | 2007-11-25 | 2007-11-25 | |
US98995007P | 2007-11-25 | 2007-11-25 | |
US98996707P | 2007-11-25 | 2007-11-25 | |
US60/989,958 | 2007-11-25 | ||
US60/989,961 | 2007-11-25 | ||
US60/989,957 | 2007-11-25 | ||
US60/989,959 | 2007-11-25 | ||
US60/989,967 | 2007-11-25 | ||
US60/989,953 | 2007-11-25 | ||
US60/989,950 | 2007-11-25 | ||
US60/989,962 | 2007-11-25 | ||
US60/989,952 | 2007-11-25 | ||
US60/989,951 | 2007-11-25 | ||
US60/989,955 | 2007-11-25 | ||
US60/989,964 | 2007-11-25 | ||
US60/989,954 | 2007-11-25 | ||
US60/989,975 | 2007-11-25 | ||
US99231307P | 2007-12-04 | 2007-12-04 | |
US99231507P | 2007-12-04 | 2007-12-04 | |
US99231207P | 2007-12-04 | 2007-12-04 | |
US60/992,312 | 2007-12-04 | ||
US60/992,315 | 2007-12-04 | ||
US60/992,313 | 2007-12-04 | ||
US2527608P | 2008-01-31 | 2008-01-31 | |
US2527808P | 2008-01-31 | 2008-01-31 | |
US2527708P | 2008-01-31 | 2008-01-31 | |
US2527308P | 2008-01-31 | 2008-01-31 | |
US2527008P | 2008-01-31 | 2008-01-31 | |
US2527908P | 2008-01-31 | 2008-01-31 | |
US2527108P | 2008-01-31 | 2008-01-31 | |
US2528708P | 2008-01-31 | 2008-01-31 | |
US2528208P | 2008-01-31 | 2008-01-31 | |
US61/025,276 | 2008-01-31 | ||
US61/025,282 | 2008-01-31 | ||
US61/025,279 | 2008-01-31 | ||
US61/025,271 | 2008-01-31 | ||
US61/025,277 | 2008-01-31 | ||
US61/025,278 | 2008-01-31 | ||
US61/025,287 | 2008-01-31 | ||
US61/025,273 | 2008-01-31 | ||
US61/025,270 | 2008-01-31 | ||
US9411608P | 2008-09-04 | 2008-09-04 | |
US61/094,116 | 2008-09-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009067254A1 true WO2009067254A1 (en) | 2009-05-28 |
Family
ID=40667803
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2008/013032 WO2009067262A2 (en) | 2007-11-25 | 2008-11-21 | Collector device and system utilizing standardized utility metering protocol |
PCT/US2008/013019 WO2009067251A1 (en) | 2007-11-25 | 2008-11-21 | Communication and message route optimization and messaging in a mesh network |
PCT/US2008/013027 WO2009067259A1 (en) | 2007-11-25 | 2008-11-21 | Transport layer and model for an advanced metering infrastructure (ami) network |
PCT/US2008/013023 WO2009067255A1 (en) | 2007-11-25 | 2008-11-21 | Point-to-point communication within a mesh network |
PCT/US2008/013022 WO2009067254A1 (en) | 2007-11-25 | 2008-11-21 | System and method for operating mesh devices in multi-tree overlapping mesh networks |
PCT/US2008/013021 WO2009067253A1 (en) | 2007-11-25 | 2008-11-21 | Creating and managing association and balancing of a mesh device in a mesh network |
Family Applications Before (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2008/013032 WO2009067262A2 (en) | 2007-11-25 | 2008-11-21 | Collector device and system utilizing standardized utility metering protocol |
PCT/US2008/013019 WO2009067251A1 (en) | 2007-11-25 | 2008-11-21 | Communication and message route optimization and messaging in a mesh network |
PCT/US2008/013027 WO2009067259A1 (en) | 2007-11-25 | 2008-11-21 | Transport layer and model for an advanced metering infrastructure (ami) network |
PCT/US2008/013023 WO2009067255A1 (en) | 2007-11-25 | 2008-11-21 | Point-to-point communication within a mesh network |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2008/013021 WO2009067253A1 (en) | 2007-11-25 | 2008-11-21 | Creating and managing association and balancing of a mesh device in a mesh network |
Country Status (4)
Country | Link |
---|---|
US (7) | US20090135836A1 (en) |
EP (2) | EP2215616B1 (en) |
CA (2) | CA2705090A1 (en) |
WO (6) | WO2009067262A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USRE49334E1 (en) | 2005-10-04 | 2022-12-13 | Hoffberg Family Trust 2 | Multifactorial optimization system and method |
Families Citing this family (208)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8145361B2 (en) * | 2007-08-28 | 2012-03-27 | Consert, Inc. | System and method for manipulating controlled energy using devices to manage customer bills |
US8700187B2 (en) | 2007-08-28 | 2014-04-15 | Consert Inc. | Method and apparatus for actively managing consumption of electric power supplied by one or more electric utilities |
US8542685B2 (en) * | 2007-08-28 | 2013-09-24 | Consert, Inc. | System and method for priority delivery of load management messages on IP-based networks |
US8260470B2 (en) * | 2007-08-28 | 2012-09-04 | Consert, Inc. | System and method for selective disconnection of electrical service to end customers |
US8996183B2 (en) | 2007-08-28 | 2015-03-31 | Consert Inc. | System and method for estimating and providing dispatchable operating reserve energy capacity through use of active load management |
US8131403B2 (en) * | 2007-08-28 | 2012-03-06 | Consert, Inc. | System and method for determining and utilizing customer energy profiles for load control for individual structures, devices, and aggregation of same |
US8890505B2 (en) | 2007-08-28 | 2014-11-18 | Causam Energy, Inc. | System and method for estimating and providing dispatchable operating reserve energy capacity through use of active load management |
US7715951B2 (en) | 2007-08-28 | 2010-05-11 | Consert, Inc. | System and method for managing consumption of power supplied by an electric utility |
US9177323B2 (en) | 2007-08-28 | 2015-11-03 | Causam Energy, Inc. | Systems and methods for determining and utilizing customer energy profiles for load control for individual structures, devices, and aggregation of same |
US9130402B2 (en) | 2007-08-28 | 2015-09-08 | Causam Energy, Inc. | System and method for generating and providing dispatchable operating reserve energy capacity through use of active load management |
US10295969B2 (en) | 2007-08-28 | 2019-05-21 | Causam Energy, Inc. | System and method for generating and providing dispatchable operating reserve energy capacity through use of active load management |
US8527107B2 (en) | 2007-08-28 | 2013-09-03 | Consert Inc. | Method and apparatus for effecting controlled restart of electrical servcie with a utility service area |
US8805552B2 (en) | 2007-08-28 | 2014-08-12 | Causam Energy, Inc. | Method and apparatus for actively managing consumption of electric power over an electric power grid |
US8806239B2 (en) | 2007-08-28 | 2014-08-12 | Causam Energy, Inc. | System, method, and apparatus for actively managing consumption of electric power supplied by one or more electric power grid operators |
EP2203911A4 (en) | 2007-10-25 | 2011-12-28 | Trilliant Networks Inc | Gas meter having ultra-sensitive magnetic material retrofitted onto meter dial and method for performing meter retrofit |
EP2215550A1 (en) | 2007-11-25 | 2010-08-11 | Trilliant Networks, Inc. | Energy use control system and method |
WO2009067256A2 (en) | 2007-11-25 | 2009-05-28 | Trilliant Networks, Inc. | System and method for power outage and restoration notification in an advanced metering infrastructure network |
WO2009067262A2 (en) * | 2007-11-25 | 2009-05-28 | Trilliant Networks, Inc. | Collector device and system utilizing standardized utility metering protocol |
KR100932923B1 (en) * | 2007-12-17 | 2009-12-21 | 한국전자통신연구원 | Method and device for setting routing path in wireless sensor network |
WO2009094264A2 (en) * | 2008-01-24 | 2009-07-30 | Firetide, Inc. | Channel assignment for wireless access networks |
US8699377B2 (en) | 2008-09-04 | 2014-04-15 | Trilliant Networks, Inc. | System and method for implementing mesh network communications using a mesh network protocol |
US9722813B2 (en) | 2008-09-08 | 2017-08-01 | Tendril Networks, Inc. | Consumer directed energy management systems and methods |
US8462707B2 (en) * | 2008-10-01 | 2013-06-11 | Digi International Inc. | Joining a mesh network in a multiple network environment |
US8289182B2 (en) | 2008-11-21 | 2012-10-16 | Trilliant Networks, Inc. | Methods and systems for virtual energy management display |
US9014736B2 (en) * | 2008-11-24 | 2015-04-21 | Plantronics, Inc. | Portable network device for the discovery of nearby devices and services |
WO2010105038A1 (en) | 2009-03-11 | 2010-09-16 | Trilliant Networks, Inc. | Process, device and system for mapping transformers to meters and locating non-technical line losses |
EP2228627B1 (en) * | 2009-03-13 | 2013-10-16 | Actaris SAS | System to assist the deployment of a fixed network for remote reading of meters |
DE102009001821A1 (en) * | 2009-03-24 | 2010-10-07 | Ihp Gmbh - Innovations For High Performance Microelectronics / Leibniz-Institut Für Innovative Mikroelektronik | Packet-forwarding protocol acceleration module and method for a transceiver for fast forwarding of data packets |
TWI410077B (en) * | 2009-04-14 | 2013-09-21 | Univ Nat Chiao Tung | Method of Wrapping Method and Winding Path in Wireless Network Environment |
KR101237502B1 (en) * | 2009-04-16 | 2013-02-27 | 연세대학교 산학협력단 | Scheduling method and synchronization method for scheduling information in ad hoc networks |
US8598986B2 (en) * | 2009-04-28 | 2013-12-03 | Dialight Corporation | Remote monitoring and control of LED based street lights |
CA2760380C (en) | 2009-04-28 | 2016-03-22 | Dialight Corporation | Method and apparatus for multi-zoned illumination |
US8803662B2 (en) * | 2009-04-28 | 2014-08-12 | Dialight Corporation | Remote monitoring and control of LED based street lights |
CA2761038C (en) | 2009-05-08 | 2015-12-08 | Consert Inc. | System and method for estimating and providing dispatchable operating reserve energy capacity through use of active load management |
US8028070B2 (en) * | 2009-05-18 | 2011-09-27 | Microsoft Corporation | Synchronizing tasks between servers |
US8121136B2 (en) | 2009-06-24 | 2012-02-21 | Cisco Technology, Inc. | Dynamic discovery mechanisms via inter-domain routing protocol |
KR101572267B1 (en) * | 2009-06-25 | 2015-11-26 | 삼성전자주식회사 | System and method for mutual authentication between node and sink in the sensor network |
US8626344B2 (en) | 2009-08-21 | 2014-01-07 | Allure Energy, Inc. | Energy management system and method |
US8533362B2 (en) * | 2009-08-07 | 2013-09-10 | Cooper Technologies Company | Methods and apparatus related to an adapter between a premise network and an advanced metering infrastructure (AMI) network |
US20110173457A1 (en) * | 2009-08-14 | 2011-07-14 | Jeffrey Reh | Enhanced security for over the air (ota) firmware changes |
US8498749B2 (en) | 2009-08-21 | 2013-07-30 | Allure Energy, Inc. | Method for zone based energy management system with scalable map interface |
US9209652B2 (en) | 2009-08-21 | 2015-12-08 | Allure Energy, Inc. | Mobile device with scalable map interface for zone based energy management |
US9838255B2 (en) | 2009-08-21 | 2017-12-05 | Samsung Electronics Co., Ltd. | Mobile demand response energy management system with proximity control |
US8217805B2 (en) * | 2009-09-01 | 2012-07-10 | Harris Corporation | Address stripping in a meter reading wireless mesh network and associated system |
US8781462B2 (en) * | 2009-09-28 | 2014-07-15 | Itron, Inc. | Methodology and apparatus for validating network coverage |
US20110080845A1 (en) * | 2009-10-07 | 2011-04-07 | Chun-Hsu Su | Intelligent Node-Matching And Control Configuration For The Wireless Network |
KR101463664B1 (en) | 2009-10-09 | 2014-12-04 | 콘서트 아이엔씨. | Apparatus and method for controlling communications to and from utility service points |
US8532272B2 (en) | 2009-10-21 | 2013-09-10 | Comcast Cable Communications, Llc | Service entry device |
EP2506392A4 (en) * | 2009-11-26 | 2014-02-19 | Toshiba Kk | Energy management apparatus and energy management system |
WO2011094523A1 (en) * | 2010-01-29 | 2011-08-04 | Elster Solutions, Llc | Clearing redundant data in wireless mesh network |
US8855102B2 (en) * | 2010-01-29 | 2014-10-07 | Elster Solutions, Llc | Wireless communications providing interoperability between devices capable of communicating at different data rates |
US8938201B2 (en) * | 2010-04-16 | 2015-01-20 | Spirent Communications, Inc. | WiFi positioning bench test method and instrument |
US8391496B2 (en) * | 2010-06-03 | 2013-03-05 | Digi International Inc. | Smart energy network configuration using an auxiliary gateway |
EP2584791B1 (en) * | 2010-06-18 | 2016-12-14 | Panasonic Intellectual Property Management Co., Ltd. | Communication apparatus and communication method |
WO2012014294A1 (en) * | 2010-07-28 | 2012-02-02 | 富士通株式会社 | Key setting method, node, and network system |
WO2012014295A1 (en) * | 2010-07-28 | 2012-02-02 | 富士通株式会社 | Key setting method, node, and network system |
WO2012014039A2 (en) * | 2010-07-30 | 2012-02-02 | Accenture Global Services Limited | Intelligent core engine |
CA2809034A1 (en) | 2010-08-27 | 2012-03-01 | Randy Frei | System and method for interference free operation of co-located tranceivers |
US9794220B2 (en) | 2010-08-31 | 2017-10-17 | Comcast Cable Communications, Llc | Wireless extension of broadband access |
US9013173B2 (en) | 2010-09-13 | 2015-04-21 | Trilliant Networks, Inc. | Process for detecting energy theft |
US8718798B2 (en) * | 2010-11-09 | 2014-05-06 | General Electric Company | Gateway mirroring of metering data between zigbee networks |
EP2641137A2 (en) | 2010-11-15 | 2013-09-25 | Trilliant Holdings, Inc. | System and method for securely communicating across multiple networks using a single radio |
US8774143B2 (en) * | 2010-11-18 | 2014-07-08 | General Electric Company | System and method of communication using a smart meter |
US20120130659A1 (en) * | 2010-11-22 | 2012-05-24 | Sap Ag | Analysis of Large Data Sets Using Distributed Polynomial Interpolation |
US8667060B2 (en) * | 2010-11-23 | 2014-03-04 | General Electric Company | Data collection from utility meters over advanced metering infrastructure |
PT105400A (en) * | 2010-11-24 | 2012-05-24 | Portugal Telecom Inovacao S A | CONCENTRATOR FOR SENSOR NETWORKS AND REMOTE ACCOUNTERS, SUPPORTING VARIOUS NETWORK ACCESS TECHNOLOGIES, WITH AUTOMATIC RECOVERY STRATEGIES AND SECURITY ACCESS TO SENSORS |
GB2486016A (en) * | 2010-12-02 | 2012-06-06 | Sony Corp | Control of storage devices in an electric power network |
US9282383B2 (en) | 2011-01-14 | 2016-03-08 | Trilliant Incorporated | Process, device and system for volt/VAR optimization |
US8863256B1 (en) | 2011-01-14 | 2014-10-14 | Cisco Technology, Inc. | System and method for enabling secure transactions using flexible identity management in a vehicular environment |
WO2012103072A2 (en) | 2011-01-25 | 2012-08-02 | Trilliant Holdings, Inc. | Aggregated real-time power outages/restoration reporting (rtpor) in a secure mesh network |
US8856323B2 (en) | 2011-02-10 | 2014-10-07 | Trilliant Holdings, Inc. | Device and method for facilitating secure communications over a cellular network |
US9041349B2 (en) | 2011-03-08 | 2015-05-26 | Trilliant Networks, Inc. | System and method for managing load distribution across a power grid |
US8462641B2 (en) * | 2011-03-23 | 2013-06-11 | General Electric Company | Power loss packet priority |
US9151654B2 (en) | 2011-04-26 | 2015-10-06 | Sensus Usa Inc. | Method and apparatus for capturing energy from a meter reading device |
US9258813B2 (en) * | 2011-04-29 | 2016-02-09 | Lg Electronics Inc. | Channel access method and apparatus using the same in wireless local area network system |
US20120280831A1 (en) * | 2011-05-05 | 2012-11-08 | General Electric Company | Calculation of auxiliary value based on meter data from non-smart electronic utility meter |
US8683027B2 (en) * | 2011-06-08 | 2014-03-25 | International Business Machines Corporation | Utilization of uncertainty dependency relationships between items in a data stream |
US9264349B2 (en) | 2011-07-05 | 2016-02-16 | Cisco Technology, Inc. | Dynamic enabling of routing devices in shared-media communication networks |
US8619801B2 (en) * | 2011-07-29 | 2013-12-31 | International Business Machines Corporation | Sharing a transmission control protocol port by a plurality of applications |
US20130027217A1 (en) * | 2011-07-29 | 2013-01-31 | General Electric Company | Systems, Methods, and Apparatus for Automatically Configuring a Utility Meter |
US8717887B2 (en) * | 2011-08-08 | 2014-05-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Scrambling code planning device and method for using same in wireless communication network |
US20130054863A1 (en) | 2011-08-30 | 2013-02-28 | Allure Energy, Inc. | Resource Manager, System And Method For Communicating Resource Management Information For Smart Energy And Media Resources |
JP2013055451A (en) * | 2011-09-02 | 2013-03-21 | Hitachi Kokusai Electric Inc | Radio sensor network system |
US9082294B2 (en) * | 2011-09-14 | 2015-07-14 | Enernoc, Inc. | Apparatus and method for receiving and transporting real time energy data |
US9001787B1 (en) * | 2011-09-20 | 2015-04-07 | Trilliant Networks Inc. | System and method for implementing handover of a hybrid communications module |
US9240895B2 (en) * | 2011-10-13 | 2016-01-19 | General Electric Company | Method, system and device of multicast functionality in an energy portal |
US10200476B2 (en) * | 2011-10-18 | 2019-02-05 | Itron, Inc. | Traffic management and remote configuration in a gateway-based network |
US8717943B2 (en) | 2011-10-18 | 2014-05-06 | Itron, Inc. | Peer-to-peer communications in AMI with source-tree routing |
US8515383B2 (en) * | 2011-11-10 | 2013-08-20 | General Electric Company | Utility powered communications gateway |
EP2645314A1 (en) * | 2012-03-28 | 2013-10-02 | Gemalto SA | Method, device and system for managing a provision of energy |
KR20130127016A (en) * | 2012-04-06 | 2013-11-22 | 한국전자통신연구원 | Apparatus and method for controlling packet flow in multi-stage switch |
US9515920B2 (en) * | 2012-04-20 | 2016-12-06 | Futurewei Technologies, Inc. | Name-based neighbor discovery and multi-hop service discovery in information-centric networks |
US9674589B2 (en) * | 2012-05-04 | 2017-06-06 | Itron, Inc. | Coordinated collection of metering data |
EP2663089A1 (en) * | 2012-05-07 | 2013-11-13 | Kamstrup A/S | Consumption meter with remote control program update |
US9207698B2 (en) | 2012-06-20 | 2015-12-08 | Causam Energy, Inc. | Method and apparatus for actively managing electric power over an electric power grid |
US9461471B2 (en) | 2012-06-20 | 2016-10-04 | Causam Energy, Inc | System and methods for actively managing electric power over an electric power grid and providing revenue grade date usable for settlement |
US9465398B2 (en) | 2012-06-20 | 2016-10-11 | Causam Energy, Inc. | System and methods for actively managing electric power over an electric power grid |
US10679131B2 (en) | 2012-07-12 | 2020-06-09 | Eaton Intelligent Power Limited | System and method for efficient data collection in distributed sensor measurement systems |
US9563215B2 (en) | 2012-07-14 | 2017-02-07 | Causam Energy, Inc. | Method and apparatus for actively managing electric power supply for an electric power grid |
FI124786B (en) * | 2012-07-18 | 2015-01-30 | Arm Finland Oy | Method and device for exchanging messages |
EP2687815A1 (en) * | 2012-07-20 | 2014-01-22 | Hexagon Technology Center GmbH | Measurement machine communication |
US9477239B2 (en) | 2012-07-26 | 2016-10-25 | Honeywell International Inc. | HVAC controller with wireless network based occupancy detection and control |
US9594384B2 (en) | 2012-07-26 | 2017-03-14 | Honeywell International Inc. | Method of associating an HVAC controller with an external web service |
US10075520B2 (en) * | 2012-07-27 | 2018-09-11 | Microsoft Technology Licensing, Llc | Distributed aggregation of real-time metrics for large scale distributed systems |
US10861112B2 (en) | 2012-07-31 | 2020-12-08 | Causam Energy, Inc. | Systems and methods for advanced energy settlements, network-based messaging, and applications supporting the same on a blockchain platform |
US10475138B2 (en) | 2015-09-23 | 2019-11-12 | Causam Energy, Inc. | Systems and methods for advanced energy network |
US8849715B2 (en) | 2012-10-24 | 2014-09-30 | Causam Energy, Inc. | System, method, and apparatus for settlement for participation in an electric power grid |
US9513648B2 (en) | 2012-07-31 | 2016-12-06 | Causam Energy, Inc. | System, method, and apparatus for electric power grid and network management of grid elements |
US8983669B2 (en) | 2012-07-31 | 2015-03-17 | Causam Energy, Inc. | System, method, and data packets for messaging for electric power grid elements over a secure internet protocol network |
US10678279B2 (en) | 2012-08-01 | 2020-06-09 | Tendril Oe, Llc | Optimization of energy use through model-based simulations |
US10095659B2 (en) | 2012-08-03 | 2018-10-09 | Fluke Corporation | Handheld devices, systems, and methods for measuring parameters |
US9247378B2 (en) | 2012-08-07 | 2016-01-26 | Honeywell International Inc. | Method for controlling an HVAC system using a proximity aware mobile device |
CA2885968C (en) * | 2012-09-14 | 2020-08-25 | Silversmith, Inc. | Data packet transport and delivery system and method |
US9689710B2 (en) * | 2012-09-21 | 2017-06-27 | Silver Spring Networks, Inc. | Power outage notification and determination |
US20140089481A1 (en) * | 2012-09-27 | 2014-03-27 | Timothy Verrall | Device broker with dynamic connectivity determination |
US9644991B2 (en) | 2012-10-01 | 2017-05-09 | Cooper Technologies Company | System and method for support of one-way endpoints in two-way wireless networks |
US9730108B2 (en) | 2012-12-14 | 2017-08-08 | Plantronics, Inc. | Network architecture using Wi-Fi devices |
US9253693B2 (en) * | 2012-12-18 | 2016-02-02 | Cisco Technology, Inc. | Optimizing a neighbor list of access points |
US9491795B2 (en) | 2012-12-19 | 2016-11-08 | Gainspan Corporation | Extended connectivity based on wireless paths between stations of a wireless local area network (WLAN) |
US9716530B2 (en) | 2013-01-07 | 2017-07-25 | Samsung Electronics Co., Ltd. | Home automation using near field communication |
US9423779B2 (en) | 2013-02-06 | 2016-08-23 | Tendril Networks, Inc. | Dynamically adaptive personalized smart energy profiles |
US9310815B2 (en) | 2013-02-12 | 2016-04-12 | Tendril Networks, Inc. | Setpoint adjustment-based duty cycling |
US10063499B2 (en) | 2013-03-07 | 2018-08-28 | Samsung Electronics Co., Ltd. | Non-cloud based communication platform for an environment control system |
US9237024B2 (en) | 2013-03-15 | 2016-01-12 | Cooper Technologies Company | Informational broadcast messages and its uses in wireless multihop networks |
WO2014145153A2 (en) * | 2013-03-15 | 2014-09-18 | Neeley John | Automatic recording and graphing of measurement data |
US8824444B1 (en) | 2013-04-19 | 2014-09-02 | Cubic Corporation | Null interface feature in wireless mesh networking device |
US9531704B2 (en) * | 2013-06-25 | 2016-12-27 | Google Inc. | Efficient network layer for IPv6 protocol |
US9191209B2 (en) | 2013-06-25 | 2015-11-17 | Google Inc. | Efficient communication for devices of a home network |
US20150003323A1 (en) * | 2013-06-30 | 2015-01-01 | Vonage Network, Llc | Systems and methods for transitioning a telephony communication between connection paths to preserve communication quality |
US9491261B1 (en) * | 2013-07-29 | 2016-11-08 | Amazon Technologies, Inc. | Remote messaging protocol |
JP6244733B2 (en) * | 2013-08-14 | 2017-12-13 | 富士通株式会社 | Node device, communication system, communication program, and communication method |
BE1021756B1 (en) * | 2013-09-12 | 2016-01-15 | Xemex, Naamloze Vennootschap | COMMUNICATION MODULE FOR TRANSFERRING THE CONSUMPTION DATA OF CONSUMPTION METERS AND DEVICE FOR COLLECTING THESE CONSUMPTION DATA |
US20150148965A1 (en) | 2013-11-22 | 2015-05-28 | Honeywell International Inc. | Method to control a communication rate between a thermostat and a cloud based server |
US9477241B2 (en) | 2013-11-22 | 2016-10-25 | Honeywell International Inc. | HVAC controller with proximity based message latency control |
CN113203168A (en) | 2013-12-11 | 2021-08-03 | 霍尼韦尔国际公司 | Automatic control system for building |
US10885583B2 (en) * | 2013-12-19 | 2021-01-05 | Chicago Mercantile Exchange Inc. | Deterministic and efficient message packet management |
US9766270B2 (en) | 2013-12-30 | 2017-09-19 | Fluke Corporation | Wireless test measurement |
KR102390049B1 (en) | 2014-01-06 | 2022-04-25 | 삼성전자주식회사 | System, device, and apparatus for coordinating environments using network devices and remote sensory information |
EP3092750B1 (en) | 2014-01-06 | 2020-07-15 | Samsung Electronics Co., Ltd. | System, device, and apparatus for coordinating environments using network devices and remote sensory information |
US9699708B2 (en) | 2014-01-17 | 2017-07-04 | Cooper Technologies Company | Dynamically-selectable multi-modal modulation in wireless multihop networks |
BR112016018682B1 (en) * | 2014-02-21 | 2024-01-09 | Landis+Gyr Innovations, Inc | METHOD FOR OPTIMIZING NETWORK PERFORMANCE BY A ONE-NODE PROCESSOR IN AN E-NODE NETWORK |
US11747430B2 (en) * | 2014-02-28 | 2023-09-05 | Tyco Fire & Security Gmbh | Correlation of sensory inputs to identify unauthorized persons |
US10015720B2 (en) | 2014-03-14 | 2018-07-03 | GoTenna, Inc. | System and method for digital communication between computing devices |
JP6403411B2 (en) * | 2014-04-01 | 2018-10-10 | 国立研究開発法人情報通信研究機構 | Wireless communication method |
US9503623B2 (en) | 2014-06-03 | 2016-11-22 | Applied Minds, Llc | Color night vision cameras, systems, and methods thereof |
US20150382278A1 (en) * | 2014-06-25 | 2015-12-31 | Michael F. Fallon | Techniques for Generating a Routing Table for a Mesh Network Having Ad Hoc Connections |
CN106797653B (en) | 2014-10-10 | 2020-11-24 | 瑞典爱立信有限公司 | Wireless device reporting |
US20160161966A1 (en) * | 2014-12-05 | 2016-06-09 | Lahav Gil | Apparatus for chargeable electrical device and/or electrical device, and electrical grid |
JP6474247B2 (en) * | 2014-12-12 | 2019-02-27 | シャープ株式会社 | Wireless telemeter system and wireless communication device |
US9900174B2 (en) | 2015-03-06 | 2018-02-20 | Honeywell International Inc. | Multi-user geofencing for building automation |
US9967391B2 (en) | 2015-03-25 | 2018-05-08 | Honeywell International Inc. | Geo-fencing in a building automation system |
US10802459B2 (en) | 2015-04-27 | 2020-10-13 | Ademco Inc. | Geo-fencing with advanced intelligent recovery |
US9609478B2 (en) | 2015-04-27 | 2017-03-28 | Honeywell International Inc. | Geo-fencing with diagnostic feature |
US10802469B2 (en) | 2015-04-27 | 2020-10-13 | Ademco Inc. | Geo-fencing with diagnostic feature |
US10382918B2 (en) * | 2015-05-14 | 2019-08-13 | Telefonaktiebolaget Lm Ericsson (Publ) | System and methods for monitoring events associated with services of mobile devices |
EP3298710B1 (en) * | 2015-05-22 | 2020-02-26 | Linear Technology Corporation | Low power sensor node operation for wireless network |
WO2017014645A1 (en) * | 2015-07-17 | 2017-01-26 | Vitir As | A centralized controlling system controlling interactions and cooperation between radio-operated devices operating in a mesh network supporting multiple radio communication protocols |
US11172273B2 (en) | 2015-08-10 | 2021-11-09 | Delta Energy & Communications, Inc. | Transformer monitor, communications and data collection device |
US10951962B2 (en) | 2015-08-10 | 2021-03-16 | Delta Energy & Communications, Inc. | Data transfer facilitation to and across a distributed mesh network using a hybrid TV white space, Wi-Fi and advanced metering infrastructure construct |
JP2018528686A (en) * | 2015-08-21 | 2018-09-27 | リニアー テクノロジー エルエルシー | Multiple Access Point Wireless Mesh Network |
US11196621B2 (en) * | 2015-10-02 | 2021-12-07 | Delta Energy & Communications, Inc. | Supplemental and alternative digital data delivery and receipt mesh net work realized through the placement of enhanced transformer mounted monitoring devices |
US10708387B2 (en) * | 2015-10-30 | 2020-07-07 | Novell, Inc. | Service usage metering techniques |
US10057110B2 (en) | 2015-11-06 | 2018-08-21 | Honeywell International Inc. | Site management system with dynamic site threat level based on geo-location data |
US9628951B1 (en) | 2015-11-11 | 2017-04-18 | Honeywell International Inc. | Methods and systems for performing geofencing with reduced power consumption |
US10516965B2 (en) | 2015-11-11 | 2019-12-24 | Ademco Inc. | HVAC control using geofencing |
US11030595B1 (en) * | 2015-11-16 | 2021-06-08 | Wells Fargo Bank, N.A. | Integrated utility distribution and automated billing |
US9860697B2 (en) | 2015-12-09 | 2018-01-02 | Honeywell International Inc. | Methods and systems for automatic adjustment of a geofence size |
US9560482B1 (en) | 2015-12-09 | 2017-01-31 | Honeywell International Inc. | User or automated selection of enhanced geo-fencing |
US10605472B2 (en) | 2016-02-19 | 2020-03-31 | Ademco Inc. | Multiple adaptive geo-fences for a building |
MX2018010238A (en) | 2016-02-24 | 2019-06-06 | Delta Energy & Communications Inc | Distributed 802.11s mesh network using transformer module hardware for the capture and transmission of data. |
US10866568B2 (en) | 2016-04-01 | 2020-12-15 | Tendril Oe, Llc | Orchestrated energy |
US20170303177A1 (en) * | 2016-04-16 | 2017-10-19 | General Electric Company | Methods and systems for load balancing in mesh networks |
US10488062B2 (en) | 2016-07-22 | 2019-11-26 | Ademco Inc. | Geofence plus schedule for a building controller |
US10302322B2 (en) | 2016-07-22 | 2019-05-28 | Ademco Inc. | Triage of initial schedule setup for an HVAC controller |
US10405264B2 (en) * | 2016-10-17 | 2019-09-03 | WiSilica Inc. | Bulk pairing for mesh networks |
US10771345B1 (en) * | 2016-12-28 | 2020-09-08 | Amazon Technologies, Inc. | Network monitoring service |
WO2018195229A1 (en) * | 2017-04-18 | 2018-10-25 | Atsushi Kasuya | Packet forwarding mechanism |
US10317102B2 (en) | 2017-04-18 | 2019-06-11 | Ademco Inc. | Geofencing for thermostatic control |
CN109587189B (en) * | 2017-09-28 | 2022-04-29 | 中兴通讯股份有限公司 | Node management method and device |
FI127549B (en) * | 2017-09-29 | 2018-08-31 | Robotonchip Oy | Executing runtime programmable applications |
US10563884B2 (en) | 2018-01-29 | 2020-02-18 | Lennox Industries Inc. | Auto addressing for HVAC units |
US10944669B1 (en) | 2018-02-09 | 2021-03-09 | GoTenna, Inc. | System and method for efficient network-wide broadcast in a multi-hop wireless network using packet echos |
CN111886848A (en) * | 2018-03-23 | 2020-11-03 | 昕诺飞控股有限公司 | Method and apparatus for querying address advertisement messages in a communication network |
EP3785467A1 (en) | 2018-04-24 | 2021-03-03 | Carrier Corporation | Automated routing in a mesh network of wireless messaging devices |
EP3785468A1 (en) | 2018-04-24 | 2021-03-03 | Carrier Corporation | Automated routing in a mesh network of wireless messaging devices |
KR102114992B1 (en) * | 2018-04-25 | 2020-05-25 | (주)휴맥스 | Wireless communication equipment and method for configuring mesh network thereof |
EP3831021A1 (en) | 2018-07-27 | 2021-06-09 | Gotenna Inc. | VINEtm ZERO-CONTROL ROUTING USING DATA PACKET INSPECTION FOR WIRELESS MESH NETWORKS |
US10785672B2 (en) * | 2018-09-11 | 2020-09-22 | WiSilica Inc. | Dynamic wireless network topology for reduced spectrum flooding |
US10736177B2 (en) | 2018-09-11 | 2020-08-04 | WiSilica Inc. | Dynamic wireless network topology for reduced spectrum flooding |
RU2768271C2 (en) * | 2018-10-04 | 2022-03-23 | Телефонактиеболагет Лм Эрикссон (Пабл) | Sending reports by wireless communication device |
DE102018009806A1 (en) * | 2018-12-14 | 2020-06-18 | Diehl Metering S.A.S. | Process for collecting data as well as sensor, data collector and measurement data information network |
DE102018009825A1 (en) * | 2018-12-14 | 2020-06-18 | Diehl Metering S.A.S. | Process for collecting data as well as sensor and supply network |
DE102018009823A1 (en) * | 2018-12-14 | 2020-06-18 | Diehl Metering S.A.S. | Process for collecting data, sensor and supply network |
DE102018009821A1 (en) * | 2018-12-14 | 2020-06-18 | Diehl Metering S.A.S. | Process for collecting data as well as sensor, data collector and measurement data information network |
WO2020185707A1 (en) | 2019-03-08 | 2020-09-17 | goTenna Inc. | Method for utilization-based traffic throttling in a wireless mesh network |
US11212870B2 (en) * | 2019-04-02 | 2021-12-28 | Elear Solutions Tech Private Limited | Method and system for managing a private, decentralized, secure, IP-based peer-to-peer mesh overlay network |
US12003796B2 (en) * | 2019-04-08 | 2024-06-04 | Palo Alto Networks, Inc. | Context-aware content delivery |
US11606829B2 (en) | 2019-06-18 | 2023-03-14 | Kyndryl, Inc. | Facilitation of data transmission in low connectivity areas |
US11206183B2 (en) | 2019-07-11 | 2021-12-21 | Synap Technologies Limited. | Network protocol method for mesh capability in narrow-band wireless networks |
US10560322B1 (en) | 2019-07-11 | 2020-02-11 | Synap Technologies Ltd. | Network protocol for mesh capability in narrow-band wireless networks |
US11149975B2 (en) | 2019-07-24 | 2021-10-19 | Uplight, Inc. | Adaptive thermal comfort learning for optimized HVAC control |
GB2586966B (en) * | 2019-08-30 | 2022-05-18 | Smarter Data Man Limited | Communication system |
FI129763B (en) | 2020-03-04 | 2022-08-15 | Wirepas Oy | Addressing system for a wireless communication network |
CN113472664B (en) * | 2020-03-31 | 2022-09-16 | 华为技术有限公司 | Method and device for storing routing information |
WO2022079543A2 (en) * | 2020-10-15 | 2022-04-21 | Rathod Yogesh | User application store, platform, network, discovery, presentation and connecting with or synchronizing or accessing user data of users from/to parent application |
US11601395B1 (en) * | 2021-12-22 | 2023-03-07 | Uab 360 It | Updating parameters in a mesh network |
US20240027230A1 (en) * | 2022-03-28 | 2024-01-25 | Rg-5 Company | Dual transceiver board module |
CN116074661B (en) * | 2022-12-22 | 2023-08-22 | 北京邮电大学 | Self-adaptive routing method based on Q learning and related equipment |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040125776A1 (en) * | 2002-12-26 | 2004-07-01 | Haugli Hans C. | Peer-to-peer wireless data communication system with progressive dynamic routing |
US20040157613A1 (en) * | 2003-02-12 | 2004-08-12 | David Steer | Self-selection of radio frequency channels to reduce co-channel and adjacent channel interference in a wireless distributed network |
US20060056368A1 (en) * | 2004-09-10 | 2006-03-16 | Nivis, Llc | System and method for a wireless mesh network of configurable signage |
US20060215673A1 (en) * | 2005-03-11 | 2006-09-28 | Interdigital Technology Corporation | Mesh network configured to autonomously commission a network and manage the network topology |
US7215926B2 (en) * | 2003-12-05 | 2007-05-08 | Microsoft Corporation | Enhanced mode technique for growing mesh networks |
Family Cites Families (458)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4132981A (en) * | 1976-10-21 | 1979-01-02 | Rockwell International Corporation | Self-powered system for measuring and storing consumption of utility meter |
US4190800A (en) * | 1976-11-22 | 1980-02-26 | Scientific-Atlanta, Inc. | Electrical load management system |
US4204195A (en) * | 1977-05-23 | 1980-05-20 | General Electric Company | Meter terminal unit for use in automatic remote meter reading and control system |
US4254472A (en) * | 1978-08-14 | 1981-03-03 | The Valeron Corporation | Remote metering system |
US4322842A (en) * | 1979-10-23 | 1982-03-30 | Altran Electronics | Broadcast system for distribution automation and remote metering |
US4396915A (en) | 1980-03-31 | 1983-08-02 | General Electric Company | Automatic meter reading and control system |
US4425628A (en) * | 1981-05-26 | 1984-01-10 | General Electric Company | Control module for engergy management system |
US4638314A (en) * | 1984-01-12 | 1987-01-20 | American Science And Engineering, Inc. | Meter transponder hybrid |
US4644320A (en) * | 1984-09-14 | 1987-02-17 | Carr R Stephen | Home energy monitoring and control system |
US4749992B1 (en) * | 1986-07-03 | 1996-06-11 | Total Energy Management Consul | Utility monitoring and control system |
US4792946A (en) | 1987-04-07 | 1988-12-20 | Spectrum Electronics, Inc. | Wireless local area network for use in neighborhoods |
US5010568A (en) | 1989-04-04 | 1991-04-23 | Sparton Corporation | Remote meter reading method and apparatus |
US5007052A (en) | 1989-04-11 | 1991-04-09 | Metricom, Inc. | Method for routing packets by squelched flooding |
US5138615A (en) * | 1989-06-22 | 1992-08-11 | Digital Equipment Corporation | Reconfiguration system and method for high-speed mesh connected local area network |
US5115433A (en) | 1989-07-18 | 1992-05-19 | Metricom, Inc. | Method and system for routing packets in a packet communication network |
US4939726A (en) | 1989-07-18 | 1990-07-03 | Metricom, Inc. | Method for routing packets in a packet communication network |
US5553094A (en) | 1990-02-15 | 1996-09-03 | Iris Systems, Inc. | Radio communication network for remote data generating stations |
US5056107A (en) | 1990-02-15 | 1991-10-08 | Iris Systems Inc. | Radio communication network for remote data generating stations |
US5673252A (en) | 1990-02-15 | 1997-09-30 | Itron, Inc. | Communications protocol for remote data generating stations |
US5130987A (en) | 1990-03-23 | 1992-07-14 | Metricom, Inc. | Method for synchronizing a wide area network without global synchronizing |
US5079768A (en) * | 1990-03-23 | 1992-01-07 | Metricom, Inc. | Method for frequency sharing in frequency hopping communications network |
US5077753A (en) | 1990-04-09 | 1991-12-31 | Proxim, Inc. | Radio communication system using spread spectrum techniques |
US5216623A (en) * | 1990-06-06 | 1993-06-01 | M. T. Mcbrian, Inc. | System and method for monitoring and analyzing energy characteristics |
US5117422A (en) | 1990-07-09 | 1992-05-26 | Itt Corporation | Method for providing an efficient and adaptive management of message routing in a multi-platform and apparatus communication system |
US5159592A (en) | 1990-10-29 | 1992-10-27 | International Business Machines Corporation | Network address management for a wired network supporting wireless communication to a plurality of mobile users |
CA2054591C (en) | 1991-02-28 | 1996-09-03 | Giovanni Vannucci | Wireless telecommunication systems |
CA2040234C (en) * | 1991-04-11 | 2000-01-04 | Steven Messenger | Wireless coupling of devices to wired network |
US5394436A (en) | 1991-10-01 | 1995-02-28 | Norand Corporation | Radio frequency local area network |
US5844893A (en) | 1991-05-14 | 1998-12-01 | Norand Corporation | System for coupling host computer meanswith base transceiver units on a local area network |
US6407991B1 (en) * | 1993-05-06 | 2002-06-18 | Intermec Ip Corp. | Communication network providing wireless and hard-wired dynamic routing |
US6084867A (en) | 1991-10-01 | 2000-07-04 | Intermec Ip Corp. | Apparatus and method of routing data in a radio frequency local area network |
US6400702B1 (en) * | 1991-10-01 | 2002-06-04 | Intermec Ip Corp. | Radio frequency local area network |
US5974236A (en) | 1992-03-25 | 1999-10-26 | Aes Corporation | Dynamically reconfigurable communications network and method |
US5761083A (en) | 1992-03-25 | 1998-06-02 | Brown, Jr.; Robert J. | Energy management and home automation system |
US5544036A (en) | 1992-03-25 | 1996-08-06 | Brown, Jr.; Robert J. | Energy management and home automation system |
AU4661793A (en) * | 1992-07-02 | 1994-01-31 | Wellfleet Communications | Data packet processing method and apparatus |
US5442633A (en) | 1992-07-08 | 1995-08-15 | International Business Machines Corporation | Shortcut network layer routing for mobile hosts |
EP0582373B1 (en) * | 1992-07-17 | 1999-10-06 | Sun Microsystems, Inc. | Method and apparatus for implementing self-organization in a wireless local area network |
IT1257167B (en) | 1992-10-27 | 1996-01-05 | METHOD FOR IMPROVING THE MANAGEMENT OF DISTRIBUTION NETWORKS, IN PARTICULAR OF GAS, WATER, ELECTRICITY, HEAT. | |
US6970434B1 (en) | 1995-06-07 | 2005-11-29 | Broadcom Corporation | Hierarchical communication system providing intelligent data, program and processing migration |
GB9312836D0 (en) | 1993-06-22 | 1993-08-04 | Schlumberger Ind Ltd | Multipoint to point radiocommunications network |
US5528507A (en) | 1993-08-11 | 1996-06-18 | First Pacific Networks | System for utility demand monitoring and control using a distribution network |
US5465398A (en) | 1993-10-07 | 1995-11-07 | Metricom, Inc. | Automatic power level control of a packet communication link |
DE69434586T2 (en) | 1993-11-04 | 2006-11-09 | Broadcom Corp., Irvine | COMMUNICATION NETWORK WITH WIRELESS AND WIRE-LINKED DYNAMIC CONDUCTIVITY |
US5608780A (en) * | 1993-11-24 | 1997-03-04 | Lucent Technologies Inc. | Wireless communication system having base units which extracts channel and setup information from nearby base units |
US5530963A (en) | 1993-12-16 | 1996-06-25 | International Business Machines Corporation | Method and system for maintaining routing between mobile workstations and selected network workstation using routing table within each router device in the network |
US5471469A (en) | 1994-02-08 | 1995-11-28 | Metricon, Inc. | Method of resolving media contention in radio communication links |
US5400338A (en) * | 1994-02-08 | 1995-03-21 | Metricom, Inc. | Parasitic adoption of coordinate-based addressing by roaming node |
US5453977A (en) | 1994-02-08 | 1995-09-26 | Metricom, Inc. | Method for network configuration via third party query |
US5963457A (en) | 1994-03-18 | 1999-10-05 | Hitachi, Ltd. | Electrical power distribution monitoring system and method |
US5430729A (en) | 1994-04-04 | 1995-07-04 | Motorola, Inc. | Method and apparatus for adaptive directed route randomization and distribution in a richly connected communication network |
US5488608A (en) * | 1994-04-14 | 1996-01-30 | Metricom, Inc. | Method and system for routing packets in a packet communication network using locally constructed routing tables |
US5467345A (en) | 1994-05-31 | 1995-11-14 | Motorola, Inc. | Packet routing system and method therefor |
US5479400A (en) | 1994-06-06 | 1995-12-26 | Metricom, Inc. | Transceiver sharing between access and backhaul in a wireless digital communication system |
US5903566A (en) | 1994-06-24 | 1999-05-11 | Metricom, Inc. | Method for distributing program code to intelligent nodes in a wireless mesh data communication network |
US5515369A (en) | 1994-06-24 | 1996-05-07 | Metricom, Inc. | Method for frequency sharing and frequency punchout in frequency hopping communications network |
US5570084A (en) | 1994-06-28 | 1996-10-29 | Metricom, Inc. | Method of loose source routing over disparate network types in a packet communication network |
CA2129199C (en) | 1994-07-29 | 1999-07-20 | Roger Y.M. Cheung | Method and apparatus for bridging wireless lan to a wired lan |
US5696501A (en) | 1994-08-02 | 1997-12-09 | General Electric Company | Method and apparatus for performing the register functions for a plurality of metering devices at a common node |
US5758331A (en) | 1994-08-15 | 1998-05-26 | Clear With Computers, Inc. | Computer-assisted sales system for utilities |
US5490139A (en) | 1994-09-28 | 1996-02-06 | International Business Machines Corporation | Mobility enabling access point architecture for wireless attachment to source routing networks |
MY123040A (en) | 1994-12-19 | 2006-05-31 | Salbu Res And Dev Proprietary Ltd | Multi-hop packet radio networks |
US5727057A (en) * | 1994-12-27 | 1998-03-10 | Ag Communication Systems Corporation | Storage, transmission, communication and access to geographical positioning data linked with standard telephony numbering and encoded for use in telecommunications and related services |
US6988025B2 (en) | 2000-11-28 | 2006-01-17 | Power Measurement Ltd. | System and method for implementing XML on an energy management device |
US7188003B2 (en) | 1994-12-30 | 2007-03-06 | Power Measurement Ltd. | System and method for securing energy management systems |
US5659300A (en) | 1995-01-30 | 1997-08-19 | Innovatec Corporation | Meter for measuring volumetric consumption of a commodity |
US7133845B1 (en) | 1995-02-13 | 2006-11-07 | Intertrust Technologies Corp. | System and methods for secure transaction management and electronic rights protection |
US5572528A (en) | 1995-03-20 | 1996-11-05 | Novell, Inc. | Mobile networking method and apparatus |
US5596722A (en) * | 1995-04-03 | 1997-01-21 | Motorola, Inc. | Packet routing system and method for achieving uniform link usage and minimizing link load |
US5608721A (en) * | 1995-04-03 | 1997-03-04 | Motorola, Inc. | Communications network and method which implement diversified routing |
US5757783A (en) | 1995-06-15 | 1998-05-26 | Lucent Technologies Inc. | Method and apparatus for routing ATM cells in an AD-ATM LAN |
US5822309A (en) | 1995-06-15 | 1998-10-13 | Lucent Technologies Inc. | Signaling and control architecture for an ad-hoc ATM LAN |
US5623495A (en) | 1995-06-15 | 1997-04-22 | Lucent Technologies Inc. | Portable base station architecture for an AD-HOC ATM lan |
US5726644A (en) * | 1995-06-30 | 1998-03-10 | Philips Electronics North America Corporation | Lighting control system with packet hopping communication |
US5896566A (en) * | 1995-07-28 | 1999-04-20 | Motorola, Inc. | Method for indicating availability of updated software to portable wireless communication units |
US5898826A (en) * | 1995-11-22 | 1999-04-27 | Intel Corporation | Method and apparatus for deadlock-free routing around an unusable routing component in an N-dimensional network |
US5737318A (en) | 1995-12-27 | 1998-04-07 | Philips Electronics North America Corporation | Method for initializing a wireless, packet-hopping network |
US6195018B1 (en) | 1996-02-07 | 2001-02-27 | Cellnet Data Systems, Inc. | Metering system |
US5896097A (en) * | 1996-03-06 | 1999-04-20 | Schlumberger Resource Management Services, Inc. | System for utility meter communications using a single RF frequency |
US5767790A (en) | 1996-03-07 | 1998-06-16 | Jovellana; Bartolome D. | Automatic utility meter monitor |
US5719564A (en) * | 1996-05-10 | 1998-02-17 | Sears; Lawrence M. | Utility meter reading system |
US5920697A (en) | 1996-07-11 | 1999-07-06 | Microsoft Corporation | Method of automatic updating and use of routing information by programmable and manual routing information configuration based on least lost routing |
US5892758A (en) * | 1996-07-11 | 1999-04-06 | Qualcomm Incorporated | Concentrated subscriber wireless remote telemetry system |
US5748104A (en) | 1996-07-11 | 1998-05-05 | Qualcomm Incorporated | Wireless remote telemetry system |
GB2315197B (en) * | 1996-07-11 | 2000-07-12 | Nokia Mobile Phones Ltd | Method and apparatus for system clock adjustment |
US5774660A (en) * | 1996-08-05 | 1998-06-30 | Resonate, Inc. | World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network |
DE19632261C2 (en) * | 1996-08-09 | 1998-07-09 | Siemens Ag | Method for establishing telecommunication connections between telecommunication devices in wireless telecommunication systems, in particular between DECT devices of a DECT system |
US6075777A (en) * | 1996-08-21 | 2000-06-13 | Lucent Technologies Inc. | Network flow framework for online dynamic channel allocation |
US5987011A (en) | 1996-08-30 | 1999-11-16 | Chai-Keong Toh | Routing method for Ad-Hoc mobile networks |
US6246677B1 (en) * | 1996-09-06 | 2001-06-12 | Innovatec Communications, Llc | Automatic meter reading data communication system |
US6078785A (en) * | 1996-10-15 | 2000-06-20 | Bush; E. William | Demand reporting of electricity consumption by radio in relays to a base station, and demand relays wattmeters so reporting over a wide area |
US5880677A (en) * | 1996-10-15 | 1999-03-09 | Lestician; Guy J. | System for monitoring and controlling electrical consumption, including transceiver communicator control apparatus and alternating current control apparatus |
US6018659A (en) * | 1996-10-17 | 2000-01-25 | The Boeing Company | Airborne broadband communication network |
US6150955A (en) | 1996-10-28 | 2000-11-21 | Tracy Corporation Ii | Apparatus and method for transmitting data via a digital control channel of a digital wireless network |
US6014089A (en) * | 1996-10-28 | 2000-01-11 | Tracy Corporation Ii | Method for transmitting data using a digital control channel of a wireless network |
US5901067A (en) | 1996-11-15 | 1999-05-04 | Kim Y. Kao | System for interactively selecting and activating groups of electrically powered devices |
US7143204B1 (en) | 1996-11-15 | 2006-11-28 | Logiclink Corporation | Method and apparatus for suspending or adjusting billing charge for usage of electrically powered devices if abnormal or halt condition detected |
US6839775B1 (en) * | 1996-11-15 | 2005-01-04 | Kim Y. Kao | Method and apparatus for vending machine controller configured to monitor and analyze power profiles for plurality of motor coils to determine condition of vending machine |
US7054271B2 (en) * | 1996-12-06 | 2006-05-30 | Ipco, Llc | Wireless network system and method for providing same |
US6044062A (en) * | 1996-12-06 | 2000-03-28 | Communique, Llc | Wireless network system and method for providing same |
JP3097581B2 (en) | 1996-12-27 | 2000-10-10 | 日本電気株式会社 | Ad-hoc local area network configuration method, communication method and terminal |
US5894422A (en) * | 1997-01-27 | 1999-04-13 | Chasek; Norman E. | System and methods that facilitate the introduction of market based economic models for electric power |
US7046682B2 (en) | 1997-02-12 | 2006-05-16 | Elster Electricity, Llc. | Network-enabled, extensible metering system |
AR011440A1 (en) | 1997-02-12 | 2000-08-16 | Abb Power T & D Co | ELECTRONIC MEASUREMENT PROVISION |
US7079810B2 (en) | 1997-02-14 | 2006-07-18 | Statsignal Ipc, Llc | System and method for communicating with a remote communication unit via the public switched telephone network (PSTN) |
US6233327B1 (en) | 1997-02-14 | 2001-05-15 | Statsignal Systems, Inc. | Multi-function general purpose transceiver |
US6618578B1 (en) | 1997-02-14 | 2003-09-09 | Statsignal Systems, Inc | System and method for communicating with a remote communication unit via the public switched telephone network (PSTN) |
US6628764B1 (en) | 1997-02-14 | 2003-09-30 | Statsignal Systems, Inc. | System for requesting service of a vending machine |
US6430268B1 (en) | 1997-09-20 | 2002-08-06 | Statsignal Systems, Inc. | Systems for requesting service of a vending machine |
US7137550B1 (en) | 1997-02-14 | 2006-11-21 | Statsignal Ipc, Llc | Transmitter for accessing automated financial transaction machines |
US5926531A (en) | 1997-02-14 | 1999-07-20 | Statsignal Systems, Inc. | Transmitter for accessing pay-type telephones |
CN1153352C (en) | 1997-03-18 | 2004-06-09 | 皇家菲利浦电子有限公司 | Receiver tuning system |
US5898387A (en) | 1997-03-26 | 1999-04-27 | Scientific-Atlanta, Inc. | Modular meter based utility gateway enclosure |
US6118269A (en) | 1997-03-26 | 2000-09-12 | Comverge Technologies, Inc. | Electric meter tamper detection circuit for sensing electric meter removal |
US6073169A (en) * | 1997-04-08 | 2000-06-06 | Abb Power T&D Company Inc. | Automatic meter reading system employing common broadcast command channel |
US6457054B1 (en) | 1997-05-15 | 2002-09-24 | Intel Corporation | System for reducing user-visibility latency in network transactions |
US5874903A (en) * | 1997-06-06 | 1999-02-23 | Abb Power T & D Company Inc. | RF repeater for automatic meter reading system |
US5991806A (en) | 1997-06-09 | 1999-11-23 | Dell Usa, L.P. | Dynamic system control via messaging in a network management system |
US5914672A (en) | 1997-06-13 | 1999-06-22 | Whisper Communications Incorporated | System for field installation of a remote meter interface |
US6108699A (en) | 1997-06-27 | 2000-08-22 | Sun Microsystems, Inc. | System and method for modifying membership in a clustered distributed computer system and updating system configuration |
US6058355A (en) * | 1997-06-30 | 2000-05-02 | Ericsson Inc. | Automatic power outage notification via CEBus interface |
JP3180726B2 (en) * | 1997-08-05 | 2001-06-25 | 日本電気株式会社 | Mobile terminal control method |
US6414952B2 (en) | 1997-08-28 | 2002-07-02 | Broadcom Homenetworking, Inc. | Virtual gateway system and method |
US6538577B1 (en) | 1997-09-05 | 2003-03-25 | Silver Springs Networks, Inc. | Electronic electric meter for networked meter reading |
US20080129538A1 (en) | 1999-02-23 | 2008-06-05 | Raj Vaswani | Electronic electric meter for networked meter reading |
US6088659A (en) | 1997-09-11 | 2000-07-11 | Abb Power T&D Company Inc. | Automated meter reading system |
AU9480798A (en) | 1997-09-12 | 1999-03-29 | Williams Wireless, Inc. | Wide area remote telemetry |
US9197599B1 (en) | 1997-09-26 | 2015-11-24 | Verizon Patent And Licensing Inc. | Integrated business system for web based telecommunications management |
US20020120569A1 (en) | 1997-10-16 | 2002-08-29 | Day Mark E. | System and method for communication between remote locations |
US5986574A (en) | 1997-10-16 | 1999-11-16 | Peco Energy Company | System and method for communication between remote locations |
US6711166B1 (en) * | 1997-12-10 | 2004-03-23 | Radvision Ltd. | System and method for packet network trunking |
JPH11187443A (en) * | 1997-12-25 | 1999-07-09 | Sony Corp | Portable radio information terminal equipment, screen operation method, record medium, and microcomputer |
US6556830B1 (en) * | 1998-02-02 | 2003-04-29 | Ericsson Inc. | Coverage area sectorization in time division multiple access/frequency-time division duplex communications systems |
SE9801172D0 (en) | 1998-04-01 | 1998-04-01 | Ericsson Telefon Ab L M | Cell selection in a system with different cell capabilities |
NO309550B1 (en) | 1998-04-07 | 2001-02-12 | It & Process As | System for controlling the power consumption of a user of electrical power |
US6778099B1 (en) | 1998-05-01 | 2004-08-17 | Elster Electricity, Llc | Wireless area network communications module for utility meters |
US6311105B1 (en) | 1998-05-29 | 2001-10-30 | Powerweb, Inc. | Multi-utility energy control system |
US6553355B1 (en) * | 1998-05-29 | 2003-04-22 | Indranet Technologies Limited | Autopoietic network system endowed with distributed artificial intelligence for the supply of high volume high-speed multimedia telesthesia telemetry, telekinesis, telepresence, telemanagement, telecommunications, and data processing services |
US6122603A (en) | 1998-05-29 | 2000-09-19 | Powerweb, Inc. | Multi-utility energy control system with dashboard |
US6445691B2 (en) * | 1998-06-08 | 2002-09-03 | Koninklijke Philips Electronics N. V. | Wireless coupling of standardized networks and non-standardized nodes |
US6891838B1 (en) | 1998-06-22 | 2005-05-10 | Statsignal Ipc, Llc | System and method for monitoring and controlling residential devices |
US6914533B2 (en) | 1998-06-22 | 2005-07-05 | Statsignal Ipc Llc | System and method for accessing residential monitoring devices |
US6218953B1 (en) | 1998-10-14 | 2001-04-17 | Statsignal Systems, Inc. | System and method for monitoring the light level around an ATM |
US6522974B2 (en) * | 2000-03-01 | 2003-02-18 | Westerngeco, L.L.C. | Method for vibrator sweep analysis and synthesis |
US6437692B1 (en) | 1998-06-22 | 2002-08-20 | Statsignal Systems, Inc. | System and method for monitoring and controlling remote devices |
US6914893B2 (en) | 1998-06-22 | 2005-07-05 | Statsignal Ipc, Llc | System and method for monitoring and controlling remote devices |
US6028522A (en) * | 1998-10-14 | 2000-02-22 | Statsignal Systems, Inc. | System for monitoring the light level around an ATM |
US6304556B1 (en) | 1998-08-24 | 2001-10-16 | Cornell Research Foundation, Inc. | Routing and mobility management protocols for ad-hoc networks |
US6665620B1 (en) | 1998-08-26 | 2003-12-16 | Siemens Transmission & Distribution, Llc | Utility meter having primary and secondary communication circuits |
US6826620B1 (en) | 1998-08-26 | 2004-11-30 | Paradyne Corporation | Network congestion control system and method |
US6246689B1 (en) * | 1998-09-21 | 2001-06-12 | Lucent Technologies Inc. | Method and apparatus for efficient topology aggregation for networks with hierarchical structure |
US20020013679A1 (en) * | 1998-10-14 | 2002-01-31 | Petite Thomas D. | System and method for monitoring the light level in a lighted area |
US7103511B2 (en) | 1998-10-14 | 2006-09-05 | Statsignal Ipc, Llc | Wireless communication networks for providing remote monitoring of devices |
US6480497B1 (en) | 1998-11-23 | 2002-11-12 | Ricochet Networks, Inc. | Method and apparatus for maximizing data throughput in a packet radio mesh network |
US6636894B1 (en) | 1998-12-08 | 2003-10-21 | Nomadix, Inc. | Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability |
US6718137B1 (en) * | 1999-01-05 | 2004-04-06 | Ciena Corporation | Method and apparatus for configuration by a first network element based on operating parameters of a second network element |
US20080136667A1 (en) | 1999-02-23 | 2008-06-12 | Raj Vaswani | Network for automated meter reading |
EP1169691A1 (en) | 1999-03-12 | 2002-01-09 | Graviton, Inc. | Systems and methods for network based sensing and distributed sensor, data and memory management |
US6747557B1 (en) | 1999-03-18 | 2004-06-08 | Statsignal Systems, Inc. | System and method for signaling a weather alert condition to a residential environment |
US7263073B2 (en) | 1999-03-18 | 2007-08-28 | Statsignal Ipc, Llc | Systems and methods for enabling a mobile user to notify an automated monitoring system of an emergency situation |
US20040183687A1 (en) | 1999-03-18 | 2004-09-23 | Petite Thomas D. | System and method for signaling a weather alert condition to a residential environment |
US7650425B2 (en) * | 1999-03-18 | 2010-01-19 | Sipco, Llc | System and method for controlling communication between a host computer and communication devices associated with remote devices in an automated monitoring system |
US6751672B1 (en) * | 1999-06-02 | 2004-06-15 | Nortel Networks Limited | Efficient dynamic home agent discovery algorithm and system |
US6300881B1 (en) | 1999-06-09 | 2001-10-09 | Motorola, Inc. | Data transfer system and method for communicating utility consumption data over power line carriers |
US6954814B1 (en) | 1999-06-10 | 2005-10-11 | Amron Technologies Inc. | Method and system for monitoring and transmitting utility status via universal communications interface |
US7231482B2 (en) | 2000-06-09 | 2007-06-12 | Universal Smart Technologies, Llc. | Method and system for monitoring and transmitting utility status via universal communications interface |
US7185131B2 (en) * | 1999-06-10 | 2007-02-27 | Amron Technologies, Inc. | Host-client utility meter systems and methods for communicating with the same |
US6725281B1 (en) * | 1999-06-11 | 2004-04-20 | Microsoft Corporation | Synchronization of controlled device state using state table and eventing in data-driven remote device control model |
US6681110B1 (en) | 1999-07-02 | 2004-01-20 | Musco Corporation | Means and apparatus for control of remote electrical devices |
US6691173B2 (en) * | 1999-07-06 | 2004-02-10 | Widcomm, Inc. | Distributed management of an extended network containing short-range wireless links |
US6785592B1 (en) | 1999-07-16 | 2004-08-31 | Perot Systems Corporation | System and method for energy management |
JP3669619B2 (en) * | 1999-09-06 | 2005-07-13 | 富士通株式会社 | Software updating method and apparatus for wireless terminal device |
US6980973B1 (en) | 1999-09-07 | 2005-12-27 | Visa International Service Association | Self-paying smart utility meter and payment service |
US6751455B1 (en) * | 1999-09-17 | 2004-06-15 | The Regents Of The University Of California | Power- and bandwidth-adaptive in-home wireless communications system with power-grid-powered agents and battery-powered clients |
US6976062B1 (en) | 1999-09-22 | 2005-12-13 | Intermec Ip Corp. | Automated software upgrade utility |
WO2001026334A2 (en) | 1999-10-06 | 2001-04-12 | Sensoria Corporation | Method and apparatus for sensor networking |
US7020701B1 (en) | 1999-10-06 | 2006-03-28 | Sensoria Corporation | Method for collecting and processing data using internetworked wireless integrated network sensors (WINS) |
US6904025B1 (en) * | 1999-10-12 | 2005-06-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Wide area network mobility for IP based networks |
US7315257B2 (en) * | 1999-10-16 | 2008-01-01 | Datamatic, Ltd. | Automated meter reader having high product delivery rate alert generator |
US7042368B2 (en) | 1999-10-16 | 2006-05-09 | Datamatic, Ltd | Automated meter reader device having optical sensor with automatic gain control |
US20060028355A1 (en) * | 1999-10-16 | 2006-02-09 | Tim Patterson | Automated meter reader having peak product delivery rate generator |
US6710721B1 (en) | 1999-10-16 | 2004-03-23 | Datamatic Inc. | Radio frequency automated meter reading device |
ATE287101T1 (en) | 1999-11-01 | 2005-01-15 | Abb Research Ltd | INTEGRATION OF A FIELD CONTROL DEVICE INTO A PLANT CONTROL SYSTEM |
US6909705B1 (en) | 1999-11-02 | 2005-06-21 | Cello Partnership | Integrating wireless local loop networks with cellular networks |
US6697331B1 (en) * | 1999-11-17 | 2004-02-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Link layer acknowledgement and retransmission for cellular telecommunications |
US6535498B1 (en) * | 1999-12-06 | 2003-03-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Route updating in ad-hoc networks |
EP1107508A1 (en) * | 1999-12-06 | 2001-06-13 | Telefonaktiebolaget Lm Ericsson | System, method and computer program product for sending broadcast messages |
US6975613B1 (en) | 1999-12-06 | 2005-12-13 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for scheduling communication sessions in an ad-hoc network |
US6480505B1 (en) | 1999-12-06 | 2002-11-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Batched fair exhaustive polling scheduler |
US6711409B1 (en) * | 1999-12-15 | 2004-03-23 | Bbnt Solutions Llc | Node belonging to multiple clusters in an ad hoc wireless network |
US6885309B1 (en) * | 2000-06-01 | 2005-04-26 | Cellnet Innovations, Inc. | Meter to internet pathway |
US6577671B1 (en) * | 1999-12-29 | 2003-06-10 | Nokia Mobile Phones Limited | Enhanced code allocation method for CDMA systems |
US6298053B1 (en) | 2000-01-14 | 2001-10-02 | Metricom, Inc. | Method and apparatus for connection handoff between connected radios |
US7213063B2 (en) * | 2000-01-18 | 2007-05-01 | Lucent Technologies Inc. | Method, apparatus and system for maintaining connections between computers using connection-oriented protocols |
US8019836B2 (en) | 2002-01-02 | 2011-09-13 | Mesh Comm, Llc | Wireless communication enabled meter and network |
US7379981B2 (en) * | 2000-01-31 | 2008-05-27 | Kenneth W. Garrard | Wireless communication enabled meter and network |
WO2001055865A1 (en) | 2000-01-31 | 2001-08-02 | Telemetry Technologies, Inc. | Wireless communication enabled meter and network |
US20010033554A1 (en) * | 2000-02-18 | 2001-10-25 | Arun Ayyagari | Proxy-bridge connecting remote users to a limited connectivity network |
US6865185B1 (en) * | 2000-02-25 | 2005-03-08 | Cisco Technology, Inc. | Method and system for queuing traffic in a wireless communications network |
US6369769B1 (en) | 2000-02-25 | 2002-04-09 | Innovatec Communications, Llc | Flush mounted pit lid antenna |
US6845091B2 (en) * | 2000-03-16 | 2005-01-18 | Sri International | Mobile ad hoc extensions for the internet |
US6775258B1 (en) | 2000-03-17 | 2004-08-10 | Nokia Corporation | Apparatus, and associated method, for routing packet data in an ad hoc, wireless communication system |
GB0007266D0 (en) | 2000-03-25 | 2000-05-17 | Hewlett Packard Co | Providing location data about a mobile entity |
FR2807235B1 (en) * | 2000-03-30 | 2002-06-28 | Andre Zalkin & Cie Ets | ELECTRIC MOTOR CONTROL DEVICE, METHOD AND PROGRAM |
US7062361B1 (en) | 2000-05-02 | 2006-06-13 | Mark E. Lane | Method and apparatus for controlling power consumption |
US6933857B2 (en) | 2000-05-05 | 2005-08-23 | Charles A. Foote | Method and system for airborne meter communication |
US20020066095A1 (en) | 2000-05-12 | 2002-05-30 | Yueh-O Yu | Process and device for updating personalized products |
US6880086B2 (en) * | 2000-05-20 | 2005-04-12 | Ciena Corporation | Signatures for facilitating hot upgrades of modular software components |
US7487282B2 (en) * | 2000-06-09 | 2009-02-03 | Leach Mark A | Host-client utility meter systems and methods for communicating with the same |
US6900738B2 (en) * | 2000-06-21 | 2005-05-31 | Henry Crichlow | Method and apparatus for reading a meter and providing customer service via the internet |
US6519509B1 (en) * | 2000-06-22 | 2003-02-11 | Stonewater Software, Inc. | System and method for monitoring and controlling energy distribution |
US7072945B1 (en) | 2000-06-30 | 2006-07-04 | Nokia Corporation | Network and method for controlling appliances |
AU2001278923A1 (en) | 2000-07-13 | 2002-01-30 | Nxegen | System and method for monitoring and controlling energy usage |
US7197046B1 (en) | 2000-08-07 | 2007-03-27 | Shrikumar Hariharasubrahmanian | Systems and methods for combined protocol processing protocols |
US6836737B2 (en) | 2000-08-09 | 2004-12-28 | Statsignal Systems, Inc. | Systems and methods for providing remote monitoring of consumption for a utility meter |
US6829216B1 (en) | 2000-08-18 | 2004-12-07 | Hitachi Telecom (U.S.A.), Inc. | Method and system for designing a network |
US7200633B2 (en) * | 2000-08-25 | 2007-04-03 | Ntt Docomo, Inc. | Information delivery system and information delivery method |
US6728514B2 (en) * | 2000-09-08 | 2004-04-27 | Wi-Lan Inc. | Scalable wireless network topology systems and methods |
US20020051269A1 (en) * | 2000-09-29 | 2002-05-02 | Shlomo Margalit | Reconfigurable over-the-air optical data transmission system |
US20020031101A1 (en) * | 2000-11-01 | 2002-03-14 | Petite Thomas D. | System and methods for interconnecting remote devices in an automated monitoring system |
US7016336B2 (en) * | 2000-11-22 | 2006-03-21 | Telefonaktiebolaget L M Ericsson (Publ) | Administrative domains for personal area networks |
US20070136817A1 (en) | 2000-12-07 | 2007-06-14 | Igt | Wager game license management in a peer gaming network |
US6965575B2 (en) * | 2000-12-29 | 2005-11-15 | Tropos Networks | Selection of routing paths based upon path quality of a wireless mesh network |
US6704301B2 (en) * | 2000-12-29 | 2004-03-09 | Tropos Networks, Inc. | Method and apparatus to provide a routing protocol for wireless devices |
US7551562B2 (en) * | 2000-12-29 | 2009-06-23 | Tropos Networks | Determining bidirectional path quality within a wireless mesh network |
FI20010095A (en) * | 2001-01-16 | 2002-07-17 | Nokia Corp | Insurance procedure, monitoring network elements in telecommunication networks, and telecommunication systems |
US6842706B1 (en) * | 2001-01-17 | 2005-01-11 | Smart Disaster Response Technologies, Inc. | Methods, apparatus, media, and signals for managing utility usage |
US6946972B2 (en) | 2001-01-25 | 2005-09-20 | Smartsynch, Inc. | Systems and methods for wirelessly transmitting data from a utility meter |
US6671635B1 (en) | 2001-02-23 | 2003-12-30 | Power Measurement Ltd. | Systems for improved monitoring accuracy of intelligent electronic devices |
AU2002225292A1 (en) | 2001-03-12 | 2002-09-24 | Koninklijke Philips Electronics N.V. | Receiving device for securely storing a content item, and playback device |
JP3700596B2 (en) * | 2001-03-14 | 2005-09-28 | 日本電気株式会社 | Communication network, path setting method, and path setting program |
EP1386432A4 (en) * | 2001-03-21 | 2009-07-15 | John A Stine | An access and routing protocol for ad hoc networks using synchronous collision resolution and node state dissemination |
AUPR441401A0 (en) | 2001-04-12 | 2001-05-17 | Gladwin, Paul | Utility usage rate monitor |
EP1393022B1 (en) * | 2001-05-02 | 2011-04-06 | Invensys Metering Systems/North America Inc. | Add-on module for utility meters |
AR033319A1 (en) | 2001-05-04 | 2003-12-10 | Invensys Metering Systems Nort | PROVISION AND METHOD FOR COMMUNICATION AND CONTROL OF AUTOMATED METER READING |
US20020186619A1 (en) | 2001-05-07 | 2002-12-12 | Reeves Michael H. | Apparatus, system and method for synchronizing a clock with a master time service |
US20020184334A1 (en) * | 2001-06-04 | 2002-12-05 | Cherry Darrel D. | System and method for providing intelligence to network devices |
US20030156715A1 (en) | 2001-06-12 | 2003-08-21 | Reeds James Alexander | Apparatus, system and method for validating integrity of transmitted data |
US7009493B2 (en) * | 2001-06-22 | 2006-03-07 | Matsushita Electric Works, Ltd. | Electronic device with paging for energy curtailment and code generation for manual verification of curtailment |
US6999441B2 (en) * | 2001-06-27 | 2006-02-14 | Ricochet Networks, Inc. | Method and apparatus for contention management in a radio-based packet network |
US6509801B1 (en) * | 2001-06-29 | 2003-01-21 | Sierra Monolithics, Inc. | Multi-gigabit-per-sec clock recovery apparatus and method for optical communications |
US7266840B2 (en) * | 2001-07-12 | 2007-09-04 | Vignette Corporation | Method and system for secure, authorized e-mail based transactions |
CA2394503A1 (en) | 2001-07-23 | 2003-01-23 | Research In Motion Limited | System and method for pushing information to a mobile device |
US7006526B1 (en) * | 2001-07-31 | 2006-02-28 | Cisco Technology, Inc. | Mechanisms for avoiding problems associated with network address protocol translation |
US7277414B2 (en) * | 2001-08-03 | 2007-10-02 | Honeywell International Inc. | Energy aware network management |
US6711512B2 (en) * | 2001-08-07 | 2004-03-23 | Korea Electric Power Data Network Co. Ltd. | Pole transformer load monitoring system using wireless internet network |
US7346463B2 (en) * | 2001-08-09 | 2008-03-18 | Hunt Technologies, Llc | System for controlling electrically-powered devices in an electrical network |
US6993571B2 (en) * | 2001-08-16 | 2006-01-31 | International Business Machines Corporation | Power conservation in a server cluster |
US6993417B2 (en) * | 2001-09-10 | 2006-01-31 | Osann Jr Robert | System for energy sensing analysis and feedback |
KR100452508B1 (en) | 2001-09-25 | 2004-10-12 | 엘지전자 주식회사 | remote detecting equipment using CO-LINE and controlling method therefore |
US7362709B1 (en) | 2001-11-02 | 2008-04-22 | Arizona Board Of Regents | Agile digital communication network with rapid rerouting |
WO2003043285A2 (en) * | 2001-11-13 | 2003-05-22 | Ems Technologies, Inc. | Flow control between performance enhancing proxies over variable bandwidth split links |
US6829347B1 (en) | 2001-12-14 | 2004-12-07 | Nortel Networks Limited | Constraint based routing |
US7106757B2 (en) | 2001-12-19 | 2006-09-12 | Intel Corporation | System and method for streaming multimedia over packet networks |
US7609673B2 (en) | 2002-02-08 | 2009-10-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Packet-based conversational service for a multimedia session in a mobile communications system |
ITMI20012726A1 (en) * | 2001-12-20 | 2003-06-20 | Enel Distribuzione Spa | SYSTEM OF REMOTE CONSUMPTION OF CONSUMPTION AND REMOTE MANAGEMENT OF USERS ALSO DISTRIBUTED OF A DOMESTIC TYPE |
US6744740B2 (en) | 2001-12-21 | 2004-06-01 | Motorola, Inc. | Network protocol for wireless devices utilizing location information |
US6714787B2 (en) * | 2002-01-17 | 2004-03-30 | Motorola, Inc. | Method and apparatus for adapting a routing map for a wireless communications network |
US6882635B2 (en) * | 2002-02-05 | 2005-04-19 | Qualcomm Incorporated | Coexistence between interfering communication systems |
US7626508B2 (en) * | 2002-03-05 | 2009-12-01 | Aeromesh Corporation | Monitoring system and method |
US7058018B1 (en) * | 2002-03-06 | 2006-06-06 | Meshnetworks, Inc. | System and method for using per-packet receive signal strength indication and transmit power levels to compute path loss for a link for use in layer II routing in a wireless communication network |
US6985087B2 (en) * | 2002-03-15 | 2006-01-10 | Qualcomm Inc. | Method and apparatus for wireless remote telemetry using ad-hoc networks |
US6801865B2 (en) | 2002-03-21 | 2004-10-05 | Engage Networks, Inc. | Meter monitoring and tamper protection system and method |
US6831921B2 (en) | 2002-03-27 | 2004-12-14 | James A. Higgins | Wireless internet access system |
WO2003084022A1 (en) | 2002-03-28 | 2003-10-09 | Robertshaw Controls Company | Energy management system and method |
US7230544B2 (en) | 2002-04-22 | 2007-06-12 | Cellnet Innovations, Inc. | Intelligent two-way telemetry |
US20040082203A1 (en) | 2002-05-07 | 2004-04-29 | Oleg Logvinov | Method and apparatus for power theft prevention based on TDR or FDR signature monitoring on LV and MV power lines |
US7987491B2 (en) | 2002-05-10 | 2011-07-26 | Richard Reisman | Method and apparatus for browsing using alternative linkbases |
US7561977B2 (en) | 2002-06-13 | 2009-07-14 | Whirlpool Corporation | Total home energy management system |
US7119713B2 (en) | 2002-06-27 | 2006-10-10 | Elster Electricity, Llc | Dynamic self-configuring metering network |
US20040113810A1 (en) | 2002-06-28 | 2004-06-17 | Mason Robert T. | Data collector for an automated meter reading system |
GB0218452D0 (en) | 2002-08-08 | 2002-09-18 | Lal Depak | Energy consumption monitoring |
US7069438B2 (en) * | 2002-08-19 | 2006-06-27 | Sowl Associates, Inc. | Establishing authenticated network connections |
US20040039817A1 (en) * | 2002-08-26 | 2004-02-26 | Lee Mai Tranh | Enhanced algorithm for initial AP selection and roaming |
US7324453B2 (en) * | 2002-08-30 | 2008-01-29 | Alcatel Lucent | Constraint-based shortest path first method for dynamically switched optical transport networks |
US7009379B2 (en) * | 2002-09-12 | 2006-03-07 | Landis & Gyr, Inc. | Electricity meter with power supply load management |
WO2004030152A2 (en) | 2002-09-30 | 2004-04-08 | Basic Resources, Inc. | Outage notification device and method |
JP3964907B2 (en) * | 2002-10-11 | 2007-08-22 | ノキア コーポレイション | Dynamic tunnel peering with performance optimization |
US6995666B1 (en) | 2002-10-16 | 2006-02-07 | Luttrell Clyde K | Cellemetry-operated railroad switch heater |
US7599323B2 (en) | 2002-10-17 | 2009-10-06 | Alcatel-Lucent Usa Inc. | Multi-interface mobility client |
WO2004047382A1 (en) * | 2002-11-20 | 2004-06-03 | Fujitsu Limited | Radio terminal apparatus |
JP3773049B2 (en) | 2002-11-28 | 2006-05-10 | ヤマハ株式会社 | A musical tone attenuation rate control device that generates decibel linear attenuation rate data according to the position of the knob. |
US20040117788A1 (en) | 2002-12-11 | 2004-06-17 | Jeyhan Karaoguz | Method and system for TV interface for coordinating media exchange with a media peripheral |
JP3799010B2 (en) * | 2002-12-19 | 2006-07-19 | アンリツ株式会社 | Mesh network bridge |
US7366113B1 (en) | 2002-12-27 | 2008-04-29 | At & T Corp. | Adaptive topology discovery in communication networks |
US6859186B2 (en) * | 2003-02-03 | 2005-02-22 | Silver Spring Networks, Inc. | Flush-mounted antenna and transmission system |
US7400264B2 (en) * | 2003-02-14 | 2008-07-15 | Energy Technology Group, Inc. | Automated meter reading system, communication and control network for automated meter reading, meter data collector, and associated methods |
JP4134916B2 (en) * | 2003-02-14 | 2008-08-20 | 松下電器産業株式会社 | Network connection device and network connection switching method |
US7304587B2 (en) * | 2003-02-14 | 2007-12-04 | Energy Technology Group, Inc. | Automated meter reading system, communication and control network for automated meter reading, meter data collector program product, and associated methods |
US20070013547A1 (en) * | 2003-02-14 | 2007-01-18 | Boaz Jon A | Automated meter reading system, communication and control network from automated meter reading, meter data collector, and associated methods |
US20040185845A1 (en) | 2003-02-28 | 2004-09-23 | Microsoft Corporation | Access point to access point range extension |
US7406298B2 (en) | 2003-03-25 | 2008-07-29 | Silver Spring Networks, Inc. | Wireless communication system |
US7089089B2 (en) | 2003-03-31 | 2006-08-08 | Power Measurement Ltd. | Methods and apparatus for retrieving energy readings from an energy monitoring device |
US7010363B2 (en) | 2003-06-13 | 2006-03-07 | Battelle Memorial Institute | Electrical appliance energy consumption control methods and electrical energy consumption systems |
US7562024B2 (en) | 2003-06-18 | 2009-07-14 | Hewlett-Packard Development Company, L.P. | Method and system for addressing client service outages |
US7053853B2 (en) * | 2003-06-26 | 2006-05-30 | Skypilot Network, Inc. | Planar antenna for a wireless mesh network |
WO2005004368A2 (en) | 2003-07-07 | 2005-01-13 | Lg Electronics, Inc. | Upgrade apparatus and its method for home network system |
US7701858B2 (en) | 2003-07-17 | 2010-04-20 | Sensicast Systems | Method and apparatus for wireless communication in a mesh network |
US7251570B2 (en) | 2003-07-18 | 2007-07-31 | Power Measurement Ltd. | Data integrity in a mesh network |
US7321316B2 (en) * | 2003-07-18 | 2008-01-22 | Power Measurement, Ltd. | Grouping mesh clusters |
KR100547788B1 (en) * | 2003-07-31 | 2006-01-31 | 삼성전자주식회사 | High speed personal wireless network and data transmission method capable of communication between devices of piconets |
JP4218451B2 (en) * | 2003-08-05 | 2009-02-04 | 株式会社日立製作所 | License management system, server device and terminal device |
US7336642B2 (en) * | 2003-08-07 | 2008-02-26 | Skypilot Networks, Inc. | Communication protocol for a wireless mesh architecture |
US20070169075A1 (en) | 2003-09-05 | 2007-07-19 | David Lill | Synchronizing and controlling software downloads, such as for utility meter-reading data collection and processing |
US7289887B2 (en) * | 2003-09-08 | 2007-10-30 | Smartsynch, Inc. | Systems and methods for remote power management using IEEE 802 based wireless communication links |
US20050055432A1 (en) * | 2003-09-08 | 2005-03-10 | Smart Synch, Inc. | Systems and methods for remote power management using 802.11 wireless protocols |
JP4139758B2 (en) | 2003-09-29 | 2008-08-27 | 関西電力株式会社 | Path setting method and network, relay station, and master station that employ the path setting method |
US7324824B2 (en) | 2003-12-09 | 2008-01-29 | Awarepoint Corporation | Wireless network monitoring system |
AU2003287497A1 (en) * | 2003-11-04 | 2004-06-06 | Thomson Licensing | Cache server at hotspots for downloading services |
KR100640327B1 (en) * | 2003-11-24 | 2006-10-30 | 삼성전자주식회사 | The Frame Structure and Data Transmission Method for Bridge Operation of WPAN |
KR100547849B1 (en) | 2003-12-05 | 2006-01-31 | 삼성전자주식회사 | Frame Structure for Selecting Bridge Device in WPAN and Method for Selecting Bridge Device in WPAN |
CN100584124C (en) | 2003-12-19 | 2010-01-20 | 诺基亚公司 | Radio resource selection in wireless communication equipment |
US7317404B2 (en) * | 2004-01-14 | 2008-01-08 | Itron, Inc. | Method and apparatus for collecting and displaying consumption data from a meter reading system |
US7802015B2 (en) | 2004-01-26 | 2010-09-21 | Tantalus Systems Corp. | Communications system of heterogeneous elements |
US7961650B2 (en) * | 2004-02-16 | 2011-06-14 | Christopher Michael Davies | Network architecture |
US7376122B2 (en) * | 2004-02-23 | 2008-05-20 | Microsoft Corporation | System and method for link quality source routing |
US20050194456A1 (en) * | 2004-03-02 | 2005-09-08 | Tessier Patrick C. | Wireless controller with gateway |
US7174260B2 (en) * | 2004-04-01 | 2007-02-06 | Blue Line Innovations Inc. | System and method for reading power meters |
US20050251403A1 (en) * | 2004-05-10 | 2005-11-10 | Elster Electricity, Llc. | Mesh AMR network interconnecting to TCP/IP wireless mesh network |
JP4449588B2 (en) | 2004-06-09 | 2010-04-14 | ソニー株式会社 | Wireless communication system, wireless communication apparatus, wireless communication method, and computer program |
US7847706B1 (en) | 2004-06-23 | 2010-12-07 | Wireless Telematics Llc | Wireless electrical apparatus controller device and method of use |
WO2006012211A2 (en) | 2004-06-24 | 2006-02-02 | Meshnetworks, Inc. | A system and method for adaptive rate selection for wireless networks |
JP4445351B2 (en) * | 2004-08-31 | 2010-04-07 | 株式会社東芝 | Semiconductor module |
US7590589B2 (en) * | 2004-09-10 | 2009-09-15 | Hoffberg Steven M | Game theoretic prioritization scheme for mobile ad hoc networks permitting hierarchal deference |
US7554941B2 (en) * | 2004-09-10 | 2009-06-30 | Nivis, Llc | System and method for a wireless mesh network |
US7263371B2 (en) * | 2004-09-13 | 2007-08-28 | Lucent Technologies Inc. | Method for controlling paging and registration of a mobile device in a wireless communications system |
US7170425B2 (en) * | 2004-09-24 | 2007-01-30 | Elster Electricity, Llc | System and method for creating multiple operating territories within a meter reading system |
US7349355B2 (en) | 2004-10-27 | 2008-03-25 | Intel Corporation | Methods and apparatus for providing a communication proxy system |
US7369856B2 (en) | 2004-11-24 | 2008-05-06 | Intel Corporation | Method and system to support fast hand-over of mobile subscriber stations in broadband wireless networks |
WO2006065188A1 (en) | 2004-12-17 | 2006-06-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Retransmission in wireless communication systems |
US7327998B2 (en) * | 2004-12-22 | 2008-02-05 | Elster Electricity, Llc | System and method of providing a geographic view of nodes in a wireless network |
US7428229B2 (en) | 2004-12-28 | 2008-09-23 | Motorola, Inc. | Ad hoc cluster idle node coordination |
US7626967B2 (en) | 2005-01-05 | 2009-12-01 | Intel Corporation | Methods and apparatus for providing a transparent bridge associated with a wireless mesh network |
US7697459B2 (en) * | 2005-01-05 | 2010-04-13 | Intel Corporation | Methods and apparatus for identifying a distance-vector route associated with a wireless mesh network |
CA2601474C (en) | 2005-03-08 | 2017-04-04 | E-Radio Usa, Inc. | Systems and methods for modifying power usage |
US7308370B2 (en) | 2005-03-22 | 2007-12-11 | Elster Electricity Llc | Using a fixed network wireless data collection system to improve utility responsiveness to power outages |
US8599822B2 (en) | 2005-03-23 | 2013-12-03 | Cisco Technology, Inc. | Slot-based transmission synchronization mechanism in wireless mesh networks |
EP1710764A1 (en) | 2005-04-07 | 2006-10-11 | Sap Ag | Authentication of products using identification tags |
US7676231B2 (en) | 2005-04-13 | 2010-03-09 | Intel Corporation | Methods and apparatus for selecting communication channels based on channel load information |
US7522540B1 (en) | 2005-04-15 | 2009-04-21 | Nvidia Corporation | Extended service set mesh topology discovery |
US7814322B2 (en) * | 2005-05-03 | 2010-10-12 | Sri International | Discovery and authentication scheme for wireless mesh networks |
KR100737854B1 (en) * | 2005-05-10 | 2007-07-12 | 삼성전자주식회사 | Optimal path routing method in Wireless Network |
US20060268879A1 (en) * | 2005-05-11 | 2006-11-30 | Texas Instruments Incorporated | Quality of service aware robust link state routing for mesh networks |
US7539882B2 (en) | 2005-05-30 | 2009-05-26 | Rambus Inc. | Self-powered devices and methods |
US20070036353A1 (en) * | 2005-05-31 | 2007-02-15 | Interdigital Technology Corporation | Authentication and encryption methods using shared secret randomness in a joint channel |
US20070063866A1 (en) * | 2005-06-02 | 2007-03-22 | Andisa Technologies, Inc. | Remote meter monitoring and control system |
US7274975B2 (en) | 2005-06-06 | 2007-09-25 | Gridpoint, Inc. | Optimized energy management system |
EP1739894B1 (en) * | 2005-06-30 | 2007-08-29 | NTT DoCoMo, Inc. | Apparatus and method for improved handover in MESH networks |
US7539151B2 (en) | 2005-06-30 | 2009-05-26 | Intel Corporation | Channel selection for mesh networks having nodes with multiple radios |
CA2616587C (en) * | 2005-07-20 | 2017-07-11 | Firetide, Inc. | Route optimization for on-demand routing protocols for mesh networks |
US20070060147A1 (en) | 2005-07-25 | 2007-03-15 | Shin Young S | Apparatus for transmitting data packets between wireless sensor networks over internet, wireless sensor network domain name server, and data packet transmission method using the same |
US7602747B2 (en) | 2005-07-29 | 2009-10-13 | Intel Corporation | Systems and methods increased mobility among mobile nodes in a wireless network |
US7106044B1 (en) | 2005-08-02 | 2006-09-12 | General Electric Company | Systems, methods, and apparatuses for detecting residential electricity theft in firmware |
US7400253B2 (en) * | 2005-08-04 | 2008-07-15 | Mhcmos, Llc | Harvesting ambient radio frequency electromagnetic energy for powering wireless electronic devices, sensors and sensor networks and applications thereof |
US7583984B2 (en) * | 2005-08-12 | 2009-09-01 | Lg Electronics Inc. | Method of providing notification for battery power conservation in a wireless system |
US7495578B2 (en) * | 2005-09-02 | 2009-02-24 | Elster Electricity, Llc | Multipurpose interface for an automated meter reading device |
US7603184B2 (en) * | 2005-09-12 | 2009-10-13 | Abl Ip Holding Llc | Light management system having networked intelligent luminaire managers |
US8874477B2 (en) | 2005-10-04 | 2014-10-28 | Steven Mark Hoffberg | Multifactorial optimization system and method |
US7498873B2 (en) | 2005-11-02 | 2009-03-03 | Rosom Corporation | Wide-lane pseudorange measurements using FM signals |
US7493494B2 (en) * | 2005-11-03 | 2009-02-17 | Prostor Systems, Inc. | Secure data cartridge |
US7756538B2 (en) | 2005-11-09 | 2010-07-13 | Motorola, Inc. | Wide area network handset assisted content delivery system and method of using same |
US7814478B2 (en) | 2005-11-09 | 2010-10-12 | Texas Instruments Norway As | Methods and apparatus for use in updating application programs in memory of a network device |
US20070110024A1 (en) * | 2005-11-14 | 2007-05-17 | Cisco Technology, Inc. | System and method for spanning tree cross routes |
WO2007079289A2 (en) | 2005-11-17 | 2007-07-12 | Silverspring Networks | Method and system for providing a network protocol for utility services |
US7962101B2 (en) * | 2005-11-17 | 2011-06-14 | Silver Spring Networks, Inc. | Method and system for providing a routing protocol for wireless networks |
US20070136473A1 (en) * | 2005-12-13 | 2007-06-14 | Birchler Mark A | Method for selecting a communications network mode having an optimum efficiency |
US7623043B2 (en) | 2005-12-19 | 2009-11-24 | General Electric Company | Method and system for metering consumption of energy |
US20070147268A1 (en) | 2005-12-23 | 2007-06-28 | Elster Electricity, Llc | Distributing overall control of mesh AMR LAN networks to WAN interconnected collectors |
US20070147255A1 (en) * | 2005-12-23 | 2007-06-28 | Ozgur Oyman | Routing in wireless mesh networks |
US20080170511A1 (en) | 2006-01-31 | 2008-07-17 | Peter Shorty | Home electrical device control within a wireless mesh network |
US20070177576A1 (en) | 2006-01-31 | 2007-08-02 | Niels Thybo Johansen | Communicating metadata through a mesh network |
US8509790B2 (en) | 2006-01-31 | 2013-08-13 | Tommas Jess Christensen | Multi-speed mesh networks |
US8194569B2 (en) | 2006-01-31 | 2012-06-05 | Sigma Designs, Inc. | Static update controller enablement in a mesh network |
US20080151825A1 (en) | 2006-01-31 | 2008-06-26 | Peter Shorty | Home electrical device control within a wireless mesh network |
US20080159213A1 (en) | 2006-01-31 | 2008-07-03 | Peter Shorty | Home electrical device control within a wireless mesh network |
US8223783B2 (en) | 2006-01-31 | 2012-07-17 | Sigma Designs, Inc. | Using battery-powered nodes in a mesh network |
US7680041B2 (en) | 2006-01-31 | 2010-03-16 | Zensys A/S | Node repair in a mesh network |
US8219705B2 (en) | 2006-01-31 | 2012-07-10 | Sigma Designs, Inc. | Silent acknowledgement of routing in a mesh network |
US20080151824A1 (en) | 2006-01-31 | 2008-06-26 | Peter Shorty | Home electrical device control within a wireless mesh network |
US8626251B2 (en) | 2006-01-31 | 2014-01-07 | Niels Thybo Johansen | Audio-visual system energy savings using a mesh network |
US8626178B2 (en) | 2006-01-31 | 2014-01-07 | Niels Thybo Johansen | Audio-visual system control using a mesh network |
US20080154396A1 (en) | 2006-01-31 | 2008-06-26 | Peter Shorty | Home electrical device control within a wireless mesh network |
US8300652B2 (en) | 2006-01-31 | 2012-10-30 | Sigma Designs, Inc. | Dynamically enabling a secondary channel in a mesh network |
US20080165712A1 (en) | 2006-01-31 | 2008-07-10 | Peter Shorty | Home electrical device control within a wireless mesh network |
US9166812B2 (en) | 2006-01-31 | 2015-10-20 | Sigma Designs, Inc. | Home electrical device control within a wireless mesh network |
US20080151795A1 (en) | 2006-01-31 | 2008-06-26 | Peter Shorty | Home electrical device control within a wireless mesh network |
US20070257813A1 (en) | 2006-02-03 | 2007-11-08 | Silver Spring Networks | Secure network bootstrap of devices in an automatic meter reading network |
US7427927B2 (en) | 2006-02-16 | 2008-09-23 | Elster Electricity, Llc | In-home display communicates with a fixed network meter reading system |
US7545285B2 (en) | 2006-02-16 | 2009-06-09 | Elster Electricity, Llc | Load control unit in communication with a fixed network meter reading system |
US7729496B2 (en) | 2006-02-28 | 2010-06-01 | International Business Machines Corporation | Efficient key updates in encrypted database systems |
US20070206521A1 (en) | 2006-03-05 | 2007-09-06 | Osaje Emeke E | Wireless Utility Monitoring And Control Mesh Network |
US7936681B2 (en) | 2006-03-06 | 2011-05-03 | Cisco Technology, Inc. | Cross-layer design techniques for interference-aware routing configuration in wireless mesh networks |
US7768926B2 (en) * | 2006-03-09 | 2010-08-03 | Firetide, Inc. | Effective bandwidth path metric and path computation method for wireless mesh networks with wired links |
US7958032B2 (en) | 2006-05-10 | 2011-06-07 | International Business Machines Corporation | Generating event messages corresponding to event indicators |
US7548907B2 (en) | 2006-05-11 | 2009-06-16 | Theresa Wall | Partitioning electrical data within a database |
EP2018633A1 (en) * | 2006-05-17 | 2009-01-28 | Tanla Solutions Limited | Automated meter reading system and method thereof |
US8103389B2 (en) | 2006-05-18 | 2012-01-24 | Gridpoint, Inc. | Modular energy control system |
US8279080B2 (en) * | 2006-06-08 | 2012-10-02 | Fairfax County Water Authority | Systems and methods for remote utility metering and meter monitoring |
WO2008004251A2 (en) | 2006-07-03 | 2008-01-10 | Tanla Solutions Limited | Home security system using an ad-hoc wireless mesh and method thereof |
US20080019321A1 (en) * | 2006-07-19 | 2008-01-24 | Electronics And Telecommunications Research Institute | Multi-hop relay system and data transmission method employed by the same |
US7843842B2 (en) * | 2006-08-04 | 2010-11-30 | Cisco Technology, Inc. | Method and system for initiating a remote trace route |
US20080032703A1 (en) * | 2006-08-07 | 2008-02-07 | Microsoft Corporation | Location based notification services |
US7548826B2 (en) | 2006-08-24 | 2009-06-16 | Blue Pillar, Inc. | Power monitoring and testing |
US8149849B2 (en) * | 2006-08-31 | 2012-04-03 | Sony Ericsson Mobile Communications Ab | Zigbee/IP gateway |
US7707415B2 (en) | 2006-09-07 | 2010-04-27 | Motorola, Inc. | Tunneling security association messages through a mesh network |
US7986718B2 (en) | 2006-09-15 | 2011-07-26 | Itron, Inc. | Discovery phase in a frequency hopping network |
US8138944B2 (en) | 2006-09-15 | 2012-03-20 | Itron, Inc. | Home area networking (HAN) with handheld for diagnostics |
US8055461B2 (en) | 2006-09-15 | 2011-11-08 | Itron, Inc. | Distributing metering responses for load balancing an AMR network |
WO2008036756A2 (en) | 2006-09-19 | 2008-03-27 | Firetide, Inc. | A multi-channel assignment method for multi-radio multi-hop wireless mesh networks |
US7720010B2 (en) * | 2006-09-29 | 2010-05-18 | Cisco Technology, Inc. | Tree based wireless mesh for an OSPF network with intra-tree communication optimization |
US20080177678A1 (en) | 2007-01-24 | 2008-07-24 | Paul Di Martini | Method of communicating between a utility and its customer locations |
US8155007B2 (en) * | 2007-01-25 | 2012-04-10 | Cisco Technology, Inc. | Path optimization for mesh access points in a wireless mesh network |
US7853417B2 (en) | 2007-01-30 | 2010-12-14 | Silver Spring Networks, Inc. | Methods and system for utility network outage detection |
CN101765758B (en) * | 2007-02-02 | 2011-08-31 | 阿芝台克联合公司 | Utility monitoring device, system and method |
US7957322B2 (en) | 2007-02-02 | 2011-06-07 | Silver Sring Networks, Inc. | Flow-through provisioning in utility AMR/AMI networks |
US8489716B2 (en) | 2007-02-02 | 2013-07-16 | Silver Spring Networks, Inc. | Method and system of providing network addresses to in-premise devices in a utility network |
US8023482B2 (en) | 2007-03-15 | 2011-09-20 | Cisco Technology, Inc. | Dynamic rate limiting in wireless mesh networks |
US7859477B2 (en) | 2007-03-30 | 2010-12-28 | Silver Spring Networks, Inc. | J-pole antenna |
US8230108B2 (en) * | 2007-04-13 | 2012-07-24 | Hart Communication Foundation | Routing packets on a network using directed graphs |
US8189577B2 (en) * | 2007-06-15 | 2012-05-29 | Silver Spring Networks, Inc. | Network utilities in wireless mesh communications networks |
US20090003356A1 (en) * | 2007-06-15 | 2009-01-01 | Silver Spring Networks, Inc. | Node discovery and culling in wireless mesh communications networks |
US8130700B2 (en) | 2007-06-15 | 2012-03-06 | Silver Spring Networks, Inc. | Method and system for providing network and routing protocols for utility services |
US7769888B2 (en) * | 2007-06-15 | 2010-08-03 | Silver Spring Networks, Inc. | Method and system for providing network and routing protocols for utility services |
US7940669B2 (en) * | 2007-06-15 | 2011-05-10 | Silver Spring Networks, Inc. | Route and link evaluation in wireless mesh communications networks |
US8233905B2 (en) * | 2007-06-15 | 2012-07-31 | Silver Spring Networks, Inc. | Load management in wireless mesh communications networks |
US8072951B2 (en) | 2007-06-15 | 2011-12-06 | Silver Spring Networks, Inc. | Method and system for providing routing protocols in a frequency hopping spread spectrum network |
US20080317047A1 (en) | 2007-06-20 | 2008-12-25 | Motorola, Inc. | Method for discovering a route to a peer node in a multi-hop wireless mesh network |
US20090010178A1 (en) * | 2007-07-03 | 2009-01-08 | Digi International Inc. | Cordless mains powered form factor for mesh network router node |
US9464917B2 (en) | 2007-07-18 | 2016-10-11 | Silver Spring Networks, Inc. | Method and system of reading utility meter data over a network |
US7894371B2 (en) * | 2007-07-31 | 2011-02-22 | Motorola, Inc. | System and method of resource allocation within a communication system |
US7961740B2 (en) * | 2007-08-01 | 2011-06-14 | Silver Spring Networks, Inc. | Method and system of routing in a utility smart-grid network |
US8279870B2 (en) * | 2007-08-01 | 2012-10-02 | Silver Spring Networks, Inc. | Method and system of routing in a utility smart-grid network |
US8385345B2 (en) * | 2007-09-19 | 2013-02-26 | At&T Intellectual Property Ii, L.P. | Data forwarding in hybrid mesh networks |
US20090115626A1 (en) | 2007-11-02 | 2009-05-07 | Raj Vaswani | Electronic meter for networked meter reading |
WO2009067262A2 (en) * | 2007-11-25 | 2009-05-28 | Trilliant Networks, Inc. | Collector device and system utilizing standardized utility metering protocol |
US8502640B2 (en) | 2007-11-25 | 2013-08-06 | Trilliant Networks, Inc. | System and method for transmitting and receiving information on a neighborhood area network |
US8289883B2 (en) | 2007-12-21 | 2012-10-16 | Samsung Electronics Co., Ltd. | Hybrid multicast routing protocol for wireless mesh networks |
US7522639B1 (en) | 2007-12-26 | 2009-04-21 | Katz Daniel A | Synchronization among distributed wireless devices beyond communications range |
US8442092B2 (en) | 2007-12-27 | 2013-05-14 | Silver Spring Networks, Inc. | Creation and use of unique hopping sequences in a frequency-hopping spread spectrum (FHSS) wireless communications network |
US20090167547A1 (en) | 2007-12-31 | 2009-07-02 | Brad Gilbert | Utility disconnect monitor node with communication interface |
US7961554B2 (en) | 2008-01-11 | 2011-06-14 | Cellnet Innovations, Inc. | Methods and systems for accurate time-keeping on metering and other network communication devices |
US8402455B2 (en) | 2008-03-17 | 2013-03-19 | Landis+Gyr Innovations, Inc. | Methods and systems for distributing firmware through an over-the-air network |
US8311063B2 (en) | 2008-03-28 | 2012-11-13 | Silver Spring Networks, Inc. | Updating routing and outage information in a communications network |
US7839899B2 (en) | 2008-03-28 | 2010-11-23 | Silver Spring Networks, Inc. | Method and system of updating routing information in a communications network |
US20090267792A1 (en) | 2008-04-25 | 2009-10-29 | Henry Crichlow | Customer supported automatic meter reading method |
US7978632B2 (en) | 2008-05-13 | 2011-07-12 | Nortel Networks Limited | Wireless mesh network transit link topology optimization method and system |
US8843241B2 (en) * | 2008-05-20 | 2014-09-23 | LiveMeters, Inc. | Remote monitoring and control system comprising mesh and time synchronization technology |
US20090303972A1 (en) | 2008-06-06 | 2009-12-10 | Silver Spring Networks | Dynamic Scrambling Techniques for Reducing Killer Packets in a Wireless Network |
US8756675B2 (en) * | 2008-08-06 | 2014-06-17 | Silver Spring Networks, Inc. | Systems and methods for security in a wireless utility network |
US8484486B2 (en) * | 2008-08-06 | 2013-07-09 | Silver Spring Networks, Inc. | Integrated cryptographic security module for a network node |
US8467370B2 (en) * | 2008-08-15 | 2013-06-18 | Silver Spring Networks, Inc. | Beaconing techniques in frequency hopping spread spectrum (FHSS) wireless mesh networks |
US8699377B2 (en) * | 2008-09-04 | 2014-04-15 | Trilliant Networks, Inc. | System and method for implementing mesh network communications using a mesh network protocol |
US8207726B2 (en) | 2008-09-05 | 2012-06-26 | Silver Spring Networks, Inc. | Determining electric grid endpoint phase connectivity |
US9025584B2 (en) | 2008-09-09 | 2015-05-05 | Silver Spring Networks, Inc. | Multi-channel mesh nodes employing stacked responses |
WO2010033244A1 (en) | 2008-09-22 | 2010-03-25 | Silver Spring Networks, Inc. | Transparent routing in a power line carrier network |
WO2010033245A1 (en) | 2008-09-22 | 2010-03-25 | Silver Spring Networks, Inc. | Power line communication using frequency hopping |
US9743337B2 (en) | 2008-09-22 | 2017-08-22 | Silver Spring Networks, Inc. | Meshed networking of access points in a utility network |
US8612386B2 (en) * | 2011-02-11 | 2013-12-17 | Alcatel Lucent | Method and apparatus for peer-to-peer database synchronization in dynamic networks |
-
2008
- 2008-11-21 WO PCT/US2008/013032 patent/WO2009067262A2/en active Application Filing
- 2008-11-21 WO PCT/US2008/013019 patent/WO2009067251A1/en active Application Filing
- 2008-11-21 WO PCT/US2008/013027 patent/WO2009067259A1/en active Application Filing
- 2008-11-21 WO PCT/US2008/013023 patent/WO2009067255A1/en active Application Filing
- 2008-11-21 US US12/275,242 patent/US20090135836A1/en not_active Abandoned
- 2008-11-21 US US12/275,236 patent/US20090135762A1/en not_active Abandoned
- 2008-11-21 US US12/275,252 patent/US20090138617A1/en not_active Abandoned
- 2008-11-21 US US12/275,257 patent/US20090135843A1/en not_active Abandoned
- 2008-11-21 EP EP08851132.4A patent/EP2215616B1/en active Active
- 2008-11-21 EP EP08851869A patent/EP2215555A4/en not_active Withdrawn
- 2008-11-21 CA CA2705090A patent/CA2705090A1/en not_active Abandoned
- 2008-11-21 CA CA2705093A patent/CA2705093A1/en not_active Abandoned
- 2008-11-21 US US12/275,305 patent/US20090135851A1/en not_active Abandoned
- 2008-11-21 WO PCT/US2008/013022 patent/WO2009067254A1/en active Application Filing
- 2008-11-21 WO PCT/US2008/013021 patent/WO2009067253A1/en active Application Filing
- 2008-11-21 US US12/275,238 patent/US8144596B2/en active Active
-
2012
- 2012-01-13 US US13/349,779 patent/US8780763B2/en not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040125776A1 (en) * | 2002-12-26 | 2004-07-01 | Haugli Hans C. | Peer-to-peer wireless data communication system with progressive dynamic routing |
US20040157613A1 (en) * | 2003-02-12 | 2004-08-12 | David Steer | Self-selection of radio frequency channels to reduce co-channel and adjacent channel interference in a wireless distributed network |
US7215926B2 (en) * | 2003-12-05 | 2007-05-08 | Microsoft Corporation | Enhanced mode technique for growing mesh networks |
US20060056368A1 (en) * | 2004-09-10 | 2006-03-16 | Nivis, Llc | System and method for a wireless mesh network of configurable signage |
US20060215673A1 (en) * | 2005-03-11 | 2006-09-28 | Interdigital Technology Corporation | Mesh network configured to autonomously commission a network and manage the network topology |
Non-Patent Citations (1)
Title |
---|
See also references of EP2215555A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
USRE49334E1 (en) | 2005-10-04 | 2022-12-13 | Hoffberg Family Trust 2 | Multifactorial optimization system and method |
Also Published As
Publication number | Publication date |
---|---|
US20090135762A1 (en) | 2009-05-28 |
EP2215616A4 (en) | 2011-01-05 |
WO2009067255A1 (en) | 2009-05-28 |
EP2215555A1 (en) | 2010-08-11 |
US20120140678A1 (en) | 2012-06-07 |
US20090135716A1 (en) | 2009-05-28 |
WO2009067253A1 (en) | 2009-05-28 |
US20090135836A1 (en) | 2009-05-28 |
WO2009067259A1 (en) | 2009-05-28 |
CA2705090A1 (en) | 2009-05-28 |
WO2009067262A2 (en) | 2009-05-28 |
US8780763B2 (en) | 2014-07-15 |
EP2215616A1 (en) | 2010-08-11 |
CA2705093A1 (en) | 2009-05-28 |
WO2009067262A3 (en) | 2009-12-30 |
EP2215555A4 (en) | 2011-01-26 |
US20090138617A1 (en) | 2009-05-28 |
US20090135851A1 (en) | 2009-05-28 |
US8144596B2 (en) | 2012-03-27 |
WO2009067251A1 (en) | 2009-05-28 |
EP2215616B1 (en) | 2016-08-17 |
US20090135843A1 (en) | 2009-05-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20090135843A1 (en) | System and method for operating mesh devices in multi-tree overlapping mesh networks | |
US9166934B2 (en) | System and method for operating mesh devices in multi-tree overlapping mesh networks | |
EP2215556B1 (en) | System and method for transmitting power status notifications in an advanced metering infrastructure network | |
US9614799B2 (en) | System and method for operating mesh devices in multi-tree overlapping mesh networks | |
US7996031B2 (en) | Method and system for providing a network protocol for utility services | |
US20090135753A1 (en) | Power-conserving network device for advanced metering infrastructure | |
WO2009067252A1 (en) | Proxy use within a mesh network | |
US20090115626A1 (en) | Electronic meter for networked meter reading | |
US8314717B2 (en) | Network address field for nodes within a meter reading wireless mesh network and associated system | |
WO2020069017A1 (en) | Connecting multiple networks for multicast groups | |
WO2011028526A1 (en) | Registration of a new node to a meter reading wireless mesh network and associated system | |
WO2011028528A1 (en) | Address stripping in a meter reading wireless mesh network and associated system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08851869 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2705090 Country of ref document: CA |
|
REEP | Request for entry into the european phase |
Ref document number: 2008851869 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008851869 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |