WO2012130018A1

WO2012130018A1 - Method and system for ip offload connection mobility support

Info

Publication number: WO2012130018A1
Application number: PCT/CN2012/071945
Authority: WO
Inventors: 霍玉臻; 周娜; 王静; 梁爽
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-28
Filing date: 2012-03-05
Publication date: 2012-10-04
Also published as: CN102711079A; CN102711079B

Abstract

Disclosed is a method for Internet Protocol (IP) offload connection mobility support, the method comprises: when a terminal moves, a wireless side network element currently serving the terminal judges the IP offload connection mobility of the terminal according to the obtained mobility determination information, maintaining the IP offload connection of the terminal when determining that the IP offload connection of the terminal supports mobility, and releasing the IP offload connection of the terminal when determining that the IP offload connection does not support mobility. Also disclosed is a system for IP offloading connection mobility support. By using the method and system of the present invention, the frequency of interruption of the IP offload connection due to terminal movement is reduced, thus improving user experience.

Description

Method and system for IP shunt connection mobility support

The present invention relates to an Internet Protocol (IP) offloading technology, and more particularly to a method and system for IP offload mobility support. Background technique

The 3rd Generation Partnership Project (EPS) evolved packet system (EPS, Evolved Packet System) by the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Mobile Management Entity (MME, Mobility Management Entity), Serving Gateway (SGW, Serving Gateway), Packet Data Network Gate (PGW, Packet Data Network GateWay), Home Subscriber Server (HSS), 3GPP GPP Authentication Authorization The AAA (Authentication, Authorization and Accounting), Policy and Charging Rules Function (PCRF) entity, and other supporting nodes.

In the existing EPS system architecture, the MME is responsible for the control layer, such as mobility management, non-access stratum signaling processing, and user mobility management context management; the access gateway includes: SGW and PGW; wherein, SGW For the access gateway device connected to the E-UTRAN, it is responsible for forwarding data between the E-UTRAN and the PGW, and is responsible for saving the paging waiting data; the PGW is an EPS and a packet data network (PDN, Packet Data Network) The border gateway is responsible for accessing the PDN and forwarding data between the EPS and the PDN. The authentication authorization server includes: an HSS, and a 3GPP AAA server; the PCRF entity is a policy and charging rule function entity, and receives the interface and the IP through the Rx. The service network is connected to obtain service information. In addition, the PCRF entity is also connected to the gateway device in the network through the Gx/Gxa/Gxc interface, and is responsible for initiating the establishment of the IP bearer. Guarantee the quality of service (QoS) of service data, and perform charging control. As a small, low-power base station, the home base station can be deployed in indoor places such as homes or offices. The home base station has the advantages of affordable, convenient, low-power output, and plug-and-play. Its main functions are: Higher service rates and lower costs for using high-rate services, while at the same time making up for the lack of coverage of existing distributed cellular wireless communication systems.

In the actual application process, the home base station can be directly connected to the core network, as shown in FIG. 1; in addition, the home base station can also access the core network through the home base station gateway, as shown in FIG. 2 . The main functions of the home base station gateway include: verifying the security of the home base station, processing the registration of the home base station, performing operation and maintenance management on the home base station, configuring and controlling the home base station according to the operator's requirements, and managing the core network and the home base station. data. In FIG. 1 and FIG. 2, the core network gateway may specifically be an SGW, a PGW, a Serving General Packet Radio Service Support Node (SGSN), or a Gateway General Packet Radio Service Support Node (GGSN). . The local gateway may be a local SGW (L-SGW, Local SGW), a local PGW (L-PGW, Local PGW), a virtual SGW (V-SGW, Virtual SGW), a virtual PGW (V-PGW, Virtual PSGW), and a local GGSN (L-GGSN, Local GGSN), external local gateway (L-GW, Local GW), or data offloading functional entity. The local gateway can be set up with the home base station, or can be set up with the home base station gateway, or can be set near the wireless side network element or the home base station gateway, that is, an external mode is adopted. The purpose of setting up the local gateway is to implement the IP offload function. In other words, it is to implement local access to other IP devices in the home network, IP devices in the enterprise network, and the Internet. The IP offload function includes: Access (LIPA, Local IP Access) and Selective IP Traffic Offload (SIPTO).

In order to achieve local access of the terminal to other IP devices and the Internet of the home network, two connections can be established. The first one is an IP connection data path, which can directly access the Internet, namely: Internet local IP access connection; IP offloads the data path, which is directly accessible Other IP devices on the home network, namely: Home network local IP access connection.

FIG. 3a and FIG. 3b are schematic diagrams of the IP offloading data of the related art wireless communication system. As shown in FIG. 3a and FIG. 3b, for a user supporting the IP offload connection, a traditional core network IP connection data path and IP offload connection data may be established. path. Specifically, FIG. 3a is a data flow path of an IP split connection and a traditional core network IP connection in the UTRAN system, and FIG. 3b is a data flow path of an IP split connection and a traditional core network IP connection in the E-UTRAN system, as shown in FIG. 3a. As shown in 3b, the IP offload data path is: Data is transmitted from the terminal through the radio side network element to the local gateway, and the data transmission does not pass through the core network.

In the prior art, as long as the user terminal moves away from the originally attached wireless side network element, the previously established IP offload connection is interrupted. Moreover, since the coverage of the home base station is small, the user terminal can easily leave the home base station that is initially attached, and therefore, the IP shunt connection of the home base station system is interrupted frequently, thereby reducing the user experience. Summary of the invention

In view of the above, the main purpose of the present invention is to provide a method and system for IP offloading mobility support, which can solve the problem that the IP split connection is interrupted frequently due to the user terminal easily leaving the attached home base station, thereby improving the user experience. .

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention provides a method for IP shunt connection mobility support, the method includes: when a terminal moves, the radio side network element currently serving the terminal moves the IP shunt connection of the terminal according to the obtained mobility determination information. If the IP offload connection of the terminal is determined to support mobility, the IP offload connection of the terminal is maintained, and when the IP offload connection of the terminal does not support mobility, the IP offload connection of the terminal is released.

