US20160165564A1 - Method and system of providing ip-based packet communications in a utility network - Google Patents

Abstract

A wireless communication system and method include a plurality of nodes that are part of a wireless local area network (LAN), and a plurality of access points connected to the wireless LAN and at least one wide area network (WAN). At least one of the nodes registers with at least two of the access points, and, for each of the access points with which that node registers, obtain a unique network address corresponding to that access point, such that the node obtains a plurality of unique network addresses each respectively associated with a corresponding one of the access points with which the node registers. The node can receive a message from an external network device via multiple routes through the WAN and the wireless LAN. Each of the multiple routes respectively corresponds to one of the unique network addresses obtained by the node.

Description

RELATED APPLICATIONS
• The present application is a continuation of U.S. application Ser. No. 14/600,427, filed on Jan. 20, 2015, which is a continuation of U.S. application Ser. No. 11/807,173 filed on May 24, 2007, which claims priority to U.S. Provisional Patent Application No. 60/899,328 entitled “SYSTEM & METHOD OF COMMUNICATIONS FOR UTILITY & HOME NETWORK SERVICES USING IPV6 AND IP PROTOCOL SUITE,” filed on Feb. 2, 2007. The entire content of these applications are hereby incorporated by reference in their entirety.
BACKGROUND
• 1. Field of the Invention
• The field of the invention relates generally to systems for controlling and delivering commodities, and more particular to IP-based packet communication systems for monitoring, controlling, and delivering commodities.
• 2. Related Background
• Automated Meter Reading (AMR) systems and Automated Meter Infrastructure Systems (AMI) provide services and capabilities to monitor and/or report the usage (or consumption) of a commodity, such as water, electricity, gas, etc. Such systems provide communication between a commodity meter and one or more systems to report, bill, etc. Commodity metering information, as well as other information, is typically reported from the network devices associated with the meters to the reporting and billing systems.
• The present invention seeks to overcome the limitations of conventional utility networks.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a generalized block diagram of a computer-based system that may be used to implement the present invention, according to one embodiment of the invention.
• FIG. 2 is a generalized block diagram of a computer-based system that may be used to implement the present invention, according to one embodiment of the invention.
• FIG. 3 is a generalized flow diagram illustrating a process for providing network addresses for nodes in a local area network, according to one possible embodiment.
• FIG. 4 is a generalized communications flow diagram of illustrating registering a nodal device with an access point, according to one embodiment of the invention.
• FIG. 5 is a generalized block diagram illustrating registering a rechargeable hybrid car with an access point, according to one embodiment of the invention.
• FIG. 6 is a generalized block diagram of a node as may be found in communications network, according to one embodiment of the invention.
• FIG. 7 is a generalized block diagram of an access point as may be found in a communications network, according to one embodiment of the invention.
• FIG. 8 is a generalized block diagram of back office system as may be found in a communications network, according to one embodiment of the invention.
• FIG. 9 is a generalized block diagram illustrating a sub-network of a utility node, according to one possible embodiment.
• FIG. 10 is a generalized block diagram illustrating a network where and IPv4 tunnel connects an IPv6 LAN to and IPv6 back office system, according to one embodiment of the invention.
• FIG. 11 is a generalized block diagram illustrating packet flow between the access point associated with the IPv6 LAN and the BOS through the IPv4 WAN, according to one embodiment of the invention.
• FIG. 12 is a generalized block diagram illustrating a network where IPv6 packets are passed through an IPv4 WAN, according to one possible embodiment.
• FIG. 13 is a generalized block diagram illustrating a network where IPv4 packets are passed through an IPv6 LAN, according to one possible embodiment.
SUMMARY
• An exemplary embodiment of the present disclosure provides a wireless communication system which includes a plurality of nodes that are part of a wireless local area network, and a plurality of access points connected to the wireless local area network, the access points providing communication between at least one of the plurality of nodes and at least one wide area network distinct from the wireless local area network. At least one of the plurality of nodes is configured to register with at least two of the plurality of access points, and, for each of the plurality of access points with which the at least one node registers, obtain a unique network address of the at least one node corresponding to that access point in response to registration, such that the at least one node obtains a plurality of unique network addresses each respectively associated with a corresponding one of the plurality of access points with which the at least one node registers. The at least one node is configured to receive a message from an external network device via multiple routes through the at least one wide area network and the wireless local area network. Each of the multiple routes respectively corresponds to one of the plurality of unique network addresses obtained by the at least one node. Each of the multiple routes is respectively associated with a corresponding one of at least two of the access points with which the node has registered.
• An exemplary embodiment of the present invention provides a method of communicating in a network. The exemplary method includes registering, by a node in a wireless local area network, with a plurality of access point devices that provide an interface between the wireless local area network and an external network, and receiving, by the node, a corresponding network address prefix for each of the plurality of access points the node registers with, respectively, such that the node receives a plurality of network address prefixes each respectively corresponding to one of the plurality of access points with which the node registers. The exemplary method also includes generating a plurality of unique network addresses for the node, each of the plurality of unique network addresses being based on a corresponding one of the plurality of network address prefixes. In addition, the exemplary method includes receiving, by the node via at least one of the access points with which the node is registered, a message from an external network device via multiple routes through the at least one wide area network and the wireless local area network, each of the multiple routes respectively corresponding to one of the plurality of unique network addresses generated for the at least one node, and each of the multiple routes being respectively associated with a corresponding one of the plurality of access points with which the node has registered.
DETAILED DESCRIPTION
• The present invention is described in the context of a specific embodiment. This is done to facilitate the understanding of the features and principles of the present invention and the present invention is not limited to this embodiment. In particular, the present invention is described in the context of a system for remotely reading, controlling and managing electronic devices in a utility network. The present invention is applicable to other systems for network-based management of electronic devices and commodity meters.
• The example embodiment provides for a network-based system and method of monitoring and controlling a utility meter in a utility network.
• FIG. 1 is a generalized block diagram of autility network100 that may be used to implement embodiments of the present invention.Utility network100 may include one or moreelectronic devices101. In a preferred embodiment, theelectronic devices101 may be connected over a wireless local area network (LAN)102. In the example of a utility network, the LAN may be a neighborhood area network (NAN) corresponding to a neighborhood or service area for the utility. As shown in the example embodiment, multiple LANs may be used, which may or may not overlap, such that a given electronic device can be connected to (or be part of) only one wireless LAN or multiple wireless LANs. The electronic devices may be any type of electronic device. Examples of electronic devices include utility nodes, which may include a utility meter or may connect to a utility meter. A utility meter is a device which is capable of measuring a metered quantity, typically a commodity like electricity, water, natural gas, etc. Utility nodes which connect to a utility meter may include a network interface card (NIC) for communicating on a network, and may include one or more RF transceivers for communicating on one or more wireless LANs. Other examples of electronic devices include communication devices, such as set top boxes (as may be used in cable television or satellite television delivery), household appliances (e.g. refrigerator, heater, light(s), cooking appliances, etc.), computers or computing devices (e.g. game consoles, storage devices, PCs, servers, etc.) networking devices such as relay, gateway, access point, router, or other networking devices, phones or cell phones, battery storage device, transportation devices, transportation vehicles (for example: an electric or hybrid car or other vehicle), entertainment devices (e.g. TVs, DVD players, set top boxes, gaming consoles, etc.), or other devise which may be found in a home, business, roadway or parking lot, or other location. Relays may handle communication betweenelectronic devices101 and thewireless LAN102. For example, a relay could provide communication between the electronic device and the infrastructure of the wireless network. Unless otherwise noted, other devices in the network such as meters, electronic devices, gateways, etc. may also perform as relays, and relays may perform the functions of other devices or software on the network.
• Thewireless LAN102 may be any type of wireless network, and may use any frequency, communications channel or communications protocol.
• TheLANs102 are typically connected to one or more access points (AP)103. A given LAN may be connected to only a single AP, or may be connected to two or more access points. Theaccess points103 may be connected to one or more wide area networks (WAN)104. The WANs104 may be connected to one or more back office systems (BOS)105. The back office system may handle a variety of business or management tasks, including participation in the collection of metering information, managing metering devices, security for the network, or other functions as may be desired in an AMI network. Examples of back office systems include billing and accounting systems, proxy servers, outage detection systems (as may be used in a utility network), data storage systems, etc.
• Nodes within the communications network, which may be a LAN or a WAN, or a combination of both, may communicate using one or more protocols. Nodes may include an electronic device, a relay, an access point, a router, or a BOS. Some nodes may be able to communicate using IPv6, some may be capable of communicating on IPv4, while some may be capable of communicating on either IPv4 or IPv6. Some nodes may be capable of encapsulating IPv6 packets in an IPv4 packet. Additionally, some nodes may be able to establish an IPv4 tunnel through an IPv6 network. The communication between nodes is described more fully below.
Assigning and Registering Network Addresses in Communication Networks
• FIG. 2 is a generalized block diagram of a communications network including aLAN200 andLAN206. The LANs connectnodes202 and access points201. As shown,LAN200 has two access points, andLAN206 has once access point. A domain name server (DNS)203 is connected toLAN200 andLAN206 throughaccess point201 to acommunications network204. In the presently preferred embodiment,DNS server203 is capable of receiving and processing dynamic updates, thus providing a dynamic DNS service. Dynamic updating of DNS is according to IETF RFC 2136.Communications network204 may be any type of communications network including, without limitation, a LAN, WAN, wireless, fixed line, private network, virtual private network, etc. In the presently preferred embodiment thecommunications network204 is a wide area network, and may use one or more communications protocols such as IPv4 or IPv6. One ormore computing devices205 connect to thecommunications network204. A message to anode202 from thecomputing device205 may be sent using a network address for the node.Computing device205 may be any device, combination of devices, network management system, server, back office systems (BOS), computers, network devices, communications devices, software application or component which is capable of communicating with an access point or node via thecommunication network204. Asecond LAN206 may also be connected to theDNS server203 and thecommunications network204. A DNS server may be dedicated to a single LAN, or two or more LANs may share a DNS server. As shown,LAN200 andLAN206 do not overlap, in that none of the nodes, and none of access points shown are members of bothLAN200 andLAN206. Alternate embodiments may have one or more LANs which overlap, with one or more nodes and/or access points common to one or more LANs. Alternate embodiments may have additional LANs, which may or may not overlap with each other. In the presently preferred embodiment, the network address of a node is obtained according to the process described in connection withFIG. 3 below.
• DNS server203 maintains network addresses for the nodes of the LAN network that it is associated with. As discussed above, a DNS server may be associated with one or more LANs and maintain the network addresses of nodes within one or more LANs. In one preferred embodiment, a node registered with several access points may have at least as many network addresses. The network addresses for the nodes may be included in the DNS server, or node route registry. Additionally, the DNS server may also maintain address allocation information such as node address allocation indicator (or node preference indicator). Table 1 below shows some of the information which may be included in maintaining network addresses for nodes in a LAN. The resource records maintained in the DNS server may include:

• 	TABLE 1
  	Resource	Node		Node Address
  	Record	Network		Preference
  	Type	Address	Node Name	Indicator
  	AAAA	ADDR1	MAC1		50
  		ADDR2		30
  		ADDR2		10
  	AAAA	ADDR4	MAC2	80
  	AAAA	ADDR5	MAC3	44
  		ADDR6		20

• As illustrated in Table 1, in the presently preferred embodiment the node name is the MAC address of the node. However, other embodiments may use other names for the node, which may or may not include or be based upon the MAC address. Further, the Resource Record (RR) Type in table 1 may be an IPv6 type.
• Information in the route registry may be updated according to multiple criteria, including periodically or in the event one or more criteria are satisfied.
• For illustration purposes only one DNS server is shown and discussed below. Alternate embodiments, however, may use multiple DNS servers.
• Alternate embodiments of the DNS resource records may include additional information or may exclude some of the information included in Table 1. Additionally, while Table 1 includes information on only three nodes, alternate embodiments of a route registry could have information on more or fewer nodes. While Table 1 includes up to three network addresses for a given node, alternate embodiments of a route registry may have any number of addresses per node.
• FIG. 3 is a generalized flow diagram of aprocess300 for obtaining a network address of a node. At step301 a node intending to send a packet or a message to a node makes a DNS resolution request to a DNS server. The DNS resolution request includes a node identifier, typically the node name. The node identifier may be any combination of letters, numbers, symbols or characters. As described above in connection with Table 1, in one presently preferred embodiment the node identifier is the MAC address of the intended node. As shown in Table 1, the source or requesting node includes information specifying the node's identifier, the node's network address, network address preference, etc. Atstep302 the DNS server receives the DNS resolution request for the intended node. Atstep303 the DNS server responds with a network address for the node associated with the node identifier. In the presently preferred embodiment, the network address is an IP address. In one presently preferred embodiment, the resource record AAAA relates to an IPv6 address. IPv4 resource record (RR) may be A, PTR, CNAME type. The DNS server may have more than one network address for a given node. For example, multiple IPv6 addresses may be associated with a given node (or access point, or BOS, or any other device on a network). If multiple addresses are associated with a given node, atstep302 the DNS server may provide all available network addresses for a particular RR. Alternatively, the DNS server may select a subset of the network addresses associated with the intended node. For example, the DNS server may choose one network address to include in the response to the electronic device. If a subset of network addresses associated with the intended node is selected the selection may be based upon a connection cost, upon a preset selection criteria, upon a policy (for example, the electronic device intending to exchange messages with the node, the type, size or priority of the message, some aspect of the use of the message by the node, or the nature of the network device e.g.: a server, a network management system, a billing system, an outage management system, a utility management system, etc.) or upon some other criteria. If multiple network addresses are provided in the DNS resolution response, the response may also include the corresponding node address preference indicators. Atstep304 the node receives the DNS resolution response from the DNS server. Atstep305 the node sends its message using a network address received from the DNS server.
• The address used to send the message from the node and/or an electronic device to the intended node or electronic device may correspond to one or more access points. For example, in an IPv6 LAN the network address would typically be an IPv6 address. In the event there is more than one access point, the IPv6 prefix of the network address may be associated with a given access point. In this manner the IPv6 network address may allow a given access pint to be used to transmit a message to the network destination. If a node is in a LAN with multiple access points, the node may have more than one IPv6 address associated with the node.
Example 1Multi Ingress Using IPv6 Network Addressing
• The present example has a given node with a node name of Node1. Node1 has two IPv6 network addresses associated with it. The route registry entry for Node1 may read:
DDNS Route Registry

