WO2011109998A1 - 一种承载处理方法、系统及移动管理网元 - Google Patents

一种承载处理方法、系统及移动管理网元 Download PDF

Info

Publication number
WO2011109998A1
WO2011109998A1 PCT/CN2010/076183 CN2010076183W WO2011109998A1 WO 2011109998 A1 WO2011109998 A1 WO 2011109998A1 CN 2010076183 W CN2010076183 W CN 2010076183W WO 2011109998 A1 WO2011109998 A1 WO 2011109998A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
voice
bearers
request message
gateway
Prior art date
Application number
PCT/CN2010/076183
Other languages
English (en)
French (fr)
Inventor
于益俊
陆峰
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201080001879.1A priority Critical patent/CN102405683B/zh
Priority to PCT/CN2010/076183 priority patent/WO2011109998A1/zh
Publication of WO2011109998A1 publication Critical patent/WO2011109998A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • 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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a bearer processing method, system, and mobility management network element. Background technique
  • SRVCC Single Radio Voice Call Continuity
  • a wireless voice call continuity technology as an initial voice continuity solution for IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) voice deployment, can be provided for E-UTRAN (Evolved UMTS Territorial Radio Access Network) , Evolved UMTS Terrestrial Radio Access Network) seamlessly switched to UTRAN (UMTS Territorial Radio Access Network UMTS) / GERAN (GSM EDGE Radio Access Network, GSM EDGE Radio Access Network)
  • the current SRVCC performance enhancement project is designed to improve the switching performance of SRVCC and to avoid excessive interruptions in the handover process.
  • the use of locally anchored SRVCC enhancement scheme is one of the main recommendations in the existing SRVCC enhancement scheme.
  • the UE performs CSFB (CS Fallback) joint attachment and registers with the IMS through the MSC (Mobile Switch Center) / MGW (Media Gate Way). And establish a SIP (Session Initiated Protocol) session with the SCCAS (Service Centralization and Continuity Application Server) in the SRVCC handover process.
  • the MSC/MGW and the SGW Serving Gateway, service
  • the gateway establishes a GTP (GPRS Tunneling Protocol) channel for transmitting voice data of the uplink and downlink.
  • GTP GPRS Tunneling Protocol
  • the existing locally anchored SRVCC enhancement is used.
  • the SGW/PGW Packet Data Network Gateway
  • the SGW/PGW suspends the non-GBR (Guest Guaranteed Bit Rate) bearer of the UE. And deactivating the GBR bearer that includes the voice bearer, so that the SGW/PGW will discard all the data packets of the received UE that include the voice service, so that the voice service cannot be normally performed by the gateway device at this time.
  • the embodiment of the present invention provides a bearer processing method, a system, and a mobility management network element, so that the gateway device does not hang and does not activate the voice bearer of the user equipment in the SRVCC process, thereby ensuring the normal voice service of the user. get on.
  • a bearer processing method includes:
  • a mobile management network element including:
  • a receiving module configured to receive a handover requirement message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node;
  • a mobile management network element including:
  • a receiving module configured to receive a handover requirement message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node;
  • a sending module configured to send a suspend request message to the serving gateway, to trigger the serving gateway to send a suspend request message to the packet data network gateway, so that the serving gateway releases the user plane resources of other bearers other than the voice bearer, and retains User plane resources carried by voice;
  • the service gateway and the packet data network gateway are caused to suspend the non-GBR bearer; or the service gateway and the packet data network gateway are suspended from other bearers other than the voice bearer.
  • a mobile management network element including:
  • a receiving module configured to receive a handover requirement message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node;
  • a sending module configured to send a suspend request message to the serving gateway, so that the serving gateway releases the user plane resources of other bearers except the voice bearer, retains the user plane resources of the voice bearer, suspends the non-GBR bearer, and deactivates Other GBR bearers other than voice bearers;
  • a bearer processing system comprising:
  • a mobility management network element configured to send a release access bearer request message or a suspension request message to the serving gateway
  • a serving gateway configured to receive a release access bearer request message or a suspend request message from the mobility management network element, perform user plane resources of other bearers other than the voice bearer, and retain the user plane resources of the voice bearer, and suspend Non-GBR bears or suspends other bearers other than voice bearers, Other GBR bearers other than live voice bearers.
  • the MME Mobility Management Entity
  • the SGW releases the user plane resources of the bearer other than the voice bearer, and retains the user plane resources of the voice bearer, so that the SGW and the PGW suspend non-GBR bearers and deactivate other GBR bearers other than the voice bearer, thereby ensuring the voice service of the user. Work properly.
  • FIG. 1 is a flowchart of a bearer processing method according to an embodiment of the present invention
  • 2a is a signaling flowchart of a bearer processing method according to an embodiment of the present invention
  • FIG. 2 is a second signaling flowchart of a bearer processing method according to an embodiment of the present invention
  • FIG. 3 is a signaling flowchart of a bearer processing method according to another embodiment of the present invention
  • FIG. 4b is a second signaling flowchart 5 of a bearer processing method according to another embodiment of the present invention.
  • FIG. 6 is a first schematic diagram of a mobility management network element according to an embodiment of the present invention.
  • 6b is a second schematic diagram of a mobility management network element according to an embodiment of the present invention.
  • 6c is a third schematic diagram of a mobility management network element according to an embodiment of the present invention.
  • FIG. 7 is a fourth schematic diagram of a mobility management network element according to an embodiment of the present disclosure.
  • FIG. 8 is a fifth schematic diagram of a mobility management network element according to an embodiment of the present disclosure.
  • FIG. 8b is a sixth schematic diagram of a mobility management network element according to an embodiment of the present disclosure.
  • FIG. 9 is a seventh schematic diagram of a mobility management network element according to an embodiment of the present disclosure.
  • FIG. 10a is a first schematic diagram of a bearer processing system according to an embodiment of the present invention.
  • FIG. 10b is a second schematic diagram of a bearer processing system according to an embodiment of the present invention. detailed description
  • All of the following embodiments of the present invention are based on the scenario of the SRVCC handover scheme, that is, the scheme of using the local SGW/PGW as an anchor point to transmit VoIP (voice over Internet Protocol) services, for example: using locally anchored SRVCC Enhance the program.
  • the description of the improved bearer processing method of the foregoing scenario is performed, and therefore, the repetitive description of the scenario is not repeated in the embodiments.
  • the bearers of the UE are classified into two types: a GBR bearer and a non-GBR bearer.
  • the GBR bearer refers to a bearer with a guaranteed bit rate, including: a voice bearer and other GBR bearers other than the voice bearer.
  • the MME/SGW/PGW may identify the voice bearer, the non-GBR bearer, and the GBR payload based on the specific value of the QoS Class Identifier (QCI), for example, if there is only one carrier QCI value in the payload 1 , the bearer can be identified as a voice bearer; or, for example, if a bearer has a QCI value of 5 to 9, the bearer is identified as a non-GBR bearer.
  • QCI QoS Class Identifier
  • the MME/SGW/PGW may perform corresponding suspension, deactivation, reservation, etc. on the bearer according to the above QCI value and other indication cells included in the received message.
  • FIG. 1 is a flowchart of a bearer processing method according to an embodiment of the present invention.
  • Step 101 In a process of performing an SRVCC, receiving a handover request message from a source-side evolved base station or from a source-side evolved base station a user equipment context release request message or a suspend message from the target side serving GPRS support node;
  • Step 102 Send a request message to the serving gateway, so that the serving gateway releases the user plane resources of other bearers outside the voice bearer, and retains the user plane resources of the voice bearer.
  • the MME can release the user plane resources of other bearers except the voice bearer according to the received information in the step 101, and retain the user plane resources of the voice bearer, and the bearer resources are reserved. Perform the corresponding suspend and deactivate processing, as described below:
  • the MME sends a release access bearer request message to the SGW, where the release access bearer request message includes a voice bearer reservation indication or a radio access bearer information of other bearers other than the voice bearer (other than the non-GBR bearer and the voice bearer)
  • the GBR carries the radio access bearer information, so that the SGW releases the user plane resources of the bearers other than the voice bearer, retains the user plane resources of the voice bearer, and receives the release access bearer response message from the SGW;
  • the MME sends a suspend request message to the SGW, the SGW suspends the non-GBR bearer, and retains the voice bearer in the GBR bearer; or the SGW suspends the bearer other than the voice bearer, and retains the voice in the GBR bearer. Hosted.
  • the SGW After the SGW receives the suspend request message sent by the MME, the SGW sends a suspend request message to the PGW, where the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or The identifier of the bearer other than the voice bearer, the PGW hangs the non-GBR bearer, and the voice bearer in the GBR bearer is reserved; or the PGW suspends other bearers except the voice bearer, and retains the voice in the GBR bearer. Hosted.
  • the identifier of the voice payload that needs to be reserved may be included in the cell "Bearer to be reserve” or "Voice Bearer”, and is used to indicate that the network element device that receives the information retains the bearer, and the embodiment does not limit the cell.
  • the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell “Bearer to be suspend” or “Bearer Context”, and is used to indicate that the network element device receiving the information suspends the bearer This embodiment does not limit the name of the cell.
  • the SGW receives the pending response message from the PGW, and the MME receives the pending response message from the SGW to complete the suspend process.
  • the MME sends a delete bearer command message to the SGW to initiate a deactivation process, and the SGW activates other GBR bearers other than the voice bearer.
  • the MME may also initiate the deactivation procedure after receiving the release access bearer response message from the SGW.
  • the above three steps of A, B, and C are executed in a fixed order relationship and can be received at the MME.
  • the handover request message from the source-side evolved base station or the user equipment context release request message from the source-side evolved base station or the suspend message from the target-side serving GPRS support node is simultaneously triggered; and the handover request from the source-side evolved base station may also be received.
  • the message is triggered separately from the user equipment context release request message from the source side evolved base station or the suspend message from the target side serving GPRS support node, but there is no fixed order relationship and mutual dependencies.
  • the deactivation process described in the foregoing C may be implemented by: after receiving the release access bearer request message from the MME, the SGW triggers the SGW to initiate a deactivation process to the PGW, and the PGW deactivates the voice bearer.
  • Other GBR bearers may be implemented by: after receiving the release access bearer request message from the MME, the SGW triggers the SGW to initiate a deactivation process to the PGW, and the PGW deactivates the voice bearer.
  • Other GBR bearers may be implemented by: after receiving the release access bearer request message from the MME, the SGW triggers the SGW to initiate a deactivation process to the PGW, and the PGW deactivates the voice bearer.
  • the MME sends a release access bearer request message to the SGW, where the release access bearer request message includes a voice bearer reservation indication or a radio access bearer information of other bearers other than the voice bearer (other than the non-GBR bearer and the voice bearer)
  • the GGW bears the radio access bearer information
  • the SGW releases the user plane resources of the bearer other than the voice bearer, retains the user plane resources of the voice bearer, and receives the release access bearer response message from the SGW;
  • the MME sends a suspend request message to the SGW, the SGW suspends the non-GBR bearer, retains the voice bearer in the GBR bearer, and deactivates other GBR bearers than the voice bearer.
  • the SGW After the SGW receives the suspend request message sent by the MME, the SGW sends a suspend request message to the PGW, where the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or The identifier of the bearer other than the voice bearer to be suspended, the PGW suspending the non-GBR bearer and retaining the voice bearer in the GBR bearer, and deactivating other GBR bearers other than the voice bearer.
  • the identifier of the voice bearer that needs to be reserved may be included in the cell "Bearer to be reserve” or "Voice Bearer", and is used to indicate that the network element device that receives the information retains the bearer, and the embodiment does not limit the cell.
  • the identifier of the other than the voice 7 that needs to be suspended may be included in the cell "Bearer to be suspend” or "Bearer Context”, and is used to indicate that the network element device receiving the information suspends the Bearer, this embodiment does not limit the name of the cell.
  • the SGW receives the suspend response message from the PGW, and the MME receives the suspend response message from the SGW, completing the suspend process and other processing on the bearer.
  • the foregoing two steps of A and B are performed in a fixed order relationship, and the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or the hanging from the target side serving GPRS support node may be received at the MME. Triggering at the same time after the message is received; may also be triggered after receiving the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or the suspend message from the target side serving GPRS support node, but no Fixed order relationships and interdependencies.
  • the MME sends a suspend request message to the SGW, where the suspend request message includes an indication of a voice-bearing reservation or an identifier of a voice bearer to be reserved or an identifier of another bearer other than the voice bearer to be suspended;
  • the SGW releases the user plane resources of the bearer other than the voice bearer, retains the user plane resources of the voice bearer, suspends the non-GBR bearer, and retains the voice bearer in the GBR bearer; or the SGW releases other bearers than the voice bearer.
  • the user plane resource retains the user plane resources of the voice bearer, suspends other bearers other than the voice bearer, and retains the voice bearer in the GBR bearer.
  • the SGW After the SGW receives the suspend request message sent by the MME, the SGW sends a suspend request message to the PGW, where the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or The identifier of the bearer other than the voice bearer, the PGW hangs the non-GBR bearer, and the voice bearer in the GBR bearer is reserved; or the PGW suspends other bearers except the voice bearer, and retains the voice in the GBR bearer. Hosted.
  • the above-mentioned identifier of the voice bearer that needs to be reserved may be included in the cell "Bearer to be reserve” or “Voice Bearer”, and is used to indicate that the network element device that receives the information retains the bearer, which is not limited in this embodiment.
  • the name of the cell; the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell "Bearer to be suspend” or "Bearer Context", and is used to indicate that the network element device that receives the information hangs For the bearer, this embodiment does not limit the name of the cell.
  • the SGW receives the suspend response message from the PGW, and the MME receives the suspend response message from the SGW, completing the suspend process and other processing on the bearer.
  • the MME sends a delete bearer command message to the SGW, and initiates a deactivation process, so that the SGW deactivates other GBR bearers other than the voice bearer.
  • the foregoing two steps of A and B are performed in a fixed order relationship, and the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or the hanging from the target side serving GPRS support node may be received at the MME. Triggering at the same time after the message is received; may also be triggered after receiving the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or the suspend message from the target side serving GPRS support node, but no Fixed order relationships and interdependencies.
  • the foregoing deactivation process may be implemented by: after receiving the suspension request message from the MME, the SGW triggers the SGW to initiate a deactivation process to the PGW, and the PGW deactivates other GBR bearers except the voice bearer.
  • the MME sends a Suspend Request message to the SGW, where the Suspend Request message includes a voice 7 bearer indication or an identifier of the voice bearer to be reserved or an identifier of a bearer other than the suspended voice bearer;
  • the user plane resources of the bearer other than the voice bearer retain the user plane resources of the voice bearer;
  • the SGW suspends the non-GBR bearer, retains the voice bearer in the GBR bearer, and deactivates other GBR bearers other than the voice bearer.
  • the SGW After the SGW receives the suspend request message sent by the MME, the SGW sends a suspend request message to the PGW, where the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or The identifier of the bearer other than the voice bearer that needs to be suspended, the PGW suspends the non-GBR bearer, retains the voice bearer in the GBR bearer, and deactivates other GBR bearers other than the voice bearer.
  • the identifier of the voice bearer that needs to be reserved may be included in the cell "Bearer to be reserve” or "Voice Bearer", and is used to indicate that the network element device that receives the information retains the bearer.
  • the embodiment does not limit the name of the cell; the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell "Bearer to be suspend” or "Bearer Context", and is used to indicate that the information is received.
  • the network element device suspends the bearer. This embodiment does not limit the name of the cell.
  • the SGW receives the pending response message from the PGW, and the MME receives the pending response message from the SGW, completing the suspending process and other processing on the bearer.
  • the voice bearer in the reserved GBR bearer may be: retaining the context of the voice bearer, not changing the voice bearer context content (eg, MBR, etc.) and not suspending the voice bearer;
  • the suspending the non-GBR bearer may be: retaining the context of the non-GBR bearer, and setting the state of the non-GBR bearer to be suspended;
  • the other bearers other than the suspended voice bearer may be: a context of the bearer other than the voice bearer, and setting the state of the other bearers other than the voice bearer to be suspended;
  • the other GBR bearers other than the deactivated voice bearer may be: deleting the voice bearer The context of other GBR bearers.
  • the SGW/PGW discards the packet corresponding to the bearer that is received by the SGW/PGW.
  • the SGW/ is because the voice bearer remains and is not suspended.
  • the PGW will normally perform IP voice (VoIP) services.
  • the MME sends a request message to the SGW, so that the SGW releases the user plane resources of other bearers except the voice bearer, and retains the user plane resources of the voice bearer.
  • the SGW and the PGW suspend non-GBR bearers and deactivate other GBR bearers other than the voice bearer to ensure normal voice service of the user.
  • FIG. 2a is a signaling flowchart of a bearer processing method according to an embodiment of the present invention, as shown in FIG. 2a:
  • the MME receives the handover requirement message from the source side eNodeB (Evolved Node B) or the MME receives the UE context release request message (UE Context Release Request) from the source side eNodB or the MME receives the Suspend message of the target side SGSN (Serving GPRS Support Node service GPRS support node), the suspend message may be a Suspend Notification message, or may be carrying a suspend request ( Suspend Request ) extends header messages (eg SGSN context Request ).
  • the source side eNodeB Evolved Node B
  • UE context release request message UE Context Release Request
  • the MME receives the Suspend message of the target side SGSN (Serving GPRS Support Node service GPRS support node)
  • the suspend message may be a Suspend Notification message, or may be carrying a suspend request ( Suspend Request ) extends header messages (eg SGSN context Request ).
  • the source side MME initiates a release access bearer process, including:
  • the MME receives the UE context release request message (UE Context Release Request) from the source side eNodB or the MME receives the target side SGSN (
  • the GPRS support node of the Serving GPRS Support Node service the source MME sends a Release Access Bearer Request message to the SGW;
  • the release access request message includes a voice bearer reservation indication or The radio access bearer information of the bearer other than the voice bearer (the non-GBR bearer and the radio bearer information of the GBR bearer other than the voice bearer), the SGW releases the user plane resources of the bearer other than the voice bearer, and retains the voice User plane resources carried;
  • the SGW sends a release access bearer response (Release Access Bearer Response) message to the source MME.
  • release access bearer response Release Access Bearer Response
  • the source MME initiates a suspension process to the SGW, including:
  • the source MME sends a suspend request message to the SGW, and the SGW suspends the non-GBR bearer; or the source MME sends a suspend request message to the SGW, and the SGW suspends other bearers other than the voice bearer;
  • the SGW suspends the non-GBR bearer or suspends other bearers other than the voice bearer.
  • the specific implementation may include, but is not limited to, the following methods:
  • the SGW may suspend the non-GBR bearer or suspend the voice bearer according to the local voice bearer reservation indication received in step 202a or the radio bearer information of other bearers other than the voice bearer. Other bearers; or,
  • the SGW may suspend a non-GBR bearer or suspend another bearer other than the voice bearer according to the voice bearer reservation indication;
  • the suspend request message includes an identifier of a voice bearer to be reserved, the label of the voice that needs to be retained. And may be included in the cell "Bearer to be reserve” or "Voice Bearer", and is used to indicate that the network element device that receives the information retains the bearer, and the embodiment does not limit the name of the cell, and the SGW may be based on The identifier of the voice bearer that needs to be reserved hangs a non-GBR bearer or suspends other bearers other than the voice bearer; or
  • the suspension request message includes an identifier of a bearer other than the voice bearer that needs to be suspended
  • the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell "Bearer to be suspend" or In the "Bearer Context", the network element device that is used to receive the information suspends the bearer.
  • the name of the cell is not limited, and the SGW may be configured according to the bearer other than the voice bearer that needs to be suspended. The identity hangs a non-GBR bearer or suspends other bearers than the voice bearer.
  • the suspending the non-GBR bearer may be: retaining the context of the non-GBR bearer, and setting the state of the non-GBR bearer to be suspended; : Preserving the context of other bearers other than the voice bearer, and setting the state of other bearers other than the voice bearer to hang. If the bearer (for example, the non-GBR bearer) is suspended, the SGW will discard the packet corresponding to the bearer that is received by the SGW. In this embodiment, the SGW is normal because the voice bearer remains and is not suspended.
  • IP voice ie VoIP
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request, or may be a new message, such as an SRVCC Suspend Notification.
  • the message this embodiment does not: limit.
  • the SGW sends a suspension request message to the PGW.
  • the SGW After the SGW receives the suspend request message from the source MME, the SGW sends a suspend request message to the PGW, and the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or needs to be suspended.
  • the PGW can perform the following operations: suspending a non-GBR bearer; or suspending other bearers other than the voice bearer. For the specific implementation, refer to the corresponding processing performed by the SGW in step 203a, and details are not described herein again.
  • the PGW will discard the packet corresponding to the bearer received by the PGW.
  • the PGW will be normal because the voice bearer remains and is not suspended. Perform IP voice (VoIP) services.
  • VoIP IP voice
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request message, or may be a new message, such as an SRVCC Suspend notification (SRVCC Suspend) Notification)
  • SRVCC Suspend SRVCC Suspend Notification
  • the message is not limited in this embodiment.
  • the PGW sends a suspension response message to the SGW, where the suspension response message is specifically a Suspend Acknowledge message.
  • the SGW sends a suspension response message to the MME, where the suspension response message is specifically a Suspend Acknowledge message.
  • the source MME After receiving the release access bearer response message from the SGW, the source MME initiates a deactivation process, including:
  • the source MME sends a Delete Bearer Command message to the SGW.
  • the Delete Bearer Command message carries the context of other GBR bearers than the voice bearer.
  • the SGW sends a Delete Bearer Command message to the PGW, where the Delete Bearer Command message carries a context of other GBR bearers than the voice bearer; 204c, the PGW sends a Delete Bearer Request message to the SGW; 204d, the SGW sends a Delete Bearer Request message to the MME; 204e, the MME sends a Delete Bearer Response message to the SGW; 204f, The SGW sends a Delete Bearer Response message to the PGW.
  • the foregoing steps 202, 203, and 204 are performed in a fixed order relationship, and the MME may receive the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or the hang from the target side serving GPRS support node. Triggering after the message is received; may also be triggered after receiving the handover request message from the source-side evolved base station or the user equipment context release request message from the source-side evolved base station or the suspend message from the target-side serving GPRS support node, but no Fixed order relationships and interdependencies.
  • the MME sends the release access bearer request message and the suspension request message to the SGW, so that the SGW releases the user of the bearer other than the voice bearer.
  • the surface resources retain the user plane resources of the voice bearer.
  • the SGW and the PGW suspend non-GBR bearers and deactivate other GBR bearers other than the voice bearers to ensure normal voice service.
  • FIG. 2b is a second signaling flowchart of a bearer processing method according to an embodiment of the present invention, as shown in FIG. 2b:
  • the first three steps are completely the same as the steps 201-203 in the embodiment shown in FIG. 2a, so the specific description refers to the description in the embodiment of FIG. 2a. This is not to be said.
  • the SGW After receiving the release access bearer request message sent by the source MME, the SGW initiates a deactivation bearer process to the PGW to deactivate other GBR bearers except the voice bearer.
  • the step specifically includes:
  • the SGW sends a Delete Bearer Command message to the PGW, where the Delete Bearer Command message carries other GBR bearers than the voice bearer. Context.
  • the PGW sends a Delete Bearer Request message to the SGW; 204'c, the SGW sends a Delete Bearer Response message to the PGW; the execution of the foregoing steps 202 and 203 has no fixed order relationship, and may be
  • the MME receives the handover request message from the source-side evolved base station or the user equipment context release request message from the source-side evolved base station or the suspension message from the target-side serving GPRS support node, and triggers simultaneously; and may also receive the source-side evolved base station from the source-side evolved base station.
  • the handover request message or the user equipment context release request message from the source side evolved base station or the suspend message from the target side serving GPRS support node is triggered separately, but there is no fixed order relationship and mutual dependency.
  • the MME sends the release access bearer request message and the suspend request message to the SGW, so that the SGW releases the user plane resources of the bearer other than the voice bearer, and retains the user plane resources of the voice bearer, and the SGW and the PGW suspend the non-GBR bearer and go.
  • the other GBR bearers other than the voice bearer are activated to ensure the normal operation of the voice service of the user.
  • FIG. 3 is a signaling flowchart of a bearer processing method according to another embodiment of the present invention, as shown in FIG. 3:
  • the MME receives a handover request message from the source side eNodeB (Evolved Node B, the evolved base station); or the MME receives the UE context release request message (UE Context Release Request) from the source side eNodB; or MME Receiving a suspend message from the target side SGSN (Serving GPRS Support Node Service GPRS Support Node), the suspend message may be a Suspend Notification message, or may be a Suspend Request extension header Message (for example, SGSN context Request).
  • the source side eNodeB evolved Node B, the evolved base station
  • the MME receives the UE context release request message (UE Context Release Request) from the source side eNodB
  • the suspend message may be a Suspend Notification message, or may be a Suspend Request extension header Message (for example, SGSN context Request).
  • the source side MME initiates a release access bearer process, including:
  • the MME receives the UE context release request message (UE Context Release Request) from the source side eNodB or the MME receives the target side SGSN ( Serving GPRS a hang message of the GPRS support node, the source MME sends a Release Access Bearer Request message to the SGW; the release access request message includes a voice bearer reservation indication or includes a voice bearer.
  • the UE context release request message UE Context Release Request
  • the target side SGSN Serving GPRS a hang message of the GPRS support node
  • the source MME sends a Release Access Bearer Request message to the SGW;
  • the release access request message includes a voice bearer reservation indication or includes a voice bearer.
  • the SGW releases the user plane resources of other bearers except the voice bearer, and retains the user plane of the voice bearer.
  • the SGW sends a Release Access Bearer Response message to the source MME.
  • the source MME initiates a suspension process to the SGW, including:
  • the source side MME sends a suspension request message to the SGW, the SGW suspends the non-GBR bearer, and deactivates other GBR bearers other than the voice bearer;
  • the SGW suspends the non-GBR bearer and deactivates other GBR bearers other than the voice bearer.
  • the specific implementation may include, but is not limited to, the following methods:
  • the SGW may receive and record a local voice bearer reservation indication or include a voice bearer according to step 302a. Carrying radio access bearer information, suspending non-GBR bearers, and deactivating other GBR bearers other than voice bearers; or
  • the SGW may suspend the non-GBR bearer according to the voice bearer reservation indication, and deactivate other GBRs other than the voice bearer; or 3) If the suspend request message includes an identifier of a voice bearer to be reserved, the identifier of the voice bearer that needs to be reserved may be included in the cell "Bearer to be reserve" or "Voice Bearer" for indicating reception The network element device of the information retains the bearer. The embodiment does not limit the name of the cell. The SGW may suspend the non-GBR bearer according to the identifier of the voice bearer that needs to be reserved, and deactivate the voice bearer. Other GBR bearers; or,
  • the suspension request message includes an identifier of a bearer other than the voice bearer that needs to be suspended
  • the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell "Bearer to be suspend" or In the "Bearer Context", the network element device that is used to receive the information suspends the bearer.
  • the name of the cell is not limited, and the SGW may be configured according to the bearer other than the voice bearer that needs to be suspended.
  • the identity hangs non-GBR bearers, and deactivates other GBR bearers other than voice bearers.
  • the suspending the non-GBR bearer may be: retaining the context of the non-GBR bearer, and setting the state of the non-GBR bearer to be suspended; : Delete the context of other GBR bearers other than the voice bearer.
  • the SGW will discard the packet corresponding to the bearer received by the SGW. In this embodiment, the SGW will be normal because the voice bearer remains and is not suspended. Perform IP voice (VoIP) services.
  • VoIP IP voice
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request, or may be a new message, such as an SRVCC Suspend Notification.
  • the message is not limited in this embodiment.
  • the SGW sends a suspension request message to the PGW.
  • the SGW After the SGW receives the suspend request message from the source MME, the SGW sends a suspend request message to the PGW, and the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or needs to be suspended.
  • the PGW can perform the following operations: suspending the non-GBR bearer, and deactivating the voice. Other GBR bearers outside the bearer. For the specific implementation, refer to the corresponding processing performed by the SGW in step 302a, and details are not described herein again.
  • the PGW will discard the packet corresponding to the bearer received by the PGW.
  • the PGW will be normal because the voice bearer remains and is not suspended. Perform IP voice (VoIP) services.
  • VoIP IP voice
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request message, or may be a new message, such as an SRVCC Suspend Notification (SRVCC Suspend Notification)
  • SRVCC Suspend Notification SRVCC Suspend Notification
  • the PGW sends a suspension response message to the SGW, where the suspension response message is specifically a Suspend Acknowledge message.
  • the SGW sends a suspension response message to the MME, where the suspension response message is specifically a Suspend Acknowledge message.
  • the foregoing steps 302 and 303 are performed in a fixed order relationship, and the MME may receive the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or the suspension message from the target side serving GPRS support node. Simultaneously triggering; may also be triggered after receiving a handover request message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspend message from the target side serving GPRS support node, but there is no fixed Order relationships and interdependencies.
  • the MME sends a release access message and a suspension request message to the SGW, so that the SGW releases the voice other than the voice carrier.
  • the user plane resources, the user plane resources of the voice carrier are reserved, and the SGW and the PGW suspend non-GBR bearers and deactivate other GBR bearers other than the voice bearer to ensure normal voice service of the user.
  • FIG. 4a is a signaling flowchart of a bearer processing method according to another embodiment of the present invention, as shown in FIG. 4a: 401.
  • the MME receives a handover request message from a source-side eNodeB (Evolved Node B, evolved base station); or the MME receives a UE Context Release Request message (UE Context Release Request) from the source side eNodB; or MME Receiving a suspend message from the target side SGSN (Serving GPRS Support Node Service GPRS Support Node), the suspend message may be a Suspend Notification message, or may be a Suspend Request extension header Message (for example, SGSN context Request).
  • a source-side eNodeB Evolved Node B, evolved base station
  • UE Context Release Request UE Context Release Request
  • MME Receiving a suspend message from the target side SGSN (Serving GPRS Support Node Service GPRS Support Node)
  • the suspend message may be
  • the source side MME initiates a suspension process, including:
  • the source MME sends a suspend request message to the SGW, and the SGW releases the user plane resources of the bearer other than the voice bearer, retains the user plane resources of the voice bearer, suspends the non-GBR bearer, or causes the SGW to put the voice.
  • the user plane resources of other bearers other than the bearer retain the user plane resources of the voice bearer, and suspend other bearers other than the voice bearer;
  • the SGW releases the user plane resources of the bearer other than the voice bearer, retains the user plane resources of the voice bearer, and suspends the non-GBR bearer; the SGW releases the user plane resources of other bearers other than the voice bearer, and retains the voice.
  • the user plane resources are carried, and other bearers other than the voice bearer are suspended.
  • the specific implementation may include, but is not limited to, the following methods:
  • the SGW may release the user plane resource of the bearer other than the voice bearer according to the voice bearer reservation indication, and retain the user plane resource of the voice bearer.
  • the non-GBR bearer is provided; or the user plane resources of other bearers other than the voice bearer are released, the user plane resources of the voice bearer are reserved, and other bearers other than the voice bearer are suspended; or
  • the identifier of the voice bearer to be reserved may be included in the cell "Bearer to be reserve" or "Voice Bearer" for indicating reception
  • the network element device of the information retains the bearer.
  • the name of the cell is not limited.
  • the SGW may release the user plane resources of other bearers except the voice bearer according to the identifier of the voice bearer that needs to be reserved.
  • the user plane resource carried by the voice hangs the non-GBR bearer; or the user plane resources of other bearers other than the voice bearer are released, and the user plane of the voice bearer is reserved.
  • Source suspend other bearers other than the voice bearer; or,
  • the suspension request message includes an identifier of a bearer other than the voice bearer that needs to be suspended
  • the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell "Bearer to be suspend" or In the "Bearer Context", the network element device that is used to receive the information suspends the bearer.
  • the name of the cell is not limited, and the SGW may be configured according to the bearer other than the voice bearer that needs to be suspended.
  • the user-side resources of the bearer other than the voice bearer are reserved, the user-side resources of the voice bearer are reserved, and the non-GBR bearer is suspended; or the user plane resources of other bearers other than the voice bearer are released, and the user plane resources of the voice bearer are reserved. , suspend other bearers than voice bearers.
  • the user plane resource of the bearer other than the voice bearer may be: the context of the other bearer except the voice bearer is deleted, and the downlink tunnel network element of the bearer other than the voice bearer is deleted (for example, The information about the incoming network element, for example, the tunnel terminal identifier and the address; the reserved voice bearer user plane resource may be: the context of the voice bearer is reserved, and the voice bearer context content is not changed (for example, the voice bearer corresponding to the downlink)
  • the tunneling terminal identifier and the address of the tunneling network element may be: retaining the non-GBR bearer context, and setting the non-GBR bearer state to be suspended; the suspending voice
  • the other bearers other than the bearer may specifically be: retain the context of other bearers other than the voice bearer, and set the state of the other bearers other than the voice bearer to be suspended.
  • the SGW will discard the packet corresponding to the bearer received by the SGW. In this embodiment, the SGW will be normal because the voice bearer remains and is not suspended. Perform IP voice (VoIP) services.
  • VoIP IP voice
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request, or may be a new message, such as an SRVCC Suspend Notification.
  • the message this embodiment does not limit this.
  • the SGW sends a suspension request message to the PGW.
  • the SGW After the SGW receives the suspend request message from the source side MME, the SGW sends a hang to the PGW.
  • a request message the hang request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of a voice bearer to be reserved or an identifier of a bearer other than the voice bearer to be suspended. Operation: Suspend non-GBR bearers and preserve voice bearers in GBR bearers; or suspend other bearers other than voice bearers and preserve voice bearers in GBR bearers.
  • the SGW receives the suspend request message from the source side MME
  • the SGW sends a hang to the PGW.
  • a request message the hang request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of a voice bearer to be reserved or an identifier of a bearer other than the voice bearer to be suspended. Operation: Suspend non-GBR bearers and preserve voice bearers in GBR bearers; or suspend
  • the PGW will discard the packet corresponding to the bearer received by the PGW.
  • the PGW will be normal because the voice bearer remains and is not suspended. Perform IP voice (VoIP) services.
  • VoIP IP voice
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request message, or may be a new message, such as an SRVCC Suspend Notification (SRVCC Suspend Notification)
  • SRVCC Suspend Notification SRVCC Suspend Notification
  • the PGW sends a suspension response message to the SGW, where the suspension response message is specifically a Suspend Acknowledge message.
  • the SGW sends a suspension response message to the MME, where the suspension response message is specifically a Suspend Acknowledge message.
  • the source MME initiates a deactivation bearer process to the SGW to deactivate other GBR bearers except the voice bearer.
  • the step includes:
  • the source side MME sends a Delete Bearer Command message to the SGW;
  • the delete bearer command message carries a context of other GBR bearers other than the voice bearer.
  • the SGW sends a Delete Bearer Command message to the PGW.
  • the Delete Bearer Command message carries a context of other GBR bearers than the voice bearer.
  • 403c the PGW sends a Delete Bearer Request message to the SGW; 403d, the SGW sends a Delete Bearer Request message to the MME; 403e, the MME sends a Delete Bearer Response message to the SGW; 403f, The SGW sends a Delete Bearer Response message to the PGW.
  • the foregoing steps 402 and 403 do not have a fixed order relationship.
  • the MME may receive the handover request message from the source-side evolved base station or the user equipment from the source-side evolved base station.
  • the context release request message or the suspend message from the target side serving GPRS support node is triggered at the same time; or may receive the handover request message from the source side evolved base station or the user equipment context release request message from the source side evolved base station or from the target side
  • the service GPRS support node triggers the suspend message separately, but there is no fixed order relationship and mutual dependencies.
  • the MME sends a suspend request message to the SGW, so that the SGW releases the user plane resources of other bearers other than the voice bearer, and the user retains the voice bearer.
  • the SGW and the PGW hang non-GBR bearers or suspend other bearers other than the voice bearer to ensure normal voice service.
  • FIG. 4b is a second signaling flowchart of a bearer processing method according to another embodiment of the present invention, as shown in FIG. 4b:
  • the first two steps are completely the same as the steps 401 to 402 in the embodiment shown in FIG. 4a, so the specific description refers to the description in the embodiment of FIG. 4a. This is not to be said.
  • step 403 This embodiment only describes step 403 in further detail.
  • the SGW After receiving the suspend request message sent by the source MME, the SGW initiates a deactivation bearer process to the PGW to deactivate other GBR bearers except the voice bearer.
  • the step specifically includes:
  • the SGW sends a Delete Bearer Command message to the PGW; wherein the Delete Bearer Command message carries a context of other GBR bearers than the voice bearer.
  • the PGW sends a Delete Bearer Request message to the SGW; 403, c, and the SGW sends a Delete Bearer Response message to the PGW.
  • the MME sends a suspend request message to the SGW, so that the SGW releases the other user plane resources except the voice bearer, and the method is retained.
  • the user plane resources of the voice, the SGW and the PGW suspend the GBR bearer and deactivate other GBR bearers other than the voice bearer, and retain the voice bearer of the UE, ensuring the normal progress of the voice service of the user.
  • FIG. 5 is a signaling flowchart of a bearer processing method according to another embodiment of the present invention, as shown in FIG. 5:
  • the MME receives a handover requirement message from a source-side eNodeB (Evolved Node B) or the MME receives a UE Context Release Request message from the source side eNodB or the MME receives the Target side SGSN
  • the suspend message may be a Suspend Notification message, or may be a message carrying a Suspend Request extension header (eg, SGSN) Context Request ).
  • GPRS Support Node GPRS Support Node
  • the suspend message may be a Suspend Notification message, or may be a message carrying a Suspend Request extension header (eg, SGSN) Context Request ).
  • the source side MME initiates a suspension process, including:
  • the source MME sends a suspend request message to the SGW, where the SGW releases the user plane resources of the bearer other than the voice bearer, retains the user plane resources of the voice bearer, suspends the non-GBR bearer, and deactivates the voice bearer.
  • Other GBR bearers Other GBR bearers.
  • the SGW releases the user plane resources of the bearer other than the voice bearer, retains the user plane resources of the voice bearer, suspends the non-GBR bearer, and deactivates other GBR bearers other than the voice bearer, and the specific implementation may include but not Limited to the following methods:
  • the SGW may release the user plane resource of the bearer other than the voice bearer according to the voice bearer reservation indication, and retain the user plane resource of the voice bearer. From non-GBR bearers, and deactivate other GBR bearers other than voice bearers; or, 2) If the suspend request message includes an identifier of a voice bearer to be reserved, the identifier of the voice bearer to be reserved may be included in the cell "Bearer to be reserve" or "Voice Bearer" for indicating reception The network element device of the information retains the bearer. In this embodiment, the name of the cell is not limited.
  • the SGW may release the user plane resources of other bearers except the voice bearer according to the identifier of the voice bearer that needs to be reserved.
  • User-side resources carried by voice, suspending non-GBR bearers, and deactivating other GBR bearers other than voice bearers; or
  • the suspension request message includes an identifier of a bearer other than the voice bearer to be suspended
  • the identifier of the bearer other than the voice bearer that needs to be suspended may be included in the cell "Bearer to be suspend" or In the "Bearer Context", the network element device that is used to receive the information suspends the bearer.
  • the name of the cell is not limited, and the SGW may be configured according to the bearer other than the voice bearer that needs to be suspended.
  • the identity of the user plane resources other than the voice bearer is released, the user plane resources of the voice bearer are reserved, the non-GBR bearer is suspended, and other GBR bearers other than the voice bearer are deactivated.
  • the user plane resource of the bearer other than the voice bearer may be: the context of the other bearer except the voice bearer is deleted, and the downlink tunnel network element of the bearer other than the voice bearer is deleted (for example, The information about the incoming network element, for example, the tunnel terminal identifier and the address; the reserved voice bearer user plane resource may be: the context of the voice bearer is reserved, and the voice bearer context content is not changed (for example, the voice bearer corresponding to the downlink)
  • the tunneling terminal identifier and the address of the tunneling network element may be: the hanged non-GBR bearer may be: retaining the context of the non-GBR bearer, and setting the state of the non-GBR bearer to be suspended;
  • the other GBR bearers other than the bearer may specifically be: Delete the context of other GBR bearers other than the voice bearer.
  • the SGW will discard the packet corresponding to the bearer that is received by the SGW.
  • the SGW is normal because the voice bearer remains and is not suspended.
  • IP voice ie VoIP
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request message, or may be a new cancellation message.
  • the SRVCC Suspend Notification message is not limited in this embodiment.
  • the SGW sends a suspension request message to the PGW.
  • the SGW After the SGW receives the suspend request message from the source MME, the SGW sends a suspend request message to the PGW, and the suspend request message sent by the SGW to the PGW includes a voice bearer reservation indication or an identifier of the voice bearer to be reserved or needs to be suspended.
  • the PGW can perform the following operations: suspending the non-GBR bearer, and deactivating other GBR bearers than the voice bearer. For the specific implementation, refer to the corresponding processing performed by the SGW in step 502a, and details are not described herein again.
  • the PGW will discard the packet corresponding to the bearer received by the PGW.
  • the PGW will be normal because the voice bearer remains and is not suspended. Perform IP voice (VoIP) services.
  • VoIP IP voice
  • the suspend request message may be an existing Suspend Notification message or a Modify Bearer Request message, or may be a new message, such as an SRVCC Suspend Notification (SRVCC Suspend Notification).
  • SRVCC Suspend Notification SRVCC Suspend Notification
  • the PGW sends a suspension response message to the SGW, where the suspension response message is specifically a Suspend Acknowledge message.
  • the SGW sends a suspension response message to the MME, where the suspension response message is specifically a Suspend Acknowledge message.
  • the MME sends a suspend request message to the SGW, so that the SGW releases the user plane resources of other bearers except the voice bearer, and retains the voice bearer.
  • the user plane resources, the SGW and the PGW hang non-GBR bearers and deactivate other GBR bearers other than the voice bearer, ensuring the normal progress of the user voice service.
  • FIG. 6 is a first schematic diagram of a mobility management network element according to an embodiment of the present invention.
  • the mobility management network element includes:
  • the receiving module 601 is configured to receive a handover requirement message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node;
  • the sending module 602 is configured to send a release access bearer request message to the SGW, so that the SGW releases the user plane resources of other bearers except the voice bearer, and retains the user plane resources of the voice bearer.
  • FIG. 6b is a second schematic diagram of a mobility management network element according to an embodiment of the present invention. As shown in Figure 6b, on the basis of the embodiment shown in Figure 6a, the mobility management network element further includes:
  • the suspending process initiating module 603 is configured to send a suspend request message to the SGW, and the SGW is triggered to send a suspend request message to the PGW, so that the SGW and the PGW suspend the non-GBR bearer, and the voice bearer is reserved; The SGW and the PGW are caused to suspend other bearers than the voice bearer.
  • Figure 6c is a third schematic diagram of a mobility management network element according to an embodiment of the present invention. As shown in Figure 6c, the mobility management network element further includes:
  • the deactivation process initiation module 604 is configured to initiate a deactivation process to the SGW, so that the SGW deactivates other GBR bearers other than the voice bearer.
  • the bearer processing device sends a release access bearer request message to the SGW, so that the SGW releases the user of the bearer other than the voice bearer in the process of performing the SRVCC in the embodiment of the present invention.
  • the area resources, the user plane resources of the voice bearer are reserved, and the SGW and the PGW hang non-GBR bearers and deactivate other GBR bearers other than the voice bearers, thereby ensuring normal voice service of the user.
  • FIG. 7 is a fourth schematic diagram of a mobility management network element according to an embodiment of the present invention. As shown in FIG. 7, the mobility management network element includes:
  • the receiving module 701 is configured to receive a handover requirement message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node.
  • the sending module 702 is configured to send a release access bearer request message to the SGW, so that the SGW releases the user plane resources of other bearers except the voice bearer, and retains the voice bearer.
  • the suspending process initiating module 703 is configured to send a suspend request message to the SGW, and trigger the SGW to send a suspend request message to the PGW, so that the SGW and the PGW suspend the non-GBR bearer, retain the voice bearer, and go Activate other GBR bearers other than voice bearers.
  • the bearer processing device sends a release access bearer request message to the SGW, so that the SGW releases the user plane resources of other bearers other than the voice bearer.
  • the user plane resources of the voice bearer are reserved, and the SGW and the PGW hang non-GBR bearers and deactivate other GBR bearers other than the voice bearer to ensure normal voice service.
  • FIG. 8 is a fifth schematic diagram of a mobility management network element according to an embodiment of the present invention. As shown in FIG. 8, the mobility management network element includes:
  • the receiving module 801 is configured to receive a handover request message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node;
  • the sending module 802 is configured to send a suspend request message to the SGW, and trigger the SGW to send a suspend request message to the PGW, so that the SGW releases user plane resources of other bearers except the voice bearer, and retains the user plane of the voice bearer. And causing the SGW and the PGW to suspend the non-GBR bearer; or, in turn, causing the SGW and the PGW to suspend other bearers than the voice bearer.
  • FIG 8b is a sixth schematic diagram of a mobility management network element according to an embodiment of the present invention. As shown in Figure 8a, the mobile management network element further includes:
  • the deactivation process initiation module 803 is configured to initiate a deactivation process to the SGW, so that the SGW deactivates other GBR bearers except the voice bearer.
  • FIG. 9 is a seventh schematic diagram of a mobility management network element according to an embodiment of the present invention. As shown in FIG. 9, the mobility management network element includes:
  • the receiving module 901 is configured to receive a handover requirement message from the source side evolved base station or a user equipment context release request message from the source side evolved base station or a suspension message from the target side serving GPRS support node;
  • the sending module 902 is configured to send a suspension request message to the SGW, so that the SGW releases the user plane resources of other bearers except the voice bearer, retains the user plane resources of the voice bearer, suspends the non-GBR bearer, and deactivates the voice.
  • the SGW For suspending the request message to the SGW, the SGW is triggered to send a suspension request message to the PGW, so that the SGW releases the user plane resources of other bearers except the voice bearer, and retains the user plane resources of the voice bearer, thereby making the PGW Suspend non-GBR bearers and deactivate other GBR bearers other than voice bearers.
  • the bearer processing device sends a suspend request message to the SGW, so that the SGW releases the user plane resources of other bearers other than the voice bearer, and retains the voice.
  • the user plane resources are carried, and the SGW and the PGW hang non-GBR bearers and deactivate other GBR bearers other than the voice bearer to ensure normal voice service.
  • FIG. 10a is a first schematic diagram of a bearer processing system according to an embodiment of the present invention. As shown in FIG. 10a, the load processing system includes:
  • a mobility management network element 1001 configured to send a release access bearer request message or a pending request message to the SGW;
  • the serving gateway 1002 is configured to receive a release access bearer request message or a suspend request message from the mobility management network element, perform user plane resources of other bearers other than the voice bearer, and retain the user plane resources of the voice bearer.
  • the non-GBR bears or suspends other bearers other than the voice bearer, and deactivates other GBR bearers other than the voice bearer.
  • FIG. 10b is a second schematic diagram of a bearer processing system according to an embodiment of the present invention, as shown in FIG. 10b. It is shown that, on the basis of FIG. 10a, the bearer processing system further comprises:
  • the packet data network gateway 1003 is configured to receive a suspend request message from the SGW, perform a non-GBR bearer or suspend other bearers other than the voice bearer, and activate other GBR bearers other than the voice bearer.
  • the bearer processing apparatus sends a release access bearer request message or a suspend request message to the SGW, so that the SGW releases the voice bearer other than the voice bearer in the embodiment of the present invention.
  • the user plane resources of the bearer are reserved, and the user plane resources of the voice bearer are reserved, so that the SGW and the PGW hang the non-GBR bearer and deactivate other GBR bearers other than the voice bearer, thereby ensuring the normal operation of the voice service of the user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种承载处理方法、 系统及移动管理网元
技术领域
本发明涉及通信技术领域， 尤其涉及一种承载处理方法、 系统及移动管理 网元。 背景技术
目前， 运营商的很多业务都运行在 GPRS ( General Packet Radio Service , 通用分组无线业务 ) /UMTS ( Universal Mobile Telecommunications System, 通 用移动通信系统）的 CS ( Circuit Switched, 电路交换）域中， SRVCC ( Single Radio Voice Call Continuity, 单一无线语音呼叫连续性）技术作为 IMS ( IP Multimedia Subsystem, IP多媒体子系统）语音部署初期的语音连续性方案， 可以为用户设备提供从 E-UTRAN ( Evolved UMTS Territorial Radio Access Network,演进的 UMTS陆地无线接入网）到 UTRAN(陆地无线接入网 , UMTS Territorial Radio Access Network UMTS ) /GERAN ( GSM EDGE Radio Access Network, GSM EDGE无线接入网） 的无缝切换， 得到了运营商持续的关注。 目前的 SRVCC性能增强项目研究， 旨在提高 SRVCC的切换性能， 尽量避免 切换过程中中断时延过大的场景出现。
其中， 使用本地锚定的 SRVCC增强方案是现有 SRVCC增强方案中的主 要推荐方案之一。 在使用本地锚定的 SRVCC增强方案中， UE执行 CSFB ( CS Fallback, 电路回落）联合附着， 并通过 MSC ( Mobile Switch Center, 移动交 换中心） /MGW ( Media Gate Way, 媒体网关）注册到 IMS , 并且在 SRVCC切 换过程中和 SCCAS ( Service Centralization and Continuity Application Server, 业务集中及连续应用服务器）建立 SIP ( Session Initiated Protocol, 会话初始协 议）会话， 在 SRVCC切换后 MSC/MGW和 SGW ( Serving Gateway, 服务网 关）建立 GTP ( GPRS隧道协议， GPRS Tunneling Protocol )通道， 用于传递 上下行的语音数据。 对于 UE ( User Equipment, 用户设备 )在 E-UTRAN执行 SRVCC切换到 不支持双向传输模式的 GERAN的场景（即 SRVCC from E-UTRAN to GERAN without DTM support ),在现有使用本地锚定的 SRVCC增强方案的技术方案中 , 一旦 SGW/PGW ( Packet Data Network Gateway, 分组数据网络网关）接收到 挂起消息后， SGW/PGW将挂起所述 UE的非 GBR ( Guaranteed Bit Rate , 保 证比特速率） 承载并去激活包含语音承载的 GBR 承载， 这样使得所述 SGW/PGW将丢弃接收到的所述 UE的包含语音业务的所有数据报文 , 使得此 时通过上述网关设备无法正常进行语音业务。 发明内容
有鉴于此， 本发明实施例提供一种承载处理方法、 系统及移动管理网元， 使得在 SRVCC过程中， 网关设备不挂起也不去激活用户设备的语音承载， 保 证了用户语音业务的正常进行。
本发明的实施例釆用如下技术方案：
一种承载处理方法， 包括：
在执行单一无线语音呼叫连续性流程中 ,接收来自源侧演进基站的切换需 求消息或者来自源侧演进基站的用户设备上下文释放请求消息或者来自目标 侧服务 GPRS支持节点的挂起消息；
向服务网关发送请求消息， 以使所述服务网关释放语音承载之外的其他承 载的用户面资源， 保留语音承载的用户面资源。
一种移动管理网元， 包括：
接收模块， 用于接收来自源侧演进基站的切换需求消息或者来自源侧演进 基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点的挂 起消息；
发送模块， 用于向服务网关发送释放接入承载请求消息， 以使所述服务网 关释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源。 一种移动管理网元， 包括：
接收模块， 用于接收来自源侧演进基站的切换需求消息或者来自源侧演进 基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点的挂 起消息；
发送模块， 用于向服务网关发送挂起请求消息 , 触发所述服务网关向分组 数据网络网关发送挂起请求消息 , 以使所述服务网关释放语音承载之外的其他 承载的用户面资源， 保留语音承载的用户面资源；
进而使得所述服务网关和分组数据网络网关挂起非 GBR承载； 或者进而 使得所述服务网关和分组数据网络网关挂起语音承载之外的其他承载。
一种移动管理网元， 包括：
接收模块， 用于接收来自源侧演进基站的切换需求消息或者来自源侧演进 基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点的挂 起消息；
发送模块， 用于向服务网关发送挂起请求消息， 以使所述服务网关释放语 音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR承载； 或者
用于向服务网关发送挂起请求消息， 触发所述服务网关向分组数据网络网 关发送挂起请求消息 , 以使所述服务网关释放语音承载之外的其他承载的用户 面资源，保留语音承载的用户面资源；进而使得分组数据网络网关挂起非 GBR 承载， 以及去激活语音承载之外的其他 GBR承载。
一种承载处理系统， 包括：
移动管理网元， 用于向服务网关发送释放接入承载请求消息或者挂起请求 消息；
服务网关， 用于接收来自所述移动管理网元的释放接入承载请求消息或者 挂起请求消息， 执行释放语音承载之外的其他承载的用户面资源， 保留语音承 载的用户面资源， 挂起非 GBR承载或者挂起语音承载之外的其他承载， 去激 活语音承载之外的其他 GBR承载。
采用本发明实施例提供的承载处理方法、系统及移动管理网元，在 SRVCC 流程中， MME ( Mobility Management Entity, 移动管理实体 )通过向 SGW发 送释放接入承载请求消息或者挂起请求消息， 使得 SGW释放语音承载之外的 其他承载的用户面资源，保留语音承载的用户面资源， 进而使得 SGW和 PGW 挂起非 GBR承载和去激活语音承载之外的其他 GBR承载，保证了用户语音业 务的正常进行。 附图说明
图 1为本发明实施例提供的一种承载处理方法的流程图；
图 2a为本发明实施例提供的一种承载处理方法的信令流程图；
图 2b为本发明实施例提供的一种承载处理方法的第二信令流程图； 图 3为本发明另一实施例提供的一种承载处理方法的信令流程图； 图 4a为本发明又一实施例提供的一种承载处理方法的信令流程图； 图 4b为本发明又一实施例提供的一种承载处理方法的第二信令流程 图 5为本发明再一实施例提供的一种承载处理方法的信令流程图； 图 6a为本发明实施例提供的一种移动管理网元的第一示意图；
图 6b为本发明实施例提供的一种移动管理网元的第二示意图；
图 6c为本发明实施例提供的一种移动管理网元的第三示意图；
图 7为本发明实施例提供的一种移动管理网元的第四示意图；
图 8a为本发明实施例提供的一种移动管理网元的第五示意图；
图 8b为本发明实施例提供的一种移动管理网元的第六示意图；
图 9为本发明实施例提供的一种移动管理网元的第七示意图；
图 10a为本发明实施例提供的一种承载处理系统的第一示意图；
图 10b为本发明实施例提供的一种承载处理系统的第二示意图。 具体实施方式
下面将结合本发明实施例中的附图 ,对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
本发明以下所有实施例均基于 SRVCC切换方案的场景， 即均为使用本地 SGW/PGW作为锚定点传输 VoIP ( Voice over Internet Protocol, 互联网协议语 音技术）业务的方案， 例如： 使用本地锚定的 SRVCC增强方案。 在后续的实 施例中都是基于对上述场景的承载处理方法的改进的描述， 故在各实施例中对 此方案场景不再做重复性赘述。
在上述场景和本发明以下所有实施例中 , UE的承载被分为 GBR承载和非 GBR承载两类。 其中， GBR承载指的是具有保证比特率的承载， 包括： 语音 承载和语音承载以外的其他 GBR承载。 MME/SGW/PGW可以基于业务质量等 级标识（QoS Class Identifier, QCI ) 的具体数值对上述语音承载、 非 GBR承 载和 GBR^ 载进行识别， 例如， 若^ ^载中只有一个 载的 QCI值为 1 , 则该 承载可以被识别为语音承载； 或者， 例如若一个承载的 QCI值为 5〜9时， 该承 载被识别为非 GBR承载。 MME/SGW/PGW可以根据上述 QCI数值以及接收 到的消息中包含的其他指示信元对承载做相应的挂起、 去激活、 保留等处理。
图 1为本发明实施例提供的一种承载处理方法的流程图， 如图 1所示： 步驟 101 , 在执行 SRVCC流程中， 接收来自源侧演进基站的切换需求消 息或者来自源侧演进基站的用户设备上下文释放请求消息或者来自目标侧服 务 GPRS支持节点的挂起消息；
步驟 102, 向服务网关发送请求消息， 以使所述服务网关释放语音承载之 外的其他承载的用户面资源， 保留语音承载的用户面资源。
MME根据接收到的步驟 101中所述信息， 通过如下四种方式实现释放语 音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源， 并对承载 执行相应的挂起和去激活处理处理 , 具体请见以下描述：
方式一：
A ) MME向 SGW发送释放接入承载请求消息， 所述释放接入承载请求消 息中包含语音承载保留指示或者包含语音承载之外的其他承载的无线接入承 载信息（非 GBR承载以及语音承载以外的 GBR承载的无线接入承载信息）， 以使所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音承载的 用户面资源并接收来自 SGW的释放接入承载响应消息；
B ) MME向 SGW发送挂起请求消息， 所述 SGW挂起非 GBR承载，保留 GBR承载中的语音承载； 或者以使所述 SGW挂起语音承载之外的其他承载 , 保留 GBR承载中的语音承载。
其中， 所述 SGW接收 MME发送的挂起请求消息之后 , SGW向 PGW发 送挂起请求消息， 所述 SGW向 PGW发送的挂起请求消息中包含语音承载保 留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他 承载的标识， 所述 PGW挂起非 GBR承载， 保留 GBR承载中的语音承载； 或 者所述 PGW挂起语音承载之外的其他承载，保留 GBR承载中的语音承载。所 述需要保留的语音 载的标识可以包含在信元 "Bearer to be reserve"或 "Voice Bearer" 中， 用于指示接收该信息的网元设备保留所述承载， 本实施例不限制 该信元的名称； 所述需要挂起的语音承载以外的其他承载的标识可以包含在信 元 "Bearer to be suspend" 或 "Bearer Context" 中， 用于指示接收该信息的网 元设备挂起所述承载 , 本实施例不限制该信元的名称。
SGW接收来自 PGW的挂起响应消息 , MME接收来自 SGW的挂起响应 消息， 完成挂起流程。
C ) MME向 SGW发送删除承载命令消息， 发起去激活流程， SGW去激 活语音承载之外的其他 GBR承载。 另外， MME还可以在接收到来自 SGW的 释放接入承载响应消息之后发起该去激活流程。
上述 A、 B、 C三个步骤的执行没有固定顺序关系， 可以在 MME接收来 自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文释 放请求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也可 以在接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设 备上下文释放请求消息或者来自目标侧服务 GPRS支持节点的挂起消息后分别 触发， 但没有固定的顺序关系以及相互依赖关系。
可选择的， 上述 C所述去激活流程还可以通过如下方式实现： SGW接收 到来自 MME的所述释放接入承载请求消息之后， 触发 SGW向 PGW发起去 激活流程， PGW去激活语音承载之外的其他 GBR承载。
方式二：
A ) MME向 SGW发送释放接入承载请求消息， 所述释放接入承载请求消 息中包含语音承载保留指示或者包含语音承载之外的其他承载的无线接入承 载信息（非 GBR承载以及语音承载以外的 GBR承载的无线接入承载信息）， 所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户 面资源， 并接收来自 SGW的释放接入承载响应消息；
B ) MME向 SGW发送挂起请求消息， 所述 SGW挂起非 GBR承载，保留 GBR承载中的语音承载， 以及去激活语音承载之外的其他 GBR承载。
其中， 所述 SGW接收 MME发送的挂起请求消息之后， SGW向 PGW发 送挂起请求消息， 所述 SGW向 PGW发送的挂起请求消息中包含语音承载保 留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他 承载的标识， 所述 PGW挂起非 GBR承载以及保留 GBR承载中的语音承载， 以及去激活语音承载之外的其他 GBR承载。 所述需要保留的语音承载的标识 可以包含在信元 "Bearer to be reserve"或 "Voice Bearer" 中, 用于指示接收该 信息的网元设备保留所述承载， 本实施例不限制该信元的名称； 所述需要挂起 的语音 7 载以外的其他 载的标识可以包含在信元 "Bearer to be suspend" 或 "Bearer Context" 中， 用于指示接收该信息的网元设备挂起所述承载， 本实施 例不限制该信元的名称。 SGW接收来自 PGW的挂起响应消息， MME接收来自 SGW的挂起响应 消息， 完成挂起流程以及对承载的其他处理。
上述 A、 B两个步驟的执行没有固定顺序关系， 可以在 MME接收来自源 侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文释放请 求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也可以在 接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上 下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂起消息后分别触 发， 但没有固定的顺序关系以及相互依赖关系。
方式三：
A ) MME向 SGW发送挂起请求消息 , 所述挂起请求消息中包含语音 载 保留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其 他承载的标识；
所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音承载的 用户面资源， 挂起非 GBR承载以及保留 GBR承载中的语音承载； 或者所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资 源， 挂起语音承载之外的其他承载以及保留 GBR承载中的语音承载。
其中， 所述 SGW接收 MME发送的挂起请求消息之后， SGW向 PGW发 送挂起请求消息， 所述 SGW向 PGW发送的挂起请求消息中包含语音承载保 留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他 承载的标识， 所述 PGW挂起非 GBR承载， 保留 GBR承载中的语音承载； 或 者所述 PGW挂起语音承载之外的其他承载 , 保留 GBR承载中的语音承载。
以上所述的需要保留的语音承载的标识可以包含在信元 "Bearer to be reserve"或 "Voice Bearer"中， 用于指示接收该信息的网元设备保留所述承载， 本实施例不限制该信元的名称； 所述需要挂起的语音承载以外的其他承载的标 识可以包含在信元 "Bearer to be suspend" 或 "Bearer Context" 中， 用于指示 接收该信息的网元设备挂起所述承载， 本实施例不限制该信元的名称。 SGW接收来自 PGW的挂起响应消息， MME接收来自 SGW的挂起响应 消息， 完成挂起流程以及对承载的其他处理。
B ) MME向 SGW发送删除承载命令消息， 发起去激活流程， 以使 SGW 去激活语音承载之外的其他 GBR承载。
上述 A、 B两个步驟的执行没有固定顺序关系， 可以在 MME接收来自源 侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文释放请 求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也可以在 接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上 下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂起消息后分别触 发， 但没有固定的顺序关系以及相互依赖关系。
可选择的， 上述去激活流程还可以通过如下方式实现： SGW接收到来自 MME的所述挂起请求消息之后， 触发 SGW向 PGW发起去激活流程， PGW 去激活语音承载之外的其他 GBR承载。
方式四：
A ) MME向 SGW发送挂起请求消息， 所述挂起请求消息中包含语音 7 载 保留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其 他承载的标识； 所述 SGW释放语音承载之外的其他承载的用户面资源， 保留 语音承载的用户面资源； 所述 SGW挂起非 GBR承载、 保留 GBR承载中的语 音承载以及去激活语音承载之外的其他 GBR承载。
其中， 所述 SGW接收 MME发送的挂起请求消息之后 , SGW向 PGW发 送挂起请求消息， 所述 SGW向 PGW发送的挂起请求消息中包含语音承载保 留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他 承载的标识， 所述 PGW挂起非 GBR承载、 保留 GBR承载中的语音承载以及 去激活语音承载之外的其他 GBR承载。
以上所述的需要保留的语音承载的标识可以包含在信元 "Bearer to be reserve"或 "Voice Bearer"中， 用于指示接收该信息的网元设备保留所述承载， 本实施例不限制该信元的名称； 所述需要挂起的语音承载以外的其他承载的标 识可以包含在信元 "Bearer to be suspend" 或 "Bearer Context" 中, 用于指示 接收该信息的网元设备挂起所述承载 , 本实施例不限制该信元的名称。
SGW接收来自 PGW的挂起响应消息， MME接收来自 SGW的挂起响应 消息， 完成挂起流程以及对承载的其他处理。
在上述四种方式中， 所述保留 GBR承载中的语音承载可以为： 保留所述 语音承载的上下文， 不改变所述语音承载上下文内容（例如 MBR等）且不将 所述语音承载挂起； 所述挂起非 GBR承载可以为： 保留所述非 GBR承载的上 下文， 并将所述非 GBR承载的状态置为挂起； 所述挂起语音承载之外的其他 承载可以是： 保留所述语音承载之外的其他承载的上下文， 并将所述语音承载 之外的其他承载的状态置为挂起； 所述去激活语音承载之外的其他 GBR承载 可以为： 删除所述语音承载之外的其他 GBR承载的上下文。其中， 若承载（例 如非 GBR承载）被挂起， 则 SGW/PGW将丢弃其所接收的所述承载对应的报 文， 本实施例中， 由于语音承载保留且未被挂起， 则 SGW/PGW将正常的进行 IP语音（即 VoIP )业务。
采用本发明实施例步驟 101〜102所述的方法，在执行 SRVCC流程中 , MME 通过向 SGW发送请求消息， 使得 SGW释放语音承载之外的其他承载的用户 面资源， 保留语音承载的用户面资源， SGW和 PGW挂起非 GBR承载和去激 活语音承载之外的其他 GBR承载， 保证了用户语音业务的正常进行。
图 2a为本发明实施例提供的一种承载处理方法的信令流程图 , 如图 2a所 示：
201 ,在执行 SRVCC流程中， MME接收到来自源侧 eNodeB( Evolved Node B, 演进基站） 的切换需求消息或者 MME接收来自源侧 eNodB的 UE上下文 释放请求消息（ UE Context Release Request )或者 MME接收来自目标侧 SGSN ( Serving GPRS Support Node服务 GPRS支持节点）的挂起消息， 所述挂起消 息可以是挂起通知 （Suspend Notification ) 消息， 或者可以是携带挂起请求 ( Suspend Request )扩展头部的消息（例如 SGSN context Request )。
202, 源侧 MME发起释放接入承载流程， 包括：
202a, 根据 201中接收到的源侧 eNodeB ( Evolved Node B , 演进基站）的 切换需求消息或者 MME接收来自源侧 eNodB的 UE上下文释放请求消息（ UE Context Release Request )或者 MME接收来自目标侧 SGSN ( Serving GPRS Support Node服务 GPRS支持节点） 的挂起消息， 源侧 MME向 SGW发送释 放接入 ? 载请求（ Release Access Bearer Request ) 消息； 所述释放接入 ? 载请 求消息中包含语音承载保留指示或者包含语音承载之外的其他承载的无线接 入承载信息（非 GBR承载以及语音承载以外的 GBR承载的无线接入承载信 息）， SGW释放除了语音承载之外的其他承载的用户面资源， 保留语音承载的 用户面资源；
其中， 所述释放除了语音承载之外的其他承载的用户面资源具体可以是： 保留所述语音承载之外的其他承载的上下文，删除语音承载之外的其他承载的 下行隧道网元（例如接入网元）的相关信息， 例如隧道终端标识和地址； 所述 保留语音承载用户面资源具体可以是： 保留所述语音承载的上下文， 不改变所 述语音 7|载上下文内容（例如语音 7|载对应的下行隧道网元的隧道终端标识和 地址）。
202b、 SGW向源侧 MME发送释放接入承载响应 （ Release Access Bearer Response ) 消息。
203, 源侧 MME向 SGW发起挂起流程， 包括：
203a, 源侧 MME向 SGW发送挂起请求消息 , 所述 SGW挂起非 GBR承 载； 或者源侧 MME向 SGW发送挂起请求消息， 所述 SGW挂起语音 载之 外的其他承载；
其中，所述 SGW挂起非 GBR承载或者挂起语音承载之外的其他承载，具 体实现可以包括但不限于以下方法：
1 )若所述挂起请求消息是未扩展的挂起通知（ Suspend Notification )消息 时，则所述 SGW可以根据步驟 202a中接收并记录在本地的语音承载保留指示 或者包含语音承载之外的其他承载的无线接入承载信息， 挂起非 GBR承载或 者挂起语音承载之外的其他承载； 或者，
2 )若所述挂起请求消息包含语音承载保留指示消息时，所述 SGW可以根 据所述语音承载保留指示挂起非 GBR承载或者挂起语音承载之外的其他承载； 或者，
3 )若所述挂起请求消息包含需要保留的语音承载的标识时， 所述需要保 留的语音^载的标。、可以包含在信元 "Bearer to be reserve" 或 "Voice Bearer" 中， 用于指示接收该信息的网元设备保留所述承载 , 本实施例不限制该信元的 名称，所述 SGW可以根据所述需要保留的语音承载的标识挂起非 GBR承载或 者挂起语音承载之外的其他承载； 或者，
4 )若所述挂起请求消息包含需要挂起的语音承载以外的其他承载的标识 时 ,所述需要挂起的语音承载以外的其他承载的标识可以包含在信元 "Bearer to be suspend" 或 "Bearer Context" 中， 用于指示接收该信息的网元设备挂起所 述承载， 本实施例不限制该信元的名称， 所述 SGW可以根据所述需要挂起的 语音承载以外的其他承载的标识挂起非 GBR承载或者挂起语音承载之外的其 他承载。
其中，所述挂起非 GBR承载具体可以是:保留所述非 GBR承载的上下文， 并将所述非 GBR承载的状态置为挂起； 所述挂起语音承载之外的其他承载具 体可以是： 保留所述语音承载之外的其他承载的上下文， 并将所述语音承载之 外的其他承载的状态置为挂起。 其中， 若承载（例如非 GBR承载）被挂起， 则 SGW将丟弃其所接收的所述承载对应的报文， 本实施例中， 由于语音承载 保留且未被挂起， 则 SGW将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改承载请求（ Modify Bearer Request ), 或者可以是新的消息， 例 如 SRVCC挂起通知 ( SRVCC Suspend Notification ) 消息， 本实施例对此不係: 限制。
203b , SGW向 PGW发送挂起请求消息；
SGW接收来自源侧 MME的挂起请求消息之后 , SGW向 PGW发送挂起 请求消息， 所述 SGW向 PGW发送的挂起请求消息包含语音承载保留指示或 者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承载的标 识， 此时， 所述 PGW可以进行如下操作： 挂起非 GBR承载； 或者挂起语音承 载之外的其他承载。 其具体实现可以参见步驟 203a中 SGW所作的相应处理， 此处不再赘述。
其中， 若承载（例如非 GBR承载）被挂起， 则 PGW将丢弃其所接收的 所述承载对应的报文， 本实施例中， 由于语音承载保留且未被挂起， 则 PGW 将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改 7 载请求（Modify Bearer Request ) 消息， 或者可以是新的消 息， 例如 SRVCC挂起通知（ SRVCC Suspend Notification ) 消息， 本实施例对 此不做限制。
203c, PGW向 SGW发送挂起响应消息； 其中， 所述挂起响应消息具体为 挂起应答 ( Suspend Acknowledge ) 消息。
203d, SGW向 MME发送挂起响应消息； 其中， 所述挂起响应消息具体 为挂起应答 ( Suspend Acknowledge ) 消息。
204, 源侧 MME接收到来自 SGW的释放接入承载响应消息之后 , 发起去 激活流程， 包括：
204a, 源侧 MME向 SGW发送删除承载命令 ( Delete Bearer Command ) 消息； 其中， 所述删除承载命令消息中携带语音承载之外的其他 GBR承载的 上下文。
204b, SGW向 PGW发送删除承载命令 ( Delete Bearer Command ) 消息； 其中，所述删除承载命令消息中携带语音承载之外的其他 GBR承载的上下文； 204c, PGW向 SGW发送删除承载请求 ( Delete Bearer Request ) 消息； 204d, SGW向 MME发送删除承载请求（ Delete Bearer Request ) 消息； 204e, MME向 SGW发送删除 载响应 （ Delete Bearer Response ) 消息； 204f, SGW向 PGW发送删除 7|载响应 （ Delete Bearer Response ) 消息。 上述步驟 202、 203和 204的执行没有固定顺序关系， 可以在 MME接收 来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文 释放请求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也 可以在接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户 设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点的挂起消息后分 别触发， 但没有固定的顺序关系以及相互依赖关系。
采用本发明实施例步驟 201〜204所述的方法， 在执行 SRVCC的流程中 , MME通过向 SGW发送释放接入承载请求消息和挂起请求消息，使得 SGW释 放语音承载之外的其他承载的用户面资源，保留语音承载的用户面资源， SGW 和 PGW挂起非 GBR承载和去激活语音承载之外的其他 GBR承载， 保证了用 户语音业务的正常进行。
图 2b为本发明实施例提供的一种承载处理方法的第二信令流程图， 如图 2b所示：
本实施例中， 与图 2a所示的实施例相比较， 前三个步驟与图 2a所述实施 例中的步驟 201〜203完全相同， 故具体描述请参照图 2a实施例中的叙述， 在 此不做赞述。
在此本实施例只对步驟 204 故进一步详细描述。
204， , SGW在接收到源侧 MME发送的释放接入承载请求消息之后 , SGW 向 PGW发起去激活承载流程， 以去激活除语音承载之外的其他 GBR承载。其 中， 该步骤具体包括：
204'a, SGW向 PGW发送删除承载命令 ( Delete Bearer Command )消息； 其中， 所述删除承载命令消息中携带除语音承载之外的其他 GBR承载的 上下文。
204'b, PGW向 SGW发送删除承载请求（ Delete Bearer Request ) 消息； 204'c, SGW向 PGW发送删除 载响应 （ Delete Bearer Response ) 消息； 上述步骤 202、 203的执行没有固定顺序关系， 可以在 MME接收来自源 侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文释放请 求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也可以在 接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上 下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂起消息后分别触 发， 但没有固定的顺序关系以及相互依赖关系。
釆用本发明实施例步驟 201〜204，所述的方法 , 在执行 SRVCC的流程中 ,
MME通过向 SGW发送释放接入承载请求消息和挂起请求消息，使得 SGW释 放语音承载之外的其他承载的用户面资源，保留语音承载的用户面资源， SGW 和 PGW挂起非 GBR承载和去激活语音承载之外的其他 GBR承载， 保证了用 户语音业务的正常进行。
图 3为本发明另一实施例提供的一种承载处理方法的信令流程图， 如图 3 所示：
301，在执行 SRVCC流程中， MME接收到来自源侧 eNodeB( Evolved Node B, 演进基站） 的切换需求消息； 或者 MME接收来自源侧 eNodB的 UE上下 文释放请求消息（UE Context Release Request ); 或者 MME接收来自目标侧 SGSN ( Serving GPRS Support Node服务 GPRS支持节点）的挂起消息， 所述 挂起消息可以是挂起通知 （ Suspend Notification ) 消息， 或者可以是携带挂起 请求（ Suspend Request )扩展头部的消息（例如 SGSN context Request )。
302, 源侧 MME发起释放接入承载流程， 包括：
302a, 根据 301中接收到的源侧 eNodeB ( Evolved Node B , 演进基站）的 切换需求消息或者 MME接收来自源侧 eNodB的 UE上下文释放请求消息（ UE Context Release Request )或者 MME接收来自目标侧 SGSN ( Serving GPRS Support Node服务 GPRS支持节点） 的挂起消息， 源侧 MME向 SGW发送释 放接入 载请求 ( Release Access Bearer Request ) 消息； 所述释放接入 载请 求消息中包含语音承载保留指示或者包含语音承载之外的其他承载的无线接 入承载信息（非 GBR承载以及语音承载以外的 GBR承载的无线接入承载信 息）， SGW释放除了语音承载之外的其他承载的用户面资源， 保留语音承载的 用户面资源；
其中， 所述释放除了语音承载之外的其他承载的用户面资源具体可以是： 保留所述语音承载之外的其他承载的上下文，删除语音承载之外的其他承载的 下行隧道网元（例如接入网元）的相关信息， 例如隧道终端标识和地址； 所述 保留语音承载用户面资源具体可以是： 保留所述语音承载的上下文， 不改变所 述语音承载上下文内容（例如语音承载对应的下行隧道网元的隧道终端标识和 地址）。
302b、 SGW向源侧 MME发送释放接入承载响应 （ Release Access Bearer Response ) 消息。
303, 源侧 MME向 SGW发起挂起流程， 包括：
303a, 源侧 MME向 SGW发送挂起请求消息 , 所述 SGW挂起非 GBR承 载， 以及去激活语音承载之外的其他 GBR承载；
其中 ,所述 SGW挂起非 GBR承载 ,以及去激活语音承载之外的其他 GBR 承载， 具体实现可以包括但不限于以下方法：
1 )若所述挂起请求消息是未扩展的挂起通知（ Suspend Notification )消息 时，则所述 SGW可以根据步驟 302a中接收并记录在本地的语音承载保留指示 或者包含语音承载之外的其他承载的无线接入承载信息， 挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR承载； 或者，
2 )若所述挂起请求消息包含语音承载保留指示消息时，所述 SGW可以根 据所述语音承载保留指示挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR^ 载； 或者， 3 )若所述挂起请求消息包含需要保留的语音承载的标识时， 所述需要保 留的语音 载的标识可以包含在信元 "Bearer to be reserve" 或 "Voice Bearer" 中， 用于指示接收该信息的网元设备保留所述承载， 本实施例不限制该信元的 名称， 所述 SGW可以根据所述需要保留的语音承载的标识挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR承载； 或者，
4 )若所述挂起请求消息包含需要挂起的语音承载以外的其他承载的标识 时 ,所述需要挂起的语音承载以外的其他承载的标识可以包含在信元 "Bearer to be suspend" 或 "Bearer Context" 中， 用于指示接收该信息的网元设备挂起所 述承载， 本实施例不限制该信元的名称， 所述 SGW可以根据所述需要挂起的 语音承载以外的其他承载的标识挂起非 GBR承载， 以及去激活语音承载之外 的其他 GBR承载。
其中，所述挂起非 GBR承载具体可以是:保留所述非 GBR承载的上下文， 并将所述非 GBR承载的状态置为挂起；所述去激活非语音承载的其他 GBR承 载具体可以是： 删除所述语音承载之外的其他 GBR承载的上下文。
其中， 若承载（例如非 GBR承载）被挂起， 则 SGW将丢弃其所接收的 所述承载对应的报文， 本实施例中， 由于语音承载保留且未被挂起， 则 SGW 将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改 载请求（ Modify Bearer Request ), 或者可以是新的消息， 例 如 SRVCC挂起通知（ SRVCC Suspend Notification ) 消息， 本实施例对此不做 限制。
302b , SGW向 PGW发送挂起请求消息；
SGW接收来自源侧 MME的挂起请求消息之后 , SGW向 PGW发送挂起 请求消息， 所述 SGW向 PGW发送的挂起请求消息包含语音承载保留指示或 者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承载的标 识， 此时， 所述 PGW可以进行如下操作： 挂起非 GBR承载， 以及去激活语音 承载之外的其他 GBR承载。 其具体实现可以参见步驟 302a中 SGW所作的相 应处理， 此处不再赘述。
其中， 若承载（例如非 GBR承载）被挂起， 则 PGW将丢弃其所接收的 所述承载对应的报文， 本实施例中， 由于语音承载保留且未被挂起， 则 PGW 将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改 载请求（Modify Bearer Request ) 消息， 或者可以是新的消 息， 例如 SRVCC挂起通知（ SRVCC Suspend Notification ) 消息， 本实施例对 此不做限制。
303c, PGW向 SGW发送挂起响应消息； 其中， 所述挂起响应消息具体为 挂起应答 ( Suspend Acknowledge ) 消息。
303d, SGW向 MME发送挂起响应消息； 其中， 所述挂起响应消息具体 为挂起应答 ( Suspend Acknowledge ) 消息。
上述步驟 302、 303的执行没有固定顺序关系， 可以在 MME接收来自源 侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文释放请 求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也可以在 接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上 下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂起消息后分别触 发， 但没有固定的顺序关系以及相互依赖关系。
采用本发明实施例步驟 301-303所述的方法，在执行 SRVCC流程中 , MME 通过向 SGW发送释放接入 7|载请求消息和挂起请求消息， 使得 SGW释放语 音^载之外的其他 载的用户面资源， 保留语音^载的用户面资源， SGW和 PGW挂起非 GBR承载和去激活语音承载之外的其他 GBR承载， 保证了用户 语音业务的正常进行。
图 4a为本发明又一实施例提供的一种承载处理方法的信令流程图， 如图 4a所示： 401 ,在执行 SRVCC流程中 , ΜΜΕ接收到来自源侧 eNodeB( Evolved Node B, 演进基站） 的切换需求消息； 或者 MME接收来自源侧 eNodB的 UE上下 文释放请求消息（UE Context Release Request ); 或者 MME接收来自目标侧 SGSN ( Serving GPRS Support Node服务 GPRS支持节点）的挂起消息， 所述 挂起消息可以是挂起通知 （ Suspend Notification ) 消息， 或者可以是携带挂起 请求（ Suspend Request )扩展头部的消息（例如 SGSN context Request )。
402, 源侧 MME发起挂起流程， 包括：
402a, 源侧 MME向 SGW发送挂起请求消息，所述 SGW释放语音承载之 外的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载； 或者使得所述 SGW放语音承载之外的其他承载的用户面资源， 保留语音承载 的用户面资源 , 挂起语音承载之外的其他承载；
其中， 所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音 承载的用户面资源，挂起非 GBR承载； 所述 SGW释放语音承载之外的其他承 载的用户面资源，保留语音承载的用户面资源，挂起语音承载之外的其他承载， 具体实现可以包括但不限于以下方法：
1 )若所述挂起请求消息包含语音承载保留指示消息时，所述 SGW可以根 据所述语音承载保留指示释放语音承载之外的其他承载的用户面资源，保留语 音承载的用户面资源， 挂起非 GBR承载； 或者释放语音承载之外的其他承载 的用户面资源， 保留语音承载的用户面资源， 挂起语音承载之外的其他承载； 或者，
2 )若所述挂起请求消息包含需要保留的语音承载的标识时， 所述需要保 留的语音 载的标识可以包含在信元 "Bearer to be reserve" 或 "Voice Bearer" 中， 用于指示接收该信息的网元设备保留所述承载， 本实施例不限制该信元的 名称， 所述 SGW可以根据所述需要保留的语音承载的标识释放语音承载之外 的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载； 或者释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资 源， 挂起语音承载之外的其他承载； 或者，
3 )若所述挂起请求消息包含需要挂起的语音承载以外的其他承载的标识 时，所述需要挂起的语音承载以外的其他承载的标识可以包含在信元" Bearer to be suspend" 或 "Bearer Context" 中， 用于指示接收该信息的网元设备挂起所 述承载， 本实施例不限制该信元的名称， 所述 SGW可以根据所述需要挂起的 语音承载以外的其他承载的标识释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载； 或者释放语音承载之外的其 他承载的用户面资源， 保留语音承载的用户面资源， 挂起语音承载之外的其他 承载。
其中， 所述释放除了语音承载之外的其他承载的用户面资源具体可以是： 保留所述语音承载之外的其他承载的上下文，删除语音承载之外的其他承载的 下行隧道网元（例如接入网元）的相关信息， 例如隧道终端标识和地址； 所述 保留语音承载用户面资源具体可以是： 保留所述语音承载的上下文， 不改变所 述语音承载上下文内容（例如语音承载对应的下行隧道网元的隧道终端标识和 地址）； 所述挂起非 GBR承载具体可以是： 保留所述非 GBR承载的上下文， 并将所述非 GBR承载的状态置为挂起； 所述挂起语音承载之外的其他承载具 体可以是： 保留所述语音承载之外的其他承载的上下文， 并将所述语音承载之 外的其他承载的状态置为挂起。 其中， 若承载（例如非 GBR承载）被挂起， 则 SGW将丢弃其所接收的所述承载对应的报文， 本实施例中， 由于语音承载 保留且未被挂起， 则 SGW将正常的进行 IP语音（即 VoIP )业务。
其中 , 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改 载请求（ Modify Bearer Request ), 或者可以是新的消息， 例 如 SRVCC挂起通知 ( SRVCC Suspend Notification ) 消息， 本实施例对此不#丈 限制。
402b , SGW向 PGW发送挂起请求消息；
SGW接收来自源侧 MME的挂起请求消息之后 , SGW向 PGW发送挂起 请求消息， 所述 SGW向 PGW发送的挂起请求消息包含语音承载保留指示或 者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承载的标 识 , 此时， 所述 PGW可以进行如下操作： 挂起非 GBR承载以及保留 GBR承 载中的语音承载； 或者挂起语音承载之外的其他承载以及保留 GBR承载中的 语音承载。其具体实现可以参见步驟 402a中 SGW所作的相应处理， 此处不再 赘述。
其中， 若承载（例如非 GBR承载）被挂起， 则 PGW将丢弃其所接收的 所述承载对应的报文， 本实施例中， 由于语音承载保留且未被挂起， 则 PGW 将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改 载请求（Modify Bearer Request ) 消息， 或者可以是新的消 息， 例如 SRVCC挂起通知（ SRVCC Suspend Notification ) 消息， 本实施例对 此不做限制。
402c, PGW向 SGW发送挂起响应消息； 其中， 所述挂起响应消息具体为 挂起应答 ( Suspend Acknowledge ) 消息。
402d, SGW向 MME发送挂起响应消息； 其中， 所述挂起响应消息具体 为挂起应答 ( Suspend Acknowledge ) 消息。
403, 源侧 MME向 SGW发起去激活承载流程， 以去激活除语音承载之外 的其他 GBR承载， 该步驟具体包括：
403a, 源侧 MME向 SGW发送删除承载命令 ( Delete Bearer Command ) 消息；
其中， 所述删除承载命令消息中携带语音承载之外的其他 GBR承载的上 下文。
403b, SGW向 PGW发送删除承载命令 ( Delete Bearer Command ) 消息； 其中， 所述删除承载命令消息中携带语音承载之外的其他 GBR承载的上 下文。 403c, PGW向 SGW发送删除承载请求 ( Delete Bearer Request ) 消息； 403d, SGW向 MME发送删除承载请求（ Delete Bearer Request ) 消息； 403e, MME向 SGW发送删除 载响应 （ Delete Bearer Response ) 消息； 403f, SGW向 PGW发送删除 7|载响应 （ Delete Bearer Response ) 消息； 上述步驟 402、 403的执行没有固定顺序关系， 可以在 MME接收来自源 侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上下文释放请 求消息或者来自目标侧服务 GPRS支持节点的挂起消息后同时触发； 也可以在 接收来自源侧演进基站的切换需求消息或者来自源侧演进基站的用户设备上 下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂起消息后分别触 发， 但没有固定的顺序关系以及相互依赖关系。
采用本发明实施例步驟 401〜403所述的方法，在执行 SRVCC流程中，ΜΜΕ 通过向 SGW发送挂起请求消息， 使得 SGW释放语音承载之外的其他承载的 用户面资源， 保留语音承载的用户面资源， SGW和 PGW挂起非 GBR承载或 挂起语音承载之外的其他承载， 保证了用户语音业务的正常进行。
图 4b为本发明又一实施例提供的一种承载处理方法的第二信令流程图， 如图 4b所示:
本实施例中， 与图 4a所示的实施例相比较， 前两个步骤与图 4a所述实施 例中的步驟 401〜402完全相同， 故具体描述请参照图 4a实施例中的叙述， 在 此不做赞述。
在此本实施例只对步驟 403，做进一步详细描述。
403，， SGW在接收到源侧 MME发送的挂起请求消息之后 , SGW向 PGW 发起去激活承载流程， 以去激活除语音承载之外的其他 GBR承载。 其中， 该 步驟具体包括：
403'a, SGW向 PGW发送删除承载命令 ( Delete Bearer Command )消息； 其中， 所述删除承载命令消息中携带语音承载之外的其他 GBR承载的上 下文。 403，b, PGW向 SGW发送删除承载请求 ( Delete Bearer Request ) 消息； 403，c, SGW向 PGW发送删除 载响应 （ Delete Bearer Response ) 消息。 采用本发明实施例步驟 401〜403，所述的方法， 在 UE执行 SRVCC切换的 流程中， MME通过向 SGW发送挂起请求消息， 使得 SGW释放语音承载之外 的其他 载的用户面资源， 保留语音 载的用户面资源， SGW和 PGW挂起 GBR承载和去激活语音承载之外的其他 GBR承载， 保留了 UE的语音承载， 保证了用户语音业务的正常进行。
图 5为本发明再一实施例提供的一种承载处理方法的信令流程图， 如图 5 所示：
501 ,在执行 SRVCC流程中 , MME接收到来自源侧 eNodeB( Evolved Node B, 演进基站） 的切换需求消息或者 MME接收来自源侧 eNodB的 UE上下文 释放请求消息（ UE Context Release Request )或者 MME接收来自目标侧 SGSN
( Serving GPRS Support Node服务 GPRS支持节点）的挂起消息， 所述挂起消 息可以是挂起通知 （Suspend Notification ) 消息， 或者可以是携带挂起请求 ( Suspend Request )扩展头部的消息（例如 SGSN context Request )。
502, 源侧 MME发起挂起流程， 包括：
502a, 源侧 MME向 SGW发送挂起请求消息，所述 SGW释放语音承载之 外的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR承载。
其中， 所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音 承载的用户面资源， 挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR 承载， 具体实现可以包括但不限于以下方法：
1 )若所述挂起请求消息包含语音承载保留指示消息时，所述 SGW可以根 据所述语音承载保留指示释放语音承载之外的其他承载的用户面资源，保留语 音承载的用户面资源，挂起非 GBR承载，以及去激活语音承载之外的其他 GBR 承载； 或者， 2 )若所述挂起请求消息包含需要保留的语音承载的标识时， 所述需要保 留的语音 载的标识可以包含在信元 "Bearer to be reserve" 或 "Voice Bearer" 中， 用于指示接收该信息的网元设备保留所述承载， 本实施例不限制该信元的 名称， 所述 SGW可以根据所述需要保留的语音承载的标识释放语音承载之外 的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR承载； 或者，
3 )若所述挂起请求消息包含需要挂起的语音承载以外的其他承载的标识 时 ,所述需要挂起的语音承载以外的其他承载的标识可以包含在信元 "Bearer to be suspend" 或 "Bearer Context" 中， 用于指示接收该信息的网元设备挂起所 述承载， 本实施例不限制该信元的名称， 所述 SGW可以根据所述需要挂起的 语音承载以外的其他承载的标识释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源， 挂起非 GBR承载， 以及去激活语音承载之外的 其他 GBR承载。
其中， 所述释放除了语音承载之外的其他承载的用户面资源具体可以是： 保留所述语音承载之外的其他承载的上下文，删除语音承载之外的其他承载的 下行隧道网元（例如接入网元）的相关信息， 例如隧道终端标识和地址； 所述 保留语音承载用户面资源具体可以是： 保留所述语音承载的上下文， 不改变所 述语音承载上下文内容（例如语音承载对应的下行隧道网元的隧道终端标识和 地址）； 所述挂起非 GBR承载具体可以是： 保留所述非 GBR承载的上下文， 并将所述非 GBR承载的状态置为挂起； 所述去激活语音承载之外的其他 GBR 承载具体可以是： 删除所述语音承载之外的其他 GBR承载的上下文。 其中， 若承载 (例如非 GBR承载）被挂起， 则 SGW将丟弃其所接收的所述承载对应 的报文， 本实施例中， 由于语音承载保留且未被挂起， 则 SGW将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改 载请求（Modify Bearer Request ) 消息， 或者可以是新的消 息， 例如 SRVCC挂起通知（ SRVCC Suspend Notification ) 消息， 本实施例对 此不做限制。
502b , SGW向 PGW发送挂起请求消息；
SGW接收来自源侧 MME的挂起请求消息之后 , SGW向 PGW发送挂起 请求消息， 所述 SGW向 PGW发送的挂起请求消息包含语音承载保留指示或 者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承载的标 识， 此时， 所述 PGW可以进行如下操作： 挂起非 GBR承载， 以及去激活语音 承载之外的其他 GBR承载。 其具体实现可以参见步驟 502a中 SGW所作的相 应处理， 此处不再赘述。
其中， 若承载（例如非 GBR承载）被挂起， 则 PGW将丢弃其所接收的 所述承载对应的报文， 本实施例中， 由于语音承载保留且未被挂起， 则 PGW 将正常的进行 IP语音（即 VoIP )业务。
其中， 所述挂起请求消息可以是现有的挂起通知（ Suspend Notification ) 消息或者是爹改承载请求（Modify Bearer Request ) 消息， 或者可以是新的消 息， 例如 SRVCC挂起通知（ SRVCC Suspend Notification ) 消息， 本实施例对 此不做限制。
502c, PGW向 SGW发送挂起响应消息； 其中， 所述挂起响应消息具体为 挂起应答 ( Suspend Acknowledge ) 消息。
502d, SGW向 MME发送挂起响应消息； 其中， 所述挂起响应消息具体 为挂起应答 ( Suspend Acknowledge ) 消息。
釆用本发明实施例步驟 501〜502所述的方法，在执行 SRVCC流程中 , MME 通过向 SGW发送挂起请求消息， 使得 SGW释放语音承载之外的其他承载的 用户面资源 , 保留语音承载的用户面资源 , SGW和 PGW挂起非 GBR承载和 去激活语音承载之外的其他 GBR承载， 保证了用户语音业务的正常进行。
图 6a为本发明实施例提供的一种移动管理网元的第一示意图， 如图 6a所 示， 该移动管理网元包括： 接收模块 601 , 用于接收来自源侧演进基站的切换需求消息或者来自源侧 演进基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点 的挂起消息；
发送模块 602 , 用于向 SGW发送释放接入承载请求消息， 以使所述 SGW 释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源。
图 6b为本发明实施例提供的一种移动管理网元的第二示意图， 如图 6b所 示， 在图 6a所示实施例的基础上， 该移动管理网元还包括：
挂起流程发起模块 603, 用于向所述 SGW发送挂起请求消息， 触发所述 SGW向 PGW发送挂起请求消息， 以使所述 SGW和 PGW挂起非 GBR承载， 保留语音承载； 或者以使所述 SGW和 PGW挂起语音承载之外的其他承载。
图 6c为本发明实施例提供的一种移动管理网元的第三示意图， 如图 6c所 示， 在图 6b所示实施例的基础上， 该移动管理网元还包括：
去激活流程发起模块 604, 用于向所述 SGW发起去激活流程， 以使所述 SGW去激活语音承载之外的其他 GBR承载。
采用本发明实施例图 6a〜图 6c所述的移动管理网元， 在执行 SRVCC流程 中， 承载处理装置通过向 SGW发送释放接入承载请求消息， 使得 SGW释放 语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源， 进而使 得 SGW和 PGW挂起非 GBR承载和去激活语音承载之外的其他 GBR承载， 保证了用户语音业务的正常进行。
图 7为本发明实施例提供的一种移动管理网元的第四示意图，如图 7所示， 该移动管理网元包括：
接收模块 701 , 用于接收来自源侧演进基站的切换需求消息或者来自源侧 演进基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点 的挂起消息；
发送模块 702 , 用于向 SGW发送释放接入承载请求消息， 以使所述 SGW 释放语音承载之外的其他承载的用户面资源， 保留语音承载。 挂起流程发起模块 703, 用于向所述 SGW发送挂起请求消息， 触发所述 SGW向 PGW发送挂起请求消息， 以使所述 SGW和 PGW挂起非 GBR承载， 保留语音承载， 以及去激活语音承载之外的其他 GBR承载。
采用本发明实施例图 7所述的移动管理网元， 在执行 SRVCC流程中， 承 载处理装置通过向 SGW发送释放接入承载请求消息， 使得 SGW释放语音承 载之外的其他承载的用户面资源，保留语音承载的用户面资源，进而使得 SGW 和 PGW挂起非 GBR承载和去激活语音承载之外的其他 GBR承载， 保证了用 户语音业务的正常进行。
图 8a为本发明实施例提供的一种移动管理网元的第五示意图， 如图 8所 示， 该移动管理网元包括：
接收模块 801 , 用于接收来自源侧演进基站的切换需求消息或者来自源侧 演进基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点 的挂起消息；
发送模块 802, 用于向 SGW发送挂起请求消息， 触发所述 SGW向 PGW 发送挂起请求消息， 以使所述 SGW释放语音承载之外的其他承载的用户面资 源， 保留语音承载的用户面资源； 进而使得所述 SGW和 PGW挂起非 GBR承 载； 或者进而使得所述 SGW和 PGW挂起语音承载之外的其他承载。
图 8b为本发明实施例提供的一种移动管理网元的第六示意图， 如图 8a所 示， 在图 8b所示实施例的基础上， 该移动管理网元还包括：
去激活流程发起模块 803 , 用于向 SGW发起去激活流程， 以使 SGW去激 活除语音承载之外的其他 GBR承载。
采用本发明实施例图 8a〜图 8b所述的移动管理网元， 在执行 SRVCC流程 中， 承载处理装置通过向 SGW发送挂起请求消息， 使得 SGW释放语音承载 之外的其他承载的用户面资源， 保留语音承载的用户面资源， 进而使得 SGW 和 PGW挂起非 GBR承载和去激活语音承载之外的其他 GBR承载， 保证了用 户语音业务的正常进行。 图 9为本发明实施例提供的一种移动管理网元的第七示意图，如图 9所示， 该移动管理网元包括：
接收模块 901， 用于接收来自源侧演进基站的切换需求消息或者来自源侧 演进基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS支持节点 的挂起消息；
发送模块 902 , 用于向 SGW发送挂起请求消息， 以使所述 SGW释放语音 承载之外的其他承载的用户面资源，保留语音承载的用户面资源，挂起非 GBR 承载， 以及去激活语音承载之外的其他 GBR承载； 或者
用于向 SGW挂起请求消息， 触发所述 SGW向 PGW发送挂起请求消息， 以使所述 SGW释放语音承载之外的其他承载的用户面资源， 保留语音承载的 用户面资源，进而使得 PGW挂起非 GBR承载， 以及去激活语音承载之外的其 他 GBR承载。
采用本发明实施例图 9所述的移动管理网元， 在执行 SRVCC流程中， 承 载处理装置通过向 SGW发送挂起请求消息， 使得 SGW释放语音承载之外的 其他承载的用户面资源，保留语音承载的用户面资源， 进而使得 SGW和 PGW 挂起非 GBR承载和去激活语音承载之外的其他 GBR承载，保证了用户语音业 务的正常进行。
图 10a为本发明实施例提供的一种承载处理系统的第一示意图， 如图 10a 所示， 该 载处理系统包括：
移动管理网元 1001 , 用于向 SGW发送释放接入承载请求消息或者挂起请 求消息；
服务网关 1002,用于接收来自所述移动管理网元的释放接入承载请求消息 或者挂起请求消息， 执行释放语音承载之外的其他承载的用户面资源， 保留语 音承载的用户面资源， 挂起非 GBR承载或者挂起语音承载之外的其他承载， 去激活语音承载之外的其他 GBR承载。
图 10b为本发明实施例提供的一种承载处理系统的第二示意图， 如图 10b 示， 在图 10a的基础上， 该承载处理系统进一步包括：
分组数据网络网关 1003, 用于接收来自所述 SGW的挂起请求消息， 执行 挂起非 GBR承载或者挂起语音承载之外的其他承载， 去激活语音承载之外的 其他 GBR承载。
采用本发明实施例图 10a〜10b所述的 载处理系统 , 在执行 SRVCC流程 中 ,承载处理装置通过向 SGW发送释放接入承载请求消息或者挂起请求消息 , 使得 SGW释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户 面资源， 进而使得 SGW和 PGW挂起非 GBR承载和去激活语音承载之外的其 他 GBR承载， 保证了用户语音业务的正常进行
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步驟可 以通过程序指令相关的硬件来完成， 前述的程序可以存储于计算机可读取存储 介质中， 该程序在执行时， 执行包括上述方法实施例的步驟； 而前述的存储介 质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。 明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要求及 其等同技术的范围之内 , 则本发明也意图包含这些改动和变型在内。

