Method and system for providing ip-based packet communications in a utility network

METHOD FOR THE SYSTEM FOR SUPPLYING TYPE COMMUNICATIONS

PACKAGE, IP-BASED, IN A UTILITY NETWORK

The scope of the invention relates generally to systems for controlling and providing facilities, and in particular to IP-based packet communication systems for monitoring, controlling and providing facilities.

Automatic meter reading (AMR) systems and the infrastructure for automatic meter systems (AMI) provide services and capabilities for monitoring and / or reporting the use (or consumption) of a facility, such as water, electricity, gas, etc. Such systems ensure communication between a meter for a facility and one or more systems for reporting, billing, etc. Facility metering information, as well as other information, is usually 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.

Figure 1 is a generalized block diagram of a computer-based system that can be used to implement the present invention, according to an embodiment of the invention.

Figure 2 is a generalized block diagram of a computer-based system that can be used to implement the present invention, according to an embodiment of the invention.

Figure 3 is a generalized diagram of the technological process that illustrates a process of providing network addresses for the nodes in a local network, according to a possible embodiment.

Figure 4 represents a generalized diagram of the technological process for communications illustrating the registration of a nodal device with an access point, according to an embodiment of the invention.

Figure 5 is a generalized block diagram illustrating the registration of a rechargeable hybrid vehicle having an access point, according to an embodiment of the invention.

t

STATE TRADE FOR INVENTIONS BRAND Patent application ¹ Nr.

..Date of deposit

Cl- 2 0 0 9 - 0 0 6 0 8 -3 O -01- 200B

Figure 6 represents a generalized block diagram of a node as can be found in the communications networks, according to an embodiment of the invention.

Figure 7 represents a generalized block diagram of an access point as can be found in the communications networks, according to an embodiment of the invention.

Figure 8 is a generalized block diagram of a back-office system as can be found in the communications networks, according to an embodiment of the invention.

)

Figure 9 is a generalized block diagram illustrating a subnet of a utility node, according to a possible embodiment.

Figure 10 is a generalized block diagram illustrating a network in which the IPv4 tunnel connects an IPv6-type LAN network to an IPv6-type back-end system, according to an embodiment of the invention.

Figure 11 is a generalized block diagram illustrating the packet flow between the access point associated with an IPv6-type LAN network and the BOS back-office system via the IPv4-type WAN network, according to an embodiment of the invention.

Figure 12 is a generalized block diagram illustrating a network in which IPv6-type packets are passed through an IPv4-type WAN network, according to a possible embodiment.

Figure 13 is a generalized block diagram illustrating a network in which IPv4-type packets are passed through an IPv6-type LAN network, according to a possible embodiment.

The present invention provides a system and method for IP-based communications in a utility network. A node in the utility network may go through a discovery process to identify its neighbors and access points to the wireless LAN that can ensure its exit from the LAN. The node then establishes a set of optimal routes to the preferred access points for the exit, via the immediately adjacent nodes that offer the lowest route costs. The node can send a registration request to one or more access point devices. Un ^ -2009-00600-3 0 -01- 2008

<img file="RO126258A2_D0001.tif" />

network address IP prefix of the network address of the access point device received from one or more access point devices is used by the final node to programmatically generate a unique network address for the utility node. The utility node is registered to a DNS server. Messages sent to the utility node are routed through the access point that corresponds to the prefix used to generate the network address for the utility node. The network address for the utility node and access point can be IPv6-type addresses, and the network address prefix can be an IPv6-type prefix.

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, the present invention being limited to this embodiment. In particular, the present invention is described in the context of a system for remote reading, control and administration of electronic devices in a utility network. The present invention is also applicable to other network-based management systems of electronic devices and facility meters.

The embodiment provides a network-based system and a method of monitoring and controlling a utility meter in a utility network.

Figure 1 is a generalized block diagram of a utility network 100 that can be used to implement the relay examples according to the present invention. Utility network 100 may include one or more electronic devices 101. In a preferred embodiment, electronic devices 101 may be connected to a wireless local area network (LAN) 102. In the example of a utility network, the LAN may represent a neighboring network (NAN) that corresponds to a service area or neighboring area for utility. As shown in the embodiment, multiple LAN networks can be used, which may or may not overlap, so that a given electronic device can only be connected to a single wireless LAN (or may be part of it) or, on multiple wireless LANs. Electronic devices can be any type of electronic device. Examples of electronic devices include utility nodes, which may include a utility meter or can be connected to a utility meter. A utility meter is a device that is capable of measuring a metered amount, typically a facility of electricity, water, natural gas, etc. Utility nodes that are ^ -2009-00603-3 0 -01- 2008

<img file="RO126258A2_D0002.tif" />

Connecting to a utility meter may include a network interface card (NIC) for communications in a network, and may include one or more radio frequency (RF) transmitters for communications on one or more wireless LAN networks. Other examples of electronic devices include communications devices, such as programmable electronic devices (as they can be used in the provision of cable or satellite television), home appliances (eg refrigerator, radiator, lights, cooking appliances, etc.), computers or computing devices (for example, game consoles, data storage devices, computers, servers, etc.), network devices such as relay, gateway, access point, router or other network devices, telephones or cell phones, battery-based data storage devices, transport devices, vehicles for transport (for example, a hybrid or electric vehicle or other vehicle), recreational devices (e.g. , TVs, DVD players, programmable electronic devices (set top boxes), game consoles, etc.) or other devices that can be found in a home, at work, on the roads or in parking lots or other locations. The relays can enable communication between the electronic devices 101 and the wireless LAN 102. For example, a relay could ensure the communication between the electronic device and the wireless network infrastructure. Unless otherwise specified, other network devices, such as counters, electronic devices, gateways, etc., may also work as relays, and relays may take over the functions of other devices or software in the network.

Wireless LAN 102 can be any type of wireless network, and can use any frequency, communications channel or communication protocol.

LAN 102 networks are typically connected to one or more access points (APs) 103. A given LAN can only be connected to a single AP or can be connected to two or more access points. Access points 103 can be connected to one or more extended networks over large geographical areas (WAN) 104. WAN networks 104 can be connected to one or more back office (BOS) systems 105. The back office system can conduct a variety of operations or administration tasks, including participating in the collection of metering information, managing the metering devices, network security, or other functions as may be desired on an AMI network. Examples of back office systems include billing and accounting systems, proxy servers, systems

2.-2 009-00608-3 0 -01- 2008 iQe fault detection (as they can be used in a utility network), data storage systems, etc. .