In the above solution, the mobility determination of the IP offload connection of the terminal is performed as follows: The radio side network element currently serving the terminal determines that it is the radio side network element that is previously serving the terminal, or is about to be based on the mobility determination information. Whether the wireless side network elements serving the terminal are in the same After the mobility zone is determined to be in the same mobility zone, it indicates that the IP offload connection of the terminal supports mobility. After determining that it is not in the same mobility zone, it indicates that the IP offload connection of the terminal does not support mobility.

In the above solution, the mobility determination information includes: a closed user group list of the mobility area and/or,

A list of access point names (APN, Access Point Name) of the mobility area; and/or a list of wireless side network elements of the mobility area.

In the foregoing solution, before performing mobility determination on the IP offload connection of the terminal, the method further includes:

The wireless side network element currently serving the terminal service obtains mobility determination information.

In the above solution, the radio side network element currently serving the terminal acquires mobility determination information, which is:

The wireless side network element currently serving the terminal from the local gateway, or the domain name system (DNS, Domain)

Name System) Server, or Home Base Station Management System (HMS, HNB Management)

System) Get mobility judgment information.

In the above solution, the acquiring the mobility determination information from the local gateway is:

When there is no control plane between the wireless side network element and the local gateway, the local gateway forwards the mobility determination information to the wireless side network element through the core network gateway and the mobility management entity, and the wireless side network element and the local gateway. When there is a control plane between, the local gateway sends the mobility determination information to the radio side network element by using control plane signaling;

The obtaining the mobility determination information from the DNS server or the HMS is:

When the radio side network element is powered on, or needs to perform mobility determination of the IP offload connection, the radio side network element sends a DNS query request message to the DNS server or the HMS;

The DNS server, or the HMS obtains the mobility determination information according to the identification information of the wireless side network element or the identification information of the local gateway that serves the IP offload connection service, and obtains the mobility determination information to the wireless side network element package. A query response message containing mobility determination information.

In the above solution, the radio side network element currently serving the terminal is: a base station, or a home base station, or a radio network controller (RNC), or a shunt gateway, or a shunt function entity, or It is a home base station gateway.

The present invention also provides a system for IP offload connection mobility support, the system comprising: a radio side network element, configured to perform mobility on an IP offload connection of the terminal according to the obtained mobility determination information when the terminal moves When it is determined that the IP offload connection of the terminal supports mobility, the IP offload connection of the terminal is maintained, and when the IP offload connection of the terminal does not support mobility, the IP offload connection of the terminal is released.

In the above solution, the system further includes a local gateway, or a DNS server, or an HMS, for providing mobility judgment information to the wireless side network element;

The wireless side network element is further configured to obtain mobility determination information from a local gateway, or a DNS server, or an HMS.

The method and system for IP shunt connection mobility support provided by the present invention, when the terminal moves, the radio side network element currently serving the terminal performs mobility judgment on the IP shunt connection of the terminal according to the obtained mobility judgment information, and determines When the IP offload connection of the terminal supports mobility, the IP offload connection of the terminal is maintained, and when the IP offload connection of the terminal does not support mobility, the IP offload connection of the terminal is released. In the solution of the present invention, when determining the support In the case of mobility, the IP offload connection of the terminal is maintained, and thus, the frequency of interruption of the IP offload connection caused by the movement of the terminal can be reduced, thereby improving the user experience. DRAWINGS

1 is a schematic diagram 1 of a related art wireless communication network connection;

2 is a schematic diagram 2 of a related art wireless communication network connection;

3a is a schematic diagram of a data flow path of an IP offload connection and a traditional core network IP connection in a UTRAN system; FIG. 3b is a schematic diagram of a data flow path of an IP offload connection and a traditional core network IP connection in an E-UTRAN system; FIG.

4 is a schematic flowchart of a method for supporting mobility support of an IP offload connection according to the present invention;

5 is a schematic flowchart of a method for acquiring mobility determination information in an attach procedure according to Embodiment 1; FIG. 6 is a schematic flowchart of a method for acquiring mobility determination information in a PDN connection establishment process according to Embodiment 2;

7 is a schematic flowchart of a method for acquiring mobility determination information and determining mobility in a tracking area update process in Embodiment 3;

FIG. 8 is a schematic flowchart of a method for acquiring mobility determination information and determining mobility in a service request process according to Embodiment 4;

9 is a schematic flowchart of a method for acquiring mobility determination information and determining mobility in a handover process of Embodiment 5;

10 is a schematic flowchart of a method for acquiring mobility determination information and determining mobility in the handover process of Embodiment 6;

FIG. 11 is a schematic flowchart of a method for obtaining mobility determination information by means of a DNS server query in Embodiment 7. detailed description

The basic idea of the present invention is: When the terminal moves, the wireless side network element currently serving the terminal performs mobility determination on the IP offload connection of the terminal according to the obtained mobility determination information, and determines the IP offload connection support mobility of the terminal. When the IP offload connection of the terminal is maintained, and the IP offload connection of the terminal does not support mobility, the IP offload connection of the terminal is released.

The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

The method for IP mobility connection mobility support provided by the present invention, as shown in FIG. 4, includes the following steps:

Step 401: The mobility side determination information is obtained by the wireless side network element currently serving the terminal. Specifically, the wireless side network element currently serving the terminal acquires mobility determination information from the local gateway, or the DNS server, or the HMS.

Here, the radio side network element currently serving the terminal may specifically be: a base station, a home base station, an RNC, a offload gateway, a offload function entity, or a home base station gateway.

The mobility determination information may include: a closed user group list of a mobility area; and/or an APN list of a mobility area; and/or a wireless side network element list of a mobility area; The closed user group list may be: a closed user group identifier (CSG ID) list, or a closed user group name (CSG name) list, and the like; the wireless side network element list may specifically be: a home base station identifier list or the like.

Step 402: When the terminal moves, the wireless side network element currently serving the terminal performs mobility determination on the IP offload connection of the terminal according to the obtained mobility determination information, and determines that the IP offload connection of the terminal supports mobility, and maintains the location. Defining the IP offload connection of the terminal, and determining that the IP offload connection of the terminal does not support mobility, and releasing the IP offload connection of the terminal;

