WO2009129697A1

WO2009129697A1 - A method and apparatus for deleting the control plane tunnel

Info

Publication number: WO2009129697A1
Application number: PCT/CN2009/000443
Authority: WO
Inventors: 熊春山; 沈宇希
Original assignee: 大唐移动通信设备有限公司
Priority date: 2008-04-25
Filing date: 2009-04-27
Publication date: 2009-10-29
Also published as: CN101567843A; CN101567843B

Abstract

A method for deleting the control plane tunnel is used to delete the General Packet Radio Service Tunnelling Protocol-Control plane (GTP-C) tunnel which is between the network entities. The method includes: detecting the number of the bearers managed by a GTP-C tunnel which is between a local network entity and an opposite network entity, when the number of the bearers changes from bigger than zero to zero, releasing the Internet Protocol (IP) address and the Tunnel Endpoint Identifier (TEID) of the GTP-C tunnel allocated by the local network entity. Additionally, an apparatus for deleting the control plane tunnel and a serving gateway are also provided.

Description

Method and device for deleting control plane tunnel

Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and apparatus for deleting a control plane tunnel. Background technique

In the packet switching (PS, Packet Switch) domain of the traditional second-generation/third-generation mobile communication standard (2G/3G) system, the General Packet Radio Service (GPRS) tunneling protocol (GTPvl) is used. Or GTPvO), and only two interfaces have a General Packet Radio Service Tunneling Protocol Control Plane (GTP-C) tunnel connection, one is a Serving GPRS Support Node (SGSN) and a Gateway GPRS Support Node (GGSN, Gateway GPRS) Between the Support Nodes, one is between the SGSN and the SGSN. For GTPvl, between the SGSN and the GGSN, there is only one GTP-C for an Access Point Name (APN, Access Point Name) and a User Data (PDP, Packet Data Protocol) address of the User Equipment (UE, User Equipment). Tunnel connection. For a user terminal (UE), if there is a GTP-C tunnel connection between the SGSN and the SGSN, there can only be one GTP-C tunnel at the same time. The GTP-C tunnel between the SGSN and the GGSN manages the GTP User Plane (GTP-U) tunnel corresponding to the same APN and the PDP Context of the PDP address of the UE. A GTP-C tunnel connection is established between the SGSN and the SGSN only during the context request (Context Request) process and the Forward Relocation process.

The traditional 2G/3G does not have the function of the Internet Protocol (IP) always-on, and the establishment of the packet data protocol context (PDP Context) and the establishment of the second packet data protocol context (second PDP Context) by the UE are only The GGSN is allowed to initiate the establishment of the Second PDP Context, and the GGSN is not allowed to initiate the establishment of the PDP Context. In this way, when the UE initiates the establishment of a PDP Context, a GTP-C tunnel connection is established between the SGSN and the GGSN, and a GTP-U tunnel is established for the PDP Context. When the PDP Context is deleted later, The corresponding GTP-U tunnel is also deleted. According to the protocol TS29.060, when all the GTP-U tunnels managed by the GTP-C tunnel are deleted, the GTP-C tunnel cannot be deleted; When a PDP address and all PDP Contexts of the APN are deleted, the corresponding GTP-C tunnel must also be retained and cannot be deleted. When the SGSN sends a Create PDP Context Request message to the GGSN, if the SGSN has previously assigned a Tunnel End Point Identifier (TEID) to the GTP-C tunnel of the GGSN, The GGSN confirms that the SGSN is not allowed to carry the TEID in this message; otherwise, the SGSN allocates a TEID and is included in this message. In addition, if the GGSN has previously assigned the TEID to the GTP-C tunnel of the SGSN and is confirmed by the SGSN, the TEID used by the SGSN to send the GTP header of the GTP message must be the TEID allocated by the GGSN; otherwise, the TEID =0. When the GGSN responds to the SGSN with a Create PDP Context Response message, the same principle is followed. If the GGSN has previously assigned the TEID to the GTP-C tunnel of the SGSN and is confirmed by the SGSN, The GGSN is not allowed to carry the TEID in this message; otherwise, the GGSN allocates a TEID and is included in this message. In addition, if the SGSN has previously assigned the TEID to the GTP-C tunnel of the GGSN for the UE and is confirmed by the GGSN, the TEID used by the GGSN to send the GTP header of the GTP message must be the TEID assigned by the SGSN; otherwise, it must be used. The TEID contained in the Create PDP Context Request by the SGSN. In addition, the protocol TS29.060 does not indicate that when the UE shares the same PDP address and all PDP Contexts of the APN are deleted, its corresponding GTP-C tunnel must be deleted. That is to say, when the same PDP address shared by the UE and all PDP Contexts of the APN are deleted, the corresponding GTP-C tunnel must also be reserved. The main reason is that the UE may later re-establish a PDP Gontext.

