WO2012068935A1

WO2012068935A1 - Gateway relocation method and source shunt gateway

Info

Publication number: WO2012068935A1
Application number: PCT/CN2011/081151
Authority: WO
Inventors: 吴瑟; 叶海洋; 刘建业; 周娜; 梁爽; 霍玉臻; 王静
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-25
Filing date: 2011-10-21
Publication date: 2012-05-31
Also published as: CN102480782B; CN102480782A

Abstract

Disclosed are a gateway relocation method and a source shunt gateway. The method includes: receiving, by a source shunt gateway, a message update request sent by a mobility management entity, when a terminal performs a mobility event; creating a message by the source shunt gateway toward a target shunt gateway; and sending a message update response by the source shunt gateway to the mobility management entity, wherein the message update response carries the message of the target shunt gateway. The present invention solves the current technical problem that the movement process cannot complete the handover function across shunt gateways, and achieves the movement function across shunt gateways.

Description

The present invention relates to the field of mobile communications, and in particular to a gateway relocation method and a source offload gateway. BACKGROUND OF THE INVENTION The 3rd Generation Partnership Project (3GPP) evolved Evolved Packet System (EPS) is an evolved universal mobile communication system (Evolved Universal Terrestrial Radio Access Network). , referred to as E-UTRAN, Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN GW for short) The Home Subscriber Server (HSS), 3GPP Authentication Authorization and Accounting (AAA) server, Policy and Charging Rules Function (Policy and Charging Rules Function, referred to as PCRF) consists of entities and other supporting nodes. 1 is a schematic diagram of an EPS system architecture according to the related art. As shown in FIG. 1, a mobility management entity is responsible for related operations of a control plane such as mobility management, processing of non-access stratum signaling, and management of a user mobility management context; The offload gateway S-GW is an access gateway device connected to the E-UTRAN, and forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data; the access gateway P-GW is EPS and Packet Data Network (PDN) The border gateway of the network is responsible for PDN access and forwarding data between EPS and PDN. Both S-GW and P-GW belong to the core network gateway. The home base station is a small, low-power base station deployed in indoor places such as homes and offices. The main purpose is to provide users with higher service rates and lower the cost of using high-speed services, while making up for existing distributed Insufficient coverage of cellular wireless communication systems. The advantages of home base stations are affordable, convenient, low power output, plug and play, and more. In the home base station system, the home base station and/or the home base station gateway are wireless side network elements, and the home base station gateway can be combined with the home base station. 2 is a schematic diagram 2 of the architecture of the existing communication system. As shown in FIG. 2, the home base station can access the core network through the logical network element of the home base station gateway, or can directly connect to the core network (as shown in FIG. 1). The main functions of the home base station gateway are: 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 exchanging data of the core network and the home base station. In addition to supporting the access of the mobile core network, the mobile communication system (including the home base station system) can also support the Internet Protocol (IP) shunt function, and the IP side of the network element has IP shunting capability and user subscription permitting IP. Under the condition of offloading, local access of the terminal to other IP devices or the Internet of the home network can be realized. The implementation of IP offloading in the system shown in Figure 1 and Figure 2 can provide powerful support for IP offloading technology by adding a shunt gateway. The shunt gateway acts as a gateway to the external network (such as the Internet) to provide address allocation and accounting. , packet packet filtering, policy control, data offloading function, NAS/S1-AP/RANAP (Radios Access Network Application Part, wireless access network application part) / GTP (General Tunneling Protocol) / PMIP (Proxy Mobile IP , Proxy Mobile IP Protocol) /MIP (Mobile IP, Mobile IP Protocol) Message parsing, NAT (Network Address Translation), IP offload policy routing and execution. The offload gateway can be combined with the wireless side network element. The offloading gateway may be an ISGW (Integrated Service Gateway), which may be a local serving gateway (Local SGW, referred to as L-SGW) and a local packet data gateway (Local PGW, referred to as L-PGW), or may be separate. L-PGW, which can be a data offload function entity. Taking the communication system of FIG. 1 as an example, the IP offloading can be implemented by adding or not adding a NAT address translation function on the branching gateway, and is not limited to the simultaneous access of the core network and the IP offloading through a connection. When the user moves to the new wireless side network element, the traffic distribution gateway can perform relocation. The IP traffic distribution service data can be offloaded through the new traffic distribution gateway (as shown in Figure 3). At this time, the traffic distribution service cannot guarantee continuity; The original offload gateway is anchored for offloading (as shown in Figure 4), and the continuity of the offload service can be maintained. In the case that there is a traffic distribution between the wireless network element and the access gateway, the existing mobile process cannot complete the switching function across the traffic distribution gateway, and the continuity of the core network data cannot be guaranteed during the terminal mobile process. SUMMARY OF THE INVENTION One of the main purposes of the present invention is to provide a gateway relocation method and a source offload gateway, so as to at least solve the above problem that when a traffic distribution gateway between a wireless side network element and an access gateway is implemented, the mobile process cannot be performed. The technical problem of completing the switching function across the distribution gateway. According to an aspect of the present invention, a gateway relocation method is provided, including: when a terminal performs a mobility event, the source offload gateway receives an information update request sent by a mobility management entity; The target offload gateway creates information; the source offload gateway sends an information update response to the mobility management entity, where the information update response carries information of the target offload gateway. The mobility event includes one of the following: a handover, a location update, or a service request. The information update request includes one of the following: a packet data protocol (PDP) context request, and a bearer update request; the creation information includes one of the following: creating a PDP context, establishing a bearer, and updating the information The response includes one of the following: Update PDP Context Response, Host Update Response. The source offload gateway is a offload gateway used before the terminal is switched or before the location is updated, and the target offload gateway is a offload gateway used after the terminal is switched or after the location is updated. When the terminal performs the handover, if the mobility management entity before and after the handover of the terminal changes, the mobility management entity that sends the information update request and receives the information update response is the terminal after the handover Mobility management entity. After the source offload gateway receives the information update request sent by the mobility management entity, the method further includes: the source offload gateway determining the type of the service transmitted by the terminal; and if the transmitted service is a service with low service continuity, The step of executing the source offload gateway to create information to the target offload gateway. After the source offload gateway determines the type of the service to be transmitted, the method further includes: if the transmitted service is not a service with low service continuity, the source offload gateway does not execute the source offload gateway to create a target offload gateway. a step of information and transmitting the information update response to the mobility management entity. The source offload gateway and the target offload gateway are one of the following: an ISGW; an L-SGW L-PGW; or an L-PGW. According to another aspect of the present invention, a source offload gateway is provided, comprising: a receiving unit, configured to receive an information update request sent by a mobility management entity when a terminal performs a mobility event; and create a unit, set to target The offload gateway creates information; the transmitting unit is configured to send an information update response to the mobility management entity after the information is created, wherein the information update response carries information of the target offload gateway. The source offload gateway is a offload gateway used before the terminal is switched or before the location is updated, and the target offload gateway is a offload gateway used after the terminal is switched or after the location is updated. The source offloading gateway further includes: a determining unit, configured to determine a type of the service transmitted by the terminal after receiving the information update request sent by the mobility management entity; and the notification unit is configured to determine the transmission When the service is a service with low business continuity, the creating unit is notified to perform the step of creating the information to the target offload gateway. In the present invention, information such as a PDP context is created by the source offload gateway to the target offload gateway, and an information update response such as a PDP update context response is sent to the mobility management entity, thereby solving the problem of the radio side network element and the access gateway. In the case where a traffic distribution gateway is implemented between the traffic distribution gateways, the existing mobile process cannot complete the handover function across the traffic distribution gateway, and the mobile function across the traffic distribution gateway is implemented, so as to effectively enhance the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a wireless communication network connection according to the related art; FIG. 2 is another schematic diagram of a wireless communication network connection according to the related art; FIG. 3 is a related art wireless communication system IP offloading FIG. 4 is another schematic diagram of IP split data of a wireless communication system in the related art; FIG. 5 is a preferred flowchart of a gateway relocation method according to an embodiment of the present invention; FIG. A scenario of the system architecture based on FIG. 1 in the embodiment of the present invention, a flowchart of a handover process performed by a terminal when a mobility management entity changes; FIG. 7 is a scenario based on the system architecture of FIG. 1 according to an embodiment of the present invention, mobility management FIG. 8 is a flowchart of a handover process performed by a terminal when the entity does not change; FIG. 8 is a flowchart of a handover process performed by the terminal when the mobility management entity changes according to the scenario of the system architecture of FIG. 1 according to an embodiment of the present invention; According to the scenario of the system architecture of FIG. 1 in the embodiment of the present invention, when the mobility management entity changes, the terminal performs a location update process. Flowchart; FIG. 10 is a system architecture based on the scenario of FIG. 1 embodiment of the present invention, the mobility management entity is not changed when the terminal is a flowchart of a location update procedure occurs; 11 is a flowchart of a service request process when a terminal is changed from an idle state to a connected state according to the scenario of the system architecture of FIG. 1 according to an embodiment of the present invention; FIG. 12 is a schematic diagram of a source offload gateway according to an embodiment of the present invention; A preferred block diagram of the structure. The technical solutions of the present invention are further described in detail below in conjunction with the accompanying drawings and specific embodiments, so that those skilled in the art can understand the invention and can implement the present invention, but the embodiments are not Limitation of the invention. Embodiment 1 FIG. 5 is a preferred flowchart of a gateway relocation method according to an embodiment of the present invention, which includes the following steps:

S502. When the terminal performs a mobility event, the source offload gateway receives the information update request sent by the mobility management entity.

S504. The source offload gateway creates information to the target offload gateway.

S506. The source offload gateway sends an information update response to the mobility management entity, where the information update response carries information of the target offload gateway. In the preferred embodiment, information such as a PDP context is created by the source offload gateway to the target offload gateway, and an information update response such as a PDP update context response is sent to the mobility management entity, thereby solving the problem that the existing mobile process cannot be completed. The problem of the switching function of the offload gateway ensures the continuity of the service when the terminal switches from the source offload gateway to the target offload gateway, so as to effectively enhance the user experience. Preferably, the mobility event comprises one of the following: a handover, a location update, or a service request. In the preferred embodiment, the utility of the present invention is increased by the definition of different mobility events. Preferably, the information update request includes one of the following: an update PDP context request, a bearer update request; the creation information includes one of the following: creating a PDP context, establishing a bearer; and the information update response includes one of the following: updating the PDP Context response, hosting update response. In the preferred embodiment, the gateway relocation method of the present invention can be applied to different scenarios. Preferably, the source offload gateway is a offload gateway used before the terminal is switched or before the location is updated, and the target offload gateway is a offload gateway used after the terminal is switched or after the location is updated. Preferably, in the case that the terminal performs handover, if the mobility management entity before and after the handover of the terminal changes, the mobility management entity that sends the information update request and receives the information update response is the terminal The switched mobility management entity. In the preferred embodiment, the correct transmission and continuity of the service of the terminal is ensured by communicating with the mobility management entity after the terminal handover. Preferably, after the source offload gateway receives the information update request sent by the mobility management entity, the method further includes: the source offload gateway determining the type of the service transmitted by the terminal; if the transmitted service is low in service continuity The service performs the step of creating information by the source offload gateway to the target offload gateway. In the preferred embodiment, the step of creating information to the target offload gateway by performing the source offload gateway on the service with low service continuity can better ensure the continuity of the service with low service continuity. Preferably, after the source offload gateway determines the type of the transmitted service, the method further includes: if the transmitted service is not a service with low service continuity, the source offload gateway does not execute the source offload gateway to the target The step of dividing the gateway to create information, and sending an information update response to the mobility management entity. In the preferred embodiment, the step of creating the information to the target offload gateway by the source offload gateway is not performed on the service whose type is not the service continuity is low, and the continuity of the service with low service continuity can be better ensured. Preferably, the source offload gateway and the target offload gateway are one of the following: an ISGW, an L-SGW, and

