WO2011020408A1

WO2011020408A1 - System and method for releasing local ip access connection

Info

Publication number: WO2011020408A1
Application number: PCT/CN2010/075704
Authority: WO
Inventors: 霍玉臻; 周娜
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-08-21
Filing date: 2010-08-04
Publication date: 2011-02-24
Also published as: CN101998370B; CN101998370A

Abstract

A method for releasing Local Internet Protocol Access (LIPA) connection, which is used to release invalid LIPA connection after the change of Mobility Management Entity (MME), includes the following steps: the original MME serving the User Equipment (UE) before the change obtains the identification information of the device serving the UE after the change, and judges whether the LIPA connection is invalid according to the identification information of the device serving the UE after the change; or the target MME serving the UE after the change obtains the identification information of the device serving the UE before the change, and judges whether the LIPA connection is invalid according to the identification information of the device serving the UE before the change; and said original MME releases the invalid LIPA connection. The present invention also provides a system for releasing LIPA connection. The present invention solves the problem of how to release the invalid connection brought after the change of MME.

Description

Release system and method for local IP access connection

TECHNICAL FIELD The present invention relates to the field of mobile communications, and in particular, to a system and method for releasing a local IP access connection.

Background technique

The 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS) is an Evolved Universal Terrestrial Radio Access Network (Evolved Universal Terrestrial Radio Access Network). E-UTRAN), Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW or PDN) GW), Home Subscriber Server (HSS), 3GPP Authentication, Authorization and Accounting (AAA), Policy and Charging Rules Function (Policy and Charging Rules Function) , referred to as PCRF) entity and other supporting nodes. 1(a), 1(b) and 1(c) are schematic diagrams of a system architecture of a prior art EPS. As shown in Figure 1 (a), Figure 1 (b), and Figure 1 (c), the Mobility Management Unit (MME) is responsible for mobility management, non-access stratum signaling processing, and user mobility management context management. Related work. The access gateway includes an S-GW and a P-GW. The 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 the paging waiting data. The P-GW is a border gateway between the EPS and the Packet Data Network (PDN) network, and is responsible for PDN access and forwarding data between the EPS and the PDN. The authentication authorization server includes the HSS and the 3GPP AAA. The PCRF entity is a policy and charging rule function entity. The receiving interface Rx is connected to the service network protocol (Internet Protocol, IP for short) service network to obtain service information. In addition, it is obtained. Connect to the gateway device in the network through the Gx/Gxa/Gxc interface, and initiate the establishment of the IP bearer to ensure the service quality of the service data. (Quality of Service, QoS for short), and charge control. 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. The home base station can be directly connected to the core network, or can be accessed to the core network through the home base station gateway, as shown in Figure 1 (b) and Figure 1 (c). 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. The access gateway may be an S-GW, a P-GW, a Serving General Packet Radio Service (GPRS) Support Node (SGSN) or a Gateway GPRS Support Node (GGSN). The local access gateway can be a local SGW (Local SGW, L-SGW for short), a local PGW (Local PGW, L-PGW for short), a virtual SGW (Virtual SGW for short, V-SGW for short), or a virtual PGW (for example). Virtual PSGW (referred to as V-PGW for short), local GGSN (Local GGSN, L-GGSN for short) or data offloading functional entity. Local access gateway and wireless side entity (wireless side network element shown in the figure) ), it can also be set up with the home base station gateway, and can also be located near the wireless side entity or the home base station gateway. In order to implement local IP access (Local IP Access, referred to as LIPA) function, that is, the terminal is to other IP devices of the home network or Local access to the Internet has been added to the local access gateway, as shown in Figure 1 (a), Figure 1 (b), Figure 1 (c) and Figure 2. Additional access to the local access gateway provides access to local IP With strong support, the local access gateway can be combined with the wireless side network element or near the wireless side network element, or with the home base station gateway or at the home base station gateway attachment. Figure 2 shows the mobile communication network architecture. In the local IP access and the traditional core network IP access data flow path. For the terminal supporting local IP access, the traditional core network IP access data path and the local IP access data path can be established. As shown in Figure 2, for the local IP The access connection, the local IP access data path from the terminal to the local access gateway (such as L-SGW or L-PGW) via the wireless side network element or the home base station gateway, the data transmission does not go through the core network. Local access to IP devices or the Internet, you can establish two connections, the first local IP Access the data path directly to the Internet (Internet LIPA connection). The second local IP access data path directly accesses other IP devices on the home network (home network LIPA connection). Due to the particularity of the LIPA connection (the data stream is transmitted directly from the wireless side network element or the home base station gateway), when the terminal needs to initiate a routing area update request after the idle state or the terminal switches, only the core network connection or the local access gateway (eg L-PGW or L-GGSN) The unchanged LIPA connection can be activated or switched, and other LIPA connections must be released. However, when the terminal initiates the routing area update, the mobility management entity (Mobility Management Element) for the terminal service may change. At this time, according to the current process, the original mobility management entity serving the terminal before and after the transformation and the target mobile respectively The SMS cannot determine whether the local access gateway connected to the LIPA of the terminal has changed. Therefore, the LIPA connection changed by the local access gateway cannot be released normally. When the terminal switches and the mobility management entity changes, according to the existing process, it will try to create the LIPA connection of the terminal, but only the local access gateway (such as L-PGW or L-GGSN) has not changed the LIPA connection. It should be created. In summary, the industry urgently needs to provide a system and method for releasing local IP access connections to solve the above problems caused by the change of the mobility management entity.

SUMMARY OF THE INVENTION The technical problem to be solved by the present invention is to provide a local IP access connection release system and method for releasing a local IP access connection after a mobility management entity changes. In order to solve the above technical problem, the present invention first provides a release of a local IP access connection.

And determining, according to the identifier information of the device that is used to serve the terminal, the local IP access connection is invalid, where the identifier information of the device serving the terminal after the change includes serving after the change Target local access gateway identification information of the terminal, or target radio side network element identification information or target home base station gateway identification information; or

The identification information of the device at the end is determined according to the identification information of the device serving the terminal before the change Whether the local IP access connection is invalid, and the identification information of the device serving the terminal before the change includes the original local access gateway identification information serving the terminal before the change, or the original wireless side network element identification information, Or the original home base station gateway identification information;

The failure means that the local IP access connection is affected in a triggering event, and the local IP access connection cannot be used continuously, that is, the local IP access connection needs to be released. Preferably, the change comprises a change of a mobility management entity caused by handover or tracking area update of the terminal in a long term evolution system, or a terrestrial wireless access system by a universal mobile communication system