Currently, the GTP-C tunnel between the GGSN and the SGSN is deleted as follows: An explicit method is to update the Packet Data Protocol Context (Update PDP Context) procedure, and the GGSN assigns the IP address of the GTP-C tunnel to the old SGSN. The TEID continues to be used by the new SGSN. When the old SGSN deletes the context (Context) of the UE by receiving the Cancel Location from the Home Subscriber Server (HSS, Home Subscriber Server), it will be assigned to the GGSN. The IP address of the GTP-C tunnel is released with the TEID. Another non-ambiguous method is that when the UE is detached, the SGSN releases the IP address and TEID of the originally assigned GTP-C tunnel to the GGSN. How does the GGSN release the IP of the originally assigned GTP-C tunnel to the SGSN? The address and TEID are not defined in TS29.060.

In the Evolved Packet System (EPS), the new core network architecture is adopted, and the GTPv2 protocol is decided to be used in the EPS system, including the SGSN, Serving GW (Serving Gateway), and mobility management entity. (MME, Mobility Management Entity), Packet Data Network Gateway (PDN GW), as shown in Figure 1, S3, S4, S5, S8, S10, S11 interface uses GTPv2 protocol, S8 is S5 roaming interface . In addition, whether there is an interface between the SGSN and the PDN GW and whether to use the GTPv2 protocol is not determined; likewise, whether there is an interface between the Serving GW and the GGSN and whether the GTPv2 protocol is used or not is also determined; and, currently, the SGSN and the GGSN The GTPvl protocol is used between them. In the future 3GPP versions, whether or not the GTPv2 protocol will be used is also undetermined.

The EPS system is a new type of 3GPP system. It is a big difference from the traditional 2G/3G system. It supports IP always online, that is, once the UE registers with the EPS system, the system assigns an IP address to the UE. And activate an EPS bearer (EPS Bearer).

In the EPS system, there is only one GTP-C tunnel connection between the SGSN and the Serving GW for one UE, and there is only one GTP-C tunnel connection between the MME and the Serving GW. There is at least one GTP-C tunnel connection between the Serving GW and a PDN GW, but the GTP-C tunnel between the MME and the Serving GW, the GTP-C tunnel between the SGSN and the Serving GW, the Serving GW and the PDN.

Summary of the invention

In view of this, the embodiment of the present invention provides a method for deleting a control plane tunnel, which is used to delete a GTP-C tunnel between an SGSN and a Serving GW, between an MME and a Serving GW, and between a Serving GW and a PDN GW.

An embodiment of the present invention provides a method for deleting a control plane tunnel, including: Detecting the number of bearers managed by a general packet radio service tunneling protocol control plane (GTP-C) tunnel between the local network entity and the peer network entity;

When the number of bearers changes from greater than zero to zero, the Internet Protocol (IP) address assigned to the GTP-C tunnel by the local network entity and the Tunnel Endpoint Identifier (TEID) are released.

An embodiment of the present invention further provides an apparatus for deleting a control plane tunnel, including:

a detecting unit, configured to detect a number of bearers managed by a general packet radio service tunnel protocol control plane (GTP-C) tunnel connected to the local network entity;

And a release unit, configured to release an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) allocated by the local network entity to the GTP-C tunnel when the number of the bearers changes from greater than zero to zero.

The embodiment of the invention further provides a service gateway, including:

a first release unit, configured to release, when the serving gateway detects that an ISR function of a user terminal (UE) is activated, and the serving gateway releases an IP address and a TEID of all GTP-C tunnels with all PDN gateways IP address and TEID of all GTP-C tunnels between the MME and the SGSN;

a second release unit, configured to release, when the serving gateway detects that an ISR function of the user terminal (UE) is activated, and the serving gateway releases an IP address and a TEID of all GTP-C tunnels between the MME and the SGSN, IP address and TEID of all GTP-C tunnels with all PDN gateways;

a third release unit, configured to: when the serving gateway detects that the ISR function of the user terminal (UE) is disabled, and the serving gateway releases the IP address and the TEID of all the GTP-C tunnels between all the PDN gateways, IP address and TEID of the GTP-C tunnel with the MME or SGSN;

a fourth release unit, configured to: when the serving gateway detects that the ISR function of the user terminal (UE) is disabled, and the serving gateway releases the IP address and TEID of the GTP-C tunnel between the MME or the SGSN, release IP address and TEID of all GTP-C tunnels between all PDN gateways.

In the embodiment of the present invention, the number of bearers managed by a general packet radio service tunneling protocol control plane (GTP-C) tunnel between the local network entity and the peer network entity is detected, when the number of the bearers changes from greater than zero. When the time is zero, the Internet Protocol (IP) address and the Tunnel Endpoint Identifier (TEID) allocated by the local network entity to the GTP-C tunnel are released, thereby saving network resources and ensuring that the IP is always online. DRAWINGS

