US10165618B2 - Service processing method and device - Google Patents

Service processing method and device Download PDF

Info

Publication number
US10165618B2
US10165618B2 US15/199,206 US201615199206A US10165618B2 US 10165618 B2 US10165618 B2 US 10165618B2 US 201615199206 A US201615199206 A US 201615199206A US 10165618 B2 US10165618 B2 US 10165618B2
Authority
US
United States
Prior art keywords
pdn connection
deleting
pgw
request message
sgw
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, expires
Application number
US15/199,206
Other languages
English (en)
Other versions
US20160316515A1 (en
Inventor
Sirui Long
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of US20160316515A1 publication Critical patent/US20160316515A1/en
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LONG, Sirui
Application granted granted Critical
Publication of US10165618B2 publication Critical patent/US10165618B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H04L65/1006—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present disclosure relates to the field of wireless communications technologies, and in particular, to a service processing method and device.
  • EPS evolved packet system
  • 3GPP 3rd Generation Partnership Project
  • SGW Serving Gateway
  • PDN gateway Packet Data Network gateway
  • the SGW when a fault occurs in the PGW, it is defined in a 3GPP protocol that when sensing that a fault occurs in the PGW, the SGW sends, to an Mobility Management Entity (MME), a message for notifying the MME that a fault occurs in the PGW, so that the MME determines, after receiving the message, that a fault occurs in the PGW.
  • MME Mobility Management Entity
  • the MME When receiving the message that is sent by the SGW and used for notifying that a fault occurs in the PGW, the MME needs to traverse context information in an information exchange system, delete a PDN connection established with the faulty PGW, and determine user equipment that need to be notified to reestablish a Packet Date Network (PDN) connection with the faulty PGW and to re-initiate a communication service request.
  • PDN Packet Date Network
  • Embodiments of the present disclosure provide a service processing method and device, which are used to solve the problem of low system service processing efficiency resulting from a long signaling transmission link caused by the fact that at present, when a fault occurs in a PGW, PGW reset is triggered by an MME.
  • a service processing method including determining, by a serving gateway SGW, that an exception occurs in a packet data network gateway PGW; obtaining, by the SGW, a policy for deleting a packet data network PDN connection established between the SGW and the PGW; deleting, by the SGW according to the policy for deleting a PDN connection, a PDN connection between the SGW and the PGW; and sending, by the SGW, a deletion request message to a mobility management entity MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the deleting, by the SGW according to the policy for deleting a PDN connection, a packet data network PDN connection established between the SGW and the PGW includes determining, by the SGW according to types of services carried over PDN connections established between the SGW and the PGW, a priority sequence for deleting PDN connections carrying services of different types, and deleting a PDN connection that needs to be preferentially deleted.
  • the determining, by the SGW according to types of services carried over PDN connections established between the SGW and the PGW, a priority sequence for deleting PDN connections carrying services of different types, and deleting a PDN connection that needs to be preferentially deleted includes: preferentially deleting a PDN connection carrying a voice service.
  • the deleting, by the SGW according to the policy for deleting a PDN connection, a packet data network PDN connection established between the SGW and the PGW includes preferentially deleting, by the SGW, a PDN connection carrying a service request message sent by a user when receiving, in a process of deleting the PDN connection, the service request message.
  • the preferentially deleting, by the SGW, a PDN connection carrying a service request message sent by a user when receiving, in a process of deleting the PDN connection, the service request message includes determining, by the SGW, priorities of the multiple users, and preferentially deleting a PDN connection carrying a service request message sent by a user having a high priority when receiving, in the process of deleting the PDN connection, service request messages sent by multiple users.
  • the deleting, by the SGW according to the policy for deleting a PDN connection, a packet data network PDN connection established between the SGW and the PGW includes preferentially deleting, by the SGW, the PDN connection carrying uplink service data sent by the user when receiving, in the process of deleting the PDN connection, the uplink service data.
  • the preferentially deleting a PDN connection carrying the uplink service data include preferentially deleting, by the SGW, a PDN connection carrying the uplink service data including the SIP signaling when determining that the uplink service data includes Session Initiation Protocol (SIP) signaling.
  • SIP Session Initiation Protocol
  • the deleting, by the SGW according to the policy for deleting a PDN connection, a packet data network PDN connection established between the SGW and the PGW includes preferentially deleting, by the SGW, the PDN connection belonging to the APN that is an IMS APN when determining that an access point name APN to which a PDN connection belongs is an Internet Protocol multimedia subsystem (IMS) access point name (APN) (IMS APN).
  • IMS Internet Protocol multimedia subsystem
  • API Internet Protocol multimedia subsystem
  • the deleting a packet data network PDN connection established between the SGW and the PGW includes traversing, by the serving gateway SGW, context information of the PDN connection established between the SGW and the PGW; and deleting, by the SGW according to the traversed context information, the packet data network PDN connection established between the SGW and the PGW.
  • the deletion request message further includes a cause value, where the cause value is used for instructing the MME to notify a user, of the deleted PDN connection, to re-initiate PDN connection reestablishment.
  • the deletion request message further includes identity information of a PGW; and the sending a deletion request message to a MME includes sending, by the SGW to the MME, deletion request message about the PDN connection corresponding to the context information, where the deletion request message is used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME deletes the PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • a service processing method including receiving, by a MME, a deletion request message sent by a serving gateway SGW, where the deletion request message includes identity information of a to-be-deleted PDN connection; and deleting, by the MME according to the deletion request message, the PDN connection corresponding to the identity information.
  • the deletion request message further includes a cause value; and the method further includes notifying, by the MME according to the cause value included in the received deletion request message, a user to re-initiate PDN connection reestablishment for the deleted PDN connection.
  • the deletion request message further includes identity information of a PGW; and the method further includes deleting, by the MME according to the identity information of the PGW included in the received deletion request message, a PDN connection established with the PGW corresponding to the identity information, and selecting another PGW for a user equipment establishing the deleted PDN connection.
  • a service processing device including a determining module configured to determine that an exception occurs in a packet data network gateway PGW; an obtaining module configured to obtain a policy for deleting a packet data network PDN connection established with the PGW; a deleting module configured to delete, according to the policy for deleting a PDN connection obtained by the obtaining module, a PDN connection established with the PGW; and a sending module configured to send a deletion request message to a MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the deleting module is further configured to determine, according to types of services carried over PDN connections established with the PGW, a priority sequence for deleting PDN connections carrying services of different types, and delete a PDN connection that needs to be preferentially deleted.
  • the deleting module is further configured to preferentially delete a PDN connection carrying a voice service.
  • the deleting module is further configured to, when a service request message sent by a user is received in a process of deleting the PDN connection, preferentially delete a PDN connection carrying the service request message.
  • the deleting module is further configured to, when service request messages sent by multiple users are received in the process of deleting the PDN connection, determine priorities of the multiple users, and preferentially delete a PDN connection carrying a service request message sent by a user having a high priority.
  • the deleting module is further configured to, when uplink service data sent by a user is received in a process of deleting the PDN connection, preferentially delete a PDN connection carrying the uplink service data.
  • the deleting module is further configured to, when it is determined that the uplink service data includes Session Initiation Protocol SIP signaling, preferentially delete a PDN connection carrying the uplink service data including the SIP signaling.
  • the deleting module is further configured to: when it is determined that an access point name APN to which a PDN connection belongs is an IP multimedia subsystem access point name IMS APN, preferentially delete the PDN connection belonging to the APN that is an IMS APN.
  • the deleting module is further configured to traverse context information of the PDN connection established with the PGW, and delete, according to the traversed context information, the packet data network PDN connection established with the PGW.
  • the deletion request message further includes a cause value, where the cause value is used for instructing the MME to notify a user, of the deleted PDN connection, to re-initiate PDN connection reestablishment.
  • the deletion request message further includes identity information of a PGW; and the sending module is further configured to send, to the mobility management entity MME, deletion request message about the PDN connection corresponding to the context information, where the deletion request message is used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME deletes the PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • a service processing device including: a receiving module configured to receive a deletion request message sent by a serving gateway SGW, where the deletion request message includes identity information of a to-be-deleted PDN connection; and a deleting module configured to delete, according to the deletion request message received by the receiving module, the PDN connection corresponding to the identity information.
  • the deletion request message further includes a cause value
  • the device further includes: a notifying module configured to notify, according to the cause value included in the deletion request message received by the receiving module, a user to re-initiate PDN connection reestablishment for the deleted PDN connection.
  • the deletion request message further includes identity information of a PGW; and the device further includes: a reselecting module configured to delete, according to the identity information of the PGW included in the deletion request message received by the receiving module, a PDN connection established with the PGW corresponding to the identity information, and select another PGW for a user equipment establishing the deleted PDN connection.
  • a serving gateway SGW device including: a processor configured to determine that an exception occurs in a packet data network gateway PGW, obtain a policy for deleting a packet data network PDN connection established with the PGW, and delete a PDN connection established with the PGW according to the policy for deleting a PDN connection; and a signal transmitter configured to send a deletion request message to a mobility management entity MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the processor is further configured to determine, according to types of services carried over PDN connections established with the PGW, a priority sequence for deleting PDN connections carrying services of different types, and delete a PDN connection that needs to be preferentially deleted.
  • the processor is further configured to preferentially delete a PDN connection carrying a voice service.
  • the processor is further configured to: when receiving, in a process of deleting the PDN connection, a service request message sent by a user, preferentially delete a PDN connection carrying the service request message.
  • the processor is further configured to: when receiving, in the process of deleting the PDN connection, service request messages sent by multiple users, determine priorities of the multiple users, and preferentially delete a PDN connection carrying a service request message sent by a user having a high priority.
  • the processor is further configured to: when receiving, in a process of deleting the PDN connection, uplink service data sent by a user, preferentially delete a PDN connection carrying the uplink service data.
  • the processor is further configured to preferentially delete a PDN connection carrying the uplink service data including the SIP signaling when determining that the uplink service data includes Session Initiation Protocol (SIP) signaling.
  • SIP Session Initiation Protocol
  • the processor is further configured to, when determining that an APN to which a PDN connection belongs is an IMS APN, preferentially delete the PDN connection belonging to the APN that is an IMS APN.
  • the processor is further configured to traverse context information of the PDN connection established with the PGW, and delete, according to the traversed context information, the packet data network PDN connection established with the PGW.
  • the deletion request message further includes a cause value, where the cause value is used for instructing the MME to notify a user, of the deleted PDN connection, to re-initiate PDN connection reestablishment.
  • the deletion request message further includes identity information of a PGW; and the signal transmitter is further configured to send, to the MME, deletion request message about the PDN connection corresponding to the context information, where the deletion request message is used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME deletes the PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • a MME device including a signal receiver configured to receive a deletion request message sent by a SGW, where the deletion request message includes identity information of a to-be-deleted PDN connection; and a processor configured to delete, according to the deletion request message received by the receiver, the PDN connection corresponding to the identity information.
  • the deletion request message further includes a cause value
  • the processor is further configured to notify, according to the cause value included in the deletion request message received by the receiver, a user to re-initiate PDN connection reestablishment for the deleted PDN connection.
  • the deletion request message further includes identity information of a PGW
  • the processor is further configured to delete, according to the identity information of the PGW included in the deletion request message received by the receiver, a PDN connection established with the PGW corresponding to the identity information, and select another PGW for a user equipment establishing the deleted PDN connection.
  • a SGW determines that an exception occurs in a PGW, obtains a policy for deleting a PDN connection established between the SGW and the PGW, deletes a PDN connection between the SGW and the PGW according to the policy for deleting a PDN connection, and sends a deletion request message to a MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the SGW no longer needs to send information indicating that an exception occurs in the PGW to the MME, thereby reducing a quantity of transmitted signaling in a system, and simplifying a service processing procedure.
  • service processing is accelerated, service processing efficiency of the system is further increased, and user experience is improved.
  • FIG. 1 is a schematic flowchart of a service processing method according to Embodiment 1 of the present disclosure
  • FIG. 2 is a schematic flowchart of a service processing method according to Embodiment 2 of the present disclosure
  • FIG. 3 is a schematic flowchart of a service processing method according to Embodiment 3 of the present disclosure
  • FIG. 4 is a schematic flowchart of a service processing method according to Embodiment 4 of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a service processing device according to Embodiment 5 of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a service processing device according to Embodiment 6 of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a serving gateway (SGW) device according to Embodiment 7 of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a mobility management entity (MME) device according to Embodiment 8 of the present disclosure.
  • MME mobility management entity
  • a SGW determines that an exception occurs in a PGW, obtains a policy for deleting a packet data network PDN connection established between the SGW and the PGW, deletes a PDN connection between the SGW and the PGW according to the policy for deleting a PDN connection, and sends a deletion request message to a MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the SGW when determining that an exception occurs in the PGW, the SGW no longer needs to send information indicating that an exception occurs in the PGW to the MME, thereby reducing a quantity of transmitted signaling in a system, and simplifying a service processing procedure. Moreover, because different deletion policies are used, service processing is accelerated, service processing efficiency of the system is further increased, and user experience is improved.
  • FIG. 1 is a schematic flowchart of a service processing method according to Embodiment 1 of the present disclosure, the method may be described as follows:
  • Step 101 An SGW determines that an exception occurs in a packet data network gateway PGW.
  • a manner in which the SGW determines that an exception occurs in the PGW includes, but is not limited to:
  • a first manner The SGW determines whether a fault occurs in the PGW by using a path detection mechanism.
  • a second manner The SGW determines, according to a Recovery value carried in a negotiation message, that the PGW is restarted.
  • the PGW sends an Echo Response message to the SGW, so that the SGW learns, according to a Recovery value included in the Echo Response message, that the PGW is restarted.
  • the SGW determines, according to a Recovery value carried in a general packet radio service (GPRS) tunneling protocol (GTP) message, that the PGW is restarted.
  • GPRS general packet radio service
  • GTP tunneling protocol
  • the SGW determines, according to a configuration policy, whether to respond to an exception event that occurs in the PGW.
  • an SGW when determining that an exception occurs in a PGW, an SGW sends a deletion message to an MME to notify the MME that a fault occurs in the PGW, so that the MME deletes a PDN connection established with the PGW in which a fault already occurs and sends, according to locally stored identity information of a user equipment establishing a PDN connection with the PGW in which the fault already occurs, PDN connection reestablishment information to the user equipment corresponding to the identity information of the user equipment, or the MME reselects another PGW for the user equipment.
  • the SGW may send a deletion message to the MME according to the 3GPP protocol, which is obviously not a manner recommended in the present disclosure.
  • Step 102 The SGW obtains a policy for deleting a packet data network PDN connection established between the SGW and the PGW.
  • the policy, obtained by the SGW, for deleting a packet data network PDN connection established between the SGW and the PGW includes, but is not limited to:
  • Policy 1 For different service types, determine a priority sequence for deleting PDN connections carrying services of different types.
  • deletion of a PDN connection carrying a voice service precedes deletion of a PDN connection carrying a data service.
  • types of services carried over PDN connections include a voice service, a video service, a web browsing service, and a background E-mail downloading service
  • a priority sequence for deleting PDN connections carrying the services of the foregoing types may be first deleting a PDN connection carrying the voice service, then deleting a PDN connection carrying the video service, then deleting a PDN connection carrying the web browsing service, and finally deleting a PDN connection carrying the background E-mail downloading service.
  • Policy 2 Determine, according to a service request message or uplink service data that is sent by a user and received in a PDN connection deletion process, a priority sequence for deleting PDN connections.
  • a PDN connection carrying the service request message or carrying the uplink service data is preferentially deleted.
  • the PDN connection carrying the service request message is preferentially deleted, and the PDN connection carrying the uplink service data is preferentially deleted.
  • deletion of the PDN connection carrying the service request message and deletion of the PDN connection carrying the uplink service data may be executed according to a receiving sequence of the service request message and the uplink service data, which is not limited herein.
  • Policy 3 For identical service request messages or identical uplink service data, determine, according to priorities of users sending the service request messages or the uplink service data, a priority sequence for deleting PDN connections.
  • Policy 4 For received uplink service data, determine, according to whether the uplink service data includes SIP signaling, a priority sequence for deleting PDN connections.
  • deletion of a PDN connection carrying uplink service data including the SIP signaling precedes deletion of a PDN connection carrying uplink service data not including the SIP signaling.
  • Policy 5 Determine, according to an APN to which a PDN connection belongs, a priority sequence for deleting PDN connections.
  • deletion of the PDN connection belonging to the APN that is an IMS APN precedes that of a PDN connection belonging to an APN that is not an IMS APN.
  • Step 103 The SGW deletes a PDN connection between the SGW and the PGW according to the policy for deleting a PDN connection.
  • step 103 when determining that an exception occurs in the PGW, the SGW traverses context information of each PDN connection established between the SGW and the PGW, so as to determine an attribute of each PDN connection.
  • an attribute of a PDN connection may refer to a type of a service carried over the PDN connection, access point information, or the like.
  • the SGW deletes, according to the traversed context information, the attribute of the PDN connection, and the policy for deleting a PDN connection, the PDN connection established between the SGW and the PGW.
  • a PDN connection carrying a service of a high-priority type is preferentially deleted, and a PDN connection belonging to an APN that is an IMS APN is preferentially deleted.
  • a high priority of a service type refers to that different priorities are configured for types of services carried over PDN connections. For example, a priority of a voice service is higher than a priority of a video service, the priority of the video service is higher than a priority of a web browsing service, and the priority of the web browsing service is higher than a priority of background E-mail downloading.
  • the SGW may traverse at least twice context information of PDN connections established with the PGW.
  • the SGW still receives a service request message or uplink service data sent by a user; in this case, according to the policy for deleting a PDN connection, deletion of a current PDN connection needs to be stopped, a PDN connection carrying the received service request message or the received uplink service data is found, the found PDN connection is preferentially deleted, and after the processing is completed, the foregoing PDN connection deletion operation is continued.
  • the PDN connection deletion process for the received uplink service data sent by the user, first, it is determined whether the uplink data includes SIP signaling; then, when it is determined that the uplink service data includes the SIP signaling, a PDN connection carrying the uplink service data including the SIP signaling is preferentially deleted.
  • deletion of the PDN connection carrying the uplink service data including the SIP signaling precedes deletion of a PDN connection carrying uplink service data not including the SIP signaling.
  • Step 104 The SGW sends a deletion request message to a mobility management entity MME.
  • the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • step 104 when determining that an exception occurs in the PGW, the SGW deletes the PDN connection between the SGW and the faulty PGW; in this case, the deletion request message is sent to the MME, requiring the MME to delete, when receiving the deletion request message, the PDN connection corresponding to the identity information of the PDN connection included in the deletion request message.
  • the SGW when determining that an exception occurs in the PGW, the SGW performs an operation on the PDN connection established with the faulty PGW, thereby reducing signaling transmission between the SGW and the MME, and improving service processing efficiency of a system.
  • the deletion request message is sent to the MME, where the deletion request message further includes identity information of the PGW, and the deletion request message is further used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME determines the PGW in which the fault occurs, deletes a PDN connection currently established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the PDN connection.
  • deletion request message further includes information, such as an IP address of an S5/S8 control plane of the PGW or an IP address of an S4/S11 interface of the PGW, for identifying a PGW fault.
  • the SGW sends the deletion request message (it should be noted that the deletion request message is a delete bearer request message) to the MME, where the deletion request message further includes a cause value of a Reactivation Request, so that when receiving the deletion request message including the cause value of the Reactivation Request, the MME deletes a specified PDN connection, and notifies a user equipment establishing the PDN connection with the PGW to re-initiate PDN connection reestablishment.
  • the deletion request message is a delete bearer request message
  • the deletion request message further includes a cause value of a Reactivation Request
  • the MME determines whether the user equipment has another PDN connection besides the PDN connection established with the faulty PGW; if not, the MME deletes the PDN connection established between the user equipment and the faulty PGW, and sends PDN connection reestablishment information to the user equipment, so that the user equipment establishes a new PDN connection with the PGW when receiving the PDN connection reestablishment information; and if yes, the MME releases, according to the cause value of the Reactivation Request included in the deletion request message, a PDN connection that is established between the user equipment and the faulty PGW and pointed to by the cause value of the Reactivation Request, and sends PDN connection reestablishment information to the user equipment, so that the user equipment establishes a new PDN connection with the PGW when receiving PDN connection reestablishment information.
  • a SGW determines that an exception occurs in a PGW, obtains a policy for deleting a PDN connection established between the SGW and the PGW, deletes a PDN connection between the SGW and the PGW according to the policy for deleting a PDN connection, and sends a deletion request message to a MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the SGW when determining that an exception occurs in the PGW, the SGW no longer needs to send information indicating that an exception occurs in the PGW to the MME, thereby reducing a quantity of transmitted signaling in a system, and simplifying a service processing procedure. Moreover, because different deletion policies are used, service processing is accelerated, service processing efficiency of the system is further increased, and user experience is improved.
  • Embodiment 2 of the present disclosure is disclosures based on a same disclosure conception, and the method may be described as follows:
  • Step 201 An SGW determines that an exception occurs in a PGW.
  • a manner in which the SGW determines that an exception occurs in the PGW includes, but is not limited to:
  • a first manner The SGW determines whether a fault occurs in the PGW by using a path detection mechanism.
  • a second manner The SGW determines, according to a Recovery value carried in a negotiation message, that the PGW is restarted.
  • the PGW sends an Echo Response message to the SGW, so that the SGW learns, according to a Recovery value included in the Echo Response message, that the PGW is restarted.
  • the SGW determines, according to a Recovery value carried in a GTP message, that the PGW is restarted.
  • the SGW determines, according to a configuration policy, whether to respond to an exception event that occurs in the PGW.
  • an SGW when determining that an exception occurs in a PGW, an SGW sends a deletion message to an MME to notify the MME that a fault occurs in the PGW, so that the MME deletes a PDN connection established with the PGW in which a fault already occurs and sends, according to locally stored identity information of a user equipment establishing a PDN connection with the PGW in which the fault already occurs, PDN connection reestablishment information to the user equipment corresponding to the identity information of the user equipment, or the MME reselects another PGW for the user equipment.
  • the SGW may send a deletion message to the MME according to the 3GPP protocol, which is obviously not a manner recommended in the present disclosure.
  • the SGW when determining that an exception occurs in the PGW, the SGW performs a deletion operation on the PDN connection established with the faulty PGW, thereby reducing signaling transmission between the SGW and the MME, and improving service processing efficiency of a system.
  • Step 202 The SGW obtains a policy for deleting a packet data network PDN connection established between the SGW and the PGW.
  • the policy, obtained by the SGW, for deleting a packet data network PDN connection established between the SGW and the PGW includes, but is not limited to:
  • Policy 1 For different service types, determine a priority sequence for deleting PDN connections carrying services of different types.
  • deletion of a PDN connection carrying a voice service precedes deletion of a PDN connection carrying a data service.
  • types of services carried over PDN connections include a voice service, a video service, a web browsing service, and a background E-mail downloading service
  • a priority sequence for deleting PDN connections carrying the services of the foregoing types may be first deleting a PDN connection carrying the voice service, then deleting a PDN connection carrying the video service, then deleting a PDN connection carrying the web browsing service, and finally deleting a PDN connection carrying the background E-mail downloading service.
  • Policy 2 Determine, according to a service request message or uplink service data that is sent by a user and received in a PDN connection deletion process, a priority sequence for deleting PDN connections.
  • a PDN connection carrying the service request message or carrying the uplink service data is preferentially deleted.
  • the PDN connection carrying the service request message is preferentially deleted, and the PDN connection carrying the uplink service data is preferentially deleted.
  • deletion of the PDN connection carrying the service request message and deletion of the PDN connection carrying the uplink service data may be executed according to a receiving sequence of the service request message and the uplink service data, which is not limited herein.
  • Policy 3 For identical service request messages or identical uplink service data, determine, according to priorities of users sending the service request messages or the uplink service data, a priority sequence for deleting PDN connections.
  • Policy 4 For received uplink service data, determine, according to whether the uplink service data includes SIP signaling, a priority sequence for deleting PDN connections.
  • deletion of a PDN connection carrying uplink service data including the SIP signaling precedes deletion of a PDN connection carrying uplink service data not including the SIP signaling.
  • Policy 5 Determine, according to an APN to which a PDN connection belongs, a priority sequence for deleting PDN connections.
  • deletion of the PDN connection belonging to the APN that is an IMS APN precedes that of a PDN connection belonging to an APN that is not an IMS APN.
  • Step 203 The SGW traverses context information of a PDN connection established with the PGW.
  • step 203 the SGW traverses one piece of context information, and determines an attribute, corresponding to the traversed context information, of the PDN connection.
  • an attribute of a PDN connection may refer to a type of a service carried over the PDN connection, access point information, or the like.
  • Step 204 The SGW deletes, according to the traversed context information, the attribute of the PDN connection, and the policy for deleting a PDN connection, the PDN connection established between the SGW and the PGW, and turns to perform step 208 .
  • step 204 during PDN connection deletion, a PDN connection carrying a service of a high-priority type is preferentially deleted, and a PDN connection belonging to an APN that is an IMS APN is preferentially deleted.
  • a high priority of a service type refers to that different priorities are configured for types of services carried over PDN connections. For example, a priority of a voice service is higher than a priority of a video service, the priority of the video service is higher than a priority of a web browsing service, and the priority of the web browsing service is higher than a priority of background E-mail downloading.
  • the SGW may traverse at least twice context information of PDN connections established with the PGW.
  • Step 205 In a PDN connection deletion process, the SGW receives a service request message sent by a user.
  • Step 206 The SGW determines whether a PDN connection carrying the service request message exists among PDN connections being deleted, if yes, performs step 207 , and otherwise, performs step 204 and at the same time responds to the service request message sent by the user.
  • Step 207 When determining that the PDN connection carrying the service request message exists, preferentially delete the PDN connection carrying the service request message, and turn to perform step 208 .
  • Step 208 The SGW sends a deletion request message to a mobility management entity MME.
  • the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • step 208 when determining that an exception occurs in the PGW, the SGW deletes the PDN connection between the SGW and the faulty PGW; in this case, the deletion request message is sent to the MME, requiring the MME to delete, when receiving the deletion request message, the PDN connection corresponding to the identity information of the PDN connection included in the deletion request message.
  • the SGW when determining that an exception occurs in the PGW, the SGW performs an operation on the PDN connection established with the faulty PGW, thereby reducing signaling transmission between the SGW and the MME, and improving service processing efficiency of a system.
  • the deletion request message is sent to the MME, where the deletion request message further includes identity information of the PGW, and the deletion request message is further used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME determines the PGW in which the fault occurs, deletes a PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • deletion request message further includes information, such as an IP address of an S5/S8 control plane of the PGW or an IP address of an S4/S11 interface of the PGW, for identifying a PGW fault.
  • the SGW sends the deletion request message (it should be noted that the deletion request message is a delete bearer request message) to the MME, where the deletion request message further includes a cause value of a Reactivation Request, so that when receiving the deletion request message including the cause value of the Reactivation Request, the MME deletes a specified PDN connection, and notifies a user equipment establishing the PDN connection with the PGW to re-initiate PDN connection reestablishment.
  • the deletion request message is a delete bearer request message
  • the deletion request message further includes a cause value of a Reactivation Request
  • the MME determines whether the user equipment has another PDN connection besides the PDN connection established with the faulty PGW; if not, the MME deletes the PDN connection established between the user equipment and the faulty PGW, and sends PDN connection reestablishment information to the user equipment, so that the user equipment establishes a new PDN connection with the PGW when receiving the PDN connection reestablishment information; and if yes, the MME releases, according to the cause value of the Reactivation Request included in the deletion request message, a PDN connection that is established between the user equipment and the faulty PGW and pointed to by the cause value of the Reactivation Request, and sends PDN connection reestablishment information to the user equipment, so that the user equipment establishes a new PDN connection with the PGW when receiving PDN connection reestablishment information.
  • Embodiment 3 of the present disclosure is disclosures based on a same disclosure conception, and the method may be described as follows:
  • Step 301 An SGW determines that an exception occurs in a PGW.
  • a manner in which the SGW determines that an exception occurs in the PGW includes, but is not limited to:
  • a first manner The SGW determines whether a fault occurs in the PGW by using a path detection mechanism.
  • a second manner The SGW determines, according to a Recovery value carried in a negotiation message, that the PGW is restarted.
  • the PGW sends an Echo Response message to the SGW, so that the SGW learns, according to a Recovery value included in the Echo Response message, that the PGW is restarted.
  • the SGW determines, according to a Recovery value carried in a GTP message, that the PGW is restarted.
  • the SGW determines, according to a configuration policy, whether to respond to an exception event that occurs in the PGW.
  • an SGW when determining that an exception occurs in a PGW, an SGW sends a deletion message to an MME to notify the MME that a fault occurs in the PGW, so that the MME deletes a PDN connection established with the PGW in which a fault already occurs and sends, according to locally stored identity information of a user equipment establishing a PDN connection with the PGW in which the fault already occurs, PDN connection reestablishment information to the user equipment corresponding to the identity information of the user equipment, or the MME reselects another PGW for the user equipment.
  • the SGW may send a deletion message to the MME according to the 3GPP protocol, which is obviously not a manner recommended in the present disclosure.
  • the SGW when determining that an exception occurs in the PGW, the SGW performs a deletion operation on the PDN connection established with the faulty PGW, thereby reducing signaling transmission between the SGW and the MME, and improving service processing efficiency of a system.
  • Step 302 The SGW obtains a policy for deleting a packet data network PDN connection established between the SGW and the PGW.
  • the policy, obtained by the SGW, for deleting a packet data network PDN connection established between the SGW and the PGW includes, but is not limited to:
  • Policy 1 For different service types, determine a priority sequence for deleting PDN connections carrying services of different types.
  • deletion of a PDN connection carrying a voice service precedes deletion of a PDN connection carrying a data service.
  • types of services carried over PDN connections include a voice service, a video service, a web browsing service, and a background E-mail downloading service
  • a priority sequence for deleting PDN connections carrying the services of the foregoing types may be first deleting a PDN connection carrying the voice service, then deleting a PDN connection carrying the video service, then deleting a PDN connection carrying the web browsing service, and finally deleting a PDN connection carrying the background E-mail downloading service.
  • Policy 2 Determine, according to a service request message or uplink service data that is sent by a user and received in a PDN connection deletion process, a priority sequence for deleting PDN connections.
  • a PDN connection carrying the service request message or carrying the uplink service data is preferentially deleted.
  • the PDN connection carrying the service request message is preferentially deleted, and the PDN connection carrying the uplink service data is preferentially deleted.
  • deletion of the PDN connection carrying the service request message and deletion of the PDN connection carrying the uplink service data may be executed according to a receiving sequence of the service request message and the uplink service data, which is not limited herein.
  • Policy 3 For identical service request messages or identical uplink service data, determine, according to priorities of users sending the service request messages or the uplink service data, a priority sequence for deleting PDN connections.
  • Policy 4 For received uplink service data, determine, according to whether the uplink service data includes SIP signaling, a priority sequence for deleting PDN connections.
  • deletion of a PDN connection carrying uplink service data including the SIP signaling precedes deletion of a PDN connection carrying uplink service data not including the SIP signaling.
  • Policy 5 Determine, according to an APN to which a PDN connection belongs, a priority sequence for deleting PDN connections.
  • deletion of the PDN connection belonging to the APN that is an IMS APN precedes that of a PDN connection belonging to an APN that is not an IMS APN.
  • Step 303 The SGW traverses context information of a PDN connection established with the PGW.
  • step 303 the SGW traverses one piece of context information, and determines an attribute, corresponding to the traversed context information, of the PDN connection.
  • an attribute of a PDN connection may refer to a type of a service carried over the PDN connection, access point information, or the like.
  • Step 304 The SGW deletes, according to the traversed context information, the attribute of the PDN connection, and the policy for deleting a PDN connection, the PDN connection established between the SGW and the PGW, and turns to perform step 310 .
  • step 304 during PDN connection deletion, a PDN connection carrying a service of a high-priority type is preferentially deleted, and a PDN connection belonging to an APN that is an IMS APN is preferentially deleted.
  • a high priority of a service type refers to that different priorities are configured for types of services carried over PDN connections. For example, a priority of a voice service is higher than a priority of a video service, the priority of the video service is higher than a priority of a web browsing service, and the priority of the web browsing service is higher than a priority of background E-mail downloading.
  • the SGW may traverse at least twice context information of PDN connections established with the PGW.
  • Step 305 In a process of deleting PDN connections established with the PGW, the SGW receives uplink service data sent by a user equipment.
  • Step 306 The SGW determines whether a PDN connection carrying the uplink service data exists among the PDN connections being deleted, if yes, performs step 307 , and otherwise, responds to the uplink service data and at the same time performs step 304 .
  • Step 307 The SGW parses the uplink service data, determines whether the uplink service data includes SIP signaling, if yes, performs step 308 , and otherwise, performs step 309 .
  • an APN to which a PDN connection carrying the uplink service data belongs is an IMS APN.
  • Step 308 When determining that the uplink service data includes the SIP signaling, the SGW preferentially deletes a PDN connection carrying the uplink service data including the SIP signaling, and turns to perform step 310 .
  • Step 309 When receiving, in the PDN connection deletion process, uplink service data sent by a user, the SGW preferentially deletes a PDN connection carrying the uplink service data, and turns to perform step 310 .
  • step 308 and step 309 are performed, a priority for performing step 308 is higher than a priority of step 309 .
  • Step 310 The SGW sends a deletion request message to a mobility management entity MME.
  • the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • step 310 when determining that an exception occurs in the PGW, the SGW deletes the PDN connection between the SGW and the faulty PGW; in this case, the deletion request message is sent to the MME, requiring the MME to delete, when receiving the deletion request message, the PDN connection corresponding to the identity information of the PDN connection included in the deletion request message.
  • the SGW when determining that an exception occurs in the PGW, the SGW performs an operation on the PDN connection established with the faulty PGW, thereby reducing signaling transmission between the SGW and the MME, and improving service processing efficiency of a system.
  • the deletion request message is sent to the MME, where the deletion request message further includes identity information of the PGW, and the deletion request message is further used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME determines the PGW in which the fault occurs, deletes a PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • deletion request message further includes information, such as an IP address of an S5/S8 control plane of the PGW or an IP address of an S4/S11 interface of the PGW, for identifying a PGW fault.
  • the SGW sends the deletion request message (it should be noted that the deletion request message is a delete bearer request message) to the MME, where the deletion request message further includes a cause value of a Reactivation Request, so that when receiving the deletion request message including the cause value of the Reactivation Request, the MME deletes a specified PDN connection, and notifies a user equipment establishing the PDN connection with the PGW to re-initiate PDN connection reestablishment.
  • the deletion request message is a delete bearer request message
  • the deletion request message further includes a cause value of a Reactivation Request
  • the MME determines whether the user equipment has another PDN connection besides the PDN connection established with the faulty PGW; if not, the MME deletes the PDN connection established between the user equipment and the faulty PGW, and sends PDN connection reestablishment information to the user equipment, so that the user equipment establishes a new PDN connection with the PGW when receiving the PDN connection reestablishment information; and if yes, the MME releases, according to the cause value of the Reactivation Request included in the deletion request message, a PDN connection that is established between the user equipment and the faulty PGW and pointed to by the cause value of the Reactivation Request, and sends PDN connection reestablishment information to the user equipment, so that the user equipment establishes a new PDN connection with the PGW when receiving PDN connection reestablishment information.
  • Embodiment 4 of the present disclosure is disclosures based on a same disclosure conception, and the method may be described as follows:
  • Step 401 A MME receives a deletion request message sent by a serving gateway.
  • the deletion request message includes identity information of a to-be-deleted PDN connection.
  • the deletion request message further includes a cause value.
  • Step 402 The MME deletes, according to the deletion request message, a PDN connection corresponding to identity information.
  • Step 403 The MME notifies, according to the cause value included in the received deletion request message, a user to re-initiate PDN connection reestablishment for the deleted PDN connection.
  • the deletion request message further includes identity information of a PGW.
  • the method further includes: deleting, by the MME according to the identity information of the PGW included in the received deletion request message, a PDN connection established with the PGW corresponding to the identity information, and selecting another PGW for a user equipment establishing the deleted PDN connection.
  • Embodiment 5 of the present disclosure and Embodiment 1 of the present disclosure to Embodiment 4 of the present disclosure are disclosures based on a same disclosure conception, and the device includes a determining module 11 , an obtaining module 12 , a deleting module 13 , and a sending module 14 , where the determining module 11 is configured to determine that an exception occurs in a packet data network gateway PGW; the obtaining module 12 is configured to obtain a policy for deleting a packet data network PDN connection established with the PGW; the deleting module 13 is configured to delete, according to the policy for deleting a PDN connection obtained by the obtaining module, a PDN connection established with the PGW; and the sending module 14 is configured to send a deletion request message to a MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to
  • the deleting module 13 is further configured to determine, according to types of services carried over PDN connections established with the PGW, a priority sequence for deleting PDN connections carrying services of different types, and delete a PDN connection that needs to be preferentially deleted.
  • the deleting module 13 is further configured to preferentially delete a PDN connection carrying a voice service.
  • the deleting module 13 is further configured to, when a service request message sent by a user is received in a process of deleting the PDN connection, preferentially delete a PDN connection carrying the service request message.
  • the deleting module 13 is further configured to, when service request messages sent by multiple users are received in the process of deleting the PDN connection, determine priorities of the multiple users, and preferentially delete a PDN connection carrying a service request message sent by a user having a high priority.
  • the deleting module 13 is further configured to, when uplink service data sent by a user is received in a process of deleting the PDN connection, preferentially delete a PDN connection carrying the uplink service data.
  • the deleting module 13 is further configured to, when it is determined that the uplink service data includes SIP signaling, preferentially delete a PDN connection carrying the uplink service data including the SIP signaling.
  • the deleting module 13 is further configured to: when it is determined that an access point name APN to which a PDN connection belongs is an IMS APN, preferentially delete the PDN connection belonging to the APN that is an IMS APN.
  • the deleting module 13 is further configured to traverse context information of the PDN connection established with the PGW, and delete, according to the traversed context information, the packet data network PDN connection established with the PGW.
  • the deletion request message further includes a cause value, where the cause value is used for instructing the MME to notify a user, of the deleted PDN connection, to re-initiate PDN connection reestablishment.
  • the deletion request message further includes identity information of the PGW.
  • the sending module 14 is further configured to send, to the MME, deletion request message about the PDN connection corresponding to the context information, where the deletion request message is used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME deletes the PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • the device described in Embodiment 5 of the present disclosure may be a device implemented in a hardware form, and may also be a device implemented in a software form, which is not limited herein.
  • Embodiment 6 of the present disclosure is a schematic structural diagram of a service processing device according to Embodiment 6 of the present disclosure
  • Embodiment 1 of the present disclosure to Embodiment 5 of the present disclosure are disclosures based on a same disclosure conception
  • the device includes a receiving module 21 and a deleting module 22 , where the receiving module 21 is configured to receive a deletion request message sent by a SGW, where the deletion request message includes identity information of a to-be-deleted PDN connection, and the deleting module 22 is configured to delete, according to the deletion request message received by the receiving module, the PDN connection corresponding to the identity information.
  • the deletion request message further includes a cause value.
  • the device further includes a notifying module 23 , where the notifying module 23 is configured to notify, according to the cause value included in the deletion request message received by the receiving module, a user to re-initiate PDN connection reestablishment for the deleted PDN connection.
  • the deletion request message further includes identity information of a PGW.
  • the device further includes a reselecting module 24 , where the reselecting module 24 is configured to delete, according to the identity information of the PGW included in the deletion request message received by the receiving module, a PDN connection established with the PGW corresponding to the identity information, and select another PGW for a user equipment establishing the deleted PDN connection.
  • the device described in Embodiment 5 of the present disclosure may be a device implemented in a hardware form, and may also be a device implemented in a software form, which is not limited herein.
  • Embodiment 7 of the present disclosure and Embodiment 1 of the present disclosure to Embodiment 6 of the present disclosure are disclosures based on a same disclosure conception, and the device includes a processor 31 and a signal transmitter 32 , where the processor 31 and the signal transmitter 32 are connected by using a bus 33 .
  • the processor 31 is configured to determine that an exception occurs in a PGW, obtain a policy for deleting a PDN connection established with the PGW, and delete a PDN connection established with the PGW according to the policy for deleting a PDN connection.
  • the signal transmitter 32 is configured to send a deletion request message to a MME, where the deletion request message includes identity information of the deleted PDN connection and is used for notifying the MME to delete a PDN connection corresponding to the identity information.
  • the processor 31 is further configured to determine, according to types of services carried over PDN connections established with the PGW, a priority sequence for deleting PDN connections carrying services of different types, and delete a PDN connection that needs to be preferentially deleted.
  • the processor 31 is further configured to preferentially delete a PDN connection carrying a voice service.
  • the processor 31 is further configured to, when receiving, in a process of deleting the PDN connection, a service request message sent by a user, preferentially delete a PDN connection carrying the service request message.
  • the processor 31 is further configured to, when receiving, in the process of deleting the PDN connection, service request messages sent by multiple users, determine priorities of the multiple users, and preferentially delete a PDN connection carrying a service request message sent by a user having a high priority.
  • the processor 31 is further configured to, when receiving, in a process of deleting the PDN connection, uplink service data sent by a user, preferentially delete a PDN connection carrying the uplink service data.
  • the processor 31 is further configured to, when determining that the uplink service data includes SIP signaling, preferentially delete a PDN connection carrying the uplink service data including the SIP signaling.
  • the processor 31 is further configured to, when determining that an APN to which a PDN connection belongs is an IMS APN, preferentially delete the PDN connection belonging to the APN that is an IMS APN.
  • the processor 31 is further configured to traverse context information of the PDN connection established with the PGW, and delete, according to the traversed context information, the packet data network PDN connection established with the PGW.
  • the deletion request message further includes a cause value, where the cause value is used for instructing the MME to notify a user, of the deleted PDN connection, to re-initiate PDN connection reestablishment.
  • the deletion request message further includes identity information of the PGW.
  • the signal transmitter 32 is further configured to send, to the MME, deletion request message about the PDN connection corresponding to the context information, where the deletion request message is used for indicating that a fault occurs in the PGW corresponding to the identity information, so that when receiving the deletion request message, the MME deletes the PDN connection established with the PGW corresponding to the identity information, and selects another PGW for a user equipment establishing the deleted PDN connection.
  • Embodiment 8 of the present disclosure and Embodiment 1 of the present disclosure to Embodiment 7 of the present disclosure are disclosures based on a same disclosure conception, and the device includes a signal receiver 41 and a processor 42 , where the signal receiver 41 and the processor 42 are connected by using a bus 43 .
  • the signal receiver 41 is configured to receive a deletion request message sent by a SGW, where the deletion request message includes identity information of a to-be-deleted PDN connection.
  • the processor 42 is configured to delete, according to the deletion request message received by the receiver, the PDN connection corresponding to the identity information.
  • the deletion request message further includes a cause value.
  • the processor 42 is further configured to notify, according to the cause value included in the deletion request message received by the receiver, a user to re-initiate PDN connection reestablishment for the deleted PDN connection.
  • the deletion request message further includes identity information of a PGW.
  • the processor 42 is further configured to delete, according to the identity information of the PGW included in the deletion request message received by the receiver, a PDN connection established with the PGW corresponding to the identity information, and select another PGW for a user equipment establishing the deleted PDN connection.
  • bus involved in the embodiments of the present disclosure may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus may be classified into an address bus, a data bus, a control bus, and the like.
  • the processor involved in the embodiments of the present disclosure may be a central processing unit (CPU), and may also be another device having a control function, which is not limited herein.
  • CPU central processing unit
  • control function which is not limited herein.
  • the embodiments of the present disclosure may be provided as a method, an apparatus (device), or a computer program product. Therefore, the present disclosure may use a form of hardware only embodiments, software only embodiments, or embodiments with a combination of software and hardware. Moreover, the present disclosure may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a disk memory, a compact disc-read only memory (CD-ROM), an optical memory, and the like) that include computer usable program code.
  • computer-usable storage media including but not limited to a disk memory, a compact disc-read only memory (CD-ROM), an optical memory, and the like
  • These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of any other programmable data processing device to generate a machine, so that the instructions executed by a computer or a processor of any other programmable data processing device generate an apparatus for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may also be stored in a computer readable memory that can instruct the computer or any other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory generate an artifact that includes an instruction apparatus.
  • the instruction apparatus implements a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
  • These computer program instructions may also be loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the other programmable device, thereby generating computer-implemented processing. Therefore, the instructions executed on the computer or the other programmable device provide steps for implementing a specific function in one or more processes in the flowcharts and/or in one or more blocks in the block diagrams.