Nodes in communications networks that can be a LAN or WAN network, or a combination of both, can communicate using one or more protocols. The nodes may include an electronic device, a relay, an access point, a router or a BOS back office system. Some nodes can communicate using IPv6, others can communicate on IPv4, while others can communicate on either IPv4 or IPv6. Some nodes can encapsulate IPv6 packets into an IPv4 packet. In addition, some nodes can establish an IPv4 tunnel through an IPv6 network. The communication between the nodes is described more fully in the following.

ALLOCATION OF NETWORK ADDRESS RECORDING

IN COMMUNICATION NETWORKS

Figure 2 represents a generalized block diagram of a communications network that includes a LAN network 200 and a LAN network 206. LAN networks connect nodes 202 and access points 201. As shown, LAN network 200 has two access points, and LAN 206 has an access point. A domain name server (DNS) 203 is connected to the LAN network 200 and the LAN network 206, through access point 201 to a communications network 204. In the preferred embodiment illustrated, the DNS server 203 is capable of receiving and processing dynamic updates, thereby providing a dynamic DNS service. Dynamic DNS update is performed according to IETF RFC 2136 classification. The communications network 204 can be a communications network of any type, which includes, without limitation, a LAN, a WAN, wireless, landline, private network, private network virtual, etc. In the preferred embodiment illustrated, the communications network 204 is a large geographical network, and may use one or more communication protocols, such as IPv4 or IPv6. One or more communication devices 205 are connected to the communications network 204. The message to node 202 from the computing device 205 can be sent using a network address for the node. The computing device 205 can be any device, combination of devices, network management system, server, back office systems (BOS), computers, network devices, devices from ^ -2009-00608-3 O -Ol-2009

<img file="RO126258A2_D0003.tif" />

communications, software application or component that is capable of communicating with an access point or node through the communications network 204. A second LAN network 206 can also connect to the DNS server 203 and the communications network 204. The DNS server may be dedicated. to a single LAN or, two or more LANs can split a DNS server. As shown, LAN 200 and LAN 206 do not overlap, as none of the nodes, nor any of the access points, are members of both LAN 200 and LAN 206. Alternative embodiments may have one or more overlapping LANs, with one or more nodes and / or access points shared with one or more LANs. Alternative embodiments may include additional LANs, which may or may not overlap with each other. In the preferred embodiment illustrated, the network address of a node is obtained according to the process described in connection with Figure 3 below.

The DNS 203 server maintains the network addresses for the LAN networks that it is associated with. As discussed above, a DNS server can be associated with one or more LANs and can maintain the node addresses of one or more LANs in the network. In a preferred embodiment, a node with several access points may have at least as many network addresses. Network addresses for the nodes can be included in the DNS server, or in the node path record. Additionally, the DNS server may also maintain address allocation information, such as the node assignment indicator (or the node preference indicator). Table 1 below presents some of the information that can be included in maintaining network addresses for the nodes in a LAN. Resource records maintained on the DNS server may include:

Table 1

<td>Type of resource registration</td><td>Network address for the node</td><td>Node name</td><td>The preference indicator for the node address</td>

<td>YYYY</td><td>ADDR1</td><td>Mac1</td><td> 50</td>

<td></td><td>ADDR2</td><td></td><td> 30</td>

<td></td><td>ADDR2</td><td></td><td> 10</td>

<img file="RO126258A2_D0004.tif" />

^-2009-00608-3 0 -01- 2008

<td>YYYY</td><td>ADDR4</td><td>MAC2</td><td> 80</td>

<td>YYYY</td><td>ADDR5</td><td>MAC3</td><td> 44</td>

<td></td><td>ADDR6</td><td></td><td> 20</td>

As illustrated in Table 1, in the preferred embodiment the node name represents the MAC address of the node. However, other embodiments may use other node names, which may or may not include, or may or may not be based on, the MAC address. In addition, the resource record type (RR) in Table 1 can be IPv6 type.

The route registration information can be updated according to multiple criteria, including periodically or if one or more criteria are met.

For illustrative purposes, in the following only a single DNS server is presented and discussed. Alternative embodiments, however, may use multiple DNS servers.

Alternative embodiments of DNS resource records may include additional information or, may exclude some of the information included in Table 1. In addition, while Table 1 includes information about only three nodes, alternative embodiments of a route record may holds information about more or less nodes. While Table 1 includes up to three network addresses for a given node, alternative examples of a route record may have any number of addresses per node.

Figure 3 is a generalized diagram of the technological process of a process 300 for obtaining a network address for a node. In step 301, the node to send a packet or message to a node requests a DNS resolution request to a DNS server. The DNS resolution request includes an element

J node identification, usually the node name. The node identifier element can be any combination of letters, numbers, symbols or characters. As described above in connection with Table 1, in a preferred embodiment illustrated the node identification element represents the MAC address of the intended node. As shown in Table 1, the source or node σ-2 Ο Ο 9 - Ο Ο 6 Ο 8 - 3 Ο -ΟΙ- 2008

<img file="RO126258A2_D0005.tif" />

the requestor includes information that specifies the node identifier, the network address of the node, the network address preference, and so on. In step 302 the DNS server receives the DNS resolution request for the intended node. In step 303, the DNS server responds with a network address for the node associated with the node identifier. In the preferred embodiment illustrated, the network address is an IP address. In a preferred embodiment illustrated, the AAAA resource record refers to an IPv6 address. IPv4 resource (RR) registration can be type A, PTR, CNAME. The DNS server may have more than one network address for a given node. For example, multiple IPv6-type addresses can be associated with a given node (or access point, or BOS system, or any other device on a network). If multiple addresses are associated with a given node, in step 302 the DNS server can provide all available network addresses for a particular resource record (RR). Alternatively, the DNS server may select a subset of the network addresses associated with the tracked node. For example, the DNS server may choose a network address to include in a response to the electronic device. If a subset of network addresses associated with the destination node is selected, the selection may be based on a connection cost, a predetermined selection criterion, on a policy (for example, the electronic device to exchange messages with the node, type, the size or priority of the message, some aspects of the message being used by the node, or the nature of the network device, for example: a server, a network management system, a billing system, a fault management system, a utility management system, etc.) or, on some other criteria. If multiple network addresses are provided in the DNS server resolution, the response may also include preference indicators corresponding to the node addresses. In step 304 the node receives the DNS server resolution response from the DNS server. In step 305 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 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. If there is more than one access point, the IPv6 prefix of the network address can be associated with a given access point. In this way, the IPv6 network address can allow £ Κ - 2 Ο Ο 9 - Ο Ο 6 ο Ο - 3 Ο -01 “2008 to use a given access point to transmit a message to the network destination. If a node is on a LAN with multiple access points, the node may have more than one IPv6 address associated with the node.

