Background technology
In packet switching PS (PacketSwitch) territory of traditional second generation/3G (Third Generation) Moblie standard 2G/3G system, that use is general packet radio service gprs (General Packet Radio Service) tunnel protocol GTPv1 or GTPv0, and have only two interfaces to have general packet wireless service tunnel protocol control plane GTP-C tunnel to connect, one is that one is between SGSN and the SGSN between Serving GPRS Support Node SGSN (Serving GPRSSupport Node) and the Gateway GPRS Support Node GGSN (Gateway GPRS Support Node).For GTPv1, between SGSN and the GGSN, for packet data protocol PDP (the Packet Data Protocol) address of an access point name APN (Access Point Name), have only a GTP-C tunnel to connect with a mobile terminal UE (UserEquipment).For a user terminal UE,, then a GTP-C tunnel can only be arranged in the same moment if when having the GTP-C tunnel to be connected between SGSN and the SGSN.Is the pairing GTP user plane of the block data protocol context PDP Context GTP-U tunnel of the pdp address of identical APN of management and UE at SGSN with GTP-C tunnel between the GGSN.Have only between SGSN and the SGSN context request Context Request process and before change and just set up a GTP-C tunnel in the reorientation Forward Relocation process and be connected.
Traditional 2G/3G does not have the always online function of Internet protocol IP (Internet Protocol), and by the foundation of UE initiation packet data protocol contexts PDP Context and the foundation of the second block data protocol context Second PDP Context, only allow GGSN to initiate the foundation of Second PDP Context, GGSN does not allow the foundation of the PDP Context that initiates.Like this when UE initiates setting up of a PDPContext, SGSN has set up a GTP-C tunnel with GGSN and has been connected, PDPContext sets up a GTP-U tunnel for this reason simultaneously, when afterwards, when this PDP Context was deleted, then Dui Ying GTP-U tunnel was also deleted, according to agreement TS29.060, when all GTP-U tunnels of being managed when the GTP-C tunnel were all deleted, this GTP-C tunnel cannot be deleted.When all PDP Context of the shared same pdp address of UE and APN were deleted, its corresponding GTP-C tunnel also must keep, can not be deleted.When SGSN sends when setting up packet data protocol context request Create PDP Context Request to GGSN, as long as before this SGSN for this reason UE distributed Tunnel End Point Identifier TEID (Tunnel End Point Identifier) to be given to the GTP-C tunnel of GGSN, and confirmed by GGSN, then SGSN does not allow to be with TEID in this message, otherwise, SGSN just distributes a TEID, and is included in this message; In addition, if this GGSN before this for this reason UE distributed TEID to be given to the GTP-C tunnel of SGSN, and confirmed that then to send GTP employed TEID of this GTP message must be the TEID that GGSN distributes to SGSN, otherwise TEID=0 by SGSN; When GGSN responds when setting up block data protocol context response Create PDP Context Response to SGSN, also follow identical reason, as long as before this GGSN for this reason UE distributed TEID to be given to the GTP-C tunnel of SGSN, and confirmed by SGSN, then GGSN does not allow to be with TEID in this message, otherwise GGSN just distributes a TEID, and is included in this message; In addition, if this SGSN before this for this reason UE distributed TEID to be given to the GTP-C tunnel of GGSN, and confirmed by GGSN, then GGSN sends the TEID that GTP employed TEID of this GTP message must be the SGSN distribution, otherwise the TEID that TEID must use SGSN to be comprised in Create PDPContext Request; In addition, agreement TS29.060 does not point out that its corresponding GTP-C tunnel must be deleted when all PDP Context of the shared same pdp address of UE and APN are deleted.That is to say that when all PDPContext of the shared same pdp address of UE and APN were deleted, its corresponding GTP-C tunnel also must keep.Chief reason is that UE might also may create a PDP Context in the back again.
At present, there is following method in GTP-C tunnel between deletion GGSN and the SGSN, a clear and definite method is a update packet data protocol contexts Update PDP Context process, then the GGSN IP address in GTP-C tunnel and the TEID that will distribute to former SGSN continues to use to new SGSN, and old SGSN is when receiving that from home subscriber servers HSS (Home Subscriber Server) cancellation is landed CancelLocation and deleted the context Context of UE, with the IP address of distributing originally and TEID release to the GTP-C tunnel of GGSN.Another non-clear and definite method is as UE during by attachment removal, the IP address to the GTP-C tunnel of GGSN that SGSN will distribute originally discharges with TEID, this moment GGSN how to discharge original distribution to the IP address in the GTP-C tunnel of SGSN and TEID then in TS29.060, defining.
In evolved packet system EPS (Evolved Packet System), adopt new core network architecture, and the GTPv2 agreement is used in decision, in the EPS system, SGSN is arranged, gateway Serving GW (Serving Gateway), Mobility Management Entity MME (Mobility Management Entity), packet data network gateway PDN GW (Packet DataNetwork Gateway), as shown in Figure 1, S3, S4, S5, S8, S10, the S11 interface uses the GTPv2 agreement, and S8 is the roaming interface of S5.In addition, between SGSN and the PDN GW whether interface is arranged at present, and whether use the GTPv2 agreement not determine; Between same Serving GW and the GGSN whether interface is arranged, and whether use the GTPv2 agreement also not determine; Also have to be to use the GTPv1 agreement between present SGSN and the GGSN, in the 3GPP version afterwards, whether can use the GTPv2 agreement also is not determine.
The EPS system is a kind of novel 3GPP system, it is to support that IP is always online with a very big difference of traditional 2G/3G system, just in a single day work as UE and be registered in the EPS system, system just distributes an IP address to give this UE and activates an EPS carrying EPS Bearer.
In the EPS system, for a UE, between SGSN and Serving GW, have only being connected of a GTP-C tunnel, also have only being connected of a GTP-C tunnel between MME and the Serving GW.Between ServingGW and the PDN GW is to have at least a GTP-C tunnel to be connected, but the GTP-C tunnel between present MME and the Serving GW, GTP-C tunnel between SGSN and the Serving GW, the GTP-C tunnel between Serving GW and the PDN GW when or under what condition deletion all do not have clear and definite method.
Embodiment
In the embodiment of the invention, user mobile control management entity comprises MME or SGSN.PDN connects all EPS carrying set of identical APN of the use that is meant UE and identical IP address.The IP address refers to the IPv4 address, IPv6 address or IPv4 and IPv6 double address.EPS session management context ESMContext (EPS Session Management Context) is meant SGSN and the employed session management SM of Serving GW Context (Session Management Context), also refer to MME, ServingGW, the employed ESM Context of PDN GW, just ESM Context and SM Context do not do specific difference.
The embodiment of the invention provides a kind of method of deleting control plane tunnel, comprise: the number that detects the carrying of being managed in a general packet wireless service tunnel protocol control plane GTP-C tunnel between local terminal network entity and opposite end network entity, when the number of described carrying from greater than zero vanishing the time, discharge Internet protocol IP address and Tunnel End Point Identifier TEID that the local terminal network entity is distributed to described GTP-C tunnel.
For a UE, when the number of the bearer context of being stored in the described local terminal network entity from greater than zero vanishing the time, then discharge the IP address and the TEID in all GTP-C control plane tunnels that are connected with described network entity, and need not to notify opposite end, tunnel network entity.
The embodiment of the invention is applied in the EPS system between any two network entities managing carrying by GTP-C control plane tunnel, and then the local terminal network entity is MME, and the opposite end network entity is ServingGW; Perhaps the local terminal network entity is Serving GW, and the opposite end network entity is MME; Perhaps the local terminal network entity is SGSN, and the opposite end network entity is Serving GW; Perhaps the local terminal network entity is ServingGW, and the opposite end network entity is SGSN; Perhaps the local terminal network entity is Serving GW, and the opposite end network entity is PDN GW; Perhaps the local terminal network entity is PDN GW, and the opposite end network entity is Serving GW.
Be carried as: evolved packet system carries hereinafter EPS Bearer Context or the pairing carrying of block data protocol context PDP Context, and a carrying is corresponding to a packet wireless service tunnel protocol user plane GTP-U tunnel.
Below in conjunction with Figure of description the embodiment of the invention is described in further detail.The GTP-C tunnel of S4 interface correspondence among Fig. 1, for a UE, if whole EPS Bearer Context of the UE that SGSN and Serving GW are stored are deleted, or the ESM Context of UE is when deleted, the number of the carrying managed of the GTP-C tunnel between SGSN and Serving GW just is from greater than zero vanishing the time, and then SGSN and Serving GW discharge the IP address in the GTP-C tunnel between SGSN and Serving GW and TEID respectively and need not to notify the other side.
Same, GTP-C tunnel for S11 interface correspondence, for a UE, when if the ESM Context of whole EPS Bearer Context that MME and ServingGW stored or UE is deleted, the number of the carrying managed of the GTP-C tunnel between MME and Serving GW just is from greater than zero vanishing the time, and then MME and Serving GW discharge the IP address in above-mentioned GTP-C tunnel and TEID respectively and need not to notify the other side.Its specific implementation step as shown in Figure 2.
In the step 201, network entity A and other network entity are that UE has set up the GTP-C tunnel and is connected.
201a. network entity A and network entity B are UE have been set up a GTP-C tunnel and has been connected;
201b. network entity A and network entity C are UE have been set up a GTP-C tunnel and has been connected;
In the step 202, some or all EPS Bearer Context of the UE of network entity ESM Context deleted or UE is deleted, the number that just is connected the carrying of or whole GTP-C tunnels being managed with network entity is from greater than zero vanishing, and is specific as follows:
202a. if whole EPS Bearer Context ESMContext deleted or UE of UE is deleted among the network entity A, then network entity A discharges the whole IP address and the TEID in all GTP-C tunnels of being set up, be that network entity A release steps 201a is the IP address and the TEID in the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, be network entity B, network entity A release steps 201b is the IP address and the TEID in the GTP-C tunnel of UE foundation simultaneously, and need not to notify the peer node in tunnel, i.e. network entity C.
202b. if whole EPS Bearer Context ESMContext deleted or UE of UE is deleted among the network entity B, then network entity B discharges the whole IP address and the TEID in all GTP-C tunnels of being set up, be that network entity B release steps 201a is the IP address and the TEID in the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, i.e. network entity A.
202c. if whole EPS Bearer Context ESMContext deleted or UE of UE is deleted among the network entity C, then network entity C discharges the whole IP address and the TEID in all GTP-C tunnels of being set up, be that network entity C release steps 201b is the IP address and the TEID in the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, i.e. network entity A.
202d. if the carrying that the GTP-C tunnel between network entity A and the network entity B is managed is all deleted, even the carrying number of the GTP-C tunnel management between network entity A and the network entity B is from greater than zero vanishing, then network entity A release steps 201a is the IP address and the TEID in the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, i.e. network entity B.But network entity A keeps IP address and TEID that step 201b is the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, i.e. network entity C.
202e. if the whole carryings of the GTP-C UE that the tunnel is managed between network entity A and the network entity C are deleted, even the carrying number of the GTP-C tunnel management between network entity A and the network entity C is from greater than zero vanishing, then network entity A release steps 201b is the IP address and the TEID in the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, i.e. network entity C.But network entity A keeps IP address and TEID that step 201a is the GTP-C tunnel of UE foundation, and need not to notify the peer node in tunnel, i.e. network entity B.
Especially, in network switching process, when a network entity has been done reorientation in handoff procedure, therefore EPS Bearer Context and the ESM Context of UE are deleted in the old network entity, and the EPS Bearer Context of other network entity that is attached thereto and ESM Context still exist, therefore, still do not used the IP address in the GTP-C tunnel of its distribution to set up new GTP-C tunnel with TEID with new network entity by the network entity of reorientation and be connected, old network entity then discharges the IP address and the TEID in its all GTP-C tunnel that UE distributed for this reason.After being meant that as Fig. 3 a UE is registered to MME and activates EPS Bearer, UE is by PDN of old Serving GW and DPN GW access.Then, MME does not have to change and the handoff procedure of Serving GW reorientation is performed, and UE continues the original PDN of access by new ServingGW and PDN GW.Concrete implementation is as follows:
Step 301, after UE was registered to MME and activates EPS Bearer, UE was by old Serving GW and PDN of PDN GW visit.This process is specially:
301a.MME set up a GTP-C tunnel with old Serving GW.
301b. old Serving GW and PDN GW have set up a GTP-C tunnel.
Step 302, MME is constant, and the handoff procedure that Serving GW changes, in handoff procedure, UE switches to new Serving GW from old Serving GW.
Step 303, new Serving GW has set up GTP-C with MME with PDN GW and has been connected.
In this step, because of MME does not change, and EPS BearerContext or the ESM Context of this UE that MME stored do not have deleted, MME do not discharge and old Serving GW between be the IP address and the TEID in the GTP-C tunnel that UE distributed, these two parameters be respectively applied for that UE for this reason sets up and new Serving GW between the tunnel of GTP-C, i.e. execution in step 303a.Same, EPS Bearer Context or the ESM Context of the UE that is stored among the PDNGW do not have deleted, therefore PDN GW do not discharge and old Serving GW between the IP address and the TEID in the GTP-C tunnel that UE distributed for this reason, these two parameters be respectively applied for that UE for this reason sets up and new Serving GW between the tunnel of GTP-C, i.e. execution in step 303b.
Step 304, all EPS Bearer Context or the ESMContext of this UE is deleted on the old Serving GW.
Step 305 is the IP address and the TEID in all GTP-C tunnels that UE distributed between old Serving GW release and MME and all the PDN GW.
GTP-C tunnel with reference to S5 interface correspondence among Fig. 1, a PDN GW may support a plurality of APN, and for same APN, PDN GW may distribute an IPv4 address to UE, an IPv6 address, or an IPv4 and an IPv6 address (promptly distributing two IP addresses simultaneously).Like this, for the same APN under the same PDN GW, between PDN GW and the Serving GW a plurality of GTP-C tunnel might be arranged, the process of deleting the GTP-C tunnel between PDN GW and the Serving GW so comprises:
The number of the carrying of being managed when a GTP-C control plane tunnel between a PDN GW and Serving GW is from greater than zero vanishing the time, then described PDN GW discharges and distributes to the IP address and the TEID in described GTP-C control plane tunnel, and keeps the IP address and the TEID in other GTP-C tunnel between described PDN GW and Serving GW.
The number of the carrying of being managed when a GTP-C control plane tunnel between a Serving GW and PDN GW is from greater than zero vanishing the time, then described Serving GW discharges and distributes to the IP address and the TEID in described GTP-C control plane tunnel, and keeps the IP address and the TEID in other GTP-C tunnel between described Serving GW and PDN GW.
Just when the GTP-C tunnel between PDN GW and Serving GW comprises at least two, whole EPSBearer Context of the UE of a GTP-C tunnel management when between any one PDN GW and Serving GW are deleted, promptly by the time greater than zero vanishing, then PDN GW discharges IP address and the TEID that distributes to described GTP-C tunnel, keeps the IP address and the TEID in other GTP-C tunnel between described PDN GW and Serving GW.Equally, when the GTP-C tunnel between PDN GW and Serving GW comprises at least two, whole EPS Bearer Context of the UE of the GTP-C tunnel management when between any one Serving GW and PDN GW are deleted, promptly by the time greater than zero vanishing, then Serving GW discharges IP address and the TEID that distributes to described GTP-C tunnel, keeps the IP address and the TEID in other GTP-C tunnel between described Serving GW and PDNGW.
When all EPS Beare Context of the UE of all GTP-C tunnel managements between Serving GW and all PDN GW are deleted, then behind the IP address and TEID in the GTP-C tunnel between Serving GW release and all PDN GW, detect un-activation of ISR function or the deexcitation of UE as Serving GW, when promptly the ISR function that detects UE as Serving GW is closed, then the IP address and the TEID in the GTP-C tunnel that is connected with MME or SGSN of Serving GW release.
Detect un-activation of ISR function or the deexcitation of UE as Serving GW, behind the IP address and TEID in the GTP-C tunnel that Serving GW release is connected with MME or SGSN, Serving GW discharges the IP address and the TEID in the GTP-C tunnel between all Serving GW and PDN GW.
Another embodiment of the present invention is applied to the EPS system, and this moment, idle state signaling optimisation technique ISR (the Idle State Signalling Reduction) function of UE was activated.When the ISR of UE function is activated, this UE is registered on universal terrestrial access network UTRAN (Universal Terrestrial RadioAccess Network)/GSM EDGE Radio Access Network network GERAN (GSM/EDGE RadioAccess Network) and evolved universal terrestrial radio access network E-TURAN (Evolved UniversalTerrestrial Radio Access Network) the pairing user mobile control management entity of connecting system simultaneously, just is registered to simultaneously on SGSN and the MME.When UE is in Idle state, UE distributes among the route district RA (Routing Area) of UE and tracking area that MME the distributes to UE tabulation TA List (Tracking Area List) when mobile at SGSN, need not to do general Routing Area Update or general tracing section updating operation.When the ISR of UE function was activated, the user plane destination node of the UE of idle condition was positioned at ServingGW.
When the ISR function that detects mobile terminal UE as Serving GW is activated, there are GTP-C tunnel between MME and Serving GW and the GTP-C tunnel between SGSN and Serving GW simultaneously, if the number of the carrying that the GTP-C tunnel described in the described Serving GW between Serving GW and MME is managed is from greater than zero vanishing the time, Serving GW discharges the GTP-C tunnel between Serving GW and MME, the IP address and the TEID that keep the GTP-C tunnel between Serving GW and SGSN, and the IP address and the TEID that keep all the GTP-C tunnels between described gateway and all PDN GW.If the number of the carrying that the GTP-C tunnel described in the described Serving GW between Serving GW and SGSN is managed is from greater than zero vanishing the time, Serving GW discharges the GTP-C tunnel between Serving GW and SGSN, the IP address and the TEID that keep the GTP-C tunnel between Serving GW and MME, and the IP address and the TEID that keep all the GTP-C tunnels between described gateway and all PDN GW.Detailed process is as follows:
Serving GW receives the request message of whole EPSBearer Contex of the described UE of deletion that MME or SGSN send over; Or,
Described Serving GW asks described MME or SGSN to delete whole EPS BearerContex of described UE; Then,
Described Serving GW discharges IP address and the TEID that distributes to GTP-C tunnel between MME or SGSN.
In the embodiment of the invention, because described Serving GW stores ESM Context or the EPS Bearer Context of the relevant UE of SGSN or MME, then described Serving GW does not discharge IP address and the TEID that distributes to SGSN or MME tunnel.And because described Serving GW keeps and all PDN GW between the ESM Context or the EPS Bearer Context of all GTP-C tunnel managements, then described gateway do not discharge and all PDN GW between the IP address and the TEID in all GTP-C tunnels.
Work as SGSN, MME and Serving GW have activated the ISR function of UE, at this moment, between SGSN and the Serving GW, between MME and the Serving GW, and between PDN GW and the Serving GW are arranged being connected of GTP-C tunnel; If this moment, the non-clear and definite attachment removal process that MME initiates has taken place, MME only is labeled as UE the attachment removal state, and the ESM Context of last this UE of MME or all EPS Bearer Context are deleted, and request Serving GW deletes all EPSBearer of this UE, at this moment, because Serving GW finds the ISR function of UE and is activated, so Serving GW only deletes the ESM Context content of this UE relevant with MME, rather than delete the ESMContext of whole UE, just Serving GW also will keep the ESM Context of the UE relevant with SGSN.But the IP address and the TEID in the GTP-C tunnel between that Serving GW will discharge that UE distributed for this reason and the MME; Receive the deletion EPS Bearer response message of Serving GW as MME after, the IP address and the TEID in the GTP-C tunnel between that MME discharges that UE distributed for this reason and the Serving GW.
Behind the ISR of UE function activation, send the request message of all EPS Bearer Context of deletion UE to Serving GW as a user mobile control management entity MME or SGSN, and when receiving the response message of Serving GW, this user mobile control management entity is because of having deleted all EPS Bearer Context of this UE, therefore discharge the IP address and the TEID in the GTP-C tunnel that is connected with Serving GW of the UE that distributes to, and do not need to notify Serving GW.
Behind the ISR of UE function activation, when Serving GW when two user mobile control management entity MME of UE and SGSN ask to delete all EPS Bearer Context of UE simultaneously, obviously, Serving GW is with the IP address and the TEID in tunnel between release and MME and SGSN, simultaneously, ServingGW has also deleted all EPS Bearer Context of UE, be that ESM Context has also deleted, this moment Serving GW also will discharge and all PDN GW between the IP address and the TEID in all GTP-C tunnels.
Behind the ISR of UE function activation, when all EPS Beare Context of the UE of all GTP-C tunnel managements are deleted between Serving GW and all PDN GW, the IP address and the TEID in the GTP-C tunnel that is connected with SGSN with MME that described Serving GW is released to that described UE distributes.Detailed process can be such, finished the request of EPSBearer Context of the deletion UE that PDN GW sends as Serving GW after, after this EPS Bearer Context is deleted, if Serving GW finds that this UE has not had EPS Bearer Context, be that deleted EPS Bearer Context is the last EPS Bearer Context of UE, then Serving GW discharges GTP-C tunnel between last Serving GW and PDN GW, the IP address and the TEID in the GTP-C tunnel between that Serving GW discharges that UE distributed for this reason and MME and the SGSN.
Between SGSN and PDN GW interface is arranged, between Serving GW and the GGSN interface is arranged, when reaching the interface use GTPv2 agreement between SGSN and the GGSN, the described method of the embodiment of the invention still can be adapted on the above-mentioned interface.
Can make up a kind of device of deleting control plane tunnel according to embodiment of the invention said method, referring to Fig. 4, comprise: detecting unit 100 and releasing unit 200.
Detecting unit 100 is used to detect the number of the carrying of being managed in a general packet wireless service tunnel protocol control plane GTP-C tunnel being connected with the local terminal network entity;
Releasing unit 200, be used for when the number of described carrying from greater than zero vanishing the time, discharge Internet protocol IP address and Tunnel End Point Identifier TEID that the local terminal network entity is distributed to described GTP-C tunnel.
Wherein, detecting unit 100 comprises: first detection sub-unit 110, the second detection sub-unit, 120, the three detection sub-unit 130 and the 4th detection sub-unit 140.
First detection sub-unit 110 is used to detect the number of the carrying of being managed in a GTP-C tunnel being connected with MME.
Second detection sub-unit 120 is used to detect the number of the carrying of being managed in a GTP-C tunnel being connected with SGSN.
The 3rd detection sub-unit 130 is used to detect the number of the carrying of being managed in a GTP-C tunnel being connected with Serving GW.
The 4th detection sub-unit 140 is used to detect the number of the carrying of being managed in a GTP-C tunnel being connected with PDN GW.
Releasing unit 200 further comprises: first discharges subelement 210, the second discharges subelement 220, the three release subelements 230 and the 4th release subelement 240.
First discharges subelement 210, and the number that is used for the carrying managed when a GTP-C tunnel that is connected with described MME discharges IP address and TEID that described MME distributes to described GTP-C tunnel from greater than zero vanishing the time.
Second discharges subelement 220, and the number that is used for the carrying managed when a GTP-C tunnel that is connected with described SGSN discharges IP address and TEID that described SGSN distributes to described GTP-C tunnel from greater than zero vanishing the time.
The 3rd discharges subelement 230, and the number that is used for the carrying managed when a GTP-C tunnel that is connected with described Serving GW discharges IP address and TEID that described Serving GW distributes to described GTP-C tunnel from greater than zero vanishing the time.
The 4th discharges subelement 240, and the number that is used for the carrying managed when a GTP-C tunnel that is connected with described PDN GW discharges IP address and TEID that described PDN GW distributes to described GTP-C tunnel from greater than zero vanishing the time.
The embodiment of the invention also discloses a kind of gateway, comprising:
First releasing unit, be used for when the ISR functional status of described gateway detection mobile terminal UE is activated, and described gateway discharges and all PDN Gateway between when the IP address in all GTP-C tunnel and TEID, the IP address and the TEID in all GTP-C tunnels between release and MME and SGSN.
Second releasing unit, be used for when the ISR functional status of described gateway detection mobile terminal UE is activated, and when the IP address in all the GTP-C tunnels between described gateway release and MME and SGSN and TEID, the IP address and the TEID in all GTP-C tunnels between release and all PDN Gateway.
The 3rd releasing unit, be used for when the ISR functional status of described gateway detection mobile terminal UE is closed, and described gateway discharges and all PDN Gateway between when the IP address in all GTP-C tunnel and TEID, the IP address and the TEID in the GTP-C tunnel between release and MME or SGSN.
The 4th releasing unit, be used for when the ISR functional status of described gateway detection mobile terminal UE is closed, and when the IP address in the GTP-C tunnel between described gateway release and MME or SGSN and TEID, the IP address and the TEID in all GTP-C tunnels between release and all PDN Gateway.
The embodiment of the invention detects the number of the carrying of being managed in a general packet wireless service tunnel protocol control plane GTP-C tunnel between local terminal network entity and opposite end network entity, when the number of described carrying from greater than zero vanishing the time, discharge the local terminal network entity and distribute to the Internet protocol IP address and the Tunnel End Point Identifier TEID in described GTP-C tunnel, thereby guaranteed that IP is always online, simultaneously also save Internet resources, improved the overall performance of system.
Though described the present invention by embodiment, those of ordinary skills know, without departing from the spirit and substance in the present invention, just can make the present invention that many distortion and variation are arranged, and scope of the present invention is limited to the appended claims.