WO2013007129A1

WO2013007129A1 - Packet forwarding processing method, network element and system

Info

Publication number: WO2013007129A1
Application number: PCT/CN2012/075422
Authority: WO
Inventors: 霍玉臻; 骆文; 沈岷; 江鸿; 宋军
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-07-14
Filing date: 2012-05-14
Publication date: 2013-01-17
Also published as: CN102882788A

Abstract

A packet forwarding processing method comprises: in a scenario where mobile access gateway (MAG) switching occurs to a mobile node (MN), a target MAG of the MN (tMAG-MN) and a source MAG of the MN (sMAG-MN) obtaining address information pointing to each other, and establishing a forwarding tunnel; before the switching is finished, the tMAG-MN or the sMAG-MN forwarding a packet between the MN and a correspondent node (CN) through the forwarding tunnel. The MAG comprises a forwarding tunnel establishment unit and a packet forwarding unit.

Description

Message forwarding processing method, network element and system

Technical field

The present invention relates to the field of mobile communications, and in particular, to a text forwarding processing method, a network element (including a Mobile Access Gateway (MAG), and a Local Mobile Anchor (LMA)) and a system.

Background technique

The Transmission Control Protocol/Internet Protocol (TCP/IP) does not consider the topology change of the terminal in the initial design. That is, the TCP/IP protocol itself does not support mobility. In the traditional TCP/IP network environment, IP provides routing for the Internet. It assigns logical addresses, ie IP addresses, to all nodes (including hosts and routers), and each port of each host is assigned. An IP address. The IP address includes the network prefix and the host part. The IP addresses of all hosts on the same link usually have the same network prefix and different host parts. This allows IP to be routed based on the network prefix portion of the destination node's IP address, allowing the router to maintain a simple network prefix route without having to maintain a separate route for each host. In this case, since the network prefix route is used, when the node switches from one link to another without changing its IP address, the node cannot receive the data packet on the new link. Therefore, it is impossible to communicate with other nodes.

As users' demand for mobility and information rises sharply, more and more people want to access the Internet at high speed during the mobile process, get much-needed information, and do what they want. Therefore, the mobile Internet has become the development direction of the future Internet, but the traditional TCP/IP protocol does not support the defect of mobility, making the mobility management of mobile nodes a major problem facing the mobile Internet.

In order to solve the mobility management problem, the industry's more popular mobility management technologies, such as mobile

IP (Mobile IP, MIP), Proxy MIP (PMIP), etc., all support the mobility of the terminal by introducing a fixed anchor (Anchor). For example, the MIP protocol uses a Home Agent (HA) as an anchor point, and the PMIP protocol uses a Local Mobility Anchor (LMA) as a point of error. Figure 1 shows the logical architecture of the PMIP protocol, including the Mobile Node (MN), the Correspondence Node (CN), the Mobile Access Gateway (MAG), and the LMA. The CN can be a fixed node or a mobile node, that is, it has a corresponding MAG and LMA. The MAG is the first hop router of the MN, and its main functions include assigning a Care of Address (CoA) to the MN when it is accessed, and performing PMIP Binding (MMIP Binding) with the MN's anchor LMA instead of the MN. . The LMA acts as the anchor of the MN. Its main functions include assigning the Home of Address (HoA) to the MN and processing the above PMIP binding. The main purpose of the PMIP binding performed between the MAG and the LMA is to let both parties know the address of the other party, the above CoA and HoA, and save it locally. In addition, during the PMIP binding process, a bidirectional tunnel is established between the MAG and the LMA for the MN. It is worth noting that the IP address finally obtained by the MN is the HoA assigned by the LMA. In a typical network deployment, the MAG is generally located at a lower topology, such as at the edge of a metropolitan area network; and the LMA is generally located at a higher topology, such as the core of the provincial backbone. The MAG and the LMA are often connected by a multi-hop router.

The mobility management of the PMIP protocol is reflected in the fact that the current connection to the MN can be changed.

MAG, while keeping the MN's IP address (ie HoA) unchanged. As shown in Figure 2, changing the currently connected MAG means changing/switching the connection to the target MAG (tMAG, target MAG) from the previously connected source MAG (sMAG, source MAG). After changing to tMAG, tMAG assigns a new CoA to the MN, and performs PMIP binding with the MN's anchor LMA for the MN, updating the information saved by the two parties mentioned above, and the t-MAG and LMA. A new two-way tunnel is established for the MN.

Figure 2 shows the process of sending and receiving IP 4 messages between MN and CN. As shown in Figure 2, the IP data packet between the MN and the CN must pass through the tunnel between the sMAG and the LMA before the switchover. After the switchover, the tunnel must pass through the tunnel between the tMAG and the LMA.

As shown in Figure 2 and Figure 3, before and after the MN moves and changes the connected MAG (hereinafter referred to as handover), the path between the MN and the CN can be expressed as MN<->MAG<->LMA<->CN, that is, all IP data messages between the MN and the CN must be detoured to the MN's anchor LMA. Even if the MAG has a routing function, and there is an IP network connection between the MAG and the CN (as shown in Figure 1), IP packets cannot be directly sent and received through the MAG, and there is a waste of the packet transmission path. Especially when the MN is currently located away from its anchor point LMA, and the current position of the MN is When the CN is closer to the CN, the above-mentioned transmission path waste problem will be more obvious. The solid line in FIG. 3 indicates that there is a wasteful route of the transmission path, and the dotted line indicates a route that is not wasted by the transmission path. On the one hand, the waste of the transmission path causes the carrier to waste the transmission of the bearer resources, which leads to an increase in the operating cost. On the other hand, the delay of sending and receiving IP packets between the ΜΝ and the CN is increased, which is not conducive to improving the user experience. It is to make a large number of IP packets converge to the MN's anchor LMA (usually an LMA can serve many MNs), making LMA easy to become a performance bottleneck, increasing the possibility of packet congestion at the node, resulting in a decline in overall network quality. , causing the MN business to be blocked or even impossible to achieve (for example, real-time services such as voice and video).

It is also worth noting that the above CN may also be located in the PMIP domain, and the above PMIP mobility management mechanism is applied (for example, CN is another mobile node, that is, CN shown in FIG. 1). At this time, CN is also connected to a MAG, and there is also an anchor LMA. In this case, the IP packet transmission path between the MN and the CN is: MN<-> MAG of the MN <-> LMA of the MN <-> MAG<->CN of the LMA<->CN of the CN. It can be seen that in this scenario, the message transmission and reception between the MN and the CN must bypass the anchor point LMA of both, and the waste of the message transmission path is more obvious, and the above-mentioned adverse consequences are more serious. To solve the above problem, the packets can be forwarded between the two MAGs. However, the packets cannot be forwarded smoothly during the MAG handover. Summary of the invention