Example 1 - Multiple entries using IPv6 network addressing

The present example presents a node with the name of node Nodel. Nodel has two IPv6 network addresses associated with itself. The route registration entry for Nodel can read:

DDNS route record

<td>Node name</td><td>Resource registration type</td><td>The network address of the node</td><td>The preference indicator for the node address</td>

<td></td><td></td><td></td><td></td>

<td>Mac1</td><td>YYYY</td><td>2001: 2105: 20ae: 1: 225: 3400: 208: aa03 2001: 2105: 20ae: 2: 225: 3400: 208: aa03</td><td> 50 30</td>

<td></td><td></td><td></td><td></td>

Node 1 connects to a communications network through two access points: access point AP1 and access point AP2. The AP1 access point is associated with the IPv6 prefix

2001 : 2105: 20ae: 1:: / 64, and the AP2 access point is associated with the IPv6 prefix

2001 : 2105: 20ae: 2:: / 64.

A network device, for example a back-office system that manages fault detection, which is to send a message to Node 10, can receive either the network address associated with Node 1 from the DNS server routing record (or it can receive both addresses network). The message sent by the fault detection system to Node 1, using the network address with the prefix 2001: 2105: 20ae: 2:: / 64, would be directed through the AP2 access point. The message sent by / ii

Gl-2 Ο Ο 9 - Ο Ο 6 Ο 9 - 3 Ο -01- 2008 the fault detection system to Nodel, using the network address with the prefix 2001: 2105: 20ae: 1 :: / 64, would be addressed by the point AP1 access.

Figure 4 represents a generalized scheme of the technological process 400 for communications illustrating the registration of a nodal device having an access point. registering a nodal device to obtain a network address can be applied to any format or protocol of network addresses. In a preferred embodiment illustrated, the LAN may use IPv6 protocols (exclusively or in parallel with IPv4 protocols). Illustratively, process 400 will describe the nodes of a wireless LAN network using IPv6-type network addresses. In a preferred embodiment, Node M initiates a discovery process and identifies the neighboring nodes and access points of one or more LAN networks that provide the output or the input. Node M can then initiate a targeting analysis to identify a preferred set of immediate neighbors that ensure exit through one or more access points at the lowest route price. You can then start the registration process by having one or more AP access points and affiliated DNS servers. At 401 node M sends a layer 2 registration message to an AP access point. At 402 AP it responds with a layer 2 recognition message that includes an IPv6 prefix that is associated with the AP access point. In addition, the acknowledgment message may include configuration information. In a preferred embodiment illustrated, the configuration information includes information that allows the Node M to register to a DNS server. In another embodiment, the AP access point may mandate the DNS server request, on behalf of the Node M. At 403 node M receives the acknowledgment message layer 2 and sends an IPv6 layer 3 registration message to the DNS server. In a preferred embodiment, the IPv6 registration message to the DNS server includes the IPv6 address for node M, which uses the IPv6 prefix received from the AP access point and a unique IPv6 type suffix, to complete an IPv6 address for the node M. This is mainly accomplished in the case of the stateless self-configuration steps of RFC 2462. In a preferred embodiment, the IPv6 type suffix is ​​based on the MAC address of node M. Alternative embodiments may use other suffixes that are not based on MAC address to create a unique IPv6 address for M node. Note, the IPv6 address for M node does not have to be entirely unique.

^-2009-00608--

0 -01- 2008

<img file="RO126258A2_D0006.tif" />

At 404, the layer 3 recognition message is sent from the DNS server to node M and received by node M at 405. The layer 3 recognition message may include confirmation of the registration of node M on the DNS server, and may include additional information.

While process 400 shows only the registration of a node with a single access point, in the preferred embodiment illustrated all the nodes would be registered with at least one access point. In addition, in another preferred embodiment, the nodes would register with more than one access point on the LAN, if there is more than one access point on the LAN network associated with the node. A node can register even with all its access points on the LAN network with which the node is associated.

In the preferred embodiment illustrated, a given node may have more than one IPv6 type address associated with the node. If, as described above, the IPv6 type address of a node is determined by the IPv6 prefix of an access point and a unique component (for example, the MAC address of the node) and, if the node is registered with access points multiple, the node will be associated with multiple unique IPv6 addresses. In this way, the nodes can be multilocated.

Node M can send a layer 3 SNMP TRAP or INFORM message to a BOS backend system at 406. Alternatively, the DNS server can signal to the BOS system via SNMP. Preferably, the SNMP TRAP or INFORM message will include at least one IPv6 type address of the M node (and may include multiple network addresses associated with the M node). At 407 the BOS system receives the SNMP TRAP or INFORM message and responds with a layer 3 message, such as a GMI (Generic Management Interface) data request. The data request message for the GMI generic management interface may request information on the M node. For example, if node M represents a counter in a utility network, the data request message for the GMI generic management interface may request information about the meter configuration facilities, the status of the meter, information about the metered facility, etc. At 408 node M receives the data request message and sends a response message consisting of data. At 409 the BOS system receives the reply message consisting of data from node M.

^-2009-00600-3 0 -01- 2008

The BOS system can always request the network address of a given node. For example, if the BOS system did not receive a message from the M node, when the message was expected, the BOS system may request a message from the M node. If the BOS system does not already have the network address of node M or, as in the case of one of the preferred embodiments illustrated, if the network is configured to request a network address, if the BOS system does not respond to a received message, the BOS system may perform a search (that is, a DNS server resolution request) from the DNS server. At 410, the BOS system sends an IPv6 network address search message for node M to the DNS server. At 411 the DNS server responds to the BOS system with an IPv6 type address for the M node to the BOS system (if the DNS server has a network address for the M node, otherwise the DNS server may respond that it does not have a network address for the M node). The IPv6 type address for node M is received at 412.

if the node is not registered or, if the BOS system does not receive a network address for the node, the BOS system may attempt to obtain the IP-based address by calculation, or may attempt to generate an IP address. The BOS system can create an ad-hoc IPv6 address, using the IPv6 address of the AP access point and the MAC address of the node (as described above). The BOS system can also send an IPv6 type message to the AP access point, requesting the AP access point to send the message further to the node, based on the unique MAC identification element of the node. Alternatively, the BOS system may request that the AP access point ping (node) the node, to determine the network address of the node, and / or request the consultation of the registration process results.