Preferably, before the step of acquiring the identification information of the device serving the terminal after the change in the tracking area update process, the method further includes: the terminal sending a tracking area update request message to the target wireless side network element After the target radio side network element selects the target mobility management entity, the tracking area update request message is forwarded to the target mobility management entity; and the device that serves the terminal after the change is obtained. The step of the identification information includes: when the target wireless side entity supports local IP access, the target mobility management entity sends a context request message to the original mobility management entity, where the context request message carries the target local The determining information of the access gateway or the target wireless side entity; determining whether the local IP access connection is invalid comprises: determining, by the original mobility management entity, the local information according to the identification information of the target local access gateway or the target wireless side entity Whether the IP access connection is invalid; or in the routing area update process, obtain the changed service Before the step of performing the identification information of the device of the terminal, the method further includes: the terminal sending a routing area update request message to the target wireless side network element, where the target wireless side network element is selected by the terminal The target mobility management entity forwards the routing area update request message to the target mobility management entity; and the step of acquiring the identification information of the device serving the terminal after the change includes: the target wireless side entity support When the local IP access is performed, the target mobility management entity requests a message from the context of the original mobility management entity, where the context request message carries the identifier information of the target local access gateway or the target wireless side entity; The step of invalidating the IP access connection includes: determining, by the original mobility management entity, the local information according to the identification information of the target local access gateway or the target wireless side entity Whether the IP access connection is invalid. Preferably, the step of determining, by the original mobility management entity, whether the local IP access connection is invalid according to the identifier information of the target local access gateway or the target radio side entity comprises: the original mobility management entity receiving the After the context request message, it is checked whether there is a local IP access connection; if yes, it is further determined whether the identity information of the target local access gateway is consistent with the identity information of the original local access gateway, and the inconsistency indicates a local IP access connection. If the fault persists, or if yes, it is further determined whether the identifier information of the target radio side entity is consistent with the identifier information of the original radio side entity, and if the inconsistency indicates that the local IP access connection is invalid. Preferably, the step of acquiring the identification information of the device serving the terminal after the change further comprises: when the target wireless side entity does not support local IP access, the target mobility management entity sends the original mobility management entity to the original mobility management entity a context request message, the context request message does not carry the identifier information of the target local access gateway or the target radio side entity, or carries indication information that does not support local IP access; and the step of determining whether the local IP access connection is invalid includes And determining, by the original mobility management entity, the context request message that does not carry the identifier information of the target local access gateway or the target radio side entity, or according to the context request message that carries the indication information, The local IP access connection is invalid. Preferably, in the process of the handover or the redirection, the request message of the device serving the terminal is changed, and the handover request message carries the identifier information of the target local access gateway; determining whether the local IP access connection is invalid. The step includes: after the original mobility management entity receives the handover request message, determining, according to the identifier information of the target local access gateway, whether the local IP access connection is invalid. Preferably, the step of determining whether the local IP access connection is invalid according to the identifier information of the target local access gateway includes: in the handover process or the redirection process, the handover request message does not carry the target local The identification information of the access gateway indicates that the local IP access connection is invalid. Preferably, the identification information of the target local access gateway is determined, and the local IP access is determined. The step of the failure of the connection includes: after the original mobility management entity receives the handover request message, it checks whether there is a local IP access connection, and further determines the identification information of the target local access gateway and the original local Whether the identification information of the access gateway is consistent. If the information is inconsistent, the local IP access connection is invalid. Preferably, after the step of determining whether the local IP access connection is invalid, the method further includes: the bearer information sent by the management entity includes a valid local IP access connection; the valid means that a trigger event does not affect the local IP access connection, That is, the local IP access connection still applies; the triggering event includes one or more of handover, relocation, routing area update, tracking area update, capability redirection, and subscription change. Preferably, before the step of acquiring the identification information of the device serving the terminal before the tracking area update process, the method further includes: the terminal sending a tracking area update request message to the target wireless side network element After the target radio side network element selects the target mobility management entity, the tracking area update request message is forwarded to the target mobility management entity; the target mobility management entity goes to the The original mobility management entity sends a context request message; the step of acquiring the identity information of the device serving the terminal before the change includes: the local IP access is connected, and the context response message carries the original local access gateway or the original The step of determining whether the local IP access connection is invalid or not includes: determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identifier information of the original local access gateway or the original wireless side entity In the routing area update process, obtaining an identification letter of the device serving the terminal before the change The method further includes: the terminal sending a routing area update request message to the target wireless side network element, where the target wireless side network element selects the target mobility management entity for the terminal, The routing area update request message is forwarded to the target mobility management entity; the target mobility management entity sends a context request message to the original mobility management entity; and acquiring identification information of a device serving the terminal before the change The step of the method includes: when the local IP access connection exists, the original mobility management entity sends a context response message to the target mobility management entity, where the context response message carries the original local access gateway or the original wireless side entity Identification information The step of invalidating the IP access connection includes: determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identification information of the original local access gateway or the original wireless side entity. Preferably, the step of determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identifier information of the original local access gateway or the original wireless side entity comprises: receiving, by the target mobility management entity, the context response After the message, it is checked whether there is a local IP access connection; if it is determined, whether the identification information of the original local access gateway is consistent with the identification information of the target local access gateway, and the inconsistency indicates that the local IP access connection is invalid, or If the identifier information of the original wireless side entity is consistent with the identifier information of the target wireless side entity, the local IP access connection is invalid. If the local IP access connection is not present, the local IP access connection is indicated. Invalid. Preferably, the step of acquiring the identification information of the device serving the terminal before the change further comprises: in the context response message sent by the original mobility management entity to the target mobility management entity when there is no local IP access connection The information of the original local access gateway or the original wireless side entity is not carried, or the indication information that the local IP access connection does not exist is carried. Preferably, in the handover process, the identifier information of the device serving the terminal after the change is acquired, and the original mobility management entity selects the target mobility management entity for the terminal, and then the target mobility management entity Sending a relocation forward request message carrying the identity information of the original local access gateway or the original radio side entity, and the target mobility management entity switches a request acknowledgement message to the target radio side network, where the handover request is confirmed The message carries the identification information of the target local access gateway or the target wireless side entity; the step of determining whether the local IP access connection is invalid includes: the target mobility management entity according to the target local access gateway or the target wireless side entity Determining, by the identifier information, whether the local IP access connection is invalid; in the redirection process, acquiring a handover request message of the identification information of the step element of the identifier information of the device serving the terminal after the change, the original mobility management entity is The terminal selects the After the target mobility management entity sends a relocation forward request message carrying the identity information of the original local access gateway or the original radio side entity to the target mobility management entity, the target mobility management entity The target radio side network element sends a relocation request message, and the target radio side network element sends a relocation request confirmation message to the target mobility management entity, where the relocation request confirmation message carries the target local access gateway or The step of determining whether the local IP access connection is invalid or not includes: determining, by the target mobility management entity, whether the local IP access connection is based on the identifier information of the target local access gateway or the target wireless side entity Invalid. Preferably, the step of determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identifier information of the target local access gateway or the target radio side entity comprises: the target mobility management entity receiving the After re-locating the forward request message, it is checked whether there is a local IP access connection, and if it is determined, whether the identification information of the original local access gateway is consistent with the identification information of the target local access gateway, and the local IP is inconsistent. The access connection has failed.

Preferably, after the step of determining whether the local IP access connection is invalid, the method further comprises serving the general wireless packet service support in the managed unit, the mobile switching center in the global mobile communication system or the universal mobile communication system in the terrestrial wireless access system. node. Preferably, the target local access gateway identifier information includes an address of the target local access gateway or identifier information dedicated to the target local access gateway; the target radio side network element identifier information includes the target The address of the wireless side network element or the identification information dedicated to the target wireless side network element; the target home base station gateway identification information includes an address of the target home base station gateway or an identifier dedicated to identifying the target home base station gateway The information of the original local access gateway includes the address of the original local access gateway or the identification information dedicated to the original local access gateway; the original wireless side network element identification information includes the original wireless The address of the side network element or dedicated to the target Identifying the identification information of the original wireless side network element; the original home base station gateway identification information includes an address of the original home base station gateway or identification information dedicated to identifying the original home base station gateway. The triggering event includes one or more of handover, relocation, routing area update, tracking area update, capability redirection, and subscription change. In order to solve the above technical problem, the present invention further provides an original mobility management entity that serves the terminal before the release of the local IP access connection, wherein: the original mobility management entity is configured to: Determining, according to the identification information of the device of the terminal, determining whether the local IP access connection is invalid according to the identification information of the device serving the terminal, and releasing the invalid local IP access connection, where the service is changed after serving The identification information of the device of the terminal includes the target local access gateway identifier information, or the target radio side network element identifier information or the target home base station gateway identifier information; the failure refers to a trigger event to affect the local IP access connection, the local IP The access connection cannot be used continuously, that is, the local IP access connection needs to be released; the triggering event includes one or more of handover, relocation, routing area update, tracking area update, capability redirection, and subscription change. In order to solve the above technical problem, the present invention also provides release of another local IP access connection.

An active management entity, wherein: the target mobility management entity is configured to: obtain identification information of a device serving the terminal before the change, and determine local IP access according to the identification information of the device serving the terminal The identifier information of the device serving the terminal includes the original local access gateway identifier information, or the original radio side network element identifier information or the original home base station gateway identifier information; the failure refers to a trigger event to enable the local IP address. The access connection is affected, the local IP access connection cannot be used continuously, that is, the local IP access connection needs to be released; the triggering event includes one of handover, relocation, routing area update, tracking area update, capability change, and subscription change or Multiple The original mobility management entity is configured to release the failed local IP access connection according to the local IP access failure indication. Compared with the prior art, the system and method for releasing the local IP access connection provided by the present invention solves the problem of how to release the failed connection caused by the change of the mobility management entity.