• 			Node
  	Resource		Address
  Node	Record		Preference
  Name	Type	Node Network Address	Indicator
  . . .	. . .	. . .	. . .
  MAC1	AAAA	2001:2105:20ae:1:225:3400:208:aa03	50
  		2001:2105:20ae:2:225:3400:208:aa03	30
  . . .	. . .	. . .	. . .

• Node1 connects to a communications network through two access points: AP1 and AP2. AP1 is associated with IPv6 prefix 2001:2105:20ae:1::/64 and AP2 is associated with IPv6 prefix 2001:2105:20ae:2::/64.
• A network device, for example a back office system which manages outage detection, intending to send a message to Node1 may receive either network address associated with Node1 from the route registry of the DNS server (or may receive both network addresses). A message sent from the outage detection system to Node1 using the network address with prefix 2001:2105:20ae:2::/64 would be routed through AP2. A message sent from the outage detection system to Node1 using the network address with prefix 2001:2105:20ae:1::/64 would be routed through AP1.
• FIG. 4 is a generalized communications flowdiagram illustrating process400 for registering a nodal device with an access point. Registering a nodal device to obtain a network address may apply to any format or protocol of network addresses. In one presently preferred embodiment, the LAN may be using IPv6 protocols (exclusively or in parallel with IPv4 protocols). For discussion purposes,process400 will describe nodes of a wireless LAN using IPv6 network addresses. In a presently preferred embodiment, Node M initiates a discovery process and identifies its neighbor nodes and the access points of one or more LANs which provide egress and ingress. Node M may further initiate a routing analysis to identify a preferred set of one-hop neighbors who provide egress via one or more access points at the lowest path cost. It may then commence registration process with one or more APs and the affiliated DNS servers. At401 node M sends alayer 2 registration message to an access point AP. At402 the AP responds with alayer 2 acknowledgement message including an IPv6 prefix which is associated with the AP. Additionally, the acknowledgement message may include configuration information. In a presently preferred embodiment, the configuration information includes information which allows node M to register with a DNS server. In Another embodiment the AP may proxy the DNS request on behalf of node M. At403 node M receives thelayer 2 acknowledgement message and sends alayer 3 IPv6 registration message to the DNS. In one presently preferred embodiment, the IPv6 registration message to the DNS includes the IPv6 address for node M, which utilizes the IPv6 prefix received from the AP and a unique IPv6 “suffix”, to complete an IPv6 address for node M. This is done consistent with stateless autoconfiguration steps of RFC 2462. In one preferred embodiment, the IPv6 suffix is based upon the MAC address of the node M. Alternate embodiments may use other suffixes not based upon the MAC address to create a unique IPv6 address for the node M. Note, the IPv6 address for node M need not be globally unique.
• At404 alayer 3 acknowledgement message is sent from the DNS to the node M and received by the node M at405. Thelayer 3 acknowledgement message may include confirmation of the registration of node M's registration with the DNS server, and may include additional information.
• Whileprocess400 only shows the registration of one node with one access point, in the presently preferred embodiment all nodes would register with at least one access point. Additionally, in one presently preferred embodiment nodes would register with more than one access point on their LAN in the event there is more than one access point on the LAN associated with the node. A node may even register with all the access points on the LAN the node is associated with.
• In the presently preferred embodiment, a given node may have more than one unique IPv6 address associated with the node. If, as described above, a node's IPv6 address is determined from the IPv6 prefix of an access point and a unique component (e.g., the MAC address of the node) then if the node registers with multiple access points the node will be associated with multiple unique IPv6 addresses. In this manner nodes may be multihomed.
• Node M may send alayer 3 SNMP TRAP or INFORM message to a back office system BOS at406. Alternatively, the DNS server may signal the BOS via SNMP. Preferably, the SNMP TRAP or INFORM message will include at least one IPv6 address of the node M (and may include multiple network addresses associated with node M). At407 the BOS receives the SNMP TRAP or INFORM message and replies with alayer 3 message such as a GMI (Generic Management Interface) data query. GMI data query message may request information on node M. For example, if node M is a meter in a utility network, the GMI data query message may request information on the configuration settings of the meter, status of the meter, information on the metered commodity, etc. At408 node M receives the data query message and sends a data response message. At409 the BOS receives the data response message from node M.
• The BOS may request the network address of a given node at any time. For example, if the BOS has not received a message from node M when a message was expected, the BOS may query node M. If the BOS does not already have the network address of node M, or, as in one presently preferred embodiment, if the network is configured to request a network address unless the BOS is responding to a message received, the BOS may perform a lookup (i.e. a DNS resolution request) with the DNS server. At410 the BOS sends an IPv6 network address lookup message for node M to the DNS server. At411 the DNS server responds to the BOS with an IPv6 address for node M to the BOS (if the DNS server has a network address for node M, otherwise the DNS server may respond that it does not have a network address for node M). The IPv6 address for node M is received at412.
• In the event the node is not registered, or if the BOS does not receive a network address for the node, the BOS may attempt to programmatically derive the IP address or may attempt to generate an IP address. The BOS may create an ad-hoc IPv6 address using the AP's IPv6 address and the node's MAC address (as described above). The BOS may also send an IPv6 message to the AP requesting the AP to forward a message to the node based upon the node according to the node's unique MAC identifier. Alternatively, the BOS may request the AP ping the node to determine the network address of the node and/or inquire into the results of the registration process.
• In the event node M encounters a problem, for example loss of power, a security incident, a problem with its hardware or software, a network problem, etc., node M may send a message indicating a problem to the BOS (or to any device reachable by node M) such as an SNMP TRAP or INFORM message. In the event of a loss of power, the node M may send a “last gasp” message. At413 node M sends a last gasp message to the AP. Typically, the later 2 last gasp message is very short with only the essential information to conserve node's and network's resources, so the message is received reliably by other neighbor nodes and the corresponding AP. At414 the AP receives the last gasp message from node M, and in the presently preferred embodiment packs an SNMP TRAP or INFORM PDU (Protocol Data Unit or SNMP packet) with L2 “last gasp” messages and forwards them to the BOS which indicates the AP has received a last gasp message from node M.
Example 2Network Addressing for Transportation Nodes
• The present example has a given node that is a transportation device as shown inFIG. 5. Specifically, Node H is a hybrid car which may have its batteries charged from an electric grid. Upon plugging Node H into an electrical outlet node H attempts to establish communication with an electrical utility billing BOS called BOS-HB. In the present example Node H is within the coverage area of LAN-7, a wireless communications network using the IPv6 protocol. Node H sends alayer 2 registration request message to at least one access point within LAN-7. AP1, an access point with LAN-7 responds with its IPv6 prefix, which is 4ea3. Node H uses the received prefix from AP1 to create a unique IPv6 address. Node H uses the MAC address of a network card in Node H, along with the IPv6 prefix from AP1, to create the unique IPv6 address. Node H sends alayer 3 registration message to a DNS server associated with LAN-7 and receives an acknowledgement from the DNS server. Node H also registers with a second access point on LAN-7 called AP2. AP1 and AP2 are both capable of communicating with BOS-HB through a communications network. AP2 sends Node-H its IPv6 prefix of 21ff, which Node H uses to create a second unique IPv6 address associated with AP2. Node H then sends an SNMP TRAP or INFORM message to BOS-HB indicating that it is on LAN-7. Additionally, the message to BOS-HB includes information to alert BOS-HB that Node H is currently connected to the electrical grid and receiving power to recharge the batteries of Node H. BOS-HB sends Node H messages to inquire into the electrical usage of Node H and also sends messages to check if Node H is still on the network. Prior to sending a message to Node H, BOS-HB performs a lookup of Node-H's network address with the DNS server. The DNS server, in responding to lookup requests corresponding to Node-H, may determine which of the two unique IP addresses associated with Node H to provide BOS-HB. In this example embodiment, the route registry of the DNS server includes a unique preference indicator associated with the IPv6 addresses corresponding to Node H. The preference indicator specifies that AP2 is preferred over AP1, as AP2 has a more reliable connection with AP2 than with AP1. Thus, the DNS server replies to BOS-HB with the network address associated with AP2. BOS-HB then uses the network address associated with AP2, which then routes messages to Node-H through AP2. In the event of a failure to deliver a message from BOS-HB to Node-H through AP2, BOS-HB (or another device on the network) may request and receive the next most preferred network address associated with Node-H, and resend the failed message using the next most preferred network address for Node-H. As the next most preferred network address for Node-H corresponds to AP1, the retry of the failed message is routed through AP1 to Node-H. In response to the failed delivery message to the network address associated with AP2, the DNS server may change the preference indicators associated with one or more network addresses associated with Node-H, and may also change the preference indicators of other nodes on according to one or more criteria (e.g. proximity to Node-H, dependence on AP2, dependence on Node-H, etc.). The request to change the preference indicator in the DDNS registry may originate from any one of Node-H, the BOS-HB, AP-1, AP-2.
• Node H responds to the request from BOS-HB received from AP2 by sending a packet including the network address of Node H. If the included network address includes the prefix of AP1, the pack may be routed through AP1 to BOS-HB, thus allowing a network address to determine which access point, from among multiple access points, to use in egressing from LAN-7. Node H may select which of multiple network addresses associated with Node H to include in packet's header sent from Node H. By routing packets based upon the access point prefix included in the Node H, the egress point of the LAN may be selected, allowing control of egress in multi-egress embodiments.
• As Node H is a mobile node capable of moving from one location to another (which may result in moving out of direct contact with a given AP, node or LAN), the AP may deregister a mobile node. For example, mobile nodes may be deregistered if they have not been in communication with the AP for a preset or configurable, period of time. Additionally, or alternatively, mobile nodes may send information to one or more APs not to deregister them, or policies at the AP may decide not to deregister a given mobile node based upon one or more characteristics.
System Components in Support of IPv6 Utility Networks
• Utility networks capable of supporting communication using IPv6 addressing and protocols may use a variety of devices capable of communicating, preferably, using IPv6. In the presently preferred embodiment, system components such as a utility node, an access point, and a back office system would have IPv6 functional support integrated into the respective system component. Example preferred embodiments of IPv6 capable systems components are shown and described in connection withFIGS. 6, 7 and 8.
• FIG. 6 is a generalized block diagram of anode600 as may be found incommunications network600 described above. In one preferred embodiment,node600 may include adevice information controller601,memory602, LAN radio controller andinterface603, private radio controller andinterface604, meter andexternal data interface605, andIPv6 protocol controller609. Meter and external data interface605 may connect to aslave device606, localmeter data interface607, and or an external sensor device output interface.IPv6 protocol controller609 may receive and send IPv6 packets, and may also create or maintain IPv6 tunnels or encapsulate/de-encapsulate packets as needed.
• While theexample node600 does not include a meter for metering a commodity, alternate embodiments may include metering capability.
• While theexample node600 does not include radios such as a private network radio or LAN radio, alternate embodiments of the node may include one or more radios.
• Whileexample node600 is described as a single device, alternate embodiments may use multiple computers, electronic devices or radios in implementingexample node600.
• FIG. 7 is a generalized block diagram of anaccess point700 as may be found incommunications network600 described above.Access point700, which may also act as a gateway to nodes in a network such as a wireless LAN, may include an accesspoint information controller701,memory702, aWAN interface703, a private wirelessradio network controller704, a wireless LAN radio controller andinterface705, and network IDsIPv6 protocol controller706. The network IDsIPv6 protocol controller706 may also include a tunnel broker, or a tunnel broker may be included separately from the router and 6-in-4 formatter in embodiments utilizing a tunnel broker.
• While theexample access point700 does not include radios such as a private network radio, WAN or LAN radio, alternate embodiments of the access point may include one or more radios.
• While theexample access point700 is distinct from a meter or other device in the network (e.g. a relay, etc.) alternate embodiments could combine the functionality of a node, meter, relay, or any other device or system in the network.
• Whileaccess point700 is described as a single device, alternate embodiments may use multiple computers, electronic devices or radios in implementingaccess point700.
• FIG. 8 is a generalized block diagram ofback office system800 as may be found incommunications network500 described above.Back office system800 may include acommunications server801, a wireless privatenetwork communications controller802, a router and 6-in-4formatter803, anapplication server804 and adatabase server805. Wireless privatenetwork communications controller802 may communicate with a private wireless network. The router and 6-in-4formatter803 may communicate with the WAN. The router and 6-in-4 formatter may also include a tunnel broker, or a tunnel broker may be included separately from the router and 6-in-4 formatter in embodiments utilizing a tunnel broker. The WAN may be the internet, an intranet, or any other type of wide area network. Application server may be any type of application which may be used in a utility network. Examples, without limitation, include billing applications, accounting applications, outage detection and/or management applications, configuration and or provisioning applications, network applications such as a proxy server, a DNS or DNS server, a storage, back-up and or recovery application, a customer interface application (for example, an interface application to allow a customer to control aspects associated with a node or to control aspects of a node), a node manager, a content management or delivery system, a communication manager or communication providing application, etc. Alternatively, the formatter may be a 6 to 4 formatter for IPv6 packet encapsulation.
• Whileback office system800 is described as a single entity, it may be implemented on one or more computers, for example on multiple servers in a data center. The described components ofback office system800 may be implemented on different computers, or may be implemented across multiple computers. Additionally,back office system800 may be implemented across multiple computers in multiple locations or on multiple networks.Back office system800 may also aggregate or include multiple applications. For example, a back office system may include both an accounting system as well as a customer billing system. As another example, back office system may include a billing system and a proxy server. Additional combinations of any number of applications may be included in additional alternate embodiments.
Utility Node Subnetworks
• FIG. 9 is a generalized block diagram illustrating autility node sub-network900.Network900 may include autility node901. The utility node may include a commodity meter, or may interface with a commodity meter.Utility node901 is capable of communicating with acommunications network902. In one preferred embodiment,utility node901 includes a wireless radio capable of communicating with a wireless LAN using IP protocols (IPv4 or IPv6).Utility node901 also includes an in-premise device interface903. In-premise device interface903 connects to in-premise devices904 to provide a communications link between the utility node and the in-premise devices. Additionally, the utility node may provide a communications link between the inpremise devices904 and thecommunications network902 connected to the utility node.
• In one presently preferred embodiment, the utility node in-premise device interface903 assigns a network address to in premise devices which it is capable of communicating with. In one possible embodiment, the network address assigned by the in-premise device interface903 is an IP address. Preferably, the network address assigned to an in-premise device is unique withincommunications network902. The in-premise device interface903 may also share, or allow sharing, of the network address assigned to an in-premise device outside of the subnet within the premise. Thus, in-premise devices are directly addressable from outside the sub-network of the premise. The utility node proxies the assigned IP address on behalf of the corresponding in-premise device, allowing other nodes in the communication network to communicate with the in-premise device using the assigned IP address. Example 3 illustrates this through one possible embodiment.
Example 3In-Premise Communication Using IPv6 Network Addressing
• The present example is of a utility node with a node name of Node 31 Cedar Ave. Node 31 Cedar Ave is deployed in a residential unit (a home) and is capable of communicating with in-premise devices (devices within the home) through multiple protocols and communications technologies. For example, utility node 31 Cedar Ave may communicate with devices using ether a wireless personal area network (WPAN) or using PLC (Power line Carrier) communications with PLC capable devices connected to the home's power grid. The example home includes five in-premise devices, a thermostat communicating via WPAN, a pool pump communicating via WPAN, a freezer communicating via PLC, and a home entertainment system communicating via WPAN.
• The WPAN may be any one, or any combination, of network technologies or standards including, without limitation, Bluetooth, ZigBee (IEEE 802.15.4), IrDA, UWB (IEEE 802.15.3), Dust TSMP, Insteon, other technologies based upon IEEE 802.15, etc.
• Utility Node 31 Cedar Ave communicates wirelessly with a utility network using IPv6 communications protocols. The utility network includes other utility nodes and at least one access point, as well as a BOS for managing node 31 Cedar Ave.
• Utility Node 31 Cedar Ave includes an electricity usage meter which monitors and reports the electrical usage of the home. Additionally, Node 31 Cedar Ave includes an interface for other commodity meters, which is connected to a natural gas meter which monitors and reports the natural gas usage of the home.
• Node 31 Cedar Ave assigns an IPv6 address to each of these in-premise devices. Node 31 Cedar Ave shares the assigned IPv6 address for the thermostat, pool pump, freezer and entertainment system with communications network. Specifically, the network addresses of the in-premise devices are shared with an in-premise management portal which is connected to the utility network and which allows the homeowner to monitor and control the in-premise devices. The network addresses of one or more in-premise devices may also be proxied by Node 31 Cedar Ave within communications network or which may communicate through the communications network with Node 31 Cedar Ave.
• Through the in-premise management portal the homeowner (or others) may communicate with the in-premise devices using the assigned IP address. Node 31 Cedar Ave receives packets intended for in-premise devices, identifies the intended device according to the assigned IP address, and forwards the payload of the packets to the intended device over the appropriate in-premise communication system (WPAN, PLC, etc.). Similarly, communication signals from the in-premise devise received over the in-premise communication system is input into the payload of a packet(s) and send to the in-premise management portal, including the network address assigned to the in-premise device.
• The in-premise registry entry for the in-premise devices may read:
In-Premise Registry