if the M node has a problem, for example, power failure, security incident, a hardware or software problem, a network problem, etc., the M node may send a message indicating a problem with the BOS system (or any other device that may be available to node M), such as a SNMPTRAP or INFORM message. In the event of a power failure, node M can send a lastgasp message (the last warning message). At 413 node M sends one last warning message to the AP access point. Typically, the latter second warning message is very short, containing only the essential information, to conserve node and network resources so that the message is correctly received by other neighboring nodes and the 'λ' point. 2 00 9 - 0 0 6 0 0 - -

0 -01- 2008 corresponding AP access. At 414 the AP access point receives the last warning message from node M, and in the preferred embodiment illustrated, it makes a packet with the last L2 SNMP TRAP or INFORM PDU (Protocol Data Unit or SNMP packet) messages. forward to the BOS system, indicating that the AP access point received the last warning message from node M.

Example 2 - Network addressing mode for transport nodes

The present example shows a given node which represents a transport device as shown in Figure 5. Specifically, Node H represents a hybrid vehicle that can charge its batteries from an electrical grid. When connecting Node H to an electrical terminal, node H tries to establish communication with a BOS system for electric utilities, called the BOS-HB system. In this example, Node H is in the coverage area of ​​LAN-7, a wireless communications network that uses an IPv6 protocol. Node H sends a layer 2 registration request message to at least one access point on the LAN-7 network. Access point AP1, an access point in the LAN-7 network, responds with its IPv6 prefix, which is 4ea3. Node H uses the prefix received from the AP1 access point to create a unique IPv6 address. Node H uses the MAC address of a network card in Node H, along with the IPv6 prefix at access point AP1, to create the unique IPv6 address. Node H sends a layer 3 registration message to a DNS server associated with the LAN-7 network and receives recognition from the DNS server. Node H is also registered at a second access point on the LAN-7 network, called the AP2 access point. The AP1 access point and the AP2 access point are both capable of communicating with the BOS-HB system through a communications network. AP2 access point sends to H-node its own IPv6 21f prefix, which H node uses to create a second unique IPv6 address associated with AP2 access point. Node H then sends an SNMP TRAP or INFORM message to the BOS-HB system, indicating that it is on the LAN-7 network. In addition, the message to the BOS-HB system includes information to alert the BOS-HB system to the fact that Node H is currently connected to the mains and receives current to recharge the batteries of Node H. The BOS-HB system sends messages to Node H, to search for electricity consumption by Node H and send further messages to verify if Node H is still on the network. Prior to sending a message to Node H, the BOS-HB system performs a network address search for Node H, with α-2009-00600-3 Ο -01-2008

<img file="RO126258A2_D0007.tif" />

DNS server help. The DNS server, in response to the search requests that correspond to the H-node, can determine which of the two unique IP addresses is associated with the H-node, to ensure the BOS-HB system. In this embodiment, the DNS server route record includes a unique preference indicator, associated with the IPv6 type addresses that correspond to the H node. The preference indicator specifies that access point AP2 is preferred over access point AP1, since access point AP2 has a more secure connection with access point AP2, than with access point AP1. Thus, the DNS server responds to the BOS-HB system with the network address associated with the AP2 access point. The BOS-HB system then uses the network address associated with the AP2 access point, which then directs the messages to the H-node, through the AP2 access point. in the event of a failure in sending message from the BOS-HB system to the Node-H via the AP2 access point, the BOS-HB system (or other network device) may request and receive the following most preferred network address, associated with the Node -H and, resend the failed message, using the following most preferred network address for NodeH. Because the next most preferred network address for H-node corresponds to access point AP1, the retry to send the failed message is routed through access point AP1 to H-node. In response to the failed delivery of the message to the network address associated with the AP2 access point, the DNS server can change the associated preference indicators with one or more network addresses associated with the H-node, and can also change the preference indicators of the H-node. to other nodes, according to one or more criteria (for example, proximity to the H-node, dependence on the AP2 access point, dependence on the H-node, etc.). The request to change the preference indicator in the DDNS record may occur on any of the Node-H, the BOS-HB system, the AP-1 access point and the AP-2 access point.

Node H responds to the request from the BOS-HB system received from access point AP2 by sending a packet that includes the network address of Node H. If the included network address includes the access point prefix AP1, the packet can be routed through the access point AP1 to the BOS-HB system, thus allowing a network address to determine which access point, among the multiple access points, to be used as an exit from the LAN-7 network. Node H can select which of the numerous network addresses associated with Node H to be included ^ -2009-00608--.

0 -01- 2008 'τ ° in the packet header sent by the Node H. By routing the packets based on the access point prefix included in the Node H, the output point of the LAN network can be selected, allowing the output control in case of realization examples. with several exits.

Because Node H represents a mobile node capable of moving from one location to another (which may result in displacement as a result of direct contact with a given AP access point, node or LAN), the AP access point can de-register a mobile node. For example, mobile nodes can be de-registered if they have not been in communication with the AP access point, for a predetermined or configurable period of time. in addition, or alternatively, mobile nodes may send information to one or more AP access points, in order not to register them, or AP access point policies may decide not to de-register a given mobile node, based on one or more features.

SYSTEM COMPONENTS SUPPORTING UTILITY NETWORKS ON

J

IPv6 BASE

Utility networks capable of supporting communication, using IPv6 addressing mode and protocols, can use a variety of devices capable of communicating, preferably, using IPv6. In the preferred embodiment illustrated, the system components, such as the utility node, the access point and the back office system, would have IPv6 functional support integrated into the respective system component. Preferred embodiments of IPv6-capable system components are presented and described in connection with Figures 6, 7 and 8.

Figure 6 represents a generalized block diagram of a node 600, as can be found in the communications network 600 described above. In a preferred embodiment, the node 600 may include an information controller 601 of the device, memory 602, a radio network controller LAN and interface 603, a private radio controller and interface 604, the counter and interface for external data 605, and the data element. control for IPv6 type 609 protocol. The meter and interface for external data 605 can be connected to a slave device (auxiliary) 606, to a data interface for local meter 607, and / or to an output interface for the device with external sensor. The controller for the IPv6-type 609 protocol can receive and send IPv6 packets, and ^ -2009-00600-3 0 -III-! 006 can also create or maintain IPv6-type tunnels, or can encapsulate or decapsulate packets as needed.

Although node 600, given for example, does not include a utility metering counter, alternative embodiments may include metering capability.

Although 600, for example, does not include radio, such as a private network radio or LAN radio, alternative embodiments of the node may include one or more radios. While node 600, for example, is described as a single device, alternative examples may use computers, electronic devices, or multiple radios to implement node 600, given for example.

