WO2010072135A1 - 一种网络切换方法、装置及系统 - Google Patents

一种网络切换方法、装置及系统 Download PDF

Info

Publication number
WO2010072135A1
WO2010072135A1 PCT/CN2009/075776 CN2009075776W WO2010072135A1 WO 2010072135 A1 WO2010072135 A1 WO 2010072135A1 CN 2009075776 W CN2009075776 W CN 2009075776W WO 2010072135 A1 WO2010072135 A1 WO 2010072135A1
Authority
WO
WIPO (PCT)
Prior art keywords
tunnel
mobile
information
mobility anchor
network
Prior art date
Application number
PCT/CN2009/075776
Other languages
English (en)
French (fr)
Inventor
王云贵
吴钦
夏晋伟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010072135A1 publication Critical patent/WO2010072135A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface

Definitions

  • Node, mobile node advertises HNP (Home Network Prefix), so that Li thinks that he is always on his home link;
  • MAG sends a registration message to LMA (Local Mobility Anchor).
  • LMA Local Mobility Anchor
  • a binding cache entry for the home network address prefix information and Proxy-CoA (Proxy Care-of Address) is established on the LMA, and a bidirectional tunnel is established between the MAG and the LMA for transmitting the MN packet.
  • Proxy-CoA Proxy Care-of Address
  • the peer node sends a packet to the home address of the mobile node, and the packet is intercepted by the LMA. Then, the LMA queries the binding list according to the home prefix, and then sends the packet to the MAG through the tunnel between the LMA and the MAG. After the encapsulation, the packet is sent to the MN according to the destination address of the packet.
  • the MAG When the mobile node sends a packet to the peer node, the MAG receives the packet for encapsulation, adds the outer IP packet header (source address), and then sends the packet to the LMA through the tunnel between the MAG and the LMA. Strip the outer IP packet header and forward the inner packet to the peer node.
  • proxy mobile IPv6 When proxy mobile IPv6 is used as an interconnection protocol for heterogeneous networks (such as WiMAX and 3GPP), MN (Mobile Node), for example, when a mobile terminal moves in a heterogeneous network, during a network handover process based on proxy mobile IPv6, pMAG (Previous Mobile Access Gateway, the original mobile access gateway) is located in an access technology network, and the nMAG (new mobile access gateway) is located in another access technology network. In an internetwork system, pMAG and nMAG are connected to the same LMA Local Mobility Anchor, local mobility anchor).
  • MN Mobile Node
  • the new mobile access gateway simultaneously establishes a two-way tunnel during the registration process to the local mobility anchor. Local shift at this time
  • the dynamic anchor point transfers the data service transmission of the mobile terminal from the tunnel corresponding to the original mobile access gateway connected to the IF1 to the new mobile access gateway connected to the IF2. Because the binding cache entry saved on the local mobility anchor corresponds to the address of the new mobile access gateway, the uplink data service sent by the mobile terminal (IF1) through the original mobile access gateway will be lost by the local mobility anchor; Since the IP address configuration and/or the radio link configuration of the mobile terminal IF2 attached to the new mobile access gateway has not been completed, the downlink data service sent by the local mobility anchor to the mobile terminal (IF2) will be used by the new mobile access gateway. Lost.
  • the present invention provides a network handover method, device and system, and a tunnel establishment method in a proxy mobile IP system.
  • a network handover method When performing network handover, data services on the local mobility anchor point and the new mobile access gateway are not lost.
  • the embodiment of the invention provides a network switching method, including:
  • the tunneling request carries the tunnel information exchanged with the local mobility anchor, where the tunnel information includes tunnel address information and tunnel type information.
  • Data is forwarded to the mobile node through a tunnel established with the local mobility anchor.
  • the embodiment of the present invention further provides a method for establishing a tunnel, which is applied to a proxy mobile IP system, including: the first network node sends a tunnel establishment request to the second network node, where the tunnel request is carried in the The tunnel information exchanged by the network node, where the tunnel information includes tunnel address information and tunnel type information; and the second network node establishes with the first network node according to the tunnel information carried in the tunnel establishment request. tunnel.
  • an embodiment of the present invention further provides a mobile access gateway, including:
  • a network address obtaining module when the mobile node moves from the first mobile network to the second mobile network, obtains the home network address prefix information of the mobile node from the local mobile anchor point;
  • the tunnel information requesting module after completing the access layer configuration with the mobile node according to the home network address prefix information, sending a tunnel establishment request to the local mobility anchor to establish a relationship with the local mobility anchor point of The tunneling request carries the tunnel information exchanged with the local mobility anchor, where the tunnel information includes tunnel address information and tunnel type information.
  • a data forwarding module configured to forward data to the mobile node by using a tunnel established between the local mobility anchor point.
  • an embodiment of the present invention further provides a local mobility anchor point, including:
  • a network address sending module when the mobile node moves from the first mobile network to the second mobile network, returning the home network address prefix information of the mobile node to the mobile access gateway in the second mobile network;
  • Establishing a tunneling module configured to establish a tunnel with the mobile access gateway after receiving the tunneling request of the mobile access gateway; and the establishing a tunnel request carries an exchange with the local mobility anchor Tunnel information, the tunnel information includes tunnel address information and tunnel type information.
  • an embodiment of the present invention further provides a network switching system, including: a mobile access gateway and a local mobile anchor point;
  • the mobile access gateway is configured to acquire, when the mobile node moves from the first mobile network to the second mobile network, the home network address prefix information of the mobile node from the local mobility anchor point; and according to the home network address prefix Transmitting, after completing the access layer configuration with the mobile node, sending a tunnel establishment request to the local mobility anchor; forwarding data to the mobile node by using a tunnel established between the local mobility anchor;
  • the tunneling request carries the tunnel information exchanged with the local mobility anchor, where the tunnel information includes tunnel address information and tunnel type information.
  • the local mobility anchor point is used to return the home network address prefix information of the mobile node to the mobile access gateway in the second mobile network; after receiving the tunnel establishment request of the mobile access gateway, establishing A tunnel with the mobile access gateway.
  • the embodiment of the present invention provides a method for establishing a tunnel, which is applied to a proxy mobile IP system, and carries tunnel information including tunnel address information and tunnel type information in establishing a tunnel request, so that the tunnel negotiation process is completely independent of the proxy. Bind the update registration process.
  • the network switching method, device and system provided by the embodiment of the present invention when the mobile node moves from the first mobile network to the second mobile network, first obtains the home network address used by the mobile node in the second mobile network from the local mobility anchor point. Prefix information; after the mobile node completes the configuration of the access layer, the tunnel between the local mobility anchor is established, such that the address of the mobile access gateway in the first mobile network saved on the local mobility anchor Will not be replaced by the address of the mobile access gateway in the second mobile network, the mobile node moves through the first mobile network
  • the uplink data service sent by the access gateway is not lost by the local mobility anchor; and the downlink data service sent by the local mobility anchor to the mobile node is not lost by the mobile access gateway in the second mobile network.
  • FIG. 1 is a flowchart of a method for establishing a tunnel in a proxy mobile IP system according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a mobile option according to an embodiment of the present invention.
  • FIG. 3 is a flow chart of a specific implementation method for establishing a tunnel in a proxy mobile IP system according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of another mobile option according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a specific implementation method for establishing a tunnel in a proxy mobile IP system according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for network switching according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of another network switching method according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a network switching system according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a proxy mobile IP system architecture based on separation of a control plane and a data plane according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a mobile access gateway according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another mobile access gateway according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a local mobility anchor point according to an embodiment of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION The present invention provides a network handover method, apparatus, and system, and a tunnel establishment method in a proxy mobile IP system, so that when a mobile node performs network handover, data services on the local mobility anchor point and the new mobile access gateway are both Will not be lost.
  • FIG. 1 is a flowchart of a method for establishing a tunnel in a proxy mobile IP system according to an embodiment of the present invention.
  • Step 100 The first network node sends a tunnel establishment request to the second network node, where the tunneling request carries the tunnel information exchanged with the second network node, where the tunnel information includes tunnel address information and tunnel type information.
  • the second network node when the first network node is a mobile access gateway, the second network node is a local mobility anchor point; or, when the first network node is a local mobility anchor point, the second network node For mobile access gateways.
  • Step 101 The second network node establishes a tunnel with the first network node according to the tunnel information carried in the tunnel message.
  • the tunnel address in the tunnel information, the tunnel type may be carried by a mobility option or two different mobility options.
  • the second network node determines to establish a tunnel with the first network node according to the configured policy.
  • the method for establishing a tunnel in the proxy mobile IP system is implemented, and the tunnel information including the tunnel address and the tunnel type is carried in the tunnel request, and the mobile node can be moved through the proxy after the tunnel node (such as the local mobility anchor and the mobile access gateway) is started.
  • a Heartbeat message or a Notification message or a proxy binding update message in the system is carried, so that the process of tunnel negotiation is independent of the registration process of the agent binding update.
  • the method for establishing a tunnel in the proxy mobile IP system includes the tunnel encapsulation mode negotiation and the tunnel identity exchange process, in addition to the tunnel address exchange process.
  • the tunnel negotiation process will be described in detail below.
  • a new mobility option that is, a data plane tunnel address option, may be added to the proxy binding update message.
  • the mobile option is a data plane address option, where:
  • Type Indicates the type identifier of the move option. This indicates that the option is a tunnel address.
  • Length indicates the length of the move option, here is the length of the tunnel address, 16 bytes.
  • Tunnel address This is the data plane tunnel address of the MAG or LMA.
  • the tunnel address option may be omitted.
  • the tunnel needs to be included in the PBU/PBA (Proxy Binding Update, Proxy Binding Acknowledge) message (or other PMIPv6 (Proxy Mobile IPv6) related messages) Address options.
  • Step 200 When the MN moves to the new network and attaches to the nMAG through the interface (IF2), the nMAG replaces the behavior of the mobile IP, and the registration request for the proxy binding update to the LMA is not included in the registration request.
  • Tunnel negotiation information When the MN moves to the new network and attaches to the nMAG through the interface (IF2), the nMAG replaces the behavior of the mobile IP, and the registration request for the proxy binding update to the LMA is not included in the registration request.
  • Step 201 The LMA accepts the registration request of the nMAG, and responds to the proxy binding determination, and assigns a HNP (Home Network Prefix) to it;
  • HNP Home Network Prefix
  • Step 202 After the MN completes the address configuration according to the HNP, the nMAG initiates a tunneling update request establishing a tunnel request to the LMA, and has the foregoing mobility option to indicate to the LMA that the data plane address carried in the mobile option is received. Downstream business.
  • Step 203 After receiving the tunnel establishment request of the nMAG, the LMA allocates a data plane tunnel address of the uplink service, and sends the data to the nMAG through the mobility option in the tunnel negotiation confirmation.
  • Step 204 The LMA and the nMAG establish a new tunnel according to the data plane address exchanged by the LMA and the nMAG, and forward the data service of the IF2 through the new tunnel.
  • the above mobile option can be regarded as an extension of the Alternate CoA option.
  • the above move option is a new move option.
  • the tunnel mode is used for transmission.
  • the proxy mobile IP protocol may be extended, and a new mobility option is added to carry the tunnel type and the tunnel identifier related information. .
  • FIG. 4 it is a schematic structural diagram of another mobile option according to an embodiment of the present invention, where:
  • Type type, which is represented as a tunnel identification option
  • Length Length, which indicates the length of the tunnel identification option.
  • Tunnel type Indicates which tunnel type to use, such as 0 for IPinIP tunnel, 1 for GRE, 2 for MPLS, and so on.
  • M Mode, which indicates negotiation of tunnel encapsulation mode; 0 indicates dynamic tunnel encapsulation. You must have a tunnel ID field at this time. 1 indicates a static pre-configured tunnel. You can have a pre-configured tunnel ID with or without this.
  • the tunnel identifier is used to determine the corresponding mobile terminal when transmitting and receiving data.
  • the message carried in the mobile access gateway is called a downlink tunnel identifier
  • the message carried in the local mobility anchor is called an uplink tunnel identifier. .
  • the GRE (Generic Routing Encapsulation) tunnel is used to describe the tunnel mode negotiation and tunnel identity exchange process.
  • the tunnel mode negotiation process is as follows:
  • GRE tunnel encapsulation mode including GRE encapsulation, static GRE encapsulation, and dynamic GRE encapsulation
  • the tunnel negotiation initiator does not have the tunnel identification option during the registration of the proxy mobile update (PBU/PBA), or sets the tunnel type to 0 in the tunnel identification option with the tunnel.
  • the tunnel negotiation initiator has the above tunnel identification option in the registration process of the proxy mobile update (PBU/PBA), and sets M to 1.
  • the initiator on the tunnel sleeve has the above tunnel identification option during the registration process of the proxy mobile update (PBU/PBA), and sets M to 0.
  • the tunnel negotiation initiator includes a mobile access gateway and a local mobility anchor.
  • the local mobility anchor initiates the negotiation of the tunnel encapsulation mode, but it is not limited to -
  • the mobile access gateway connected to it can actively negotiate the tunnel encapsulation mode.
  • the local mobility anchor sends a response message to the mobile access gateway with the type of the tunnel encapsulation mode determined in the configuration information.
  • the local mobility anchor has configuration information in the response message.
  • the tunnel identification option shown in Figure 4 must be included, and the K flag is set to 1, with the appropriate tunnel identifier.
  • the tunnel ID in this direction is empty. Data transfer in this direction cannot be performed. For example, if the tunnel identification option is sent by the mobile access gateway, the downlink tunnel direction is empty, and the local mobility anchor does not need to send downlink data through the tunnel.
  • the nMAG carries the mobility option in the tunnel establishment request initiated by the LMA, and negotiates the tunnel type, the tunnel encapsulation mode, and the exchange of the data plane address and the tunnel identifier with the LMA, and is completely independent of the proxy.
  • the tunnel negotiation process is performed, and the data plane address exchange is completed, thereby establishing a tunnel for data service transmission.
  • the above tunnel negotiation process is further described as follows: 1.
  • the LMA changes the data plane address in some cases (for example, the data plane interface is switched to the new interface)
  • the LMA can actively initiate a message flow for updating the data plane tunnel address, and the MAG accepts the data plane address update request. , will maintain a new data plane tunnel.
  • the LMA When the LMA performs route optimization processing, it can initiate route optimization between two MAGs.
  • FIG. 5 is a flow chart of a specific implementation method for establishing a tunnel in a proxy mobile IP system according to an embodiment of the present invention, and the specific description is as follows:
  • MAGK MAG2 respectively performs a registration update process for the binding update of the LMA to the LMA, and establishes a binding cache entry BCE for the MN1 and CN2 on the LMA.
  • step 2011 the LMA initiates a tunneling request to the MAG1, and the data tunneling address option is included in the tunneling request, which includes the tunneling address of the MAG2.
  • Step 2012 MAG1 saves the tunnel address as an uplink tunnel address, and returns a confirmation message
  • the LMA initiates a tunnel negotiation process to the MAG2, where the request message carries a data plane tunnel address option, which includes the tunnel address of the MAG1.
  • Step 2014 the MAG2 saves the tunnel address as an uplink tunnel address, and returns a confirmation message.
  • step 2011 and step 2013 may be performed simultaneously, regardless of the order. If MAG1 initiates the process of changing the data plane tunnel address to the LMA in some cases, the LMA will notify you in time.
  • MAG2 is updated (the tunnel address of MAG1), and vice versa. If the data plane address of MAG2 is changed, MAG1 is notified to change after the LMA receives it.
  • the LMA updates the data plane address of the MAG3 to MAG2 after registering with the MAG3 agent.
  • the LMA can initiate route optimization between two MAGs.
  • FIG. 6 is a flowchart of a method for network switching according to an embodiment of the present invention.
  • the first mobile interface is attached to the first mobile access gateway of the first mobile network, and the second mobile interface is attached to the second mobile network.
  • An access gateway; the first interface and the second interface are logical interfaces, and may be the same physical interface or two different physical interfaces.
  • Step 300 When the mobile node moves from the first mobile network to the second mobile network, obtain the home network address prefix information of the mobile node from the local mobility anchor point; it should be noted that the mobile node moves from the second mobile network to the first The situation of the mobile network and the mobile node moving from the first mobile network to the second mobile network are not described again;
  • Step 301 After completing the access layer configuration with the mobile node according to the home network address prefix information, send a tunnel establishment request to the local mobility anchor to establish a tunnel with the local mobility anchor point.
  • the tunneling request carries the tunnel information exchanged with the local mobility anchor, where the tunnel information includes tunnel address information and tunnel type information;
  • Step 302 Forward data to the mobile node by using a tunnel established between the local mobility anchor point.
  • Step 302 Forward data to the mobile node by using a tunnel established between the local mobility anchor point.
  • the uplink data service sent by the mobile node through the mobile access gateway in the first mobile network is not lost by the local mobility anchor; and the downlink data service sent by the local mobility anchor to the mobile node is not moved by the second The mobile access gateway in the network is lost.
  • FIG. 7 is a flowchart of another network switching method according to an embodiment of the present invention.
  • the mobile node is specifically a mobile terminal.
  • Step 400 The mobile terminal (on IF1) is attached to the original mobile access gateway.
  • Step 401 The original mobile access gateway initiates a proxy binding registration message to the local mobility anchor, and establishes a corresponding binding buffer entry BCE and a data plane tunnel for the MN. Initial registration process, if other servers such as AAA
  • the established data plane tunnel includes any combination information such as a tunnel address, a tunnel type, and a tunnel identifier, and the information is stored in a binding buffer entry established by the MN.
  • Step 402 The original mobile access gateway sends a route advertisement to the mobile terminal (IF1) with the home network address prefix information allocated for the mobile terminal IF1.
  • Step 403 The mobile terminal performs local radio access configuration, where the mobile terminal may interact with the network to perform address repeat address detection and the like.
  • the mobile terminal communicates with the opposite node through the tunnel established between the original mobile access gateway and the local mobility anchor point, and sends and receives data packets.
  • Step 404 When the mobile terminal moves to a new mobile network, or needs to switch to a new interface IF2 under the condition of reliability maintenance of the interface, the mobile terminal (at IF2) attaches to the new mobile network for new mobile access. On the gateway. In the process of attaching the mobile network, the new mobile access gateway learns that the mobile terminal performs a handover preparation phase on the interface through the link layer information or the subscription information of the mobile terminal, and indicates whether the mobile terminal is about to switch to the IF2.
  • Step 405 The new mobile access gateway initiates a first proxy binding update (PBU, Proxy Binding Update) message to the local mobility anchor, but does not include the tunnel identification information. That is, in step 405, no tunnel negotiation is performed.
  • the tunnel information is required, and may be carried with a specific tunnel address or tunnel identifier, such as an empty tunnel address or a tunnel identifier, etc., to indicate that the handover preparation phase is being performed, and downlink data is not received temporarily.
  • the local mobility anchor accepts the PBU request, creates a new binding buffer entry, and assigns the home network address prefix information to the mobile terminal (IF2);
  • Step 406 The new mobile access gateway sends a route advertisement to the mobile terminal, with the home network address prefix information allocated for the mobile terminal IF2. If the home network address prefix is the same as the home prefix on the mobile terminal IF1, the identifier is set at this time, and the mobile terminal IF2 is required not to perform address conflict detection. If they are inconsistent, the new mobile access gateway may request the mobile terminal IF2 to perform address collision detection or at its discretion.
  • Step 407 The mobile terminal performs wireless access configuration locally.
  • Step 408 The new mobile access gateway detects whether the wireless access configuration of the mobile terminal is completed (such as address configuration, wireless configuration, etc.).
  • a feasible detection method is to detect whether the mobile terminal sends a link layer handover complete message or an uplink data or an IP layer message (route request).
  • Step 409 The new mobile access gateway sends a second proxy binding update (PBU) update message to the local mobility anchor, where the PBU message carries the tunnel information exchanged with the local mobility anchor, where the tunnel information includes the tunnel address. Information, tunnel type information, and tunnel identification information.
  • PBU proxy binding update
  • the second network node determines to establish a tunnel with the first network node according to the configured policy.
  • the new mobile access gateway will determine the type of tunnel that establishes a tunnel with the local mobility anchor. If the new mobile access gateway supports the tunnel type between the original mobile access gateway and the local mobility anchor, select a consistent tunnel and generate a corresponding tunnel identifier. If the tunnel type included in the setup tunnel request is different from the tunnel type stored by the second network node, and the new mobile access gateway supports the tunnel type between the original mobile access gateway and the local mobility anchor, for example A GRE tunnel is used between the original mobile access gateway and the local mobility anchor, and the new mobile access gateway and the local mobility anchor pre-configure the MPLS tunnel.
  • the new mobile access gateway will allocate a tunnel identifier of the new tunnel type, and
  • the PBU is carried to the local mobility anchor; optionally, the original tunnel information is also included in the PBU.
  • a one-to-one mapping relationship is established between the tunnel identifiers of different tunnel types, so that the same BCE data area can be located and forwarded when receiving the downlink data service.
  • Step 410 The local mobility anchor point allows the new mobile access gateway to send uplink data, and the response message includes tunnel information, including tunnel address information, tunnel type information, and tunnel identification information.
  • the second network node determines to establish a tunnel with the first network node according to the configured policy.
  • the local mobility anchor will check the configured policy, where the policy will indicate whether to allow the tunnel type to be changed. For example, if the policy flag is set to 1, it means that it is allowed, and 0 means no.
  • the policy can be configured for each mobile node or configured for this mobility anchor (i.e., all mobile nodes registered to the local mobility anchor comply with the configured policy).
  • the tunnel establishment request is rejected, the failed proxy binding acknowledgement message is returned, and the status code of the tunnel type is not allowed to be changed; if the tunnel type is allowed to be changed, the tunnel establishment request is accepted.
  • the tunnel ID of the new tunnel type will be assigned and carried to the new mobile access gateway through a successful proxy binding acknowledgement message.
  • the local mobility anchor may need to receive the data service of the original mobile access gateway or send data services to the original mobile access gateway. At this time, two new tunnels of different tunnel types will be established on the local mobility anchor point.
  • the local mobility anchor switches the network, establishes a tunnel with the new mobile access gateway, and performs data transmission.
  • the local mobility anchor initiates a binding revocation process to the original mobile access gateway, or waits for the mobile terminal to disconnect from the original mobile access gateway, and performs a proxy mobile binding deregistration process.
  • FIG. 8 is a schematic structural diagram of a network switching system according to an embodiment of the present invention.
  • the network switching system in this embodiment includes: a new mobile access gateway 21, a local mobility anchor point 3; optionally, the system further includes: a mobile node 1, an original mobile access gateway 20;
  • the first interface is attached to the original mobile access gateway 20 of the first mobile network, and the second interface is attached to the new mobile access gateway of the second network. twenty one ;
  • a new mobile access gateway 21 configured to acquire the home network address prefix information of the mobile node 1 from the local mobility anchor 3 when the mobile node 1 moves from the first mobile network to the second mobile network;
  • a local mobility anchor point 3 configured to return to the new mobile access gateway 21 in the second mobile network, the home network address prefix information used by the mobile node 1 in the second mobile network;
  • the new mobile access gateway 21 After the new mobile access gateway 21 completes the access layer configuration according to the home network address prefix information, the new mobile access gateway 21 sends a tunnel establishment request to the local mobility anchor 3 to establish a tunnel with the local mobility anchor 3.
  • the tunneling request carries the tunnel information exchanged with the local mobility anchor, where the tunnel information includes tunnel address information and tunnel type information;
  • the local mobility anchor point 3 is configured to establish a tunnel with the new mobile access gateway 21 after receiving the tunnel establishment request of the new mobile access gateway 21;
  • the new mobile access gateway 21 is for forwarding data to the mobile node 1 through a tunnel established with the local mobility anchor 3.
  • FIG. 9 is a schematic diagram of a proxy mobile IP system architecture based on the separation of the control plane and the data plane according to an embodiment of the present invention.
  • the MAG and the LMA have respective control plane addresses and data plane addresses.
  • the control plane address is used for the registration, update, and logout control processes of the MAG and the LMA
  • the data plane address is used to forward the data packet in the proxy mobile IP tunnel between the MAG and the LMA.
  • the data plane address is included in the context data area established for each MN (for example, BCE Binding Cache Entry Binding Cache).
  • the context data area established for each MN on the above MAG including the following options in Table 1 (other items not related to this scheme are not listed)
  • the uplink LMA address of the MAG sends data, and the MAG (user plane, uplink) can receive the downlink data of the address at the same time;
  • the tunnel identification is an option, such as GRE Key.
  • the uplink LMA tunnel ID of the MAG sends data.
  • the MAG can receive downlink data of the tunnel at the same time;
  • the MAG receives the downlink data of the address; the uplink data may or may not be sent on the (user plane, downlink) address.
  • this address is consistent with the "LMA address (user plane, uplink)", and inconsistencies may occur during the handover process.
  • the tunnel identification is an option, such as GRE Key.
  • the MAG receives the downlink data corresponding to the tunnel identifier; the uplink data may or may not be sent on the tunnel.
  • the tunnel identifier is consistent with the "LMA tunnel identifier (user plane, uplink)", and inconsistencies may occur during the switching process.
  • MAG address (user plane) The current MAG data plane address for the MN service.
  • Control Plane Address is also the source address of the Proxy Binding Update (Registration/Response) message.
  • the data plane address carries the mobility option negotiated in the tunnel.
  • the network switching system referred to in this embodiment is a proxy mobile IP system separated from the data plane (tunnel) based on the control plane (proxy binding registration process), which adopts a registration process and a tunneling process to resolve the mobile terminal. Packet loss problem when heterogeneous network switching based on proxy mobile IP protocol.
  • the functions and functions of the mobile terminal 1, the original mobile access gateway 20, the new mobile access gateway 21, and the local mobility anchor point 3 in the network switching system will be described in detail;
  • one interface IF1 of the mobile terminal 1 remains in communication with the pMAG 20, and the other interface IF2 is connected to the nMAG 21.
  • the nMAG 21 first registers with the LMA3, and the nMAG 21 learns that the mobile terminal 1 will switch from IF1 to IF2 from the link layer access or subscription information of the mobile terminal 1, and in the preparation phase, only the proxy binding update (PBU) is sent to the LMA3. ) message, registering;
  • the LMA3 accepts the registration request, and returns a binding confirmation message to the nMAG 21, carrying the home address prefix HNP for the mobile terminal 1.
  • the nMAG 21 transmits a route advertisement to the mobile terminal 1, and transmits the home network address prefix information on the IF 2 of the mobile terminal 1.
  • the mobile terminal 1 performs wireless access configuration according to the home network address prefix information. After learning that the IF2 radio access configuration of the mobile terminal 1 is completed (through the link layer information, or the route request message sent by the MN, or other manners), the nMAG21 initiates an update request of the PBU to the LMA3, with the service for the mobile terminal.
  • the data plane address option is used to establish a downlink tunnel; the LMA3 accepts the PBU update request, and returns a binding acknowledgement message to the nMAG 21 with the uplink data plane address option.
  • LMA3 and nMAG21 forward the data service of IF2 of mobile terminal 1 through a new tunnel.
  • FIG. 10 is a schematic structural diagram of a mobile access gateway according to an embodiment of the present invention.
  • the network address obtaining module 200 when the mobile node moves from the first mobile network to the second mobile network, acquires home network address prefix information used by the mobile node in the second mobile network from the local mobility anchor point;
  • the tunnel information requesting module 201 after completing the access layer configuration with the mobile node according to the home network address prefix information, sending a tunnel establishment request to the local mobility anchor to establish a local mobility anchor point
  • the tunneling request carries the tunnel information exchanged with the local mobility anchor, and the tunnel information includes tunnel address information and tunnel type information;
  • the data forwarding module 202 is configured to forward data to the mobile node by using a tunnel established between the local mobility anchor point.
  • FIG. 11 is a schematic structural diagram of another mobile access gateway according to an embodiment of the present invention.
  • the mobile access gateway in this embodiment has the same network address obtaining module 200, tunnel information requesting module 201, and data forwarding module 202 as in FIG. 11.
  • the network address obtaining module 200 and the tunnel information request are further explained.
  • the module 201 wherein the network address obtaining module 200 is specifically configured to send a first proxy binding update message to the local mobility anchor to obtain the home network address prefix information of the mobile node from the local mobility anchor.
  • the tunnel information is required, and may include a specific tunnel address or a tunnel identifier, such as an empty tunnel address or a tunnel identifier, etc., to indicate that the handover preparation phase is not received. .
  • the local mobility anchor accepts the PBU request, creates a new binding buffer entry, and assigns the home network address prefix to the mobile terminal (IF2);
  • the tunnel information requesting module 201 is specifically configured to send a second proxy binding update message to the local mobility anchor point, where the second proxy binding update message carries tunnel information to indicate a local mobility anchor point, where the 2.
  • the mobile access gateway is already in the handover ready phase and is ready to receive downlink data.
  • the tunnel address information may be a data plane address.
  • the tunnel information requesting module 201 needs to detect whether the wireless terminal configuration of the mobile terminal is complete (such as address configuration, wireless) before sending the second proxy binding update message. Configuration, etc.) is completed.
  • a feasible detection method is to detect whether the mobile terminal sends a link layer handover complete message or an uplink data or an IP layer message (route request).
  • the tunnel identifier sending module 203 is configured to send, according to the tunnel type in the tunnel information carried in the second proxy binding update message, a tunnel identifier corresponding to the tunnel type to the local mobility anchor point.
  • the tunnel identity sending module 203 sends a tunnel identifier corresponding to the tunnel type and the tunnel encapsulation mode to the local mobility anchor.
  • the mobile access gateway in this embodiment when the mobile node moves from the first mobile network to the second mobile network, first obtains the home network address prefix information of the mobile node from the local mobility anchor point; and completes the access layer at the mobile node. After the configuration, the tunnel with the local mobility anchor is established, so that the address of the mobile access gateway in the first mobile network saved on the local mobility anchor is not connected by the mobile in the second mobile network. In place of the address of the gateway, the uplink data service sent by the mobile node through the mobile access gateway in the first mobile network is not lost by the local mobility anchor; and the downlink data service sent by the local mobility anchor to the mobile node is not The mobile access gateway in the second mobile network is lost.
  • FIG. 12 it is a schematic structural diagram of a local mobility anchor point according to an embodiment of the present invention.
  • the tunnel information exchanged, the tunnel information includes tunnel address information and tunnel type information.
  • the local mobility anchor further includes: an update tunnel module, configured to: when the tunnel type included in the tunnel establishment request and the tunnel type stored by the second network node are different, the second network node according to the configured policy Determining establishing a tunnel with the first network node.
  • an update tunnel module configured to: when the tunnel type included in the tunnel establishment request and the tunnel type stored by the second network node are different, the second network node according to the configured policy Determining establishing a tunnel with the first network node.
  • the local mobility anchor point when receiving the notification that the mobile access gateway is in the preparatory handover phase and does not receive the downlink data, the local mobility anchor only allocates the home network address prefix information to the mobile terminal, and After the mobile terminal completes the radio access configuration, the local mobility anchor sends the downlink data information to the mobile access gateway, so that the address of the original mobile access gateway stored on the local mobility anchor will not be newly moved during the registration process.
  • the address of the access gateway is replaced, and the uplink data service sent by the mobile terminal through the original mobile access gateway is not lost by the local mobility anchor point; and after the wireless terminal configuration of the mobile terminal attached to the new mobile access gateway is completed, the data is further performed. Transmission, so the downlink data service sent by the local mobility anchor to the mobile terminal will not be lost by the new mobile access gateway.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种网络切换方法、 装置及系统