1(a), FIG. 1(b) and FIG. 1(c) are schematic diagrams of a mobile communication network connection in the prior art; FIG. 2 is a schematic diagram of a local IP access data flow in a mobile communication system in the prior art; FIG. 4 is a schematic flowchart of a second embodiment of a method according to the present invention; FIG. 5 is a schematic flowchart of a third embodiment of the method according to the present invention; Figure 6 is a schematic flow chart of a fifth embodiment of the method of the present invention; Figure 7 is a schematic flowchart of a sixth embodiment of the method of the present invention; Figure 8 is a schematic flowchart of a seventh embodiment of the method of the present invention; A schematic diagram of the flow of the eighth embodiment of the inventive method.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and embodiments, by which the present invention is applied to the technical means to solve the technical problems, and the realization of the technical effect can be fully understood and Implementation. In the present invention, the local IP access may be a local IP access user local network, a local IP access company local network, a local IP access Internet, a diversion operation of the Internet service, and a specific IP data offload. In the present invention, the effective refers to the local IP access connection is not affected after a certain trigger event (such as one or more of handover, relocation, routing area update, tracking area update, capability change, and subscription change). , ie the local IP access connection still applies. Failure is after a certain trigger event

(For example, one or more of handover, relocation, routing area update, tracking area update, capability change, and subscription change), the local IP access connection is affected, that is, the local IP access connection cannot be used continuously, that is, the local IP Access to the connection needs to be released. The method for releasing a local IP access connection proposed by the present invention, in the process of handover, relocation, tracking area update or routing area update, before the handover, relocation, tracking area update or routing area update, the wireless side network element or The identification information of the target home base station gateway, and determining whether the LIPA connection is invalid according to the identification information; wherein the target local access gateway, the target wireless side network element, and the target home base station gateway are respectively the handover, relocation, tracking area update, or After the routing area is updated, the local access gateway, the wireless side network element, or the home base station gateway serving the terminal; for the failed LIPA connection, the original mobility management entity sends the bearer information that needs to be activated or switched to the handover, relocation, and tracking. When the area update or the routing area is updated, the mobility management entity of the terminal, that is, the target mobility management entity, does not send the bearer information of the failed LIPA connection; or the process of handover, relocation, tracking area update or routing area update In the target mobility management entity, the original local access gateway is obtained. Line side network element identification information of the original home base station or gateway, and based on this identification information, determines whether the LIPA connection failure. For a failed LIPA connection, the target mobility management entity notifies the original mobility management entity that the LIPA connection is invalid. The original local access gateway, the original wireless side network element, and the original home base station gateway are local access gateways, wireless side network elements, or home base stations serving the terminal before the handover, relocation, tracking area update, or routing area update, respectively. Gateway. The identifier information of the target local access gateway includes the address of the target local access gateway or the identifier information that is used to identify the target local access gateway. The identifier information of the target wireless side network element includes the target wireless side network. The address of the element is used to identify the identification information of the target wireless side network element. The identification information of the target home base station gateway includes the address of the target home base station gateway or the identification information dedicated to identifying the target home base station gateway. The identifier information of the original local access gateway includes the address of the original local access gateway or the identifier information that is used to identify the original local access gateway. The identifier information of the original wireless side network element includes the original wireless side network. The address of the element is used to identify the identity information of the original wireless side network element. The identity information of the original home base station gateway includes the address of the original home base station gateway or the identification information dedicated to identifying the original home base station gateway. For a failed LIPA connection, the original mobility management entity releases the LIPA connection. The identification information obtained by the original mobility management entity is delivered by the target mobility management entity. The identification information obtained by the target mobility management entity is delivered by the original mobility management entity. The identifier information of the local access gateway may be an address of the local access gateway or identifier information dedicated to identifying the local access gateway. The identifier information of the radio side network element may be an address of the radio side network element or identifier information dedicated to identifying the radio side network element. The radio side entity may be a base station, a home base station, or a radio network controller (Radio Network Controller, or RNC for short). The Mobility Management Element (Mobility Management Element) can be a Mobility Management Entity (MME) in the LTE system or a Mobile Switching Centre (MSC) in the Global System for Mobile Communications (GSM). Or the Serving GPRS Support Node (SGSN) in the UTRAN system. The local access gateway may be an L-SGW, an L-PGW, an L-GW, a data offloading functional entity or an L-GGSN. The ingress gateway may be an S-GW or an SGSN. In the embodiment of the present invention, when an external L-GW or a data offloading functional entity is used, the L-SGW and the L-PGW do not exist, and the MME may Message interaction with L-GW or data offload function entity, no L-SGW, L-PGW participation. For Universal Mobile Telecommunications System (UMTS), when using external L-GW or data When the function entity is offloaded, the L-GGSN does not exist. In this case, the SGSN performs message interaction with the L-GW or the data offload function entity, and no L-GGSN participates. Figure 3 is a first embodiment of the present invention. The first embodiment of the present invention is a local IP access connection release process in a tracking area update process in a Long Term Evolution (LTE) system, and is combined with the network diagrams shown in FIG. 1( a ), FIG. 1 ( b ), and FIG. 1 ( c ). The first embodiment of the present invention mainly includes the following steps Step 301: The idle state terminal periodically initiates or changes the tracking area list due to the movement to initiate a tracking area update process; the terminal sends a non-access stratum (Non-Access-Stratum, referred to as NAS) message-tracking area update request message to The wireless side network element currently serving the terminal (collectively referred to as the target wireless side network element). After the terminal moves, the target radio side network element may be different from the radio side network element (collectively referred to as the original radio side network element) before the terminal enters the idle state. Step 302: The target radio side network element selects a mobility management entity (collectively referred to as a target mobility management entity) currently serving the terminal for the terminal, and the tracking area update request message is included in the S1 message and sent to the target mobility management entity. If there is a home base station gateway, the tracking area update request is first forwarded to the home base station gateway, and then the home base station gateway selects the target mobility management entity, and sends the tracking area update request message to the target mobility management entity. The mobility management entity is an MME in the LTE system. Step 303: The target mobility management entity obtains an address of the mobility management entity (collectively referred to as the original mobility management entity) before the terminal enters the idle state according to the tracking area update request message, and initiates a context acquisition process to the original mobility management entity. The mobility management entity sends a context request message to the original mobility management entity, and carries the identity information of the target local access gateway or the identity information of the target wireless side entity in the context request message. When the target radio side entity supports local IP access, the message carries the identifier information of the target local access gateway or the target radio side entity identifier information. When the target wireless side entity does not support the local IP access, the message may not carry the identifier information of the target local access gateway or the target wireless side entity identifier information to indicate that the local IP access is not supported; or the indication information is not indicated in the message. Support for local IP access. The identifier information of the local access gateway may be the address of the local access gateway, or the identifier information dedicated to the local access gateway; the identifier information of the wireless side network element may be the address of the wireless side network element, or dedicated The identifier information of the wireless side network element is identified. Step 304: After receiving the context request message, the original mobility management entity checks whether the terminal has a local IP access connection. If yes, it checks whether the LIPA connection of the terminal is affected according to the identifier information or the indication information in the context request message. For the terminal that has the local IP access connection: When the context request message carries the identification information of the target local access gateway, the original mobility management entity checks the identity information and the context request message of the local access gateway of the terminal local IP access connection. Whether the identity information of the target local access gateway carried in the device is consistent. If the identity of the local access gateway connected to the LIPA is unchanged, the LIPA connection of the terminal is not affected. If the local access gateway of the LIPA connection is inconsistent, the local access gateway connected to the LIPA is considered to have occurred. Change, the terminal's LIPA connection needs to be released. The identification information of the local access gateway of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection. When the message carries the identification information of the target wireless side network element, the original mobility management entity checks whether the wireless side network element identification information of the terminal local IP access connection and the identification information of the target wireless side network element carried in the message are consistent. If it is consistent, the terminal is still connected from the original wireless side network element, and the terminal's LIPA connection is not affected; if it is inconsistent, the terminal is considered to be accessed from the new wireless side network element, and the terminal's LIPA connection needs to be released; the terminal local IP access connection The wireless side network element identification information is saved in the context when the terminal establishes the LIPA connection, and is not released when the terminal enters the idle state. When the message does not carry any identification information or carries the indication information that does not support local IP access, it indicates that the target wireless side network element does not support local IP access, and the local IP access connection of the terminal needs to be released. Step 305: The original mobility management entity includes the context information of the terminal in the context response message, and sends the information to the target mobility management entity, where the context response message carries the bearer information to be activated or the bearer information to be activated. As a result of the judgment, the local IP access connection needs to be released, and the context response message does not need to carry the bearer information of the connection, so as to complete the release of the failed connection. Step 306: The target mobility management entity may initiate an authentication and authentication process for the terminal. Step 307: The target mobility management entity responds to the original mobility management entity with a context confirmation message. Steps 308, 309, the target mobility management entity initiates a session establishment and bearer update process of the core network connection. Step 310: The target mobility management entity initiates a location update procedure to the authentication authority server. Step 311: The authentication authorization server initiates a location deletion process to the original mobility management entity. In step 312, the original mobility management entity may initiate a session deletion to the core network S-GW. Step 313: The original mobility management entity initiates a LIPA session deletion process to the original local access gateway according to the determination result of step 304. This step may be performed at any time after step 304. Steps 314, 315, the target mobility management entity sends a routing area update to the terminal. In this embodiment, the local access gateway is an L-PGW and an L-SGW. In this embodiment, the L-PGW and the L-SGW are located at or near the radio side network element, and the mobility management entity is changed. The release process of the terminal local IP access connection. When the L-SGW does not exist, the connection release process is similar to this process. The difference is that the mobility management entity needs to directly interact with the L-PGW. The L-SGW does not participate in the process. Said. The local access gateway can also be an L-GW or a data offloading functional entity. When the L-SGW is located in the core network, the release process is the same as this process, except that the mobility management entity needs to exchange messages with the SGW of the core network, and then the L-PGW is notified by the core network SGW, instead of being notified by the L-SGGW to the L-PGW. , will not be detailed here.