L-PGW, or L-PGW. Preferably, the source offload gateway and the target offload gateway are both ISGWs, or L-SGWs and L-PGWs, respectively, or both are L-PGWs. With the present embodiment, the applicability of the present invention is increased. The following embodiment describes an application scenario based on a UTRAN (Universal Terrestrial Radio Access Network) system. Embodiment 2 FIG. 6 is a flowchart of a handover process performed by a terminal when a mobility management entity changes based on a scenario of the system architecture of FIG. 1. The specific steps are described as follows: Step 602: The radio side network element determines that a handover needs to be initiated. Step 603: The source radio side network element sends a relocation request to the source mobility management entity. Step 604: The source mobility management entity sends a relocation forward request message to the target mobility management entity. Step 605: The target mobility management entity requests the target radio side network element to perform relocation. Step 606: The target radio side network element responds to the target mobility management entity with a relocation response message. Step 607: The target mobility management entity sends a relocation forward response message to the source mobility management entity. Step 608: The source mobility management entity sends a relocation command to the source radio side network element. Step 609: The source radio side network element sends a relocation execution message to the target radio side network element. Step 610: After receiving the relocation execution, the target radio side network element initiates relocation detection to the target mobility management entity. Step 611: The target radio side network element sends the radio access network mobility information to the terminal. After the terminal reconfigures, the target radio side network element returns an acknowledgement message. Step 612: The target radio side network element sends a relocation complete notification message to the target mobility management entity. Step 613: The relocation redirection completion message is exchanged between the source mobility management entity and the target mobility management entity. Step 614: The target mobility management entity sends a PDP context update request message to the source offload gateway. Step 615: The source offload gateway selects a target offload gateway, and the selection manner may be: selecting by using terminal location information. Step 616: The source offload gateway sends a PDP context creation request to the target offload gateway, and carries the access gateway information. Step 617: The target offload gateway sends a PDP context update request to the access gateway. Step 618: The access gateway replies with a PDP context update response. Step 619: The target offload gateway returns a PDP context setup response to the source offload gateway. Step 620: The source offload gateway initiates a PDP context update response to the target mobility management entity, and carries the target offload gateway information. Step 621: The target mobility management entity may update the locally saved offload gateway information, and update the radio bearer to the target radio side network element to carry the target offload gateway information. Embodiment 3 FIG. 7 is a flowchart of a handover process performed by a terminal when a mobility management entity does not change based on a scenario of the system architecture of FIG. 1. The specific steps are described as follows: In step 6a02, the radio side network element determines that a handover needs to be initiated. Step 6a03: The source radio side network element sends a relocation request to the mobility management entity. In step 6a04, the mobility management entity requests the target radio side network element to perform relocation. In step 6a05, the target radio side network element responds to the mobility management entity with a relocation response message. Step 6a06: The mobility management entity sends a relocation command to the source radio side network element. Step 6a07: The source radio side network element sends a relocation execution message to the target radio side network element. Step 6a08, after receiving the relocation execution, the target radio side network element initiates relocation detection to the target mobility management entity. Step 6a09: The target radio side network element sends the radio access network mobility information to the terminal. After the terminal reconfigures, the target radio side network element returns an acknowledgement message. In step 6al0, the target radio side network element sends a relocation complete notification message to the mobility management entity. In step 6all, the mobility management entity sends a PDP context update request message to the source offload gateway. Step 6al2, the source offload gateway selects the target offload gateway, and the selection manner thereof may be: selecting by using terminal location information. In step 6al3, the source offload gateway sends a PDP context creation request to the target offload gateway, and carries the access gateway.