Figure 7 represents a generalized block diagram of an access point 700, as can be found in the communications network 600, described above. Access point 700, which can also act as a gateway for nodes in a network such as the wireless LAN, may include an information controller 701 for the access point, memory 702, the WAN interface 703, the network controller wireless private radio 704, wireless LAN radio controller and interface 705, and protocol controller 706 for IPv6 type network IDs. Protocol controller 706 for network IPv6 type IDs can also include a tunnel broker or, the tunnel broker can be included separately from the router and 6-in-4 formatter, in use examples that use a tunnel broker.

Although the access point given for example 700 does not include radios such as private radio, WAN or LAN radio, alternative embodiments of the access point may include one or more radios.

Although the access point 700 given for example differs from a meter or other device in a network (for example, a relay, etc.), the alternative embodiments could combine the functionality of a node, counter, relay or any other device or network system.

While the access point 700 given for exemplification is described as a single device, alternative embodiments may use multiple computers, electronic devices or radios to implement the access point 700.

if

0 ^ 2009-00608-3 0 -Oh 2008

Figure 8 is a generalized block diagram of the 800 oft back system, as can be found in the communications network 500, described above. The back Office 800 system can include a server 801 for communications, a controller 802 for wireless private communications networks, a router and 6-in-4 formatter 803, a server 804 for applications and a server 805 for the database. The 802 controller for wireless private communications networks can communicate with a private wireless network. The router and 6-in-4 formatter 803 can communicate with the WAN network. The router and 6-in-4 formatter may also include a tunnel broker, or, the tunnel broker may be included separately from the router and 6-in-4 formatter, in use examples using a tunnel broker. The WAN network can be the internet, intranet, or any other type of network for large geographical areas. Alternatively, the formatter may be a 6 to 4 formatter for IPv6 type encapsulation. The application server can be any type of application that can be used on a utility network. Examples include, without limitation, billing applications, accounting applications, fault detection and / or administration applications, configuration and / or power applications, network applications, such as a proxy server, a DNS or DNS server, a security application. storage, back-up and / or recovery, a client interface application (for example, an interface application that allows a client to control aspects associated with a node or to control aspects of a node), a node administrator, a content or delivery system administrator, a communications administrator, or an application that provides communication, etc.

While the back office 800 system is described as a single entity, it can be implemented on one or more computers, for example on multiple servers in a data center. The described components of the back office 800 system can be implemented on different computers, or, can be implemented on multiple computers. In addition, the back office 800 system can be implemented on multiple computers, on multiple locations or on multiple networks. The back office 800 system can also cumulate or include multiple applications. For example, a back office system may include both an accounting system and a customer billing system. As another example, a back office system may include a billing system and a proxy server. Additional combinations with any number of applications can be included in the alternative embodiments.

Ο Ο 9 - Ο Ο β Ο 8 - - b

01 -01- 2008

UTILITY NODE SUB-NETWORKS

Figure 9 is a generalized block diagram illustrating a utility node subnet 900. Network 900 may include a utility node 901. The utility node may include a facility meter, or, may interface with a facility meter. Utility node 901 is capable of communicating with a communications network 902. In a preferred embodiment, utility node 901 includes a wireless radio capable of communicating with a wireless LAN network, using IP based protocols (IPv4 or IPv6). Utility node 901 also includes an interface 903 of the device used in the home. The interface 903 of the device used in the home is connected to the devices 904 used in the home, in order to ensure a communication link between the utility node and the devices used in the home. In addition, the utility node can provide a communication link between the devices used in the housing 904 and the communication network 902, connected to the utility node.

In a preferred embodiment illustrated, the interface 903 of the device used in the home for the utility node assigns a network address to the devices used in the home, address with which it is capable of communicating. In a possible embodiment, the network address assigned by the interface 903 of the device used in the home is an IP address. Preferably, the network address assigned to a device used in the home is unique in the 902 communications network. Interface 903 a

J 5! 1 of the device used in the home may also share, or, allow the network address assigned to a device used in the home to be shared outside the subnet used in the home. Thus, the devices used in the home are directly addressable from outside the sub-network used in the home. The utility node mandates the IP address assigned on behalf of the appropriate device used in the home, allowing other nodes in the communication to communicate with the device used in the home, using the IP address assigned. Example 3 illustrates this through a possible embodiment.

Example 3 - Communication used in the home using IPv6 network addressing

The present example is that of a utility node named node Node 31 Cedar Ave. Node 31 Cedar Ave is deployed in a residential unit (a dwelling) and is capable of communicating with the devices used in the dwelling

0 9 - 0 0 6 0 8 --

0 -01- 2008

<img file="RO126258A2_D0008.tif" />

(home devices), through multiple protocols and communication technologies. For example, utility node 31 Cedar Ave may communicate with devices, using either a wireless personal area network (WPAN), or using PLC (electrical network infrastructure) communications, which have capable PLC grid infrastructure devices, connected to the electrical terminal of the house. The housing example includes five devices used in the home, a thermostat that communicates through the WPAN, a pool pump that communicates through the WPAN, a freezer that communicates through the infrastructure for the PLC power grid, and a recreational system such as the ones for the home. communicate through the WPAN network.

The WPAN network may represent any, or any combination of technologies or network standards that include, without limitation, Bluetooth, ZigBee (IEEE 802.15.4), IrDA, UWB (IEEE 802.15.3), Dust TSMP, Insteon, other technologies based on IEEE 802.15, etc.

Utility node 31 Cedar Ave communicates wirelessly with a utility network using IPv6 communication protocols. The utility network includes other nodes and at least one access point, as well as a BOS back office system for managing 31 Cedar Ave.

Utility node 31 Cedar Ave includes an electricity consumption meter that monitors and reports the electricity use at the home level. In addition, node 31 Cedar Ave includes an interface for other facility meters, which is connected to a natural gas meter that monitors and reports the natural gas consumption at the dwelling level.

Node 31 Cedar Ave assigns an IPv6 address to each of these devices used in the home. Node 31 Cedar Ave shares the IPv6 address assigned to the thermostat, the pool pump, the freezer and the recreational system with the communications network. Specifically, the network addresses of the devices used in the home are shared with a home administration portal, which is connected to the utility network and allows the homeowner to monitor and control the devices used in the home. Network addresses of one or more devices used in the home may also be mandated by Node 31 Cedar Ave in the communications network or, may communicate through the communications network with Node 31 Cedar Ave.

CK- 2 Ο Ο 9 - Ο Ο 6 Ο 8 - -

01 -01- 2008

