WO2008145035A1

WO2008145035A1 - Mobility management entity, communication system and mobile ip route updating method

Info

Publication number: WO2008145035A1
Application number: PCT/CN2008/070743
Authority: WO
Inventors: Zhonghui Yao; Cheng He; Yonggang Tian
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-05-29
Filing date: 2008-04-17
Publication date: 2008-12-04
Also published as: CN101316222A; CN101316222B

Abstract

A mobility management entity (1) includes: a storage unit (21), a receiving unit (23) and a processing unit (22). The storage unit (21) stores information of a corresponding node of a mobile node, the receiving unit (23) receives current address information of the mobile node from the mobile node, according to the information of the corresponding node stored in the storage unit (21), the processing unit (22) transmits the current address information of the mobile node received from the receiving unit (23) to the corresponding node. A communication system and a mobile IP route updating method are also provided.

Description

Route management method for mobility management entity, communication system and mobile IP

The present invention relates to the field of communications, and in particular, to a mobility management entity, a communication system, and a route update method for a mobile IP. Background technique

The Mobile IP (Mobile IP) protocol provides a routing mechanism that supports the connectivity of a Mobile Node (MN) while moving over an IP network, allowing the MN to remain connected to the network after leaving its home network.

In MIPv4, when the MN leaves the home network, the MN-side always uses the Home Address (HoA) for identification, does not change due to changes in the visited network, and on the other hand, obtains a care-of address (Care of Address, CoA), and registers the CoA with its Home Agent (HA) to associate with a Care of Address (CoA). When the MN receives the data packet transmitted by the correspondent node (Corresponding Node, CN), it will be intercepted by the MN's HA and then sent to the MN's CoA through the tunnel; but when the MN sends the data packet to the CN, it can directly route to the CN. As shown in FIG. 1 , when the CN communicates with the MN, a triangle route is formed, which increases the delay in the transmission process, and it is difficult to guarantee the quality of service (QoS), and also causes the consumption of network resources.

In response to the above problem, MIPv6 performs Route Optimization (RO) processing. Each IPv6 node can maintain a binding address of a home address and a care-of address (HoA-CoA). Because of the existence of the binding cache, CN The data can be directly sent to the MN without going through the HA, thus avoiding the phenomenon of "triangular routing". Therefore, the update maintenance of the binding cache is very heavy. When the MN moves, the MN's CoA changes, MN The CN and home agent are notified to update the binding cache by sending a Binding Update (BU) message.

Currently, the MN notifies the CN to update the binding cache process by sending a Binding Update (BU) message. To ensure the security of signaling transmission, the MN must perform a Round Trip Routability Procedure (RRP) test before sending the BU. On the one hand, the RRP test needs to be transmitted through the HA, which increases the burden on the HA and brings a large delay. On the other hand, since the RRP test can usually protect the MN and CN off-path attacks, But can't come from MN and CN Attacks on the path (On-Path) are protected. Therefore, in order to minimize the impact of on-path attacks, a BU operation must be performed every 420 seconds. This scheme is especially effective for MNs. In the case of MN, a large signaling overhead burden will be incurred. This burden is particularly severe when both communicating parties are mobile nodes. Summary of the invention

Embodiments of the present invention provide a mobility management entity, a communication system, and a route update method for a mobile IP, which not only ensure the security of signaling transmission, but also avoid a large delay with an RRP test scheme, and a heavy one. Signaling overhead burden.

In order to solve the above technical problem, an embodiment of the present invention provides a mobility management entity, including a storage unit, a receiving unit, and a processing unit, where:

The storage unit is configured to save the peer node information of the mobile node;

The receiving unit is configured to receive current address information of the mobile node from the mobile node, where the processing unit is configured to receive, according to the peer node information of the mobile node stored in the storage unit, the receiving unit The current address information of the mobile node to be sent is sent to the opposite node of the mobile node.