• 		Assigned IPv	In-Premise
  	In-Premise	6 Network	Communication	Native
  	Device Name	Address	Technology	Address
  	Thermostat	Address
  1	ZigBee	Z1
  	Freezer	Address 2	PLC	PLC1
  	Pool Pump	Address	3	ZigBee	Z2
  	Entertainment	Address 4	ZigBee	Z3
  	System

• Node 31 Cedar Ave uses the assigned network addresses and the in premise communication technology to allow communication between the in-premise devices and outside of premise communications networks.
• In one preferred embodiment the utility node may also maintain an access control list (ACL) for in-premise devices. Using the ACL, the utility node allows access to an in-premise device according to the ACL. For example, the ACL may specify that a home security system may only allow access from a security portal. Any device or system attempting to communicate with the home security system will be denied access unless it provides the appropriate verification information specified in the ACL as corresponding to the security portal.
• The utility node ACL may also specify service ports or network daemon names which are allowable for either, or both, inbound and outbound traffic.
• In one presently preferred embodiment, the utility node may assign routable network addresses to in-premise devices. In premise devices may not be capable of using the network address, as in Example 3 above, where WPAN and PLC devices use their own network address and have assigned an IP address. Thus, the network address assigned the in-premise device is proxied by the utility node. In embodiments using IPv6, an access point may assign a portion of its allocated IPv6 addresses to the utility node. In turn, the utility node may allocate addresses to in premise devices from the IPv6 addresses assigned the utility node. In one preferred embodiment, the AP may allocate a block of continuous addresses to one or more utility nodes. The utility nodes may then assign any of the allocated addresses, or portions of them, to in-premises devices.
• The network address assigned a device may be, partially or entirely, based upon the MAC address of the utility node communicating with the device, an access point, or the device itself.
• Additionally or alternatively, rules or policies may be used to determine the allocation of addresses to in premise devices. Rules may be based upon the device type, device attributes, network technology or network protocol used by the device, the device's commodity usage type (e.g. electric, gas, water, etc.), the device's commodity usage history or characteristic (e.g. high usage, moderate usage, etc.), the premise or section of a premise the device is physically located in, or assigned attributes of the device (e.g. the importance of a device, the use of a device such as medical equipment, fire suppression equipment, security equipment, emergency response equipment, etc.), or upon attributes assigned by a user of the device or the owner/operator of the premise. Rules may also combine multiple factors listed above, for example considering the type of device, the physical premise, the electrical power consumption, and whether the device is related to security or emergency response.
• Additionally or alternatively, some network addresses may be set aside for particular devices, uses, users, etc. For example, certain network addresses may be set aside for emergency personnel or their equipment. Thus, a mobile in-premise device of an emergency responder which appears on a given in-premise subnet may be assigned an address from a set-aside group of addresses for such devices of emergency responders. The address given from the group of address set aside may also be allocated according to a rule, for example assigning an address based upon the type of responder (police, fire, EMT, etc.) their affiliation or organization (department, precinct, etc.) the device type, or any other attribute of the organization, purpose, device, etc.
• Example 4 illustrates one possible embodiment for implementing allocation of addresses to utility nodes and the assignment of allocated addresses to in-premise devices using utility nodes.
Example 4Assigning in-Premise IPv6 Network Addresses
• A utility node with a node name of Meter HM is deployed in a residential unit (a home) and is capable of communicating with in-premise devices (devices within the home or neighboring homes) through multiple protocols and communications technologies. Additionally, Meter HM also includes a commodity meter which meters the electricity used in the home. Meter HM may communicate with devices using either WPAN or PLC, with PLC capable devices connected to the home's power grid. The home includes six in-premise devices which may communicate with Meter HM: a thermostat communicating via WPAN, a freezer communicating via PLC, a home alarm system communicating over WPAN, a video camera which monitors a portion of the home and communicates over WPAN, a health monitoring system which may monitor the health of an elderly relative and which communicates over WPAN, and a home entertainment system communicating via WPAN.
• Meter HM communicates wirelessly with a utility network using IPv6 communications protocols. The utility network includes other utility nodes and at Access points AP214, AP137 and AP8, as well as a BOS for managing Meter HM. The BOS also includes a customer portal which allows the homeowner to either monitor or control, or both, some or all of the in premise devices.
• Access points AP214, AP137 and AP8 each have a /64 allocation of IPv6 addresses. Access point AP137 has allocated a /125 of IPv6 addresses to utility node Meter HM. Meter HM selects addresses from its /125 allocation of IPv6 addresses to assign addresses to the in-premise devise which register with it. Meter HM assigns addresses to the thermostat communicating via WPAN, the freezer communicating via PLC, the home alarm system communicating over WPAN, the video camera communicates over WPAN, the health monitoring system communicating over WPAN, and the home entertainment system communicating via WPAN. In the event one or more in-premise devices is removed, or unregistered from Meter HM then Meter HM may reassign the network address assigned to the removed or unregistered in-premise device to another in premise device.
• Allocation of blocks of addresses to utility nodes may be segregated according to various criteria. For example, different sections of the utility network, geographically or logically, may have address blocks allocated from a subset of available address blocks.
• While the above example embodiments had the in-premise devices communicate with a utility node which is assigned to (or installed at) the some premise of the utility node, alternate embodiments may allow in-premise devices to communicate via utility nodes from neighboring premises.
• While the above example used continuous blocks of a given size according to CIDR (Classless Inter-domain routing) notation, alternate embodiments could use address blocks of any size, whether continuous or non-continuous.
• Transit of Packets from an IPv6 Node Through IPv4 Network
• Determination of whether to use “6 to 4” or “6 in 4” communication through an IPv4 network may be made by the access point, the back office system, or another component of the system. Communication between an IPv6 node in the utility network through an IPv4 network may be through either “6 to 4” or “6 in 4” communication, according to the type of node, the type of network, the selected access point, the back office system, the type of message, the contents of the message, the desired security level, etc. For example, for increased security “6 in 4” communication may be used. Note, “6 in 4” communication is often referred to as tunneling, whereas “6 to 4” communication is often referred to as network address translations (NAT) or IPv6 packet encapsulation.
• FIG. 10 is a generalized block diagram illustrating anetwork1000 where an IPv4 tunnel connects an IPv6 LAN to and IPv6 back office system.Network1000 includes twolocal area networks1001 and1002.LANs1001 and1002 includenodes1003. In the presently preferred embodiment,nodes1003 are utility nodes.LAN1002 is connected to accesspoint AP11004.LAN1001 is connected to accesspoints AP21005 andAP31006.Access point AP11004 andaccess point AP21005 connect tocommunications network1007.Access point AP31006 connects tocommunications network1008. In the presently preferred embodiment,communications networks1007 and1008 are wide area networks. Back office system BOS-11009 connects toWAN1007. Back office system BOS-21010 connects toWAN1007 andWAN1008. Back office system BOS-31011 connects toWAN1008.
• In the example embodiment,LANs1001 and1002 communicate using the IPv6 protocol. Similarly,WAN1008 utilize the IPv6 communications protocol.Access point AP31006, connectingLAN1001 toWAN1008, utilizes IPv6. Back office Systems BOS-11009, BOS-21010 and BOS-31101 all utilize the IPv6 communications protocol.
• WAN1007 is an IPv4 network, and does not support IPv6.Access points1004 and1005 which connectLAN1002 and1001, respectively, toWAN1007 are capable of communicating using IPv6 and in participating in a mechanism that facilitates transit of IPv6 packets throughWAN1007 toBOS1009 and1010, and vice versa.
• A message from anode1003 onLAN1002, intended for BOS-11009 or BOS-21010, is sent using and IPv6 address and packet format to accesspoint AP11004.AP11004 creates and uses an IPv6 tunnel (dynamically or manually configured) throughWAN1007. An IPv6 packet from anode1003 onLAN1001 to BOS-21010 may route the packet throughWAN1007 or throughWAN1008. If the IPv6 packet is to be routed throughWAN1008,AP31006 is used and asWAN1008 is an IPv6 network, no tunneling, translation or encapsulation need be performed. However, if the packet is routed throughWAN1007, thenAP21005 is used an the IPv6 packet fromnode1003 will either be passed through a “6-in-4” tunnel, as described in Figure, or may be encapsulated in an IPv4 packet for transit throughWAN1007 in a 6to4 virtual tunnel, as described below in connection withFIG. 12.
• As shown inFIG. 11, packet flow between the access point associated with the IPv6 LAN and the BOS is through the IPv4 WAN.
• FIG. 12 is a generalized block diagram illustrating anetwork1200 where IPv6 packets are passed through an IPv4 WAN.Network1200 may include twolocal area networks1201 and1202.LANs1201 and1202 includenodes1203. In the presently preferred embodiment,nodes1203 are utility nodes.LANs1201 and1202 communicate withnodes1203 using IPv6 protocols and addressing.LAN1202 is connected to accesspoint AP11204.LAN1201 is connected to accesspoints AP21205 andAP31206.Access point AP11204 andaccess point AP21205 connect tocommunications network1207.Access point AP31206 connects tocommunications network1208. In the presently preferred embodiment,communications networks1207 and1208 are wide area networks which communicate using IPv4 protocols and addresses. Back office system BOS-11209 connects toWAN1207. Back office system BOS-21210 connects toWAN1208. Back office system BOS-31211 connects toWAN1208.
• Anode1203 onLAN1201 or1202 sending a message to one, or more, of the back office systems BOS-1, BOS-2, and BOS-3 must pass through one ormore IPv4 WANs1207 or1208.
• Node1203 onLAN1201 or1202 sends an IPv6 packet using and IPv6 address to the appropriate access point to communicate with the intended back office system. In the event BOS-11209 is the intended back office system,AP11204 may be used to connect toWAN1207.AP11204 receives the IPv6 packet fromnode1203, and may encapsulate the received IPv6 packet in the payload portion of an IPv4 packet. AP1 may have or acquire a global IPv4 address for itself for this purpose. The IPv4 header with Protocol 41 is prepended to the IPv6 packet. An IPv4 address associated with BOS-1 is used in the IPv4 packet with the IPv6 packet as payload (the IPv6 packet is a datagram within the IPv4 packet). The IPv4 address of BOS-1 for the prepended packet header can also be derived from the IPv6 destination address of the encapsulated packet by extracting the 32-bits following the IPv6 destination address'2002:: prefix. In such an embodiment, the IPv4 source address in the prepended packet is the IPv4 address of AP1. The packet IPv4 packet is then transmitted to BOS-11209 throughWAN1207. BOS-11209 receives the IPv4 packet, and extracts the encapsulated IPv6 packet. The payload of the IPv6 packet is extracted by the BOS-11209. In thismanner AP11204 and BOS-11209 use a “6 to 4” tunnel translation thoughIPv4 WAN1207 without establishing an explicit tunnel. Alternatively,AP11204 receiving the IPv6 packet fromnode1203, and encapsulate IPv6 packets within UDP packets for transmission to BOS-11209 usingWAN1207. As above, in thismanner AP11204 and BOS-11209 are able to exchange IPv6 packets throughIPv4 WAN1207.
• BOS-11209 intending to send a message tonode1203 through IPv4 WAN and IPv6 LAN may send an IPv4 packet toAP11204 throughWAN1207.AP11204 may prepend an IPv6 prefix to the IPv4 address of the packet received from BOS-11209 and intended fornode1203, allowing the IPv4 address to be effectively converted for transmitting the received packet overIPv6 LAN1201.
• In yet another alternative embodiment, an IPv6 “explicit tunnel” may be created through one or more IPv4 WANs (or more than one IPv6 tunnels may be created through a given IPv4 WAN) as also discussed above in connection withFIG. 10. For example,Node1203 onLAN1201 or1202 sends an IPv6 packet using and IPv6 address to the appropriate access point to communicate with the intended back office system. In the event BOS-11209 is the intended back office system,AP11204 may be used to connect toWAN1207.AP11204 receives the IPv6 packet fromnode1203, and may establish an IPv6 tunnel (or may access an established IPv6 tunnel) throughIPv4 WAN1207. A tunnel broker (not shown) may establish an IPv6 tunnel throughIPv4 WAN1207. This is a configured tunnel (referred to as 6in4 tunnel) where the traffic between nodes on either side intended BOS and AP nodes will, in the presently preferred embodiment, always use this tunnel. A configuration script may be exchanged between the access point of the utility network and a back office system in establishing the tunnel through the wide area network. In one preferred embodiments,AP11204 establishes the IPv6 tunnel to BOS-11209. However, alternate embodiments may have one or more back office systems establish a “6 in 4” tunnel through a WAN to one or more access points. 6in4 tunnel is a configured tunnel. In alternate embodiments, UDP encapsulation of IPv6 packets may also be used, for example to prevent the transiting packet throughWAN1207 is not blocked by any NAT (Network address Translation) device that may be present inWAN1207.
• The IPv6 packet IPv4 received byAP11204 is transmitted to BOS-11209 via the “6 in 4” tunnel throughWAN1207. BOS-11209 receives and processes the IPv6 packet. Similarly, BOS-11209 may send IPv6 packets toNode1203 throughAP11204 using the “6 in 4” tunnel throughWAN1207.
Transit of IPv4 Packets Through an IPv6 Utility LAN Network
• FIG. 13 is a generalized block diagram illustrating anetwork1300 where IPv4 packets are passed through an IPv6 LAN.Network1300 may include twolocal area networks1301 and1302.LANs1301 and1302 includenodes1303. In the presently preferred embodiment,nodes1303 are utility nodes.LAN1302 is connected to accesspoint AP11304.LAN1301 is connected to accesspoints AP21305 andAP31306.Access point1304 andaccess point1305 connect tocommunications network1307.Access point1306 connects tocommunications network1308. In the presently preferred embodiment,communications networks1307 and1308 are wide area networks. Back office system BOS-11309 connects toWAN1307. Back office system BOS-21310 connects toWAN1307 andWAN1308. Back office system BOS-31311 connects toWAN1308.
• Nodes1312 onLAN1301 are IPv4 nodes which communicate using IPv4, whereasLAN1301 utilizes IPv6.Node1312 sending a message toBOS1310, which connects toLAN1301 through IPv6 WANs and access points, may be accomplished bynode1312 sending an IPv4 packet onLAN1301.
• Node1312 sends its IPv4 packet to AP2 for forwarding to BOS-11309. In this case, AP2 has the capability to read the destination header in the IPv4 packet but does not reformat the packet; the packet traverses to BOS-11309 or BOS-21310 overIPv4 WAN1307; BOS-11309 and BOS-21310 both have the capability to strip the IPv4 packet, read the source information and the payload; BOS-11309 and BOS-21310 also generate IPv4 packets intended forIPv4 node1312 for traverse throughWAN1307, and forwarding tonode1312 byAP21305.
• In one possible alternative embodiment,AP21305 has the capability to map and convert the IPv4 address and headers to IPv6 and also read and map the payload on to IPv6 packet. From then on, the IPv6 packet traversesthro WAN1307 in a 6to4 or 6in4 tunnels like all other IPv6 packets do;BOS1309 andBOS1310 receive and process the reformatted IPv6 packet, and also generate an IPv6 packet in any response to or communication withnode1312. The return IPv6 packet is converted back to IPv4 format byAP21305 before it is forwarded tonode1312.
• In yet another possible embodiment, the IPv4 packet fromnode1312 heading toBOS1310 or BOS1311 via IPv6 WAN is converted to IPv6 format byAP21305 orAP31306, and forwarded toBOS1310 or BOS1311 (in this manner, 6in4 or 6to4 tunneling need not be involved).
• The invention has been described with reference to particular embodiments. However, it will be readily apparent to those skilled in the art that it is possible to embody the invention in specific forms other than those of the preferred embodiments described above. This may be done without departing from the spirit of the invention.
• Thus, the preferred embodiment is merely illustrative and should not be considered restrictive in any way. The scope of the invention is given by the appended claims, rather than the preceding description, and all variations and equivalents which fall within the range of the claims are intended to be embraced therein.