US15/199,206 2013-12-31 2016-06-30 Service processing method and device Active 2034-08-16 US10165618B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/091168 WO2015100638A1 (fr) 2013-12-31 2013-12-31 Procédé et dispositif de traitement de service

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/091168 Continuation WO2015100638A1 (fr) 2013-12-31 2013-12-31 Procédé et dispositif de traitement de service

Publications (2)

Publication Number Publication Date
US20160316515A1 US20160316515A1 (en) 2016-10-27
US10165618B2 true US10165618B2 (en) 2018-12-25

Family

ID=50671638

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/199,206 Active 2034-08-16 US10165618B2 (en) 2013-12-31 2016-06-30 Service processing method and device

Country Status (5)

Country Link
US (1) US10165618B2 (fr)
EP (1) EP3089544B1 (fr)
KR (1) KR101922577B1 (fr)
CN (1) CN103797838B (fr)
WO (1) WO2015100638A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2666633C2 (ru) * 2014-06-30 2018-09-11 Хуавэй Текнолоджиз Ко., Лтд. Способ повторного установления pdn-соединения, центральный сервер сброса, элемент сети управления мобильностью и шлюз передачи данных
CN105338560B (zh) * 2014-08-07 2019-02-26 中国电信股份有限公司 服务网关容灾方法、设备和系统
CN105682155B (zh) * 2014-11-21 2020-09-08 南京中兴新软件有限责任公司 一种mme识别pdn连接受pgw故障影响的方法及装置
CN105813119B (zh) * 2014-12-31 2019-06-14 中国电信股份有限公司 容灾恢复方法、网元以及通信系统
WO2017018663A1 (fr) * 2015-07-24 2017-02-02 엘지전자 주식회사 Procédé de gestion de connexion pdn et entité de réseau
RU2676681C1 (ru) * 2015-08-17 2019-01-10 Хуавэй Текнолоджиз Ко., Лтд. Способ и устройство обновления шлюза плоскости пользователя
WO2018141114A1 (fr) * 2017-02-06 2018-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et dispositif d'identification de connexion pdn pour service ims
CN109144735B (zh) * 2018-09-29 2019-12-27 百度在线网络技术（北京）有限公司 用于处理数据的方法和装置
CN111757401B (zh) * 2019-03-29 2021-12-14 华为技术有限公司 一种网关选择系统及方法

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101610201A (zh) 2008-06-20 2009-12-23 大唐移动通信设备有限公司 实现pdn连接释放的方法、装置和系统
CN101686563A (zh) 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法
CN101730125A (zh) 2009-06-19 2010-06-09 中兴通讯股份有限公司 一种非相邻节点间进行节点检测的方法
CN101730062A (zh) 2009-06-11 2010-06-09 中兴通讯股份有限公司 一种非相邻节点间异常处理方法
WO2011095256A1 (fr) 2010-02-02 2011-08-11 Telefonaktiebolaget L M Ericsson (Publ) Redémarrage de nœud homologue
US20110299429A1 (en) * 2010-06-02 2011-12-08 Kundan Tiwari Methods for handling ps and cs communication service
CN102413584A (zh) 2010-09-20 2012-04-11 电信科学技术研究院 一种pdn连接的管理方法和设备
CN102413562A (zh) 2010-09-20 2012-04-11 电信科学技术研究院 一种pdn连接的管理方法和设备
US20120147839A1 (en) 2009-08-21 2012-06-14 Huawei Technologies Co., Ltd. Method, System, and Access Gateway for Traffic Flows to Share Resources
CN102625475A (zh) 2012-04-06 2012-08-01 电信科学技术研究院 一种pdn连接的删除方法和设备
US20120294155A1 (en) * 2010-01-27 2012-11-22 Huawei Technologies Co., Ltd. Method, apparatus and system for handling node failure
US20130042011A1 (en) * 2010-04-14 2013-02-14 Panasonic Corporation Communication nodes and network nodes
US20140349602A1 (en) * 2013-05-23 2014-11-27 Broadcom Corporation Deactivating Elevated Priority Public Data Network Connections In User Equipment
US20160380802A1 (en) * 2013-09-24 2016-12-29 Nec Corporation Methods and apparatuses for facilitating p-cscf restoration when a p-cscf failure has occurred

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110164566A1 (en) 2008-06-20 2011-07-07 Datang Mobile Communications Equipment Co., Ltd. Method, Apparatus and System for Enabling to Release PDN Connections
CN101610201A (zh) 2008-06-20 2009-12-23 大唐移动通信设备有限公司 实现pdn连接释放的方法、装置和系统
CN101686563A (zh) 2008-09-23 2010-03-31 三星电子株式会社 移动通信系统中资源释放的方法
US20120069733A1 (en) 2009-06-11 2012-03-22 Zte Corporation Method for processing abnormality between non-adjacent nodes
CN101730062A (zh) 2009-06-11 2010-06-09 中兴通讯股份有限公司 一种非相邻节点间异常处理方法
CN101730125A (zh) 2009-06-19 2010-06-09 中兴通讯股份有限公司 一种非相邻节点间进行节点检测的方法
US20120147839A1 (en) 2009-08-21 2012-06-14 Huawei Technologies Co., Ltd. Method, System, and Access Gateway for Traffic Flows to Share Resources
US20120294155A1 (en) * 2010-01-27 2012-11-22 Huawei Technologies Co., Ltd. Method, apparatus and system for handling node failure
WO2011095256A1 (fr) 2010-02-02 2011-08-11 Telefonaktiebolaget L M Ericsson (Publ) Redémarrage de nœud homologue
US20130042011A1 (en) * 2010-04-14 2013-02-14 Panasonic Corporation Communication nodes and network nodes
US20110299429A1 (en) * 2010-06-02 2011-12-08 Kundan Tiwari Methods for handling ps and cs communication service
CN102413584A (zh) 2010-09-20 2012-04-11 电信科学技术研究院 一种pdn连接的管理方法和设备
CN102413562A (zh) 2010-09-20 2012-04-11 电信科学技术研究院 一种pdn连接的管理方法和设备
CN102625475A (zh) 2012-04-06 2012-08-01 电信科学技术研究院 一种pdn连接的删除方法和设备
US20140349602A1 (en) * 2013-05-23 2014-11-27 Broadcom Corporation Deactivating Elevated Priority Public Data Network Connections In User Equipment
US20160380802A1 (en) * 2013-09-24 2016-12-29 Nec Corporation Methods and apparatuses for facilitating p-cscf restoration when a p-cscf failure has occurred

