|
(11) | EP 2 169 849 A1 |
| (12) | EUROPEAN PATENT APPLICATION |
| published in accordance with Art. 153(4) EPC |
|
|
|
|
|||||||||||||||||||||||
| (54) | ACCESS NETWORK SWITCHING METHOD, ANCHOR MANAGEMENT DEVICE, AND MOBILE ACCESSING DEVICE |
| (57) An access network handover method, an anchor management device, and a mobile access
device are disclosed. The method includes the following steps: when a User Equipment
(UE) moves from a first network based on a first mobility management protocol to a
second network based on a second mobility management protocol, an access Gateway (GW)
or a Mobility Management Entity (MME) obtains an anchor address corresponding to the
second mobility management protocol, where the anchor address corresponding to the
second mobility management protocol indicates an anchor device used by the UE in the
first network; and the access GW or MME uses the second mobility management protocol
to set up a connection from the access GW or the MME to the anchor device indicated
by the anchor address corresponding to the second mobility management protocol according
to the anchor address corresponding to the second mobility management protocol. |
Field of the Invention
[0001] The present invention relates to mobile communications, and in particular, to an access network handover method, an anchor management device, and a mobile access device.
Background of the Invention
[0002] Currently, the radio communication network defined by the 3rd Generation Partnership Project (3GPP) standardization organization is typically composed of a 3GPP Radio Access Network (RAN) and a 3GPP radio core network.
[0003] The 3GPP System Architecture Evolution (SAE) network supports the 3GPP access technology, the non-3GPP access technology, and mobility between heterogeneous access networks. In an SAE network, the Packet Data Network Gateway (PDN GW) allocates an IP address to a User Equipment (UE). To support mobility of the UE between heterogeneous RANs, the SAE network uses the PDN GW as an anchor device for handover between heterogeneous systems. A network element such as a Home Subscriber Sever (HSS) or an Authentication, Authorization and Accounting (AAA) server manages information about the anchor currently used by the UE.
[0004] When the UE is handed over from one access network to another, a Mobility Management Entity (MME) obtains the anchor currently used by the UE from the HSS or AAA server, and uses the anchor as a target anchor connected to the new data channel. In this way, as long as the UE uses the same anchor to access the data packet network before and after the handover, the same IP address is allocated, and the continuity of the data service is realized. Currently, the SAE network uses a Mobile IP (MIP) protocol to implement mobility between heterogeneous networks.
[0005] For example, the UE moves from an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) to a Wireless Local Area Network (WLAN). After the UE sets up a connection at the E-UTRAN successfully, the UE stores the Home Address (HA) of the used PDN GW, namely, the HA of the MIP protocol, into the HSS or AAA server. When the UE is handed over to a WLAN, a Proxy Mobility Agent (PMA) obtains the stored HA of the PDN GW from the HSS or AAA server, and sends a Proxy Mobile Internet Protocol (PMIP) registration request to the PDN GW to set up a PMIP tunnel with the PDN GW. In this way, the IP connection of the UE between the WLAN and the PDN GW is set up. Because the UE uses the same IP address to set up a PMIP tunnel with the PDN GW before and after the handover, the continuity of the data service is realized.
[0006] In the prior art described above, the same mobility management protocol, namely, Mobile Internet Protocol (MIP), is used for handover between heterogeneous access networks. If the 3GPP access technology supports a General Packet Radio Service (GPRS) Tunnel Protocol (GTP), the handover between heterogeneous access networks involves handover between different management protocols, for example, handover between a GTP protocol and a MIP protocol.
[0007] The GTP Control Plane (GTP-C) address of the PDN GW is stored in the HSS or AAA server if the GTP protocol is used for setting up a service connection. In this case, for the MIP protocol, the HA of the PDN GW is stored in the HSS or AAA server. The HA is a network address identical with the service address allocated to the UE, and is a user-plane address. The HA of the PDN GW and the GTP-C are generally two different addresses on the PDN GW.
[0008] In the process of implementing the present invention, the inventor finds at least the following defect in the prior art: The prior art is unable to realize continuity of the data service when the UE is handed over between networks of different mobility management protocols.
Summary of the Invention
[0009] Embodiments of the present invention provide an access network handover method, an anchor management device, and a mobile access device to maintain continuity of data services when a UE is handed over between access networks of different mobility management protocols.
[0010] An access network handover method provided in an embodiment of the present invention includes:
when a UE moves from a first network based on a first mobility management protocol to a second network based on a second mobility management protocol, by an access GW or an MME, obtaining an anchor address corresponding to the second mobility management protocol, where the anchor address corresponding to the second mobility management protocol indicates an anchor device used by the UE in the first network; and
using the second mobility management protocol to set up a connection from the access GW or the MME to the anchor device indicated by the anchor address corresponding to the second mobility management protocol according to the anchor address corresponding to the second mobility management protocol.
[0011] An anchor management device provided in an embodiment of the present invention includes:
a receiving unit, adapted to receive anchor addresses of an anchor device currently used by a UE, where the anchor addresses correspond to mobility management protocols;
a storing unit, adapted to: record anchor information of the anchor device, and update the anchor information according to the anchor addresses that are received by the receiving unit and correspond to the mobility management protocol, where the anchor information includes the anchor addresses of the anchor device and the anchor addresses correspond to multiple mobility management protocols;
a selecting unit, adapted to select an anchor address of the anchor device among the anchor addresses received by the receiving unit, where the selected anchor address corresponds to a mobility management protocol used by the network to which the UE is handed over; and
a sending unit, adapted to send the anchor address selected by the selecting unit.
[0012] A mobile access device provided in an embodiment of the present invention includes:
an obtaining unit, adapted to obtain anchor addresses of an anchor device currently used by a UE, where the anchor addresses correspond to mobility management protocols;
a selecting unit, adapted to select an anchor address of the anchor device among the anchor addresses obtained by the obtaining unit, where the selected anchor address corresponds to a mobility management protocol used by the network to which the UE is handed over; and
a connection setup unit, adapted to set up a connection by using the corresponding mobility management protocol according to the anchor address selected by the selecting unit.
[0013] An access network handover system provided in an embodiment of the present invention includes: a first network based on a first mobility management protocol, a second network based on a second mobility management protocol, an access GW connected to the first network, and an MME connected to the second network.
[0014] When a UE moves from the first network to the second network, the MME obtains the anchor address corresponding to the second mobility management protocol, and the anchor address corresponding to the second mobility management protocol indicates the anchor device used by the UE in the first network; moreover, the MME uses the second mobility management protocol to set up a connection from the MME to the anchor device indicated by the anchor address corresponding to the second mobility management protocol according to the anchor address corresponding to the second mobility management protocol.
[0015] When the UE moves from the second network to the first network, the access GW obtains the anchor address corresponding to the first mobility management protocol, and the anchor address corresponding to the first mobility management protocol indicates the anchor device used by the UE in the second network; moreover, the access GW uses the first mobility management protocol to set up a connection from the access GW to the anchor device indicated by the anchor address corresponding to the first mobility management protocol according to the anchor address corresponding to the first mobility management protocol.
[0016] Through the access network handover method, anchor management device, and mobile access device in the embodiments of the present invention, the anchor management device stores anchor addresses of the anchor device, and the anchor addresses correspond to multiple different mobility management protocols. When the UE is handed over from a network based on one mobility management protocol to a network based on another mobility management protocol, the anchor management device provides the UE with an anchor address of the anchor device, and this anchor address corresponds to another mobility management protocol. According to the anchor address, a connection from the UE to the access network is set up. Therefore, the continuity of the data service is still maintained when the UE is handed over between the access networks based on different mobility management protocols.
Brief Description of the Drawings
[0017]
FIG. 1 is a signaling flowchart of an access network handover method according to a first embodiment of the present invention;
FIG. 2 is a signaling flowchart of an access network handover method according to a second embodiment of the present invention; and
FIG. 3 shows a structure of a mobile network system according to an embodiment of the present invention.
Detailed Description of the Embodiments
[0018] To make the technical solution of the present invention clearer, the following describes the embodiments of the present invention in detail with reference to accompanying drawings.
[0019] FIG. 1 is a signaling flowchart of an access network handover method according to the first embodiment of the present invention. In this embodiment, a UE is handed over from a non-3GPP access network to a 3GPP access network. The process of handover between the access networks includes the following steps:
Step 101: The UE detects signals of the non-3GPP access network, and connects to the non-3GPP access network.
Step 102: The non-3GPP access GW discovers that the UE needs to access the SAE core network, and sends a UE access authentication request to the anchor management device HSS or AAA server. The non-3GPP access network obtains UE subscription information in the authentication process.
Step 103: After the HSS or AAA server performs the access authentication for the UE successfully, the access GW, in place of the UE, uses a PMIP protocol to send a connection request to the anchor device PDN GW.
[0020] In this embodiment, the non-3GPP access GW sends a Binding Update message to the PDN GW. As a packet data gateway of the UE, the PDN GW is also an anchor device that moves between the non-3GPP network and the 3GPP network, supports multiple mobility management protocols and has anchor addresses corresponding to different mobility management protocols. For example, the PDN GW has an anchor address corresponding to the PMIP protocol.
[0021] Step 104: After receiving the connection request, the PDN GW provides the HSS or AAA server with the anchor addresses of the PDN GW, where the anchor addresses correspond to multiple mobility management protocols. According to the anchor addresses provided by the PDN GW, the HSS or AAA server updates the stored anchor information, and returns a response to the PDN GW, indicating that the anchor information is updated.
[0022] In this embodiment, the HSS or AAA server is an anchor management device, and can store and maintain the anchor information of the anchor device. The anchor information includes the anchor addresses of the anchor device, and the anchor addresses correspond to different mobility management protocols. The HSS or AAA server can also provide the MME, access GW, or UE with the anchor addresses of the anchor device currently used by the UE. The anchor addresses correspond to multiple mobility management protocols.
[0024] In this embodiment, the PDN GW returns a Binding Ack (binding acknowledgement) message to the access GW according to the Binding Update message sent by the access GW through a PMIP protocol.
[0025] Steps 101-105 above constitute a process that the UE accesses an SAE core network through a non-3GPP access network based on a PMIP protocol.
[0026] When the UE moves to a radio network covered by a 3GPP E-UTRAN, the signals of the non-3GPP access network in the current location are deteriorated, and the signals of the E-UTRAN are enhanced, and therefore, the UE needs to be handed over to the E-UTRAN. The 3GPP E-UTRAN uses GTP as a mobility management protocol.
[0029] Step 108: The MME sends a UE access authentication request to the HSS or AAA server. The HSS or AAA server performs access authentication for the UE, and returns an authentication response to the MME.
[0030] Step 109: The MME sends a location update request to the HSS or AAA server, and registers the MME address with the HSS or AAA server. The HSS or AAA server delivers the UE subscription data to the MME, and sends the anchor address in the stored anchor information to the MME, where the anchor address corresponds to the GTP protocol.
[0031] Because the HSS or AAA server serves as an anchor management device which stores and maintains the anchor addresses corresponding to different mobility management protocols, the HSS or AAA server can send the stored anchor address corresponding to the GTP protocol to the MME.
[0032] The HSS or AAA server may provide multiple anchor addresses corresponding to multiple mobility management protocols (including the GTP mobility management protocol) for the MME, or provide only the anchor address corresponding to the GTP mobility management protocol (namely, a GTP-C address) for the MME.
[0033] Step 110: The MME selects a serving Gateway (GW) that supports the GTP protocol, sends a Create Bearer Request to the serving GW, and provides the anchor address corresponding to the GTP protocol for the serving GW.
[0034] If the HSS or AAA server provides only the anchor address corresponding to the GTP mobility management protocol for the MME, the MME provides only the anchor address corresponding to the GTP mobility management protocol (namely, a GTP-C address) for the serving GW.
[0035] If the HSS or AAA server provides multiple anchor addresses corresponding to multiple mobility management protocols (including the GTP mobility management protocol) for the MME, the MME may provide multiple anchor addresses corresponding to different mobility management protocols (including the GTP mobility management protocol) for the serving GW, or provide only the anchor address corresponding to the GTP mobility management protocol (namely, a GTP-C address) for the serving GW.
[0036] Step 111: The serving GW forwards the Create Bearer Request to the PDN GW according to the anchor address corresponding to the GTP protocol.
[0037] If the MME provides only the anchor address corresponding to the GTP mobility management protocol for the serving GW, the serving GW forwards the Create Bearer Request to the PDN GW according to the anchor address corresponding to the GTP mobility management protocol and provided by the MME.
[0038] If the MME provides multiple anchor addresses corresponding to multiple mobility management protocols (including the GTP mobility management protocol) for the serving GW, because the protocol supported by the serving GW is the GTP protocol, the serving GW selects the anchor address corresponding to the GTP mobility management protocol, and forwards the Create Bearer Request to the PDN GW.
[0039] Step 112: After receiving the Create Bearer Request, the PDN GW provides the anchor addresses of the anchor device currently used by the UE, where the anchor addresses correspond to multiple mobility management protocols; and the HSS or AAA server updates the stored anchor information of the anchor device.
[0040] Step 113: The PDN GW returns a Create Bearer Response to the serving GW. The message carries the anchor addresses of the anchor device currently used by the UE.
[0041] Step 114: The serving GW forwards the Create Bearer Response to the MME. The message carries the anchor addresses of the anchor device currently used by the UE.
[0042] Step 115: After receiving the Create Bearer Response, the MME sends the anchor addresses of the anchor device currently used by the UE to the HSS or AAA server. The HSS or AAA server updates the stored anchor information of the anchor device, and returns a response to the PDN GW, indicating that the anchor information is updated.
[0046] The anchor management device may obtain and update the anchor addresses corresponding to multiple mobility management protocols in this way: When the UE initiates network connection setup, the anchor device, MME or UE provides the anchor addresses of the anchor device currently used by the UE for the anchor management device, where the anchor addresses correspond to multiple mobility management protocols.
[0047] For example, in step 104, after the UE is authenticated for accessing the non-3GPP network, the anchor device PDN GW sends the anchor addresses of the anchor device currently used by the UE to the anchor management device HSS or AAA server for updating, where the anchor addresses correspond to multiple mobility management protocols.
[0048] In step 112, when the UE is handed over to the 3GPP network, in the process of setting up a bearer, the anchor device PDN GW sends the anchor addresses of the anchor device currently used by the UE to the anchor management device HSS or AAA server for updating, where the anchor addresses correspond to multiple mobility management protocols.
[0049] In step 115, when the UE is handed over to the 3GPP network, after the Create Bearer Request is sent, the MME sends the anchor addresses of the anchor device currently used by the UE to the anchor management device HSS or AAA server for updating, where the anchor addresses correspond to multiple mobility management protocols.
[0050] Through any one of step 104, step 112, and step 115 or any combination thereof, the anchor addresses (corresponding to multiple mobility management protocols) of the anchor device currently used by the UE may be provided for the anchor management device.
[0051] The anchor address is identifier information that can address the anchor, and may be an IP address or a domain name of the anchor.
[0052] When the anchor address is the IP address of the anchor device, the anchor address corresponding to a mobility management protocol may be an IP address and the corresponding protocol information, for example, GTP-IP1; the anchor addresses corresponding to multiple mobility management protocols may be mapping relations from multiple IP addresses to different mobility management protocols, for example, GTP-IP1, and PMIP-IP2; the anchor addresses corresponding to multiple mobility management protocols may be a mapping relation from one IP address to different mobility management protocols, for example, GTP-IP1, and PMIP-IP1.
[0053] When the anchor address is the domain name of the anchor device, the anchor address corresponding to a mobility management protocol may be a domain name and the corresponding protocol information such as GTP-sina.com, or a domain name that includes the protocol information such as sina.GTP.com; the anchor addresses corresponding to multiple mobility management protocols may be multiple domain names and the corresponding protocol information (for example, GTP-domain name 1, and PMIP-domain name 2), or multiple domain names that include diversified protocol information (for example, sina.GTP.com, and sina.PMIP.com), or domain names that include no protocol information (for example, sina.com). The protocol information needs to be added by the network element that selects the protocol (namely, the MME, access GW, or serving GW). For example, if the MME selects a GTP protocol, the domain name constructed at the time of resolving the domain name is sina.GTP.com.
[0054] In step 109, when the anchor addresses obtained by the MME, access GW, or serving GW correspond to multiple mobility management protocols, the MME, access GW, or serving GW may select a mobility management protocol according to their own configuration or policy, and use the anchor address corresponding to the selected mobility management protocol to set up a connection to the anchor device indicated by the anchor address, as detailed below:
[0055] When the anchor addresses corresponding to multiple mobility management protocols are multiple anchor IP addresses corresponding to multiple mobility management protocols, the MME, access GW or serving GW selects a mobility management protocol according to their own configuration or policy, uses the anchor IP address corresponding to the selected mobility management protocol as an IP address of the target anchor device, and sets up a connection to the anchor device indicated by the IP address.
[0056] When the anchor addresses corresponding to multiple mobility management protocols are anchor domain names corresponding to multiple mobility management protocols, the MME, access GW or serving GW may select a mobility management protocol according to their own configuration or policy, use the anchor domain name corresponding to the selected mobility management protocol (including the anchor domain name corresponding to the mobility management protocol and constructed in foregoing mode), obtain the anchor IP address through a domain name resolution service, use the anchor IP address as an IP address of the target anchor device, and set up a connection to the anchor device indicated by the IP address.
[0057] The domain name resolution service may be provided by the MME, access GW, or serving GW, or by a third-party Domain Name Server (DNS). FIG. 2 is a signaling flowchart of an access network handover method in the second embodiment of the present invention. In this embodiment, the UE is handed over from a 3GPP access network to a non-3GPP access network. The process of handover between the access networks includes the following steps:
Step 201: The UE sends an Attach Request to the NodeB of the 3GPP access network.
[0058] In this embodiment, the 3GPP access network is an E-UTRAN. The E-UTRAN uses GTP as a mobility management protocol.
[0060] Step 203: The MME sends a UE access authentication request to the HSS or AAA server. The HSS or AAA server performs access authentication for the UE, and returns an authentication response to the MME.
[0061] Step 204: The MME sends a location update request to the HSS or AAA server, and registers the MME address with the HSS or AAA server. The HSS or AAA server delivers the UE subscription data to the MME, and sends the stored anchor address corresponding to the GTP protocol to the MME.
[0062] In this embodiment, the HSS or AAA server is an anchor management device, and can store and maintain the anchor information of the anchor device. The anchor information includes the anchor addresses of the anchor device, and the anchor addresses correspond to different mobility management protocols. The HSS or AAA server can also provide the MME, access GW, or UE with the anchor addresses of the anchor device currently used by the UE. The anchor addresses correspond to multiple mobility management protocols.
[0063] The HSS or AAA server may provide multiple anchor addresses corresponding to multiple mobility management protocols (including the GTP mobility management protocol) for the MME, or provide only the anchor address corresponding to the GTP mobility management protocol (namely, a GTP-C address) for the MME. If the UE provides no anchor address when accessing the HSS or AAA server for the first time, the MME may select an anchor according to other information (such as an Access Point Name, APN) or policies (such as support of the GTP protocol).
[0064] Step 205: The MME selects a serving GW that supports the GTP protocol, sends a Create Bearer Request to the serving GW, and provides the anchor address corresponding to the GTP protocol for the serving GW, where the anchor address is allocated by the PDN GW.
[0065] If the HSS or AAA server provides only the anchor address corresponding to the GTP mobility management protocol for the MME, the MME provides only the anchor address corresponding to the GTP mobility management protocol (namely, a GTP-C address) for the serving GW.
[0066] If the HSS or AAA server provides multiple anchor addresses corresponding to multiple mobility management protocols (including the GTP mobility management protocol) for the MME, the MME may provide multiple anchor addresses corresponding to different mobility management protocols (including the GTP mobility management protocol) for the serving GW, or provide only the anchor address corresponding to the GTP mobility management protocol (namely, a GTP-C address) for the serving GW.
[0067] Step 206: The serving GW forwards the Create Bearer Request to the PDN GW according to the anchor address corresponding to the GTP protocol.
[0068] If the MME provides only the anchor address corresponding to the GTP mobility management protocol for the serving GW, the serving GW forwards the Create Bearer Request to the PDN GW according to the anchor address corresponding to the GTP mobility management protocol and provided by the MME.
[0069] If the MME provides multiple anchor addresses corresponding to multiple mobility management protocols (including the GTP mobility management protocol) for the serving GW, because the protocol supported by the serving GW is the GTP protocol, the serving GW selects the anchor address corresponding to the GTP mobility management protocol, and forwards the Create Bearer Request to the PDN GW.
[0070] Step 207: After receiving the Create Bearer Request, the PDN GW provides the anchor addresses of the anchor device currently used by the UE for the HSS or AAA server, where the anchor addresses correspond to multiple mobility management protocols; and the HSS or AAA server updates the stored anchor information of the anchor device.
[0071] Step 208: The PDN GW returns a Create Bearer Response to the serving GW. The message carries the anchor addresses of the anchor device currently used by the UE.
[0072] Step 209: The serving GW forwards the Create Bearer Response to the MME. The message carries the anchor addresses of the anchor device currently used by the UE.
[0073] Step 210: After receiving the Create Bearer Response, the MME forwards the anchor addresses of the anchor device currently used by the UE to the HSS or AAA server. The HSS or AAA server updates the stored anchor information of the anchor device, and returns a response to the PDN GW, indicating that the anchor information is updated.
[0076] Step 213: The NodeB of the 3GPP access network returns an Attach Complete response to the MME.
[0077] Steps 201-213 above constitute a process of the UE accessing an SAE core network through a 3GPP access network based on a GTP protocol.
[0078] When the UE moves to a radio network covered by a non-3GPP E-UTRAN, the signals of the E-UTRAN in the current location are deteriorated, and the signals of the non-3GPP access network are enhanced, and therefore, the UE needs to be handed over to the non-3GPP access network. The non-3GPP access network uses PMIP as a mobility management protocol.
[0080] Step 215: The non-3GPP access network discovers that the UE needs to access the SAE core network, and sends a UE access authentication request to the HSS or AAA server. The non-3GPP access network obtains the UE subscription information in the authentication process. After performing access authentication for the UE successfully, the HSS or AAA server provides the anchor address (corresponding to the PMIP protocol) of the anchor device currently used by the UE for the access GW.
[0081] Step 216: The access GW, in place of the UE, uses the PMIP protocol to send a connection request to the PDN GW according to the anchor address corresponding to the PMIP protocol.
[0082] In this embodiment, the access GW sends a Binding Update message to the PDN GW. As a packet data gateway of the UE, the PDN GW is also an anchor device that moves between the non-3GPP network and the 3GPP network, supports multiple mobility management protocols and has anchor addresses corresponding to different mobility management protocols. For example, the PDN GW has an anchor address corresponding to the PMIP protocol.
[0083] Step 217: After receiving the connection request, the PDN GW provides the HSS or AAA server with the anchor addresses of the anchor device currently used by the UE, where the anchor addresses correspond to multiple mobility management protocols. According to the anchor addresses provided by the PDN GW, the HSS or AAA server updates the stored anchor information, and returns a response to the PDN GW, indicating that the anchor information is updated.
[0086] The anchor management device may obtain and update the anchor addresses corresponding to multiple mobility management protocols in this way: When the UE initiates network connection setup, the anchor device, MME or UE provides the anchor addresses of the anchor device currently used by the UE for the anchor management device, where the anchor addresses correspond to multiple mobility management protocols.
[0087] For example, in step 207, when the UE sends a Create Bearer Request in the 3GPP network, the anchor device PDN GW sends the anchor addresses of the anchor device currently used by the UE to the anchor management device HSS or AAA server for updating, where the anchor addresses correspond to multiple mobility management protocols.
[0088] In step 210, when the UE sends a Create Bearer Request in the 3GPP network, the MME sends the anchor addresses of the anchor device currently used by the UE to the anchor management device HSS or AAA server for updating, where the anchor addresses correspond to multiple mobility management protocols.
[0089] In step 217, after the UE is handed over to a non-3GPP network and is authenticated for accessing the non-3GPP network, the anchor device PDN GW sends the anchor addresses of the anchor device currently used by the UE to the anchor management device HSS or AAA server for updating, where the anchor addresses correspond to multiple mobility management protocols.
[0090] Through any one of step 207, step 210, and step 217 or any combination thereof, the anchor addresses (corresponding to multiple mobility management protocols) of the anchor device currently used by the UE may be provided for the anchor management device.
[0091] Another access network handover method is provided in an embodiment of the present invention. In the process of handover between access networks, an IP address is used as the anchor IP address of the mobility management protocol. The anchor device is on the interface corresponding to the IP address, monitors receiving of signaling of different mobility management protocols, and forwards the intercepted signaling to the physical mobility protocol processing module.
[0092] For example, the anchor device supports both GTP and MIP as a mobility management protocol, and uses an HA IP address as the anchor IP address.
[0093] After the UE uses the MIP protocol to set up a MIP connection successfully, the HA IP address is registered with the anchor management device, which is the same as a general MIP protocol processing process. When the UE moves to a network which uses GTP as a mobility management protocol, because the anchor IP address is an HA IP address which is different from the GTP-C address, the following actions are necessary: monitoring the User Datagram Protocol (UDP) port on the anchor IP address, filtering the signaling packets of the GTP-C, and forwarding the obtained signaling packets to the GTP protocol processing module.
[0094] In another example, the anchor device supports both GTP and MIP as a mobility management protocol, and uses a GTP-C IP address as the anchor IP address.
[0095] When the UE uses MIP as a mobility management protocol, because the GTP-C IP address is not an HA IP address, the following actions are necessary: monitoring on the GTP-C IP address to check whether any MIP registration message exists (through the UDP port in the case of IPv4, or through the IP mobile extension header in the case of IPv6), resolve the Home Address (HoA) of the packet or extend the carried information about the external network to be accessed, and forward the MIP packet to the corresponding HA. The address of the UE at one side of the tunnel from the user-plane UE to the HA (namely, the real HA address) may be carried in a MIP response and returned to the device at the other side of the MIP tunnel. When the UE moves to a network that uses GTP as a mobility management protocol, the control-plane anchor IP address is the GTP-C address, and the processing is the same as general GTP protocol processing.
[0096] The anchor address is identifier information that can address the anchor, and may be an IP address or a domain name of the anchor. The processing is almost the same as that of the first embodiment above, and is not described further.
[0097] Those skilled in the art are aware that all or part of the steps of the foregoing embodiments may be implemented by hardware instructed by a program. The program may be stored in a computer-readable storage medium. The storage medium may be a Read-Only Memory (ROM)/Random Access Memory (RAM), a magnetic disk, or a Compact Disk (CD).
[0098] FIG. 3 shows a structure of a mobile network system according to an embodiment of the present invention.
[0099] As shown in FIG. 3, the mobile network system includes a UE 10, a non-3GPP access GW 20, a 3GPP access network NodeB 30, an anchor device 40, an anchor management device 50, an MME 60, and a serving GW 70. The anchor device may be a PDN GW, and the anchor management device may be an HSS or an AAA server.
[0101] The specific process of the UE 10 accessing the non-3GPP network is as follows:
The UE 10 sends a UE access authentication request to the anchor management device 50 through the non-3GPP access GW 20. The anchor management device 50 performs access authentication for the UE 10.
[0102] After the access authentication, through the non-3GPP access GW 20, the UE 10 uses a MIP protocol to send a connection request to the anchor device 40. After receiving the connection request, the anchor device 40 provides the anchor management device 50 with the anchor address corresponding to the MIP protocol, and returns a connection response to the UE 10. The UE accesses the non-3GPP network successfully. According to the anchor address provided by the anchor device 40, the anchor management device 50 updates the stored anchor information. The anchor information includes at least one anchor address (corresponding to the mobility management protocol) of the anchor device.
[0103] The specific process of handover of the UE 10 to a 3GPP network is as follows:
The UE 10 sends an Attach Request to the 3GPP network NodeB 30. The 3GPP network NodeB 30 forwards the Attach Request to the MME 60, and the MME 60 sends a request for authenticating the UE 10 to the anchor management device 50.
[0104] After receiving the access authentication request, the anchor management device 50 sends the anchor address corresponding to the GTP protocol to the MME 60. According to the anchor address corresponding to the GTP protocol, the MME 60 sends a GTP-based Create Bearer Request to the anchor device 40 through the serving GW 70. After receiving the Create Bearer Request, the anchor device 40 provides the anchor management device 50 with the anchor address corresponding to the GTP protocol, and returns a Create Bearer Response to the MME 60. The UE 10 is attached to the 3GPP network successfully.
[0105] The anchor management device includes:
a receiving unit, adapted to receive anchor addresses of the anchor device currently used by the UE, where the anchor addresses correspond to mobility management protocols;
a storing unit, adapted to: store anchor information of the anchor device, and update the anchor information according to the anchor addresses that are received by the receiving unit and correspond to the mobility management protocols, where the anchor information includes at least one anchor address of the anchor device and the anchor address corresponds to at least one mobility management protocol;
a selecting unit, adapted to select an anchor address of the anchor device among the anchor addresses obtained by the receiving unit, where the selected anchor address corresponds to a mobility management protocol used by the network to which the UE is handed over; and
a sending unit, adapted to send the anchor address selected by the selecting unit to the access GW or MME.
[0106] The MME, access GW or serving GW is a mobile access device, and includes:
an obtaining unit, adapted to obtain anchor addresses of the anchor device currently used by the UE, where the anchor addresses correspond to mobility management protocols;
a selecting unit, adapted to select an anchor address of the anchor device among the anchor addresses obtained by the obtaining unit, where the selected anchor address corresponds to a mobility management protocol used by the network to which the UE is handed over; and
a connection setup unit, adapted to set up a connection by using the corresponding mobility management protocol according to the anchor address selected by the selecting unit.
[0107] The anchor address is identifier information that can address the anchor, and may be an IP address or a domain name of the anchor. The processing is almost the same as that of the first embodiment above, and is not described further.
[0108] Through the access network handover method, anchor management device, and mobile access device in the embodiments of the present invention, the anchor management device stores anchor addresses of the anchor device, and the anchor addresses correspond to multiple different mobility management protocols. When the UE is handed over from a network based on one mobility management protocol to a network based on another mobility management protocol, the anchor management device provides the UE with an anchor address of the anchor device, and this anchor address corresponds to another mobility management protocol. According to the anchor address, a connection from the UE to the access network is set up. Therefore, the continuity of the data service is still maintained when the UE is handed over between the access networks based on different mobility management protocols.
[0109] Detailed above are an access network handover method, an anchor management device, and a mobile access device under the present invention. Although the invention is described through several exemplary embodiments, the invention is not limited to such embodiments. It is apparent that those skilled in the art can make modifications and variations to the invention without departing from the scope of the invention. The invention is intended to cover the modifications and variations provided that they fall in the scope of protection defined by the following claims or their equivalents.
when a User Equipment (UE) moves from a first network based on a first mobility management protocol to a second network based on a second mobility management protocol, by an access Gateway (GW) or a Mobility Management Entity (MME), obtaining an anchor address corresponding to the second mobility management protocol, wherein the anchor address corresponding to the second mobility management protocol indicates an anchor device used by the UE in the first network; and
using the second mobility management protocol to set up a connection from the access GW or the MME to the anchor device indicated by the anchor address corresponding to the second mobility management protocol according to the anchor address corresponding to the second mobility management protocol.
the access GW or the MME obtains the anchor address corresponding to the second mobility management protocol from an anchor management device.
by the anchor device, the MME or the UE, providing an anchor management device with anchor addresses of the anchor device, wherein the anchor addresses correspond to mobility management protocols and comprise the anchor address corresponding to the second mobility management protocol.
providing, by the anchor device, anchor addresses of the anchor device currently used by the UE for the anchor management device after access authentication is performed for the UE, wherein the anchor addresses correspond to mobility management protocols; and
storing, by the anchor management device, the anchor addresses corresponding to the mobility management protocols from the anchor device.
providing, by the anchor device, anchor addresses of the anchor device currently used by the UE for the anchor management device in a process of setting up a bearer, wherein the anchor addresses correspond to mobility management protocols; and
storing, by the anchor management device, the anchor addresses corresponding to the mobility management protocols from the anchor device.
providing, by the MME, anchor addresses of the anchor device currently used by the UE for the anchor management device in a process of setting up a bearer, wherein the anchor addresses correspond to mobility management protocols;
and
storing, by the anchor management device, the anchor addresses corresponding to the mobility management protocols from the MME.
the anchor address provided by the MME for the anchor management device and corresponding to the second mobility management protocol is provided by the anchor device.
each of the anchor addresses corresponding to the mobility management protocols is an anchor IP address corresponding to a mobility management protocol or an anchor domain name corresponding to a mobility management protocol.
the anchor domain name corresponding to the mobility management protocol comprises corresponding mobility management protocol information.
the anchor addresses corresponding to the mobility management protocols are the anchor IP addresses corresponding to multiple mobility management protocols; and
the step of setting up the connection from the access GW or the MME to the anchor device indicated by the anchor address corresponding to the second mobility management protocol comprises:
by the MME or the access GW, selecting a mobility management protocol as the second mobility management protocol according to their own configuration or policy, using the anchor IP address corresponding to the second mobility management protocol as an IP address of a target anchor device, and setting up the connection to the anchor device indicated by the IP address.
the anchor addresses corresponding to the mobility management protocols are the anchor domain names corresponding to multiple mobility management protocols;
the step of setting up the connection from the access GW or the MME to the anchor device indicated by the anchor address corresponding to the second mobility management protocol comprises:
by the MME or the access GW, selecting a mobility management protocol as the second mobility management protocol according to their own configuration or policy, resolving the anchor domain name corresponding to the second mobility management protocol to obtain an anchor IP address, using the anchor IP address as an IP address of a target anchor device, and setting up the connection to the anchor device indicated by the IP address.
when the anchor domain name corresponding to the second mobility management protocol does not comprise information about the second mobility management protocol, the step of resolving the anchor domain name corresponding to the second mobility management protocol to obtain the anchor IP address comprises:
adding the information about the second mobility management protocol to the anchor domain name corresponding to the second mobility management protocol; and
resolving the anchor domain name that comprises the information about the second mobility management protocol to obtain the anchor IP address.
a receiving unit, adapted to receive anchor addresses of an anchor device currently used by a User Equipment (UE), wherein the anchor addresses correspond to mobility management protocols;
a storing unit, adapted to: record anchor information of the anchor device, and update the anchor information according to the anchor addresses that are received by the receiving unit and correspond to the mobility management protocols, wherein the anchor information carries the anchor addresses of the anchor device and the anchor addresses correspond to multiple mobility management protocols; a selecting unit, adapted to select an anchor address of the anchor device among the anchor addresses received by the receiving unit, wherein the selected anchor address corresponds to a mobility management protocol used by a network to which the UE is handed over; and
a sending unit, adapted to send the anchor address selected by the selecting unit.
the anchor management device is a Home Subscriber Server (HSS) or an Authentication, Authorization and Accounting (AAA) server.
an obtaining unit, adapted to obtain anchor addresses of an anchor device currently used by a User Equipment (UE), wherein the anchor addresses correspond to mobility management protocols;
a selecting unit, adapted to select an anchor address of the anchor device among the anchor addresses obtained by the obtaining unit, wherein the selected anchor address corresponds to a mobility management protocol used by a network to which the UE is handed over; and
a connection setup unit, adapted to set up a connection by using the corresponding mobility management protocol according to the anchor address selected by the selecting unit.
the mobile access device is a Mobility Management Entity (MME), an access Gateway (GW), or a serving GW.
when a User Equipment (UE) moves from the first network to the second network, the MME obtains an anchor address corresponding to the second mobility management protocol, and the anchor address corresponding to the second mobility management protocol indicates an anchor device used by the UE in the first network; and the MME uses the second mobility management protocol to set up a connection from the MME to the anchor device indicated by the anchor address corresponding to the second mobility management protocol according to the anchor address corresponding to the second mobility management protocol; and
when the UE moves from the second network to the first network, the access GW obtains an anchor address corresponding to the first mobility management protocol, and the anchor address corresponding to the first mobility management protocol indicates an anchor device used by the UE in the second network; and the access GW uses the first mobility management protocol to set up a connection from the access GW to the anchor device indicated by the anchor address corresponding to the first mobility management protocol according to the anchor address corresponding to the first mobility management protocol.
the anchor management device is adapted to receive and store anchor addresses of the anchor device currently used by the UE, wherein the anchor addresses correspond to mobility management protocols;the access GW obtains the anchor address corresponding to the second mobility management protocol from the anchor management device; and
the MME obtains the anchor address corresponding to the second mobility management protocol from the anchor management device.