JP5123360B2 - Routing method and system for IP mobile network, corresponding network and computer program product - Google Patents

Description

  The present invention relates to a traffic routing technique in a communication network, and has been developed particularly for application to a so-called IP-based mobile network. The term “IP-based mobile network” refers to a mobile network that employs the IP protocol for data routing.

  However, it should be noted that reference to this particular field should not be considered as limiting the scope of the present invention.

  A scenario that characterizes IP-based mobile networks is that a mobile user moves through the network and generates traffic that is routed in the network towards the node (corresponding node) with which the user is communicating. It is. During a user's move, the user can connect to a different network than the user's service provider or operator's network. In this case, the user may enter an unknown access network where there is no agreement on mobility management or roaming.

  In this situation, it is necessary to be able to communicate wherever the user is and to keep all the communication sessions that the user has in progress.

  During a user's move, the user may have to change the access network (subnetwork) that allows the user to use the IP service. This operation must be transparent to the user so that the user can continue to communicate with the corresponding node without interruption.

  Due to their inherent nature, conventional protocols used as the basis for IP networks have been unable to manage IP terminals moving within the network. To fill this gap, a standardization group known as IETF (Internet for Engineering Task Force) created the Mobile IP protocol, which allows mobile terminals to enter the network so that they are transparent to the application. Allows you to change the connection point. This Mobile IP protocol is available as Mobile IPv4 in IPv4 based networks and Mobile IPv6 in IPv6 based networks.

  Mobile IPv6 is described in the document draft-ietf-mobileip-ipv6-24. This is the first reference herein to the draft ... or RFC ... standard, but relevant information can be found at the IETF website as of the filing date of this application at the address http: // www. ietf. org.

  When Mobile IPv6 is adopted, two IP addresses must be assigned to the mobile node. The first address is its home address (HoA), which does not change and is used to uniquely identify the identity of the node (also referred to later as a mobile node or terminal). The second address is a care-of address (CoA), which belongs to the accessed subnet and is used to identify the actual location of the mobile terminal.

  For any movement that means a change in the IP subnet being accessed, a mobile terminal (Home Agent (HA)) where the mobile terminal has its own care-of address on its provider's network (also called the "home network") Registration). Other IP terminals attempting to communicate with the mobile node by contacting the mobile node on the same mobile node provider's network (via the home address) are brought to the mobile node's actual location by the home agent HA. It is redirected towards it, which is identified by a care-of address. In this way, all traffic directed to the mobile node is sent by the home agent to the user's current address, the care-of address. Therefore, the mobile node can always contact regardless of the connection point to the network.

  FIG. 1 shows a general scenario for the use of Mobile IPv6 in an IP network hosting a mobile node.

  In particular, in FIG. 1, a mobile node MN (mobile node) indicated by 100 is linked to an access network indicated by 104.

  The network 104 allows the mobile node 100 to establish a connection with its provider's network 112, and in particular, a communication session 102 with a particular server, indicated at 114 in FIG. 1 and called a home agent (HA). Makes it possible to establish

  Reference numerals 106, 108 and 110 denote other networks (sub-networks) for accessing the IP network. Further, reference numeral 116 indicates an interconnection network between the provider's network 112 of the mobile node 100 and another provider's network 118. Movement of mobile node 100 within the network is indicated by arrow 120.

  Mobile IPv6 defines two communication methods between the mobile node 100 and a node with which the node 100 is communicating (referred to as “corresponding node”). These two schemes are shown in FIG.

  The first scheme, called a bidirectional tunnel (BT), requires that the movement of the mobile node 100 be known only to its home agent 114. Thus, all traffic related to the mobile node 100 is intercepted by the home agent 114, which redirects towards the correct destination, the mobile node's care-of address.

  In this way, all traffic generated and received by the mobile node 100 passes through the network 112 of the same mobile node provider. In FIG. 2, a traffic route (referred to as a bidirectional tunnel) according to this method is drawn with a broken line and indicated by reference numeral 124.

  The second method is referred to as route optimization (RO), and means that the movement causes the mobile node 100 to transmit information about its new location, that is, the new care-of address, to the corresponding node 130 as well. In this way, the correspondent node 130 can directly exchange traffic with the mobile node 100 when it knows its address (ie, the care-of address) within the network being accessed.

  Thus, traffic directed to the mobile node 100 no longer necessarily passes through the provider's network 112, and can follow an “optimized” path shown in solid lines in FIG. . All this is done by at least partial exclusion of the provider's network 112.

  Since traffic routing can be optimized, the possibility of communication by the second scheme, namely route optimization, has been introduced in Mobile IPv6. This usually results in an improvement in the performance experienced by the user due to better management of network resources so that overloading of the provider's network with respect to the mobile node causes the provider's network 112 to be at least partially out of the routing path. It is prevented by excluding it.

  According to the Mobile IPv6 standard, the choice of communication in the bidirectional tunnel method or route optimization method is left entirely to the mobile terminal, and the provider's network (ie the network indicated by 112 in FIGS. 1 and 2) is There is no intervention for this choice.

  This operational behavior is also fully applicable when the user moves within the network of the user's provider (eg, mobile operator or Internet service provider (ISP)), or other provider's network with which roaming agreements are made. . In fact, in all these cases, regardless of the routing scheme (ie bi-directional tunnel or route optimization), the provider to which the mobile user subscribes to the service with the cooperation of the provider managing the accessed network is always The resulting traffic can be monitored and checked. All of the above is taken to ensure the uniformity of the services provided and thereby the potential for billing, whenever the connection point to the network changes.

  However, in a wider mobility scenario that can be moved to local networks (eg, corporate or corporate networks, free access public networks) without roaming agreements, communication with route optimization In this case, it may happen that the service provider no longer knows the type and amount of traffic generated by the user. This is true even if the supplier exclusion is only partial rather than complete. In fact, the supplier continues to allocate resources to guarantee the user a set of value-added services, such as guaranteeing reachability to the user's own home address and managing mobility while moving.

  Lacking enough information to ensure the uniformity of the service provided, the provider can use the home agent when the user is connected to an access network that is not roaming (ie, an unknown access network). You can choose to block the service at.

  Obviously, this situation is disadvantageous for users who cannot actually have a reliable mobility level, as service continuity can no longer be guaranteed.