The technical problem to be solved by the present invention is to provide a packet forwarding processing method, a network element, and a system to solve the problem that packets cannot be successfully forwarded during the MAG handover process.

In order to solve the above technical problem, the present invention provides a packet forwarding processing method, and the method includes:

In the scenario where the mobile node (MN) has a mobile access gateway (MAG) handover, the target MAG (tMAG-MN) of the MN and the source MAG (sMAG-MN) of the MN acquire address information pointing to the other party, and establish forwarding. Tunnel

Before the handover is completed, the tMAG-MN or the sMAG-MN forwards the packet between the MN and the correspondent node (CN) through the forwarding tunnel.

Preferably, the step of acquiring the address information of the tMAG-MN and the sMAG-MN to the other party includes: The local mobility anchor (LMA-MN) of the MN sends a first message to the tMAG-MN, where the address information that points to the sMAG-MN is carried;

The tMAG-MN receives the first message, and sends a second message to the sMAG-MN according to the address information that is directed to the sMAG-MN, where the node information that points to the MN and the information that points to the tMAG-MN are carried. Address information;

The sMAG-MN receives the second message.

Preferably, the step of acquiring the address information of the other party by the tMAG-MN and the sMAG-MN includes:

The local mobility anchor (LMA-MN) of the MN sends a first message to the sMAG-MN, where the node information that points to the MN and the address information that points to the tMAG-MN are carried; the sMAG-MN Receiving, by the first message, a second message sent to the tMAG-MN according to the address information of the tMAG-MN, where the node information that points to the MN and the address information that points to the sMAG-MN are carried;

The tMAG-MN receives the second message.

Preferably, before the sending, by the LMA-MN, the method, the method further includes: sending, by the tMAG-MN, a Proxy Binding Update (PBU) message to the LMA-MN, where the message carries a node that points to the MN Information and address information of the tMAG-MN, the LMA-MN transmitting the first message according to the PUB message and the saved binding relationship between the MN and the sMAG-MN.

Preferably, before the first message is sent by the LMA-MN, if the DeRegister message sent by the sMAG-MN is received, the binding relationship between the MN and the sMAG-MN is retained until the first message is sent. The first message is deleted.

When the sMAG-MN determines that the MN is away, sends a first message to the LMA-MN for querying address information that points to the tMAG-MN, where the first message carries node information that points to the MN. ;

Sending, by the LMA-MN, a second message to the sMAG-MN, where the node information that points to the MN and the address information that points to the tMAG-MN are carried; The sMAG-MN sends a third message to the tMAG-MN, where the node information that points to the MN and the address information that points to the sMAG-MN are carried;

The tMAG-MN receives the third message.

Preferably, the sMAG-MN determines that the MN is away from the uplink or downlink data of the MN, or detects that the MN switches or moves away within a preset timer time.

Preferably, the step of forwarding, by the tMAG-MN, the packet between the MN and the correspondent node (CN) by using the forwarding tunnel includes:

The tMAG-MN encapsulates the first packet to generate a second packet, where the source address of the first packet points to the MN, and the destination address points to the CN; the outer source address of the second "3⁄4" text is Addressing the address information of the tMAG-MN, the outer destination address is the address information of the sMAG-MN; the tMAG-MN sends the second packet to the sMAG-MN through the forwarding tunnel.

Preferably, the step of forwarding, by the sMAG-MN, the packet between the MN and the correspondent node (CN) by using the forwarding tunnel includes:

After the sMAG-MN decapsulates the first packet, the second packet is encapsulated or directly encapsulated, and the source address of the first packet is directed to the MAG (MAG-CN) of the CN, and the destination address is directed to the sMAG- MN; the outer source address of the second packet is the address information of the sMAG-MN, and the outer destination address is the address information of the tMAG-MN;

The sMAG-MN sends the second packet to the tMAG-MN through the forwarding tunnel.

Preferably, after the forwarding tunnel is established, the method further includes: the tMAG-MN releasing the forwarding tunnel, and the triggering condition for releasing the forwarding tunnel is a tunnel establishment between the tMAG-MN and the MAG-CN.

Preferably, the node information that points to the MN includes an identifier (ID) of the MN, a home address or a home network prefix, and the address information that points to the sMAG-MN or the tMAG-MN includes the sMAG-MN or tMAG-MN The address, or sMAG-MN or tMAG-MN, is the proxy care-of address (CoA) assigned to the MN.

In order to solve the above technical problem, the present invention also provides a mobile access gateway (MAG), The MAG includes:

a forwarding tunnel establishing unit, configured to: obtain, when the mobile node (MN) is in a mobile access gateway (MAG) handover scenario, as the target MAG (tMAG-MN) of the MN, obtain an address that points to the sMAG-MN Information, establishing a forwarding tunnel; as the source MAG (sMAG-MN) of the MN, acquiring address information directed to the tMAG-MN, and establishing a forwarding tunnel;

A message forwarding unit is configured to: forward, by the forwarding tunnel, a message between the MN and a correspondent node (CN).

Preferably, the forwarding tunnel establishing unit includes:

a message receiving module, configured to: receive, as the tMAG-MN, a first message sent by a local mobility anchor (LMA-MN) of the MN, carrying address information directed to the sMAG-MN; and, as Receiving, by the sMAG-MN, the second message sent by the tMAG-MN; the message sending module is configured to: when the tMAG-MN is used, according to the address information of the first message that points to the sMAG-MN Sending a second message to the sMAG-MN, carrying node information directed to the MN and address information directed to the tMAG-MN.

Preferably, the forwarding tunnel establishing unit includes:

a message receiving module, configured to: when the sMAG-MN is used, receive a first message sent by the local mobility anchor (LMA-MN) of the MN, carry node information directed to the MN, and point to the tMAG- The address information of the MN; and, when the tMAG-MN is used, receiving the second message sent by the sMAG-MN;

a message sending module, configured to: when the sMAG-MN is used, send a second message to the tMAG-MN according to the address information of the first message in the tMAG-MN, and carry the node information that is directed to the MN And address information pointing to the sMAG-MN.

Preferably, the forwarding tunnel establishing unit includes:

a query module, configured to: send the first message to the LMA-MN as the sMAG-MN and determine that the MN is away; query the address information that points to the tMAG-MN, where the first message carries the Node information of the MN;

