Background technology
At existing LTE (Long Term Evolution; Long Term Evolution) in the system, there is inter MME (Mobility Management Entity, Mobility Management Entity)/SGSN (Serving GPRS Supporting Node; Serving GPRS Support Node) inter SGW (Serving Gateway; Gateway) handoff procedure, for example, S1-Based Handover (based on the switching of S1 mouth) process.
As shown in Figure 1, the sketch map for a kind of S1-Based Handover process may further comprise the steps:
1, UE (User Equipment, subscriber equipment) Decision (decision) to trigger (triggering) a relocation (migration) via (via) S1.
2, Source eNodeB (source base station) sends Handover Required (demand) to Source MME.
3, Source MME is to Target (target) MME Forward (forwarding) Relocation Request (request).
4, Target MME sends Create (establishment) Session (session) Request to Target SGW.
4a, Target SGW send Create Session Response (response) to Target MME.
5, Target MME sends Handover Request to Target eNodeB.
5a, Target eNodeB send Handover Request ACKnowledge (affirmation) to Target MME.
6, Target MME sends Create Indirect (indirectly) Data (data) Forwarding (forwarding) Tunnel (tunnel) Request to Target SGW.
6a, Target SGW send Create Indirect Data Forwarding Tunnel Response to Target MME.
7, Target MME sends Forward Relocation Response to Source MME.
8, Source MME sends Create Indirect Data Forwarding Tunnel Request to Source SGW.
8a, Source SGW send Create Indirect Data Forwarding Tunnel Response to Source MME.
9, Source MME sends Handover Command (order) to Source eNodeB.
9a, Source eNodeB send Handover Command to UE.
10, Source eNodeB sends eNB Status (state) Transfer (transfer) to Source MME.
10a, Source MME send Forward Access (access) Context (context) Notification (notice) to Target MME.
10b, Target MME send Forward Access Context ACKnowledge to Source MME.
10c, Target MME send eNB Status Transfer to Target eNodeB.
11a, Source eNodeB send Only for Direct (directly) forwarding of data to Target eNodeB.
11b, Target eNodeB send Only for Indirect forwarding of data to Source SGW, Target SGW.
12, UE sends Handover Confirm (affirmation) to Target eNodeB.
13, Target eNodeB sends Handover Notify to Target MME.
14, Target MME sends Forward Relocation Complete (completion) Notification to Source MME.
14b, Source MME send Forward Relocation Complete Acknowledge to Target MME.
15, Target MME sends Modify (modification) Bearer (carrying) Request to Target SGW.
16, Target SGW sends Modify Bearer Request to HSS (Home Location Register, attaching position register).
16a, HSS send Modify Bearer Response to Target SGW.
17, Target SGW sends Modify Bearer Response to Target MME.
18, UE carries out Tracking Area Update procedure (tracking area update process).
19a, Source MME send UE Context Release (release) Command to Source eNodeB.
19b, Source eNodeB send UE Context Release Complete to Source MME.
19c, Source MME send Delete (deletion) Session Request to Source SGW.
19d, Source SGW send Delete Session Response to Source MME.
20a, Source MME send Delete Indirect Data Forwarding Tunnel Request to Source SGW.
20b, Source SGW send Delete Indirect Data Forwarding Tunnel Response to Source MME.
21a, Target MME send Delete Indirect Data Forwarding Tunnel Request to Target SGW.
21b, Target SGW send Delete Indirect Data Forwarding Tunnel Response to Target MME.
In flow process shown in Figure 1, be the processing procedure of a PDN Connection (connection), when supposing that UE supports a plurality of PDN Connection, then Fig. 1 only describes the wherein processing procedure of a PDN Connection.
In the prior art; At target MME when target SGW sends Create Session Request message; If when SGW can not set up the Contexts of default (acquiescence) Bearer that this PDN connects owing to reasons such as resources, then SGW need carry cause and refuse Create Session Request in Create Session Response.
Further; In step 5a process; When if Target eNodeB can not set up default Bearer owing to reasons such as resources; Then Target eNodeB need tell MME in Handover Request Acknowledge message, and MME can initiate this PDN connection of MME Initiated PDN Connection Deactivation (release) process deletion then.In step 19c, Source MME sends Delete Session Request message and gives Source SGW, the Bearer Contexts that this PDN of notice Source SGW deletion connects.
In realizing process of the present invention, the inventor finds to exist at least in the prior art following problem:
In the handover process of inter MME/SGSN inter SGW in the existing LTE system; If SGW has refused the Create Session Request message that target MME/SGSN sends; Then can not create the Bearer Context that this PDN connects on the SGW; If initiating PDN, target MME/SGSN this moment connects the deactivation process; To send Delete Session request and give SGW, SGW then can return Context not found and give target MME/SGSN in Delete Session Response message, and can Delete Session Request message not issued PGW (PDN GW).And the Delete Session request message that source MME/SGSN sends only arrives source SGW, and has only deleted the Bearer Context of this PDN Connecting on the source SGW.Therefore, the last Bearer Context that connects about this PDN of PGW will can not deleted.
Embodiment
In the LTE system of existing 3GPP; A UE possibly support a plurality of PDN Connection; And target SGW possibly appear because reasons such as resource refusal PDN connects the situation of the request of foundation in the non-X2 handoff procedure of inter MME/SGSN inter SGW; If this moment, UE had only a PDNConnection, then MME/SGSN can gravity treatment SGW, and the new PDN of initiation that lays equal stress on connects the process of setting up; If set up when successful but UE exists many PDN Connection and part PDN to connect, then MME/SGSN just can not gravity treatment SGW, but needs this PDN connection of deletion.
In the prior art; MME/SGSN can delete the Bearer Contexts of this last PDN Connection of SGW, PGW through initiating PDN Connection Deactivation process; And because the Bearer Contexts of this PDN Connection not on the SGW; Then SGW will return Context not found mistake; And SGW can not pass to PGW with Delete Session Request message, and promptly MME/SGSN can't delete the Bearer Context of the last PDN Connection of SGW, PGW through PDN Connection Deactivation process.
To the problems referred to above; Management method and equipment that the embodiment of the invention provides a kind of PDN to connect; The sign that connects through the PDN that can't delete sends to source MME/SGSN; Connect according to the corresponding PDN of sign deletion that this PDN connects by source MME/SGSN, in the handoff procedure of inter MME/SGSN inter SGW, can't delete the problem that is connected by the PDN of SGW refusal thereby solve.
To combine the accompanying drawing among the present invention below, the technical scheme among the present invention is carried out clear, intactly description, obviously, described embodiment only is a part of embodiment of the present invention, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills are not making the every other embodiment that is obtained under the creative work prerequisite, all belong to the scope of the present invention's protection.
The management method that the embodiment of the invention one provides a kind of PDN to connect; This method is applied in the handoff procedure of inter MME/SGSN inter SGW, and connected state UE switches under the application scenarios under the target side Mobility Management Entity from the source Mobility Management Entity.
Concrete; When connected state UE need switch to the target side base station from the source base station; Then handoff request message (Handover Required) can be sent to the source Mobility Management Entity in the source base station; Afterwards, the source Mobility Management Entity can be to target side Mobility Management Entity request message (Forward Relocation Request message), the information of having carried this connected state UE in this request message.
Further; After the target side Mobility Management Entity receives the request message from the source Mobility Management Entity; Because the information of having carried connected state UE in this request message, then the target side Mobility Management Entity can confirm that connected state UE switches to the target side Mobility Management Entity from the source Mobility Management Entity according to this request message.
Based on above-mentioned application scenarios, as shown in Figure 2, this method may further comprise the steps:
Step 201 connects as PDN and can't set up when successful, and the target side Mobility Management Entity is confirmed the PDN link information of said connected state UE.In the embodiment of the invention, this PDN link information includes but not limited to: the sign that this PDN connects.
In the embodiment of the invention; If Idle state UE has many PDN to connect; And during connecting, many PDN exist when setting up successful PDN connection (the PDN connection is admitted by target side SGW); If have PDN to connect can't to set up success (PDN connect excluded by target side SGW), then the target side Mobility Management Entity need be confirmed this and can't set up successful PDN link information.
In UMTS (Universal Mobile Telecommunications System, UMTS) system, Mobility Management Entity includes but not limited to SGSN.In EPS (Evolved Packet System, the grouping system of evolution) system, Mobility Management Entity includes but not limited to MME.
Describe for ease, in the embodiment of the invention, Mobility Management Entity is that example describes with MME/SGSN, and promptly the target side Mobility Management Entity can be target side (Target) MME/SGSN.
In this step, target side MME/SGSN confirms that the process of the sign that PDN connects is specially: when response message was set up in the session that has received from carrying of target side SGW Reason For Denial as target side MME/SGSN, target side MME/SGSN confirmed the sign that PDN connects.
Concrete; Target side MME/SGSN is receiving the Create Session Response message that target side SGW returns; And when having carried Reject Cause in the Create Session Response message; Target side MME/SGSN need note this PDN and connect, and confirms the sign that this PDN connects.
Further; Target side SGW is specially to the process that target side MME/SGSN returns the Create Session Response message of having carried Reject Cause: when target side SGW confirms to set up the default bearing context of PDN connection, send the session of carrying Reason For Denial (Reject Cause) to target side MME/SGSN and set up response message (Create Session Response message).
Step 202, target side MME/SGSN sends to the source Mobility Management Entity with the sign that PDN connects.
In the embodiment of the invention, in the UMTS system, Mobility Management Entity includes but not limited to SGSN.In the EPS system, Mobility Management Entity includes but not limited to MME.Describe for ease, the source Mobility Management Entity is that example describes with source MME/SGSN.
In this step; The process that the sign that target side MME/SGSN connects PDN sends to source MME/SGSN is specially: target side MME/SGSN notice source MME/SGSN about the sign that connected by the PDN of SGW refusal (for example; Default Bearer ID), and this PDN of notice source MME/SGSN connect because the SGW refusal causes and can't set up.
It should be noted that in the existing protocol between source MME/SGSN and the target side MME/SGSN interacting message is arranged, therefore, the sign that can adopt existing transmission of messages PDN to connect in the embodiment of the invention.
For example; Target side MME/SGSN need send Forward Relocation Response message to source MME/SGSN in the existing protocol; Be can be in the embodiment of the invention, make and to carry the sign that PDN connects in the Forward Relocation Response message through Forward Relocation Response message is expanded.Certainly, in the practical application, also can define a piece of news again and transmit the sign that this PDN connects.This message can be selected arbitrarily according to actual conditions.For example, this message can connect notification message (Delete PDN Connection Notification message) for deletion PDN.Describe for ease, describe with the example that is designated of transmitting this PDN connection through Forward Relocation Response message in the embodiment of the invention.Forward Relocation Response message after a kind of expansion as shown in table 1.
Table 1
Therefore; Through the Forward Relocation Response message after this expansion; Target side MME/SGSN can send to source MME/SGSN with the sign that PDN connects, i.e. portability PDN link information in the Forward Relocation Response message after the expansion.
Step 203, source MME/SGSN connects according to the corresponding PDN of sign deletion that PDN connects.
Concrete; Receive the sign of the PDN connection that can't set up because SGW refuses that target side MME/SGSN sends as source MME/SGSN after; Can confirm that the PDN of deletion connects according to the sign that this PDN connects; And connect dispose procedure (PDN Connection Deactivation process) and delete this PDN and connect through initiating PDN, this PDN connects in dispose procedure embodiment of the invention and gives unnecessary details no longer in detail.
In the embodiment of the invention, after source MME/SGSN had deleted corresponding PDN connection, target side MME/SGSN can know that by the PDN Connection of SGW refusal be deleted PDN Connection.
Further; All PDN for connected state UE connect; If target side MME/SGSN receives the session of having carried Reason For Denial that all PDN to this connected state UE from target side SGW connect when setting up response message, then target side MME/SGSN confirms that all PDN of this connected state UE connect and is excluded by target side SGW; At this moment, target side MME/SGSN can reselect target side SGW, and initiates the PDN connection to the target side SGW that reselects and set up process.
Certainly, in the practical application, target side MME/SGSN also can send to source MME/SGSN with the sign that each PDN connects, and is connected according to each PDN of sign deletion that PDN connects by source MME/SGSN.
Further, in practical application, in a plurality of PDN of knowing connected state UE connect, there is PDN to connect (one or more) and excluded by target side SGW; When other all PDN connections outside this PDN connection (one or more PDN that excluded by target side SGW connect) exclude by target side SGW admittance and by the target side base station; Then target side MME/SGSN need send the Forward Relocation Response message of carrying Reject cause to source MME/SGSN; Handle accordingly according to the Forward Relocation Response message that this carries Reject cause by source MME/SGSN that (need not delete PDN in this processing procedure connects; Can adopt existing mode to handle, repeat no more in this processing procedure embodiment of the invention).
In the embodiment of the invention; PDN connects the process that is excluded by target side SGW and comprises: when response message was set up in the session that has received from carrying of target side SGW Reason For Denial, then target side MME/SGSN confirmed that corresponding PDN connection is excluded by said target side SGW; In addition; The process that PDN connects by target side SGW admits and other PDN connections are excluded by the target side base station comprises: set up response message when receiving the session of accepting from the expression request of target side SGW; And when receiving the switch failure information of carrying Reason For Denial (Handover Failure message) from the target side base station, target side MME/SGSN confirms that corresponding PDN connection excludes by target side SGW admittance and by the target side base station.
It is thus clear that; In the embodiment of the invention; The sign that connects through the PDN that can't delete sends to source SGSN/MME; Connect according to the corresponding PDN of sign deletion that this PDN connects by source SGSN/MME, in the handoff procedure of inter MME/SGSN inter SGW, can't delete the problem that is connected by the PDN of SGW refusal thereby solve.
In order more clearly to set forth the technical scheme that the embodiment of the invention provides, the management method that this PDN connects is discussed in detail below in conjunction with concrete embodiment.The management method that the embodiment of the invention two provides a kind of PDN to connect, this method is that example describes with S1-based Handover process.As shown in Figure 3, this method may further comprise the steps:
1、UE?Decision?to?trigger?a?relocation?via?S1。
2, Source eNodeB sends Handover Required to Source MME.
3, Source MME is to Target MME Forward Relocation Request.
4, Target MME sends Create Session Request to Target SGW.
4a, Target SGW send Create Session Response to Target MME.
In this step, when Target SGW can not set up the default bearing context of PDN connection, need in Create Session Response message, carry reject cause; And after receiving the Create Session Response message of carrying reject cause as Target MME, think that promptly this PDN connection need be released, need this PDN of record to connect, and the sign that connects of definite PDN.
5, Target MME sends Handover Request to Target eNodeB.
In this step, can't set up because PDN connects, then when Target eNodeB sends Handover Request, Target MME need not ask to set up this PDN and connect in Handover Request message.
5a, Target eNodeB send Handover Request ACKnowledge to Target MME.
In addition; In practical application; When receiving Handover Request; Target eNodeB can also send Handover Failure message to Target MME, if when Target eNodeB connects owing to reasons such as own resource exclude PDN, can in Handover Failure message, carry Reason For Denial; When Target MME receives the Handover Failure message of having carried Reason For Denial, confirm that PDN connects because Target eNodeB refusal causes setting up success.
6, Target MME sends Create Indirect Data Forwarding Tunnel Request to Target SGW.
6a, Target SGW send Create Indirect Data Forwarding Tunnel Response to Target MME.
7, Target MME sends Forward Relocation Response message to Source MME.
In this step; Because Target MME can send Forward Relocation Response message to Source MME; Then through Forward Relocation Response message is expanded; Can carry the sign (like the Default Bearer ID that this PDN connects, the sign that the PDN that promptly writes down among the step 4a connects) that PDN connects in the Forward Relocation Response message after expansion.
Further, Source MME/SGSN then initiates PDN Connection Deactivation process after receiving the Forward Relocation Response message of carrying Default Bearer ID, the PDN Connection that deletion is relevant.
8, Source MME sends Create Indirect Data Forwarding Tunnel Request to Source SGW.
8a, Source SGW send Create Indirect Data Forwarding Tunnel Response to Source MME.
9, Source MME sends Handover Command to Source eNodeB.
9a, Source eNodeB send Handover Command to UE.
10, Source eNodeB sends eNB Status Transfer to Source MME.
10a, Source MME send Forward Access Context Notification to Target MME.
10b, Target MME send Forward Access Context ACKnowledge to Source MME.
10c, Target MME send eNB Status Transfer to Target eNodeB.
11a, Source eNodeB send Only for Direct forwarding of data to Target eNodeB.
11b, Target eNodeB send Only for Indirect forwarding of data to Source SGW, Target SGW.
12, UE sends Handover Confirm to Target eNodeB.
13, Target eNodeB sends Handover Notify to Target MME.
14, Target MME sends Forward Relocation Complete Notification to Source MME.
14b, Source MME send Forward Relocation Complete Acknowledge to Target MME.
15, Target MME sends Modify Bearer Request to Target SGW.
16, Target SGW sends Modify Bearer Request to HSS.
16a, HSS send Modify Bearer Response to Target SGW.
17, Target SGW sends Modify Bearer Response to Target MME.
18, UE carries out Tracking Area Update procedure.
19a, Source MME send UE Context Release Command to Source eNodeB.
19b, Source eNodeB send UE Context Release Complete to Source MME.
19c, Source MME send Delete Session Request to Source SGW.
19d, Source SGW send Delete Session Response to Source MME.
20a, Source MME send Delete Indirect Data Forwarding Tunnel Request to Source SGW.
20b, Source SGW send Delete Indirect Data Forwarding Tunnel Response to Source MME.
21a, Target MME send Delete Indirect Data Forwarding Tunnel Request to Target SGW.
21b, Target SGW send Delete Indirect Data Forwarding Tunnel Response to Target MME.
It is thus clear that; In the embodiment of the invention; The sign that connects through the PDN that can't delete sends to source SGSN/MME; Connect according to the corresponding PDN of sign deletion that this PDN connects by source SGSN/MME, in the handoff procedure of interMME/SGSN inter SGW, can't delete the problem that is connected by the PDN of SGW refusal thereby solve.
Based on the inventive concept same with said method, the management equipment that also provides a kind of PDN to connect in the embodiment of the invention, as shown in Figure 4, comprising:
Receiver module 41 has been used to receive from carrying of source Mobility Management Entity the request message of connected state UE information;
First determination module 42 is used for confirming that according to the request message that said receiver module 41 receives said connected state UE switches to the target side Mobility Management Entity from said source Mobility Management Entity;
Second determination module 43 is used for confirming the PDN link information of said connected state UE;
Sending module 44 is used for the PDN link information that said second determination module 43 is confirmed is sent to said source Mobility Management Entity; Indicating said source Mobility Management Entity to delete said PDN according to said PDN link information connects.
Said second determination module 43; Specifically be used for when response message is set up in the session that has received from carrying of target side SGW Reason For Denial; Confirm that this session sets up the corresponding PDN of response message and connect and excluded by said target side SGW, and confirm said PDN link information.
Said second determination module 43; Also be used for when response message is set up in the session of having carried Reason For Denial that all PDN to said connected state UE that receive from said target side SGW connect, all PDN that confirm said connected state UE connect and are excluded by said target side SGW;
Reselect target side SGW, and initiate the PDN connection to the target side SGW that reselects and set up process.
Said second determination module 43 specifically is used for having the PDN connection to be excluded by said target side SGW when a plurality of PDN of knowing said connected state UE connect; When all PDN connections of other outside said PDN connects exclude by said target side SGW admittance and by the target side base station, send the Forward Relocation Response message of carrying Reject cause to the source Mobility Management Entity.
Said second determination module 43 is further used for when response message is set up in the session that has received from carrying of target side SGW Reason For Denial, confirms that corresponding PDN connection is excluded by said target side SGW;
Set up response message when receiving the session of accepting from the expression request of target side SGW; And receive from the target side base station carry the switch failure information of Reason For Denial the time, confirm that corresponding PDN connects by said target side SGW to admit and excluded by the target side base station.
Said second determination module 43; Specifically be used for connecting when said Idle state UE has many PDN; And exist during many PDN connect when setting up successful PDN connection, excluded by said target side SGW, then confirm this PDN link information that is excluded by said target side SGW if there is PDN to connect.
Said sending module 44 specifically is used for said PDN link information and PDN connects because the information that target side SGW refusal causes setting up sends to said source Mobility Management Entity.
Said sending module 44; Specifically be used for through expanding current Forward Relocation Response message, and said PDN link information sent to said source Mobility Management Entity through the Forward Relocation Response message after the expansion.
Wherein, each module of apparatus of the present invention can be integrated in one, and also can separate deployment.Above-mentioned module can be merged into a module, also can further split into a plurality of submodules.
It is thus clear that; In the embodiment of the invention; The sign that connects through the PDN that can't delete sends to source SGSN/MME; Connect according to the corresponding PDN of sign deletion that this PDN connects by source SGSN/MME, in the handoff procedure of inter MME/SGSN inter SGW, can't delete the problem that is connected by the PDN of SGW refusal thereby solve.
Based on the inventive concept same with said method, the management equipment that also provides a kind of PDN to connect in the embodiment of the invention, as shown in Figure 5, comprising:
Receiver module 51 is used for when the target side Mobility Management Entity is confirmed the PDN link information, receives the said PDN link information from said target side Mobility Management Entity;
Removing module 52 is used for deleting said PDN according to the PDN link information that said receiver module 51 receives and connects.
Said receiver module 51 specifically is used to receive from the said PDN link information of said target side Mobility Management Entity and PDN and connects because target side SGW refusal causes the information that can't set up.
Said receiver module 51 specifically is used to receive the Forward Relocation Response message from after the expansion of said target side Mobility Management Entity, carries said PDN link information among the Forward Relocation Response after the said expansion.
Said removing module 52 specifically is used for confirming that according to said PDN link information the PDN of needs deletion connects, and deletes said PDN connection through PDN connection dispose procedure.
In the embodiment of the invention, said PDN link information comprises the sign that said PDN connects.
Wherein, each module of apparatus of the present invention can be integrated in one, and also can separate deployment.Above-mentioned module can be merged into a module, also can further split into a plurality of submodules.
It is thus clear that; In the embodiment of the invention; The sign that connects through the PDN that can't delete sends to source SGSN/MME; Connect according to the corresponding PDN of sign deletion that this PDN connects by source SGSN/MME, in the handoff procedure of inter MME/SGSN inter SGW, can't delete the problem that is connected by the PDN of SGW refusal thereby solve.
Through the description of above execution mode, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware, but the former is better execution mode under a lot of situation.Based on such understanding; The part that technical scheme of the present invention contributes to prior art in essence in other words can be come out with the embodied of software product; This computer software product is stored in the storage medium; Comprise some instructions with so that computer equipment (can be personal computer, server, the perhaps network equipment etc.) carry out the described method of each embodiment of the present invention.
It will be appreciated by those skilled in the art that accompanying drawing is the sketch map of a preferred embodiment, module in the accompanying drawing or flow process might not be that embodiment of the present invention is necessary.
It will be appreciated by those skilled in the art that the module in the device among the embodiment can be distributed in the device of embodiment according to the embodiment description, also can carry out respective change and be arranged in the one or more devices that are different from present embodiment.The module of the foregoing description can be merged into a module, also can further split into a plurality of submodules.
The invention described above embodiment sequence number is not represented the quality of embodiment just to description.
More than disclosedly be merely several specific embodiment of the present invention, still, the present invention is not limited thereto, any those skilled in the art can think variation all should fall into protection scope of the present invention.