Specifically, according to the mobility determination information, it is determined whether the wireless side network element that is previously served by the terminal, or the wireless side network element that is to serve the terminal is in the same mobility area, and if yes, indicates the IP address of the terminal. The offload connection supports mobility, otherwise it indicates that the terminal's IP offload connection does not support mobility.

For example, when the mobility determination information includes a CSG ID list of a mobility area, the wireless side network element currently serving the terminal determines whether the CSG ID of the terminal is wireless with the previous service according to the mobility determination information. The side network element, or the CSG ID of the wireless side network element that is about to serve the terminal, is in the closed user group list in the same mobility area. If yes, the IP offload connection of the terminal can be maintained. Otherwise, the IP address of the terminal is indicated. The shunt connection cannot be maintained. Similarly, when the mobility determination information includes a home base station identifier list of a mobility area, the wireless side network element currently serving the terminal determines whether the home base station identifier of the terminal is the wireless side that is previously serving the terminal according to the mobility determination information. Network element, or home with the wireless side network element that will serve the terminal The base station identifies the home base station identifier list in the same mobility area. If yes, the IP split connection of the terminal can be maintained. Otherwise, the IP split connection of the terminal cannot be maintained. Similarly, when the mobility determination information includes an APN list of the mobility area, the wireless side network element currently serving the terminal determines whether the APN of the IP offload connection of the terminal can be wirelessly served by the terminal according to the mobility determination information. The side network element, or the wireless side network element that is about to serve the terminal, moves. If yes, the IP offload connection of the terminal can be maintained. Otherwise, the IP offload connection of the terminal cannot be maintained. The mobility management entity obtains, by using the prior art, the identification information related to the mobility determination information of the wireless side network element that is previously served by the terminal before the terminal moves, and the wireless side network element currently serving the terminal is from the mobility management entity. Obtaining the identification information related to the mobility determination information of the wireless side network element that is previously served by the terminal, such as: a CSG ID, or a home base station identifier, etc.; for the handover procedure, the wireless side network element currently serving the terminal is reported according to the terminal Identification information, such as: CSG ID, or home base station identification.

Here, the timing at which the terminal moves may be: performing tracking area update, performing a service request after moving, or performing switching.

When the timing of the movement of the terminal is to perform the tracking area update, the wireless side network element currently serving the terminal determines whether the wireless side network element serving as the terminal service is in the same mobility area according to the mobility determination information; The wireless side network element that is currently serving the terminal refers to: a wireless side network element that is currently serving the terminal after moving to an area outside the tracking area list.

When the time when the terminal moves is the service request after the mobile, the wireless side network element that is currently serving the terminal determines whether the wireless side network element that is the service of the terminal is in the same mobility area according to the mobility determination information; The wireless side network element that is currently serving the terminal refers to: a wireless side network element that is currently serving the terminal after the mobile.

When the time when the terminal moves is to perform the handover, the wireless side network element currently serving the terminal determines whether it is in the same state as the wireless side network element to be served by the terminal according to the mobility determination information. The wireless side network element that is currently serving the terminal refers to: the wireless side network element that serves the terminal before the handover; the wireless side network element that is to serve the terminal refers to: The wireless side network element of the terminal service.

Here, it should be noted that: the IP offloading according to the present invention may be: a local IP access user local network, a local IP access company local network, a local IP access Internet, a streaming operation of an Internet service, or a specific IP data offload.

The present invention will be further described in detail below with reference to the embodiments.

Embodiment 1:

The method for acquiring mobility determination information in the attaching process of this embodiment, as shown in FIG. 5, includes the following steps:

Step 501: Before performing communication, the terminal needs to establish a radio resource control (RRC) connection as a signaling message or a bearer of service data. At this time, the terminal sends the initialization non-access stratum (NAS) to the radio side network element. , Non-Access-Stratum) message attachment request message, performing an attach operation;

Step 502: After receiving the attach request message, the wireless side network element sends the initial user message to the mobility management entity, and forwards the attach request message to the mobility management entity.

Step 503: After receiving the request message, the mobility management entity starts the authentication and the security process, and performs a risk certificate on the user.

Step 504: The mobility management entity determines that it needs to be established according to the APN or the local access identifier.

After the IP offload connection, the session establishment request message is sent to the core network gateway;

Here, the APN or local access identity is carried in the initial user message.

In the Long Term Evolution (LTE) system, the core network gateway refers to: a core network service gateway, that is, an SGW.

Step 505: The core network gateway sends a session establishment request message to the local gateway.

Step 506: After receiving the session establishment request message, the local gateway creates a user context, and sends the user context to the core. The heart network gateway responds to the session establishment response message;

Here, the mobility determination information has been previously configured on the local gateway.

There is no control plane between the local gateway and the wireless side network element. That is, the local gateway cannot directly send the mobility judgment information to the wireless side network element. In this case, the mobility judgment information needs to pass through the core network gateway and mobility. The management entity forwards the packet to the wireless side network element.

The session establishment response message includes mobility determination information.

Step 507: After receiving the session establishment response message, the core network gateway sends a session establishment response message to the mobility management entity.

Here, the session establishment response message includes mobility determination information.

Step 508: After receiving the session establishment response message, the mobility management entity sends an initial context setup request message to the radio side network element.

Here, the initial context establishment request message includes mobility determination information.

Step 509: After receiving the initial context setup request message, the radio side network element performs an RRC connection configuration process.

Step 510: After the RRC connection configuration process is completed, a direct tunnel is established between the wireless side network element and the local gateway.

Here, since there is no control plane between the wireless side network element and the local gateway, in this step, there is no control plane signaling interaction between the wireless side network element and the local gateway.

Step 509 and step 510 can be performed in parallel.

Step 511: The wireless side network element saves the obtained mobility determination information.

Here, this step may also be performed after step 508, that is, the wireless side network element may perform the step after obtaining the mobility determination information.

Step 512: The radio side network element returns an initial context establishment response to the mobility management entity. Step 513: The terminal then sends a direct transmission message to the radio side network element, including the attachment completion information. Step 514: After receiving the direct transmission message, the wireless side network element sends an attach complete message to the mobility management entity.