本申请要求于 2008年 12月 24日提交中国专利局、 申请号为 200810220342. 9、 发 明名称为 "网络切换方法、 装置及系统、 隧道协商方法"的中国专利申请以及于 2009 年 3月 11日提交中国专利局、 申请号为 200910128198. 0、 发明名称为 "一种网络切换 方法、 装置及系统"的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及移动通信技术, 尤其涉及一种网络切换方法、 装置及系统。 背景技术 在代理移动 IP系统中, MAG (Mobile Access Gateway)模拟家乡链路,向丽(Mobile
Node, 移动节点)通告 HNP (Home Network Prefix, 家乡网络地址前缀), 使丽以为自 己始终在家乡链路上; MAG代替丽向 LMA (Local Mobility Anchor, 本地移动锚点) 发送注册报文, 在 LMA上建立关于家乡网络地址前缀信息和 Proxy-CoA (Proxy Care-of Address , 代理转交地址) 的绑定缓存条目, 并且在 MAG和 LMA间建立一条双向隧道用 于传输丽的报文。 其报文收发过程如下:
对端节点向移动节点的家乡地址发送报文, 该报文会被 LMA截获, 然后 LMA根据家 乡前缀查询绑定列表, 然后通过 LMA与 MAG之间的隧道将报文发送给 MAG处理, MAG解 封装后根据报文的目的地址将报文发送给丽。
移动节点给对端节点发报文时, MAG收到该报文进行封装, 增加外层 IP报文头(源 地址), 然后通过 MAG与 LMA之间的隧道, 将报文发送给 LMA, LMA剥离外层 IP报文头, 将内层报文转发给对端节点。
当代理移动 IPv6作为异质网络(如 WiMAX与 3GPP)的互联互通协议时, MN (Mobile Node, 移动节点), 例如移动终端在异质网络中移动时, 基于代理移动 IPv6的网络切换 过程中, pMAG (Previous Mobile Access Gateway, 原移动接入网关)位于一种接入技 术网络中, nMAG (new Mobile Access Gateway, 新移动接入网关)位于另一种接入技 术网络中。在互联网络系统中, pMAG和 nMAG连接到相同的 LMA Local Mobility Anchor, 本地移动锚点)。
发明人在实施本发明的过程中, 发现现有技术存在如下缺点:
新移动接入网关在向本地移动锚点的注册过程中同时建立了双向隧道。此时本地移 动锚点将移动终端的数据业务传输从 IF1连接的原移动接入网关对应的隧道,切换到了 IF2连接的新移动接入网关。 因为本地移动锚点上保存的绑定缓存条目中对应的是新移 动接入网关的地址, 所以移动终端 (IF1 ) 通过原移动接入网关发送的上行数据业务将 被本地移动锚点丢失; 并且因为附着在新移动接入网关的移动终端 IF2的 IP地址配置 和 /或无线链路配置尚未完成, 所以本地移动锚点向移动终端(IF2)发送的下行数据业 务将被新的移动接入网关丢失。
发明内容
本发明实施提供一种网络切换方法、装置及系统、代理移动 IP系统中建立隧道方法, 在进行网络切换时, 本地移动锚点和新移动接入网关上的数据业务都不会丢失。
本发明实施例提供一种网络切换方法, 包括:
当移动节点从第一移动网络移动到第二移动网络时,从本地移动锚点获取移动节点 的家乡网络地址前缀信息;
根据所述家乡网络地址前缀信息, 完成与所述移动节点之间的接入层配置后, 向本 地移动锚点发送建立隧道请求, 以建立与所述本地移动锚点之间的隧道; 所述建立隧道 请求中携带有与所述本地移动锚点交换的隧道信息, 所述隧道信息包括隧道地址信息、 隧道类型信息;
通过与所述本地移动锚点之间建立的隧道, 向所述移动节点转发数据。
本发明实施例还提供了一种建立隧道的方法, 应用于代理移动 IP系统中, 包括: 第一网络节点向第二网络节点发送建立隧道请求,所述建立隧道请求中携带有与所 述第二网络节点交换的隧道信息, 所述隧道信息包括隧道地址信息、 隧道类型信息; 所述第二网络节点根据所述建立隧道请求中携带的隧道信息,建立与所述第一网络 节点之间的隧道。
相应地, 本发明实施例还提供了一种移动接入网关, 包括:
网络地址获取模块, 当移动节点从第一移动网络移动到第二移动网络时, 从本地移 动锚点获取移动节点的家乡网络地址前缀信息;
隧道信息请求模块, 根据所述家乡网络地址前缀信息, 完成与所述移动节点之间的 接入层配置后, 向本地移动锚点发送建立隧道请求, 以建立与所述本地移动锚点之间的 隧道; 所述建立隧道请求中携带有与所述本地移动锚点交换的隧道信息, 所述隧道信息 包括隧道地址信息、 隧道类型信息;
数据转发模块, 用于通过与所述本地移动锚点之间建立的隧道, 向所述移动节点转 发数据。
相应地, 本发明实施例还提供了一种本地移动锚点, 包括:
网络地址发送模块, 当移动节点从第一移动网络移动到第二移动网络时, 向所述第 二移动网络中的移动接入网关返回所述移动节点的家乡网络地址前缀信息;
建立隧道模块, 用于在接收到所述移动接入网关的建立隧道请求后, 建立与所述移 动接入网关之间的隧道; 所述建立隧道请求中携带有与所述本地移动锚点交换的隧道信 息, 所述隧道信息包括隧道地址信息、 隧道类型信息。
相应地, 本发明实施例还提供了一种网络切换系统, 包括: 移动接入网关和本地移 动锚点;
所述移动接入网关, 用于当移动节点从第一移动网络移动到第二移动网络时, 用于 从本地移动锚点获取移动节点的家乡网络地址前缀信息; 并根据所述家乡网络地址前缀 信息, 完成与所述移动节点之间的接入层配置后, 向本地移动锚点发送建立隧道请求; 通过与所述本地移动锚点之间建立的隧道, 向所述移动节点转发数据; 其中, 所述建立 隧道请求中携带有与所述本地移动锚点交换的隧道信息,所述隧道信息包括隧道地址信 息、 隧道类型信息;
所述本地移动锚点,用于向所述第二移动网络中的移动接入网关返回所述移动节点 的家乡网络地址前缀信息; 在接收到所述移动接入网关的建立隧道请求后, 建立与所述 移动接入网关之间的隧道。
实施本发明, 具有如下有益效果:
本发明实施例提供了建立隧道方法应用于一种代理移动 IP系统中,通过在建立隧道 请求中携带包括隧道地址信息和隧道类型信息在内的隧道信息,从而使得隧道协商的过 程完全独立于代理绑定更新的注册过程。
本发明实施例提供的网络切换方法、 装置和系统, 当移动节点从第一移动网络移动 到第二移动网络时, 首先从本地移动锚点获取移动节点在第二移动网络中使用的家乡网 络地址前缀信息; 在移动节点完成接入层的配置之后, 才建立与所述本地移动锚点之间 的隧道,从而使得因为本地移动锚点上保存的第一移动网络中的移动接入网关的地址不 会被第二移动网络中的移动接入网关的地址代替,移动节点通过第一移动网络中的移动 接入网关发送的上行数据业务不会被本地移动锚点丢失;并且本地移动锚点向移动节点 发送的下行数据业务也不会被第二移动网络中的移动接入网关丢失。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有 技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本 发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的附图。
图 1是本发明实施例的一种代理移动 IP系统中建立隧道方法流程图;
图 2是本发明实施例的一种移动选项的结构示意图;
图 3是本发明实施例的另一种代理移动 IP系统中建立隧道的具体实现方法的流程 图;
图 4是本发明实施例的另一种移动选项的结构示意图;
图 5是本发明实施例的另一种代理移动 IP系统中建立隧道的具体实现方法的流程 图;
图 6是本发明实施例的一种网络切换的方法流程图;
图 7是本发明实施例的另一种网络切换方法的流程图;
图 8是本发明实施例的一种网络切换系统结构示意图;
图 9是本发明实施例的一种基于控制面与数据面分离的代理移动 IP系统架构示意 图;
图 10是本发明实施例的一种移动接入网关的结构示意图;
图 11是本发明实施例的另一种移动接入网关的结构示意图;
图 12是本发明实施例的一种本地移动锚点的结构示意图。 具体实施方式 本发明实施提供一种网络切换方法、装置及系统、代理移动 IP系统中建立隧道方法, 使得移动节点在进行网络切换时,本地移动锚点和新移动接入网关上的数据业务都不会 丢失。
参见图 1为本发明实施例的一种代理移动 IP系统中建立隧道方法的流程图。 步骤 100, 第一网络节点向第二网络节点发送建立隧道请求, 所述建立隧道请求中 携带有与所述第二网络节点交换的隧道信息, 所述隧道信息包括隧道地址信息、 隧道类 型信息。
其中,当所述第一网络节点为移动接入网关时,所述第二网络节点为本地移动锚点; 或者, 当所述第一网络节点为本地移动锚点时, 所述第二网络节点为移动接入网关。
步骤 101, 第二网络节点根据所述隧道消息中携带的隧道信息, 建立与所述第一网 络节点之间的隧道。
可选的, 所述隧道信息中的隧道地址, 隧道类型可以通过一个移动选项或两个不同 的移动选项来携带。
当所述建立隧道请求中包含的隧道类型和所述第二网络节点存储的隧道类型不同 时, 所述第二网络节点根据配置的策略, 确定建立与所述第一网络节点之间的隧道。
实施上述代理移动 IP系统中建立隧道方法,通过在建立隧道请求中携带包括隧道地 址、 隧道类型等隧道信息, 可以在隧道节点 (如本地移动锚点, 移动接入网关) 启动后 通过代理移动 IP系统中的心跳 (Heartbeat ) 消息或通知 (Notification) 消息或代理 绑定更新消息来承载, 从而使得隧道协商的过程独立于代理绑定更新的注册过程。
本发明实施例的代理移动 IP系统中建立隧道方法, 除了包括隧道地址的交换过程还 包括隧道封装模式协商以及隧道标识交换过程。 下面将就该隧道协商过程进行详细阐 述。
首先需要说明的是, 基于代理移动 IP协议的系统中, 实现隧道地址的协商过程, 从 实现上,可以在代理绑定更新消息中增加一个新的移动选项,也即数据面隧道地址选项。
参见图 2, 为本发明中移动选项实施例的示意图, 在本发明中, 该移动选项是数据 面地址选项, 其中:
Type: 表示该移动选项的类型标识。 这里表示该选项为隧道地址。
Length: 表示该移动选项的长度, 这里是隧道地址的长度, 16个字节。
隧道地址:这里是 MAG或 LMA的数据面隧道地址。当数据面地址与控制面地址一致时, 该隧道地址选项可以不带。只有不一致时,需要在 PBU/PBA (代理绑定更新, Proxy Binding Update/代理绑定确认, Proxy Binding Acknowledge) 消息 (或其他 PMIPv6 (代理移动 IPv6, Proxy Mobile IPv6) 相关消息) 中带有该隧道地址选项。
参见图 3, 本发明实施例的一种代理移动 IP系统中建立隧道方法具体实现的流程如 下: 步骤 200, 当丽移动到新的网络, 并通过接口 (IF2) 附着到 nMAG下时, nMAG代替丽 进行移动 IP的行为, 向 LMA发起代理绑定更新的注册请求所述注册请求中未带有隧道协 商信息。
步骤 201, LMA接受 nMAG的注册请求, 向其回复代理绑定确定, 为其分配 HNP (Home Network Prefix, 家乡地址前缀) ;
步骤 202, 在丽根据 HNP, 完成地址配置之后, nMAG向 LMA发起代理绑定更新的建立 隧道请求时, 带有上述移动选项, 以向 LMA指示, 在该移动选项携带的数据面地址接收 丽的下行业务。
步骤 203, LMA接受 nMAG的建立隧道请求后, 分配上行业务的数据面隧道地址, 并在 隧道协商确认中通过该移动选项带给 nMAG。
步骤 204, LMA与 nMAG根据其交换的数据面地址, 建立新的隧道, 并通过该新的隧道 转发丽 ( IF2) 的数据业务。
需要说明的是, 从 nMAG来看, 上述移动选项可以看作是 Alternate CoA选项的扩展。 但对于 LMA来讲, 上述移动选项是一个新的移动选项。
基于代理移动 IP协议的系统中, 采用隧道方式进行传输, 为了实施本发明的隧道协 商方法, 还可以对代理移动 IP协议进行扩展, 增加一个新的移动选项, 以便携带隧道类 型与隧道标识相关信息。
参见图 4, 为本发明中实施例的另一种移动选项的结构示意图, 其中:
Type: 类型, 这里表示为隧道标识选项;
Length: 长度, 表示隧道标识选项的长度。
隧道类型: 表示采用哪一种隧道类型, 如 0表示 IPinIP隧道、 1表示 GRE、 2表示 MPLS 等。
M: 模式, 表示隧道封装模式的协商; 0表示动态隧道封装。 此时必须带有隧道标识 字段。 1表示静态预配置隧道。 此时可带有或不带有预配置的隧道标识。
K: 标识, 表示是否携带有隧道标识字段。
隧道标识, 用于发送接收数据时确定相应的移动终端等; 一般地, 携带在移动接入 网关发送的消息中称为下行隧道标识,携带在本地移动锚点发送的消息中称为上行隧道 标识。
下面以 GRE (Generic Routing Encapsulation, 通用路由封装) 隧道来说明隧道模 式协商和隧道标识交换过程。 隧道模式协商过程如下:
GRE隧道封装模式, 包括不支持 GRE封装, 静态 GRE封装, 动态 GRE封装;
A、 不支持 GRE封装: 隧道协商发起方在代理移动更新 (PBU/PBA) 的注册过程中, 不带有该隧道标识选项, 或者在带有的隧道标识选项中将隧道类型设置为 0。
B、 静态 GRE封装: 隧道协商发起方在代理移动更新 (PBU/PBA) 的注册过程中带有 上述隧道标识选项, 同时置 M为 1。
C、 动态 GRE封装: 隧道袖上发起方在代理移动更新 (PBU/PBA) 的注册过程中带有 上述隧道标识选项, 同时置 M为 0。
本实施例中, 隧道协商发起方包括移动接入网关和本地移动锚点。 本地移动锚点发 起隧道封装模式的协商的场景有, 但不局限于-
A、 当本地移动锚点配置改变或软件升级, 可主动向其连接的移动接入网关进行隧 道封装模式进行协商。
B、 当移动接入网关上未启动隧道封装(例如 GRE隧道封装) 时, 本地移动锚点在向 移动接入网关发送的响应消息中带有配置信息中确定的隧道封装模式的类型。
C 当移动终端从原移动接入网关移动到新移动接入网关时, 新移动接入网关发送 代理绑定更新时未带有该隧道选项时,本地移动锚点在响应消息中带有配置信息中确定 的隧道类型。
如果移动接入网关和本地移动锚点需要进行隧道标识交换, 则必须包括图 4所示的 隧道标识选项, 同时设置 K标志为 1, 并带有合适的隧道标识。
如果 K标志为 1, 且隧道标识选项中的长度字段指示的长度不包括隧道标识字段时, 则表示该方向的隧道标识为空。 不能进行该方向的数据传输。 例如, 该隧道标识选项由 移动接入网关发出, 则表示下行隧道方向为空, 本地移动锚点不需要通过隧道发送下行 数据。
实施上述隧道协商的方法, nMAG通过在向 LMA发起的建立隧道请求中携带移动选项, 以和 LMA协商隧道类型, 隧道封装模式, 以及进行数据面地址和隧道标识的交换, 在完 全独立于代理绑定更新的注册过程之外, 进行隧道协商过程, 完成数据面地址交换, 从 而建立隧道, 进行数据业务传输。
上述隧道协商过程进一步说明如下: 1、 当 LMA在某些情况下数据面地址改变时(例如数据面接口倒换到新的接口上) , LMA可主动发起用于更新数据面隧道地址的消息流程, MAG接受数据面地址更新请求后, 将维护新的数据面隧道。
2、 当 LMA为了进行路由优化处理时, 可以发起建立两个 MAG间的路由优化。
图 5为本发明实施例的另一种代理移动 IP系统中建立隧道的具体实现方法的流程 图, 具体描述如下:
步骤 2010, MAGK MAG2各自代理丽 1、 CN2 (Correspondent Node, 对端节点)分别 向 LMA进行绑定更新的注册过程, 在 LMA上分别建立丽 1、 CN2的绑定缓存条目 BCE。
步骤 2011, 在数据面或其他信令消息的触发下, LMA向 MAG1发起建立隧道请求, 其 在该建立隧道请求中携带数据面隧道地址选项, 其中包含 MAG2的隧道地址。
步骤 2012, MAG1保存该隧道地址作为上行隧道地址, 并回复确认消息;
步骤 2013, LMA向 MAG2发起隧道协商过程, 其中在请求消息中携带数据面隧道地址 选项, 其中包含 MAG1的隧道地址。
步骤 2014, MAG2保存该隧道地址作为上行隧道地址, 并回复确认消息;
如图 5所示, 其中步骤 2011和步骤 2013两个步骤可能同时进行, 不分先后顺序。 如果 MAG1在某些情况下向 LMA发起更改数据面隧道地址的过程, 则 LMA将及时通知
MAG2进行更新(MAG1的隧道地址) , 反之亦然, MAG2的数据面地址更改, 则 LMA收到后, 通知 MAG1进行更改。
如果丽 1从 MAG1切换到 MAG3, 则 LMA在 MAG3代理丽 1进行注册后, 将 MAG3的数据面地 址更新到 MAG2。
实施上述隧道协商方法, LMA可以发起建立两个 MAG间的路由优化。
参见图 6, 为本发明实施例的一种网络切换的方法流程图。
首先, 移动节点从第一移动网络移动到第二移动网络之前, 在第一接口附着在第一 移动网络的第一移动接入网关, 在第二接口附着在第二移动网络中的第二移动接入网 关; 需要说明的是, 所述第一接口和第二接口是逻辑接口, 在具体实现的时候, 可以是 同一个物理接口, 或者两个不同的物理接口。
步骤 300, 当移动节点从第一移动网络移动到第二移动网络时, 从本地移动锚点获 取移动节点的家乡网络地址前缀信息; 需要说明的是, 移动节点从第二移动网络移动到 第一移动网络的情形与移动节点从第一移动网络移动到第二移动网络, 不再赘述; 步骤 301, 根据所述家乡网络地址前缀信息, 完成与所述移动节点之间的接入层配 置后, 向本地移动锚点发送建立隧道请求, 以建立与所述本地移动锚点之间的隧道; 所 述建立隧道请求中携带有与所述本地移动锚点交换的隧道信息,所述隧道信息包括隧道 地址信息、 隧道类型信息;
步骤 302, 通过与所述本地移动锚点之间建立的隧道, 向所述移动节点转发数据。 实施上述的网络切换方法, 当移动节点从第一移动网络移动到第二移动网络时, 首 先从本地移动锚点获取移动节点的家乡网络地址前缀信息;在移动节点完成接入层的配 置之后, 才建立与所述本地移动锚点之间的隧道, 从而使得因为本地移动锚点上保存的 第一移动网络中的移动接入网关的地址不会被第二移动网络中的移动接入网关的地址 代替,移动节点通过第一移动网络中的移动接入网关发送的上行数据业务不会被本地移 动锚点丢失;并且本地移动锚点向移动节点发送的下行数据业务也不会被第二移动网络 中的移动接入网关丢失。
参见图 7, 为本发明实施例的另一种网络切换方法的流程图。
本实施例中, 移动节点具体为移动终端。
步骤 400, 移动终端 (在 IF1上) 附着到原移动接入网关上。
步骤 401, 原移动接入网关向本地移动锚点发起代理绑定注册消息, 为丽建立相应 的绑定缓冲条目 BCE和数据面隧道。 初次注册过程, 如果其他服务器如 AAA
(Authentication Authorization Accounting, 鉴权授权计费服务器)等没有为移动 终端预先分配家乡网络地址前缀信息,本地移动锚点为移动终端分配家乡网络地址前缀 信息。 其中, 建立的数据面隧道包括隧道地址、 隧道类型、 隧道标识等任意组合信息, 这些信息保存在为丽建立的绑定缓冲条目中。
步骤 402, 原移动接入网关向移动终端 (IF1 )发送路由公告, 带有为移动终端 IF1 分配的家乡网络地址前缀信息。
步骤 403, 移动终端在本地进行无线接入配置, 其中可能与网络进行交互, 以进行 地址重复地址检测等。
上述过程完成,移动终端将通过原移动接入网关和本地移动锚点之间建立的隧道与 对端节点进行通信, 收发数据包。
步骤 404, 当移动终端移动到新的移动网络, 或者其接口的可靠性维护等情况下需 要切换到新的接口 IF2下工作时, 移动终端(在 IF2)附着到新移动网络的新移动接入网 关上。 在附着移动网络的过程中,新移动接入网关通过移动终端的链路层信息或者签约信 息等了解到移动终端是在该接口上进行切换准备阶段, 表示移动终端是否正要切换到 IF2上。
步骤 405, 新移动接入网关向本地移动锚点发起第一代理绑定更新 (PBU, Proxy Binding Update) 消息, 但不包括隧道标识信息, 即在步骤 405, 不进行隧道协商。 在 某些实现中, 隧道信息是必须的, 则可以带有特定的隧道地址或隧道标识, 如空隧道地 址或隧道标识等; 以表示正在切换准备阶段, 暂不接收下行数据。
本地移动锚点接受 PBU请求, 创建新的绑定缓冲条目, 为移动终端 (IF2)分配家乡 网络地址前缀信息;
步骤 406, 新移动接入网关向移动终端发送路由公告, 带有为移动终端 IF2分配的家 乡网络地址前缀信息。 如果此家乡网络地址前缀与移动终端 IF1上的家乡前缀一致, 则 此时带有标识, 要求移动终端 IF2不做地址冲突检测。 如果不一致, 则新移动接入网关 可要求移动终端 IF2做地址冲突检测或由其自行决定。
步骤 407, 移动终端在本地进行无线接入配置。
步骤 408, 新移动接入网关检测移动终端无线接入配置是否完成 (如地址配置, 无 线配置等)完成。 可行的检测方式有, 检测移动终端是否发送链路层切换完成消息或者 上行数据或者 IP层消息 (路由请求) 等。
步骤 409, 新移动接入网关向本地移动锚点发送第二代理绑定更新(PBU) 的更新消 息, 该 PBU消息中携带有与本地移动锚点交换的隧道信息, 所述隧道信息包括隧道地址 信息、 隧道类型信息和隧道标识信息。
当所述建立隧道请求中包含的隧道类型和所述第二网络节点存储的隧道类型不同 时, 所述第二网络节点根据配置的策略, 确定建立与所述第一网络节点之间的隧道。
具体为: 新移动接入网关将确定与本地移动锚点之间建立隧道的隧道类型。 如果新 移动接入网关支持原移动接入网关与本地移动锚点之间的隧道类型, 则选择一致的隧 道, 并生成相应的隧道标识等。 如果当所述建立隧道请求中包含的隧道类型和所述第二 网络节点存储的隧道类型不同时,且新移动接入网关支持原移动接入网关与本地移动锚 点之间的隧道类型, 例如原移动接入网关与本地移动锚点之间采用 GRE隧道, 而新移动 接入网关与本地移动锚点预配置 MPLS隧道, 则此时新移动接入网关将分配新隧道类型的 隧道标识, 并在 PBU中携带给本地移动锚点; 可选地, 在 PBU中还包括原隧道信息。 并在 新建立隧道之前, 不同隧道类型的隧道标识间将建立一一映射关系, 以便接收到下行数 据业务时能定位到相同的 BCE数据区, 并进行转发。
步骤 410, 本地移动锚点允许新移动接入网关发送上行数据, 则在应答消息中, 带 有隧道信息, 包括隧道地址信息、 隧道类型信息和隧道标识信息等。
当所述建立隧道请求中包含的隧道类型和所述第二网络节点存储的隧道类型不同 时, 所述第二网络节点根据配置的策略, 确定建立与所述第一网络节点之间的隧道。
具体为: 当新移动接入网关带有的隧道类型与本地移动锚点中移动节点绑定缓冲条 目 BCE中的隧道类型 (也即本地移动锚点与原移动接入网关之间的隧道的隧道类型) 不 同时, 本地移动锚点将检查配置的策略, 这里策略将指示是否允许改变隧道类型, 例如 策略标志设置为 1, 表示允许, 为 0, 表示不允许。 策略可以针对每个移动节点来配置, 或者针对本移动锚点来配置(也即注册到本地移动锚点的所有移动节点遵从该配置的策 略) 。
根据配置的策略, 如果不允许改变隧道类型, 则拒绝该建立隧道请求, 回复失败的 代理绑定确认消息, 带有不允许改变隧道类型的状态码; 如果允许改变隧道类型, 则接 受建立隧道请求, 此时将分配新隧道类型的隧道标识, 并通过成功的代理绑定确认消息 携带给新移动接入网关。 同时, 为了保证数据完整性, 本地移动锚点可能需要接收原移 动接入网关的数据业务或向原移动接入网关发送数据业务,此时本地移动锚点上将建立 两种不同隧道类型的新隧道标识之间的一一映射关系, 以便收发数据业务时根据不同的 隧道标识都能检索到相同的 BCE数据区, 并进行转发。 最后, 本地移动锚点切换网络, 建立与新移动接入网关之间的隧道, 进行数据传输。
可选地, 在完成上述过程后, 本地移动锚点向原移动接入网关发起绑定撤销过程, 或者等待移动终端从原移动接入网关断开, 进行代理移动绑定注销过程。
实施上述的网络切换方法, 当移动节点从第一移动网络移动到第二移动网络时, 首 先从本地移动锚点获取移动节点的家乡网络地址前缀信息; 在移动节点完成接入层的配 置之后, 才建立与所述本地移动锚点之间的隧道, 从而使得因为本地移动锚点上保存的 第一移动网络中的移动接入网关的地址不会被第二移动网络中的移动接入网关的地址 代替,移动节点通过第一移动网络中的移动接入网关发送的上行数据业务不会被本地移 动锚点丢失; 并且本地移动锚点向移动节点发送的下行数据业务也不会被第二移动网络 中的移动接入网关丢失。
参见图 8, 为本发明实施例的一种网络切换系统结构示意图。 本实施例中的网络切换系统, 包括: 新移动接入网关 21、 本地移动锚点 3; 可选的, 所述系统还包括: 移动节点 1、 原移动接入网关 20;
移动节点 1从第一移动网络移动到第二移动网络之前, 在第一接口附着在第一移动 网络的原移动接入网关 20, 在第二接口附着在第二网络中的新移动接入网关 21 ;
新移动接入网关 21, 当移动节点 1从第一移动网络移动到第二移动网络时, 用于从 本地移动锚点 3获取移动节点 1的家乡网络地址前缀信息;
本地移动锚点 3,用于向第二移动网络中的新移动接入网关 21返回移动节点 1在所述 第二移动网络中使用的家乡网络地址前缀信息;
新移动接入网关 21根据所述家乡网络地址前缀信息完成接入层配置后,新移动接入 网关 21向本地移动锚点 3发送建立隧道请求, 以建立与本地移动锚点 3之间的隧道; 所述 建立隧道请求中携带有与所述本地移动锚点交换的隧道信息,所述隧道信息包括隧道地 址信息、 隧道类型信息;
本地移动锚点 3用于在接收到新移动接入网关 21的建立隧道请求后, 建立与新移动 接入网关 21之间的隧道;
新移动接入网关 21用于通过与本地移动锚点 3之间建立的隧道, 向移动节点 1转发数 据。
实施上述的网络切换系统, 当移动节点从第一移动网络移动到第二移动网络时, 首 先从本地移动锚点获取移动节点的家乡网络地址前缀信息;在移动节点完成接入层的配 置之后, 才建立与所述本地移动锚点之间的隧道, 从而使得因为本地移动锚点上保存的 第一移动网络中的移动接入网关的地址不会被第二移动网络中的移动接入网关的地址 代替,移动节点通过第一移动网络中的移动接入网关发送的上行数据业务不会被本地移 动锚点丢失;并且本地移动锚点向移动节点发送的下行数据业务也不会被第二移动网络 中的移动接入网关丢失。
基于控制面与数据面分离的代理移动 IP系统架构如图 9, 图 9为本发明实施例的一种 基于控制面与数据面分离的代理移动 IP系统架构示意图。
如图 9所示, 在代理移动 IP系统中, MAG与 LMA分别具有各自的控制面地址和数据面 地址。 其中控制面地址用于 MAG与 LMA交互的注册、 更新、 注销等控制过程, 而数据面地 址是用于 MAG与 LMA之间的代理移动 IP隧道中转发丽的数据包。该数据面地址包含在为每 个丽建立的上下文数据区 (例如 BCE Binding Cache Entry绑定缓存区) 中。 上述 MAG上为每个丽建立的上下文数据区, 包括表 1中的以下选项(其他与本方案不 相关项未列出)
表 1
Figure imgf000015_0001
PMIP6隧道相关参数
LMA地址 当前 PMIP6隧道中, MAG发送数据的上行 LMA地址, MAG (用户面, 上行) 同时可以接收该地址的下行数据;
LMA隧道标识 隧道标识是一个可选项, 如 GRE Key。
(用户面, 上行) 当前 PMIP6隧道中, MAG发送数据的上行 LMA隧道标识,
MAG同时可以接收该隧道的下行数据;
LMA地址 当前 PMIP6隧道中, MAG接收该地址的下行数据; 在该 (用户面, 下行) 地址上可能发送或不发送上行数据。一般地,该地址与" LMA 地址(用户面, 上行) "一致, 在切换过程中, 可能出现 不一致的情况。
LMA隧道标识 隧道标识是一个可选项, 如 GRE Key。
(用户面, 下行) 当前 PMIP6隧道中, MAG接收该隧道标识对应的下行数 据; 在该隧道上可能发送或不发送上行数据。 一般地, 该 隧道标识与 "LMA隧道标识(用户面, 上行) "一致, 在切 换过程中, 可能出现不一致的情况。
MAG地址(用户面) 当前为丽服务的 MAG数据面地址
在代理移动 IPv6协议的实现中, 控制面地址也即是代理绑定更新(注册 /响应) 消 息的源地址。 而数据面地址则携带在隧道协商的移动选项。
同样参见图 8, 说明本发明中网络切换系统又一实施例。
本实施例中所称的网络切换系统是基于控制面(代理绑定注册过程)与数据面(隧 道)分离的代理移动 IP系统, 其采用注册过程与建立隧道过程分离的方式, 解决移动终 端在基于代理移动 IP协议的异质网络切换时存在的数据包丢失问题。
本实施例中将详细描述网络切换系统中移动终端 1, 原移动接入网关 20, 新移动接 入网关 21, 本地移动锚点 3的功能和作用;
当移动终端 1从原移动接入网关 20 (pMAG)切换到新移动接入网关 21 (nMAG)前, 移动终端 1的一个接口 IF1与 pMAG20仍旧保持通信, 而另一个接口 IF2连接到 nMAG21。
nMAG21先向 LMA3进行注册, nMAG21从移动终端 1的链路层接入或签约信息等得知移 动终端 1将从 IF1切换到 IF2,且在准备阶段,则仅向 LMA3发送代理绑定更新(PBU)消息, 进行注册; LMA3接受注册请求, 向 nMAG21回复绑定确认消息, 携带为移动终端 1分配家乡地址 前缀 HNP。 nMAG21向移动终端 1发送路由通告, 在移动终端 1的 IF2上发送家乡网络地址前 缀信息。
移动终端 1根据家乡网络地址前缀信息进行无线接入配置。 nMAG21在得知移动终端 1 的 IF2无线接入配置完成(通过链路层信息, 或者丽发送的路由请求消息, 或其他方式) 后, 向 LMA3发起 PBU的更新请求, 带有为移动终端服务的数据面地址选项, 以建立下行 隧道; LMA3接受 PBU的更新请求, 向 nMAG21回复绑定确认消息, 带有上行的数据面地址 选项。 LMA3与 nMAG21通过新的隧道转发移动终端 1的 IF2的数据业务。
实施上述的网络切换系统, 当移动节点从第一移动网络移动到第二移动网络时, 首 先从本地移动锚点获取移动节点的家乡网络地址前缀信息; 在移动节点完成接入层的配 置之后, 才建立与所述本地移动锚点之间的隧道, 从而使得因为本地移动锚点上保存的 第一移动网络中的移动接入网关的地址不会被第二移动网络中的移动接入网关的地址 代替,移动节点通过第一移动网络中的移动接入网关发送的上行数据业务不会被本地移 动锚点丢失; 并且本地移动锚点向移动节点发送的下行数据业务也不会被第二移动网络 中的移动接入网关丢失。
参见图 10, 为本发明实施例的一种移动接入网关的结构示意图。
本实施例中的移动接入网关, 包括:
网络地址获取模块 200, 当移动节点从第一移动网络移动到第二移动网络时, 从本 地移动锚点获取移动节点在第二移动网络中使用的家乡网络地址前缀信息;
隧道信息请求模块 201, 根据所述家乡网络地址前缀信息, 完成与所述移动节点之 间的接入层配置后, 向本地移动锚点发送建立隧道请求, 以建立与所述本地移动锚点之 间的隧道; 所述建立隧道请求中携带有与所述本地移动锚点交换的隧道信息, 所述隧道 信息包括隧道地址信息、 隧道类型信息;
数据转发模块 202, 用于通过与所述本地移动锚点之间建立的隧道, 向所述移动节 点转发数据。
实施上述的移动接入网关, 当移动节点从第一移动网络移动到第二移动网络时, 首 先从本地移动锚点获取移动节点的家乡网络地址前缀信息; 在移动节点完成接入层的配 置之后, 才建立与所述本地移动锚点之间的隧道, 从而使得因为本地移动锚点上保存的 第一移动网络中的移动接入网关的地址不会被第二移动网络中的移动接入网关的地址 代替,移动节点通过第一移动网络中的移动接入网关发送的上行数据业务不会被本地移 动锚点丢失; 并且本地移动锚点向移动节点发送的下行数据业务也不会被第二移动网络 中的移动接入网关丢失。
参见图 11为本发明实施例的另一种移动接入网关的结构示意图。
本实施例中的移动接入网关, 具有与图 11相同的网络地址获取模块 200、 隧道信息 请求模块 201、 数据转发模块 202, 本实施例中, 将进一步说明网络地址获取模块 200和 隧道信息请求模块 201,其中网络地址获取模块 200具体用于向本地移动锚点发送第一代 理绑定更新消息以从本地移动锚点获取移动节点的家乡网络地址前缀信息。需要说明的 是, 在某些实现中, 隧道信息是必须的, 则可以带有特定的隧道地址或隧道标识, 如空 隧道地址或隧道标识等; 以表示正在切换准备阶段, 暂不接收下行数据。
本地移动锚点接受 PBU请求, 创建新的绑定缓冲条目, 为移动终端 (IF2)分配家乡 网络地址前缀;
隧道信息请求模块 201具体用于向所述本地移动锚点发送第二代理绑定更新消息, 在所述第二代理绑定更新消息中携带有隧道信息, 以指示本地移动锚点, 所述第二移动 接入网关已处于切换就绪阶段, 准备接收下行数据。 所述隧道地址信息具体可以是数据 面地址; 需要说明的是, 隧道信息请求模块 201在发送第二代理绑定更新消息之前, 还 需要检测移动终端无线接入配置是否完成(如地址配置, 无线配置等)完成。 可行的检 测方式有, 检测移动终端是否发送链路层切换完成消息或者上行数据或者 IP层消息(路 由请求) 等。
本实施例中的移动接入网关还包括:
隧道标识发送模块 203, 用于根据第二代理绑定更新消息携带的隧道信息中的隧道 类型, 向本地移动锚点发送与隧道类型相应的隧道标识。 在第二代理绑定更新消息携带 的隧道信息中还包括隧道封装模式时, 则隧道标识发送模块 203向本地移动锚点发送与 隧道类型和隧道封装模式相应的隧道标识。
本实施例中的移动接入网关, 当移动节点从第一移动网络移动到第二移动网络时, 首先从本地移动锚点获取移动节点的家乡网络地址前缀信息; 在移动节点完成接入层的 配置之后, 才建立与所述本地移动锚点之间的隧道, 从而使得因为本地移动锚点上保存 的第一移动网络中的移动接入网关的地址不会被第二移动网络中的移动接入网关的地 址代替,移动节点通过第一移动网络中的移动接入网关发送的上行数据业务不会被本地 移动锚点丢失; 并且本地移动锚点向移动节点发送的下行数据业务也不会被第二移动网 络中的移动接入网关丢失。 参见图 12, 为本发明实施例的一种本地移动锚点的结构示意图。
本实施例中的本地移动锚点, 包括:
网络地址发送模块 30, 当移动节点从第一移动网络移动到第二移动网络时, 向所述 第二移动网络中的移动接入网关返回所述移动节点的家乡网络地址前缀信息;
建立隧道模块 31, 用于在接收到所述移动接入网关的建立隧道请求后, 建立与所述 移动接入网关之间的隧道; 所述建立隧道请求中携带有与所述本地移动锚点交换的隧道 信息, 所述隧道信息包括隧道地址信息、 隧道类型信息。
所述本地移动锚点还包括: 更新隧道模块, 用于当所述建立隧道请求中包含的隧道 类型和所述第二网络节点存储的隧道类型不同时, 所述第二网络节点根据配置的策略, 确定建立与所述第一网络节点之间的隧道。
本实施例中的本地移动锚点, 在接收到移动接入网关正处于准备切换阶段时, 不接 收下行数据的信息的通知时, 本地移动锚点只为移动终端分配家乡网络地址前缀信息, 并在移动终端完成无线接入配置后,本地移动锚点才向移动接入网关发送下行数据的信 息,使得因为本地移动锚点上保存原移动接入网关的地址不会在注册过程就被新移动接 入网关的地址代替,移动终端通过原移动接入网关发送的上行数据业务不会被本地移动 锚点丢失; 并且附着在新移动接入网关的移动终端无线接入配置完成之后, 再进行数据 传输, 所以本地移动锚点向移动终端发送的下行数据业务不会被新的移动接入网关丢 失。
上述移动节点、 移动接入网关、 本地移动锚点实现隧道协商和网络切换的具体流程 如上述网络切换方法和隧道协商方法实施例中的描述,其在网络切换系统中的功能和作 用如上述网络切换系统实施例中的描述, 不再赘述。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到本发明可借助软 件加必需的硬件平台的方式来实现,当然也可以全部通过硬件来实施。基于这样的理解, 本发明的技术方案对背景技术做出贡献的全部或者部分可以以软件产品的形式体现出 来, 该计算机软件产品可以存储在存储介质中, 如 R0M/RAM、 磁碟、 光盘等, 包括若干 指令用以使得一台计算机设备(可以是个人计算机, 服务器, 或者网络设备等)执行本 发明各个实施例或者实施例的某些部分所述的方法。
以上所揭露的仅为本发明一种较佳实施例而已, 当然不能以此来限定本发明之权利 范围, 因此依本发明权利要求所作的等同变化, 仍属本发明所涵盖的范围。