Claims

权利 要求 书
1、 一种承载处理方法， 其特征在于， 包括：
在执行单一无线语音呼叫连续性流程中， 接收来自源侧演进基站的切换需 求消息或者来自源侧演进基站的用户设备上下文释放请求消息或者来自目标侧 服务 GPRS支持节点的挂起消息；
向服务网关发送请求消息 , 以使所述服务网关释放语音承载之外的其他承 载的用户面资源， 保留语音承载的用户面资源。
2、 根据权利要求 1所述的承载处理方法， 其特征在于， 所述向服务网关发 送请求消息 , 以使所述服务网关释放语音承载之外的其他承载的用户面资源 , 保留语音承载的用户面资源包括：
向服务网关发送释放接入承载请求消息 , 所述释放接入承载请求消息中包 含语音承载保留指示或者包含语音承载之外的其他承载的无线接入承载信息， 所述服务网关释放语音承载之外的其他承载的用户面资源， 保留语音承载的用 户面资源。
3、 根据权利要求 2所述的承载处理方法， 其特征在于， 还包括： 向所述服务网关发送挂起请求消息；
所述服务网关挂起非保证比特速率 GBR承载， 保留语音承载。
4、 根据权利要求 2所述的承载处理方法， 其特征在于， 还包括： 向所述服务网关发送挂起请求消息；
所述服务网关挂起语音承载之外的其他承载， 保留语音承载。
5、 根据权利要求 3所述的承载处理方法， 其特征在于， 还包括： 所述服务网关向分组数据网络网关发送挂起请求消息 , 所述挂起请求消息 中包含语音承载保留指示或者需要保留的语音承载的标识或者需要挂起的语音 承载以外的其他承载的标识；
所述分组数据网络网关挂起非 GBR承载， 保留语音承载。
6、 根据权利要求 4所述的承载处理方法， 其特征在于， 还包括： 所述服务网关向分组数据网络网关发送挂起请求消息， 所述挂起请求消息 中包含语音承载保留指示或者需要保留的语音承载的标识或者需要挂起的语音 载以外的其他^载的标识；
所述分组数据网络网关挂起语音承载之外的其他承载， 保留语音承载。
7、 根据权利要求 3-6任一所述的承载处理方法， 其特征在于， 还包括： 向所述服务网关发起去激活流程， 所述服务网关去激活语音承载之外的其 他 GBR承载。
8、 根据权利要求 3-6任一所述的承载处理方法， 其特征在于， 所述向服务 网关发送释放接入承载请求消息之后， 还包括：
所述服务网关向分组数据网络网关发起去激活流程 , 所述分组数据网络网 关去激活语音承载之外的其他 GBR承载。
9、 根据权利要求 2所述的承载处理方法， 其特征在于， 还包括：
向所述服务网关发送挂起请求消息；
所述服务网关挂起非 GBR承载， 保留语音承载， 以及去激活语音承载之外 的其他 GBR承载。
10、 根据权利要求 9所述的承载处理方法， 其特征在于， 还包括： 所述服务网关向分組数据网络网关发送挂起请求消息， 所述挂起请求消息 中包含语音承载保留指示或者需要保留的语音承载的标识或者需要挂起的语音 承载以外的其他承载的标识；
所述分组数据网络网关挂起非 GBR承载， 保留语音承载， 以及去激活语音 承载之外的其他 GBR承载。
11、 根据权利要求 1 所述的承载处理方法， 其特征在于， 所述向服务网关 发送请求消息 , 以使所述服务网关释放语音承载之外的其他承载的用户面资源 , 保留语音承载的用户面资源包括：
向服务网关发送挂起请求消息， 所述挂起请求消息中包含语音承载保留指 示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承载的 标识；
所述服务网关释放语音承载之外的其他承载的用户面资源， 保留语音承载 的用户面资源， 挂起非 GBR承载。
12、 根据权利要求 1 所述的承载处理方法， 其特征在于， 所述向服务网关 发送请求消息， 以使所述服务网关释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源包括：
向服务网关发送挂起请求消息， 所述挂起请求消息中包含语音承载保留指 示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承载的 标识；
所述服务网关释放语音承载之外的其他承载的用户面资源， 保留语音承载 的用户面资源 , 挂起语音承载之外的其他承载。
13、 根据权利要求 11所述的承载处理方法， 其特征在于， 还包括： 所述服务网关向分组数据网络网关发送挂起请求消息， 所述挂起请求消息 中包含语音承载保留指示或者需要保留的语音承载的标识或者需要挂起的语音 承载以外的其他承载的标识；
所述分组数据网络网关挂起非 GBR承载以及保留语音承载。
14、 根据权利要求 12所述的承载处理方法， 其特征在于， 还包括： 所述服务网关向分组数据网络网关发送挂起请求消息 , 所述挂起请求消息 中包含语音承载保留指示或者需要保留的语音承载的标识或者需要挂起的语音 载以外的其他^载的标识；
所述分组数据网络网关挂起语音承载之外的其他承载以及保留语音承载。
15、 根据权利要求 11-14任一所述的承载处理方法， 其特征在于， 还包括： 向所述服务网关发起去激活流程， 所述服务网关去激活除语音承载之外的 其他 GBR 7|载。
16、 根据权利要求 11或者 14任一所述的承载处理方法， 其特征在于， 所 述向服务网关发送挂起请求消息之后， 还包括： 所述服务网关向分组数据网络 网关发起去激活流程， 所述分组数据网络网关去激活语音承载之外的其他 GBR 承载。
17、 根据权利要求 1 所述的承载处理方法， 其特征在于， 所述向服务网关 发送请求消息， 以使所述服务网关释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源包括：
向所述服务网关发送挂起请求消息， 所述挂起请求消息中包含语音承载保 留指示或者需要保留的语音承载的标识或者需要挂起的语音承载以外的其他承 载的标识；
所述服务网关释放语音承载之外的其他承载的用户面资源， 保留语音承载 的用户面资源；
所述服务网关挂起非 GBR承载， 去激活语音承载之外的其他 GBR承载。
18、 根据权利要求 17所述的承载处理方法， 其特征在于， 还包括： 所述服务网关向分组数据网络网关发送挂起请求消息， 所述挂起请求消息 中包含语音承载保留指示或者需要保留的语音承载的标识或者需要挂起的语音 承载以外的其他承载的标识；
所述分组数据网络网关挂起非 GBR承载，去激活语音承载之外的其他 GBR 承载。
19、 一种移动管理网元， 其特征在于， 包括：
接收模块， 用于接收来自源侧演进基站的切换需求消息或者来自源侧演进 基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂 起消息；
发送模块， 用于向服务网关发送释放接入承载请求消息， 以使所述服务网 关释放语音承载之外的其他承载的用户面资源， 保留语音承载的用户面资源。
20、 根据权利要求 19所述的移动管理网元， 其特征在于， 还包括： 挂起流程发起模块， 用于向所述服务网关发送挂起请求消息， 触发所述服 务网关向分组数据网络网关发送挂起请求消息， 以使所述服务网关和分组数据 网络网关挂起非 GBR承载； 或者以使所述服务网关和分组数据网络网关挂起语 音承载之外的其他承载。
21、 根据权利要求 20所述的移动管理网元， 其特征在于， 还包括： 去激活流程发起模块， 用于向所述服务网关发起去激活流程， 以使所述服 务网关去激活语音承载之外的其他 GBR承载。
22、 根据权利要求 19所述的移动管理网元， 其特征在于， 还包括： 挂起流程发起模块， 用于向所述服务网关发送挂起请求消息 , 触发所述服 务网关向分组数据网络网关发送挂起请求消息， 以使所述服务网关和分组数据 网络网关挂起非 GBR承载， 以及去激活语音承载之外的其他 GBR承载。
23、 一种移动管理网元， 其特征在于， 包括：
接收模块， 用于接收来自源侧演进基站的切换需求消息或者来自源侧演进 基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂 起消息；
发送模块， 用于向服务网关发送挂起请求消息， 触发所述服务网关向分组 数据网络网关发送挂起请求消息， 以使所述服务网关释放语音承载之外的其他 承载的用户面资源， 保留语音承载的用户面资源；
进而使得所述服务网关和分組数据网络网关挂起非 GBR承载； 或者进而使 得所述服务网关和分组数据网络网关挂起语音承载之外的其他承载。
24、 根据权利要求 23所述的移动管理网元， 其特征在于， 还包括： 去激活流程发起模块， 用于向服务网关发起去激活流程， 以使服务网关去 激活除语音承载之外的其他 GBR承载。
25、 一种移动管理网元， 其特征在于， 包括：
接收模块， 用于接收来自源侧演进基站的切换需求消息或者来自源侧演进 基站的用户设备上下文释放请求消息或者来自目标侧服务 GPRS 支持节点的挂 起消息；
发送模块， 用于向服务网关发送挂起请求消息， 以使所述服务网关释放语 音承载之外的其他承载的用户面资源，保留语音承载的用户面资源，挂起非 GBR 承载， 以及去激活语音承载之外的其他 GBR承载； 或者
用于向服务网关发送挂起请求消息， 触发所述服务网关向分组数据网络网 关发送挂起请求消息 , 以使所述服务网关释放语音承载之外的其他承载的用户 面资源， 保留语音承载的用户面资源； 进而使得分组数据网络网关挂起非 GBR 承载 , 以及去激活语音承载之外的其他 GBR承载。
26、 一种承载处理系统， 其特征在于， 包括：
移动管理网元， 用于向服务网关发送释放接入承载请求消息或者挂起请求 消息；
服务网关， 用于接收来自所述移动管理网元的释放接入承载请求消息或者 挂起请求消息， 执行释放语音承载之外的其他承载的用户面资源， 保留语音承 载的用户面资源， 挂起非 GBR承载或者挂起语音承载之外的其他承载， 去激活 语音承载之外的其他 GBR承载。
27、 根据权利要求 26所述的承载处理系统， 其特征在于， 还包括： 分组数据网络网关， 用于接收来自所述服务网关的挂起请求消息， 执行挂 起非 GBR承载或者挂起语音承载之外的其他承载， 去激活语音承载之外的其他 GBR承载。
PCT/CN2010/076183 2010-08-20 2010-08-20 一种承载处理方法、系统及移动管理网元 WO2011109998A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201080001879.1A CN102405683B (zh) 2010-08-20 2010-08-20 一种承载处理方法、系统及移动管理网元
PCT/CN2010/076183 WO2011109998A1 (zh) 2010-08-20 2010-08-20 一种承载处理方法、系统及移动管理网元

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/076183 WO2011109998A1 (zh) 2010-08-20 2010-08-20 一种承载处理方法、系统及移动管理网元