Claims (22)

What is claimed is:

1. A wireless communication system comprising:

a plurality of nodes that are part of a wireless local area network; and

a plurality of access points connected to the wireless local area network, the access points providing communication between at least one of the plurality of nodes and at least one wide area network distinct from the wireless local area network;

wherein at least one of the plurality of nodes is configured to:

register with at least two of the plurality of access points; and

for each of the plurality of access points with which the at least one node registers, obtain a unique network address of the at least one node corresponding to that access point in response to registration, such that the at least one node obtains a plurality of unique network addresses each respectively associated with a corresponding one of the plurality of access points with which the at least one node registers,

wherein the at least one node is configured to receive a message from an external network device via multiple routes through the at least one wide area network and the wireless local area network, each of the multiple routes respectively corresponding to one of the plurality of unique network addresses obtained by the at least one node, and each of the multiple routes being respectively associated with a corresponding one of at least two of the access points with which the node has registered.

2. The wireless communication system ofclaim 1, wherein the at least one node is configured to forward, via at least one of the access points with which the at least one node is registered, the plurality of unique network addresses to an intended network destination accessible through the at least one wide area network, to provide the intended network destination with the multiple routes to reach the node,

3. The wireless communication system ofclaim 2, wherein the intended network destination is associated with a global network address, and