Claims

权利要求
1、 一种建立隧道的方法, 应用在代理移动 IP系统中, 其特征在于, 包括: 第一网络节点向第二网络节点发送建立隧道请求,所述建立隧道请求中携带有隧道 信息, 所述隧道信息包括隧道地址信息、 隧道类型信息;
所述第二网络节点根据所述建立隧道请求消息中携带的隧道信息,建立与所述第一 网络节点之间的隧道。
2、 如权利要求 1的建立隧道方法, 其特征在于, 建立隧道所述方法还包括: 当所述建立隧道请求中包含的隧道类型和所述第二网络节点存储的隧道类型不同 时, 所述第二网络节点根据配置的策略, 确定建立与所述第一网络节点之间的隧道。
3、 如权利要求 1或权利要求 2所述的建立隧道方法, 其特征在于, 当所述第一网络 节点为移动接入网关时, 所述第二网络节点为本地移动锚点; 或者, 当所述第一网络节 点为本地移动锚点时, 所述第二网络节点为移动接入网关。
4、 一种网络切换方法, 其特征在于, 包括:
当移动节点从第一移动网络移动到第二移动网络时,从本地移动锚点获取移动节点 的家乡网络地址前缀信息;
根据所述家乡网络地址前缀信息, 完成与所述移动节点之间的接入层配置后, 向本 地移动锚点发送建立隧道请求, 以建立与所述本地移动锚点之间的隧道; 所述建立隧道 请求中携带有与所述本地移动锚点交换的隧道信息, 所述隧道信息包括隧道地址信息、 隧道类型信息;
通过与所述本地移动锚点之间建立的隧道, 向所述移动节点转发数据。
5、 如权利要求 4所述的网络切换方法, 其特征在于, 所述从本地移动锚点获取移动 节点的家乡网络地址前缀信息具体包括:
所述第二移动网络中的移动接入网关向本地移动锚点发送第一代理绑定更新消息 以从本地移动锚点获取移动节点的家乡网络地址前缀信息,在该第一代理绑定更新消息 中未携带隧道信息或携带空值的隧道信息, 以指示本地移动锚点, 所述第二移动接入网 关正处于切换准备阶段, 不接收数据。
6、 如权利要求 4或 5所述的网络切换方法, 其特征在于, 所述向本地移动锚点发送 建立隧道请求, 包括: 第二移动网络中的移动接入网关向所述本地移动锚点发送第二代理绑定更新消息, 在所述第二代理绑定更新消息中携带有隧道信息, 以指示本地移动锚点, 所述移动接入 网关已处于切换就绪阶段, 准备接收数据。
7、 如权利要求 6所述的网络切换方法, 其特征在于, 所述隧道信息中还包括: 隧道 封装模式信息, 和 /或与所述隧道类型和所述隧道封装模式相对应的隧道标识信息。
8、 一种本地移动锚点, 其特征在于, 包括:
网络地址发送模块, 当移动节点从第一移动网络移动到第二移动网络时, 向所述第 二移动网络中的移动接入网关返回所述移动节点的家乡网络地址前缀信息;
建立隧道模块, 用于在接收到所述移动接入网关的建立隧道请求后, 建立与所述移 动接入网关之间的隧道; 所述建立隧道请求中携带有与所述本地移动锚点交换的隧道信 息, 所述隧道信息包括隧道地址信息、 隧道类型信息。
9、 如权利要求 8的本地移动锚点, 其特征在于, 所述本地移动锚点还包括: 更新隧道模块,用于当所述建立隧道请求中包含的隧道类型和所述第二网络节点存 储的隧道类型不同时, 所述第二网络节点根据配置的策略, 确定建立与所述第一网络节 点之间的隧道。
10、 一种移动接入网关, 其特征在于, 包括:
网络地址获取模块, 当移动节点从第一移动网络移动到第二移动网络时, 从本地移 动锚点获取移动节点的家乡网络地址前缀信息;
隧道信息请求模块, 根据所述家乡网络地址前缀信息, 完成与所述移动节点之间的 接入层配置后, 向本地移动锚点发送建立隧道请求, 以建立与所述本地移动锚点之间的 隧道; 所述建立隧道请求中携带有与所述本地移动锚点交换的隧道信息, 所述隧道信息 包括隧道地址信息、 隧道类型信息;
数据转发模块, 用于通过与所述本地移动锚点之间建立的隧道, 向所述移动节点转 发数据。
11、 如权利要求 10所述的移动接入网关, 其特征在于, 所述网络地址获取模块具体 用于向本地移动锚点发送第一代理绑定更新消息以从本地移动锚点获取移动节点的家 乡网络地址前缀信息,在该第一代理绑定更新消息中未携带隧道信息或携带空值的隧道 信息, 以指示本地移动锚点,所述第二移动接入网关正处于切换准备阶段,不接收数据。
12、 如权利要求 10或 11所述的移动接入网关, 其特征在于, 所述隧道信息请求模块 具体用于向所述本地移动锚点发送第二代理绑定更新消息,在所述第二代理绑定更新消 息中携带有隧道信息, 以指示本地移动锚点, 所述第二移动接入网关已处于切换就绪阶 段, 准备接收数据。
13、 如权利要求 11所述的移动接入网关, 其特征在于, 隧道信息中还包括: 隧道封 装模式信息, 和 /或与所述隧道类型和所述隧道封装模式相对应的隧道标识信息。
14、 一种网络切换系统, 其特征在于, 包括: 移动接入网关、 本地移动锚点; 所述移动接入网关, 用于当移动节点从第一移动网络移动到第二移动网络时, 从本 地移动锚点获取移动节点的家乡网络地址前缀信息; 并根据所述家乡网络地址前缀信 息, 完成与所述移动节点之间的接入层配置后, 向本地移动锚点发送建立隧道请求; 通 过与所述本地移动锚点之间建立的隧道, 向所述移动节点转发数据; 其中, 所述建立隧 道请求中携带有与所述本地移动锚点交换的隧道信息, 所述隧道信息包括隧道地址信 息、 隧道类型信息;
所述本地移动锚点,用于向所述第二移动网络中的移动接入网关返回所述移动节点 的家乡网络地址前缀信息; 在接收到所述移动接入网关的建立隧道请求后, 建立与所述 移动接入网关之间的隧道。
PCT/CN2009/075776 2008-12-24 2009-12-21 一种网络切换方法、装置及系统 WO2010072135A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200810220342 2008-12-24
CN200810220342.9 2008-12-24
CN2009101281980A CN101765092B (zh) 2008-12-24 2009-03-11 一种网络切换方法、装置及系统
CN200910128198.0 2009-03-11