Correspondingly, the embodiment of the present invention further provides a communication system, including: a mobility management entity, configured on a network side, configured to receive current address information of the mobile node from a mobile node, and according to the stored The peer node information of the mobile node sends the current address information of the mobile node to the opposite node of the mobile node.

Correspondingly, an embodiment of the present invention further provides a method for updating a route of a mobile IP, including: receiving current address information of the mobile node from a mobile node;

Transmitting the current address information of the mobile node to the peer node of the mobile node; the current address information of the mobile node is used to update the current address in the correspondent node as a care-of address of the mobile node.

In the embodiment of the present invention, each node in the routing system is configured with a home MME, and the MME carries a message from the mobile node carrying the current address of the mobile node according to the saved peer node information of the mobile node. And sending, to the peer node of the mobile node, the peer node as the care-of address of the mobile node by using the current address. Therefore, the information about the current address of the mobile node carried in the binding update (BU) signaling message in the embodiment of the present invention passes through the MN and the mobile node. The mobility management entity (MME/MN) of the home station and the mobility management entity (MME/CN) of the home node of the opposite node are finally sent to one or more CNs, and the signaling transmission can be easily secured. Details are as follows:

The mobile node managed by the same operator communicates with the network because of the signaling interaction between the MME and the MN. Therefore, the security association can be established in advance, for example, using the security mechanism (IPsec) for signaling protection;

Similarly, the MME/CN and the CN can also use the same method for signaling transmission protection. For the communication path between the MME/MN and the MME/CN, since there are mutual trust relationships between different operators, After the negotiation, the signaling transmission on the path is protected by establishing a secure tunnel between the MME/MN and the MME/CN. Moreover, the security tunnel is established on the wired network, and after the establishment, the trust relationship between the operators and the mutual negotiation is expired, so the transmission delay of the BU message is not increased.

In summary, since the entire BU message signaling transmission process has security protection, the Return Routability Procedure (RRP) can be eliminated, and the binding update time is shortened; and no new security threat is introduced. Increased security level, can prevent on-path attacks, extend the life cycle of binding updates, up to 86400 seconds, that is, the MN's HoA prefix valid time is extended, reducing the need for frequent binding updates Signaling overhead. DRAWINGS

1 is a schematic diagram of data exchange between a mobile node and a peer node in the prior art;

2 is a schematic diagram of a first embodiment of a communication system of the present invention;

3 is a network architecture diagram of an application embodiment of a first embodiment of a communication system according to the present invention;

4 is a schematic diagram of a second embodiment of a communication system of the present invention;

5 is a schematic diagram of a network architecture of an application embodiment of a second embodiment of a communication system according to the present invention; FIG. 6 is a schematic diagram of a first embodiment of a mobility management entity of the present invention;

7 is a schematic diagram of a second embodiment of a mobility management entity of the present invention;

8 is a schematic diagram of a third embodiment of a mobility management entity of the present invention;

9 is a schematic diagram of a format of a BU message mobility option according to an embodiment of the present invention;

10 is a schematic diagram of a fourth embodiment of a mobility management entity of the present invention;

11 is a schematic flowchart diagram of a first embodiment of a method for updating a mobile IP route according to the present invention; 12 is a schematic flow chart of a specific step of 1101 in FIG. 10;

13 is a schematic flow chart of a second embodiment of a method for updating a mobile IP route according to the present invention;

14 is a schematic diagram of a format of a BU message according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a format of a BA message according to an embodiment of the present invention. detailed description

Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

First of all, in the embodiments of the present invention, one end node is a mobile node (MN), and the other end node may be a fixed node or a mobile node. For the peer node (CN).

In addition, the information about the current address of the mobile node from the mobile node in the implementation of the present invention may be carried in the binding update message in an actual application, and the binding update message is taken as an example for description.

2 is a schematic diagram of a first embodiment of a communication system according to the present invention, including a Mobility Management Entity (MME) 1 deployed on a network side for receiving the mobile node from a mobile node. The current address information is sent, and the current address information of the mobile node is sent to the opposite node of the mobile node according to the peer node information of the mobile node in the storage unit.