The message receiving module is configured to: when the sMAG-MN is used, receive the second message sent by the LMA-MN, and carry the node information that points to the MN and the address that points to the tMAG-MN Receiving, as tMAG-MN, receiving a third message sent by the sMAG-MN;

The message sending module is configured to: when the sMAG-MN is used, send a third message to the tMAG-MN, carrying node information that points to the MN and address information that points to the sMAG-MN.

Preferably, the determining that the MN is away includes not receiving uplink and downlink data of the MN within a preset timer time, or detecting that the MN switches or moves away.

Preferably, the text forwarding unit includes:

The encapsulating module is configured to: encapsulate the first packet to generate a second packet, where the source address of the text is directed to the MN, and the destination address is directed to the CN; The outer source address is the address information of the tMAG-MN, and the outer destination address is the address information of the sMAG-MN; when the sMAG-MN is used, the source address of the first packet points to the CN MAG (MAG-CN), the destination address is directed to the sMAG-MN; the outer source address of the second text is address information pointing to the sMAG-MN, and the outer destination address is an address pointing to the tMAG-MN Information

The sending module is configured to: when the second message is sent by using the forwarding tunnel, the second message is sent to the sMAG-MN as the tMAG-MN; and when the sMAG-MN is used, The tMAG-MN sends the second packet.

Preferably, the MAG further includes a forwarding tunnel release unit, configured to: when the tMAG-MN is used, after the tunnel between the tMAG-MN and the MAG-CN is established, releasing the tMAG-MN and the sMAG- Forwarding tunnel between MNs.

Preferably, the address information directed to the sMAG-MN or the tMAG-MN includes an address of the sMAG-MN or tMAG-MN, or a proxy care-of address (CoA) assigned by the sMAG-MN or tMAG-MN to the MN.

To solve the above technical problem, the present invention also provides a local mobility anchor (LMA), where the LMA includes:

Registration module, which is set to: Receive Proxy Binding Update (PBU) messages, including mobile nodes

(MN) A Proxy Binding Update (PBU) message sent by the target MAG (tMAG-MN) of the MN in the scenario of a mobile access gateway (MAG) handover, where the node information and the pointing location pointing to the MN are carried Address information of the tMAG-MN; a binding relationship maintenance module, configured to: save a binding relationship according to the received PBU message, including a binding relationship between the MN and the sMAG-MN;

An address information management module, configured to: after receiving the PBU message sent by the tMAG-MN, send a first message to the sMAG-MN or the tMAG-MN, where the first message sent to the sMAG-MN Carrying information about the node that points to the MN and address information that is directed to the tMAG-MN; the first message sent to the tMAG-MN carries node information that points to the MN and address information that points to the sMAG-MN .

Preferably, the registration module is further configured to: receive a DeRegister message, including a DeRegister message sent by the sMAG-MN; the binding relationship maintenance module is further configured to: delete the corresponding binding according to the received DeRegister message And determining a binding relationship between the MN and the sMAG-MN after the first message is sent, if the DeRegister message sent by the sMAG-MN is received before the first message is sent.

To solve the above technical problem, the present invention also provides a message forwarding processing system, the system comprising a mobile access gateway (MAG) and a local mobility anchor as described above.

The method, the network element, and the system provided by the embodiment of the present invention establish a forwarding tunnel between the tMAG-MN and the sMAG-MN in a scenario where the mobile node (MN) has a mobile access gateway (MAG) handover, thereby making the MAG During the handover, packets between the MN and the CN can be forwarded smoothly through the forwarding tunnel. BRIEF abstract

The accompanying drawings are intended to provide a In the drawing:

Figure 1 is a logical architecture diagram of an existing PMIP protocol;

2 is a schematic diagram of a process of transmitting and receiving IP packets between a MN and a CN according to the existing PMIP protocol; FIG. 3 is a schematic diagram of a transmission path waste problem existing according to the existing PMIP protocol; FIG. 4 is a logical architecture of the modified PMIP protocol. Figure

FIG. 5 is a process diagram of transmitting and receiving IP packets between a MN and a CN according to the modified PMIP protocol. Intention

6 is a schematic diagram of Embodiment 1 of a packet forwarding processing method according to the present invention;

7 is a schematic diagram of Embodiment 2 of a packet forwarding processing method according to the present invention;

8 is a schematic diagram of Embodiment 3 of a packet forwarding processing method according to the present invention;

9 is a schematic diagram of Embodiment 4 of a packet forwarding processing method according to the present invention;

FIG. 10 is a schematic diagram of a method for processing forwarding according to an embodiment of the present invention; FIG.

11 to 14 are schematic structural diagrams of modules of a MAG according to an embodiment of the present invention;

FIG. 15 is a schematic structural diagram of a module of a LAM according to an embodiment of the present invention.

Preferred embodiment of the invention

The present invention is directed to a method for packet forwarding processing based on the modified PMIP protocol. The method is to enable the MN to change the MAG after the terminal moves, and the IP data packet between the MN and the CN can pass the sMAG- The forwarding tunnel between the MN and the tMAG-MN avoids packet loss and meets the mobility requirements of the MN.

It should be noted that the node information pointed to the MN or CN in the present invention is information for indicating which mobile node or the opposite node is, and may be an identifier (ID) of the mobile node or the opposite node. The home address may also be a home network prefix, or a combination of two pieces of information or three pieces of information; the address information of the MAG referred to in the present invention is used to indicate which MAG is a mobile node or a peer node. The information of the attached or previously attached MAG may be the address of the MAG, or may be the proxy care-of address (CoA) assigned by the MAG to the mobile node (MN) and the correspondent node (CN), or may be the address of the MAG and the CoA. combination. The information of the node information directed to the MN or the CN is specifically represented by what information, and the information indicating the address information of the MAG is specifically determined by the specific application scenario or information that may be obtained by the corresponding network element, which is not the focus of the present invention. The invention is not limited by the description, and the detailed description is not intended to limit the invention.

It should be noted that the LMA allocates a home network prefix (HNP) for the MN or the CN. After receiving the router advertisement message (the message carries the HNP), the MN or the CN performs address configuration to obtain the home address HoA derived from the HNP. In PMIPv6, HNP and HoA are - corresponding, In other words, ΗΝΡ can represent HoA. The LMA/MAG may not know the HoA configured by the MN or the CN. In a specific network application, it is also possible for the LMA/MAG to obtain the HoA configured by the MN or CN. When the LMA/MAG does not know the HoA, the mapping relationship between the LMA and the MAG is the mapping between the HNP and the CoA or the MAG address. When the LMA/MAG knows the HoA, the mapping between the LMA and the MAG can be the HoA and CoA or MAG address. The mapping relationship can also be a mapping relationship between HNP and CoA or MAG addresses.