Through the home device management portal, the homeowner (or others) can communicate with the home-based devices, using the IP address assigned. Node 31 Cedar Ave receives the packets intended for the devices used in the home, identifies the intended device according to the assigned IP address, and, forwards the contents of the packets to the intended device, through the appropriate communication system used in the home (WPAN network, PLC grid infrastructure , etc.). Similarly, the communication signals from the device used in the home, received through the communication system used in the home, are entered into the contents of the package (s) and sent to the administration portal used in the home, which includes the network address assigned to the device used in the home .

The registration entry used in the home for the devices used in the home can read:

registration used in the home

<td>Name of the device used in the home</td><td>The assigned IPv6 network address</td><td>The communication technology used »In the house</td><td>Native address</td>

<td>Thermostat</td><td>Address 1</td><td>ZigBee</td><td>Day</td>

<td>Freezer</td><td>Address 2</td><td>PLC</td><td>plates</td>

<td>Pool pump</td><td>Address 3</td><td>ZigBee</td><td>z₂</td>

<td>Recreational system</td><td>Address 4</td><td>ZigBee</td><td>z₃</td>

Node 31 Cedar Ave uses the assigned network address and the communications technology used in the home to enable communications between the devices used in the home and the communications networks outside the home.

In a preferred embodiment, the utility node may also maintain an access control list (ACL) for the devices used in the home. Using the ACL access control list, the utility node allows access to a device used in the home, according to the ACL access control list. For example, the ACL access control list may specify that a home security system can only access a security portal. Any device or system η -2009-00608--

01 -01- 2008 trying to communicate with the home security system will be denied access, if it does not provide the appropriate verification information, specified in the ACL access control list, corresponding to the security portal.

The utility node of the ACL access control list can also specify the service ports or network daemon names that are admissible for traffic limited to incoming or outgoing, each or both.

In a preferred embodiment illustrated, the utility node may assign routable network addresses to the devices used in the home. Home appliances may not be able to use network addresses, as in Example 3 above, where WPAN network devices and PLC electrical network infrastructure use their own network address and have a network-based network address assigned. IP. Thus, the network address assigned to the device used in the home is sent by the utility node. In embodiments that use IPv6, an access point may allocate a portion of its allocated IPv6 address to the utility node. In turn, the utility node can allocate addresses to the devices used in the home, from the IPv6 addresses assigned to the utility node. In a preferred embodiment, the AP access point may assign a continuous address block to one or more utility nodes. Utility nodes can then assign any of the assigned addresses, or portions thereof, to the devices used in the home.

The network address assigned to a device may be, in whole or in part, based on the MAC address of the utility node that communicates with the device, an access point, or, the device itself.

In addition or alternatively, rules or policies may be used to determine the allocation of addresses to the devices used in the home. The rules may be based on the type of device, the attributes of the device, the network technology or the network protocol used by the device, the type of facility used by the device (for example, electricity, gas, water, etc.), the history or characteristics of the facility (e.g. , high usage, moderate use, etc.), the dwelling or part of the dwelling where the device or attributes physically assigned to the device (for example, the importance of the device, use of the device as medical equipment, fire extinguishing equipment, security equipment, emergency response equipment, etc.), or, on attributes assigned by a

009-00608-3 Ο -01- 2008

<img file="RO126258A2_D0009.tif" />

user of the device or owner / operator of the home. The rules can also combine the multiple factors listed above, for example, discussing the type of device, physical home, electricity consumption, and whether the device is linked to a response that relates to security or emergency.

Additionally or alternatively, some network addresses may be retained for certain devices, uses, users, etc. For example, certain network addresses may be retained for emergency personnel or equipment. Thus, a mobile device used in the home of an emergency responder station, which appears on a given subnet, used in the home, may be assigned an address from a group of addresses kept for such devices of the responder stations in case of expedite. The address given in the address group can also be assigned according to a rule, for example, assigning an address based on the type of responder station (police, firefighters, emergency response teams - EMT, etc.), affiliation or their organization (department, constituency, etc.), device type, or, any other attribute of the organization, purpose, device, etc.

Example 4 illustrates a possible embodiment for implementing address allocation to utility nodes and recognizing addresses allocated to home-based devices that use utility nodes.

Example 4 - IPv6 network allocation addresses used in homes

A utility node named Meter HM node is deployed in a residential unit (a dwelling) and is capable of communicating with the devices used in the dwelling (its dwelling devices). neighboring dwellings), through protocols and technologies. multiple communications. Additionally, the Meter HM meter also includes a facility meter that measures the electricity used in the home. The Meter HM meter can communicate with the devices using either the WPAN network or the PLC power grid infrastructure, having the PLC power grid infrastructure devices connected to the electrical terminal of the home. The home includes six home-use devices that can communicate with the Meter HM meter: a thermostat that communicates through the WPAN network, a freezer that communicates through the PLC's electrical network infrastructure, a home alarm system that communicates through the WPAN network, a video camera that monitors a portion of the home and communicating through the WPAN network, a health monitoring system ¢ ^ - 2 0 0 9 - 0 0 5 0 3 -

0 -01- 2008 that can monitor the health of an older relative and that communicates through the WPAN network, and, a recreational housing system that communicates through the WPAN network.

The Meter HM meter communicates wirelessly with a utility network that uses 1 IPv6 communication protocols. The utility network includes other utility nodes and AP214, AP137 and AP8 access points, as well as a BOS system for managing the Meter HM meter. The BOS system also includes a customer portal that allows the owner to monitor or control, and, one and the other, some or all of the devices used in the home.

Access points AP214, AP137 and AP8 each have an allocation / 64 IPv6 address. Access point AP137 allocated / 125 of the IPv6 type addresses to the utility node represented by the Meter HM counter. The Meter HM counter selects the addresses from its own allocation / 125 from the IPv6 type addresses to designate the addresses to the devices used in the home with which it is registered. The Meter HM meter designates the addresses to the thermostat that communicates through the WPAN network, the freezer that communicates through the infrastructure of the PLC electrical network, the home alarm system that communicates through the WPAN network, the video camera of the housing that communicates through the WPAN network, the home monitoring system that communicates through the WPAN network, and the recreational housing system that communicates through the WPAN network. If one or more devices used in the home is removed, or de-registered from the Meter HM meter, then the Meter HM meter can reassign the designated network address to the device used in the home removed or de-registered to another device used in the home .

The allocation of address blocks to the utility nodes can be segregated according to various criteria. For example, sections other than utility networks, geographically or logically, may have address blocks allocated from a subset of available address blocks.

Although the above embodiments have caused the devices used in the home to communicate with a utility node that is designated (or installed) in the same dwelling of the utility node, the alternative embodiments may allow devices used in the home to communicate through the utility nodes. from neighboring homes.