FIG. 3 is a network architecture diagram of an application embodiment of the present embodiment, where a Mobile Node represents a mobile node, an MME/MN represents a mobility management entity of a mobile node's home location, a DNS Server represents a domain name server, and Corresponding Nodes represents a peer node. MME/CN indicates a mobility management entity at the home end of the peer node, and Foreign Link indicates a foreign link.

When the mobile node moves, the mobility management entity of the mobile node's home location first receives the binding update message of the mobile node, and then sends the binding update message to the pair according to the saved peer node information of the mobile node. The mobility management entity of the end node's home location, after receiving the binding update message, the mobility management entity of the home node of the peer node forwards the binding update message to the corresponding peer node.

It should be noted that the application embodiment is different in that the mobile node and the opposite node belong to each other, that is, the mobile node and the opposite node respectively correspond to different mobility management entities, but the mobile node belongs to the local application in actual application. The peer node may also be the same, that is, corresponding to the same mobility management entity, and correspondingly, the mobility management entity MME/MN of the mobile node attribution in FIG. 3 and the mobility management entity MME of the home node of the opposite node /CN is the same.

In addition, the embodiment of the communication system of the present invention may further include a positioning server that stores information of the MME. 2, such as Domain Name Server (DNS), as shown in Figure 4. In a specific implementation, the mobility management entity at the home node of the mobile node queries the domain name server to obtain the MME information of the home location of each peer node, for example, IP, before sending the binding update message to the mobility management entity at the home node of the peer node. The network structure of the application embodiment is as shown in FIG. 5, where the Mobile Node represents the mobile node, the MME/MN represents the mobility management entity of the mobile node's home location, the DNS Server represents the domain name server, and the Corresponding Nodes represents the peer node. MME/CN indicates a mobility management entity at the home end of the peer node, and Foreign Link indicates a foreign link.

The MME in the embodiment of the present invention is described in detail below. Referring to FIG. 6, the figure is a schematic diagram of a first embodiment of the mobility management entity of the present invention. The mobility management entity mainly includes: a storage unit 21, a receiving unit 23, and a processing unit 22 The storage unit 21 stores the information of the mobile node peer node. In actual application, the peer node information is an entry, and the mobile node may register the information of the peer node when registering with the home network, and the peer end The node information can be identified by an IP address, or by other means such as a Session Initiation Protocol (SIP) address or a domain name address. If the IP address is used for identification, when the CN is a mobile node, the CN in the List The IP address of the CN should be the HoA of the CN and the CoA. If the CN is a fixed node, the IP address of the CN in the List is the fixed address of the CN;

The processing unit 22 sends the current address information of the mobile node received by the receiving unit 23 to the opposite node of the mobile node according to the peer node information of the mobile node saved by the storage unit 21, and indicates the peer end The node updates the binding of the home address of the mobile node to the care-of address, and uses the current address as the care-of address of the mobile node; in this embodiment, we assume that the current address information of the mobile node is carried in the binding update. In the message, the processing unit 22 actually sends the binding update message to the opposite node of the mobile node;

The receiving unit 23 is configured to receive current address information of the mobile node sent by the mobile node, for example, receive a binding update message that is sent by the mobile node and carries current address information of the mobile node.

Referring to FIG. 7, the figure is a schematic diagram of a second embodiment of a mobility management entity according to the present invention. Similarly to the first embodiment, the mobility management entity also includes: a storage unit 21, a receiving unit 23, and a processing unit 22.

The method is: when the processing unit 22 is specifically implemented, after receiving the binding update message of the mobile node, determining, according to the saved information of each peer node of the mobile node, the peer node to be updated and binding, Updating the mobility management entity information of the bound peer node home location, and according to the peer end The mobility management entity information of the node sends the binding update message, if the mobility management entity information of the peer node indicates that the peer node is the same as the home location of the mobile node, the update message is directly Sent to the opposite end node, otherwise, the mobility management entity at the home node of the opposite end node sends the binding update message to the opposite end node; or receives the binding from the MME of the mobile node's home location When the update message is sent, the binding update message from the mobility management entity of the mobile node's home location is forwarded to the corresponding peer node; or the binding update message from the correspondent node is forwarded to the corresponding mobile node.