Figure 4 is a flow chart showing a second embodiment of the present invention. The second embodiment of the present invention is a local IP access connection release process in another tracking area update process in the LTE system, and the network diagram shown in FIG. 1 (a), FIG. 1 (b) and FIG. 1 (c), the present invention The second embodiment mainly includes the following steps: Step 401: The terminal in the idle state periodically or changes the tracking area list due to the movement, and initiates a tracking area update process. The terminal sends a non-access stratum (Non-Access-Stratume, NAS for short) message-tracking area update request message to the radio side network element currently serving the terminal (collectively referred to as the target radio side network element); when the terminal moves, the The wireless side network element may be different from the wireless side network element (collectively referred to as the original wireless side network element) before the terminal enters the idle state. Step 402: The radio side network element selects, for the terminal, the mobility management entity currently serving the terminal. The target mobility management entity is included, and the tracking area update request message is included in the initial user message and sent to the target mobility management entity; if the home base station gateway exists, the initial user message is first forwarded to the home base station gateway. The target mobility management entity is then selected by the home base station gateway and the initial user message is sent to the target mobility management entity. The mobility management entity in the LTE system is a mobility management unit (MME). Step 403: The target mobility management entity obtains an address of the mobility management entity (collectively referred to as the original mobility management entity) before the terminal enters the idle state according to the tracking area update request message, and sends a context request message to the original mobility management entity to initiate Context acquisition process. Step 404: After receiving the context request message, the original mobility management entity includes the context information of the terminal in the context response message, and sends the identifier to the target mobility management entity, and carries the identifier of the original local access gateway in the context response message. Information or identification information of the original wireless side entity. When the terminal has a local IP access connection, the context response message carries the identity information of the original local access gateway or the original wireless side entity identification information. When the terminal does not have a local IP access connection, the identifier information of the original local access gateway or the original wireless side entity identification information may not be carried in the context response message to indicate that there is no local IP access connection; or the indication information is passed in the message. Indicates that there is no local IP access connection. The identifier information of the local access gateway may be the address of the local access gateway, or the identifier information dedicated to the local access gateway; the identifier information of the wireless side network element may be the address of the wireless side network element, or dedicated The identifier information of the wireless side network element is identified. The identification information of the original local access gateway of the terminal local IP access connection is established in the terminal.

The LIPA connection is saved in the context; the original radio side network element identification information of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection, and is not released when the terminal enters the idle state. Step 405: After receiving the context response message, the target mobility management entity checks whether the terminal has a local IP access connection. If yes, it checks whether the LIPA connection of the terminal is affected according to the identifier information or the indication information in the context response message. For terminals with local IP access connections: When the context response message carries the identity information of the original local access gateway, the target mobility management entity checks whether the identity information of the target local access gateway and the identity information of the original local access gateway carried in the context response message are consistent. If the agreement is made, the local access gateway connected to the LIPA is not changed, and the LIPA connection of the terminal is not affected. If the local access gateway of the LIPA connection is changed, the LIPA connection of the terminal needs to be released. When the context response message carries the identification information of the original radio side network element, the target mobility management entity checks whether the identification information of the original radio side network element and the identity information of the original radio side network element carried in the context response message are consistent. If the terminal is still connected from the original wireless side network element, the terminal's LIPA connection is not affected. If the terminal is inconsistent, the terminal is considered to be connected from the new wireless side network element, and the terminal's LIPA connection needs to be released. When the context response message does not carry any identification information or carries the indication information that there is no local IP access connection, it indicates that the terminal does not have a local IP access connection. When the context response message carries the identification information, but the target wireless side network element does not support the local

When IP access, the local IP access connection of the terminal needs to be released. Step 406: The target mobility management entity may initiate an authentication and authentication process for the terminal. Step 405 and step 406 in this embodiment have no sequence. Step 407: The target mobility management entity responds to the original mobility management entity with a context confirmation message. According to the determination result of step 405, if the LIPA connection of the terminal needs to be released, the LIPA failure indication is carried in the context confirmation message. Steps 408-415 are the same as steps 308-315. In this embodiment, the local access gateway is an L-PGW and an L-SGW. In this embodiment, the L-PGW terminal local IP access connection release process. When the L-SGW does not exist, the release process is similar to the process. The MME needs to directly interact with the L-PGW. The L-SGW does not participate in the process. The release process is the same as the current process when the L-SGW is located in the core network. Only the MME needs to exchange messages with the SGW of the core network, and then the L-PGW is notified by the core network SGW instead of the L-PGW by the L-SGW. No longer detailed. In addition, the local access gateway may also be an L-GW or a data offloading functional entity. Figure 5 is a flow chart showing a third embodiment of the present invention. The third embodiment of the present invention is a local IP access connection release process in the handover process in the LTE system, and the network diagram shown in FIG. 1 (a), FIG. 1 (b) and FIG. 1 (c), the third embodiment of the present invention The method includes the following steps: Step 501: The wireless side network element determines that the S1 handover needs to be initiated. When the original wireless side network element and the target wireless side network element have interaction, the target wireless side network element can access the local access gateway (target local access). The identification information of the gateway is transmitted to the original radio side network element, or the terminal can report the identification information of the target local access gateway to the original radio side network element. The identifier information of the local access gateway may be an address of the local access gateway or identifier information dedicated to identifying the local access gateway. Step 502: The original radio side network element sends a handover request message to the original mobility management entity, where the handover request message carries the identifier information of the target radio side entity. If the identification information of the target local access gateway is obtained, the information is also carried in the handover request message and transmitted to the original mobility management entity. If there is a home base station gateway, the handover request message is first forwarded to the home base station gateway, and then the home base station gateway sends the handover request message to the original mobility management entity. The mobility management entity is an MME in the LTE system. Step 503: After receiving the handover request message, the original mobility management entity checks whether the terminal has a local IP access connection. If yes, it checks whether the terminal's LIPA connection is affected. For the terminal that has the local IP access connection: When the handover request message carries the identity information of the target local access gateway, the original mobility management entity checks the identity information of the local access gateway of the terminal local IP access connection and the target local access gateway. If the identity information of the terminal is consistent, the local access gateway connected to the terminal LIPA is not changed, and the LIPA connection of the terminal is not affected. If the local access gateway connected to the terminal LIPA has changed, the LIPA connection of the terminal needs to be changed. freed. The identification information of the local access gateway of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection, and is not released when the terminal enters the idle state. When the handover request message does not carry the identification information of the target local access gateway, the terminal's The IP access connection needs to be released.

