The management method that a kind of PDN connects and equipment
Technical field
The present invention relates to communication technical field, especially relate to management method and the equipment of a kind of PDN connection.
Background technology
At existing LTE (Long Term Evolution, Long Term Evolution) in 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, such as, S1-Based Handover (switching based on S1 mouth) process.
As shown in Figure 1, be a kind of schematic diagram of S1-Based Handover process, comprise the following 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 sends Create Session Response (response) to Target MME.
5, Target MME sends Handover Request to Target eNodeB.
5a, Target eNodeB sends Handover Request ACKnowledge (confirmation) to Target MME.
6, Target MME sends Create Indirect (indirectly) Data (data) Forwarding (forwarding) Tunnel (tunnel) Request to Target SGW.
6a, Target SGW sends Greate 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 sends Create Indirect Data Forwarding Tunnel Response to Source MME.
9, Source MME sends Handover Command (order) to Source eNodeB.
9a, Source eNodeB sends Handover Command to UE.
10, Source eNodeB sends eNB Status (state) Transfer (transfer) to Source MME.
10a, Source MME sends Forward Access (access) Context (context) Notification (notice) to Target MME.
10b, Target MME sends Forward Access Context ACKnowledge to Source MME.
10c, Target MME sends eNB Status Transfer to Target eNodeB.
11a, Source eNodeB sends Only for Direct (directly) forwarding of data to Target eNodeB.
11b, Target eNodeB sends Only for Indirect forwarding of dara to Source SGW, Target SGW.
12, UE sends Handover Confirm (confirmation) to Target eNodeB.
13, Target eNodeB sends Handover Notify to Target MME.
14, Target MME sends ForwardRelocation Complete (completing) Notification to Source MME.
14b, Source MME sends Forward Relocation Complete Acknowledge to Target MME.
15, Target MME sends Modify (amendment) 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 performs Tracking Area Update procedure (tracking area update process).
19a, Source MME sends UE Context Release (release) Command to Source eNodeB.
19b, Source eNodeB sends UE Context Release Complete to Source MME.
19c, Source MME sends Delete (deletion) Session Request to Source SGW.
19d, Source SGW sends Delete Session Response to Source MME.
20a, Source MME sends Delete Indirect Data Forwarding Tunnel Request to Source SGW.
20b, Source SGW sends Delete Indirect Data Forwarding Tunnel Response to Source MME.
21a, Target MME sends Delete Indirect Data Forwarding Tunnel Request to Target SGW.
21b, Target SGW sends Delete Indirect Data Forwarding Tunnel Response to Target MME.
In the flow process shown in Fig. 1, be the processing procedure of a PDN Connection (connection), when supposing that UE supports multiple PDN Connection, then Fig. 1 only describes the processing procedure of a wherein PDN Connection.
In prior art, when target MME sends Create Session Request message to target SGW, if SGW due to the reasons such as resource can not set up the Contexts of default (acquiescence) Bearer that this PDN connects time, then SGW needs carry cause to refuse CreateSession Request in Create Session Response.
Further, in step 5a process, if Target eNodeB due to the reasons such as resource can not set up default Bearer time, then Targete NodeB needs to tell MME in Handover Request Acknowledge message, and then MME can initiate MME Initiated PDN Connection Deactivation (release) process and deletes this PDN and connect.In step 19c, Source MME sends Delete Session Request message to Source SGW, and notice Source SGW deletes the Bearer Contexts that this PDN connects.
Realizing in process of the present invention, inventor finds at least there is following problem in prior art:
In the handover process of the inter MME/SGSN inter SGW in existing LTE system, if SGW have rejected the Create Session Request message that target MME/SGSN sends, then SGW can not create the Bearer Context that this PDN connects, if now target MME/SGSN initiates PDN connection deactivation process, Delete Session request will be sent to SGW, SGW then can return Contextnot found to target MME/SGSN in Delete Session Response message, and Delete Session Request message can not be issued PGW (PDN GW).And the Delete Session request message that source MME/SGSN sends only arrives source SGW, and only delete the Bearer Context of this PDN Connecting on source SGW.Therefore, the upper Bearer Context about this PDN connection of PGW can not be deleted.
Summary of the invention
The management method that the embodiment of the present invention provides a kind of PDN to connect and equipment, connect to delete PDN in handoff procedure.
In order to achieve the above object, the embodiment of the present invention provides a kind of PDN management method connected, and comprising:
Target side Mobility Management Entity receives the request message carrying connected state UE information from source Mobility Management Entity, and determines that described connected state UE is switched to described target side Mobility Management Entity from described source Mobility Management Entity according to described request message;
Described target side Mobility Management Entity determines the PDN link information of described connected state UE;
Described PDN link information is sent to described source Mobility Management Entity by described target side Mobility Management Entity; Indicate described source Mobility Management Entity to delete described PDN according to described PDN link information to connect.
The embodiment of the present invention provides a kind of PDN management equipment connected, and comprising:
Receiver module, for receiving the request message carrying connected state UE information from source Mobility Management Entity;
First determination module, the request message for receiving according to described receiver module determines that described connected state UE is switched to target side Mobility Management Entity from described source Mobility Management Entity;
Second determination module, for determining the PDN link information of described connected state UE;
Sending module, the PDN link information for being determined by described second determination module sends to described source Mobility Management Entity; Indicate described source Mobility Management Entity to delete described PDN according to described PDN link information to connect.
The embodiment of the present invention provides a kind of PDN management method connected, and comprising:
Source Mobility Management Entity receives the PDN link information from target side Mobility Management Entity;
Described source Mobility Management Entity is deleted described PDN according to described PDN link information and is connected.
The embodiment of the present invention provides a kind of PDN management equipment connected, and comprising:
Receiver module, for receiving the described PDN link information from described target side Mobility Management Entity;
Removing module, the PDN link information for receiving according to described receiver module is deleted described PDN and is connected.
Compared with prior art, the embodiment of the present invention at least has the following advantages:
The mark connected by the PDN that cannot delete sends to source SGSN/MME, delete corresponding PDN by source SGSN/MME according to the mark that this PDN connects to connect, thus solve the problem cannot deleted in the handoff procedure of interMME/SGSN inter SGW and be connected by the PDN that SGW refuses.
Accompanying drawing explanation
In order to be illustrated more clearly in technical scheme of the present invention, below the accompanying drawing used required in describing embodiment is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the schematic diagram of S1-Based Handover process in prior art;
Fig. 2 is the management method schematic flow sheet of a kind of PDN connection that the embodiment of the present invention one provides;
Fig. 3 is the management method schematic flow sheet that under a kind of S1-Based Handover scene of providing of the embodiment of the present invention two, PDN connects;
Fig. 4 is the structural representation of the management equipment of a kind of PDN connection that the embodiment of the present invention provides;
Fig. 5 is the structural representation of the management equipment of the another kind of PDN connection that the embodiment of the present invention provides.
Embodiment
In the LTE system of existing 3GPP, a UE may support multiple PDN Connection, and target SGW may be there is because the situation of the reason refusal PDN connection establishment requests such as resource in the non-X2 handoff procedure of inter MME/SGSN inter SGW, if now UE only has a PDNConnection, then MME/SGSN can gravity treatment SGW, and again initiates PDN connection establishment process; If but UE there are many PDN Connection and part PDN connects when being successfully established, then MME/SGSN just can not gravity treatment SGW, but needs to delete this PDN and connect.
In prior art, MME/SGSN can delete the Bearer Contexts of this PDN Connection on SGW, PGW by initiating PDN Connection Deactivation process, and due to the Bearer Contexts of not this PDN Connection on SGW, then SGW will return Contextnot found mistake, and SGW can not by Delete Session Request Message Transmission to PGW, namely MME/SGSN cannot delete the Bearer Context of the PDNConnection on SGW, PGW by PDN Connection Deactivation process.
For the problems referred to above, the management method that the embodiment of the present invention provides a kind of PDN to connect and equipment, the mark connected by the PDN that cannot delete sends to source MME/SGSN, delete corresponding PDN by source MME/SGSN according to the mark that this PDN connects to connect, thus solve the problem cannot deleted in the handoff procedure of interMME/SGSNinter SGW and be connected by the PDN that SGW refuses.
Below in conjunction with the accompanying drawing in the present invention, be clearly and completely described the technical scheme in the present invention, obviously, described embodiment is only a part of embodiment of the present invention, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
The embodiment of the present invention one provides a kind of PDN management method connected, the method is applied in the handoff procedure of interMME/SGSN inter SGW, and connected state UE is switched under the application scenarios the Mobility Management Entity of target side from source Mobility Management Entity.
Concrete, when connected state UE needs to be switched to base station, target side from source base station, then source base station can send handover request message (Handover Required) to source Mobility Management Entity, afterwards, source Mobility Management Entity to target sidesway mobility management entity requests message (Forward Relocation Request message), can carry the information of this connected state UE in this request message.
Further, after target side Mobility Management Entity receives the request message from source Mobility Management Entity, owing to carrying the information of connected state UE in this request message, then target side Mobility Management Entity can be switched to target side Mobility Management Entity according to this request message determination connected state UE from source Mobility Management Entity.
Based on above-mentioned application scenarios, as shown in Figure 2, the method comprises the following steps:
Step 201, when there being PDN connection to be successfully established, target side Mobility Management Entity determines the PDN link information of described connected state UE.In the embodiment of the present invention, this PDN link information includes but not limited to: the mark that this PDN connects.
In the embodiment of the present invention, if Idle state UE has many PDN to connect, and when there is PDN connection (PDN connection is received by target side SGW) that be successfully established in many PDN connections, if have PDN to connect cannot be successfully established (PDN connect excluded by target side SGW), then target side Mobility Management Entity needs the PDN link information of determining that this cannot be successfully established.
In UMTS (Universal Mobile Telecommunications System, universal mobile telecommunications system) 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.
For convenience of description, in the embodiment of the present invention, Mobility Management Entity is described for MME/SGSN, and namely target side Mobility Management Entity can be target side (Target) MME/SGSN.
In this step, target side MME/SGSN determines that the process of the mark that PDN connects is specially: when target side MME/SGSN receive from target side SGW carry the session establishment response message of Reason For Denial time, target side MME/SGSN determines the mark that PDN connects.
Concrete, the Create Session Response message that target side MME/SGSN is receiving target side SGW and returns, and when carrying Reject Cause in Create Session Response message, target side MME/SGSN needs to record this PDN and connects, and determines the mark that this PDN connects.
Further, target side SGW returns process from the Create Session Response message carrying Reject Cause to target side MME/SGSN is specially: when target side SGW determines the default bearing context can not setting up PDN connection, send the session establishment response message (Create Session Response message) carrying Reason For Denial (Reject Cause) to target side MME/SGSN.
Step 202, the mark that PDN connects is sent to source Mobility Management Entity by target side MME/SGSN.
In the embodiment of the present invention, in the umts system, Mobility Management Entity includes but not limited to SGSN.In EPS, Mobility Management Entity includes but not limited to MME.For convenience of description, source Mobility Management Entity is described for source MME/SGSN.
In this step, the mark that PDN connects sends to the process of source MME/SGSN to be specially by target side MME/SGSN: target side MME/SGSN notifies that mark that source MME/SGSN connects about the PDN refused by SGW (such as, Default Bearer ID), and notify that this PDN of source MME/SGSN connects because SGW refusal causes setting up.
It should be noted that in existing protocol, between source MME/SGSN and target side MME/SGSN, have interacting message, therefore, the mark that existing transmission of messages PDN connects in the embodiment of the present invention, can be adopted.
Such as, in existing protocol, target side MME/SGSN needs to send Forward Relocation Response message to source MME/SGSN, namely by expanding ForwardRelocation Response message, the mark can carrying PDN connection in Forward Relocation Response message can be made in the embodiment of the present invention.Certainly, in practical application, the mark that a piece of news connects to transmit this PDN also can be redefined.This message can be selected arbitrarily according to actual conditions.Such as, this message can connect notification message (Delete PDN Connection Notification message) for deleting PDN.For convenience of description, the example that is designated connected to be transmitted this PDN by Forward Relocation Response message in the embodiment of the present invention is described.Forward Relocation Response message after a kind of expansion as shown in table 1.
Table 1
Therefore, by the Forward Relocation Response message after this expansion, the mark that PDN connects can be sent to source MME/SGSN by target side MME/SGSN, can carry PDN link information in the Forward Relocation Response message namely after expansion.
Step 203, source MME/SGSN deletes corresponding PDN according to the mark that PDN connects and connects.
Concrete, after source MME/SGSN receives the mark of the PDN connection cannot set up due to SGW refusal that target side MME/SGSN sends, the mark that can connect according to this PDN determines that the PDN deleted connects, and delete this PDN connect by initiating PDN Connection Release process (PDN Connection Deactivation process), repeat no longer in detail in this PDN Connection Release process embodiment of the present invention.
In the embodiment of the present invention, after source MME/SGSN deletes corresponding PDN connection, target side MME/SGSN can know that by the PDN Connection that SGW refuses be deleted PDNConnection.
Further, all PDN for connected state UE connect, if when what the MME/SGSN all PDN for this connected state UE received from target side SGW in target side connected carries the session establishment response message of Reason For Denial, then target side MME/SGSN determines that all PDN of this connected state UE connect and is excluded by target side SGW; Now, target side MME/SGSN can reselect target side SGW, and initiates PDN connection establishment process to the target side SGW reselected.
Certainly, in practical application, the mark that each PDN connects also can be sent to source MME/SGSN by target side MME/SGSN, deletes each PDN connect by source MME/SGSN according to the mark that PDN connects.
Further, in actual applications, when knowing during multiple PDN of connected state UE connect that having PDN to connect (one or more) is excluded by target side SGW, this PDN other all PDN connected outside (being connected by one or more PDN that target side SGW excludes) connect and to be received by target side SGW and when being excluded by base station, target side, then target side MME/SGSN needs to send the Forward Relocation Response message of carrying Reject cause to source MME/SGSN, the Forward Relocation Response message of carrying Reject cause according to this by source MME/SGSN processes accordingly (not to be needed to delete PDN to connect in this processing procedure, existing mode can be adopted to process, repeat no more in this processing procedure embodiment of the present invention).
In the embodiment of the present invention, PDN connects and is comprised by the process that target side SGW excludes: when receive from target side SGW carry the session establishment response message of Reason For Denial time, then target side MME/SGSN determines that corresponding PDN connects and is excluded by described target side SGW; In addition, PDN connects by target side SGW receiving and other PDN connection is comprised by the process that base station, target side excludes: when receiving the session establishment response message accepted from the expression request of target side SGW, and when receiving switch failure information (the Handover Failure message) of carrying Reason For Denial from base station, target side, target side MME/SGSN determines that corresponding PDN connects by target side SGW receiving and excluded by base station, target side.
Visible, in the embodiment of the present invention, the mark connected by the PDN that cannot delete sends to source SGSN/MME, delete corresponding PDN by source SGSN/MME according to the mark that this PDN connects to connect, thus solve the problem cannot deleted in the handoff procedure of inter MME/SGSN inter SGW and be connected by the PDN that SGW refuses.
In order to the technical scheme that the elaboration embodiment of the present invention clearly provides, below in conjunction with specific embodiment, the management method that this PDN connects is discussed in detail.The embodiment of the present invention two provides a kind of PDN management method connected, and the method is described for S1-based Handover process.As shown in Figure 3, the method comprises the following steps:
1、UE?Decision?to?trigger?a?relocation?via?S1。
2, Source eNodeB sends Handover Required to Source MME.
3, Source MME is to TargetMMEForwardRelocation Request.
4, Target MME sends CreateSession Request to Target SGW.
4a, Target SGW sends Create Session Response to Target MME.
In this step, when Target SGW can not set up the default bearing context of PDN connection, need to carry reject cause in Create Session Response message; And after Target MME receives the Create Session Response message of carrying reject cause, namely think that this PDN connects needs and is released, needing to record this PDN connects, and determines the mark that PDN connects.
5, Target MME sends Handover Request to Target eNodeB.
In this step, cannot set up because PDN connects, then, when sending Handover Request to Target eNodeB, TargetMME does not need in Handover Request message, ask to set up this PDN and connects.
5a, Target eNodeB sends Handover Request ACKnowledge to Target MME.
In addition, in actual applications, when receiving Handover Request, Target eNodeB can also send Handover Failure message to Target MME, if Target eNodeB due to the reasons such as own resource exclude PDN connect time, Reason For Denial can be carried in Handover Failure message, when Target MME receives the Handover Failure message carrying Reason For Denial, determine that PDN connects because Target eNodeB refusal causes being successfully established.
6, Target MME sends Create Indirect Data Forwarding Tunnel Request to Target SGW.
6a, Target SGW sends 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 by expanding Forward Relocation Response message, the mark (as the mark that the Default Bearer ID that this PDN connects, the PDN namely recorded in step 4a connect) that PDN connects can be carried in Forward Relocation Response message after expansion.
Further, after Source MME/SGSN receives the Forward Relocation Response message of carrying Default Bearer ID, then initiate PDN Connection Deactivation process, delete relevant PDN Connection.
8, SourceMME sends Create Indirect Data Forwarding Tunnel Request to Source SGW.
8a, Source SGW sends Create Indirect Data Forwarding Tunnel Response to Source MME.
9, Source MME sends Handover Command to Source eNodeB.
9a, Source eNodeB sends Handover Command to UE.
10, Source eNodeB sends eNB Status Transfer to Source MME.
10a, Source MME sends Forward Access ContextNotification to Target MME.
10b, Target MME sends Forward Access Context ACKnowledge to Source MME.
10c, Target MME sends eNB Status Transfer to Target eNodeB.
11a, Source eNodeB sends Only for Direct forwarding of data to Target eNodeB.
11b, Target eNodeB sends 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 sends ForwardRelocation CompleteAcknowledge 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 TargetSGW.
17, TargetSGW sends Modify Bearer Response to TargetMME.
18, UE performs Tracking Area Update procedure.
19a, Source MME sends UE Context Release Command to Source eNodeB.
19b, Source eNodeB sends UE Context Release Complete to Source MME.
19c, SourceMME send Delete Session Request to Source SGW.
19d, Source SGW sends Delete Session Response to Source MME.
20a, Source MME sends Delete Indirect Data Forwarding Tunnel Request to Source SGW.
20b, Source SGW sends Delete Indirect Data ForwardingTunnel Response to Source MME.
21a, Target ME sends Delete Indirect Data Forwarding Tunnel Request to Target SGW.
21b, Target SGW sends Delete Indirect Data Forwarding Tunnel Response to Target MME.
Visible, in the embodiment of the present invention, the mark connected by the PDN that cannot delete sends to source SGSN/MME, delete corresponding PDN by source SGSN/MME according to the mark that this PDN connects to connect, thus solve the problem cannot deleted in the handoff procedure of inter MME/SGSN inter SGW and be connected by the PDN that SGW refuses.
Based on the inventive concept same with said method, additionally provide the management equipment that a kind of PDN connects in the embodiment of the present invention, as shown in Figure 4, comprising:
Receiver module 41, for receiving the request message carrying connected state UE information from source Mobility Management Entity;
For the request message received according to described receiver module 41, first determination module 42, determines that described connected state UE is switched to target side Mobility Management Entity from described source Mobility Management Entity;
Second determination module 43, for determining the PDN link information of described connected state UE;
Sending module 44, sends to described source Mobility Management Entity for the PDN link information determined by described second determination module 43; Indicate described source Mobility Management Entity to delete described PDN according to described PDN link information to connect.
Described second determination module 43, specifically for when receive from target side SGW carry the session establishment response message of Reason For Denial time, determine that the PDN connection that this session establishment response message is corresponding is excluded by described target side SGW, and determine described PDN link information.
Described second determination module 43, also for when receive from all PDN for described connected state UE of described target side SGW connect carry the session establishment response message of Reason For Denial time, determine that all PDN of described connected state UE connect and all excluded by described target side SGW;
Reselect target side SGW, and initiate PDN connection establishment process to the target side SGW reselected.
Described second determination module 43, specifically for having PDN connection to be excluded by described target side SGW when knowing during multiple PDN of described connected state UE connect; Other all PDN outside described PDN connects connect by described target side SGW receiving and when being excluded by base station, target side, send the Forward Relocation Response message of carrying Reject cause to source Mobility Management Entity.
Described second determination module 43, be further used for when receive from target side SGW carry the session establishment response message of Reason For Denial time, determine that corresponding PDN connects and excluded by described target side SGW;
When receiving the session establishment response message accepted from the expression request of target side SGW, and receive from base station, target side carry the switch failure information of Reason For Denial time, determine that corresponding PDN connects and to be received by described target side SGW and to be excluded by base station, target side.
Described second determination module 43, connect specifically for there being many PDN as described Idle state UE, and when there is the PDN connection be successfully established in many PDN connections, excluded by described target side SGW if there is PDN to connect, then determine this PDN link information excluded by described target side SGW.
Described sending module 44, specifically for connecting described PDN link information and PDN because SGW refusal in target side causes the information that cannot set up to send to described source Mobility Management Entity.
Described sending module 44, specifically for passing through the current Forward Relocation Response message of expansion, and by the Forward Relocation Response message after expansion, described PDN link information is sent to described source Mobility Management Entity.
Wherein, the modules of apparatus of the present invention can be integrated in one, and also can be separated deployment.Above-mentioned module can merge into a module, also can split into multiple submodule further.
Visible, in the embodiment of the present invention, the mark connected by the PDN that cannot delete sends to source SGSN/MME, delete corresponding PDN by source SGSN/MME according to the mark that this PDN connects to connect, thus solve the problem cannot deleted in the handoff procedure of inter MME/SGSN inter SGW and be connected by the PDN that SGW refuses.
Based on the inventive concept same with said method, additionally provide the management equipment that a kind of PDN connects in the embodiment of the present invention, as shown in Figure 5, comprising:
Receiver module 51, for when target side Mobility Management Entity determines PDN link information, receives the described PDN link information from described target side Mobility Management Entity;
Removing module 52, the PDN link information for receiving according to described receiver module 51 is deleted described PDN and is connected.
Described receiver module 51, connects because SGW refusal in target side causes the information that cannot set up from the described PDN link information of described target side Mobility Management Entity and PDN specifically for receiving.
Described receiver module 51, specifically for receiving from the Forward Relocation Response message after the expansion of described target side Mobility Management Entity, carries described PDN link information in the Forward Relocation Response after described expansion.
Described removing module 52, specifically for determining that according to described PDN link information the PDN needing to delete connects, and deletes described PDN by PDN Connection Release process and connects.
In the embodiment of the present invention, described PDN link information comprises the mark that described PDN connects.
Wherein, the modules of apparatus of the present invention can be integrated in one, and also can be separated deployment.Above-mentioned module can merge into a module, also can split into multiple submodule further.
Visible, in the embodiment of the present invention, the mark connected by the PDN that cannot delete sends to source SGSN/MME, delete corresponding PDN by source SGSN/MME according to the mark that this PDN connects to connect, thus solve the problem cannot deleted in the handoff procedure of inter MME/SGSN inter SGW and be connected by the PDN that SGW refuses.
Through the above description of the embodiments, those skilled in the art can be well understood to the mode that the present invention can add required general hardware platform by software and realize, and can certainly pass through hardware, but in a lot of situation, the former is better execution mode.Based on such understanding, technical scheme of the present invention can embody with the form of software product the part that prior art contributes in essence in other words, this computer software product is stored in a storage medium, comprising some instructions in order to make a computer equipment (can be personal computer, server, or the network equipment etc.) perform method described in each embodiment of the present invention.
It will be appreciated by those skilled in the art that accompanying drawing is the schematic diagram of a preferred embodiment, the module in accompanying drawing or flow process might not be that enforcement the present invention is necessary.
It will be appreciated by those skilled in the art that the module in the device in embodiment can carry out being distributed in the device of embodiment according to embodiment description, also can carry out respective change and be arranged in the one or more devices being different from the present embodiment.The module of above-described embodiment can merge into a module, also can split into multiple submodule further.
The invention described above embodiment sequence number, just to describing, does not represent the quality of embodiment.Be only several specific embodiment of the present invention above, but the present invention is not limited thereto, the changes that any person skilled in the art can think of all should fall into protection scope of the present invention.