As shown in FIG. 7, the processing unit 22 mainly includes: a policy determining unit 2211, a determining processing unit 2212, and a sending unit 2213;

In a specific implementation, first, after receiving the current address information of the mobile node from the mobile node, the policy determining unit 2211 determines to send the current address information to the opposite node of the mobile node by interacting with the upper application layer. And determining, by the determination processing unit 2212, whether the mobile terminal management of the determined peer node is stored in the storage unit 21 Entity information, if yes, acquiring the mobility management entity information of the home node of the opposite node from the storage unit 21; otherwise, interacting with the positioning server to acquire the mobility management entity information of the home node of the opposite node; The unit 2213 determines, according to the mobility management entity information of the home node of the peer node acquired by the determining processing unit 2212, if the determined peer node and the mobile node belong to the same home location, determine the unit according to the policy. The determined policy of 2211 sends the current address information to the Optional peer node, otherwise, the policy determining unit 2211 according to the policy determined by the mobility management entity of the home terminal node of the determined current transmitting address information to the opposite node selected.

It should be noted that, after receiving the current address information of the mobile node from the mobile node (that is, receiving the binding update message), the policy determining unit 2211 passes the upper layer application according to the saved information of each peer node of the mobile node. The layer interaction determines a policy of sending the current address information to the opposite node of the mobile node, determining which pair of end nodes to send a binding update message, for example, may choose to send a BU message to the N registered CNs that have recently communicated. Or sending a BU message to the CN registered with the online mobile terminal, thereby improving the efficiency of the BU signaling transmission.

In addition, in the embodiment, the setting of the determining processing unit 2212 fully takes into account the information list of the correspondent node registered by the mobile node stored in the storage unit 21, and may include the CN attribution associated with the CN in addition to the HoA including the CN. MME address case, then you can directly from the information list In obtaining the MME information of the home node of the peer node, it is no longer necessary to query the positioning server, such as a domain name server (DNS), to obtain the MME address of the CN home location, which reduces the signaling overhead.

Referring to FIG. 8, the figure is a schematic diagram of a third embodiment of the mobility management entity of the present invention. In this embodiment, the mobility management entity includes the same functional modules as the second embodiment, and the processing unit 22 further Includes:

The peer node information editing unit 2214 is configured to add, delete, or modify the peer node information of the mobile node in the storage unit according to the message received by the receiving unit 23. For example, when the binding update message carries a mobile option indicating that the opposite node is added to the storage unit, or the saved opposite node is deleted, the mobile option is deleted or added according to the mobile option. Peer node information.

In this embodiment, the update problem of the peer node information list is fully considered, and may be updated by the BU message as needed. In addition, when the mobile node registers with the home network, when the information of the peer node is not initialized, When the content of the storage unit 21 is empty, the CN information may also be increased by the mobility option in the BU message.

In addition, the format of the BU message mobility option, as shown in FIG. 9, when the CN node needs to be added, the mobile option type (Type) value is 6, and the main information included is the IP address of the CN to be added, if the CN is a mobile node. , the HoA of the CN is included; when the CN node is deleted, the value of the Type in the mobility option is 7, and the message mainly includes the IP address of the CN to be deleted.

In addition, when the MME address of the CN home location is stored in the storage unit 21, if the CN needs to be added, the MME that includes the CN to be added in addition to the HoA that includes the CN to be added is required in the BU message mobility option. Address; If you need to delete the CN, the mobile option contains the HoA of the CN to be deleted.