Publications (1)

Publication Number Publication Date
WO2010072135A1 true WO2010072135A1 (zh) 2010-07-01

Family

ID=42286895

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/075776 WO2010072135A1 (zh) 2008-12-24 2009-12-21 一种网络切换方法、装置及系统

Country Status (2)

Country Link
CN (1) CN101765092B (zh)
WO (1) WO2010072135A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113905109A (zh) * 2021-12-08 2022-01-07 深圳竹云科技有限公司 零信任网络数据传输方法、装置、设备及计算机存储介质
CN115278793A (zh) * 2022-07-05 2022-11-01 李丽芳 一种用于5g设备的多网络切换方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8645531B2 (en) * 2011-03-31 2014-02-04 Alcatel Lucent Method and apparatus for home network access by a trusted monitoring agent
CN103516603B (zh) * 2012-06-15 2019-01-15 中兴通讯股份有限公司 一种路由优化方法、装置及系统
WO2014101181A1 (zh) * 2012-12-31 2014-07-03 华为技术有限公司 用户设备及异构网络切换的方法
CN103763145B (zh) * 2014-01-27 2019-12-13 上海斐讯数据通信技术有限公司 一种隧道代理方法
SG11201800098WA (en) * 2015-07-15 2018-02-27 Huawei Tech Co Ltd Ip address management method and apparatus, ip address anchor, and mobile node

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179457A (zh) * 2006-11-09 2008-05-14 华为技术有限公司 一种基于本地移动管理域中路由优化的切换方法
CN101237699A (zh) * 2008-02-29 2008-08-06 中兴通讯股份有限公司 无线网络节点与接入服务器之间建立多隧道的控制方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179457A (zh) * 2006-11-09 2008-05-14 华为技术有限公司 一种基于本地移动管理域中路由优化的切换方法
CN101237699A (zh) * 2008-02-29 2008-08-06 中兴通讯股份有限公司 无线网络节点与接入服务器之间建立多隧道的控制方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GUNDAVELLI, S. ET AL.: "Proxy Mobile IPv6. RFC5213.", IETF, August 2008 (2008-08-01), Retrieved from the Internet <URL:http://tools.ietf.org/search/rfc5213> *
ZORN, G. ET AL.: "RADIUS Attributes for Tunnel Protocol Support. RFC2868.", IETF, June 2000 (2000-06-01), Retrieved from the Internet <URL:http://www.ietf.org/rfc/rfc2868.txt> *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113905109A (zh) * 2021-12-08 2022-01-07 深圳竹云科技有限公司 零信任网络数据传输方法、装置、设备及计算机存储介质
CN115278793A (zh) * 2022-07-05 2022-11-01 李丽芳 一种用于5g设备的多网络切换方法