Publications (1)

Publication Number Publication Date
WO2011109998A1 true WO2011109998A1 (zh) 2011-09-15

Family

ID=44562827

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076183 WO2011109998A1 (zh) 2010-08-20 2010-08-20 一种承载处理方法、系统及移动管理网元

Country Status (2)

Country Link
CN (1) CN102405683B (zh)
WO (1) WO2011109998A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016150046A1 (zh) * 2015-03-25 2016-09-29 中兴通讯股份有限公司 一种降低掉话率的方法、装置及系统
CN108370613A (zh) * 2015-12-18 2018-08-03 华为技术有限公司 一种重定向的方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110089151B (zh) * 2016-12-20 2022-05-31 苹果公司 在切换过程期间用于分组转发的系统和方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478795A (zh) * 2008-04-30 2009-07-08 华为技术有限公司 资源处理的方法、通信系统和移动性管理网元
CN101494848A (zh) * 2008-01-25 2009-07-29 华为技术有限公司 业务挂起的方法、业务恢复的方法、系统及设备
CN101662756A (zh) * 2008-08-28 2010-03-03 华为技术有限公司 语音连续性呼叫切换的方法、系统及移动业务交换中心

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2338299A2 (en) * 2008-10-15 2011-06-29 Telefonaktiebolaget L M Ericsson (publ) Methods, apparatuses and computer software for extending the mme-ganc interface to report which ues have registered for the gan to tunnel cs voice over evolved packet system (eps)
US8543114B2 (en) * 2008-10-15 2013-09-24 Telefonaktiebolaget Lm Ericsson (Publ) Voice over LTE via generic access handover (HO) apparatus and method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494848A (zh) * 2008-01-25 2009-07-29 华为技术有限公司 业务挂起的方法、业务恢复的方法、系统及设备
CN101478795A (zh) * 2008-04-30 2009-07-08 华为技术有限公司 资源处理的方法、通信系统和移动性管理网元
CN101662756A (zh) * 2008-08-28 2010-03-03 华为技术有限公司 语音连续性呼叫切换的方法、系统及移动业务交换中心

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"TS 23.216 V9.4.0 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Single Radio Voice Call Continuity (SRVCC); Stage 2 (Release 9)", 3GPP, June 2010 (2010-06-01) *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016150046A1 (zh) * 2015-03-25 2016-09-29 中兴通讯股份有限公司 一种降低掉话率的方法、装置及系统
CN108370613A (zh) * 2015-12-18 2018-08-03 华为技术有限公司 一种重定向的方法及装置
EP3393201A4 (en) * 2015-12-18 2018-11-14 Huawei Technologies Co., Ltd. Method and device for redirection
US10455380B2 (en) 2015-12-18 2019-10-22 Huawei Technologies Co., Ltd. Redirection method and apparatus