1 is a structural view of an EPS system in the prior art;

2 is a schematic diagram of a method for deleting a GTP-C tunnel according to an embodiment of the present invention;

3 is a schematic diagram of a method for deleting a GTP-C tunnel in a network entity handover process according to an embodiment of the present invention;

4 is a structural diagram of an apparatus for deleting a GTP-C tunnel in an embodiment of the present invention. detailed description

In the embodiment of the present invention, the user mobility control management entity includes an MME and an SGSN. A PDN connection refers to a collection of all EPS bearers of the UE that use the same APN and the same IP address. An IP address is an IPv4 address, an IPv6 address, or an IPv4 and IPv6 dual address. The EPS session management context (ESM Context, EPS Session Management Context) refers to the session management context (SM Context, Session Management Context) used by the SGSN and the Serving GW, and also refers to the ESM Context used by the MME, the Serving GW, and the PDN GW. That is to say, the ESM Context is not specifically different from the SM Context.

An embodiment of the present invention provides a method for deleting a control plane tunnel, including: detecting a general packet radio service tunnel protocol control plane between a local network entity and a peer network entity.

(GTP-C) The number of bearers managed by the tunnel. When the number of bearers changes from greater than zero to zero, the Internet Protocol (IP) address assigned to the GTP-C tunnel and the tunnel endpoint are released. Identification (TEID).

For a UE, when the number of bearer contexts stored in the local network entity changes from greater than zero to zero, the IP addresses and TEIDs of all GTP-C tunnels connected to the local network entity are released. There is no need to notify the tunnel peer network entity.

The embodiment of the present invention can be applied to any two network entities in the EPS system that manage the bearer through the GTP-C tunnel, that is, when the local network entity is the MME, the peer network entity is the Serving GW; or when the local network is When the entity is Serving GW, the peer network entity is the MME; or When the local network entity is the SGSN, the peer network entity is the Serving GW; or when the local network entity is the Serving GW, the peer network entity is the SGSN; or when the local network entity is the Serving GW, the peer network entity is PDN GW; or when the local network entity is the PDN GW, the peer network entity is the Serving GW.

The bearer is 7 bearers corresponding to an EPS packet bearer context (EPS Bearer Context) or a packet data protocol context (PDP Context), and one bearer corresponds to a packet radio service tunneling protocol user plane (GTP-U) tunnel.

The embodiments of the present invention are further described in detail below with reference to the accompanying drawings.

In the GTP-C tunnel corresponding to the S4 interface in FIG. 1, for one UE, when all the EPS Bearer Contexts of the UEs stored by the SGSN and the Serving GW are deleted, or the ESM Context of the UE is deleted, that is, the GTP between the SGSN and the Serving GW. When the number of bearers managed by the -C tunnel changes from greater than zero to zero, the SGSN and the Serving GW release the IP address and TEID of the GTP-C tunnel between the SGSN and the Serving GW, respectively, without notifying the other party.

Similarly, for a GTP-C tunnel corresponding to the S11 interface, for one UE, when the MME and the Serving GW store all the EPS Bearer Contexts of the UE or the ESM Context of the UE is deleted, that is, the GTP-C between the MME and the Serving GW. When the number of bearers managed by the tunnel is changed from greater than zero to zero, the MME and the Serving GW release the IP addresses and TEIDs of the GTP-C tunnel between the MME and the Serving GW, respectively, without notifying the other party. As shown in Figure 2, the specific implementation steps of the GTP-C tunnel deletion method are as follows:

In step 201, the network entity A and the other network entities establish a GTP-C tunnel connection for the UE, where:

201a. Network entity A and network entity B establish a GTP-C tunnel connection for the UE; 201b. Network entity A and network entity C establish a GTP-C tunnel connection for the UE. In step 202, when some or all EPS Bearer Contexts of the UE stored by the network entity are deleted or the ESM Context of the UE is deleted, that is, the number of bearers managed by one or all GTP-C tunnels connected to the network entity is from When greater than zero becomes zero, the network entity releases the IP address and TEID of the one or all GTP-C tunnels. details as follows: 202a. If the entire EPS Bearer Context of the UE stored by the network entity A is deleted or the ESM Context of the UE is deleted, the network entity A releases all the IP addresses and TEIDs of all the established GTP-C tunnels, that is, the network entity A is released. In step 201a, the IP address and the TEID of the GTP-C tunnel established for the UE are not required to notify the peer node of the tunnel, that is, the network entity B, and the network entity A releases the IP address of the GTP-C tunnel established for the UE in step 201b. With TEID, there is no need to notify the peer node of the tunnel, ie network entity C.

