WO2006046261A1 - Method for controlling routing operations in a network, related network and computer program product thereof - Google Patents
Method for controlling routing operations in a network, related network and computer program product thereof Download PDFInfo
- Publication number
- WO2006046261A1 WO2006046261A1 PCT/IT2004/000600 IT2004000600W WO2006046261A1 WO 2006046261 A1 WO2006046261 A1 WO 2006046261A1 IT 2004000600 W IT2004000600 W IT 2004000600W WO 2006046261 A1 WO2006046261 A1 WO 2006046261A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- address
- gateway
- addresses
- global
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- the present invention relates to techniques for monitoring and controlling routing operations in communication networks, and has been developed by- paying specific attention to the possible application in wireless Mobile Ad-hoc Networks (MANETs) .
- MANETs wireless Mobile Ad-hoc Networks
- MANETs are wireless networks characterized by the absence of any infrastructure: nodes of a MANET operate both as hosts (i.e. they are end-points of a communication) and as routers. In fact packets that cannot be directly delivered between two nodes are routed through other intermediate nodes following a multi-hop path to reach their destination.
- Routing within a MANET is enabled by a routing protocol, which has to run on every node belonging to the MANET, called “MANET node” : by exchanging control messages the nodes calculate the optimal path that data packets must follow within the network.
- Nodes typically own a unique identifier, which is used for routing purposes and/or data exchange.
- a MANET can be an isolated network or can be connected to an external network through one or more nodes which act as gateways.
- each MANET node has to be identified by a valid IP address which is necessary to receive packets transmitted by hosts located outside the Mobile Ad-hoc Network.
- Routing issues in MANETs are mainly handled by the Internet Engineering Task Force (IETF) , where a number of MANET routing protocols have been proposed. Among those MANET routing protocols, the Optimized Link State Routing (OLSR) protocol has been standardized.
- IETF Internet Engineering Task Force
- OLSR Optimized Link State Routing
- OLSR Optimized Link State Routing Protocol
- the OLSR protocol enables a MANET node to discover gateways connecting the Mobile Ad-hoc Network to external networks and to build a route to such gateways.
- the Optimized Link State Routing protocol defines a particular type of routing messages to perform gateway discovery.
- Each MANET node can therefore calculate the routes towards the gateways and choose the optimal one (i.e. the default gateway) , with respect to the number of hops, which will be used to send packets to hosts located in the external network (i.e. uplink traffic) .
- the OLSR protocol does not cope with the IP address configuration of the nodes and assumes that each interface on each node is configured with a unique IP address, by means of an unspecified configuration mechanism.
- every gateway runs the NAT: this implies that each gateway replaces the source address of data packets destined outside the MANET with its own global address (which is routable on the external network) .
- the IP source address of outgoing data packets is a globally routable address: return traffic flows through a given gateway towards its destination, located in the MANET.
- an external host will return packets using the IP address of the NAT-gateway as destination IP address.
- the gateway can then replace the destination IP address with the IP address of the IVLANET node and inject the return traffic into the MANET.
- TCP Transmission Control Protocol
- a mobile node running MIPv4 is uniquely identified by an address, named Home Address, belonging to a Home Network.
- Mobile IPv4 defines two functional entities named MIP-Home Agent (MIP-HA) and MIP-Foreign Agent (MIP-FA) , respectively located in the Home Network and in the Foreign (i.e. Visited) Network.
- MIP-HA MIP-Home Agent
- MIP-FA MIP-Foreign Agent
- the mobile node roams to the Foreign Network, it discover the presence of one or more MIP-Foreign Agents and, using Mobile IPv4 signaling, registers the public address of one of the discovered MIP-Foreign Agents, named Care-of Address, to its MIP-Home Agent.
- the MIP-Home Agent intercepts all traffic directed to the mobile node on its Home Network and tunnels it towards Care-of Address on the MIP-Foreign Agent, which, in turn, directly delivers it to the mobile node.
- the mobile node After changing the network it is connected to, the mobile node discovers a new MIP-Foreign Agent and registers the new Care-of- Address to its Home Agent : the Home agent executes traffic redirection.
- the applications use the Home Address, which does not change during roaming, as the end-point for communication and data session continuity is maintained.
- gateways act as MIP- Foreign Agents: a mobile node elects the chosen default gateway as its MIP-Foreign Agent.
- Use of Mobile IPv4 guarantees global connectivity, since each MANET node is uniquely identified by a Home Address, which is reachable from external hosts: traffic directed to Home Address is tunneled by the Home Agent towards the default gateway (acting as MIP-Foreign Agent) , which in turn delivers it to the nodes through a multi-hop path.
- the default gateway change causes also a
- Tuominen in "Global connectivity for IPv6 Mobile Ad Hoc Networks" , IETF Internet expired draft, draft-wakikawa-manet-globalv6-03.txt, specify two mechanisms through which a MANET node can discover gateways and can obtain a global IPv6 prefix from which it can build its global IPv6 address.
- the first mechanism is based upon a reactive solicitation of gateways information by a node which needs global connectivity.
- the second mechanism is based upon a periodical advertisement of gateway information executed by gateways themselves.
- both mechanisms can be realized modifying either the routing protocol or the standard Neighbor Discovery Protocol (NDP) defined by IPv6.
- NDP Neighbor Discovery Protocol
- Such modification consists in configuring a temporary address on the nodes to join routing protocol and receive a global prefix, by means of modified routing messages or modified Neighbor Discovery Protocol messages: temporary addresses are obtained using an IPv6 stateless auto-configuration mechanism, starting from a pre-defined MANET_LOCAL prefix.
- MIPv6 Mobile IPv6 Home Address
- MIPv6 Mobile IPv6 Home Address
- the same address configuration mechanism is applicable also when a node must change its global address: this could happen when its current gateway leaves the MANET, or fails or when the node chooses to change its default gateway within the MANET because of performance reasons. If any of the cases above applies, the MANET node experiments a significant delay, given by the time needed to choose a new default gateway, configure a global address built from a prefix received by chosen gateway and re-join routing protocol with such new global address.
- the time needed by a node to choose a new gateway is negligible, while the amount of time, here defined "Routing Convergence Latency", needed to propagate new address information by means of routing messages to the whole MANET can be significant, heavily depending on routing settings and MANET topology and cardinality.
- the proposed global prefix selection and propagation mechanism enable the prefix continuity, i.e. the existence of a path, between a node and the gateway whose global prefix has been chosen, made of nodes which have configured their global address with such global prefix too.
- a node When a MANET splits into two or more MANETs, it may happen that a node cannot find a route towards its current default gateway.
- the node can choose a new default gateway, but, for downlink traffic reception, the node needs a new global address obtained from a global prefix associated to the new default gateway.
- a MANET node uses a global address obtained by its default gateway to start a session with a host located outside the MANET.
- the default gateway from which the node has obtained such global address acts as Home Agent.
- the node will receive from its new default gateway a new global address, named Locator, used as Care of Address.
- Locator used as Care of Address.
- the node registers the Locator to the gateway acting as Home Agent, which tunnels back to the Locator all the traffic destined to the global address of the node.
- gateways must therefore always be active and its failure implies session break and procedure failure. Moreover, in order to obtain a new Locator, the node experiences delays similar to those described above. Moreover, gateways must maintain and update address information related to all nodes to which they assigned an address.
- A. Laouiti, S. Boudjit, P. Minet and C. Adjih, "OLSR for IPv6 Networks" in Proceedings of Med-Hoc 2004, June 2004 propose a number of changes in the basic OLSR protocol, to enable it to perform IPv6 stateless auto-configuration.
- the auto-configuration procedure relies on two sub procedures: a reactive duplicate address detection process, triggered when a node first join a MANET, and a periodic duplicate address checking process. Both processes use routing protocol messages: in particular, a new type of OSLR message named "Multiple Address Declaration" , which contains all the Ipv6 addresses configured on the network interface, is disclosed in order to perform the periodic checking.
- the Applicant observes that the specific case of an isolated MANET, with no connection to an external network, is considered. In case of address change, especially in the presence of gateways in the MANET, can bring delays similar to those explained above.
- IPv6 is not supported by MANET nodes . So in case of gateway failure, MANET gets disconnected from the
- routing latency has a negative impact over the Mobile IPv6 performance, when supported by MANET nodes : during this period, the Binding Acknowledgment sent by the Home Agent and received by a gateway, cannot be immediately routed to the MANET node which sent the Binding Update, because gateway must first discover a path to the Care-of address of the node, which changed its address. As a consequence, the node starts Mobile IP back-off procedure and the handover cannot be seamless.
- the object of the present invention is thus to provide an improved technique for monitoring and controlling routing operation in communication networks adapted to overcome the limitations of the previous arrangements considered in the foregoing.
- the Applicant has found that the above mentioned problem can be at least partially solved by providing a method for controlling routing operations wherein the gateways announce global . prefixes to the other nodes, where they are used to build a plurality of valid global IP node addresses, and finally these valid global IP node addresses are broadcast to all the nodes of the network.
- the invention also relates to a corresponding system, a related network as well as a related computer program product, loadable in the memory of at least one computer and including software code portions for performing the steps of the method pf the invention when the product is run on a computer.
- a computer program product is intended to be equivalent to reference to a computer- readable medium containing instructions for controlling a computer system to coordinate the performance of the method of the invention.
- Reference to "at least one computer” is evidently intended to highlight the possibility for the present invention to be implemented in a distributed/ modular fashion.
- a preferred embodiment of the invention reduces the Routing Convergence Latency generated in a MANET by Optimized Link State Routing MuIti-Provider Router (OLSR-MPR) election mechanism and topological data propagation, as the result of global address change.
- OLSR-MPR Optimized Link State Routing MuIti-Provider Router
- each node of the network builds two set of addresses : one Primary Address, which is fixed and independent from the prefixes announced by gateways, and
- valid global address it is intended an address which is globally routable, i.e. reachable from all hosts and routers located within external networks (e.g. the Internet) .
- Each node inserts all its secondary addresses into its broadcasted Multiple Interface Declaration (MID) messages, or "MI messages".
- MI Multiple Interface Declaration
- PA Prefix Advertisement
- Each gateway inserts into the generated Prefix Advertisement messages its global prefixes.
- a node is reachable with no significant delay even after its address changes : the connectivity within the
- MANET is achieved through the primary address while global connectivity is achieved by MID messages processing, as every configured global address is a secondary address proactively announced through MID messages.
- MID messages processing does not differ from the processing specified in the OLSR standard.
- a gateway that becomes a node after losing connectivity towards the external network can receive downlink traffic immediately by using the other gateways that are still present in the MANET.
- the present invention thus relates to a method for controlling routing operations in a network, to a related network and to a computer program product therefore, as defined in the attached claims.
- FIG. 2 shows an example of a MANET network linked with a cellular network
- FIG. 3 shows address attributes of a MANET node
- FIG. 4 shows a typical scenario of the arrangement described herein;
- FIG. 5 shows address attributes of a MANET node
- FIG. 6 shows an example of message exchanges ' among nodes in the network.
- Figures Ia and Ib show, respectively, two examples of equipment of a mobile node 10 in a hybrid ad-hoc network, generally designated N in Figure 2. Specifically, Figures Ia and Ib may refer, by way of example, to any of .the mobile nodes designated with 10 in the rest of the description.
- Figure 2 depicts the general context of application considered herein, namely, an ad-hoc network N comprising a set of nodes (designated 10 and 20) wherein topological information on the network N is broadcast to all the nodes 10, 20 in the set.
- the network N has associated an external network 30 with infrastructure.
- the network N is a Mobile Ad-hoc Network (MANET) and the external network 30 is a mobile-radio network (or "cellular network") suitable to provide access to Internet.
- the mobile-radio network 30 comprises a server 32 and a plurality of radio stations 33.
- a number of nodes 20 of the network N are adapted to perform a gateway function between the MANET N and the external network 30 and will be referred to as gateways 20.
- the solution described herein preferably applies to a MANET with the following, exemplary characteristics: - as shown in Figures Ia and Ib, all the nodes of the MANET are equipped with a Wireless Local Area Network Interface (or "WLAN Interface") 10a of a known type, which enables direct delivery of data to other nodes in a transmission range; each node may possibly be equipped with more than one WLAN interface 10a, for example for connections at different bit-rates;
- WLAN Interface 10a Wireless Local Area Network Interface
- certain of the nodes of the MANET are also equipped, in addition to the above interface 10a, with a second radio interface, namely a Cellular Network Interface (or "CN Interface") 10b of a known type, which allows interconnection with the external network 30; these nodes are also preferably equipped with a SIM-card (not shown) ;
- a second radio interface namely a Cellular Network Interface (or "CN Interface") 10b of a known type, which allows interconnection with the external network 30;
- these nodes are also preferably equipped with a SIM-card (not shown) ;
- nodes equipped with both types of interfaces 10a and 10b have an active link towards the external network 30 by means of the CN interface 10b; these nodes are the above-mentioned gateways 20;
- - other MANET nodes which are not equipped with a cellular network interface 10b or which do not have an active link towards the external network 30, communicate with hosts located in the Internet by means of a multi-hop connection to the gateways 20, through other nodes; these are the IVLANET nodes, or terminal nodes, and are indicated with 10 in Figure 2; - all nodes of the MANET run a Network Protocol, e.g. IPv6, and have an address configured on each of their interfaces.
- the gateways 20 have an address CAdd configured on the CN Interface 10b, as shown in Figure 3.
- the gateways 20 own one or more delegated prefixes (P1...PN) that they can assign to other MANET nodes 10 to allow connection with the external network 30.
- These prefixes can be statically configured or dynamically acquired during cellular link activation (e.g. by Dynamic Host Configuration Protocol and Dynamic Host Configuration Protocol prefix delegation protocol) ;
- OLSR permits to use an address, which is independent from the IPv6 addresses configured on the node's interfaces, to identify the nodes and their messages. Such address is called "primary address" and is indicated with PAdd, as shown in Figure 3.
- the primary address PAdd may be for example an IPv6 address, which can be statically or dynamically configured.
- a node uses its primary address PAdd to participate to OLSR protocol. As such, all OLSR messages transmitted by a node contain the primary address of that node into the OLSR "Originator Address" field.
- OLSR normally assumes that each node has one address configured on each interface connected to the MANET: such addresses are defined as "Interface Addresses" . If a node is connected to the MANET by means of more than one interface, all its interfaces must be listed into MID (Multiple Interface Declaration) messages, which are periodically generated by the nodes and broadcasted over the MANET.
- MID Multiple Interface Declaration
- each node has also associated one or more secondary address, which are preferably valid global IPv6 addresses, and which are used as source address for outgoing traffic. Building and use of secondary addresses will be described in greater detail later on.
- the solution described herein comprises two main phases: a first phase called “set-up phase” and a second phase called “normal operation process” .
- the set-up phase performs global addressing of the MANET nodes to allow communication with the Internet. This phase involves three steps, as described in the following.
- the first step of the set-up phase is called “Path Discovery within the MANET” step.
- the MANET nodes 10, 20 exchange OLSR control messages, as specified in the OLSR standard, by using their Primary Addresses PAdd in the Originator Address field.
- gateways 20 generate and broadcast Host and Network Association (HNA) messages: by means of these messages, all nodes become aware of which are the gateways 20 in the MANET and set-up a route towards the external networks.
- HNA Host and Network Association
- the nodes 10, 20 own a path to all the other nodes 10, 20, identified through their Primary Addresses PAdd, and a routing table listing all these paths can be built.
- the nodes of the MANET are not reachable from the external network 30 by their Primary Address PAdd as IPv6 destination address, and can only communicate with the other MANET nodes. In the same way, the nodes cannot use their PAdd as IP Source Address for communication outside the MANET.
- the second step of the set-up phase can be defined as "Transmission and Reception of Prefix Advertisement" step.
- the gateways 20 periodically disseminate delegated prefixes (Pl,...,PN) , which are required to build the global addresses of the MANET nodes.
- Each gateway 20 has associated therewith one or more prefixes .
- These prefixes are disseminated in the MANET by means of Prefix Advertisement (PA) messages implemented as OLSR messages.
- PA messages are broadcast over the MANET . through an OLSR default forwarding algorithm called Multi Point Relay (MPR) and are received by each node in the MANET.
- MPR Multi Point Relay
- the two represented gateways 20 generate respective PA messages PAl and PA2 to disseminate respective sets of delegated prefixes P1...PM-1 and PM...PN.
- PA messages can be considered complementary to HNA (Host and Network Association) messages, whose content is used by the MANET nodes to set up their default route, as specified in the first step, and therefore to send uplink traffic to hosts located outside the MANET.
- HNA Home and
- Each PA message has an OLSR header including an originator address field containing the gateway primary address (PAddl and PAdd2 in Figure 4) .
- Each PA message comprises two further fields, called "Network Address field” and "Net-mask field", which contain a global prefix associated to the gateway (in particular, these fields specify the address and the netmask of the external network reachable through the gateway) .
- Prefix Table for PA message contents management .
- the solution described herein allows building a data OLSR structure, named Prefix Table, for PA message contents management .
- the following Prefix Table is referred to the particular example of Figure 4. This table is OLSR dynamically updated upon reception of PA messages.
- the Prefix Table has four columns; each associated with a respective field, indicated with P_GW_add, P_Net_addr, P_Net_mask, P_time.
- Each Prefix Table entry line corresponds to a different set of values of these fields and contains the information regarding a prefix announced by a gateway.
- - P_GW_add is the primary address of the gateway that generated the processed PA message
- - P_Net_addr and P_Net_mask are respectively the Network Address and the Net-mask of the global prefix inserted into the PA message
- P_time is the time until which the line is valid) .
- each node 10 Upon reception of a PA message, each node 10 creates a line into the Prefix Table initializing the corresponding fields, or refreshing P_time if the line is already present in the Prefix Table.
- P_time is initialized to a default value PtimeValue and is refreshed each time a subsequent PA message is received, using the value contained in the "Vtime" field (defined in OLSR standard) of the OLSR message header.
- a line is removed when P_time expires.
- Each node 10 chooses its global prefix, used to configure its global address, by examining the metric
- each gateway (e.g. the distance in hops) associated to each gateway
- a node 10 shall choose the global prefix associated to the gateway 20 which has the best metric value, according to the routing table metrics. This gateway will be called
- the third step of the set-up phase is called "Interface configuration with global IPv6 address” step and it is performed for configuring each interface 10a of nodes 10, with a global IPv6 address to be used for data transmission.
- each node 10 looks up in the Prefix Table and chooses the line corresponding to the best gateway 20. Then the node 10 builds its global IPv6 address, attaching the value contained in the field P_Net_addr of the chosen line to a unique 64- bit interface identifier.
- this identifier can be an End-System Unique Identifier ("EUI-64 identifier”) , e.g. derived from the MAC address of the node.
- EUI-64 identifier End-System Unique Identifier
- the International Mobile Subscriber Identity of a SIM-card can be used for this purpose. If the Prefix Table contains more than one line associated with the best gateway, the node 10 will choose one of these lines according to a predetermined criterion; for example, it can simply choose the first one in the list.
- the address so obtained is here identified as a "best" secondary address.
- This secondary address is configured on the interface 10a of node 10.
- the considered node 10 builds further secondary addresses by attaching the other announced prefixes contained in the Prefix Table (i.e., the announced prefixes not associated with the best gateway).
- a plurality of secondary addresses (SAddl,..., SAddN) is therefore built, one for each received prefix.
- the considered node could use only a sub-set of the prefixes and therefore build a number of secondary addresses lower than the total number of prefixes.
- the considered node 10 can optionally configure on its interface 10a all the secondary addresses (SAddl,...,SAddN) , as shown in Figure 5, or a subset of them.
- the normal operation process includes a step called: "Broadcasting of MID messages" step.
- the different nodes of the MANET here indicated with 100, 110, 120, 130, 140 and
- MID MID
- (MID) messages 40 each containing the secondary addresses configured on the interfaces 10a in the third step of the set-up phase, which are derived from the prefixes announced by the best gateway, and all the other secondary addresses built in the third step of the set-up phase, or a subset of them.
- Figure 6 shows for example a plurality of MID messages 40 broadcasted in the MANET by node 140.
- MANET nodes routing tables contain a route for each secondary address listed into the MID messages.
- SAdd2 ⁇ l40 ⁇ - Next HOP PAdd ⁇ ll ⁇
- a packet whose destination is one of the secondary addresses of a node e.g. downlink traffic
- All the topological information received and generated by MANET nodes is associated to nodes primary addresses and are therefore independent from the global address configuration of the nodes.
- a node 10 stops inserting a secondary address into MID messages if it detects that the gateway 20 associated to the prefix used to configure that secondary address has failed. If the failed gateway 20 is bound to a prefix associated with a secondary address used for data session, the node considers such address invalid and chooses another one of its secondary addresses. If this secondary address has not yet been configured on the interface 10a, the considered node 10 configures it on the interface 10a. The chosen secondary address must be the one whose global prefix corresponds to the best gateway among the currently active gateways 20. Such choice (made upon the information obtained by the routing table) optimizes downlink traffic routing.
- MID message and PA message processing must be executed by gateways 20 too.
- the only operation a gateway 20 does not have to do is configuring any secondary address on its interface 10a, because gateways 20 already own a global address (CAdd) configured on the 10b interface.
- CAdd global address
- a node 10 in case of data transmission to an external host, sends outgoing traffic using as IP header source address the secondary address associated to the default gateway 20 chosen by OLSR.
- a node executes the following operations :
- the node chooses another active gateway as its new default gateway, by looking at the Routing Table.
- the node chooses, among the active gateways, the one currently associated with the best metric value. This operation is performed seamlessly by each node;
- the chosen address corresponds to the prefix of the new default gateway.
- the node will choose one of these prefixes according to a predetermined rule, for example it may choose the first one in the Prefix Table. If the new global address is not configured on the interface 10a, the node 10 configures it on the interface 10a. Then, the node 10 starts using this new global address as IP source address .
- this address has been already announced with MID messages: this means that all the other MANET nodes already know the correct path to reach the node 10 by this address, therefore avoiding it to bootstrap OLSR with the new address; the time in which the node is not reachable by other hosts and cannot therefore communicate with them is consequently reduced (ideally to zero) .
- a gateway 20 that becomes a node 10 executes the operations that a normal node 10 performs after the change of its default gateway.
- the node 10 that previously was a gateway 20 chooses the secondary address corresponding to the best active gateway 20 and configures it on its interface 10a.
- Such configuration permits the node to communicate with the hosts located outside the MANET.
- the node 10 that was previously a gateway 20 has always been sending MID messages, the communication is not affected by any latency.
- the change of a gateway 20 introduces negligible latency and allows the MANET node 10 that has changed the address to communicate with other hosts immediately after the address change, due to the fact that a node 10 avoids bootstrapping OLSR every time it changes gateway 20 and address.
- the reduction of such latency implies better performances when the MANET nodes use Mobile IPv6.
- a node 10 experiments a change from a first gateway to a second gateway and it is using, as Mobile IP Care-of Address, an address which is derived from the prefix announced by the first gateway, it will choose the second gateway and a secondary address associated to the second gateway, and then it will send a Binding Update message to its Home Agent (which is located within the external network) , registering the new chosen address as the new Care-of Address.
- the Home Agent responds with a Binding Acknowledge message.
- the proposed invention optimizes the routing path of the downlink traffic generated by hosts located outside the MANET.
- the choice of a particular prefix defines the gateway 20 to which external hosts route packets directed to MANET nodes 10, whose addresses are derived from that prefix.
- a node 10 first chooses the best gateway 20 and then configures its own global address using the global prefix advertised by the chosen gateway 20.
- the best gateway 20 is selected with the same mechanism of default gateway selection used by OLSR: in this way, the two gateways 20 will generally be the same and, therefore, uplink and downlink traffic will follow the same optimal path.
- the invention enables a gateway 20 to become a node 10 and permits it to communicate with any other host immediately after it has become a node 10.
- the solution just described can be generalized to any routing protocol, which broadcasts topological information to all nodes.
- the solution can be applied for broadcasting address information related to each node, by means of routing protocol messages.
- Gateways 20 can be fixed nodes, i.e. they do not change their geographical location.
- the uplink interface on the gateways 20 can be a wired interface.
- IP network comprising terminals and/or routers, wired or wireless.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2004800447594A CN101091357B (en) | 2004-10-29 | 2004-10-29 | Method for controlling routing operations in a network, related network and computer program product thereof |
EP04791934A EP1810458B1 (en) | 2004-10-29 | 2004-10-29 | Method for controlling routing operations in a network, related network and computer program product thereof |
US11/666,619 US7586897B2 (en) | 2004-10-29 | 2004-10-29 | Method for controlling routing operations in a network, related network and computer program product thereof |
PCT/IT2004/000600 WO2006046261A1 (en) | 2004-10-29 | 2004-10-29 | Method for controlling routing operations in a network, related network and computer program product thereof |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/IT2004/000600 WO2006046261A1 (en) | 2004-10-29 | 2004-10-29 | Method for controlling routing operations in a network, related network and computer program product thereof |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006046261A1 true WO2006046261A1 (en) | 2006-05-04 |
Family
ID=34959424
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IT2004/000600 WO2006046261A1 (en) | 2004-10-29 | 2004-10-29 | Method for controlling routing operations in a network, related network and computer program product thereof |
Country Status (4)
Country | Link |
---|---|
US (1) | US7586897B2 (en) |
EP (1) | EP1810458B1 (en) |
CN (1) | CN101091357B (en) |
WO (1) | WO2006046261A1 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008109391A2 (en) * | 2007-03-01 | 2008-09-12 | Meraki Networks, Inc. | Node self-configuration and operation in a wireless network |
WO2009038877A1 (en) * | 2007-09-17 | 2009-03-26 | The Boeing Company | Method and apparatus for distributing dynamic auto-summarization of internet protocol reachable addresses |
WO2009038888A1 (en) * | 2007-09-17 | 2009-03-26 | The Boeing Company | Method and apparatus for network routing between a tactical network and a satellite network |
CN102377835A (en) * | 2010-08-20 | 2012-03-14 | 杭州华三通信技术有限公司 | Communication method and device for network element group network |
RU2468524C2 (en) * | 2007-06-15 | 2012-11-27 | Силвер Спринг Нетворкс, Инк. | Method and system designed to provide network protocols and routing protocols for utility services |
US8914445B2 (en) | 2007-10-17 | 2014-12-16 | Futurewei Technologies, Inc. | System and method for diameter prefix authorization |
CN111756637A (en) * | 2019-03-29 | 2020-10-09 | 佳能株式会社 | Information processing apparatus, control method of information processing apparatus, and storage medium |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102004015895B4 (en) * | 2004-03-31 | 2006-10-05 | Siemens Ag | Method for communicating in a WLAN with a group of relay stations and radio access points |
US7539202B2 (en) * | 2004-11-02 | 2009-05-26 | Cisco Technology, Inc. | Maintaining secrecy of assigned unique local addresses for IPv6 nodes within a prescribed site during access of a wide area network |
US9609116B2 (en) * | 2005-01-31 | 2017-03-28 | Nokia Technologies Oy | Establishing an ad-hoc group based on addresses in an e-mail |
US20090031130A1 (en) * | 2005-04-28 | 2009-01-29 | Matsushita Electric Industrial Co., Ltd. | System, associated methods and apparatus for securing prefix-scoped binding updates |
FI20051061A0 (en) * | 2005-10-21 | 2005-10-21 | Nokia Corp | Establishing a non-hierarchical relationship |
US8204039B2 (en) * | 2005-11-30 | 2012-06-19 | Symbol Technologies, Inc. | System and method for data communication in a wireless network |
US8843657B2 (en) * | 2006-04-21 | 2014-09-23 | Cisco Technology, Inc. | Using multiple tunnels by in-site nodes for securely accessing a wide area network from within a multihomed site |
KR100800822B1 (en) * | 2007-01-03 | 2008-02-04 | 삼성전자주식회사 | Method for processing handover in bridge-based cellular ethernet network |
US8489716B2 (en) * | 2007-02-02 | 2013-07-16 | Silver Spring Networks, Inc. | Method and system of providing network addresses to in-premise devices in a utility network |
US7769888B2 (en) * | 2007-06-15 | 2010-08-03 | Silver Spring Networks, Inc. | Method and system for providing network and routing protocols for utility services |
US8233905B2 (en) * | 2007-06-15 | 2012-07-31 | Silver Spring Networks, Inc. | Load management in wireless mesh communications networks |
US8072951B2 (en) * | 2007-06-15 | 2011-12-06 | Silver Spring Networks, Inc. | Method and system for providing routing protocols in a frequency hopping spread spectrum network |
US8279870B2 (en) * | 2007-08-01 | 2012-10-02 | Silver Spring Networks, Inc. | Method and system of routing in a utility smart-grid network |
US8018873B1 (en) * | 2007-11-08 | 2011-09-13 | Juniper Networks, Inc. | Enhanced link state protocol for identifying broadcast networks |
US20100316035A1 (en) * | 2008-02-12 | 2010-12-16 | Panasonic Corporation | Position information management device, network edge device, and mobile terminal |
EP3709182A3 (en) * | 2008-03-31 | 2020-12-23 | Amazon Technologies, Inc. | Configuring communications between computing nodes |
WO2009147468A2 (en) * | 2008-05-27 | 2009-12-10 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for backwards compatible multi-access with proxy mobile internet protocol |
MY150340A (en) * | 2008-10-23 | 2013-12-31 | Mimos Berhad | Wireless network system |
US8893209B2 (en) * | 2009-03-31 | 2014-11-18 | Comcast Cable Communications, Llc | Selection of a proxy device for a network |
US20120250529A1 (en) * | 2010-01-21 | 2012-10-04 | John Lee | Mobile ad-hoc re-routing method |
US8615571B2 (en) | 2010-05-12 | 2013-12-24 | International Business Machines Corporation | Network address assignment in a data center |
CN102143050A (en) * | 2010-09-29 | 2011-08-03 | 华为终端有限公司 | Network connection processing method and device for internet protocol version 6 (IPv6) network |
CN103460789A (en) * | 2011-04-06 | 2013-12-18 | 日本电气株式会社 | Ad-hoc network, user node, management server, communication method and program |
GB2491856B (en) * | 2011-06-14 | 2015-06-17 | Sca Ipla Holdings Inc | Wireless communications system and method |
WO2013130454A1 (en) * | 2012-03-01 | 2013-09-06 | Interdigital Patent Holdings, Inc. | Method and apparatus for supporting dynamic and distributed mobility management |
CN103313414B (en) | 2012-03-09 | 2017-02-08 | 上海贝尔股份有限公司 | Method for radio resource scheduling in wireless local area network |
WO2020023909A1 (en) | 2018-07-27 | 2020-01-30 | GoTenna, Inc. | Vine™: zero-control routing using data packet inspection for wireless mesh networks |
CN114363292A (en) * | 2021-12-08 | 2022-04-15 | 芯讯通无线科技(上海)有限公司 | Network address generation method, communication method, system, device and storage medium |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5636216A (en) * | 1994-04-08 | 1997-06-03 | Metricom, Inc. | Method for translating internet protocol addresses to other distributed network addressing schemes |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1111874A1 (en) * | 1999-12-20 | 2001-06-27 | Telefonaktiebolaget L M Ericsson | Routing in mobile-IP Ad-Hoc networks |
FI109950B (en) * | 2000-01-20 | 2002-10-31 | Nokia Corp | Address Acquisition |
US7327683B2 (en) * | 2000-03-16 | 2008-02-05 | Sri International | Method and apparatus for disseminating topology information and for discovering new neighboring nodes |
US6850532B2 (en) * | 2002-09-20 | 2005-02-01 | Cisco Technology, Inc. | Arrangement in a gateway for registering mobile routers of a mobile ad hoc network to respective home agents |
US7209978B2 (en) * | 2002-12-13 | 2007-04-24 | Cisco Technology, Inc. | Arrangement in a router of a mobile network for optimizing use of messages carrying reverse routing headers |
US7552234B2 (en) * | 2003-02-11 | 2009-06-23 | Cisco Technology, Inc. | Arrangement for establishing a bidirectional tunnel between a mobile router and a correspondent node |
US7149225B2 (en) * | 2003-03-10 | 2006-12-12 | Cisco Technology, Inc. | Arrangement for traversing an IPv4 network by IPv6 mobile nodes via a mobility anchor point |
US6865184B2 (en) * | 2003-03-10 | 2005-03-08 | Cisco Technology, Inc. | Arrangement for traversing an IPv4 network by IPv6 mobile nodes |
KR100579834B1 (en) * | 2003-10-20 | 2006-05-15 | 삼성전자주식회사 | Method for assigning address based on IP site-local prefix pool in Mobile Ad-hoc Network |
US7428221B2 (en) * | 2004-06-01 | 2008-09-23 | Cisco Technology, Inc. | Arrangement for providing network prefix information from attached mobile routers to a clusterhead in a tree-based ad hoc mobile network |
US7443880B2 (en) * | 2004-06-25 | 2008-10-28 | Cisco Technology, Inc. | Arrangement for reaching IPv4 public network nodes by a node in a IPv4 private network via an IPv6 access network |
-
2004
- 2004-10-29 WO PCT/IT2004/000600 patent/WO2006046261A1/en active Application Filing
- 2004-10-29 US US11/666,619 patent/US7586897B2/en not_active Expired - Fee Related
- 2004-10-29 EP EP04791934A patent/EP1810458B1/en not_active Not-in-force
- 2004-10-29 CN CN2004800447594A patent/CN101091357B/en not_active Expired - Fee Related
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5636216A (en) * | 1994-04-08 | 1997-06-03 | Metricom, Inc. | Method for translating internet protocol addresses to other distributed network addressing schemes |
Non-Patent Citations (3)
Title |
---|
KIM B-Y ET AL: "Hierarchical Prefix Delegation Protocol for Internet Protocol Version 6 (IPv6)", DRAFT-BYKIM-IPV6-HPD-00.TXT, 20 October 2003 (2003-10-20), XP002293413 * |
PAAKKANEN P ET AL: "IPv6 prefix delegation-based addressing solution for a mobile personal area network", MULTIMEDIA SIGNAL PROCESSING, 2002 IEEE WORKSHOP ON 9-11 DEC. 2002, PISCATAWAY, NJ, USA,IEEE, 19 May 2003 (2003-05-19), pages 819 - 824, XP010642470, ISBN: 0-7803-7713-3 * |
RYUJI WAKIKAWA KEIO UNIVERSITY JARI T MALINEN CHARLES E PERKINS NOKIA RESEARCH CENTER ANDERS NILSSON UNIVERSITY OF LUND ANTTI J TU: "Global connectivity for IPv6 Mobile Ad Hoc Networks draft-wakikawa-manet-globalv6-01.txt", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, no. 1, 1 July 2002 (2002-07-01), XP015005657, ISSN: 0000-0004 * |
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8339991B2 (en) | 2007-03-01 | 2012-12-25 | Meraki, Inc. | Node self-configuration and operation in a wireless network |
WO2008109391A3 (en) * | 2007-03-01 | 2008-11-06 | Meraki Networks Inc | Node self-configuration and operation in a wireless network |
US9559891B2 (en) | 2007-03-01 | 2017-01-31 | Cisco Technology, Inc. | System and method for hosted network management |
US9237063B2 (en) | 2007-03-01 | 2016-01-12 | Cisco Technology, Inc. | System and method for remote monitoring and control of network devices |
US9210034B2 (en) | 2007-03-01 | 2015-12-08 | Cisco Technology, Inc. | Client addressing and roaming in a wireless network |
WO2008109391A2 (en) * | 2007-03-01 | 2008-09-12 | Meraki Networks, Inc. | Node self-configuration and operation in a wireless network |
US8595357B2 (en) | 2007-03-01 | 2013-11-26 | Cisco Technology, Inc. | System and method for hosted network management |
US7852819B2 (en) | 2007-03-01 | 2010-12-14 | Meraki, Inc. | Client operation for network access |
US8527662B2 (en) | 2007-03-01 | 2013-09-03 | Meraki, Inc. | System and method for remote monitoring and control of network devices |
US8477771B2 (en) | 2007-03-01 | 2013-07-02 | Meraki Networks, Inc. | System and method for remote monitoring and control of network devices |
KR101433995B1 (en) * | 2007-06-15 | 2014-08-25 | 실버 스프링 네트웍스, 인코포레이티드 | Method and system for providing network and routing protocols for utility services |
RU2468524C2 (en) * | 2007-06-15 | 2012-11-27 | Силвер Спринг Нетворкс, Инк. | Method and system designed to provide network protocols and routing protocols for utility services |
GB2465953B (en) * | 2007-09-17 | 2012-08-22 | Boeing Co | Method and apparatus for distributing dynamic auto-summarization of internet protocol reachable addresses |
US7782882B2 (en) | 2007-09-17 | 2010-08-24 | The Boeing Company | Method and apparatus for distributing dynamic auto-summarization of internet protocol reachable addresses |
US7760745B2 (en) | 2007-09-17 | 2010-07-20 | The Boeing Company | Method and apparatus for network routing between a tactical network and a satellite network |
GB2465953A (en) * | 2007-09-17 | 2010-06-09 | Boeing Co | Method and apparatus for distributing dynamic auto-summarization fo internet protocol reachable addresses |
WO2009038888A1 (en) * | 2007-09-17 | 2009-03-26 | The Boeing Company | Method and apparatus for network routing between a tactical network and a satellite network |
WO2009038877A1 (en) * | 2007-09-17 | 2009-03-26 | The Boeing Company | Method and apparatus for distributing dynamic auto-summarization of internet protocol reachable addresses |
US8914445B2 (en) | 2007-10-17 | 2014-12-16 | Futurewei Technologies, Inc. | System and method for diameter prefix authorization |
CN102377835A (en) * | 2010-08-20 | 2012-03-14 | 杭州华三通信技术有限公司 | Communication method and device for network element group network |
CN111756637A (en) * | 2019-03-29 | 2020-10-09 | 佳能株式会社 | Information processing apparatus, control method of information processing apparatus, and storage medium |
CN111756637B (en) * | 2019-03-29 | 2023-04-28 | 佳能株式会社 | Information processing apparatus, control method of information processing apparatus, and storage medium |
Also Published As
Publication number | Publication date |
---|---|
US7586897B2 (en) | 2009-09-08 |
CN101091357A (en) | 2007-12-19 |
CN101091357B (en) | 2011-02-16 |
EP1810458B1 (en) | 2012-09-05 |
US20070258473A1 (en) | 2007-11-08 |
EP1810458A1 (en) | 2007-07-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7586897B2 (en) | Method for controlling routing operations in a network, related network and computer program product thereof | |
Tseng et al. | Integrating mobile IP with ad hoc networks | |
US8670407B2 (en) | Proxy mobile IP | |
EP1011241B1 (en) | Wireless access to packet-based networks | |
EP1011243B1 (en) | Single phase local mobility scheme for wireless access to packet-based networks | |
US7894408B2 (en) | System and method for distributing proxying error information in wireless networks | |
US20020039357A1 (en) | Addressing and routing in mobile ad hoc networks | |
JP2008136243A (en) | Method and system for low-overhead mobility management protocol in internet protocol layer | |
JP2008136243A6 (en) | Method and system for low overhead mobility management protocol in internet protocol layer | |
JP4654703B2 (en) | Network identifier sharing method and mobile router | |
KR100521139B1 (en) | Method for processing packet of ad hoc network | |
JP2008042302A (en) | Ad hoc network and router and mobile ip terminal for composing same, communication system, router, mobile ip terminal, and home agent | |
Kumar et al. | Review Strategies and Analysis of Mobile Ad Hoc Network-Internet Integration Solutions | |
WO2006043503A1 (en) | Communication system for mobile body | |
JP2003309596A (en) | Mobile communication network system, external agent router, address server and packet delivery method used for the same | |
Shin et al. | Gateway discovery and routing in ad hoc networks with NAT-based Internet connectivity | |
Le-Trung et al. | Reducing problems in providing Internet connectivity for mobile ad hoc networks | |
Baumann et al. | A protocol for macro mobility and multihoming notification in wireless mesh networks | |
KR20100073808A (en) | Method for configurating addresses of mobile node in multiples of gateway connected manet and method for selecting a basic gateway of mobile node | |
ES2364597T3 (en) | PROCEDURE AND COMMUNICATIONS SYSTEM FOR THE REALIZATION OF TRANSPARENT WIRELESS MULTIPLE JUMP NETWORKS WITH MOBILITY SUPPORT. | |
Ancillotti et al. | A layer-2 framework for interconnecting ad hoc networks to fixed internet: Test-bed implementation and experimental evaluation | |
Paakkonen et al. | IPv6 prefix delegation-based addressing solution for a mobile personal area network | |
Nie et al. | Handoffs in integrating ad hoc networks to Internet | |
Shankar et al. | Review Techniques and Fundamentals of Internet Access Solutions: MANET-INTERNET Integration Scenario | |
Bondareva et al. | Handling addressing and mobility in hybrid wireless mesh networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BW BY BZ CA CH CN CO CR CU CZ DK DM DZ EC EE EG ES FI GB GD GE GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MK MN MW MX MZ NA NI NO NZ PG PH PL PT RO RU SC SD SE SG SK SY TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SZ TZ UG ZM ZW AM AZ BY KG MD RU TJ TM AT BE BG CH CY DE DK EE ES FI FR GB GR HU IE IT MC NL PL PT RO SE SI SK TR BF CF CG CI CM GA GN GQ GW ML MR SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004791934 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11666619 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200480044759.4 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2004791934 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 11666619 Country of ref document: US |