Step 515: After receiving the attach complete message, the mobility management entity requests an update bearer from the core network gateway.

Here, it should be noted that: when there is a control plane between the wireless side network element and the local gateway, the session establishment response message that the local gateway responds to the core network gateway in step 506 does not include mobility determination information, and correspondingly, in step 507. The session establishment response message and the initial context establishment request message in step 508 do not contain mobility determination information. At this time, in step 510, there is interaction of control plane signaling between the wireless side network element and the local gateway. The wireless side network element requests the mobility determination information from the local gateway through the control plane signaling in the direct tunnel establishment process, and the local gateway returns the mobility determination information to the wireless side network element by using corresponding signaling; or, the local gateway directly The mobility judgment information is sent to the radio side network element through the control plane signaling in the direct tunnel establishment process, and the radio side network element request is not required.

In this embodiment, only the establishment of the IP offload connection is described, and the establishment of the core network connection is not affected. The establishment of the core network connection can be implemented by using the prior art.

In this embodiment, an EPS access system is taken as an example to describe a flow of obtaining mobility determination information by a radio side network element in an attach procedure, and an enhanced data rate GSM evolved radio access network (GERAN, GSM EDGE) in a UTRAN or global mobile communication system. The Radio Access Network (PDP) context activation process can also be used to implement the mobility determination information, that is, the mobility determination information is carried in the corresponding message. Send to the wireless side network element.

Embodiment 2:

This embodiment is applicable to the PDN connection establishment process of the EPS access system. The method for obtaining the mobility determination information in the PDN connection establishment process in this embodiment, as shown in FIG. 6, includes the following steps: Step 601: The terminal sends the information to the radio side network element. PDN connection request message, PDN connection Establish operation

Here, the terminal is attached to the network and has a PDN connection.

Step 602: After receiving the connection request message, the wireless side network element forwards the PDN connection request message to the mobility management entity.

Step 603: After receiving the connection request message, the mobility management entity determines, according to the APN or the local access identifier, that after the IP offload connection needs to be established, sends a session establishment request to the core network gateway, where the APN or the local access identifier carries the PDN connection request. In the message.

In the LTE system, the core network gateway refers to: a core network service gateway, that is, an SGW. Step 604: After receiving the session establishment request message, the core network gateway sends a session establishment request message to the local gateway.

Step 605: After receiving the session establishment request message, the local gateway creates a user context, and responds to the core network gateway with a session establishment response message.

Step 606: After receiving the session establishment response message, the core network gateway sends a session establishment response message to the mobility management entity.

Step 607: After receiving the session establishment response message, the mobility management entity sends a bearer setup request message to the radio side network element.

Here, the initial bearer setup request message includes mobility determination information.

Step 608: After receiving the bearer setup request message, the radio side network element performs RRC connection configuration. Process

Step 609: After the RRC connection configuration process is completed, a direct tunnel is established between the wireless side network element and the local gateway.

Step 608 and step 609 can be performed in parallel.

Step 610: The wireless side network element saves the obtained mobility determination information.

Here, this step may also be performed after step 607, that is, the radio side network element may perform the step after obtaining the mobility determination information.

Step 611: The radio side network element sends a bearer setup response message to the mobility management entity. Step 612: The terminal sends a direct transmission message to the radio side network element, including the attach completion information. Step 613: The radio side network element receives the direct transmission message. Afterwards, sending a PDN connection complete message to the mobility management entity;

Step 614: After receiving the PDN connection completion message, the mobility management entity requests an update bearer from the core network gateway.

Here, it should be noted that: when there is a control plane between the wireless side network element and the local gateway, the session establishment response message that the local gateway responds to the core network gateway in step 605 does not include mobility determination information, and correspondingly, in step 606 The session establishment response message and the bearer setup request message in step 607 do not contain mobility determination information. At this time, in step 609, there is interaction of control plane signaling between the radio side network element and the local gateway. The wireless side network element requests the mobility determination information from the local gateway through the control plane signaling in the direct tunnel establishment process, and the local gateway returns the mobility determination information to the wireless side network element by using corresponding signaling; or, the local gateway directly The mobility judgment information is sent to the radio side network element through the control plane signaling in the direct tunnel establishment process, and the radio side network element request is not required.

In this embodiment, only the establishment of the IP offload connection is described, and the establishment of the core network connection is not affected. The establishment of the core network connection can be achieved by using the prior art.

In this embodiment, the EPS access system is taken as an example to describe the process of obtaining the mobility determination information by the radio side network element in the PDN connection establishment process, and the PDP context activation process in the UTRAN or GERAN access may also use the embodiment. The obtaining of the mobility determination information is performed, that is, the mobility determination information is carried in the corresponding message and sent to the wireless side network element.

Embodiment 3:

This embodiment is applicable to the tracking area update process of the EPS access system. In the following description, in order to distinguish each radio side network element, the mobility management entity, and the core network gateway, the radio side network element that is currently serving the terminal after the terminal moves is used. The wireless side network element, which is called the target wireless side network element, and serves the terminal before the terminal enters the idle state, is called the original wireless side network element, and the mobility management entity that is currently serving the terminal after the mobile is called the target mobility. The management entity, the mobility management entity that serves the terminal before the terminal enters the idle state, is called the original mobility management entity, and the core network gateway that is currently serving the terminal after the mobile is called the target core network gateway, and the terminal enters the idle state. The core network gateway that was previously used for terminal services is called the original core network gateway. The method for obtaining the mobility determination information and the mobility determination in the tracking area update process in this embodiment, as shown in FIG. 7, includes the following steps: Step 701: After the terminal moves, send a tracking area update request message to the target wireless side network element, and the target The wireless side network element sends a tracking area update request message to the target mobility management entity selected by the terminal;

Here, after the terminal accesses the wireless communication system, it has an IP offload connection. Thereafter, the terminal enters an idle state, and when the terminal moves to an area other than the routing area or the tracking area list, or the period timer expires, etc., the terminal tracking area update request is triggered. Message.