Non-Patent Citations (16)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Restoration procedures (Release 11)," 3GPP TS 23.007, Technical Specification, V11.0.0, Dec. 2011, 56 pages.
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Restoration procedures (Release 12)," 3GPP TS 23.007, V12.3.0, Dec. 2013, 85 pages.
"Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services-Systems and Terminal Equipment for Audiovisual Services, Packet-Based Multimedia Communications Systems, Amendment 1: Use of Facility message to enable call transfer," ITU-T, H.323, Amendment 1, Mar. 2013, 8 pages.
"Series H: Audiovisual and Multimedia Systems, Infrastructure of audiovisual services—Systems and Terminal Equipment for Audiovisual Services, Packet-Based Multimedia Communications Systems, Amendment 1: Use of Facility message to enable call transfer," ITU-T, H.323, Amendment 1, Mar. 2013, 8 pages.
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study of EPC Nodes Restoration (Release 11), 3GPP TR 23.857, Technical Specification, V1.6.0, Nov. 2011, 58 pages.
Foreign Communication From a Counterpart Application, Chinese Application No. 201380002817.6, Chinese Office Action dated Oct. 25, 2016, 8 pages.
Foreign Communication From a Counterpart Application, European Application No. 13900596.1, Extended European Search Report dated Jan. 2, 2017, 8 pages.
Foreign Communication From a Counterpart Application, Korean Application No. 10-2016-7020909, English Translation of Korean Office Action dated Feb. 2, 2018, 3 pages.
Foreign Communication From a Counterpart Application, Korean Application No. 10-2016-7020909, Korean Office Action dated Feb. 2, 2018, 5 pages.
Foreign Communication From a Counterpart Application, PCT Application No. PCT/CN2013/091168, English Translation of International Search Report dated Sep. 30, 2014, 2 pages.
Foreign Communication From a Counterpart Application, PCT Application No. PCT/CN2013/091168, English Translation of Written Opinion dated Sep. 30, 2014, 7 pages.
Partial English Translation and Abstract of Chinese Patent Application No. CN101686563, Part 1, dated Mar. 31, 2010, 9 pages.
Partial English Translation and Abstract of Chinese Patent Application No. CN101686563, Part 2, dated Mar. 31, 2010, 2 pages.
Partial English Translation and Abstract of Chinese Patent Application No. CN101730125, dated Jun. 9, 2010, 5 pages.
Partial English Translation and Abstract of Chinese Patent Application No. CN102413562, dated Apr. 11, 2012, 5 pages.
Partial English Translation and Abstract of Chinese Patent Application No. CN102413584, dated Apr. 11, 2012, 6 pages.