In addition, the MME in the implementation of the present invention may also provide a location-hidden service to the MN, as shown in FIG. 10, which is a schematic diagram of a fourth embodiment of the mobility management entity of the invention, which is related to the mobility management entity. The first embodiment is different in that the mobility management entity further includes a data packet processing unit 24, configured to receive a data packet from a correspondent node of the mobile node, and use the data between the mobile node and the local entity to tunnel the data. The packet is sent to the mobile node. That is, when the correspondent node for transmitting the data packet to the mobile node does not belong to the opposite node of the mobile node that has been saved in the storage unit 21, the mobility management entity of the mobile node's home location intercepts the peer end. The data packet of the node, and the data packet is sent to the mobile node through a tunnel with the mobile node, so the MME is compatible with all HA functions, and has strong portability and scalability. In addition, although the MME in the embodiment of the present invention has a packet processing unit, it is mainly used to transmit signaling information such as address information to the CN instead of the MN, and does not participate in the transmission of data information of the user in the case of most data. The separation between the control surface and the user plane is realized, which is conducive to the flattening of communication.

Referring to FIG. 11, which is a schematic flowchart of a first embodiment of a method for updating a mobile IP route according to the present invention, the process includes:

1101. Receive current address information of the mobile node from the mobile node, and send current address information of the mobile node to the correspondent node of the mobile node.

1102. The peer node receives current address information of the mobile node, and uses the current address as a care-of address of the mobile node.

Figure 12 shows a specific implementation flow of steps 1101 and 1102, which may include the following steps:

1201. Receive current address information of the mobile node from a mobile node.

1202: Determine a policy for sending the current address information to a peer node of the mobile node, and select a peer node that receives the current address information;

1203. Determine mobility management entity information of the peer node attribution location;

1204: Determine whether the peer node and the mobile node belong to the same home location, if yes, execute 1205, otherwise execute 1206;

1205: Send the current address information of the mobile node to the peer node according to the policy.

1206. Send the mobile node current address information to the opposite node by using a mobility management entity of the peer node home according to the policy.

Wherein, steps 1202 and 1203 further include:

a determining, according to current address information of the mobile node from the mobile node, a peer node that receives the address information, and acquiring, by the saved peer node information of the mobile node, the selected peer node Information

And determining, according to the information of the selected peer node, whether the mobility management entity information of the selected peer node attribution is saved, and if yes, acquiring mobility management of the selected peer node attribution Entity information, otherwise, interacting with the positioning server to acquire mobility management entity information of the selected peer node attribution.

After step 1102, the correspondent node transmits a data packet with the mobile node according to the updated binding of the mobile node's home address and the care-of address. Here, if the CN that sends the data packet to the MN is not the CN registered by the MN, that is, the peer node information that currently sends the data packet to the mobile node When the information is not saved, the MME of the MN home receives the data packet, and transmits the data packet to the MN through a tunnel in order to hide the address of the MN.

It should be noted that, in the case that the MN location change, the service requirement, or the binding lifetime is about to expire, the MN may initiate a BU message to the MME/MN.

As shown in FIG. 13, the second embodiment of the mobile IP route update method of the present invention includes the following process: MME/MN indicates the MME of the MN home, and the MME/CN indicates the MME of the CN home.

1301. The MN sends a BU message to the MME/MN.

1302. After performing security check on the BU message, the MME/MN updates the binding of the MN.

1303. The MME/MN replies to the MN with a BA message.

1304, the MME/MN acquires the CN information of the MN, determines which CNs in the saved CN need to update the binding of the MN, and obtains information about the CN bound by the MN to be updated, where the CN message may be the HoA of the CN. . In a specific implementation, the policy of sending the current address information to the opposite node of the mobile node is determined by interacting with the upper application layer. For example, the BU message may be selected to be sent to the N most recently registered CNs, or may be online. The CN registered by the mobile terminal sends a BU message, etc., which improves the efficiency of the BU signaling transmission;

1305, the MME/MN sends a Request for MME/CN to the DNS according to the acquired HoA of the CN to be updated by the MN, and queries the address of the MME/CN registered by the mobile terminal.

1306, the DNS replies to the MME/MN Response for MME/CN, and replies to the MME/MN with the address of the MME/CN;