After the terminal moves, the target wireless side network element may be different from the original wireless side network element.

Step 702: When the target mobility management entity determines that the original mobility management entity is different from the original mobility management entity, the target mobility management entity sends a context request message to the original mobility management entity.

Here, the tracking area update request message includes related information of the terminal, the target mobility tube According to this, the entity learns whether the original mobility management entity is the same, and after determining the difference, further obtains the IP address of the original mobility management entity according to the IP address, and sends a context request message to the original mobility management entity according to the IP address, where the specific processing procedure It is exactly the same as the prior art, and will not be described here.

If the target mobility management entity determines to be the same as the original mobility management entity, steps 702-705 are not performed.

Step 703: After receiving the context request message, the original mobility management entity includes a context response message of the context information of the terminal to the target mobility management entity.

Here, if the terminal has an IP offload connection, the message carries the bearer letter of the IP offload connection. Step 704: After receiving the context response message, the target mobility management entity initiates an authentication process. Here, if the target mobility management entity is based on the terminal Context information, when it is determined that the authentication process needs to be initiated, perform this step to determine that the authentication process is not required.

Step 705: The target mobility management entity saves the context information of the terminal, and responds to the original mobility management entity with a context confirmation message.

Step 706: The target mobility management entity sends a session establishment request message to the target core network gateway selected for the IP offload connection.

Step 707: The target core network gateway initiates an update process to the local gateway.

There is no control plane between the local gateway and the wireless side network element. That is, the local gateway cannot directly send the mobility judgment information to the wireless side network element. In this case, the mobility judgment information needs to pass through the core network gateway and mobility. The management entity forwards the information to the wireless network element. Specifically, the local gateway sends the mobility determination information to the target core network gateway in the bearer update response.

Step 708: The target core network gateway sends a session establishment response to the target mobility management entity. Here, the session establishment response includes mobility determination information.

Step 709: After receiving the session establishment response message, the target mobility management entity initiates a location update process to the authentication authorization server.

Step 710: After the location update process is completed, the authentication authorization server initiates a location deletion process to the original mobility management entity.

Step 711: The original mobility management entity initiates a session deletion process to the original core network gateway.

Here, if the original mobility management entity has established a connection session with the original core network gateway, this step is performed. If not, the step is not performed.

Step 712: When the target mobility management entity decides not to activate the user's bearer, the target mobility management entity sends a tracking area update accept message to the target wireless side network element, and then performs steps 723-724, when the target mobility management entity decides to activate. When the user is carrying, the mobility management entity sends an initial context setup request message to the target wireless side network element, and simultaneously sends a tracking area update accept message;

Here, the initial context setup request message carries an address of the local gateway serving as the IP offload connection service of the terminal, and mobility determination information.

Step 713: After receiving the initial context setup request message, the target radio side network element determines whether the local gateway of the IP offload connection service of the terminal can continue to serve the target radio side network element. If yes, step 714 is performed, otherwise, execution is performed. Step 718, then continue to perform steps 720-722; Here, when the IP offload connection needs to support business continuity, this step must be performed, otherwise the step may not be performed.

Step 714: Establish a direct tunnel between the target radio side network element and the local gateway.

Here, since there is no control plane between the wireless side network element and the local gateway, in this step, there is no control plane signaling interaction between the wireless side network element and the local gateway. Step 715: The target radio side network element saves the obtained mobility determination information. Step 716: The target radio side network element determines, according to the obtained mobility determination information, whether the target radio side network element is in the same mobility as the original radio side network element. In the area, if yes, perform steps 717-719, then perform steps 724~725, otherwise, perform step 718, and then perform steps 720-725;

Step 717: The target radio side network element performs an RRC connection configuration process.

Here, this step can also be performed after step 712.

Step 718: After the RRC connection configuration process is completed, the target radio side network element returns an initial context setup response message to the target mobility management entity.

Here, when the target radio side network element determines that the local gateway cannot continue to serve the target radio side network element, or when the target radio side network element determines that the original radio side network element is not in the same mobility area, the initial reply The context establishment response message indicates that the IP offload connection cannot be established.

Step 719: After receiving the initial context setup response message, the target mobility management entity initiates a tampering process to the target core network gateway.

Here, when the bearer modification process is performed, the bearer modification process may be performed between the target core network gateway and the local gateway, and the specific processing process is completely the same as the prior art, and details are not described herein again.

Step 720: Perform a direct tunnel release process between the target radio side network element and the local gateway to release the direct tunnel of the IP offload connection.

Steps 721 to 723: The target mobility management entity initiates a session deletion process to the target core network gateway, and deletes the IP offload connection information on the target core network gateway. The target core network gateway initiates a session deletion process to the local gateway, and deletes the IP on the local gateway. Divide the connection information; the target core network gateway replies to the target mobility management entity with a session deletion response message;

Here, steps 721 to 723 are processes for releasing the core network tunnel.

If the local gateway does not delete the IP offload connection information of the terminal in step 720, then step 722 is performed, that is, the target core network gateway initiates a session deletion process to the local gateway. Delete the IP offload connection information on the local gateway. When the local gateway has deleted the IP offload connection information of the terminal in step 720, step 722 is not performed.

Steps 724~725: The target radio side network element sends a location update accept message to the terminal, and the terminal sends a tracking area update complete message to the target mobility management entity.

Here, if the IP offload connection is the only connection of the terminal, and since it cannot be released while supporting mobility within the coverage of the current radio side network element, the target mobility management entity will then initiate the user de attach procedure.

In this embodiment, when the target radio side network element determines that the target radio side network element is not in the same mobility area as the original radio side network element, in step 716, it is determined that the IP offload connection cannot support mobility. The process of releasing the IP split connection is adopted. In this case, the process of releasing only the direct tunnel and retaining the core network tunnel may be adopted. The direct tunnel refers to: the local gateway - the target core network gateway - the target wireless side network element directly Tunnel.