('X ÎL-2 0 0 9 - 0 0 6 0 8 -3 O -01- 2008

Although the above example used continuous blocks of a given size, according to the CIDR (Classless Inter-Domain Routing / Classless Inter-Domain Routing) notation, the alternative embodiments could use address blocks of any size, be they continuous or discontinuous.

PACKAGE TRANSIT FROM AN IPv6 TYPE NODE FROM AN IPv4 TYPE NETWORK

The decision whether to use a 6 to 4 or 6 in 4 communication over an IPv4 network can be made by the access point, the back office system or another component of the system. The communication between an IPv6 type node in a utility network through an IPv4 type network can be achieved by communication 6 to 4 or 6 in 4, depending on the type of node, the type of network, the selected access point, the back office system, the type of message, the content of the message, the desired security level, etc. For example, for increased security a type 6 in 4 communication can be used. Of note, the type 6 in 4 communication is often referred to as the tuning term, while the type 6 to 4 communication is often referred to as the term of network address transfers (NAT) or packet type encapsulation.

Figure 10 is a generalized block diagram illustrating a network 1000 in which the IPv4 tunnel connects to an IPv6 LAN and an IPv6 back office system. Network 1000 includes two local area networks 1001 and 1002. LAN networks 1001 and 1002 include nodes 1003. In the preferred embodiment shown, nodes 1003 represent utility nodes. The LAN network 1002 is connected to the access point AP1 1004. The LAN network 1001 is connected to the access points AP2 1005 and AP3 1006. The access point AP1 1004 and the access point AP2 1005 are connected to the communications network 1007. The access point AP3 1006 is connected to the network 1008. In the preferred embodiment presented, communication networks 1007 and 1008 represent communications networks for large geographical areas. The BOS-1 1009 back office system connects to the WAN 1007 network. The BOS-2 1010 back office system connects to the WAN 1007 and WAN 1008. The BOS-3 1011 back office system connects to the WAN 1008 network.

In the embodiment, LAN networks 1001 and 1002 communicate using the IPv6 type protocol. Similarly, the WAN 1008 network uses the IPv6 communication protocol. Access point AP3 1006, which connects the LAN

009-00608--

On -01- 2008

<img file="RO126258A2_D0010.tif" />

1001 from WAN 1008, uses IPv6. The BOS-1 1009, BOS-2 1010 and BOS-3 1101 back-up systems all use IPv6 communication protocol.

The WAN 1007 network is an IPv4 type network, and does not support IPv6. Access points 1004 and 1005 that connect LAN networks 1002 and 1001, respectively, of the WAN 1007 network, can communicate using IPv6, can participate in a mechanism that facilitates the transit of IPv6-type packets through the WAN 1007 network to BOS 1009 and 1010 systems. , and vice versa.

A message from a node 1003 on the LAN network 1002, intended for the BOS-1 system

1009 or the BOS-2 1010 system, is sent using an IPv6 address and packet format to an AP1 1004 access point. The AP1 1004 access point creates and uses an IPv6 type tunnel (configured dynamically or manually) over the WAN 1007. IPv6 packet from a node 1003 on the LAN network 1001 to the BOS-2 system

1010 can route the packet through WAN 1007 network or WAN 1008. If IPv6 packet is to be routed through WAN 1008 network, AP3 1006 access point is used and, as WAN 1008 network represents IPv6 type network, there is no need to perform any kind of tunneling, translation or encapsulation. However, if the packet is routed through the WAN 1007 network, and then the AP2 access point 1005 is used, the IPv6 packet from node 1003 will either be passed through a 6-in-4 tunnel, as described in Figure 10, or, may be encapsulated in an IPv4 type packet, for transit through the WAN 1007 network in a virtual tunnel type 6 through 4, as described below, in connection with Figure 12.

As shown in Figure 11, the packet flow between the access point associated with the IPv6-type LAN network and the BOS system is achieved through the IPv4-type WAN network.

Figure 12 is a generalized block diagram illustrating a 1200 network in which IPv6 packets are passed through an IPv4 WAN network. Network 1200 may include two local networks 1201 and 1202. LAN networks 1201 and 1202 include nodes 1203. In the preferred embodiment illustrated, nodes 1203 are utility nodes. LAN networks 1201 and 1202 communicate with nodes 1203 using IPv6 protocols and addresses. The LAN network 1202 is connected to the access point AP1 1204. The LAN network 1201 is connected to the access points AP2 1205 and AP3 1206. The access point AP1 1204 and the access point AP2 1205 are

Cl-2 009-00608--

0 -01- 2008 connects to the communications network 1207. The access point AP3 1206 is connected to the communications network 1208. In the preferred embodiment illustrated, the communication networks 1207 and 1208 represent the networks for large geographical areas that communicate using protocols and addresses. type IPv4. The BOS-1 1209 back office system is connected to the WAN 1207. The BOS-2 1210 back office system is connected to the WAN 1208 network. The BOS-3 1211 back office system connects to the WAN 1208 network.

Node 1203 on the 1201 or 1202 LAN networks, which sends a message to one or more of the BOS-1, BOS-2, and BOS-3 back office systems, must pass through one or more IPv4 1207 WAN networks or 1208.

Node 1203 on LAN networks 1201 or 1202 sends an IPv6-type packet that uses an IPv6-type address to the appropriate access point, to communicate with the intended back office system. If the BOS-1 1209 is the intended back office system, the AP1 1204 access point can be used to connect to the WAN 1207 network. Access point AP1 1204 receives the IPv6 packet from node 1203, and can encapsulate the IPv6 packet, received in the data portion, into the contents of an IPv4 packet. For this purpose, the AP1 access point can have or acquire a global IPv4 address for itself. The IPv4 header with Protocol 41 is added to the IPv6 packet. An IPv4-type address associated with the BOS-1 system is used in the IPv4-type package having the IPv6-type package as its content (the IPv6-type package represents a datagram in the IPv4-type package). The IPv4 type address of the BOS-1 system for the added packet header can also be derived from the IPv6 destination address of the encapsulated packet, by extracting the 32 bits following the destination address 2002 :: IPv6 prefix. In such an embodiment, the IPv4 source address in the added package is the IPv4 address of the AP1 access point. The IPv4 packet is then transmitted to the BOS-1 1209 system via the WAN 1207. The BOS-1 1209 system receives the IPv4 packet, and extracts the encapsulated IPv6 packet. The contents of the IPv6 type packet are extracted by the BOS-1 1209 system. In this way, the AP1 access point 1204 and the BOS-1 system 1209 use a type 6 to 4 tunnel translation through the IPv4 WAN 1207 network, without establishing an explicit tunnel.

0, -2 0 0 9 - 0 0 6 0 8 -3 0 -01-2008 Alternatively, the AP1 access point 1204 receives the IPv6 packet from node 1203 and encapsulates the IPv6 packets in the UDP packets, for transmission to BOS-1 1209 system, using WAN 1207. As above, in this way the access point AP1 1204 and BOS-1 1209 can exchange IPv6 packets through WAN 1207 IPv4 network.

The BOS-1 1209 system, which is to send a message to node 1203 via the IPv4 WAN network and the IPv6 LAN network, can send an IPv4 packet to the AP1 1204 access point through the WAN 1207. The AP1 1204 access point can add an IPv6-type prefix to the IPv4-type address of the packet received from the BOS-1 system 1209 and intended for node 1203, allowing the IPv4-type address to be effectively converted, for the transmission of the packet received through the IPv6-type LAN 1201 network.

In another alternative embodiment, an explicit IPv6 type tunnel may be created through one or more IPv4 type WAN networks (or, more than one IPv6 type tunnel may be created through a given IPv4 WAN network), so as also discussed above in connection with Figure 10. For example, Node 1203 on LAN networks 1201 or 1202 sends an IPv6-type packet that uses an IPv6-type address to the appropriate access point, to communicate with the intended back office system. If the BOS-1 1209 system is the intended back office system, the access point AP1 1204 can be used to connect to the WAN 1207. The access point AP1 1204 receives the IPv6 type packet from node 1203 and can establish a type tunnel. IPv6 (or can access an established IPv6 tunnel) through the WAN 1207 IPv4 network. A tunnel broker (not shown) can establish an IPv6 tunnel through the WAN 1207 IPv4 network. This is a configured tunnel (referred to as tunnel 6 in 4), in which traffic between the BOS system nodes and the AP access point, on any destined part, will always use this tunnel, as in the preferred embodiment. illustrated. A configuration script can be changed between the access point of the utility network and a back office system, in establishing the tunnel through the network for large geographical areas. In a preferred embodiment, access point AP1 1204 sets the IPv6 tunnel to the BOS-1 1209. However, alternative embodiments may cause one or more back office systems to establish a 6-in-4 tunnel through a WAN network, to one or more access points. Type 6 tunnel 4 is a configured tunnel. In (Χ-2 0 0 9 - Ο Ο 6 0 8 3 Ο -01- 2000 alternative embodiments, UDP encapsulation of IPv6 packets may also be used, for example, to prevent the packet from transiting through the WANI 207 network be blocked by any NAT (network address translation device) that may be present on the WANI 207 network.

The IPv6 type IPv4 packet received through the access point AP1 1204 is transmitted to the BOS-1 1209 system via tunnel 6 in 4, through the WAN 1207. The BOS-1 1209 system receives and processes the IPv6 type packet. Similarly, the BOS-1 1209 system can send IPv6-type packets to Node 1203, via AP1 access point 1204, using tunnel 6 in 4 over the WAN 1207 network.

IPv4 TYPE PACKAGE TRANSIT FROM AN IPv6 TYPE LAN UTILITY NETWORK

Figure 13 is a generalized block diagram illustrating a 1300 network in which IPv4 packets are passed through an IPv6 LAN. Network 1300 may include two local networks 1301 and 1302. LAN networks 1301 and 1302 include nodes 1303. In the preferred embodiment illustrated, nodes 1303 represent utility nodes. LAN network 1302 is connected to access point AP1 1304. LAN network 1301 is connected to access points AP2 1305 and AP3 1306. Access point 1304 and access point 1305 are connected to the communications network 1307. Access point 1306 is connected to the communications network 1308. In the illustrated preferred embodiment, the communication networks 1307 and 1308 represent the networks for large geographical areas. The BOS-1 1309 back office system connects to the WAN 1307. The BOS-2 1310 back office system connects to the WAN 1307 and WAN 1308 networks. The BOS-3 1311 back office system connects to the WAN 1308 network.

Nodes 1312 on LAN 1301 represent IPv4-type nodes that communicate using IPv4, while LAN 1301 uses IPv6. Node 1312, which sends a message to the BOS 1310 system that connects to LAN 1301 through IPv6 WAN networks and access points, can be achieved by sending by node 1312, an IPv4 packet on LAN 1301.

Node 1312 sends its own IPv4 type packet to AP2 access point, for forwarding to BOS-1 1309. In this case, AP2 access point has ^ - 2 0 0 9 - 0 0 6 0 8-3 Ο -01- 2008

11 (, the ability to read the destination header from the IPv4 packet, but does not reformat the packet; the packet traverses to the BOS-1 1309 system or the BOS-2 1310 system on the WAN 1307 IPv4 type network; both BOS-1 1309 and BOS- 2 1310 have the ability to unpack IPv4, read information from source and content; the BOS-1 1309 system and the BOS-2 1310 system also generate the IPv4 packets, intended for the IPv4 type 1312 node, to cross over the WAN 1307 network and forward to the 1312 node through the AP2 access point 1305.

In a possible alternative embodiment, the AP2 access point 1305 has the ability to copy and convert the IPv4 address and headers to IPv6 and can also read and copy the content into the IPv6 packet. From that moment, the IPv6 packet traverses the WAN 1307 network, in tunnels 6 to 4 or 6 in 4, as all other IPv6 packets do; BOS 1309 and BOS 1310 systems receive and process the reformatted IPv6 packet and also generate an IPv6 packet in any response to, or in any communication with node 1312. The returned IPv6 packet is converted back to the Ipv4 format by AP2 access point 1305, before being sent further to node 1312.

In another possible embodiment, the IPv4 packet from node 1312, which is routed to the BOS 1310 or BOS 1311 systems via the IPv6 type WAN network, is converted to the IPv6 format by the AP2 access points 1305 or AP3 1306 and, submitted to BOS 1310 or BOS 1311 systems (in this way, 6-in-4 or 6-to-4 tuning should not be involved).

The invention has been described with reference to particular embodiments. However, it will be apparent to those skilled in the art that it is possible for the invention to be made in other specific forms than those of the preferred embodiments described above. This can be achieved without departing from the spirit of the invention.

Thus, the preferred embodiment is rather illustrative and should not be considered in any way restrictive. The scope of the invention is given by the appended claims, rather than by the foregoing description, and all variations and equivalents falling within the claims are intended to be contained therein.

&lt;λ - 2 009-00603--

01 -01- 2008

<img file="RO126258A2_D0011.tif" />