Also Published As

Publication number Publication date
CN101765092A (zh) 2010-06-30
CN101765092B (zh) 2011-07-20

Similar Documents

Publication Publication Date Title
JP5453430B2 (ja) マルチインタフェース通信環境におけるプロキシモバイルインターネットプロトコル(pmip)
US9750071B1 (en) Method and apparatus for supporting multiple connections over different types of access in 3GPP systems
US8144660B2 (en) Multimode terminal for supporting fast handover between heterogeneous networks
TWM294788U (en) Wireless communication system for implementing media independent handover between technologically diversified access networks
JP4990985B2 (ja) プロキシ・モバイルipルーティング
JP4968328B2 (ja) モバイルip通信システム、モバイルip通信装置およびモバイルip通信方法
JP2010539838A (ja) マルチアクセス環境におけるシステム間ハンドオフ
WO2010000174A1 (zh) 移动节点的注册、通信、切换方法及装置
WO2007006227A1 (fr) Procédé et système de négociation destinés à l’établissement de chemins de données d’interface
WO2011001594A1 (ja) リダイレクション方法、リダイレクションシステム、モバイルノード、ホームエージェント及び代理ノード
WO2010072135A1 (zh) 一种网络切换方法、装置及系统
KR20150074220A (ko) 고속 핸드오프 전이 동안 이동성 액세스 게이트웨이 간의 터널링을 위한 시스템 및 프로토콜들
WO2011085618A1 (zh) 一种终端切换的方法及相应的通信网络
KR20060042522A (ko) 이동 인터넷 프로토콜 통신 시스템에서 소스 노드의핸드오프에 따른 멀티캐스트 서비스 제공 방법
WO2009028885A2 (en) Method and system for managing mobility in a mobile communication system using proxy mobile internet protocol
WO2007131404A1 (fr) Méthode et dispositif de transfert rapide
JP5363590B2 (ja) 同時の端末アクセスのサポートのためのセッションの連続性
US7917142B2 (en) Comprehensive registration method for wireless communication system
US8768357B2 (en) Changes of forward-link and reverse-link serving access points
WO2013007133A1 (zh) 报文转发路径管理方法、系统及网元
JP5685161B2 (ja) ネットワークアーキテクチャ、ローカル・モビリティ・アンカー、及びモビリティ・アンカー・ゲートウェイ
KR101901109B1 (ko) 무선자원 효율성 증진을 통한 안정적인 트래픽 전송을 제공하는 하이브리드 융합 네트워크 관리 시스템 및 방법
WO2008089671A1 (fr) Procédé, système et terminal pour réduire le temps de transfert
Choi et al. Cost analysis of integrated HIP-PMIPv6 handoff scheme in multicasting-based mobile networks
WO2013064053A1 (zh) 一种流移动中的策略管理方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09834088

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09834088

Country of ref document: EP

Kind code of ref document: A1