Objects and Summary of the Invention From the above description of the state of the art, it is possible to manage in a fully satisfactory manner the situation in which mobile users connect to a local network where there is no roaming agreement by the provider to which the user is subscribed. The need for technology to make clear.

  The object of the present invention is to satisfy such a requirement.

  According to the invention, the above object is achieved by a method having the features set forth in the claims. The invention also relates to information technology products that include portions of software code that can be loaded into the memory of at least one computer and perform the above method, as well as related systems. Thus, as used herein, reference to such an information technology product refers to a computer readable means containing instructions for controlling a computer system to coordinate the execution of the method according to the invention. Is considered to be equivalent to The phrase “at least one computer” is intended to highlight the possibility of implementing the present invention in a distributed and / or modular fashion.

  In a presently preferred aspect of the invention, it is necessary to check traffic routing for mobile nodes associated with the provider's network. A mobile node can communicate with at least one corresponding node associated with another network. For mobile nodes and corresponding nodes, at least one first mode of operation (eg, bi-directional tunnel) over the provider's network and a second mode of operation (eg, route optimization) due to at least partial exclusion of the provider's network. ) Is likely to communicate. There is at least one element associated with the provider's network, typically a home agent, which serves the mobile node and operates in the second mode of operation with the exclusion of the provider's network Configured to selectively check permissions.

  The solution described here allows the provider to maintain monitoring for user-generated traffic without restricting the user's freedom of movement. In particular, whenever a user connects to an unknown access network, there is no need to disconnect the user if necessary.

  To achieve this goal, in one aspect described herein, a service provider can selectively prohibit the use of route optimization techniques to force users to continue communicating in a two-way tunnel. In some cases, it is envisaged that intervention may be possible. All of the above is performed so that traffic from and to the mobile node passes through the network of the provider to which the user subscribes (so-called “home network”).

  This method of operation can be used by a provider to monitor user activity when the user moves to an access network where no roaming agreement exists. In fact, all traffic sent and received by mobile nodes in this way is routed through a centralized server (ie home agent) and collects information about service usage (including billing data) on this centralized server. And / or a dedicated policy can be executed on a particular application flow.

  In the presently preferred aspect, the technical solution described above assumes that the home agent sends out a mobile node to establish route-optimized communication based on a policy created by the network administrator. At least one of the signaling messages generated can be intercepted, for example if the mobile user is connected to an unknown network, intervening in the procedure and communication can continue in the two-way tunnel.

  The invention will now be described by way of non-limiting examples with reference to the accompanying drawings.