wherein the global network address associated with the intended network destination is used by the at least one node to send a message to the intended network destination.

4. The wireless communication system ofclaim 1, wherein at least one of the plurality of unique network addresses corresponding to the access point that the at least one node is registered with includes an address prefix associated with the access point the node is registered with.

5. The wireless communication system ofclaim 4, wherein the address prefix is an IPv6 address prefix.

6. The wireless communication system ofclaim 1, wherein at least one of the plurality of nodes is configured to communicate with a utility meter and transmit information on a metered commodity.

7. A method of communicating in a network, comprising:

registering, by a node in a wireless local area network, with a plurality of access point devices that provide an interface between the wireless local area network and an external network;

receiving, by the node, a corresponding network address prefix for each of the plurality of access points the node registers with, respectively, such that the node receives a plurality of network address prefixes each respectively corresponding to one of the plurality of access points with which the node registers;

generating a plurality of unique network addresses for the node, each of the plurality of unique network addresses being based on a corresponding one of the plurality of network address prefixes; and

receiving, by the node via at least one of the access points with which the node is registered, a message from an external network device via multiple routes through the at least one wide area network and the wireless local area network, each of the multiple routes respectively corresponding to one of the plurality of unique network addresses generated for the at least one node, and each of the multiple routes being respectively associated with a corresponding one of the plurality of access points with which the node has registered.