In order to more clearly describe the contents of the present invention, the following provisions are made in the present invention:

The sMAG-MN/MAG-MN refers to the MAG that the current MN accesses, and the proxy care-of address assigned by the MAG to the MN is CoAl.

The tMAG-MN refers to the MAG changed after the MN moves, that is, the MAG accessed by the MN after the handover, and the proxy care-of address assigned by the MAG to the MN is CoA2.

MAG-CN refers to the MAG currently accessed by the CN, and the proxy delivery address assigned by the MAG to the CN is CoA3.

The LMA-MN refers to the LMA that the MN accesses. The home network prefix assigned by the LMA to the MN is HNP1, and the home address obtained by the MN according to the HNP1 configuration is HoAl.

LMA-CN refers to the LMA that the CN accesses. The home network prefix assigned by the LMA to the CN is HNP3, and the home address obtained by CN according to HNP3 is HoA3.

In the present invention, the address of the MAG (including the MAG of the MN and the MAG of the CN) may be an interface address, or any other address that can represent the MAG.

In order to solve the problem of waste of transmission path existing in the existing PMIP mechanism, a series of adverse consequences are required, and the existing PMIP mechanism needs to be modified. Figure 4 shows the modified PMIP protocol architecture.

Compared with the logical architecture of the existing PMIP protocol (as shown in Figure 1), the modified PMIP protocol architecture also includes the mobile node MN, the communication peer CN, the mobile access gateway MAG, and the LMA. The CN can be a fixed node or a mobile node, that is, it has a corresponding MAG and LMA.

The MAG is the first hop router of the MN, and its main function is to allocate the care-of address CoA for the MN in the existing PMIP architecture, and perform PMIP between the MN and the anchor LMA of the MN instead of the MN. In addition to binding, you also need to have the following features:

Query the LMA to obtain the address of the MAG (MAG-CN) to which the communication peer CN is currently connected or the care-of address CoA of the CN.

A bidirectional tunnel is established between the MAG (MAG-MN) of the MN and the MAG of the CN, and the IP data between the MN and the CN is forwarded.

The LMA is no longer used as the anchor of the MN. The IP data packet between the MN and the CN is no longer required to pass through the LMA. The LMA needs to save the address of the current MAG-MN and/or the CoA of the MN for the communication peer of the MN. To query.

Figure 5 shows the process of sending and receiving IP packets between the MN and the CN when the modified PMIP architecture is applied. As shown in Figure 5, the IP data packet between the MN and the CN needs to pass through the tunnel between the MAG-MN and the MAG-CN.

When the MN sends an uplink IP packet to the CN, the MN needs to send the IP packet to the MAG-MN in accordance with the existing PMIP mechanism. Subsequent to the existing PMIP mechanism, in the present invention, the MAG-MN needs to query the address of the MAG-CN. After querying the address of the MAG-CN (such as the IP address of the MAG-CN), the MAG-MN uses the address of the MAG-CN as the destination to establish a tunnel from the MAG-MN to the MAG-CN (for example, an IP in IP tunnel). At the same time, the above IP packet is placed in the tunnel and sent directly to the MAG-CN. After receiving the IP packet from the tunnel, the MAG-CN sends the IP packet to the CN.

It should be noted that the MAG-MN can also query the CoA of the CN, and replace the address of the MAG-CN with the CoA address of the CN, and can achieve the same purpose. At this time, the MAG-MN uses the CoA as the end point and establishes the tunnel of the MAG-MN to the MAG-CN with the same effect. It is also worth noting that when the MAG-MN queries the address of the MAG-CN of the CN (or the CoA of the CN), it first queries the local cache, and if it does not query, it can query other network elements. For example, the CN LMA (LMA-CN) can be queried according to the HoA of CN. After querying the desired result, MAG-MN caches the query results locally. The advantage of caching the query results locally is that it can avoid frequent logins to other network elements.

By the same token, when the CN sends a downlink IP packet to the MN, the similar method is also used. The principle is the same and will not be described again. Using the method of the present invention, the way to send and receive IP messages between the MN and the CN The MAG<->CN of the MAG<->CN of the MN<->MN does not need to pass through the anchor LMA network element of the MN (or MN and CN), thereby avoiding a series of problems such as waste of the transmission path.

Applying the modified PMIP mechanism, after the terminal moves and changes the connected MAG, the existing

The sMAG-MN is not in the sMAG-MN, so the data packet is lost. The present invention provides a packet forwarding processing method, so that the MN changes the MAG and the IP data between the MN and the CN. The packet can pass the forwarding tunnel between the sMAG-MN and the tMAG-MN, thus avoiding packet loss.

As shown in FIG. 10, the method for processing the forwarding of the present invention includes:

Step 101: In a scenario where a mobile node (MN) has a mobile access gateway (MAG) handover, the target MAG (tMAG-MN) of the MN and the source MAG (sMAG-MN) of the MN acquire address information of the opposite party. And establishing a forwarding tunnel. Step 102: Before the handover is completed, the tMAG-MN or the sMAG-MN forwards the packet between the MN and the opposite node (CN) through the forwarding tunnel.

The technical solutions of the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments, so that those skilled in the art can It is to be understood that the examples are not intended to limit the invention.

Embodiment 1

FIG. 6 is a first embodiment of a packet forwarding processing method according to the present invention. As shown in Figure 6, the following steps are specifically included:

Step 601: After the MN accesses the PMIPv6 domain through the attach procedure, the MN sends a route request (RS, Router Solicitation) message to the sMAG-MN.

Step 602: The sMAG-MN sends a Proxy Binding Update (PBU) message to the LMN-MN, instead of registering with the LMN, the message carries the MN identity (MN ID) and the proxy broadcast address allocated by the sMAG-MN for the MN. CoAl. The address of the sMAG-MN is also sent to the LMA-MN in this message.

Step 603: The LMA-MN accepts the PBU message, and allocates a home network prefix (HNP1) to the MN. Create/update a Binding Cache Entry (BCE) and return a Proxy Binding Ack (PBA) message to the sMAG-MN.

Step 604: The LMA-MN caches the binding relationship between the MN and the sMAG-MN, and may be represented by a mapping relationship between the HNP1 and the CoAl, or a mapping relationship between the HNP1 and the sMAG-MN address.