2 illustrates a general scenario for the use of Mobile IPv6 in an IP network hosting a mobile node. Two communication systems are shown between the mobile node 100 and the corresponding node. It is a functional flowchart showing the registration procedure of mobile IP protocols, such as mobile IPv6. It is a functional flowchart showing communication from the corresponding node to a mobile node by a bidirectional tunnel system. It is a functional flowchart showing communication from the mobile node MN to a corresponding node by a bidirectional tunnel system. It is a figure showing the update of the new position in a corresponding node. It is another figure showing the procedure called "return routability". It is a figure which shows in detail the method of checking the possibility of communication by a route optimization system by a mobile node. Here is a message format that can be used in the solution described here. In order to start communication in route optimization, a field to be examined by a home agent inside a signaling packet transmitted by a mobile node is shown.

Detailed Description of Embodiments of the Invention The Mobile IPv6 Protocol (MIPv6) is a solution proposed within the IETF (Internet Engineering Task Force) to handle terminal mobility between IPv6 networks ( draft-ietf-mobileip-ipv6-24).

  The protocol allows mobile nodes (already indicated at 100 in FIGS. 1 and 2) to connect to the network from different locations while maintaining a single identity and to keep existing connections usable. Can be changed dynamically.

As already mentioned, this protocol is
-Two different IPv6 addresses for each mobile node: a home address and a care-of address, and
-A new agent called Home Agent (HA),
To manage the mobility of the mobile node (MN).