Or, regardless of whether the target wireless side network element supports local IP access, the local IP access connection needs to be released after the wireless side network element changes. Step 504: The original mobility management entity selects a mobility management entity (collectively referred to as a target mobility management entity) that is a terminal service after the handover, and sends a relocation forward request message to the target mobility management entity, where the relocation is performed. The transfer request message carries bearer information that needs to be switched. According to the judgment result of the step 503, if the terminal local IP access connection needs to be released, the relocation request message does not carry the bearer information of the connection, so as to complete the release of the failed connection. Step 505: The target mobility management entity may initiate a session establishment and forwarding tunnel establishment procedure of the core network connection to the target S-GW. Step 506: The target mobility management entity sends a handover request message to the target radio side network element. Step 507: The target radio side network element responds to the target mobility management entity with a handover request acknowledgement message. Step 508, continuing the normal switching process. In step 509, the terminal may initiate a tracking area update process. Step 510: The original mobility management entity may initiate session deletion and forwarding tunnel deletion to the original S-GW of the core network. Step 511: The original mobility management entity initiates a LIPA session deletion process to the original local access gateway according to the determination result of step 503. This step may be performed at any time after step 503. In step 512, the target mobility management entity may initiate a forwarding tunnel deletion to the core network target S-GW. In this embodiment, the local access gateway is an L-PGW and an L-SGW. In this embodiment, the L-PGW terminal local IP access connection release process. When the L-SGW does not exist, the release process is similar to the process. The MME needs to directly interact with the L-PGW. The L-SGW does not participate in the process. The release process is the same as this process when the L-SGW is located in the core network. Only the MME needs to exchange messages with the SGW of the core network, and then the core network SGW notifies. L-PGW, instead of being notified by the L-SGGW, is not detailed here. The local access gateway may also be an L-GW or a data offloading functional entity. In this embodiment, the original mobility management entity determines whether the terminal LIPA connection is affected. Similar to the embodiment shown in FIG. 3, the target mobility management entity may also perform this determination, similar to the embodiment shown in FIG. It will not be detailed. Other switching processes are similar to this process and will not be detailed here.

Figure 5a is a schematic flow chart of a fourth embodiment of the present invention. The fourth embodiment of the present invention is a process for releasing another local IP access connection in the handover process in the LTE system, and the network diagram shown in FIG. 1(a), FIG. 1(b) and FIG. 1(c), the fourth aspect of the present invention The embodiment mainly includes the following steps: Step 501a: The radio side network element determines that an S1 handover needs to be initiated. Step 502a: The original radio side network element sends a handover request message to the original mobility management entity. If there is a home base station gateway, the handover request message is first forwarded to the home base station gateway, and then the handover request message is sent by the home base station gateway. The original mobility management entity. The mobility management entity is an MME in the LTE system. Step 503a: The original mobility management entity selects a mobility management entity (collectively referred to as a target mobility management entity) that is a terminal service after the handover, and sends a relocation forward request message to the target mobility management entity, and relocates the forwarding The request message carries the identifier information of the original local access gateway or the identifier information of the original wireless side entity. In step 504a, the target mobility management entity may initiate a session establishment and forwarding tunnel establishment procedure of the core network connection to the target S-GW. Step 505a: The target mobility management entity sends a handover request message to the target radio side network element. Step 506a: The target radio side network element responds to the target mobility management entity with a handover request acknowledgement message, and carries the target local access gateway identifier in the handover request acknowledgement message. Step 507a, the same as step 405; but the message therein is a handover request acknowledgement message. In step 508a, the target mobility management entity responds to the relocation forward response message. According to the steps As a result of the determination of 507a, the terminal local IP access connection needs to be released, and the relocation forward response message carries the LIPA connection failure indication information, indicating that the LIPA connection is released. Step 509a: The target mobility management entity initiates a bearer deletion process for the LIPA connection. After the step 505a, the resources reserved by the radio side network element for the LIPA are deleted. Steps 510a-514a are the same as steps 508-512, respectively.

Figure 6 is a flow chart showing a fifth embodiment of the present invention. The fifth embodiment of the present invention is another local IP access connection release process in the routing area update process in the UTRAN system, and the network diagram shown in FIG. 1(a), FIG. 1(b) and FIG. 1(c), the present invention The fifth embodiment mainly includes the following steps: Step 601: A terminal in an idle state initiates a routing area update procedure periodically or due to a change in a routing area caused by the movement. The terminal sends a non-access stratum (NAS) message - a routing area update request to the radio side network element currently serving the terminal (collectively referred to as the target radio side network element). After the terminal moves, the wireless side network element may be different from the wireless side network element (collectively referred to as the original wireless side network element) before the terminal enters the idle state. Step 602: The radio side network element selects, for the terminal, the mobility management entity currently serving the terminal (collectively referred to as the target mobility management entity), and the routing area update request message is included in the initial user message and sent to the target mobility management entity. If there is a home base station gateway, the initial user message is first forwarded to the home base station gateway, and then the home base station gateway selects the target mobility management entity, and sends the initial user message to the target mobility management entity. The mobility management entity in the UTRAN system is an SGSN. Step 603: The target mobility management entity obtains an address of the mobility management entity (collectively referred to as the original mobility management entity) before the terminal enters the idle state according to the routing area update request message, and initiates a context acquisition process to the original mobility management entity. The target mobility management entity sends a context request message to the original mobility management entity, and carries the identifier information of the target local access gateway or the identifier information of the target wireless side entity in the context request message. When the target wireless side entity supports local IP access, the target local message is carried in the context request message. The identification information of the access gateway or the target wireless side entity identification information. When the target wireless side entity does not support the local IP access, the identifier information of the target local access gateway or the target wireless side entity identification information may not be carried in the context request message, indicating that the local local access identifier information is not supported.

IP access; or indication in the context request message indicates that local IP access is not supported. The identifier information of the local access gateway may be an address of the local access gateway or identifier information dedicated to identifying the local access gateway. The identifier information of the radio side network element may be an address of the radio side network element or identifier information dedicated to identifying the radio side network element. Step 604: After receiving the context request message, the original mobility management entity checks whether the terminal has a local IP access connection. If yes, it checks whether the LIPA connection of the terminal is affected according to the identifier information or the indication information in the context request message. For the terminal that has the local IP access connection: When the context request message carries the identification information of the target local access gateway, the original mobility management entity checks the identification information of the local access gateway of the terminal local IP access connection and carries the message. Whether the identity information of the target local access gateway is consistent. If the identity is the same, the local access gateway connected to the LIPA is not changed, and the LIPA connection of the terminal is not affected. If the local access gateway of the LIPA connection is changed, the local access gateway of the LIPA connection is changed. The terminal's LIPA connection needs to be released. The identification information of the local access gateway of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection. When the context request message carries the identifier information of the target radio side network element, the original mobility management entity checks the radio side network element identifier information of the terminal local IP access connection and the identifier of the target radio side network element carried in the context request message. If the information is consistent, if the terminal is still connected from the original wireless side network element, the terminal's LIPA connection is not affected. If the terminal is not connected, the terminal is considered to be connected from the new wireless side network element, and the terminal's LIPA connection needs to be released. The radio side network element identification information of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection, and is not released when the terminal enters the idle state. When the context request message does not carry any identification information or carries the indication information that does not support local IP access, it indicates that the target radio side network element does not support local IP access, and the local IP access connection of the terminal needs to be released. Step 605: The original mobility management entity includes the context information of the terminal in the context response message, and sends the information to the target mobility management entity. The context response message carries the bearer information to be activated or the bearer information to be activated. According to the judgment result of the step 604, when the local IP access connection needs to be released, the bearer information of the connection is not carried in the context response message, and the release of the failed connection is completed. Step 606: The target mobility management entity may initiate an authentication and authentication process for the terminal. Step 607: The target mobility management entity responds to the original mobility management entity with a context confirmation message. Step 608: The target mobility management entity initiates a Packet Data Protocol (PDP) context update procedure of the core network connection. Step 609: The target mobility management entity initiates a location update procedure to the authentication authority server. Step 610: The authentication authorization server initiates a location deletion process to the original mobility management entity. Step 611: The original mobility management entity initiates a LIPA connection PDP context deletion process to the original local access gateway according to the determination result of step 604. This step may be performed at any time after step 604. Steps 612, 613, the target mobility management entity sends a routing area update to the terminal, and the terminal responds to the routing area update completion. In this embodiment, the local access gateway is an L-GGSN. In this embodiment, the L-GGSN is located in a disconnected release process. The local access gateway may also be an L-GW, a data offloading functional entity.