Step 605: After receiving the PBA message, the sMAG-MN establishes a mapping relationship between the HNP-CoA of the MN, that is, a mapping relationship of the HNP1-CoAl.

Step 606: The sMAG-MN returns a RA (Router Advertisement) message to the MN. After receiving the router advertisement message, the MN performs address configuration to obtain the home address HoAl originating from the home network prefix HNP1.

Step 607, when the sMAG-MN receives the uplink IP data packet sent by the MN to the CN, it checks locally whether the mapping relationship between the CN and the MAG-CN is cached, that is, the node information pointing to the CN and the MAG-CN The mapping relationship between the address information, which may be specifically represented by the mapping relationship between HNP3 (CN's home network prefix)/HoA3 and the address of the MAG-CN, or the mapping relationship between the HNP3/HoA3 and the CN's CoA3. If not, query the LMA-MN/LMA-CN to obtain the above mapping relationship, and then sMAG-MN caches the query result locally; if so, directly uses the local cache mapping relationship. The sMAG-MN uses the address of the MAG-CN or the CoA3 of the CN as the destination, establishes a tunnel from the sMAG-MN to the MAG-CN (for example, an IP in IP tunnel), and puts the above IP data packet in the tunnel and directly sends it to the tunnel. MAG-CN. On the other hand, when the CN sends an IP data packet to the MN, the MAG-CN also needs to perform the above operation to directly send the IP data packet to the sMAG-MN through the tunnel from the sMAG-MN to the MAG-CN.

Step 608: After receiving the IP data packet between the first MN and the CN, the sMAG-MN needs to locally establish a mapping relationship between the HoA3/HNP3 of the CN and the CoA3 or the HoA3/HNP3 of the CN and the address of the MAG-CN.

Step 609: The MN moves and replaces the sMAG-MN. After the MN accesses the PMIPv6 domain through the attach procedure, it sends an RS message to the associated tMAG-MN.

After the sMAG-MN detects the MN handover/movement, optionally, the sMAG-MNLMA-MN initiates a DeRegister procedure. The sMAG-MN initiates a DeRegister process to the LMA-MN. If the LMA-MN receives the sMAG-MN before returning the PBA message The DeRegister message, the LMA still needs to maintain the mapping relationship between HoAl/HNP1 and CoAl, or the mapping relationship between HoAl/HNP1 and sMAG-MN addresses.

Step 610: The tMAG-MN sends a PBU message to the LMN-MN, instead of the MN registering with the LMN, the message carries the MN identity (MN ID), the tMAG-MN is the newly assigned proxy broadcast address CoA2 of the MN, and the home network prefix HNP1 of the MN. The address of the tMAG-MN is also sent to the LMA-MN in this message.

Step 611: The LMA-MN accepts the PBU message, updates the binding cache list BCE of the MN, and returns a PBA message to the tMAG-MN. The message carries the address of the CoAl assigned by the sMAG-MN to the MN, and/or the sMAG-MN.

Step 612, the tMAG-MN returns an RA message to the MN.

Step 613: After receiving the PBA message, the tMAG-MN establishes a mapping relationship between the HNP-CoA of the MN, that is, the mapping relationship of the HNP1-CoA2.

Step 614: The tMAG-MN sends a handover indication message to the sMAG-MN, where the message carries the address of the CoA2, and/or tMAG-CN allocated by the MN to the MN. In this message, the MN identity or HNP1 is also required to identify/distinguish the user.

The source address and the destination address of the handover indication message may be CoA2 of the MN and CoAl of the MN, respectively, or may be an address of the tMAG-MN and an address of the sMAG-MN, that is, address information and a pointer to the tMAG-MN, respectively. Address information of sMAG-MN.

The purpose of the handover indication message is to send the address of the tMAG-MN or CoA2 to the sMAG-MN to establish a forwarding tunnel between the sMAG-MN and the tMAG-MN. The name of the message can be other names as long as the message carries the address of the tMAG-MN or CoA2.

Step 615, this step is optional. The sMAG-MN sends a handover confirmation message to the tMAG-MN. After the steps 614 and 615 are performed, the forwarding tunnel between the sMAG-MN and the tMAG-MN is established, and the IP data packets between the MN and the CN need to be sent through the forwarding tunnel.

Step 616: When the sMAG-MN receives the downlink IP data sent by the CN to the MN, the source address of the downlink IP data source points to the MAG-CN, the destination address points to the sMAG-MN, and the sMAG-MN needs to firstly MAG -CN is added to the encapsulation of the data packet header, and then a layer of encapsulation is added to the header of the data packet, and the address of the sMAG-MN or the CoAl of the MN is used as the source address. The IP data file is directly sent to the tMAG-MN by using the address of the tMAG-MN or the CoA2 of the MN as the destination address, and then the packet is deleted/detached by the tMAG-CN, and the IP data packet is directly sent to the MN. Alternatively, after receiving the data packet, the sMAG-CN directly encapsulates the MAG-CN, adds a layer of encapsulation, uses the address of the sMAG-MN or the CoAl of the MN as the source address, and uses the address of the tMAG-MN or the MN. As the destination address, CoA2 sends the IP data packet directly to the tMAG-MN. At this time, the data packet received by the tMAG-MN has two layers of encapsulation. After the tMAG-MN needs to delete/peel the two layers of encapsulation, the IP address is the same. The data message is sent directly to the MN.

Step 617a: When the tMAG-MN receives the uplink IP data packet sent by the MN to the CN, the source address of the uplink IP data packet points to the MN, the destination address points to the CN, and the tMAG-MN is in the data packet. Add a layer of encapsulation, use the address of the tMAG-MN or the CoA2 of the MN as the source address, and use the address of the sMAG-MN or the CoAl of the MN as the destination address to send the IP data packet directly to the sMAG-MN, and then by the sMAG. - CN deletes/peeles the encapsulation, and then sends the IP data packet directly to the MAG-CN as described in step 607. Or,

Step 617b: When receiving the uplink IP data packet sent by the MN to the CN, the tMAG-MN adds a layer encapsulation to the data packet header, and uses the address of the tMAG-MN or the CoA2 of the MN as the source address, and uses the MAG-CN. The IP address of the IP address of the CN or the CoAs of the CN is directly sent to the MAG-CN, and then the MAG-CN deletes/discards the encapsulation and sends the IP data packet directly to the CN.

In this step, the MAG-CN can learn the address of the tMAG-MN and/or the CoA2 that the tMAG-MN allocates for the MN through the data packet, and the IP data of the subsequent CN to the MN can be directly sent as described in step 607. Give tMAG-MN. After the tunnel between the tMAG-MN and the MAG-CN is established, the tMAG-MN releases the forwarding tunnel between the tMAG-MN and the sMAG-MN.

Embodiment 2

FIG. 7 is a second embodiment of a packet forwarding processing method according to the present invention. As shown in FIG. 7, the following steps are included: Steps 701-710, and steps 601-610.

Step 711: The LMA-MN accepts the PBU message, updates the binding cache list BCE of the MN, and returns a PBA message to the tMAG-MN.

Steps 712, 713 are the same as steps 612 and 613. Step 714: The LMA-MN sends a handover indication message to the sMAG-MN, where the message carries the address of the CoA2, and/or the tMAG-CN allocated by the tMAG-MN for the MN. The MN identity or HNP1 needs to be carried in the message to identify/distinguish the user.

The purpose of the handover indication message is to send the address of the tMAG-MN or CoA2 to the sMAG-MN. The name of the message may be other names as long as the message carries the address of the tMAG-MN or CoA2.

This step can be performed in parallel with step 711 or at any time thereafter.

Step 715: After receiving the handover indication message, the sMAG-MN establishes a request message to the tMAG-MN tunnel, where the message carries the address of the CoAl, and/or sMAG-CN allocated by the sMAG-MN for the MN. In this message, it is also necessary to carry the MN identity or HNP1 to identify/distinguish the user.

The source address and the destination address of the tunnel establishment request message may be CoAl of the MN and CoA2 of the MN, or may be an address of the sMAG-MN and an address of the tMAG-MN.

The purpose of the tunnel establishment request message is to send the address of the sMAG-MN or CoAl to the tMAG-MN to establish a forwarding tunnel between the sMAG-MN and the tMAG-MN. The name of the message can be other names as long as the message carries the address of sMAG-MN or CoAl.

In step 716, this step is optional. The tMAG-MN sends a tunnel setup response message to the sMAG-MN. Step 717, this step is optional. The sMAG-MN sends a handover confirmation message to the LMA-MN. Steps 718, 717a, 719b, the same steps 616, 617a, 617b.

Embodiment 3

FIG. 8 is a third embodiment of a packet forwarding processing method according to the present invention. As shown in FIG. 8, the following steps are included: Steps 801-806, the same steps as 701-706.

Step 807, the sMAG-MN sets a timer 1 after receiving the PBA message, and the purpose of the timer is to determine when the MN leaves the sMAG-MN.

When the timer exceeds 1, and there is no uplink and downlink data of the MN, the sMAG-MN considers that the MN has left the sMAG-MN.

Or, when the timer 1 expires and there is no uplink and downlink data of the MN, the sMAG-MN sets the timer 2, and monitors whether the MN has uplink and downlink data in the time range of the timer 2, if not, It is considered that the MN has left the sMAG-MN, and if so, the MN is still attached to the sMAG-MN, and the timer 1 is reset.

When the timer expires and there is MN uplink and downlink data, the MN still attaches to the sMAG-MN and resets the timer 1.

When the sMAG-MN detects the MN handover/movement, the timer 1 has not expired, and it is considered that the MN has left the sMAG-MN. At this time, according to the timer 1 timeout processing, the step 816 is started.

Step 808 - Step 813, the same steps as 707-712.

In step 814, the timer 1 set in step 807 times out. As described in step 807, the sMAG-MN determines whether the MN has left the sMAG-MN, and if not, performs the subsequent steps. If not, the method is reset according to step 807. Timer 1.

Step 815: The sMAG-MN sends a handover query request to the LMA-MN, where the message carries the MN identifier or HoAl.

Step 816: The LMA-MN returns a handover inquiry response message to the sMAG-MN, where the message carries the address of the CoA2, and/or tMAG-CN allocated by the tMAG-MN to the MN. In this message, it is also necessary to carry the MN identity or HoAl to identify/distinguish the user.

The purpose of switching the query request message and the switch query response message is to query the address of the tMAG-MN or CoA2 from the LMA-MN. The name of the message may be other names as long as the message completes the above query function.

Steps 817-819, 820a, 820b, and steps 716-718, 719a, 719b.

The above embodiments of the present invention describe the establishment of a forwarding tunnel between the tMAG-MN and the sMAG-MN by taking the PMIP process as an example. This embodiment is also applicable to Fast Handovers for Proxy Mobile (FPMIP).

Embodiment 4

FIG. 9 is a fourth embodiment of a message forwarding processing method according to the present invention. The embodiment is applicable to FPMIP. As shown in Figure 9, the following steps are specifically included:

Steps 901-908, the same steps 601-608.

Step 909, when the MN is ready to switch, the sMAG-MN receives an indication of the lower layer link, The MN is about to switch. The implementation of the indication may have different implementations in different application scenarios, and is not specifically described herein.

Step 910: The sMAG-MN sends a handover indication (Handover Indication) to the tMAG-MN.

HI) message, the message carries the MN identity.