Of two different addresses:
i) The first address, i.e. the home address (HoA), is the address assigned by the provider to which the user subscribes. This address never changes (at least during the work session) and is used to uniquely identify the identity of the mobile node.
-ii) The second address, the care-of address (CoA), is an address belonging to the accessed network and is dynamically obtained by the mobile node by IPv6 automatic configuration. This address identifies the current location of the mobile node and thus changes with each movement of the same mobile node.

  This new agent, or home agent (HA), is provided on the network of the provider to which the user subscribes (so-called “home network”) and is destined for the mobile node 100 (ie home address). With the task of redirecting traffic addressed to the current location (ie care-of address or CoA) of the same mobile node.

  In FIG. 3, when the mobile node 100 moves and changes its connection point, it corresponds to its current location in the network 140 accessed via IPv6 autoconfiguration (eg, stateless autoconfiguration, see rfc2462). Get a new CoA (indicated by 101b).

  At this point, the mobile node 100 notifies the home agent 114 of this address (ie, CoA) by a signaling message 150 (referred to as a binding update).

  The home agent 114 updates the table indicated by 170 (referred to as a binding cache) to store the new location of the mobile node 100 and the same mobile node via a binding acknowledgment message 160. In response to 100, the successful registration result is confirmed.

  In the binding cache table, addresses HoA and CoA exist in the field 172 in addition to the mobile node identifier stored in the field 171. Finally, field 173 of this table is given information about the validity period of the previous field.

  4 and 5, once the mobile node 100 has registered, the home agent 114 intercepts all traffic destined for it and tunnels it to the mobile node via "IPv6 in IPv6" tunneling. Redirection to the current location (ie CoA).

  In this manner, the corresponding node (CN) indicated at 130 need not necessarily know the movement of the mobile node 100. That is, everything is done as if the mobile node 100 is still on the home network 112. Similarly, the mobile node 100 encapsulates the packet into a packet destined for the home agent 114 so that the packet from the home network 112 (and thus having the home address as the source address) can reach the corresponding node 130. Transmit to the corresponding node 130.

  4 and 5, reference numeral 180 indicates a general IP packet sent to the home agent 114 by the corresponding node 130. This packet has the address of the corresponding node 130 (field 181) as the source address and the home address HoA (field 182) of the mobile node 100 as the destination address. Further, the payload exists as a field code 183.

  Reference numeral 190 indicates a packet obtained from the encapsulation operation performed by the home agent 114. In particular, reference numerals 193, 194 and 195 indicate three fields corresponding to the fields 181, 182 and 183 of the packet 180. In the packet 190, these three fields are preceded by two fields 191 and 192, which represent the source and destination addresses of the encapsulated packet, respectively, of the home agent 114, respectively. The address and the care-of address CoA of the mobile node 100 are included.

  In the case of the packet of FIG. 5, the structure of the packets 180 and 190 shown in FIG. 4 is similar to that of FIG. 5, except that the field order is changed to take into account the different directions of the associated traffic. It is also maintained in the packet.

  As can be seen from the diagram described above, the corresponding node 130 is not the destination of any Mobile IPv6 signaling message, and thus can continue to communicate with the mobile node 100 even if it does not support the protocol.

  The traffic routing obtained by the bidirectional tunnel method is not optimized. In fact, all packets sent by or addressed to the mobile node 100 must pass through the home agent 114, and thus the home network 112 (ie, the network of the provider to which the user is subscribed to service). ) You have to go up.

  This is the reason why a second communication method called route optimization is provided between the mobile node 100 and the corresponding node 130.

  In accordance with the communication method shown in FIG. 6, the mobile node 100 notifies the corresponding node 130 of its position (ie, CoA indicated by 101b) by a message 150 called binding update. From that very moment, mobile node 100 and corresponding node 130 can communicate directly, thus preventing their traffic from passing through home agent 114.

  FIG. 6 shows a procedure for updating information related to the position of the mobile node 100 at the corresponding node 130. In order to operate in a route optimized manner, the corresponding node must support Mobile IPv6, i.e. with a table 170 called a binding cache, to store and update the actual location of the mobile node 100.

  All mobile IPv6 signaling messages are authenticated to prevent security attacks based on fake registrations. Mobile node 100 and home agent 114 can be assumed to share a security association, so the IPsec protocol can be used for this purpose, but the correspondent node can be any node in the Internet, so it can move with correspondent node 130. The node 100 cannot be assumed to share a preset secret.

  For this reason, Mobile IPv6 introduces a signaling procedure called return routability. This signaling procedure allows these nodes to exchange keys and secure signaling even though they do not share a secret.