202b. If the entire EPS Bearer Context of the UE stored in the network entity B is deleted or the ESM Context of the UE is deleted, the network entity B releases all the IP addresses and TEIDs of all the established GTP-C tunnels, that is, the network entity B is released. In step 201a, the IP address and TEID of the GTP-C tunnel established by the UE are not required to notify the peer node of the tunnel, that is, the network entity A.

202c. If the entire EPS Bearer Context of the UE stored by the network entity C is deleted or the ESM Context of the UE is deleted, the network entity C releases all the IP addresses and TEIDs of all the established GTP-C tunnels, that is, the network entity C is released. In step 201b, the IP address and TEID of the GTP-C tunnel established for the UE are not required to notify the peer node of the tunnel, that is, the network entity A.

202d. If the bearers managed by the GTP-C tunnel between the network entity A and the network entity B are all deleted, that is, if the number of bearers managed by the GTP-C tunnel between the network entity A and the network entity B changes from greater than zero If the value is zero, the network entity A releases the IP address and TEID of the GTP-C tunnel established for the UE in step 201a without notifying the peer node of the tunnel, that is, the network entity B. However, the network entity A retains the IP address and TEID of the GTP-C tunnel established for the UE in step 201b without notifying the peer node of the tunnel, that is, the network entity C.

202e. If the bearers managed by the GTP-C tunnel between the network entity A and the network entity C are all deleted, that is, if the number of bearers managed by the GTP-C tunnel between the network entity A and the network entity C changes from greater than zero If the value is zero, the network entity A releases the IP address and TEID of the GTP-C tunnel established for the UE in step 201b without notifying the peer node of the tunnel, that is, the network entity C. However, the network entity A retains the IP address and TEID of the GTP-C tunnel established for the UE in step 201a without notifying the peer node of the tunnel, that is, the network entity B.

In particular, during network switching, if a network entity is relocated during the handover process, The EPS Bearer Context and the ESM Context of the UE stored by the old network entity are deleted, and the EPS Bearer Context and the ESM Context of the UE stored by other network entities connected thereto still exist, and therefore, the network entity that is not relocated The new GTP-C tunnel connection is still established with the new network entity using the IP address of the assigned GTP-C tunnel and the TEID, while the old network entity releases the IP of all GTP-C tunnels it has allocated for this UE. Address and TEID. As shown in FIG. 3, after a UE registers with the MME and activates the EPS Bearer, the UE accesses a PDN through the old Serving GW and the PDN GW. Then, the MME does not change and the handover procedure of the Serving GW relocation is performed, and the UE continues to access the original PDN through the new Serving GW and the PDN GW. The specific implementation process is as follows:

Step 301: After the UE registers with the MME and activates the EPS Bearer, the UE accesses a PDN through the old Serving GW and the PDN GW. This process is specifically:

301a. The MME establishes a GTP-C tunnel with the old Serving GW.

301b. The old Serving GW and the PDN GW have established a GTP-C tunnel.

In step 302, the MME is unchanged, and the handover procedure of the Serving GW relocation is performed. During the handover, the UE switches from the old Serving GW to the new Serving GW.

Step 303: The new Serving GW establishes a GTP-C tunnel with the MME and the PDN GW, respectively. In this step, since the MME has not changed, and the EPS Bearer Context or ESM Context of the UE stored by the MME is not deleted, the MME does not release the IP address of the GTP-C tunnel allocated to the UE between the old Serving GW and the UE. With the TEID, these two parameters are respectively used to establish a GTP-C tunnel with the new Serving GW for this UE, that is, step 303a is performed. Similarly, the EPS Bearer Context or ESM Context of the UE stored in the PDN GW is not deleted, so the PDN GW does not release the IP address and TEID of the GTP-C tunnel allocated to the UE with the old Serving GW. The parameters are respectively used to establish a GTP-C tunnel with the new Serving GW for this UE, that is, step 303b is performed.

Step 304: All EPS Bearer Context or ESM Context of the UE stored by the old Serving GW is deleted.

Step 305, the old Serving GW release is separated from the MME and all PDN GWs for the UE. IP address and TEID of all GTP-C tunnels.

Referring to the GTP-C tunnel corresponding to the S5 interface in FIG. 1, one PDN GW may support multiple APNs, and for the same APN, the PDN GW may assign an IPv4 address, or an IPv6 address, or an IPv4 and an IPv6 address to the UE. (ie assign two IP addresses at the same time). In this way, for the same APN under the same PDN GW, there may be multiple GTP-C tunnels between the PDN GW and the Serving GW. The process of deleting the GTP-C tunnel between the PDN GW and the Serving GW includes:

When the number of bearers managed by one GTP-C tunnel between a PDN GW and a Serving GW changes from greater than zero to zero, the PDN GW releases the IP address and TEID assigned to the GTP-C tunnel, and the reservation The IP address and TEID of other GTP-C tunnels between the PDN GW and the Serving GW.