In step 6al4, the target offload gateway sends a PDP context update request to the access gateway, step 6al5, and the access gateway replies to the PDP context update response. In step 6al6, the target offload gateway returns a PDP context establishment response to the source offload gateway. In step 6al7, the source offload gateway initiates a PDP context update response to the mobility management entity, and carries the target offload gateway information. In step 6al8, the mobility management entity may update the locally saved offload gateway information, and update the radio bearer to the target radio side network element to carry the target offload gateway information. Example 4 FIG. 8 is a flowchart of a handover process performed by a terminal when a mobility management entity changes according to a scenario of the system architecture of FIG. 1. In this process, the source switching gateway performs the switching mode selection. The specific steps are described as follows: Step 702: The radio side network element determines that a handover needs to be initiated. Step 703: The source radio side network element sends a relocation request to the source mobility management entity. Step 704: The source mobility management entity sends a relocation forward request message to the target mobility management entity. Step 705: The target mobility management entity requests the target radio side network element to perform relocation. Step 706: The target radio side network element responds to the target mobility management entity with a relocation response message. Step 707: The target mobility management entity sends a relocation forward response message to the source mobility management entity. Step 708: The source mobility management entity sends a relocation command to the source radio side network element. Step 709: The source radio side network element sends a relocation execution message to the target radio side network element. Step 710: After receiving the relocation execution, the target radio side network element initiates relocation detection to the target mobility management entity. Step 711: The target radio side network element sends the radio access network mobility information to the terminal. After the terminal reconfigures, the target radio side network element returns an acknowledgement message. Step 712: The target radio side network element sends a relocation complete notification message to the target mobility management entity. Step 713: The relocation redirection completion message is exchanged between the source mobility management entity and the target mobility management entity. Step 714: The target mobility management entity sends a PDP context update request message to the source offload gateway. Step 715: The source offload gateway determines the handover mode according to the service type. For example, if the service continuity requirement is low, the handover mode of FIG. 6 is used, and step 615 to step 621 are performed; otherwise, the following step 716 is performed. Step 716: The source offload gateway initiates a PDP context update response to the target mobility management entity. Embodiment 5 FIG. 9 is a flowchart of a location update process performed by a terminal when a mobility management entity changes according to the scenario of the system architecture of FIG. 1 according to the present invention. The specific steps are described as follows: Step 801: The terminal sends a routing area update request to the target mobility management entity via the target wireless side network element.