Also Published As

Publication number Publication date
EP3089544A1 (fr) 2016-11-02
WO2015100638A1 (fr) 2015-07-09
KR20160104058A (ko) 2016-09-02
KR101922577B1 (ko) 2018-11-27
CN103797838B (zh) 2018-08-07
CN103797838A (zh) 2014-05-14
US20160316515A1 (en) 2016-10-27
EP3089544B1 (fr) 2020-04-08
EP3089544A4 (fr) 2017-01-25

Similar Documents

Publication Publication Date Title
US10165618B2 (en) Service processing method and device
CN110366214B (zh) 一种语音业务的网络切换方法及装置
US11178057B2 (en) Offloading policy negotiation method and apparatus
WO2017063427A1 (fr) Procédé et appareil de communication, et terminal
US20150036492A1 (en) Terminal triggering method and related device
CN107580335A (zh) 移动终止呼叫改进
US9332426B2 (en) Communication system, communication method, and communication program
CN104704866A (zh) 重建pdn连接的方法、复位中心服务器、移动管理网元和数据网关
CN109429366B (zh) 一种pdu会话处理方法及设备
US20180255481A1 (en) Service flow transmission method and apparatus
US10440616B2 (en) Failure handling method, packet data network, mobility management entity, and network system
WO2013097503A1 (fr) Procédé et dispositif de régulation d'encombrement
CN112437426B (zh) 一种发送下行数据通知消息的方法和装置
CN107205230B (zh) 一种恢复终端在线计费状态的方法、装置及系统
WO2017000694A1 (fr) Procédé et dispositif de réacheminement de données
WO2020200136A1 (fr) Système et procédé de sélection de passerelle
WO2021047443A1 (fr) Procédé et appareil de transfert de paquet de données de service
JP6180626B2 (ja) ユーザ装置、通信制御装置、及び発信拒否制御方法
WO2014090011A1 (fr) Procédé d'initiation de signalisation, appareil et dispositif passerelle
CN105027660A (zh) 一种ps业务恢复方法、msc/vlr及mme
CN105744620A (zh) 一种电路域回落的寻呼方法及装置
KR101620362B1 (ko) Gtp 네트워크 프로토콜 버전에 따른 세션 관리 방법 및 장치
WO2011160287A1 (fr) Procédés et dispositifs de régulation de l'encombrement
KR20240044508A (ko) 세션 관리를 위한 방법 및 장치
WO2013102303A1 (fr) Procédé, dispositif et système de communication de commande de session

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LONG, SIRUI;REEL/FRAME:041008/0908

Effective date: 20161129

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4