When the number of bearers managed by one GTP-C tunnel between the Serving GW and one PDN GW changes from greater than zero to zero, the Serving GW releases the IP address and TEID assigned to the GTP-C tunnel, and the reservation The IP address and TEID of other GTP-C tunnels between the Serving GW and the PDN GW.

That is, when the GTP-C tunnel between the PDN GW and the Serving GW includes at least two, the entire EPS Bearer Context of the UE managed by any GTP-C tunnel between the PDN GW and the Serving GW is deleted, that is, the GTP-C When the number of bearers managed by the tunnel changes from greater than zero to zero, the PDN GW releases the IP address and TEID allocated to the GTP-C tunnel, and retains the IP of other GTP-C tunnels between the PDN GW and the Serving GW. Address and TEID. Similarly, when the GTP-C tunnel between the Serving GW and the PDN GW includes at least two, the entire EPS Bearer Context of the UE managed by any GTP-C tunnel between the Serving GW and the PDN GW is deleted, that is, the GTP-C When the number of bearers managed by the tunnel changes from greater than zero to zero, the Serving GW releases the IP address and TEID allocated to the GTP-C tunnel, and retains the IP of other GTP-C tunnels between the Serving GW and the PDN GW. Address and TEID.

All EPS Bearer Contexts of all GTP-C tunnel managed UEs between the Serving GW and all PDN GWs are deleted, and the Serving GW releases GTP-C between all PDN GWs. After the IP address of the tunnel and the TEID, the Serving GW detects that the Idle State Signalling Reduction (ISR) function of the UE is not activated or deactivated, that is, when the Serving GW detects that the ISR function of the UE is disabled, Serving The GW releases the IP address and TEID of the GTP-C tunnel connected to the MME or the SGSN.

When the Serving GW detects that the ISR function of the UE is not activated or deactivated, after the Serving GW releases the IP address and TEID of the GTP-C tunnel connected to the MME or the SGSN, the Serving GW releases the GTP between the Serving GW and all PDN GWs. IP address and TEID of the C tunnel.

Another embodiment of the present invention is applied to an EPS system in which the ISR function of the UE is activated. When the UE's ISR function is activated, the UE simultaneously registers with the Universal Terrestrial Radio Access Network (UT AN), GSM/EDGE Radio Access Network (GERAN, GSM/EDGE Radio Access Network) and evolution. The E-TURAN (Evolved Universal Terrestrial Radio Access Network) access system corresponds to the user mobility control management entity, that is, simultaneously registered to the SGSN and the MME. When the UE is in an idle state, the UE does not need to perform general routing area update or general when it moves in the routing area (RA, Routing Area) allocated by the SGSN to the UE and the tracking list (TA List, Tracking Area List) allocated by the MME to the UE. Track area update operation. When the UE's ISR function is activated, the user plane termination point of the UE in the idle state is located at the Serving GW.

When the Serving GW detects that the ISR function of the user terminal (UE) is activated, there is a GTP-C tunnel between the MME and the Serving GW, and a GTP-C tunnel between the SGSN and the Serving GW, when the Serving GW is in the Serving GW. When the number of bearers managed by the GTP-C tunnel between the GW and the MME changes from greater than zero to zero, the Serving GW releases the IP address and TEID of the GTP-C tunnel between the Serving GW and the MME, and retains the GTP between the Serving GW and the SGSN. The IP address and TEID of the -C tunnel, and the IP address and TEID of all GTP-C tunnels between the serving gateway and all PDN GWs. When the number of bearers managed by the GTP-C tunnel between the Serving GW and the SGSN in the Serving GW changes from greater than zero to zero, the Serving GW releases the IP address and TEID of the GTP-C tunnel between the Serving GW and the SGSN. Retaining the IP address and TEID of the GTP-C tunnel between the Serving GW and the MME, and retaining the service gateway and all IP address and TEID of all GTP-C tunnels between PDN GWs. The specific process is as follows:

The Serving GW receives all the EPSs sent by the MME or the SGSN to delete the UE.

Bearer Context request message; or,

The Serving GW requests the MME or the SGSN to delete all EPS Bearers of the UE

Context; Then,

The Serving GW releases the IP address and TEID assigned to the GTP-C tunnel between itself and the MME or SGSN.

In the embodiment of the present invention, because the Serving GW further stores an ESM Context or an EPS Bearer Context of a UE related to the SGSN or the MME, the Serving GW does not release the IP address of the GTP-C tunnel allocated to the SGSN or the MME. TEID. And because the Serving GW also stores all GTP-C tunnel managed ESM Context or EPS Bearer Context with all PDN GWs, the serving gateway does not release the IP addresses of all GTP-C tunnels with all PDN GWs. With TEID.