Here, when there is a control plane between the wireless side network element and the local gateway, the bearer update response message sent by the local gateway to the core network gateway in step 707 does not include mobility determination information, and correspondingly, the session establishment response message in step 708 And the initial context establishment request message in step 712 does not include mobility determination information. At this time, in step 714, there is interaction of control plane signaling between the wireless side network element and the local gateway. The wireless side network element may request the mobility judgment information from the local gateway through the control plane signaling in the direct tunnel establishment process, and the local gateway returns the mobility determination information to the wireless side network element by using corresponding signaling; or, the local gateway The mobility judgment information is directly sent to the radio side network element through the control plane signaling in the direct tunnel establishment process, and the radio side network element request is not required.

In this embodiment, only the processing of the original IP offloading of the terminal in the tracking area update (TAU) process is described, and the processing of the core network connection is not affected. The processing of the core network connection can be implemented by using the prior art.

In this embodiment, the EPS access system is taken as an example to describe that the wireless side network element obtains the mobile in the TAU process. Sexual judgment information and a flow of mobility determination based on the mobility determination information, and

In the tracking area update process in the UTRAN/GERAN access, the present embodiment can also be used to implement the acquisition of mobility determination information and the determination of mobility.

Embodiment 4:

This embodiment is applicable to the EPS access system service request process. In the following description, in order to distinguish each radio side network element, the radio side network element that is currently serving the terminal after the terminal moves is called the target radio side network element, and The wireless side network element serving the terminal before the terminal enters the idle state is called the original wireless side network element. The method for obtaining the mobility determination information and the mobility determination in the service request process of this embodiment, as shown in FIG. 8, includes the following steps:

Step 801: When the terminal has signaling or data transmission, send a service request message to the target radio side network element, and the target radio side network element sends a service request message to the mobility management entity.

Here, the terminal has an IP offload connection after accessing the wireless communication system, and thereafter, the terminal enters an idle state. After the terminal moves, signaling or data transmission will trigger the terminal to initiate a service request message. At this time, the terminal moves beyond the area outside the tracking area list.

Step 802: Perform an authentication process of the NAS;

Here, the service request message includes related information of the terminal, and the mobility management entity determines whether the authentication process needs to be initiated according to the determination. If it is determined, the step is performed, and when it is determined that it is not needed, the step is not performed.

Step 803: After the authentication process is completed, the mobility management entity sends an initial context setup request message to the target wireless side network element.

Here, the initial context setup request message carries an address of a local gateway that is an IP offload connection service of the terminal.

Step 804: After receiving the initial context setup request message, the target radio side network element determines whether the local gateway of the IP offload connection service of the terminal can continue to serve the target radio side network element. If yes, step 805 is performed; otherwise, execution is performed. Step 809; Here, when the IP offload connection needs to support business continuity, that is, support for mobility must perform this step; otherwise, this step may not be performed.

Step 805: Establish a direct tunnel between the wireless side network element and the local gateway.

Here, when there is no control plane between the wireless side network element and the local gateway, in this step, there is no control plane signaling interaction between the wireless side network element and the local gateway. At this time, the wireless side network element can be from the DNS. Or HMS obtains mobility judgment information.

When there is a control plane between the wireless side network element and the local gateway, in this step, the wireless side network element may request mobility determination information from the local gateway through the control plane signaling in the direct tunnel establishment process, and the local gateway will The mobility judgment information is returned to the radio side network element by using the corresponding signaling; or the local gateway directly sends the mobility judgment information to the radio side network element through the control plane signaling in the direct tunnel establishment process, and does not need the radio side network element. request.

Step 806: The wireless side network element saves the obtained mobility determination information.

Step 807: The radio side network element determines, according to the obtained mobility determination information, whether the target radio side network element is in the same mobility area as the original radio side network element, and if yes, performing steps 808-810, otherwise, performing steps 809, after performing steps 811~814;

Step 808: The target radio side network element performs an RRC connection configuration process.

Step 809: After the RRC connection configuration process is completed, the target radio side network element returns an initial context setup response message to the mobility management entity.

Here, when the target radio side network element determines that the original radio side network element is not in the same mobility area, the reply initial context setup response message indicates that the IP offload connection cannot be established.

Step 810: After receiving the initial context setup response message, the mobility management entity initiates a bearer modification process to the core network gateway.

Here, when the bearer modification process is performed, the bearer modification process may be performed between the core network gateway and the local gateway, and the specific processing process is completely the same as the prior art, and details are not described herein again.

Step 811: Perform a direct tunnel release process between the wireless side network element and the local gateway to release Direct tunneling of IP split connections;

Steps 812~814: After the mobility management entity initiates a session deletion process to the core network gateway, the IP offload connection information on the core network gateway is deleted; the target core network gateway initiates a session deletion process to the local gateway, and deletes the IP offload connection on the local gateway. Information; the core network gateway then replies to the mobility management entity with a session deletion response;

Here, steps 812-814 are processes for releasing the core network tunnel.

If the local gateway does not delete the IP offload connection information of the terminal in the step 811, the step 813 is performed, that is, the target core network gateway initiates a session deletion process to the local gateway, and deletes the IP offload connection information on the local gateway. When the local gateway has deleted the IP offload connection information of the terminal in step 811, step 813 is not performed.

In this embodiment, when the target radio side network element determines that the target radio side network element is not in the same mobility area as the original radio side network element, in step 807, it is determined that the IP offload connection cannot support mobility. The process of releasing the IP split connection is adopted. In this case, the process of releasing only the direct tunnel and retaining the core network tunnel may be adopted. The direct tunnel refers to: the local gateway - the target core network gateway - the target wireless side network element directly Tunnel.

In the embodiment, only the processing of the original IP offload of the terminal in the service request (SR) process is described, and the processing of the core network connection is not affected. The processing of the core network connection can be implemented by using the prior art.

In this embodiment, an EPS access system is taken as an example to describe a process in which a radio side network element obtains mobility determination information and a mobility judgment according to the mobility determination information, and a service request process in UTRAN/GERAN access The present embodiment can also be used to implement the acquisition of mobility determination information and the determination of mobility.

Embodiment 5:

This embodiment is applicable to the S1 handover process of the EPS access system. To distinguish the wireless side network elements, the mobility management entity, and the core network gateway, the wireless side network element that is currently serving the terminal is called the original wireless side network element. The wireless side network element serving the terminal after the terminal performs the handover, which is called the target wireless The side network element, the mobility management entity that is currently serving the terminal, is called the original mobility management entity, and the mobility management entity that is the terminal service after the terminal is switched, is called the target mobility management entity, and is currently serving the terminal. The core network gateway, called the original core network gateway, is the core network gateway that serves the terminal after switching the terminal, and is called the target core network gateway. The method for obtaining the mobility determination information and the mobility determination in the handover process, as shown in FIG. 9, includes the following steps: Step 901: When the original radio side network element discovers that the cell signal currently accessed by the terminal is lower than the threshold , initiate the S1 handover process;

Here, the terminal periodically detects the wireless signal of the local cell and other neighboring cells, and reports the report to the original wireless side network element in the form of a measurement report.

At this time, the original radio side network element selects a target radio side network element with a suitable signal strength to initiate a handover procedure.

Step 902: The original radio side network element determines, according to the saved mobility determination information, whether the target radio side network element is in the same mobility area as the original radio side network element. If yes, step 903 is performed; otherwise, the terminal is placed. IP offload connection;

Step 903: The original radio side network element sends a handover request message to the original mobility management entity. Here, the handover request message includes bearer information of the IP offload connection of the terminal.

Step 904: After receiving the handover request message, the original mobility management entity sends a handover forward request message to the target mobility management entity.

Here, the handover forward request message includes bearer information of an IP offload connection.

Step 905: After receiving the handover forward request message, the target mobility management entity initiates a session establishment process to the target core network gateway.

Here, when the core network gateway serving the terminal does not change during the handover, this step is not performed.

Step 906: The target mobility management entity sends a handover request message to the target radio side network element. Here, the message carries the address of the local gateway of the IP offload connection service of the terminal. Step 907: After receiving the handover request message, the target radio side network element determines whether the local gateway of the IP offload connection service of the terminal can continue to serve the target radio side network element. If yes, step 908 is performed, otherwise, the IP offload is deleted. connection;

Here, when the IP offload connection needs to support business continuity, this step must be performed. Otherwise, this step may not be performed.

Step 908: Establish a direct tunnel between the target wireless side network element and the local gateway.

Here, when there is no control plane between the target radio side network element and the local gateway, in this step, there is no control plane signaling interaction between the target radio side network element and the local gateway. At this time, the target radio side network element Mobility judgment information can be obtained from DNS or HMS.

When there is a control plane between the target wireless side network element and the local gateway, in this step, the target wireless side network element may request mobility determination information from the local gateway through the control plane signaling in the direct tunnel establishment process, and the local gateway will The mobility determination information is returned to the target radio side network element by using the corresponding signaling; or the local gateway directly sends the mobility determination information to the target radio side network element by using the control plane signaling in the direct tunnel establishment process, Target wireless side network element request.

Step 909: The target radio side network element responds to the target mobility management entity with a handover confirmation message. Step 910: Continue to complete the subsequent handover process.

Step 911: Continue tracking the zone update process.

In this embodiment, in step 902, when the original radio side network element determines that the target radio side network element is not in the same mobility area as the original radio side network element, that is, when it is determined that the IP offload connection cannot support mobility, The process of releasing the IP offloading connection is adopted. In this case, the process of releasing only the direct tunnel and retaining the core network tunnel may be adopted. The direct tunnel refers to: the local gateway-target core network gateway-target wireless side network element directly Tunnel.

In this embodiment, only the processing of the original IP offloading of the terminal in the S1 handover process is described, and the processing of the core network connection is not affected. The processing of the core network connection can be implemented by using the prior art.

In this embodiment, the EPS access system is taken as an example to describe that the radio side network element is removed during the S1 handover process. Dynamic judgment information and a flow of mobility determination based on the mobility determination information, and

In the handover procedure in the UTRAN/GERAN access, the present embodiment can also be used to implement the acquisition of mobility judgment information and the determination of mobility.

Example 6:

This embodiment is applicable to the X2 handover process of the EPS access system. To distinguish the wireless side network elements, the wireless side network element that is currently serving the terminal is called the original wireless side network element, and the terminal is switched to serve the wireless service of the terminal. The side network element is called the target wireless side network element. The method for obtaining the mobility determination information and the mobility determination in the handover process, as shown in FIG. 10, includes the following steps: Step 1001: When the original radio side network element discovers that the cell signal currently accessed by the terminal is lower than the threshold , initiate the X2 handover process;

Step 1002: The original radio side network element determines, according to the saved mobility determination information, whether the target radio side network element is in the same mobility area as the original radio side network element. If yes, step 1002 is performed. Otherwise, the terminal is released. IP offload connection;

Step 1003: The original radio side network element sends a handover request message to the target radio side network element. Here, the handover request message includes bearer information of the IP offload connection of the terminal and an address of the local gateway serving the IP offload connection service of the terminal.

Step 1004: The target radio side network element determines whether the local gateway of the IP offload connection service of the terminal can continue to serve the target radio side network element. If yes, step 1005 is performed; otherwise, the IP offload connection of the terminal is released;

Here, when the IP offload connection needs to support business continuity, this step must be performed. Otherwise, this step may not be performed. Step 1005: A direct tunnel is established between the target wireless side network element and the local gateway. Here, when there is no control plane between the target wireless side network element and the local gateway, in this step, between the target wireless side network element and the local gateway There is no interaction of control plane signaling. At this time, the target radio side network element can obtain mobility determination information from the DNS or HMS.

Step 1006: The target radio side network element responds to the original radio side network element with a handover confirmation message. Step 1007: Continue to complete the subsequent handover process.

In this embodiment, in step 1002, when the target radio side network element determines that the target radio side network element is not in the same mobility area as the original radio side network element, that is, when it is determined that the IP offload connection cannot support mobility, The process of releasing the IP offload connection is adopted. In this case, the process of releasing only the direct tunnel and retaining the core network tunnel may be adopted. The direct tunnel refers to: the local gateway - the core network gateway - the target wireless side network element directly tunnel.