8. The method ofclaim 7, comprising:

forwarding, by the node via at least one of the access points with which the node is registered, the plurality of unique network addresses to an intended network destination to provide the intended network destination with multiple routes to reach the node.

9. The method ofclaim 7, comprising:

registering the plurality of unique network addresses with a dynamic domain name server associated with the external network to provide the external network device in communication with the external network with the multiple routes to reach the node.

10. The method ofclaim 7, comprising:

routing messages to the node according to one of the plurality of unique network addresses,

wherein the network address prefixes are IPv6 address prefixes, and

wherein the routed messages are routed through one of the access points corresponding to the IPv6 prefix, and one of the plurality of unique network addresses for the node is chosen according to a network address preference indicator.

11. The method ofclaim 10, wherein the network address preference indicator is stored in a DNS server associated with the wireless local area network.

12. The method ofclaim 10, wherein the preference indicator corresponds to a configurable cost metric of packet delivery performance of a connection to the corresponding node.

13. The method ofclaim 10, wherein the preference indicator corresponds to a configurable cost metric of packet delivery performance of a connection to the corresponding node.

14. The method ofclaim 10, wherein the preference indicator corresponds to a configurable policy.

15. The method ofclaim 10, comprising:

selecting an alternate route upon failure of an initial packet delivery attempt.