Step 802: The target mobility management entity sends a context request message to the source mobility management entity. Step 803: The source mobility management entity sends a context response message to the target mobility management entity. Step 804: The target mobility management entity sends a context accept message to the source mobility management entity. Step 805: The target mobility management entity initiates a PDP context update request to the source offload gateway. Step 806: The source offload gateway selects a target offload gateway, and the selection manner may be: selecting by using terminal location information. Step 807: The source offload gateway sends a PDP context creation request to the target offload gateway, and carries the access gateway information. Step 808: The target offload gateway sends a PDP context update request to the access gateway. Step 809, the access gateway replies with a PDP context update response. Step 810: The target offload gateway returns a PDP context establishment response to the source offload gateway. Step 811: The source offload gateway initiates a PDP context update response to the target mobility management entity, and carries the target offload gateway information. Step 812: The target mobility management entity and the authentication authorization database perform location update and subscription acquisition. The source mobility management entity and the authentication authorization database perform a location cancellation process. Step 813: The target mobility management entity initiates a tracking area update accept message to the terminal via the target wireless side network element. Step 814: The terminal replies to the tracking area update completion message. Embodiment 6 FIG. 10 is a flowchart of a location update process performed by a terminal when a mobility management entity does not change according to the scenario of the system architecture of FIG. 1 according to the present invention. The specific steps are described as follows: Step 8a01: The terminal sends a routing area update request message to the mobility management entity via the target radio side network element. Step 8a02: The target mobility management entity initiates a PDP context update request to the source offload gateway. Step 8a03: The source offload gateway selects a target offload gateway, and the selection manner may be: selecting by using terminal location information. Step 8a04: The source offload gateway sends a PDP context creation request to the target offload gateway, and carries the access gateway information. In step 8a05, the target offload gateway sends a PDP context update request to the access gateway. In step 8a06, the access gateway replies with a PDP context update response. In step 8a07, the target offload gateway replies to the source offload gateway with a PDP context setup response. In step 8a08, the source offload gateway initiates a PDP context update response to the target mobility management entity, and carries the target offload gateway information. In step 8a09, the mobility management entity initiates a tracking area update accept message to the terminal via the target wireless side network element. In step 8al0, the terminal replies to the tracking area update completion message. Embodiment 7 FIG. 11 is a flow chart showing the process of requesting a service when a terminal is switched from an idle state to a connected state based on the system architecture of FIG. 1. The specific steps are as follows: Step 901: The terminal sends a Radio Resource Control (Radio Resource Control, RRC for short) connection establishment request to the radio side network element. Step 902: The radio side network element performs RRC connection establishment. Step 903: The terminal sends a service request message to the mobility management entity via the radio side network element. Step 904: The mobility management entity sends a radio bearer assignment request to the radio side network element, and the mobility management entity, the radio side network element, and the terminal perform a radio bearer assignment and establishment process. Step 905: The mobility management entity sends a PDP context update request message to the source offload gateway. Step 906: The source offload gateway selects a target offload gateway, and the selection manner may be: selecting by using terminal location information. Step 907: The source offload gateway sends a PDP context creation request to the target offload gateway, and carries the access gateway.