1307, the MME/MN sends a BU message to the MME/CN through a tunnel with the MME/CN according to the address of the MME/CN;

1308, the MME/CN forwards the BU message to one or more corresponding CNs indicated in the BU message;

1309, CN updates the binding cache according to the received BU. In specific implementation, after receiving the message, the CN determines whether it needs to reply to the BA message according to the value of the "A" bit of the BU message, as shown in FIG. The picture shows the basic format of the BU message. If the A bit is set, the BA message is replied. Otherwise, the BA message is not replied.

It should be noted that, in this embodiment, the mobile node MN and the correspondent node CN have different attributions, that is, the MN and the CN respectively correspond to different mobility management entities, but in actual applications, the MN attribution and the CN attribution may also be the same, that is, corresponding For the same mobility management entity, correspondingly, after 1305, 1306 The method further includes: transmitting, according to the mobility management entity information of the peer node, the binding update message, if the mobility management entity information of the peer node indicates the attribution of the correspondent node and the mobile node The same, the mobile node current address information is sent to the opposite node according to the policy, otherwise, execution 1306;

In addition, the MN-registered CN information saved by the MME/MN in the embodiment of the present invention may also be updated. In the specific implementation, the BU message carries the mobility option, and accordingly, after receiving the BU message from the MN, the 1302 receives the BU message from the MN. The CN indicated in the mobile option is deleted or added according to the type of the mobile option. If the mobile option type (Type) value is X (such as 6), the CN indicated in the mobile option is added to the CN information table registered by the MN. If the value of Type in the mobility option is Y (such as 7), the CN indicated by the mobility option is deleted; therefore, the peer node is deleted or added according to the mobility option, and if the BU message is only for deleting the CN node information list, After receiving the BU message, the MME/MN does not send the BU message of the MN to the CN in the list. If the BU message is to add a CN node to the List, the MME/MN adds the CN to the newly added CN after the list is added. The node sends the BU message of the MN. Correspondingly, in step 1303, the MME/MN returns a BA message carrying the relevant status code to the MN to indicate the update status of the CN information table registered by the MN, for example. If the number 2 is carried, it means accepting the addition; if the number 3 is carried, it means accepting the deletion; if the number 140 is carried, it means rejecting the addition; if the number 141 is carried, it means rejecting the deletion, etc., as shown in FIG. , the figure is a schematic diagram of a BA message carrying a status code, where

Mobility Option: indicates a move option;

Sequence #: indicates the sequence number ¹ J;

Lifetime: indicates the lifetime of the binding cache;

Status: indicates the status, that is, the status code in the embodiment of the present invention, for example:

1) 2, indicating acceptance of the entry;

2) 3 , indicating that the entry is deleted;

3) 140, indicating that the entry is rejected;

4) 141, indicating that the entry is deleted;

In addition, the basic format of the BU message in 1308 is briefly described below, as shown in Figure 14:

Mobility Option: indicates a move option;

Sequence #: indicates the sequence number ¹ J;

Lifetime: indicates the lifetime of the binding cache; Reserved: indicates a reserved bit;

A: indicates A bit;

H: indicates H bits;

L: indicates L bits;

K: indicates Κ bit;

In summary, according to the embodiment of the communication system, the mobility management entity, and the mobile IP route update method of the present invention, since the entire BU message signaling transmission process has security protection, the round-trip routable process can be eliminated (Return Routability) Procedure, RRP), shortens the binding update time; does not introduce new security threats, improves the security level, prevents on-path attacks, and extends the life cycle of binding updates, up to 86400 seconds, ie MN The effective time of the HoA prefix is extended to reduce the signaling overhead caused by the need to frequently bind updates.

The above is a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. These improvements and retouchings are also considered. It is the scope of protection of the present invention.

Claims

Rights request

A mobility management entity, comprising:

a storage unit, configured to save the peer node information of the mobile node;