Figure 7 is a flow chart showing a sixth embodiment of the present invention. The sixth embodiment of the present invention is another local IP access connection release process in the routing area update process in the UTRAN system, and the network diagram shown in FIG. 1(a), FIG. 1(b) and FIG. 1(c), the present invention The sixth embodiment mainly includes the following steps: Step 701: The terminal in the idle state initiates a routing area update process periodically or due to a change in the routing area caused by the movement. The terminal sends a non-access stratum (Non-Access-Stratum, referred to as NAS) The information-routing area update request message is sent to the radio side network element (collectively referred to as the target radio side network element) currently serving the terminal. After the terminal moves, the wireless side network element may be different from the wireless side network element (collectively referred to as the original wireless side network element) before the terminal enters the idle state. Step 702: The radio side network element selects, for the terminal, the mobility management entity currently serving the terminal (collectively referred to as the target mobility management entity), and the routing area update request message is included in the initial user message and sent to the target mobility management entity. If there is a home base station gateway, the initial user message is first forwarded to the home base station gateway, and then the home base station gateway selects the target mobility management entity, and sends the initial user message to the target mobility management entity. The mobility management entity in the UTRAN system is an SGSN. Step 703: The target mobility management entity obtains an address of the mobility management entity (collectively referred to as the original mobility management entity) before the terminal enters the idle state according to the routing area update request message, and sends a context request message to the original mobility management entity to initiate Context acquisition process. Step 704: After receiving the context request message, the original mobility management entity includes the context information of the terminal in the context response message, and sends the context information to the target mobility management entity. At the same time, the identifier information of the original local access gateway or the identifier information of the original wireless side entity is carried in the context response message. When the terminal has a local IP access connection, the context response message carries the identity information of the original local access gateway or the original wireless side entity identification information. When the terminal does not have a local IP access connection, the identifier information of the original local access gateway or the original wireless side entity identification information may not be carried in the context response message to indicate that there is no local IP access connection; or the indication information is passed in the message. Indicates that there is no local IP access connection. The identifier information of the local access gateway may be an address of the local access gateway or identifier information dedicated to identifying the local access gateway. The identifier information of the radio side network element may be an address of the radio side network element or identifier information dedicated to identifying the radio side network element. The identifier information of the original local access gateway of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection. The original radio side network element identification information of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection, and is not released when the terminal enters the idle state. Step 705: The target mobility management entity may initiate an authentication and authentication process for the terminal. Step 706: After receiving the context response message, the target mobility management entity checks whether the terminal has a local IP access connection. If yes, it checks whether the LIPA connection of the terminal is affected according to the identifier information or the indication information in the context response message. For the terminal that has the local IP access connection: when the context response message carries the identification information of the original local access gateway, the target mobility management entity checks the identity information of the target local access gateway and the original local information carried in the context response message. The identity information of the access gateway is the same. If the identity of the access gateway is the same, the local access gateway connected to the LIPA is not changed. The LIPA connection of the terminal is not affected. If the local access gateway of the LIPA connection is changed, the LIPA of the terminal is changed. The connection needs to be released. When the context response message carries the identification information of the original radio side network element, the target mobility management entity checks whether the identification information of the original radio side network element and the identity information of the original radio side network element carried in the context response message are consistent. If the terminal is still connected from the original wireless side network element, the terminal's LIPA connection is not affected. If the terminal is inconsistent, the terminal is considered to be connected from the new wireless side network element, and the terminal's LIPA connection needs to be released. When the context response message does not carry any identification information or carries the indication information that there is no local IP access connection, it indicates that the terminal does not have a local IP access connection. When the context response message carries the identification information, but the target wireless side network element does not support the local

When IP access, the local IP access connection of the terminal needs to be released. Step 707: The target mobility management entity responds to the original mobility management entity with a context confirmation message. According to the judgment result of the step 706, when the LIPA connection of the terminal needs to be released, the LIPA failure indication information is carried in the context confirmation message. Steps 708-713 are the same as steps 608-613. In this embodiment, the local access gateway is an L-GGSN. In this embodiment, the L-GGSN is located in a disconnected release process. The local access gateway may also be an L-GW, a data offloading functional entity. Figure 8 is a flow chart showing a seventh embodiment of the present invention. The seventh embodiment of the present invention is a local IP access connection release process in the relocation process in the UTRAN system, and the seventh embodiment of the present invention is combined with the network diagram shown in FIG. 1(a), FIG. 1(b) and FIG. 1(c). The example mainly includes the following steps: Step 801: The wireless side network element determines that the relocation needs to be initiated. When the original wireless side network element and the target wireless side network element have interaction, the target wireless side network element can connect its local access gateway (target local connection) The identification information of the ingress gateway is transmitted to the original radio side network element, or the terminal can report the identification information of the target local access gateway to the original radio side network element. The identifier information of the local access gateway may be an address of the local access gateway or identifier information dedicated to identifying the local access gateway. Step 802: The original radio side network element sends a handover request message to the original mobility management entity, where the handover request message carries the identifier of the target radio side entity. If the identification information of the target local access gateway is obtained, the information is also carried in the handover request message and transmitted to the original mobility management entity. If there is a home base station gateway, the handover request message is first forwarded to the home base station gateway, and then the home base station gateway sends the handover request message to the original mobility management entity. The mobility management entity in the UTRAN system is an SGSN. Step 803: After receiving the handover request message, the original mobility management entity checks whether the terminal has a local IP access connection. If yes, it checks whether the terminal's LIPA connection is affected. For the terminal that has the local IP access connection: When the handover request message carries the identity information of the target local access gateway, the original mobility management entity checks the identity information of the local access gateway of the terminal local IP access connection and the target local access gateway. If the identity information of the terminal is consistent, the local access gateway connected to the terminal LIPA is not changed, and the LIPA connection of the terminal is not affected. If the local access gateway connected to the terminal LIPA has changed, the LIPA connection of the terminal needs to be changed. freed. The identification information of the local access gateway of the terminal local IP access connection is saved in the context when the terminal establishes the LIPA connection, and is not released when the terminal enters the idle state. When the handover request message does not carry the identifier information of the target local access gateway, the local IP access connection of the terminal needs to be released. In this case, the target wireless side network element does not support the local IP access, and the target wireless side network may be considered. Whether the element supports local IP access, and the wireless side network element changes. All need to release the local IP access connection. Step 804: The original mobility management entity selects a mobility management entity (collectively referred to as a target mobility management entity) that is a terminal service after the handover, and sends a relocation forward request message to the target mobility management entity, where the relocation is performed. The transfer request message carries bearer information that needs to be switched. According to the judgment result of the step 803, when the terminal local IP access connection needs to be released, the relocation request message does not carry the bearer information of the connection, so as to complete the release of the failed connection. Step 805: The target mobility management entity sends a relocation request to the target radio side network element. Step 806, continuing the normal handover process. Step 807: The original mobility management entity initiates a LIPA connection PDP context deletion process to the original local access gateway according to the determination result of step 803. This step may be performed at any time after step 803. Step 808: The terminal may initiate a routing area update process. In this embodiment, the local access gateway is an L-GGSN. In this embodiment, the L-GGSN is located in a disconnected release process. The local access gateway may also be an L-GW or a data offloading functional entity. In this embodiment, the original mobility management entity determines whether the terminal LIPA connection is affected. For example, the method shown in FIG. 6 can also be used by the target mobility management entity, which is similar to the method shown in FIG. No longer detailed. The processing of other switching processes is similar to this process and will not be described in detail here.