When the SGSN, the MME, and the Serving GW activate the ISR function of the UE, there is a GTP-C tunnel connection between the SGSN and the Serving GW, between the MME and the Serving GW, and between the PDN GW and the Serving GW; When the detach procedure is clarified, the MME marks the UE as a detached state, and the ESM Context or all EPS Bearer Contexts of the UE are deleted on the MME, and the Serving GW is requested to delete all EPS Bearer Contexts of the UE, at this time, because Serving GW It is detected that the ISR function of the UE has been activated, so the Serving GW only deletes all EPS Bearer Contexts of the UE related to the MME, instead of deleting all EPS Bearer Contexts or ESM Contexts of the entire UE, that is, the Serving GW will also retain the SGSN. All EPS Bearer Context or ESM Context for this UE. The Serving GW will release the IP address and TEID of the GTP-C tunnel allocated to the MME for the UE. After the MME receives the response message of the Serving GW to delete the EPS Bearer Context, the MME releases the allocation allocated for the UE. IP address and TEID of the GTP-C tunnel between Serving GWs.

That is, after the ISR function of the UE is activated, when a user mobility control management entity MME or SGSN sends a request to the Serving GW to delete all EPS Bearer Contexts of the UE. Message, and when receiving the response message from Serving GW, because this user mobility control management entity has deleted all EPS Bearer Contexts of this UE, the IP address of the GTP-C tunnel with the Serving GW allocated to the UE is released. With TEID, there is no need to notify Serving GW.

After the ISR function of the UE is activated, when the Serving GW requests to delete all EPS Bearer Contexts of the UE from the two user mobility control entities MME and SGSN of the UE, it is obvious that the Serving GW will release the GTP between the MME and the SGSN. The IP address and TEID of the C tunnel. At the same time, the Serving GW also deletes all EPS Bearer Contexts of the UE, that is, the ESM Context is also deleted. At this time, the Serving GW will also release all GTP-C tunnels with all PDN GWs. IP address and TEID.

After the ISR function of the UE is activated, when all EPS Beare Contexts of all GTP-C tunnel-managed UEs between the Serving GW and all PDN GWs are deleted, the Serving GW releases the MME and the allocated MME for the UE. IP address and TEID of the GTP-C tunnel between SGSNs. The specific process may be as follows: After the Serving GW completes the request of the PDN GW to delete the EPS Bearer Context of the UE, if the EPS Bearer Context is deleted, the Serving GW finds that the UE does not have an EPS Bearer Context or an ESM Context, and is deleted. The EPS Bearer Context is the last EPS Bearer Context of the UE, and the Serving GW releases the IP address and TEID of the GTP-C tunnel between the last Serving GW and the PDN GW, and the Serving GW releases the MME and the assigned to the UE. IP address and TEIDo of the GTP-C tunnel between SGSNs

When the SGSN and the PDN GW have an interface, the Serving GW and the GGSN have an interface, and the interface between the SGSN and the GGSN uses the GTPv2 protocol, the method described in the embodiment of the present invention can still be applied to these interfaces.

The embodiment of the present invention further provides an apparatus for deleting a control plane tunnel. The structure thereof is shown in FIG. 4, and includes: a detecting unit 100 and a releasing unit 200.

The detecting unit 100 is configured to detect a number of bearers managed by a general packet radio service tunnel protocol control plane (GTP-C) tunnel connected to the local network entity;

The releasing unit 200 is configured to release the local network when the number of the bearers changes from greater than zero to zero. The Internet Protocol (IP) address and Tunnel Endpoint Identifier (TEID) assigned by the entity to the GTP-C tunnel. The detecting unit 100 includes: a first detecting subunit 110, a second detecting subunit 120, a third detecting subunit 130, and a fourth detecting subunit 140.

The first detecting sub-unit 110 is configured to detect the number of loads managed by a GTP-C tunnel connected to the MME.

The second detecting sub-unit 120 is configured to detect the number of loadings managed by a GTP-C tunnel connected to the SGSN.

The third detecting sub-unit 130 is configured to detect the number of bearers managed by one GTP-C tunnel connected to the Serving GW.

The fourth detecting subunit 140 is configured to detect the number of 7|loads managed by one GTP-C tunnel connected to the PDN GW.

The release unit 200 further includes: a first release subunit 210, a second release subunit 220, a third release subunit 230, and a fourth release subunit 240.

a first release subunit 210, configured to release an IP address allocated by the MME to the GTP-C tunnel when a number of bearers managed by one GTP-C tunnel connected to the MME is changed from greater than zero to zero With TEID.

a second release subunit 220, configured to release an IP address allocated by the SGSN to the GTP-C tunnel when a number of bearers managed by one GTP-C tunnel connected to the SGSN changes from greater than zero to zero With TEID.