The return routability procedure is shown in FIG.
The mobile node 100 sends two messages: a message indicated at 200 and called Home Test Init (HoTI) and a message indicated at 202 and called Care-of Test Init (CoTI). This first message is transferred in a bidirectional tunnel manner (ie, via the home agent 114), and the second message is sent directly to the corresponding node 130 using the care-of address 101b as the source address. The message 200HoTI is protected by IPsec along the network path between the mobile node 100 and the home agent 114 (see draft-ietf-mobileip-mipv6-ha-ipsec-04).
-Upon receipt of these two messages 200 and 202, the correspondent node 130 generates some random data and converts them into two additional messages: Home Test (HoT) indicated by 204 and Care- It is sent to the mobile node 100 together with of Test (CoT). This first message 204 is addressed to the HoA (101a) and the second message is addressed to the CoA (101b) of the mobile node 100. Along the network path between the home agent 114 and the mobile node 100, the message 204HoT is protected by IPsec.
-At this point, the mobile node 100 and the corresponding node 130 use the random data generated by the corresponding node 130 to generate a shared secret and use this value for all signaling messages they exchange (binding update message). 150 and the binding acknowledgment message 160).

  Therefore, Mobile IPv6 leaves selections for communication in the bidirectional tunnel method or route optimization method to the mobile node 100, and policies for making these selections are not analyzed within the standard.

  Assuming mobility scenarios where movement towards a local network without a roaming agreement may occur, the choice of communicating in a route optimization scheme is assigned by the service provider to the user's traffic (both type and volume) and to it. May hinder monitoring resources. This is unacceptable. This is because a user is linked to a third party network, but continues to use multiple value-added services provided by the user's original provider through the home agent (ie, Guarantees the possibility of arrival at the user's own home address and mobility management during the user's movement.

  Thus, in such a case, the provider simply decides to shut down the service at the home agent whenever the user connects to an access network that is not roaming (ie in the case of an unknown access network). be able to.

  A typical example of when this situation occurs is that the last-running user is managed as a free access or pay-per-use network by the community or private person after starting a work session within the user's own provider's network (eg GPRS) This is a case of moving to a local network (for example, a wireless LAN).

  In such a case, even if the mobile user 100 is connected to a public network and thus does not use the network access (eg GPRS) provided by the user's own provider, the mobile user 100 will benefit from the home address and the home agent. Continue to receive contact services provided by.

  The solution described here introduces a mechanism that allows a provider to continue to monitor traffic generated by a user without restricting the user's freedom of movement. In particular, it eliminates the need to forcibly disconnect a user when the user moves into an unknown access network.

  To this end, the solution described here allows service providers to use route optimization techniques to ensure that all traffic to and from the mobile node must go through the user's own home network. It is assumed that the user can be forcibly prohibited and the user can be forced to communicate in the bidirectional tunnel method.

  In particular, the solution described here allows the provider's network to notify the mobile node whether or not communication in the route optimization scheme is permitted. In addition, the provider's network can decide to prohibit the use of route optimization schemes by unauthorized mobile nodes. Thus, the selection of the communication method is monitored by the provider.

What forms the architecture and participates in the execution of the functions envisaged by the solution described here is substantially as follows.
-Home agent 114. Here, based on policies established by the administrator, some of the signaling messages exchanged during the return routability procedure can be selectively intercepted so that the mobile node 100 communicates in a route optimized manner. Modules are arranged that can affect the possibilities. By using an extension in the Binding Acknowledgment (BA) message, this module is also allowed to communicate in a route optimized manner from its current location, or is a different policy applied to it It has a task to notify the mobile node 100 whether or not.
-Mobile node 100. Here, each module that can interpret the notification sent by the home agent 114 in the binding acknowledgment message is arranged. It is optional to provide this module on the mobile node 100. If the mobile node 100 cannot be notified that communication in the route optimization scheme is not allowed from the current location, the same mobile node 100 assumes that the failure to complete the procedure has occurred due to normal loss of signaling packets. The solution proposed here actually works correctly (although it requires a larger bandwidth) under the condition that the return routability procedure continues to repeat at regular intervals.

  In this regard, an example of a procedure that can be applied to the solution described here is shown in FIG. In particular, the movement of the mobile node 100 (represented by the cross 300) causes the mobile node 100 to leave its “home network” 112 and enter a network that does not have a roaming relationship with an operator acting as a provider of the network 112. is assumed.

  First, as given by Mobile IPv6, the mobile node 100 sends a binding update message 150 indicating its new current location (ie, a new CoA) to its own home agent 114.

  The mobile node 100 can then initiate a return routability procedure to communicate with one of its corresponding nodes 130 in a route optimization manner.

For this purpose, the mobile node 100 sends the following two messages simultaneously.
-The Home Test Init message 200 is sent to the corresponding node 130 by the bidirectional tunnel method. Thus, message 200 is encapsulated in a second message addressed to home agent 114. This means that the message 200 reaches the home agent 114 before reaching the corresponding node 130.
A Care of Test Init message 202 is sent directly to the corresponding node 130 without going through the home network 112.

When the binding update message 150 is received, the home agent 1
14 registers the new location of the mobile node 100 in its binding cache 170, and the mobile node 100 communicates from its current location in a route optimized manner (based on a policy defined by the network administrator). It is verified whether or not is permitted.

  This check can be done in various ways.

  For example, the home agent 114 may maintain a table that includes a list of network prefixes that allow (or specifically prohibit) communication in a route optimization scheme. This table may be specific to each user (eg, some users may also be allowed to use route optimization schemes from any network according to the service profile).

  Alternatively, the home agent 114 can analyze the information present in the authentication server to verify whether the user is accessing from a known network (ie, a network where a roaming agreement exists).

  In the former case, based on the user's service profile, it is possible to determine whether to allow the route optimization procedure in consideration of the identity of the network / operator from which the user is accessing.

  Instead, in the latter case, the operator can decide whether to allow route-optimized communication unconditionally or to determine them on a case-by-case basis considering the user's service profile.

  If the mobile node is allowed to communicate in route optimization from its current location, the procedure ends with the transmission of the binding acknowledgment message 210 to the mobile node. The format of the message is assumed by Mobile IPv6 because there is an additional bit (indicated by 250 in FIG. 9) that is used to inform the mobile node that route optimized communication has been enabled. Different from format.

  When the additional bit 250 is set to 1, the route optimization scheme is enabled, and when set to 0, the route optimization scheme is disabled.

When the mobile node is not permitted to communicate in the route optimization method, the home agent performs the following two operations. That is,
-Sends a binding acknowledgment message to the mobile node, notifying that route optimization is not enabled in the accessed network.
-Apply a filtering policy to the Home Test Init (HoTI) message sent by the mobile node 100 to prohibit forwarding towards the corresponding node. In this way, the completion of the return routability procedure is prevented and the mobile node is forced to continue communicating in the bidirectional tunnel method.

  The procedure described in FIG. 8 can be repeated at predetermined time intervals so that, if necessary, the home agent 114 can continue the session with route optimization subject to a defined rate / cost billing plan. .

  FIG. 10 shows a format of a Home Test Init (HoTI) message sent from the mobile node 100 to the home agent 114 by the bidirectional tunnel method.

  The fields indicated by 302 and 304 represent the source address and destination address of the IP packet, respectively, where the HoTI message is encapsulated and forced through the home agent.

  Field 302 contains the mobile node's care-of address and field 304 contains the home agent address.

  The subsequent fields indicated at 306 and 308 represent the source address and destination address of the HoTI message itself, respectively. Field 306 contains the home address of mobile node 100 and field 308 contains the address of corresponding node 130.

  Fields 310 and 312 represent the information content of a message encoded in the form of a mobility header as specified in the Mobile IPv6 standard. In particular, field 310 contains an indication of the type of message being exchanged, ie the mobility header type. It can be understood from the contents of the field 310 whether the message is a HoTI message or a different signaling message assumed by the Mobile IPv6 standard.

  Eventually, reference numeral 314 indicates a filter present in the home agent HA, which is generated by the mobile node 100 when the mobile node 100 is not allowed to communicate in a route optimization manner from its current location. Selectively block incoming HoTI messages. Filter 314 acts on fields 302, 306 and 310.

  It can be seen that the filter 314 examines both the outer header 302 and the inner header 306 of the packet, including the mobility header type 310 (from which it can understand whether the packet is actually a HoTI message).

  Once the mobile node receives a binding acknowledgment message that informs it that communication in the route optimization scheme is prohibited, it should stop sending HoTI and CoTI messages.

  Such behavior is arbitrary and in any case does not affect the effectiveness of this procedure because the HoTI message is blocked by the home agent 114 before reaching the corresponding node 130. In any case, as such, the mobile node 100 avoids sending unnecessary signaling traffic over the network, thus optimizing its own bandwidth and processing resources.

The above procedure for controlling route optimization is:
-Mobile IPv6 protocol for managing the movement of mobile nodes;
-Return routability procedures to manage the transition from bidirectional tunnel to route optimization,
Specific scenarios characterized by the use of were set up in detail.

However, the mechanism on which the present invention is based can be extended to the following situations.
-The transition from bidirectional tunnel to route optimization is managed through a procedure different from return routability based on the exchange of one or more signaling messages routed via the home agent.
-The movement of the mobile node is managed by using a different protocol (eg mobile IPv4 protocol, see rfc3344), in which case the transition from bidirectional tunnel to route optimization is the procedure described above (return routability) ) By using equivalent signaling procedures with the same or similar characteristics.

  As a result, without changing the principles of the invention, the details of the embodiments and the forms of the embodiments have been described by way of non-limiting examples, but from the scope of the invention as set forth in the claims. Substantial changes can be made without departing.