In this embodiment, only the processing of the original IP offloading of the terminal in the X2 handover process is described, and the processing of the core network connection is not affected. The processing of the core network connection can be implemented by using the prior art.

Example 7:

This embodiment is applicable to the EPS, UTRAN, or GERAN access system. In this embodiment, the method for obtaining mobility determination information by using a DNS server query manner, as shown in FIG. 11, includes the following steps:

Step 1101: When the radio side network element is powered on, or needs to perform mobility determination of the IP offload connection, the radio side network element sends a DNS query request message to the DNS server.

Here, the DNS server has previously configured the mobility determination information. The DNS query request message carries the identifier information of the radio side network element or the identifier information of the local gateway that serves the IP offload connection service, where the identifier information of the radio side network element may be: a CSG ID or a radio side network element. The identification information, the address, and the like, the identification information of the local gateway that is the IP offload connection service may be a local gateway identifier or an address, and the like.

Step 1102: The DNS server obtains the mobility determination information according to the identifier information of the wireless side network element or the identity information of the local gateway that is the IP offload connection service, and returns a DNS query response message including the mobility determination information to the wireless side network element. ;

Step 1103: After receiving the DNS query response, the wireless side network element saves the obtained mobility judgment information.

In this embodiment, only the wireless side network element queries the DNS server for the mobility determination information, and the mobility determination information can also be configured on the HMS. At this time, the wireless side network element needs to query the HMS, and the specific processing process and the DNS server are performed. The processing of the query is exactly the same and will not be described here.

When the wireless side network element obtains the mobility determination information by using the method in this embodiment, if the terminal moves, the mobility determination of the wireless side network element is the same as the process shown in FIG. 7 to FIG. 10, and the difference is: The wireless side network element does not need to obtain the mobility determination information from the local gateway.

Here, it should be noted that all the above embodiments are based on the example that the home base station is directly connected to the E-UTRAN system, and the related process of obtaining the mobility determination information and performing the mobility judgment in the wireless side network element in the IP offload connection communication system is described. . The radio side network element may be: the radio side network element may be a base station, a home base station, an RNC, a offload gateway, a offload function entity, or a home base station gateway, etc.; the mobility management entity may be an MME, an MSC, an SGSN, or Home base station gateways, etc.

All of the above embodiments are applicable to the UTRAN/GERAN access network and the core network through which the home base station is connected through the home base station gateway. Wherein, if accessing the UTRAN system, the core network gateway is a GGSN, and if accessing the E-UTRAN system, the core network gateway refers to: SGW and PGW. The access system is different, the message is different, but the effect is similar. The process of obtaining the traffic distribution policy for the local gateway is similar to the above embodiment, and does not affect the present invention. The processes are all known to those skilled in the art and are not mentioned here.

Based on the foregoing method, the present invention further provides a system for IP offload connection mobility support, where the system includes: a radio side network element, configured to perform IP offloading to the terminal according to the obtained mobility determination information when the terminal moves. The connection is used for mobility determination. When it is determined that the IP offload connection of the terminal supports mobility, the IP offload connection of the terminal is maintained, and when the IP offload connection of the terminal does not support mobility, the IP offload connection of the terminal is released.

Here, it should be noted that: the radio side network element refers to: a radio side network element currently serving the terminal.

The system may further include a local gateway, or a DNS server, or an HMS, for providing mobility determination information to the wireless side network element;

Here, the specific processing procedure of the radio side network element, the local gateway, or the DNS server, or the HMS in the system of the present invention has been described in detail above and will not be described again.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for Internet Protocol (IP) offload connection mobility support, the method comprising:

When the terminal moves, the wireless side network element currently serving the terminal performs mobility determination on the IP offload connection of the terminal according to the obtained mobility determination information, and determines that when the IP offload connection of the terminal supports mobility, the terminal is maintained. The IP offload connection determines that the IP offload connection of the terminal is released when the IP offload connection of the terminal does not support mobility.

The method according to claim 1, wherein the determining, by the IP splitting connection of the terminal, the mobility is:

The wireless side network element currently serving the terminal service determines whether it is in the same mobility area as the wireless side network element that is serving the terminal or the wireless side network element that is to serve the terminal according to the mobility determination information. After the same mobility zone is displayed, it indicates that the IP offload connection of the terminal supports mobility. After determining that it is not in the same mobility zone, it indicates that the IP offload connection of the terminal does not support mobility.

The method according to claim 1 or 2, wherein the mobility determination information comprises: a closed user group list of the mobility area; and/or,

a list of access point names (APNs) for the mobility zone; and / or,

A list of wireless side network elements in the mobility area.

The method according to claim 1 or 2, wherein before the mobility determination of the IP offload connection of the terminal, the method further comprises:

The method according to claim 4, wherein the wireless side network element currently serving the terminal acquires mobility determination information, which is:

The wireless side network element currently serving the terminal obtains mobility determination information from a local gateway, or a Domain Name System (DNS) server, or a Home Base Station Management System (HMS).

The method according to claim 5, wherein the obtaining the mobility determination information from the local gateway is:

The DNS server or the HMS queries the obtained mobility determination information according to the identification information of the wireless side network element or the identification information of the local gateway that is the IP offload connection service, and includes the query response message of the mobility determination information to the wireless side network element.

The method according to claim 1 or 2, wherein the radio side network element currently serving the terminal is: a base station, or a home base station, or a radio network controller (RNC), or a shunt Gateway, either for offloading functional entities, or for home base station gateways.

A system for supporting IP mobility and mobility support, the system comprising: a wireless side network element, configured to: when the terminal moves, move the IP offload connection of the terminal according to the obtained mobility determination information And determining, when the IP offload connection of the terminal supports the mobility, maintaining the IP offload connection of the terminal, and determining that the IP offload connection of the terminal does not support mobility, releasing the IP offload connection of the terminal.

The system according to claim 8, wherein the system further comprises a local gateway, or a DNS server, or an HMS, for providing mobility determination information to the wireless side network element;

The system according to claim 8 or 9, wherein the current terminal is The wireless side network element of the service is: a base station, or a home base station, or an RNC, or a shunt gateway, or a shunt function entity, or a home base station gateway.