a third release subunit 230, configured to release, when the number of bearers managed by one GTP-C tunnel connected to the Serving GW changes from greater than zero to zero, release the Serving GW to allocate to the GTP-C tunnel IP address and TEID.

a fourth release subunit 240, configured to release, when the number of bearers managed by one GTP-C tunnel connected to the PDN GW changes from greater than zero to zero, release the PDN GW to be allocated to the GTP-C tunnel IP address and TEID.

The embodiment of the invention also discloses a service gateway, including:

a first release unit, configured to: when the serving gateway detects that an ISR function of a user terminal (UE) is When activated, and the service gateway releases the IP address and TEID of all GTP-C tunnels with all PDN gateways, the IP address and TEID of all GTP-C tunnels between the MME and the SGSN are released.

a second release unit, configured to: when the serving gateway detects that an ISR function of the user terminal (UE) is activated, and the serving gateway releases an IP address and a TEID of all GTP-C tunnels between the MME and the SGSN, releasing All GTP-C P lost IP addresses and TEIDs between all PDN gateways.

a third release unit, configured to: when the serving gateway detects that the ISR function of the user terminal (UE) is disabled, and the serving gateway releases the IP address and the TEID of all the GTP-C tunnels with all the PDN gateways, IP address and TEID of the GTP-C tunnel with the MME or SGSN.

a fourth release unit, configured to: when the serving gateway detects that the ISR function of the user terminal (UE) is disabled, and the serving gateway releases the IP address and the TEID of the GTP-C tunnel between the MME or the SGSN, release IP address and TEID of all GTP-C tunnels between all PDN gateways.

The embodiment of the present invention detects the number of bearers managed by a general packet radio service tunneling protocol control plane (GTP-C) tunnel between the local network entity and the peer network entity, when the number of the bearers changes from greater than zero to zero. when releasing the end of the present network entity is assigned to the Internet protocol GTP-C tunnel (IP) address of the tunnel endpoint identifier (the TEID), thus ensuring IP ₇ j away online, but also saves network resources and improve the system Overall performance.

While the invention has been described by the embodiments of the invention in the embodiments of the invention Request to limit.

Claims

Rights request

A method for deleting a control plane tunnel, comprising:

Detecting a general packet radio service tunneling protocol between the local network entity and the peer network entity, and controlling the number of bearers managed by the GTP-C tunnel;

When the number of the bearers changes from greater than zero to zero, the Internet Protocol IP address assigned by the local network entity to the GTP-C tunnel and the tunnel endpoint identifier TEID are released.

2. The method according to claim 1, wherein when the local network entity is a mobility management entity MME, the peer network entity is a serving gateway;

When the local network entity is a serving gateway, the peer network entity is an MME;

When the local network entity is a serving GPRS serving node SGSN, the peer network entity is a serving gateway;

When the local network entity is a serving gateway, the peer network entity is an SGSN;

When the local network entity is a serving gateway, the peer network entity is a packet data network PDN gateway;

When the local network entity is a PDN gateway, the peer network entity is a serving gateway.

3. The method according to claim 1, wherein when the local network entity is a PDN gateway, the peer network entity is a serving gateway, and a GTP-C tunnel between the PDN gateway and the serving gateway Including at least two,

If the number of bearers managed by one GTP-C tunnel between the PDN gateway and the serving gateway is changed from greater than zero to zero, the IP address and TEID assigned by the PDN gateway to the GTP-C tunnel are released, and the reserved The IP address and TEID of other GTP-C tunnels between the PDN gateway and the serving gateway.

The method according to claim 1, wherein when the local network entity is a serving gateway, the peer network entity is a PDN gateway, and a GTP-C tunnel between the serving gateway and a PDN gateway Including at least two,

Number of bearers managed by a GTP-C tunnel between the serving gateway and the PDN gateway When it is changed from greater than zero to zero, the IP address and TEID assigned by the serving gateway to the GTP-C tunnel are released, and the IP addresses and TEIDs of other GTP-C tunnels between the serving gateway and the PDN gateway are reserved.

The method according to claim 2, wherein, when the local network entity is a serving gateway, the peer network entity is an SGSN, and the serving gateway detects idle state signaling of the user terminal UE. When the optimized ISR function is activated,

If the number of bearers managed by the GTP-C tunnel between the serving gateway and the SGSN changes from greater than zero to zero, releasing the IP address and TEID assigned by the serving gateway to the GTP-C tunnel, and

Retaining the IP address and TEID of the GTP-C tunnel between the serving gateway and the MME;

Keep the IP address and TEIDo of all GTP-C tunnels between the service gateway and all PDN gateways

The method according to claim 2, wherein, when the local network entity is a serving gateway, the peer network entity is an MME, and the serving gateway detects that the ISR function of the UE is activated,