DESCRIPTION OF SYMBOLS 100 ... Mobile node 102 ... Communication session 104 ... Access network 106, 108, 110 ... Another network 112 ... Provider's network 114 ... Home agent 116 ... Interconnection network 118 ... Another provider's network 130 ... Corresponding node

Claims (24)

A method for controlling the routing of traffic between the network and the mobile node and the correspondent node, wherein the network further includes a home agent, the mobile node have a address indicating the access network to which the mobile node connects and the home agent stores the address of the mobile node, the method comprising:
Sending a first message to the home agent and sending a second message to the corresponding node when the mobile node initiates communication with the corresponding node without passing through the home agent;
When the home agent receives the first message, if the access network indicated by the address of the mobile node is a specific network, the first message is sent to the corresponding node. Forwarding, thereby allowing communication between the mobile note and the corresponding node without passing through the home agent, the home agent if the access network is not the specific network Not forwarding the first message; and
The corresponding node responding to the first message and the second message, wherein the mobile node receives both a response to the first message and the second message from the corresponding node; when the, the communication not via the home agent becomes possible between the mobile node and the corresponding node, comprising the <br/> step method. The network includes a network of providers associated with the mobile node and the home agent, and the method includes a service of the provider's network (112) to serve the mobile node (100) as the home agent. comprising the step of configuring the server the method of claim 1. The network includes a network of providers to which the mobile node and the home agent are associated, communication via the home agent between the mobile node and the corresponding node corresponds to a first operation mode, and Communication between the mobile node and the corresponding node without passing through the home agent corresponds to a second mode of operation, and the method is performed by the home agent (114) by the mobile node (100). the usage of the operation modes is selectively inhibited, comprising the step of forcing the use of the first operation mode to the mobile node (100), the method of claim 1. The network includes a network of providers to which the mobile node and the home agent are associated, communication between the mobile node and the corresponding node not via the home agent corresponds to a second operation mode, and The method is
Selectively checking the mobile node (100) permission to operate in the second operation mode by the home agent (114) at given intervals ;
The continuation of operation in the second operation mode includes a step of restraining the application of planning a defined rate or billing the <br/>, method according to claim 1 of the mobile node (100). The network includes a network of providers associated with the mobile node and the home agent, the method comprising:
Including steps <br/> to register the current location of the mobile node (100) in said home agent (114), The method of claim 1. Wherein the communication not via the home agent during the mobile node and the correspondence node corresponds to the second mode of operation, the method, or that can communicate with the second operation mode is enabled It comprises sending the symbol the mobile node an acknowledgment message (160) containing the (250) (100) indicating that it is not the method of claim 1. Communication between the mobile node and the corresponding node not via the home agent corresponds to a second operation mode, and the method is such that the mobile node (100) communicates in the second operation mode. Is not allowed,
Sending a message to the mobile node (100) notifying that the second mode of operation is not enabled on another network with which the corresponding node is associated ;
Applying a filtering policies to messages sent toward the corresponding node (130) by said mobile node (100),
Comprising at least one A method according to claim 1 of the. The network includes a network of Puropaida the mobile node and the home agent associated network of said Puropaida (112) is a network for managing the mobility of the terminal by the mobile IP protocol, according to claim 1 Method. The communication via the home agent during the mobile node and the corresponding node corresponds to the operation mode of the bidirectional tunneling method according to claim 1. The method according to claim 1, wherein the communication between the mobile node and the corresponding node without going through the home agent corresponds to a route-optimized operation mode. Communication between the mobile node and the corresponding node without passing through the home agent corresponds to a second operation mode, and the method uses the Home message as the first message generated by the mobile node (100). using Test Init (HoTI) type messages comprising the step of setting the second operation mode, the method according to claim 1. A home agent for controlling the routing of traffic between a mobile node and a corresponding node in the network , wherein the mobile node has an address indicating an access network to which the mobile node is connected, and the home agent The mobile node stores the address of the mobile node, and when the mobile node initiates communication with the corresponding node without passing through the home agent, the mobile node sends a first message to the home agent and sends a second message When the home agent receives the first message and the access network indicated by the address of the mobile node is a specific network, the first agent is sent to the corresponding node. Forward the message to the corresponding node, thereby Permits communication between the mobile note and the corresponding node without passing through the home agent, and the home agent transfers the first message when the access network is not the specific network. The corresponding node responds to the first message and the second message, and the mobile node receives both a response to the first message and the second message from the corresponding node. In addition, a home agent that enables communication between the mobile node and the corresponding node without using the home agent . The network includes a network of Puropaida the mobile node and the home agent associated, the home agent (114) is a server of the network (112) of said provider to provide the service to the mobile node (100) , home agent of claim 12. The network includes a network of providers to which the mobile node and the home agent are associated, communication via the home agent between the mobile node and the corresponding node corresponds to a first operation mode, and the communication not via the home agent corresponding to the second mode of operation, the home agent (114), said second operation mode according to prior Symbol mobile node (100) between the mobile node and the corresponding node using selectively prohibit the said configured to force the use of the first operation mode to the mobile node (100), home agent of claim 12. The network includes a network of providers to which the mobile node and the home agent are associated, communication between the mobile node and the corresponding node not via the home agent corresponds to a second operation mode, and Home agent (114),
Subject to planning before Symbol the authorization of the mobile node (100) of the work in the second operation mode selectively checking at given intervals, and a defined rate or billing, the second the operation of the mobile node (100) configured to that <br/> so continue, the home agent of claim 12 in operation. The network includes a network of providers to which the mobile node and the home agent are associated, and the home agent (114) includes :
Current position configured <br/> so to register, the home agent according to claim 12, wherein said mobile node (100). Communication between the mobile node and the corresponding node without passing through the home agent corresponds to a second operation mode, and the home agent sends the first message generated by the mobile node (100). Home Test Init is configured to set said second operation mode using the (HoTI) type message, the home agent according to claim 12 as. The network includes a network of providers to which the mobile node and the home agent are associated, communication between the mobile node and the corresponding node not via the home agent corresponds to a second operation mode, and home agent (114), the second operation mode the mobile node symbols acknowledgment message including the (250) (160) indicating that the communication has not been possible or has been enabled (100 13. The home agent of claim 12 , configured to send to: The network includes a network of providers to which the mobile node and the home agent are associated, communication between the mobile node and the corresponding node not via the home agent corresponds to a second operation mode, and when the mobile node (100) is not authorized to communicate in said second operation mode, before Symbol home agent (114),
Sending a message to notify that the second operation mode is not enabled in another network to which the correspondent node is associated with the mobile node (100),
Configured to perform at least one of <br/> and applying filtering policies to messages sent toward the corresponding node (130) by said mobile node (100), according to claim 12 Home agent . A communication network including the home agent according to any one of claims 12 to 19 . The communication network comprises a network of Puropaida the mobile node and the home agent associated network of said Puropaida (112) is a mobile IP-type network, the communication network of claim 20. 21. The communication network according to claim 20 , wherein communication between the mobile node and the corresponding node via the home agent corresponds to a two-way tunnel type operation mode. 21. The communication network according to claim 20 , wherein communication between the mobile node and the corresponding node not via the home agent corresponds to a route optimization type operation mode. A loadable program in the memory of at least one electronic computer, comprising software code portions for performing the method according to any one of claims 1 to 11 programs.

Images