Figure 8a is a schematic flow chart of an eighth embodiment of the present invention. The eighth embodiment of the present invention is a process for releasing another local IP access connection in the relocation process in the UTRAN system, and the network diagram shown in FIG. 1(a), FIG. 1(b) and FIG. 1(c), the present invention The eight embodiments mainly include the following steps: Step 801a: The radio side network element determines that relocation needs to be initiated. Step 802a: The original radio side network element sends a handover request message to the original mobility management entity, where the handover request message carries the identifier of the target radio side entity. If there is a home base station gateway, the first cut The change request message is forwarded to the home base station gateway, and then the home base station gateway sends the handover request message to the original mobility management entity. The mobility management entity in the UTRAN system is an SGSN. Step 803a, the same as step 503a, but the message therein is a handover request message. Step 804a: The target mobility management entity sends a relocation request message to the target radio side network element. Step 805a: The target radio side network element sends a relocation request confirmation message in response, and carries the target local access gateway identifier in the relocation request confirmation message. Step 806a, the same as step 507a, but the message therein is a relocation request confirmation message. Step 807a: The target mobility management entity sends a relocation forward response message to the target radio side network element. According to the judgment result of the step 806a, when the terminal local IP access connection needs to be released, the relocation pre-transmission response message carries the LIPA connection failure indication information, indicating that the LIPA connection is released. Step 808a: The target mobility management entity initiates a bearer deletion process for the LIPA connection. After the step 505a, the resources reserved by the radio side network element for the LIPA are deleted. Steps 809a-811a are the same as steps 806-808, respectively. In the embodiment shown in FIG. 5, FIG. 5a, FIG. 8 and FIG. 8a, the identification information of the target local access gateway may also be configured on the target mobility management entity. In this case, FIG. 5a and FIG. 8a are used. The illustrated embodiment process. In this process, the target mobility management entity can directly determine whether the LIPA of the terminal is invalid after receiving the handover or relocation forward request, and it is no longer necessary for the radio side network element to reserve resources for the LIPA; the same. According to the foregoing method embodiment of the present invention, the present invention provides a release system of a local IP access connection, including an original mobility management entity serving the terminal before the change, wherein: the original mobility management entity is configured to: obtain the changed service and serve the terminal The target local access gateway identification information, or the target wireless side network element identification information, or the target home base station gateway identification information, and determine, according to the identification information, whether the local IP access connection is valid and release the invalid local IP access connection. According to the foregoing method embodiment of the present invention, the system further provides that the local IP access connection includes the original mobility management entity serving the terminal before the change and the target mobility management entity serving the terminal after the change, wherein: The target mobility management entity is configured to: obtain original local access gateway identification information serving the terminal before the change, or original wireless side network element identification information, or original home base station gateway identification information, and determine a local IP access connection according to the identification information. After the failure, the local IP access failure indication is responded to the original mobility management entity by the message; the original mobility management entity is configured to: release the failed local IP access connection according to the local IP access failure indication. The above two system embodiments are understood in accordance with the method embodiments of the present invention. In order to simplify the description, the above embodiment illustrates the release method of the local IP access connection only by taking the case where there is no home base station gateway and the local access gateway is located at or near the wireless side entity. The case where there is a home base station gateway is similar. Of course, when there is a home base station gateway, and the local access gateway is located at or near the wireless side entity, the message between the mobility management entity and the wireless side entity and the message between the mobility management entity and the local access gateway will be via the home. The base station gateway passes. When there is a home base station gateway, and the local access gateway is located at or near the home base station gateway, the message between the mobility management entity and the wireless side entity will be transmitted through the home base station gateway, and the mobility management entity and the local access gateway The message between the home base station and the gateway is no longer required to be forwarded by the home base station. The identification information of the newly added radio side network element needs to be replaced by the identification information of the home base station gateway. In these cases, the manner in which the local IP access connection is released is very similar to the above embodiment, and will not affect the description of the present invention, and thus the description will not be repeated here. The system and method for releasing a local IP access connection provided by the present invention solves the problem of how to release a failed connection caused by a change of a mobility management entity. In the handover of the LTE system or the identification information of the tracking area gateway or the wireless side network element or the home base station gateway, it is determined whether the LIPA connection is invalid. For the failed LIPA connection, the original mobility management entity no longer sends the bearer information of the connection to the target. The mobility management entity, while the original mobility management entity releases the LIPA connection. The above embodiments can be applied not only to the home base station system but also to the macro base station system. In the above embodiment, the wireless side entity may be a base station, a home base station or a radio network controller.

(Radio Network Controller, referred to as RNC). The mobility management entity may be an MME, an MSC or an SGSN. The local access gateway may be an L-SGW, an L-PGW, an L-GGSN, an L-GW, or a data offloading functional entity. The core network access gateway can be an S-GW or an SGSN. The radio side network element or home base station gateway of the local IP access can be the same as the local access gateway address.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software. While the embodiments of the present invention have been described above, the described embodiments are merely for the purpose of understanding the invention and are not intended to limit the invention. Any modification and variation of the form and details of the invention may be made by those skilled in the art without departing from the spirit and scope of the invention. It is still subject to the scope defined by the appended claims.

Industrial Applicability Compared with the prior art, the system and method for releasing the local IP access connection provided by the present invention solves the problem of how to release the failed connection caused by the change of the mobility management entity.

Claims

Claim

A method for releasing a local IP access connection, characterized in that, for a mobility management entity to change, a failed local IP access connection is released, the method comprising:

And determining, according to the identifier information of the device that is used to serve the terminal, the local IP access connection is invalid, where the identifier information of the device serving the terminal after the change includes serving after the change Target local access gateway identification information of the terminal, or target radio side network element identification information, or target home base station gateway identification information; or

Determining, by the identification information of the device of the terminal, whether the local IP access connection is invalid according to the identification information of the device serving the terminal before the change, where the identifier information of the device serving the terminal before the change includes serving before the change The original local access gateway identification information of the terminal, or the original wireless side network element identification information, or the original home base station gateway identification information;

The failure means that the local IP access connection is affected in a triggering event, and the local IP access connection cannot be used continuously, that is, the local IP access connection needs to be released.

2. The method of claim 1, wherein: the change comprises a change of a mobility management entity caused by handover or tracking area update of the terminal in a long term evolution system, or terrestrial wireless access by a universal mobile communication system The end of the system

The method according to claim 2, wherein: before the step of acquiring the identification information of the device serving the terminal after the change in the tracking area update process, the method further includes: the terminal is to the target The wireless side network element sends a tracking area update request message, and the target wireless side network element forwards the tracking area update request message to the target mobility management entity after the terminal selects the target mobility management entity; Get change The step of serving the identification information of the device of the terminal includes: the target radio side entity supporting the text request message, where the context request message carries the identifier information of the target local access gateway or the target radio side entity; The step of invalidating the local IP access connection includes: determining, by the original mobility management entity, whether the local IP access connection is invalid according to the identifier information of the target local access gateway or the target wireless side entity; or in the routing area update process Before the step of acquiring the identification information of the device that is used to serve the terminal, the method further includes: the terminal sending a routing area update request message to the target wireless side network element, where the target wireless side network element is The terminal selects the target mobility management entity, and forwards the routing area update request message to the target mobility management entity; and the step of acquiring the identification information of the device serving the terminal after the change includes: the target Wireless side entity supports local

When the IP access is performed, the target mobility management entity sends a context request message to the original mobility management entity, where the context request message carries the identifier information of the target local access gateway or the target radio side entity; The step of invalidating the access connection includes: determining, by the original mobility management entity, whether the local IP access connection is invalid according to the identifier information of the target local access gateway or the target wireless side entity.

The method of claim 3, wherein the step of determining, by the original mobility management entity, whether the local IP access connection is invalid according to the identification information of the target local access gateway or the target wireless side entity comprises: After receiving the context request message, the original mobility management entity checks whether the local IP access connection exists; if yes, further determines the identifier information of the target local access gateway and the original local access gateway. Whether the identification information is consistent or not, indicating that the local IP access connection is invalid, or