16. The method ofclaim 10, wherein the preference indicator is based on at least one of reliability, speed, priority and link quality.

17. The method ofclaim 10, comprising:

modifying the preference indicator corresponding to the unique network address used to send a message to the node in response to a failed attempt to deliver a message to the node.

18. The method ofclaim 17, comprising:

modifying preference indicators of DNS entries corresponding to other nodes that are dependent on a node which failed to deliver the message to the node.

19. The method ofclaim 7, wherein the node is configured to communicate with a utility meter and transmit information on a metered commodity.

20. The method ofclaim 7, comprising:

communicating, via the node, with at least one in-premise device over a sub-network of a premises;

associating at least one of the plurality of unique network addresses with the in-premise device; and

sending an indication of the association of the network address with the in-premise device to at least one other node in the local area network.

21. The method ofclaim 7, comprising:

communicating, via the node, with at least one in-premise device over a sub-network of a premises;

receiving a block of network addresses from at least one of the access points in the local area network;

allocating a network address to the in-premise device from the received block of network addresses; and

sending an indication of the allocation of the network address with the in-premise device to at least one other node in the local area network.

22. A wireless communication system comprising:

a plurality of nodes that are part of a wireless local area network; and

a plurality of access points connected to the wireless local area network, the access points providing communication between at least one of the plurality of nodes and at least one wide area network;

wherein at least one of the plurality of nodes is configured to:

register with at least two of the plurality of access points; and

for each of the plurality of access points with which the at least one node registers, obtain a unique network address of the at least one node corresponding to that access point in response to registration, such that the at least one node obtains a plurality of unique network addresses each respectively associated with a corresponding one of the plurality of access points with which the at least one node registers,

wherein the at least one node is addressable using any one of the plurality of unique network addresses obtained by the at least one node such that the at least one node is configured to receive a message from an external network device via multiple routes through the at least one wide area network and the wireless local area network.

Images