If the number of bearers managed by the GTP-C tunnel between the serving gateway and the MME is changed from greater than zero to zero, releasing the IP address and TEID assigned by the serving gateway to the GTP-C tunnel, and

Retaining the IP address and TEID of the GTP-C tunnel between the serving gateway and the SGSN;

The IP address and TEID of all GTP-C tunnels between the service gateway and all PDN gateways are reserved.

The method according to claim 2, wherein when the local network entity is a serving gateway, and the serving gateway detects that the ISR function of the UE is activated,

If the serving gateway releases the IP address and TEID of all the GTP-C tunnels with all the PDN gateways, the serving gateway releases the IP addresses and TEIDs of all the GTP-C tunnels between the MME and the SGSN.

The method according to claim 2, wherein, when the local network entity is a serving gateway, and the serving gateway detects that the ISR function of the UE is disabled, If the serving gateway releases the IP address and TEID of all GTP-C tunnels with all PDN gateways, the serving gateway releases the IP address and TEID of the GTP-C tunnel with the MME or SGSN.

The method according to claim 2, wherein, when the local network entity is a serving gateway, and the serving gateway detects that the ISR function of the UE is activated,

If the serving gateway releases the IP address and TEID of all GTP-C tunnels between the MME and the SGSN, the serving gateway releases the IP addresses and TEIDs of all GTP-C tunnels with all PDN gateways.

The method according to claim 2, wherein, when the local network entity is a service gateway, and the serving gateway detects that the ISR function of the UE is disabled,

If the serving gateway releases the IP address and TEID of the GTP-C tunnel with the MME or the SGSN, the serving gateway releases the IP addresses and TEIDs of all the GTP-C tunnels with all the PDN gateways.

The method according to any one of claims 1-10, wherein the bearer is: the evolved packet system carries a bearer corresponding to the EPS Bearer Context or the packet data protocol context PDP Context.

12. A device for deleting a control plane tunnel, comprising:

a detecting unit, configured to detect a number of bearers managed by a general packet radio service tunnel protocol control plane GTP-C tunnel connected to the local network entity;

And a releasing unit, configured to release the Internet Protocol IP address and the tunnel endpoint identifier TEID allocated by the local network entity to the GTP-C tunnel when the number of the bearers changes from greater than zero to zero.

The apparatus according to claim 12, wherein the detecting unit comprises: a first detecting subunit, configured to detect a number of bearers managed by a GTP-C tunnel connected to the MME;

a second detecting subunit, configured to detect a number of bearers managed by a GTP-C tunnel connected to the SGSN;

a third detecting subunit, configured to detect a GTP-C tunnel managed by the serving gateway Number of bearers;

The fourth detecting subunit is configured to detect the number of bearers managed by a GTP-C tunnel connected to the PDN gateway.

The apparatus according to claim 12, wherein the releasing unit comprises: a first releasing subunit, configured to: when a number of bearers managed by one GTP-C tunnel connected to the MME is greater than zero When it becomes zero, the IP address and TEID allocated by the MME to the GTP-C tunnel are released;

a second release subunit, configured to release an IP address assigned by the SGSN to the GTP-C tunnel when a number of bearers managed by one GTP-C tunnel connected to the SGSN changes from greater than zero to zero TEID;

a third release subunit, configured to release an IP allocated by the serving gateway to the GTP-C tunnel when a number of bearers managed by one GTP-C tunnel connected to the serving gateway changes from greater than zero to zero Address and TEID;

a fourth release subunit, configured to release an IP allocated by the PDN gateway to the GTP-C tunnel when a number of bearers managed by one GTP-C tunnel connected to the PDN gateway changes from greater than zero to zero Address and TEID.

15. A service gateway, comprising:

a first release unit, configured to release the MME when the serving gateway detects that the ISR function of the user terminal UE is activated, and the serving gateway releases the IP address and the TEID of all the GTP-C tunnels with all the PDN gateways. IP address and TEID of all GTP-C tunnels between the SGSN and the SGSN;

a second release unit, configured to: when the serving gateway detects that the ISR function of the user terminal UE is activated, and the serving gateway releases the IP address and TEID of all GTP-C tunnels between the MME and the SGSN, release and all IP address and TEID of all GTP-C tunnels between PDN gateways;

a third release unit, configured to release the MME when the serving gateway detects that the ISR function of the user terminal UE is disabled, and the serving gateway releases the IP address and the TEID of all GTP-C tunnels with all the PDN gateways. Or the IP address and TEID of the GTP-C tunnel between the SGSNs;

a fourth release unit, configured to: when the serving gateway detects that the ISR function of the user terminal UE is off When the service gateway releases the IP address and TEID of the GTP-C tunnel with the ΜΜΕ or SGSN, the IP address and TEID of all GTP-C tunnels with all PDN gateways are released.