Step 911, the tMAG-MN sends a PBU message to the LMN-MN, instead of the MN registering with the LMN, the message carries the MN identity (MN ID), the tMAG-MN is the newly assigned proxy broadcast address CoA2 of the MN, and the home network prefix HNP1 of the MN. The address of the tMAG-MN is also sent to the LMA-MN in this message.

Step 912: The LMA-MN accepts the PBU message, updates the binding cache list BCE of the MN, and returns a PBA message to the tMAG-MN. The message carries the address of the CoAl assigned by the sMAG-MN to the MN, and/or the sMAG-MN.

Step 913: After receiving the PBA message, the tMAG-MN establishes a mapping relationship between the HNP-CoA of the MN, that is, the mapping relationship of the HNP1-CoA2.

Step 914, the tMAG-MN returns a Handover Acknowledge ( Hack) message to the sMAG-MN. The message carries the address of CoA2, and / or tMAG-CN assigned by the tMAG-MN to the MN. In this message, the MN identity or HNP1 needs to be carried in it to identify another user.

The source address and the destination address of the handover confirmation message may be CoA2 of the MN and CoAl of the MN, respectively, or may be an address of the tMAG-MN and an address of the sMAG-MN, that is, address information and a pointer to the tMAG-MN, respectively. Address information of sMAG-MN.

Step 915: The sMAG-MN sends a handover command message to the lower layer link, and the message is forwarded to the 匪.

Step 916, this step is optional. After the sMAG-MN receives the Hack message, it sends a handover confirmation message to tMAG-MN.