a receiving unit, configured to receive current address information of the mobile node from the mobile node, and a processing unit, configured to receive, according to the peer node information of the mobile node stored in the storage unit, the receiving unit The current address information of the mobile node is sent to the opposite node of the mobile node.

The mobility management entity according to claim 1, wherein the processing unit comprises: a determining unit, configured to determine, after the receiving unit receives the current address information of the mobile node from the mobile node, Receiving the peer node of the current address information;

a determining processing unit, configured to determine whether the mobility management entity information of the determined peer node attribution is stored in the storage unit, and if yes, acquiring mobility management entity information of the home node of the opposite node, otherwise And acquiring, by the positioning server, the mobility management entity information of the home node of the peer node;

a sending unit, configured to determine, according to the mobility management entity information of the home node of the peer node acquired by the determining processing unit, if the determined peer node and the mobile node belong to the same home location, according to the determining The peer node determined by the unit, otherwise, the current address information is sent to the determined peer node by the mobility management entity of the determined peer node home.

The mobility management entity according to claim 1 or 2, further comprising: a peer node information editing unit, configured to add, delete, or modify the binding update message according to the receiving unit The peer node information of the mobile node in the storage unit.

4. The mobility management entity of claim 1, further comprising:

And a data packet processing unit, configured to receive a data packet from the correspondent node, and send the data packet to the mobile node by using a tunnel between the mobile node and the local entity.

A communication system, comprising: a mobility management entity deployed on a network side, And receiving current address information of the mobile node from the mobile node, and sending current address information of the mobile node to the opposite node of the mobile node according to the stored peer node information of the mobile node.

6. The communication system according to claim 5, wherein the mobility management entity comprises:

a receiving unit, configured to receive current address information of the mobile node from the mobile node, and a processing unit, configured to: according to the stored peer node information of the mobile node, the mobile node that is received by the receiving unit The current address information is sent to the opposite node of the mobile node.

7. The communication system of claim 5, further comprising:

The location server is used to save the information of the mobility management entity in the network for the mobility management entity to query.

8. A method for updating a route of a mobile IP, comprising:

Receiving current address information of the mobile node from the mobile node;

The method for updating a route of a mobile IP according to claim 8, wherein the sending the current address information of the mobile node to the opposite node of the mobile node comprises:

And selecting, according to a policy for sending the current address information to a peer node of the mobile node, a peer node that receives the current address information;

Determining mobility management entity information of the selected peer node attribution;

If the selected peer node and the mobile node belong to the same home location, send the current address information of the mobile node to the selected peer node; otherwise, the selected peer node belongs to The mobility management entity of the ground sends the current address information of the mobile node to the selected peer node.

The method for updating a route of a mobile IP according to claim 9, wherein the selecting a pair of the current address information according to a policy of transmitting the current address information to a peer node of the mobile node End nodes include:

Selecting, according to a current address information of the mobile node from the mobile node and a policy of sending the current address information to a peer node of the mobile node, a peer node that receives the address information, from the saved mobile node Obtaining information of the selected peer node in each pair of end node information.

The method for updating the routing of the mobile IP according to claim 9, wherein the determining the mobility management entity information of the selected peer node attribution location comprises:

Determining, according to the information of the selected peer node, whether the mobility management entity information of the selected peer node attribution is saved, and if yes, acquiring the mobility management entity information of the selected peer node attribution Otherwise, interacting with the positioning server to acquire mobility management entity information of the selected peer node attribution.

The method for updating a route of a mobile IP according to claim 8, further comprising:

Receiving indication information from the mobile node, the indication information indicating deleting or adding information of the opposite node of the mobile node;

The information of the opposite node is deleted or added according to the indication information.

The method for updating a route of a mobile IP according to any one of claims 8 to 12, wherein when the information of the peer node that sends the data packet to the mobile node is not saved, the method further includes:

The mobility management entity at the home of the mobile node receives a data packet from the correspondent node, and transmits the data packet to the mobile node through a tunnel of the mobility management entity and the mobile node.