If yes, it is further determined whether the identifier information of the target radio side entity is consistent with the identifier information of the original radio side entity, and if not, the local IP access connection is invalid. The method of claim 3 wherein: The step of obtaining the identification information of the device serving the terminal after the change further comprises: when the target wireless side entity does not support local IP access, the target mobility management entity sends a context request message to the original mobility management entity The Context Request message does not carry the identifier information of the target local access gateway or the target radio side entity, or carries the indication information that does not support the local IP access. The step of determining whether the local IP access connection is invalid includes: Determining, by the original mobility management entity, the local IP access according to the context request message that does not carry the identifier information of the target local access gateway or the target radio side entity or according to the context request message that carries the indication information. The connection is invalid.

The method of claim 2, wherein: in the handover or redirection process, acquiring the identification information of the device serving the terminal after the change, the handover request message carrying the identifier information of the target local access gateway The step of determining whether the local IP access connection is invalid includes: determining, by the original mobility management entity, that the local IP access connection is invalid according to the identification information of the target local access gateway after receiving the handover request message.

The method of claim 6, wherein, according to the identification information of the target local access gateway, the step of determining whether the local IP access connection is invalid comprises: in the switching process or the redirection process, If the identifier information of the target local access gateway is not carried in the handover request message, the local IP access connection is invalid.

The method of claim 6, wherein the step of determining whether the local IP access connection is invalid according to the identification information of the target local access gateway comprises: the original mobility management entity receiving the handover After the request message is sent, it is checked whether there is a local IP access connection, and if it is determined, it is further determined whether the identity information of the target local access gateway is consistent with the identity information of the original local access gateway, and the inconsistency indicates that the local IP access connection is invalid. .

The method of claim 3 or 6, wherein after the step of determining whether the local IP access connection is invalid, the method further includes:

The bearer information sent by the dynamic management entity includes a valid local IP access connection; the valid means that a trigger event does not affect the local IP access connection, that is, the local IP access connection is still applicable; the trigger event includes handover, relocation, One or more of routing area updates, tracking area updates, capability redirection, and contract changes.

The method of claim 2, wherein: before the step of acquiring the identification information of the device serving the terminal before the change in the tracking area update process, the method further includes: the terminal is to the target The wireless side network element sends a tracking area update request message, and the target wireless side network element forwards the tracking area update request message to the target mobility management entity after the terminal selects the target mobility management entity; The step of the target service information of the device of the terminal includes: when the local IP access connection exists, the context response message carries the identifier information of the original local access gateway or the original wireless side entity; determining local IP access The step of determining whether the connection is invalid or not includes: determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identification information of the original local access gateway or the original wireless side entity; Before the step of serving the identification information of the device of the terminal, the method further includes: Transmitting, by the target radio side network element, a routing area update request message, the target radio side network element selecting the target mobility management entity for the terminal, and forwarding the routing area update request message to the target mobility management The entity mobility management entity sends a context request message to the original mobility management entity; the step of acquiring the identity information of the device serving the terminal before the change comprises: when the local IP access connection exists, the original mobile The trait management entity sends a context response message to the target mobility management entity, where the context response message carries the identification information of the original local access gateway or the original wireless side entity; and the step of determining whether the local IP access connection is invalid includes: The target mobility management entity is based on the original The identification information of the local access gateway or the original wireless side entity determines whether the local IP access connection is invalid.

The method of claim 10, wherein the step of determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identification information of the original local access gateway or the original wireless side entity comprises: the target After receiving the context response message, the mobility management entity checks whether there is a local IP access connection, and further determines whether the identity information of the original local access gateway is consistent with the identity information of the target local access gateway. Inconsistent means that the local IP access connection is invalid, or

And determining whether the identification information of the original wireless side entity is consistent with the identification information of the target wireless side entity, if the inconsistency indicates that the local IP access connection is invalid; when not present, the local IP access connection indicates The local IP access connection is invalid.

The method according to claim 10, wherein the step of acquiring the identification information of the device serving the terminal before the change further comprises: when there is no local IP access connection, the original mobility management entity is to the target The context response message sent by the mobility management entity does not carry the identifier information of the original local access gateway or the original wireless side entity, or carries the indication information that the local IP access connection does not exist.

13. The method according to claim 2, wherein: in the handover process, the step of acquiring the identification information of the device serving the terminal after the change, the package mobility management entity selecting the target mobility management entity for the terminal Sending, to the target mobility management entity, identifier information carrying the original local access gateway or the original wireless side entity.

And the acknowledgment message, the handover request acknowledgment message carries the identifier information of the target local access gateway or the target radio side entity; and the step of determining whether the local IP access connection is invalid includes: the target shift The dynamic management entity determines, according to the identification information of the target local access gateway or the target wireless side entity, whether the local IP access connection is invalid; in the redirection process, acquiring the identification information of the device serving the terminal after the change a handover request message of the identification information of the step element, the original mobility management entity, after selecting the target mobility management entity for the terminal, transmitting, to the target mobility management entity, the original local access gateway or a relocation request message of the identification information of the original radio side entity, the target mobility management entity sending a relocation request message to the target radio side network element, where the target radio side network element manages the target mobility The entity sends a relocation request confirmation message, where the relocation request confirmation message carries the identification information of the target local access gateway or the target radio side entity; and the step of determining whether the local IP access connection is invalid includes: the target mobility management entity Determining the location according to the identification information of the target local access gateway or the target wireless side entity Local IP access connection is invalid.

The method of claim 13, wherein the step of determining, by the target mobility management entity, whether the local IP access connection is invalid according to the identification information of the target local access gateway or the target wireless side entity comprises: After receiving the relocation forward request message, the target mobility management entity checks whether there is a local IP access connection, and further determines whether the identity information of the original local access gateway is related to the target local access gateway. Whether the identification information is consistent or not, indicating that the local IP access connection is invalid.

The method of claim 10 or 13, wherein, after the step of determining whether the local IP access connection is invalid, the method further includes:

16. The method of claim 1, wherein: the original mobility management entity and/or the target mobility management entity comprise a long term evolution system A mobile radio management unit, a mobile switching center in a global mobile communication system, or a serving general wireless packet service supporting node in a terrestrial wireless access system of a universal mobile communication system.

17. The method of claim 1, wherein: the target local access gateway identification information comprises an address of the target local access gateway or identification information dedicated to identifying the target local access gateway; The wireless side network element identification information includes an address of the target wireless side network element or identifier information dedicated to the target wireless side network element; the target home base station gateway identification information includes an address of the target home base station gateway or a dedicated And identifying the identifier information of the target home base station gateway; the original local access gateway identifier information includes an address of the original local access gateway or identifier information dedicated to identifying the original local access gateway; The side network element identification information includes an address of the original wireless side network element or identification information dedicated to the original wireless side network element; the original home base station gateway identification information includes an address of the original home base station gateway or is dedicated to Identifying identification information of the original home base station gateway.

18. The method of claim 1, wherein the triggering event comprises one or more of handover, relocation, routing area update, tracking area update, capability redirection, and subscription change.

A release system for a local IP access connection, characterized in that, for a mobility management entity to change and release a failed local IP access connection, the system includes an original mobility management entity serving the terminal before the change, wherein: The original mobility management entity is configured to: obtain the identification information of the device serving the terminal after the change, and determine whether the local IP access connection is invalid according to the identification information of the device that is changed to serve the terminal, and release the The failed local IP access connection, where the identification information of the device serving the terminal after the change includes target local access gateway identification information, or target radio side network element identification information, or target home base station gateway identification information; The failure refers to a trigger The local IP access connection is affected, and the local IP access connection cannot be used continuously, that is, the local IP access connection needs to be released; the triggering events include handover, relocation, routing area update, tracking area update, capability redirection, and subscription change. One or more.

20. A release system for a local IP access connection, characterized in that, for a mobility management entity to change, a failed local IP access connection is released, the system including the original migration of the service before the change.

The target mobility management entity is configured to: obtain identification information of a device that is served by the terminal before the change, and determine, according to the identifier information of the device that serves the terminal, that the local IP accesses the The identification information of the device of the terminal includes the original local access gateway identification information, or the original wireless side network element identification information, or the original home base station gateway identification information. The failure refers to a trigger event that affects the local IP access connection. The local IP access connection cannot be used continuously, that is, the local IP access connection needs to be released; the triggering event includes one or more of handover, relocation, routing area update, tracking area update, capability change, and subscription change; The original mobility management entity is configured to release the failed local IP access connection according to the local IP access failure indication.