Step 908: The target offload gateway sends a PDP context update request to the access gateway, step 909, and the access gateway replies with a PDP context update response. Step 910: The target offload gateway returns a PDP context setup response to the source offload gateway. Step 911: The source offload gateway initiates a PDP context update response to the mobility management entity, and carries the target offload gateway information. Step 912: The mobility management entity may update the locally saved offload gateway information, and update the radio bearer to the radio side network element to carry the target offload gateway information. Embodiment 8 In this embodiment, communication can be realized by a wireless connection and a wired connection. FIG. 12 is a block diagram of a preferred structure of a source offload gateway according to an embodiment of the present invention, including: a receiving unit 1202, configured to receive an information update request sent by a mobility management entity when a terminal performs a mobility event; 1204, in communication with the receiving unit 1202, configured to create information to the target offload gateway; the transmitting unit 1206, in communication with the creating unit 1204, configured to send an information update response to the mobility management entity after the information is created, where The information update response carries information of the target offload gateway. In the preferred embodiment, information such as a PDP context is created by the source offload gateway to the target offload gateway, and an information update response such as a PDP update context response is sent to the mobility management entity, thereby solving the problem that the existing mobile process cannot be completed. The problem of the switching function of the offload gateway ensures the continuity of the service when the terminal switches from the source offload gateway to the target offload gateway, so as to effectively enhance the user experience. Preferably, the mobility event comprises one of the following: a handover, a location update, or a service request. In the preferred embodiment, the utility of the present invention is increased by the definition of different mobility events. Preferably, the information update request includes one of the following: an update PDP context request, a bearer update request; the creation information includes one of the following: creating a PDP context, establishing a bearer; and the information update response includes one of the following: updating the PDP Context response, hosting update response. In the preferred embodiment, the gateway relocation method of the present invention can be applied to different scenarios. Preferably, the source offload gateway is a offload gateway used before the terminal is switched or before the location is updated, and the target offload gateway is a offload gateway used after the terminal is switched or after the location is updated. Preferably, in the case that the terminal performs handover, if the mobility management entity before and after the handover of the terminal changes, the mobility management entity that sends the information update request and receives the information update response is the terminal The switched mobility management entity. In the preferred embodiment, the correct transmission and continuity of the service of the terminal is ensured by communicating with the mobility management entity after the terminal handover. Preferably, the source offloading gateway further includes: a determining unit 1208, configured to communicate with the receiving unit 1202, and configured to: after receiving the information update request sent by the mobility management entity, determine a type of the service transmitted by the terminal; the notification unit 1210, The creating unit 1204 is configured to notify the creating unit 1204 to perform the step of creating information to the target offload gateway when it is determined that the transmitted service is a service with low business continuity. Preferably, the determining unit 1208 is in communication with the notifying unit 1210. In the preferred embodiment, the step of creating information to the target offload gateway by performing the source offload gateway on the service with low service continuity can better ensure the continuity of the service with low service continuity. Preferably, after the source offload gateway determines the type of the transmitted service, if the determining unit 1208 determines that the transmitted service is not a service with low service continuity, the notification unit 1210 notifies the creating unit 1204 not to perform the Describe the step of the source offload gateway creating information to the target offload gateway, and sending an information update response to the mobility management entity. In the preferred embodiment, the step of creating the information to the target offload gateway by the source offload gateway is not performed on the service whose type is not the service continuity is low, and the continuity of the service with low service continuity can be better ensured. Preferably, the source offload gateway and the target offload gateway are one of the following: 1) ISGW; 2) L-SGW and L-PGW; or 3) L-PGW. Preferably, the source offload gateway and the target offload gateway are both ISGWs, or L-SGWs and L-PGWs, respectively, or both are L-PGWs. With the present embodiment, the applicability of the present invention is increased. In various embodiments of the present invention, the offload gateway information may be one or more of the following: a traffic distribution gateway identifier, a traffic distribution gateway address. In order to simplify the description, the above embodiment only illustrates the manner in which the serving gateway performs relocation in the IP offload connection communication system by taking the case of FIG. 1 as an example. In the case of the system of FIG. 2, either the E-UTRAN or the UTRAN system, the update PDP context request can be replaced with a bearer update request, the created PDP context is replaced with a bearer, and the updated PDP context response is replaced with a bearer update response. The process of relocating the traffic distribution gateway is similar to that of the foregoing embodiment, and will not affect the description of the present invention, and therefore will not be described again. When the terminal performs the mobility event, the source offload gateway receives the information update request sent by the mobility management entity; the source offload gateway creates information to the target offload gateway; and the source offload gateway sends an information update response to the mobility management entity. The update PDP context response carries information of the target offload gateway. The information update request includes one of the following: an update PDP context request, a bearer update request. The creation information includes one of the following: Create a PDP context, establish a bearer. The information update response includes one of the following: Update PDP context response, bearer update response. In all the above embodiments, the offload gateway may be an ISGW, may be an L-SGW and an L-PGW, may be a separate L-PGW, may be an L-GGSN and an L-SGSN, and may be a separate L-GGSN, and may be It is a data offloading function entity, which can be a local broadband access server (L-BRAS), an access controller (AC), or an evolved packet data gateway (Evolved Packet). Data Gateway (abbreviated as ePDG), which can be a Packet Data Gateway (PDG). The offload gateway includes a split access gateway and/or a offload service gateway; the offload access gateway is an L-PGW or an L-GGSN or an L-BRAS; and the offload service gateway is an L-SGW or an L-SGSN or an AC, or ePDG, or PDG. The wireless side network element may be a base station, a home base station, a radio network controller (Radio Network Controller, RNC for short), a traffic distribution gateway, a traffic distribution function entity, a home base station gateway, and an access point (AP). The mobility management entity may be an MME, a Mobile Switching Center (MSC), a GPRS Service Support Point (SGSN), a home base station gateway, and an AC. The access gateway may be a core network access gateway, and may be a split access gateway; the service gateway may be a core network service gateway, and may be a offload service gateway. The core network access gateway is a P-GW, or a Gateway GPRS Support Node (GGSN), or a Broadband Remote Access Server (BRAS); the core network service gateway is S- GW, or SGSN, or AC, or ePDG, or PDG. IP offloading can be local IP access to the user's local network, local IP access to the company's local network, local IP access to the Internet, Internet traffic shunting, and specific IP data offloading. The information of the offload gateway may be a Fully Qualified Domain Name (FQDN) or/and an IP address. It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from this The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A gateway relocation method, including:

The source offload gateway receives the information update request sent by the mobility management entity when the terminal performs the mobility event;

The source offload gateway creates information to the target offload gateway;

The source offload gateway sends an information update response to the mobility management entity, where the information update response carries information of the target offload gateway.

2. The method of claim 1, wherein the mobility event comprises one of: a handover, a location update, or a service request.

3. The method according to claim 1, wherein the information update request comprises one of: updating a PDP context request, a bearer update request; the creating information comprises one of: creating a PDP context, establishing a bearer; The information update response includes one of the following: Update PDP Context Response, Host Update Response.

The method according to claim 1, wherein the source offload gateway is a offload gateway used before the terminal switches or before the location update, and the target offload gateway is after the terminal is switched or after the location is updated. The shunt gateway used.

The method according to claim 4, wherein, in the case that the terminal performs handover, if the mobility management entity before and after the handover of the terminal changes, sending the information update request and receiving the information update The responding mobility management entity is a mobility management entity after the terminal is switched.

The method according to claim 1, wherein, after receiving the information update request sent by the mobility management entity, the source offloading gateway further includes:

Determining, by the source offload gateway, a type of service transmitted by the terminal;

And performing the step of creating information by the source offload gateway to the target offload gateway if the transmitted service is a service with low service continuity.

The method according to claim 6, wherein after the source offload gateway determines the type of the transmitted service, the method further includes: If the transmitted service is not a service with low service continuity, the source offload gateway does not perform the step of creating information by the source offload gateway to the target offload gateway, and sends the information update to the mobility management entity. response.

The method according to claim 1, wherein the source offload gateway and the target offload gateway are one of: an ISGW; an L-SGW and an L-PGW; or an L-PGW.

9. A source offload gateway, comprising:

a receiving unit, configured to receive an information update request sent by the mobility management entity when the terminal performs a mobility event;

Create a unit, set to create information to the target offload gateway;

And a transmitting unit, configured to send an information update response to the mobility management entity after the information is created, where the information update response carries information of the target offload gateway.

The source offload gateway according to claim 9, wherein the source offload gateway is a offload gateway used before the terminal switches or before the location update, where the target offload gateway is after the terminal is switched or The offload gateway used after the location is updated.

11. The source offload gateway according to claim 9, further comprising:

a determining unit, configured to determine a type of the service transmitted by the terminal after receiving the information update request sent by the mobility management entity;

The notifying unit is configured to, when determining that the transmitted service is a service with low service continuity, notify the creating unit to perform the step of creating the information to the target offload gateway.