In step 917, the MN switches to tMAG-MN. After the MN accesses the PMIPv6 domain through the attach procedure, it sends an RS message to the associated tMAG-MN.

Step 918, the tMAG-CN returns an RA message to the MN.

Steps 919, 920a, 920b are the same as steps 616, 617a, 617b. Corresponding to the above method, the present invention further provides a mobile access gateway (MAG), as shown in FIGS. 11 to 14, the MAG includes:

a forwarding tunnel establishing unit, configured to acquire address information directed to the sMAG-MN when the mobile node (MN) is in a mobile access gateway (MAG) handover scenario, as the target MAG (tMAG-MN) of the MN, Establishing a forwarding tunnel; when the source MAG (sMAG-MN) of the MN is used, acquiring address information that points to the tMAG-MN, and establishing a forwarding tunnel;

And a packet forwarding unit, configured to forward, by using the forwarding tunnel, a packet between the MN and the correspondent node (CN).

Further, as shown in FIG. 11, the forwarding tunnel establishing unit includes:

a message receiving module, configured, as the tMAG-MN, to receive a first message sent by the local mobility anchor (LMA-MN) of the MN, where the address information that is directed to the sMAG-MN is carried; Receiving, by the sMAG-MN, the second message sent by the tMAG-MN; and the message sending module, when the tMAG-MN is used, according to the address information of the first message that points to the sMAG-MN The sMAG-MN sends a second message, where the node information that points to the MN and the address information that points to the tMAG-MN are carried.

Further, as shown in FIG. 11, the forwarding tunnel establishing unit includes:

a message receiving module, when the sMAG-MN is used, to receive a first message sent by the local mobility anchor (LMA-MN) of the MN, where the node information that points to the MN is carried and the tMAG- The address information of the MN; and, when the tMAG-MN is used, receiving the second message sent by the sMAG-MN;

a message sending module, configured to send, by the sMAG-MN, a second message to the tMAG-MN according to the address information that is directed to the tMAG-MN in the first message, where the node information that points to the MN is carried And address information pointing to the sMAG-MN.

Further, as shown in FIG. 12, the forwarding tunnel establishing unit includes:

The querying module, as the sMAG-MN, and determining that the MN is leaving, is configured to send a first message to the LMA-MN, where the information about the address of the tMAG-MN is queried, where the first message carries a pointing address Describe the node information of the MN;

a message receiving module, when used as an sMAG-MN, for receiving the first transmission by the LMA-MN And a second message, where the information about the node that is directed to the MN and the address information that is directed to the tMAG-MN is carried; and when the tMAG-MN is used, the third message that is sent by the sMAG-MN is received;

The message sending module, when the sMAG-MN is used, is configured to send a third message to the tMAG-MN, where the node information that points to the MN and the address information that points to the sMAG-MN are carried.

Further, determining that the MN is away includes not receiving the preset timer time

The uplink and downlink data of the MN, or detecting that the MN switches or moves away.

Further, as shown in FIG. 13, the text forwarding unit includes:

An encapsulating module, configured to encapsulate a first packet to generate a second packet, where the source address of the text is directed to the MN, and the destination address is directed to the CN; the second "^" The outer source address is the address information of the tMAG-MN, and the outer destination address is the address information of the sMAG-MN; when the sMAG-MN is used, the source address of the first packet points to the CN MAG (MAG-CN), the destination address is directed to the sMAG-MN; the outer source address of the second packet is address information directed to the sMAG-MN, and the outer destination address is directed to the tMAG-MN Address information;

a sending module, configured to send the second packet to the tMAG-MN, when the second packet is sent to the sMAG-MN as the sMAG-MN, to the tMAG - The MN sends the second message.

Further, as shown in FIG. 14, the MAG further includes a forwarding tunnel release unit, where the tMAG-MN is used to release the tMAG after the tunnel between the tMAG-MN and the MAG-CN is established. - Forwarding tunnel between MN and sMAG-MN.

As described above, the node information that points to the MN includes an identifier (ID) of the MN, a home address, or a home network prefix, and the address information that points to the sMAG-MN or the tMAG-MN includes the sMAG-MN or tMAG. - The address of the MN, or the proxy care-of address (CoA) assigned by the sMAG-MN or tMAG-MN to the MN.

In addition, the present invention also provides a Local Mobility Anchor (LMA). As shown in FIG. 15, the LMA includes:

a registration module, configured to receive a proxy binding update (PBU) message, including a target MAG (tMAG-MN) of the MN in a scenario where a mobile node (MN) has a mobile access gateway (MAG) handover a sent proxy binding update (PBU) message, which carries node information directed to the MN and address information directed to the tMAG-MN;

a binding relationship maintenance module, configured to save a binding relationship according to the received PBU message, including a binding relationship between the MN and the sMAG-MN;

An address information management module, configured to send a first message to the sMAG-MN or the tMAG-MN after receiving the PBU message sent by the tMAG-MN, where the first message sent to the sMAG-MN is carried in the first message Node information directed to the MN and address information directed to the tMAG-MN; the first message sent to the tMAG-MN carries node information directed to the MN and address information directed to the sMAG-MN.

Further, the registration module is further configured to receive a DeRegister message, including a DeRegister message sent by the sMAG-MN, and the binding relationship maintenance module is further configured to delete the corresponding binding according to the received DeRegister message. And determining a binding relationship between the MN and the sMAG-MN after the first message is sent, if the DeRegister message sent by the sMAG-MN is received before the first message is sent.

Additionally, the present invention also provides a message forwarding processing system, the system comprising a Mobile Access Gateway (MAG) as described above and a local mobility anchor as described above.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention. Industrial applicability

The method, the network element, and the system provided by the embodiment of the present invention establish a forwarding tunnel between the tMAG-MN and the sMAG-MN in a scenario where the mobile node (MN) has a mobile access gateway (MAG) handover, thereby making the MAG During the handover, packets between the MN and the CN can be forwarded smoothly through the forwarding tunnel.

Claims

Claim

1. A text forwarding processing method, the method comprising:

2. The method according to claim 1, wherein the step of acquiring the address information of the tMAG-MN and the sMAG-MN to the other party comprises:

The local mobility anchor (LMA-MN) of the MN sends a first message to the tMAG-MN, carrying address information directed to the sMAG-MN;

Receiving, by the tMAG-MN, the first message, sending a second message to the sMAG-MN according to address information that is directed to the sMAG-MN, carrying node information that points to the MN, and an address that points to the tMAG-MN Information

The sMAG-MN receives the second message.

