CN102413562B - Management method and equipment of PDN (Packet Data Network) connection - Google Patents
Management method and equipment of PDN (Packet Data Network) connection Download PDFInfo
- Publication number
- CN102413562B CN102413562B CN201010288572.6A CN201010288572A CN102413562B CN 102413562 B CN102413562 B CN 102413562B CN 201010288572 A CN201010288572 A CN 201010288572A CN 102413562 B CN102413562 B CN 102413562B
- Authority
- CN
- China
- Prior art keywords
- pdn connection
- management entity
- mobility management
- new
- idle
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title abstract description 81
- 238000000034 method Methods 0.000 claims abstract description 68
- 230000008569 process Effects 0.000 claims abstract description 32
- 230000004044 response Effects 0.000 claims description 33
- 238000012217 deletion Methods 0.000 claims description 10
- 230000037430 deletion Effects 0.000 claims description 10
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000008859 change Effects 0.000 description 5
- 230000009849 deactivation Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a management method and equipment of PDN (Packet Data Network) connection. The management method comprises the following steps: a New mobile management entity receives a request message which is from idle-state UE (User Equipment) and carries information of an old mobile management entity, and determines that the idle-state UE moves from the old mobile management entity to the New mobile management entity according to the request message; the New mobile management entity determines PDN connection information of the idle-state UE; the New mobile management entity sends the PDN connection information to the old mobile management entity; and the old mobile management entity is indicted to delete the PDN connection according to the PDN connection information. In the invention, an identifier of the PDN connection which cannot be deleted to the old SGSN (Service GPRS (General Packet Radio Service) Supporting Node) entity/MME (Mobile Management Entity), and the corresponding PDN connection is deleted by the SGSN entity and the MME according to the identifier of the PDN connection, therefore the problem that the PDN connection which is refused by an SGW (Serving Gateway) cannot be deleted in the TAU/RAU (Tracking Area Update/Routing Area Update) process of the inter MME/SGSN inter SGW.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and a device for managing a PDN connection.
Background
In an existing LTE (Long Term Evolution) system, there is a TAU (Tracking Area Update)/RAU (Routing Area Update) process of an inter MME (Mobility Management Entity)/SGSN (Serving GPRS support Node) inter SGW (Serving Gateway).
As shown in fig. 1, a schematic diagram of a TAU with SGW change process includes the following steps:
1. UE (User Equipment) trigger to start tauuprocedure (procedure).
2. The UE sends a TAU Request to the eNodeB.
3. The eNodeB sends a TAU Request to the New MME.
4. The New MME sends a Context Request to the old MME/old SGSN.
In this step, the old MME/old SGSN may start a timer to delete the Context of the PDN connection on the old SGW.
5. The old MME/old SGSN sends a Context Response to the New MME.
6. The New MME performs Authentication/Security for the UE through an HSS (Home Subscriber Server).
7. The New MME sends a Context ACKnowledge to the old MME/old SGSN.
8. The New MME sends a Create Session Request to the New SGW.
9. The New SGW sends a Modify Bearer Request to a PDN (Packet Data Network) GW.
10. And the PDN GW sends a Modify Bearer Response to the New SGW.
11. The New SGW sends Create Session Response to the New MME.
12. The New MME sends Update Location (Location Update) to HSS.
13. HSS sends Cancel Location to old ME/old SGSN.
14. The old MME/old SGSN sends a Cancel Location Ack (acknowledgement) to the HSS.
15. The old MME/old SGSN sends an Iu Release Command to an RNC (Radio Network Controller).
16. RNC sends Iu Release Complete to old MME/old SGSN.
17. HSS sends Update Location Ack to New MME.
18. And the old MME/old SGSN sends a Delete Session Request to the old SGW.
19. And the old SGW sends a Delete Session Response to the old MME/old SGSN.
20. The New MME sends TAU Accept to the UE.
21. The UE sends TAU Complete to the New MME.
In the flow shown in fig. 1, for a processing procedure of one PDN Connection, if the UE supports multiple PDN connections, fig. 1 only describes the processing procedure of one PDN Connection.
In the prior art, when a New MME sends a Create Session Request message to a New SGW, if the SGW cannot establish a default Bearer context of the PDN connection due to a resource or the like, the SGW needs to carry a cause in a Create Session Response to reject the Create Session Request.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
in the TAU/RAU process of inter MME/SGSN inter SGW in the existing LTE system, if the SGW rejects the Create Session Request message sent by the New MME/SGSN, then the Bearer Context of the PDN connection is not created on the SGW, at this time, if the New MME/SGSN initiates a PDN connection deactivation (release) process, a Delete Session Request is sent to the SGW, the SGW returns a Context found in the Delete Session Response message to the New MME/SGSN, and the Delete Session Request message is not sent to Pgw (PDN). And the Delete Session request message sent by the old MME/SGSN only reaches the old SGW, and only the Bearer Context of the PDN connection on the old SGW is deleted. Therefore, BearerContext on the PGW for this PDN connection will not be deleted.
Disclosure of Invention
The embodiment of the invention provides a management method and equipment of PDN connection, which are used for deleting the PDN connection in a TAU/RAU process.
In order to achieve the above object, an embodiment of the present invention provides a method for managing a PDN connection, where the method includes:
a New mobile management entity receives a request message carrying old mobile management entity information from idle UE, and determines that the idle UE moves from the old mobile management entity to the New mobile management entity according to the request message;
the New mobility management entity determines PDN connection information of the idle UE;
the New mobility management entity sends the PDN connection information to the old mobility management entity; and instructing the old mobility management entity to delete the PDN connection according to the PDN connection information.
An embodiment of the present invention provides a management device for PDN connection, including:
a receiving module, configured to receive a request message carrying old mobility management entity information from an idle UE;
a first determining module, configured to determine, according to the request message received by the receiving module, that the idle-state UE moves from the old mobility management entity to a New mobility management entity;
a second determining module, configured to determine PDN connection information of the idle UE;
a sending module, configured to send the PDN connection information determined by the second determining module to the old mobility management entity; and instructing the old mobility management entity to delete the PDN connection according to the PDN connection information.
The embodiment of the invention provides a management method of PDN connection, which comprises the following steps:
the old mobility management entity receives PDN connection information from a New mobility management entity;
and the old mobility management entity deletes the PDN connection according to the PDN connection information.
An embodiment of the present invention provides a management device for PDN connection, including:
a receiving module, configured to receive PDN connection information from a New mobility management entity;
and the deleting module is used for deleting the PDN connection according to the PDN connection information received by the receiving module.
Compared with the prior art, the embodiment of the invention at least has the following advantages:
in the TAU/RAU process of the inter MME/SGSN inter SGW, the identifier of the PDN connection which cannot be deleted is sent to the old SGSN entity/MME entity, and the old SGSN entity/MME entity deletes the corresponding PDN connection according to the identifier of the PDN connection, so that the problem that the PDN connection rejected by the SGW cannot be deleted in the TAU/RAU process of the inter MME/SGSN inter SGW is solved.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
FIG. 1 is a schematic diagram of a TAU with SGW change process in the prior art;
fig. 2 is a flowchart illustrating a method for managing a PDN connection according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a management method for PDN connection in a TAU with SGW change scenario according to a second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a management device for PDN connection according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another management device for PDN connection according to an embodiment of the present invention.
Detailed Description
In the existing 3GPP LTE system, one UE may support multiple PDN connections, and in the TAU/RAU process of an inter MME/SGSN inter SGW, a situation may occur where the New SGW rejects a PDN Connection establishment request due to a resource or the like, if the UE has only one PDN Connection at this time, the MME/SGSN may reselect the SGW and restart the PDN Connection establishment process; however, if there are multiple PDN connections for the UE and some PDN connections have been successfully established, the MME/SGSN may not reselect the SGW and may need to delete the PDN Connection.
In the prior art, an MME/SGSN may initiate a PDN Connection Deactivation procedure to Delete a Bearer Context of the PDN Connection on an SGW or a PGW, and since the SGW does not have the Bearer Context of the PDN Connection, the SGW returns a Context not error, and the SGW does not transmit a Delete Session Request message to the PGW, that is, the MME/SGSN cannot Delete the Bearer Context of the PDN Connection on the SGW or the PGW through the PDN Connection Deactivation procedure.
In view of the above problems, embodiments of the present invention provide a method and an apparatus for managing PDN connections, where an identifier of a PDN connection that cannot be deleted is sent to an old SGSN entity/MME entity, and the old SGSN entity/MME entity deletes a corresponding PDN connection according to the identifier of the PDN connection, so as to solve a problem that a PDN connection rejected by an SGW cannot be deleted in a TAU/RAU process of an inter MME/SGSN inter SGW.
The technical solutions in the present invention will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides a management method of PDN connection, which is applied to the TAU/RAU process of an inter MME/SGSN inter SGW, and under the application scene that idle UE moves from an old mobility management entity to a New mobility management entity (namely the idle UE moves from the old mobility management entity to the New mobility management entity through the TAU or RAU process).
Specifically, when the idle UE finds that the current TA is not in its own TA list, the idle UE needs to send a TAU request message to the New mobility management entity (i.e., the mobility management entity corresponding to the current TA), where the TAU request message carries identification information of an old mobility management entity (i.e., the mobility management entity corresponding to the previous TA).
When the idle UE finds that the current RA is not in its RA list, the idle UE needs to send an RAU request message to a New mobility management entity (i.e., a mobility management entity corresponding to the current RA), where the RAU request message carries identification information of an old mobility management entity (i.e., a mobility management entity corresponding to the previous RA).
Further, after the New mobility management entity receives the TAU request message or the RAU request message from the idle UE, because the TAU request message or the RAU request message carries the information (identification information) of the old mobility management entity, the New mobility management entity can determine that the idle UE moves from the old mobility management entity to the New mobility management entity according to the TAU request message or the RAU request message.
Based on the application scenario, as shown in fig. 2, the method includes the following steps:
step 201, when the PDN connection cannot be successfully established, the New mobility management entity determines PDN connection information of the idle UE.
In the embodiment of the invention, if the idle-state UE has a plurality of PDN connections and the PDN connections successfully established exist in the PDN connections (the PDN connection is admitted by the New SGW), if the PDN connection cannot be successfully established (the PDN connection is refused to be admitted by the New SGW), the New mobility management entity needs to determine the information of the PDN connection which cannot be successfully established.
In this embodiment of the present invention, the information of the PDN connection includes, but is not limited to: an identity of the PDN connection.
In addition, in the UMTS (Universal Mobile Telecommunications System), the mobility management entity includes, but is not limited to, an SGSN.
In an EPS (Evolved Packet System) System, the mobility management entity includes, but is not limited to, an MME.
For convenience of description, in the embodiment of the present invention, the mobility management entity is illustrated by taking an MME/SGSN as an example, that is, the New mobility management entity may be a New MME/SGSN.
In this step, the process of determining the PDN connection identifier by the New MME/SGSN specifically includes: and when the New MME/SGSN receives a session establishment response message carrying the rejection reason from the New SGW, the New MME/SGSN determines the identification of the PDN connection.
Specifically, when the New MME/SGSN receives a Create Session Response message returned by the New SGW and the Create Session Response message carries a Reject Cause, the New MME/SGSN needs to record the PDN connection and determine an identifier of the PDN connection.
Further, the process of the New SGW returning the Create Session Response message carrying the Reject Cause to the New MME/SGSN specifically is as follows: and when the New SGW determines that the default bearer context of the PDN connection cannot be established, sending a Session establishment Response message (Create Session Response message) carrying a rejection reason (RejectCause) to the New MME/SGSN.
Step 202, the New MME/SGSN sends the identifier of the PDN connection to the old mobility management entity.
In the embodiment of the present invention, in the UMTS system, the mobility management entity includes, but is not limited to, an SGSN. In the EPS system, the mobility management entity includes, but is not limited to, an MME. For convenience of description, the old mobility management entity is illustrated by using old MME/SGSN as an example.
In this step, the process of sending the identifier of the PDN connection to the old MME/SGSN by the New MME/SGSN specifically includes: the New MME/SGSN informs the Old MME/SGSN of the identification (e.g. Default Bearer ID) of the PDN connection rejected by the SGW and informs the Old MME/SGSN that the PDN connection cannot be established due to the SGW rejection.
It should be noted that, since there is no message interaction between the Old MME/SGSN and the New MME/SGSN in the existing protocol, in the embodiment of the present invention, a message needs to be redefined to transmit the identifier of the PDN connection. The message can be arbitrarily selected according to actual conditions. For example, the message may be a Delete PDN Connection Notification message (Delete PDN Connection Notification message), such as one of the Delete PDN Connection Notification messages shown in table 1.
TABLE 1
Therefore, through the Delete PDN Connection Notification message, the New MME/SGSN may send the identifier of the PDN Connection to the old MME/SGSN, that is, the Delete PDN Connection Notification message may carry information of the PDN Connection.
And step 203, the old MME/SGSN deletes the corresponding PDN connection according to the identifier of the PDN connection.
Specifically, after the Old MME/SGSN receives the identifier of the PDN Connection that cannot be established due to SGW rejection sent by the New MME/SGSN, the PDN Connection to be deleted may be determined according to the identifier of the PDN Connection, and the PDN Connection may be deleted by initiating a PDN Connection release procedure (PDN Connection Deactivation procedure), which is not described in detail in the embodiments of the present invention.
In the embodiment of the present invention, after the old MME/SGSN deletes the corresponding PDN Connection, the new MME/SGSN may know that the PDN Connection rejected by the SGW is the deleted PDN Connection.
Further, for all PDN connections of the idle-state UE, if the New MME/SGSN receives a session establishment response message carrying a rejection reason from the New SGW for all PDN connections of the idle-state UE, the New MME/SGSN determines that all PDN connections of the idle-state UE are rejected and admitted by the New SGW; at this time, the New MME/SGSN may reselect the New SGW and initiate a PDN connection establishment procedure to the reselected New SGW.
Certainly, in practical application, the New MME/SGSN may also send the identifier of each PDN connection to the old MME/SGSN, and the old MME/SGSN deletes each PDN connection according to the identifier of the PDN connection.
In the embodiment of the invention, in the TAU/RAU process of the inter MME/SGSN inter SGW, the identifier of the PDN connection which cannot be deleted is sent to the old SGSN entity/MME entity, and the old SGSN entity/MME entity deletes the corresponding PDN connection according to the identifier of the PDN connection, so that the problem that the PDN connection rejected by the SGW cannot be deleted in the TAU/RAU process of the inter MME/SGSN inter SGW is solved.
In order to more clearly illustrate the technical solutions provided by the embodiments of the present invention, the following discusses the management method of the PDN connection in detail with reference to specific embodiments.
A second embodiment of the present invention provides a method for managing PDN connection, where the method takes a process of TAU with Serving GW change as an example, and a process of RAU with Serving GW change is similar to that of TAU, and is not described in detail in this embodiment of the present invention. As shown in fig. 3, the method comprises the steps of:
1. UE trigger to start TAU procedure.
2. The UE sends a TAU Request to the eNodeB.
3. The eNodeB sends a TAU Request to the New MME.
4. The New MME sends a Context Request to the old MME/old SGSN.
5. And the old MME/old SGSN sends Context Response to the New MME.
6. The New MME performs Authentication/Security on the UE through the HS S.
7. The New MME sends Context ACKnowledge to old MME/old SGSN.
8. The New MME sends a Create Session Request to the New SGW.
9. And the New SGW sends a Modify Bearer Request to the PDN GW.
10. And the PDN GW sends a Modify Bearer Response to the New SGW.
11. The New SGW sends Create Session Response to the New MME.
In this step, when the New SGW cannot establish a default bearer context of the PDN connection, a reject cause needs to be carried in a Create Session Response message; and after the New MME receives the Create Session Response message carrying the reject cause, it considers that the PDN connection needs to be released, and needs to record the PDN connection, and determines the identifier of the PDN connection.
12. The New MME sends Update Location to HSS.
13. HSS sends Cancel Location to old MME/old SGSN.
14. And the old MME/old SGSN sends a Cancel Location Ack to the HSS.
15. And the old MME/old SGSN sends an Iu Release Command to the RNC.
16. RNC sends Iu Release Complete to old MME/old SGSN.
17. HSS sends Update Location Ack to New MME.
18. And the old MME/old SGSN sends a Delete Session Request to the old SGW.
19. And the old SGW sends a Delete Session Response to the old MME/old SGSN.
20. The New MME sends TAUAccept to the UE.
21. The UE sends TAU Complete to the NewMME.
22. And the New MME sends a Delete PDN Connection Notification message to the old MME/SGSN.
The Delete PDN Connection Notification message carries an identifier of the PDN Connection (e.g., a Default Bearer ID of the PDN Connection, that is, the identifier of the PDN Connection recorded in step 11).
Further, after receiving the Delete PDN connectivity Notification message carrying the Default Bearer ID, the old MME/SGSN initiates a PDN connectivity Deactivation procedure to Delete the relevant PDN connectivity.
In the embodiment of the invention, in the TAU/RAU process of the inter MME/SGSN inter SGW, the identifier of the PDN connection which cannot be deleted is sent to the old SGSN entity ME entity, and the old SGSN entity/MME entity deletes the corresponding PDN connection according to the identifier of the PDN connection, so that the problem that the PDN connection rejected by the SGW cannot be deleted in the TAU/RAU process of the inter MME/SGSN inter SGW is solved.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a management device for PDN connection, as shown in fig. 4, including:
a receiving module 41, configured to receive a request message carrying old mobility management entity information from an idle UE;
a first determining module 42, configured to determine, according to the request message received by the receiving module 41, that the idle-state UE moves from the old mobility management entity to a New mobility management entity;
a second determining module 43, configured to determine PDN connection information of the idle UE;
a sending module 44, configured to send the PDN connection information determined by the second determining module 43 to the old mobility management entity; and instructing the old mobility management entity to delete the PDN connection according to the PDN connection information.
The receiving module 41 is specifically configured to receive a TAU request message from the idle UE when the idle UE finds that the current TA is not a TA list of the idle UE, where the TAU request message carries the identification information of the old mobility management entity; or,
and when the idle-state UE finds that the current RA is not in the RA list of the idle-state UE, receiving an RAU request message from the idle-state UE, wherein the RAU request message carries the identification information of the old mobility management entity.
The second determining module 43 is specifically configured to, when receiving a session establishment response message carrying a rejection reason from the New SGW, determine that the PDN connection corresponding to the session establishment response message is rejected by the New SGW for admission, and determine the PDN connection information.
The second determining module 43 is further configured to determine, when receiving a session establishment response message carrying a reject reason from the New SGW for all PDN connections of the idle-state UE, that all PDN connections of the idle-state UE are rejected for admission by the New SGW;
and reselecting the New SGW, and initiating a PDN connection establishment process to the reselected New SGW.
The second determining module 43 is specifically configured to, when the idle-state UE has multiple PDN connections and there is a PDN connection successfully established among the multiple PDN connections, determine, if there is a PDN connection that is rejected by the New SGW for admission, PDN connection information that is rejected by the New SGW for admission.
The sending module 44 is specifically configured to send the PDN connection information and information that the PDN connection cannot be established due to a NewSGW reject to the old mobility management entity.
The sending module 42 is specifically configured to send a PDN connection deletion notification message to the old mobility management entity, where the PDN connection deletion notification message carries the PDN connection information.
In this embodiment of the present invention, the PDN connection information includes an identifier of the PDN connection.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
In the embodiment of the present invention, the identifier of the PDN connection that cannot be deleted is sent to the old SGSN entity/MME entity, and the old SGSN entity/MME entity deletes the corresponding PDN connection according to the identifier of the PDN connection, so as to solve the problem that the PDN connection rejected by the SGW cannot be deleted in the TAU/RAU process of the inter MME/SGSN inter SGW.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a management device for PDN connection, as shown in fig. 5, including:
a receiving module 51, configured to receive PDN connection information from a New mobility management entity;
a deleting module 52, configured to delete the PDN connection according to the PDN connection information received by the receiving module 51.
The receiving module 51 is specifically configured to receive the PDN connection information from the New mobility management entity and information that a PDN connection cannot be established due to a New SGW reject.
The receiving module 51 is specifically configured to receive a PDN connection deletion notification message from the New mobility management entity, where the PDN connection deletion notification message carries the PDN connection information.
The deleting module 52 is specifically configured to determine, according to the PDN connection information, a PDN connection that needs to be deleted, and delete the PDN connection through a PDN connection release process.
In this embodiment of the present invention, the PDN connection information includes an identifier of the PDN connection.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
Therefore, in the embodiment of the present invention, the identifier of the PDN connection that cannot be deleted is sent to old
And the SGSN entity/MME entity deletes the corresponding PDN connection according to the identification of the PDN connection by the old SGSN entity/MME entity, thereby solving the problem that the PDN connection rejected by the SGW cannot be deleted in the TAU/RAU process of the inter MME/SGSN inter SGW.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.
Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (20)
1. A method for managing a PDN connection, the method comprising:
a New mobile management entity receives a request message carrying old mobile management entity information from idle UE, and determines that the idle UE moves from the old mobile management entity to the New mobile management entity according to the request message;
the New mobility management entity determines PDN connection information of the idle UE;
the New mobility management entity sends the PDN connection information to the old mobility management entity; instructing the old mobility management entity to delete the PDN connection according to the PDN connection information;
wherein the determining, by the New mobility management entity, PDN connection information of the idle UE includes:
when receiving a session establishment response message carrying a rejection reason from a New SGW, the New mobility management entity determines that the PDN connection of the idle UE corresponding to the session establishment response message is rejected by the New SGW for admission, and determines the PDN connection information;
when the idle-state UE has a plurality of PDN connections and the PDN connections successfully established exist in the PDN connections, if the PDN connections are refused to be admitted by the New SGW, the New mobility management entity determines the PDN connection information refused to be admitted by the New SGW.
2. The method of claim 1, wherein the New mobility management entity receives a request message carrying old mobility management entity information from an idle UE, and the method comprises:
when the idle-state UE finds that the current TA is not in the TA list of the idle-state UE, the New mobility management entity receives a TAU request message from the idle-state UE, wherein the TAU request message carries identification information of the old mobility management entity; or,
when the idle-state UE finds that the current RA is not in the RA list of the idle-state UE, the New mobility management entity receives an RAU request message from the idle-state UE, wherein the RAU request message carries the identification information of the old mobility management entity.
3. The method of claim 1, wherein receiving a session establishment response message carrying a reject reason from the New SGW further comprises:
when receiving a session establishment response message carrying a rejection reason from the New SGW for all PDN connections of the idle-state UE, the New mobility management entity determines that all PDN connections of the idle-state UE are rejected to be admitted by the New SGW;
and the New mobility management entity reselects the New SGW and initiates a PDN connection establishment process to the reselected New SGW.
4. The method of claim 1, wherein the New mobility management entity sending the PDN connectivity information to the old mobility management entity comprises:
and the New mobility management entity sends the PDN connection information and information that PDN connection cannot be established due to New SGW rejection to the old mobility management entity.
5. The method of claim 1, wherein the New mobility management entity sending the PDN connectivity information to the old mobility management entity comprises:
and the New mobile management entity sends a PDN connection deleting notification message to the old mobile management entity, wherein the PDN connection deleting notification message carries the PDN connection information.
6. The method of any one of claims 1-5, wherein the PDN connection information comprises an identification of the PDN connection.
7. The method of any one of claims 1 to 5,
in a UMTS system, the New mobility management entity comprises a New SGSN entity, and the old mobility management entity comprises an old SGSN entity;
in the EPS system, the New mobility management entity includes a New MME entity, and the old mobility management entity includes an old MME entity.
8. A management device for PDN connections, comprising:
a receiving module, configured to receive a request message carrying old mobility management entity information from an idle UE;
a first determining module, configured to determine, according to the request message received by the receiving module, that the idle-state UE moves from the old mobility management entity to a New mobility management entity;
a second determining module, configured to determine PDN connection information of the idle UE;
a sending module, configured to send the PDN connection information determined by the second determining module to the old mobility management entity; instructing the old mobility management entity to delete the PDN connection according to the PDN connection information;
the second determining module is specifically configured to, when receiving a session establishment response message from the New SGW and carrying a rejection reason, determine that the PDN connection of the idle-state UE corresponding to the session establishment response message is rejected by the New SGW for admission, and determine the PDN connection information;
the second determining module is specifically configured to determine PDN connection information that is rejected by the New SGW if there is a PDN connection rejected by the New SGW when the idle-state UE has multiple PDN connections and there is a PDN connection successfully established among the multiple PDN connections.
9. The apparatus of claim 8,
the receiving module is specifically configured to receive a TAU request message from the idle-state UE when the idle-state UE finds that the current TA is not a TA list of the idle-state UE, where the TAU request message carries identification information of the old mobility management entity; or,
and when the idle-state UE finds that the current RA is not in the RA list of the idle-state UE, receiving an RAU request message from the idle-state UE, wherein the RAU request message carries the identification information of the old mobility management entity.
10. The apparatus of claim 8,
the second determining module is further configured to determine that all PDN connections of the idle-state UE are rejected for admission by the New SGW when receiving a session establishment response message carrying a reject reason from the New SGW for all PDN connections of the idle-state UE;
and reselecting the New SGW, and initiating a PDN connection establishment process to the reselected New SGW.
11. The apparatus of claim 8,
the sending module is specifically configured to send the PDN connection information and information that the PDN connection cannot be established due to a NewSGW reject to the old mobility management entity.
12. The apparatus of claim 8,
the sending module is specifically configured to send a PDN connection deletion notification message to the old mobility management entity, where the PDN connection deletion notification message carries the PDN connection information.
13. A method for managing a PDN connection, the method comprising:
the old mobility management entity receives PDN connection information from a New mobility management entity;
the old mobility management entity deletes the PDN connection according to the PDN connection information;
the PDN connection information of the New mobility management entity specifically includes:
when receiving a session establishment response message carrying a rejection reason from a New SGW, the New mobility management entity determines that the PDN connection of idle UE corresponding to the session establishment response message is rejected by the New SGW for admission, and determines the PDN connection information;
when the idle-state UE has a plurality of PDN connections and the PDN connections successfully established exist in the PDN connections, if the PDN connections are refused to be admitted by the New SGW, the New mobility management entity determines the PDN connection information refused to be admitted by the New SGW.
14. The method of claim 13, wherein the old mobility management entity receives PDN connection information from a New mobility management entity, comprising:
and the old mobility management entity receives the PDN connection information from the New mobility management entity and information that PDN connection cannot be established due to New SGW rejection.
15. The method of claim 13, wherein the old mobility management entity receives PDN connection information from a New mobility management entity, comprising:
and the old mobility management entity receives a PDN connection deletion notification message from the New mobility management entity, wherein the PDN connection deletion notification message carries the PDN connection information.
16. The method of claim 13, wherein the old mobility management entity deleting the PDN connection according to the PDN connection information, comprising:
and the old mobility management entity determines the PDN connection to be deleted according to the PDN connection information, and deletes the PDN connection through a PDN connection release process.
17. A management device for PDN connections, comprising:
a receiving module, configured to receive PDN connection information from a New mobility management entity;
a deleting module, configured to delete the PDN connection according to the PDN connection information received by the receiving module;
the PDN connection information of the New mobility management entity specifically includes:
when receiving a session establishment response message carrying a rejection reason from a New SGW, the New mobility management entity determines that the PDN connection of idle UE corresponding to the session establishment response message is rejected by the New SGW for admission, and determines the PDN connection information;
when the idle-state UE has a plurality of PDN connections and the PDN connections successfully established exist in the PDN connections, if the PDN connections are refused to be admitted by the New SGW, the New mobility management entity determines the PDN connection information refused to be admitted by the New SGW.
18. The apparatus of claim 17,
the receiving module is specifically configured to receive the PDN connection information from the New mobility management entity and information that a PDN connection cannot be established due to a New SGW reject.
19. The apparatus of claim 17,
the receiving module is specifically configured to receive a PDN connection deletion notification message from the New mobility management entity, where the PDN connection deletion notification message carries the PDN connection information.
20. The apparatus of claim 17,
and the deleting module is specifically configured to determine the PDN connection that needs to be deleted according to the PDN connection information, and delete the PDN connection through a PDN connection release process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010288572.6A CN102413562B (en) | 2010-09-20 | 2010-09-20 | Management method and equipment of PDN (Packet Data Network) connection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010288572.6A CN102413562B (en) | 2010-09-20 | 2010-09-20 | Management method and equipment of PDN (Packet Data Network) connection |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102413562A CN102413562A (en) | 2012-04-11 |
| CN102413562B true CN102413562B (en) | 2015-01-14 |
Family
ID=45915327
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010288572.6A Active CN102413562B (en) | 2010-09-20 | 2010-09-20 | Management method and equipment of PDN (Packet Data Network) connection |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102413562B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103415050B (en) * | 2013-07-23 | 2017-10-31 | 大唐移动通信设备有限公司 | The processing method and processing device of cell pingpong reselection between TD SCDMA and TD LTE |
| KR101922577B1 (en) | 2013-12-31 | 2018-11-27 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Service processing method and device |
| US10477615B2 (en) * | 2015-01-16 | 2019-11-12 | Mediatek Inc. | Methods for handling a PDN disconnection request and communications apparatus utilizing the same |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101330751A (en) * | 2007-06-19 | 2008-12-24 | 华为技术有限公司 | Method for releasing source network resource, gateway entity and network appliance |
| CN101500322A (en) * | 2008-02-02 | 2009-08-05 | 中兴通讯股份有限公司 | Resource releasing method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8077685B2 (en) * | 2007-04-24 | 2011-12-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for avoiding hanging PDP contexts |
| CN101790151B (en) * | 2009-01-23 | 2012-08-29 | 电信科学技术研究院 | Deleting method and system of EPS load |
-
2010
- 2010-09-20 CN CN201010288572.6A patent/CN102413562B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101330751A (en) * | 2007-06-19 | 2008-12-24 | 华为技术有限公司 | Method for releasing source network resource, gateway entity and network appliance |
| CN101500322A (en) * | 2008-02-02 | 2009-08-05 | 中兴通讯股份有限公司 | Resource releasing method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102413562A (en) | 2012-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103621123B (en) | Flow shunt is carried out via local network | |
| EP2732660B1 (en) | Telecommunications handover when handover restriction list is missing | |
| US9491732B2 (en) | Paging processing method, user equipment and system | |
| JP2015195622A (en) | Method and apparatus for relocating and restoring connections through failed serving gateway and traffic offloading | |
| US10517121B2 (en) | Service processing method, related apparatus, and system | |
| WO2020063649A1 (en) | Network service control method and communication device | |
| TWI659667B (en) | Device and method of handling a connection in a wireless communication system | |
| WO2015174045A1 (en) | Method for mobile communication system, mobile communication system, mobile terminal, network node, and pgw | |
| KR20190099308A (en) | Communication methods, access network devices, and terminals | |
| US20160105790A1 (en) | Combined location updating processing method, apparatus, and system | |
| KR20220091555A (en) | Connection processing method and communication equipment | |
| CN108293228B (en) | Method for establishing voice call and user equipment | |
| WO2018059401A1 (en) | Network switching method, device and system, and network access method and device | |
| WO2014194672A1 (en) | Method and device for inter-system reselection or switching processing | |
| WO2016054822A1 (en) | Csfb call establishment method and device | |
| WO2019029228A1 (en) | Method and device for processing voice service, and storage medium | |
| EP3044992B1 (en) | Method and apparatus for setup of a circuit switched call during circuit switched fallback | |
| WO2018010583A1 (en) | Network system | |
| CN102413562B (en) | Management method and equipment of PDN (Packet Data Network) connection | |
| CN102325348B (en) | Method and equipment for constructing local Internet protocol access (LIPA) packet data network (PDN) connection | |
| WO2018130053A1 (en) | Flow conflict processing method and device | |
| WO2012146202A1 (en) | Method and system for establishing radio resource control connection | |
| CN105828399B (en) | Tracking area updating method and device | |
| WO2013152715A1 (en) | Subscription information transmission method and device for closed subscription group | |
| CN102413584B (en) | Method and equipment for managing PDN (public data network) connection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| CP01 | Change in the name or title of a patent holder | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210602 Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd. Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY |
|
| TR01 | Transfer of patent right |