Also Published As

Publication number Publication date
CN102405683A (zh) 2012-04-04
CN102405683B (zh) 2014-04-30

Similar Documents

Publication Publication Date Title
USRE48262E1 (en) Communication system, mobility management network element and method for processing resource
US9980181B2 (en) PS to CS handover indicator
ES2738105T3 (es) Procedimiento y sistema de soporte de continuidad de la llamada por radio vídeo única durante un traspaso
JP5536954B2 (ja) 回路交換ドメインからパケット交換ドメインへのハンドオーバー方法、装置、および通信システム
US9596634B2 (en) Assist reordering of downlink data at serving GW relocation
WO2011006440A1 (zh) 一种切换方法和装置
US20100056147A1 (en) Bearer suspension method, bearer resumption method, and gateway agent
WO2009132550A1 (zh) 一种切换方法及通讯系统以及相关设备
CN102232321B (zh) 承载建立方法、系统和网关设备
WO2010105525A1 (zh) 一种切换的优化方法、切换装置和系统
WO2009092260A1 (zh) 实现语音呼叫连续性的方法、互联功能实体及终端设备
WO2009149656A1 (zh) 一种实现业务切换的方法、装置及系统
WO2011109998A1 (zh) 一种承载处理方法、系统及移动管理网元
WO2014005306A1 (zh) 视频呼叫的反向切换的方法和装置
WO2013107022A1 (zh) 分组数据网连接处理方法及系统、锚点设备和用户设备

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080001879.1

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10847256

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10847256

Country of ref document: EP

Kind code of ref document: A1