3. The method according to claim 1, wherein the step of acquiring the address information of the other party of the tMAG-MN and the sMAG-MN comprises: the local mobility anchor (LMA-MN) of the MN to the sMAG - the MN sends a first message carrying node information directed to the MN and address information directed to the tMAG-MN; the sMAG-MN receiving the first message, according to the address information of the tMAG-MN The tMAG-MN sends a second message, carrying node information directed to the MN and address information directed to the sMAG-MN;

The tMAG-MN receives the second message.

The method according to claim 2 or 3, wherein the LMA-MN sends a first message, carrying node information directed to the MN and address information pointing to the tMAG-MN, The LMA-MN sends the first message according to the PUB message and the saved binding relationship between the MN and the sMAG-MN.

The method according to claim 2 or 3, wherein, before the first message is sent by the LMA-MN, if the DeRegister message sent by the sMAG-MN is received, the MN is still retained. The binding relationship with the sMAG-MN is deleted after the first message is sent.

The method of claim 1, wherein the step of acquiring the address information of the other party by the tMAG-MN and the sMAG-MN comprises: when the sMAG-MN determines that the MN is away, to the LMA-MN Sending a first message, configured to query address information that is directed to the tMAG-MN, where the first message carries node information that points to the MN;

The LMA-MN sends a second message to the sMAG-MN, carrying node information directed to the MN and address information directed to the tMAG-MN;

The sMAG-MN sends a third message to the tMAG-MN, carrying node information directed to the MN and address information directed to the sMAG-MN;

The tMAG-MN receives the third message.

The method of claim 6, wherein the sMAG-MN determines that the MN is away from the uplink or downlink data of the MN, or detects the MN handover. Or move away.

The method of claim 1, wherein the step of the tMAG-MN forwarding the message between the MN and the correspondent node (CN) through the forwarding tunnel comprises:

9. The method of claim 1, wherein the sMAG-MN passes the forwarding tunnel The step of forwarding the message between the MN and the correspondent node (CN) includes:

The method of claim 1, wherein, after the forwarding tunnel is established, the method further includes: the tMAG-MN releasing the forwarding tunnel, and the triggering condition for releasing the forwarding tunnel is the tMAG-MN Tunnel establishment with MAG-CN.

The method according to claim 2 or 3, wherein the node information directed to the MN includes an identifier (ID) of the MN, a home address or a home network prefix, and the pointing to the sMAG-MN or tMAG- The address information of the MN includes the address of the sMAG-MN or tMAG-MN, or

12. A mobile access gateway (MAG), the MAG comprising:

a message forwarding unit, configured to: forward the MN and the peer node by using the forwarding tunnel

Message between (CN).

The MAG of claim 12, wherein the forwarding tunnel establishing unit comprises: a message receiving module, configured to: receive, as the tMAG-MN, a local mobility anchor (LMA-MN) of the MN a first message sent, carrying address information directed to the sMAG-MN; and, when the sMAG-MN is received, receiving a second message sent by the tMAG-MN; a message sending module, configured to: The tMAG-MN sends a second message to the sMAG-MN according to the address information in the first message that is directed to the sMAG-MN, Node information of the MN and address information pointing to the tMAG-MN.

The MAG of claim 12, wherein the forwarding tunnel establishing unit comprises: a message receiving module, configured to: receive, as the sMAG-MN, a local mobility anchor (LMA-MN) of the MN a first message sent, carrying node information directed to the MN and address information directed to the tMAG-MN; and, when the tMAG-MN is received, receiving a second message sent by the sMAG-MN;

The MAG of claim 12, wherein the forwarding tunnel establishing unit comprises: a querying module, configured to: when the sMAG-MN is determined and the MN leaves, send a first message to the LMA-MN; Querying address information of the tMAG-MN, where the first message carries node information that points to the MN;

a message receiving module, configured to: when the sMAG-MN is used, receive a second message sent by the LMA-MN, and carry node information that points to the MN and address information that points to the tMAG-MN; Receiving a third message sent by the sMAG-MN;

The MAG according to claim 15, wherein the determining that the MN is away includes not receiving uplink and downlink data of the MN within a preset timer time, or detecting that the MN switches or moves away. .

The MAG of claim 12, wherein the packet forwarding unit comprises: an encapsulating module, configured to: encapsulate the first packet to generate a second packet, and when the tMAG-MN is used, the text The source address is directed to the MN, and the destination address is directed to the CN; the outer source address of the second text is address information directed to the tMAG-MN, and the outer destination address is address information directed to the sMAG-MN As the sMAG-MN, the source address of the first packet points to the MAG (MAG-CN) of the CN, and the destination address points to the sMAG-MN; The outer source address of the text is the address information of the sMAG-MN, and the outer destination address is the address information of the tMAG-MN;

The MAG of claim 12, wherein the MAG further includes a forwarding tunnel release unit, configured to: when the tMAG-MN is used, after the tunnel between the tMAG-MN and the MAG-CN is established And releasing a forwarding tunnel between the tMAG-MN and the sMAG-MN.

The MAG according to claim 12, wherein the address information directed to the sMAG-MN or the tMAG-MN includes an address of the sMAG-MN or tMAG-MN, or

20. A Local Mobility Anchor (LMA), the LMA comprising:

a registration module, configured to: receive a proxy binding update (PBU) message, including a proxy sent by the target MAG (tMAG-MN) of the MN in a scenario where a mobile node (MN) has a mobile access gateway (MAG) handover a Binding Update (PBU) message carrying node information directed to the MN and address information directed to the tMAG-MN;

a binding relationship maintenance module, configured to: save a binding relationship according to the received PBU message, and include a binding relationship between the MN and the sMAG-MN;

An address information management module, configured to: after receiving the PBU message sent by the tMAG-MN, send a first message to the sMAG-MN or the tMAG-MN, where the first message is sent to the sMAG-MN The message carries the node information of the MN and the address information of the tMAG-MN; the first message sent to the tMAG-MN carries the node information directed to the MN and points to the sMAG-MN Address information.

21. The LMA of claim 20, wherein

The registration module is further configured to: receive a DeRegister message, including a DeRegister message sent by the sMAG-MN; the binding relationship maintenance module is further configured to: delete a corresponding binding relationship according to the received DeRegister message, Receiving before sending the first message After the first message is sent to the DeRegister message sent by the sMAG-MN, the binding relationship between the MN and the sMAG-MN is deleted.

A message forwarding processing system, the system comprising the mobile access gateway (MAG) according to any one of claims 12 to 19 and the local mobility anchor according to claim 20 or 21.