[go: up one dir, main page]

WO2011085668A1 - Procédé, dispositif et système de commande de transfert - Google Patents

Procédé, dispositif et système de commande de transfert Download PDF

Info

Publication number
WO2011085668A1
WO2011085668A1 PCT/CN2011/070147 CN2011070147W WO2011085668A1 WO 2011085668 A1 WO2011085668 A1 WO 2011085668A1 CN 2011070147 W CN2011070147 W CN 2011070147W WO 2011085668 A1 WO2011085668 A1 WO 2011085668A1
Authority
WO
WIPO (PCT)
Prior art keywords
voip
message
msc
bearer
mgw
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2011/070147
Other languages
English (en)
Chinese (zh)
Inventor
刘海
吴晓波
帅扬来
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2011085668A1 publication Critical patent/WO2011085668A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present invention relates to the field of communication technologies, specific handover control methods, and related devices and systems.
  • BACKGROUND Currently, many areas have been widely deployed second generation GSM technology / global third generation mobile communication technology (2G / 3G, 2 nd Generation / 3 rd Generation) network, in a way be seen as a Comprehensive coverage.
  • the third-generation partner project standards organization launched a new generation of evolution network architecture, in which the core network part is the System Architecture Evolution (SAE) network, and the access network part is long-term evolution (LTE, Long).
  • SAE System Architecture Evolution
  • LTE Long-term evolution
  • LTE long-term evolution
  • E-UTRAN Universal Mobile communication system Terrestrial Radio Access Network
  • a network such as SAE/LTE that provides only a PS domain is called a pure PS domain network.
  • mobile communication services can be divided into:
  • CS Circuit Switching
  • the services carried by the packet switching (PS, Packet Switching) domain include data services and session services, and the session services include Voice over Internet Protocol (VoIP) services.
  • VoIP Voice over Internet Protocol
  • the embodiments of the present invention provide a handover control method and related devices and systems, which are beneficial for maintaining voice continuity in a network handover process.
  • a handover control method includes:
  • the mobile switching center MSC receives the first message from the mobility management entity MME, where the first message carries the VoIP EPS bearer ID of the first user equipment, the control data bearer information corresponding to the first UE of the packet data gateway PGW, and the PGW corresponding to the first message.
  • the bearer modification request message carries a VoIP EPS bearer ID of the first user equipment and a VoIP corresponding to the first UE of the media gateway MGW
  • the user plane bearer information, and the user plane bearer corresponding to the VOIP of the first UE is updated to the MGW;
  • a handover control method includes:
  • the MME receives an attach request message or a PDN activation request message from the first UE;
  • a PS to CS switching control method includes:
  • the MSC receives a request from the SGW to establish a first session establishment request message corresponding to the control plane bearer of the first UE, and establishes a control plane bearer corresponding to the first UE corresponding to the SGW;
  • the MSC obtains the address information of the PGW
  • a handover control method includes:
  • the MME sends a second message to the MSC, where the second message carries the user plane bearer information of the VoIP corresponding to the first UE of the SGW;
  • the bearer modification message carries the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and the user plane bearer of the VoIP corresponding to the first UE of the SGW is further New to MGW.
  • a handover control method includes:
  • the MME sends a fourth message to the MSC, where the fourth message carries the user plane bearer information of the VoIP corresponding to the first UE of the SGW;
  • the MME receives a fifth message from the MSC, where the fifth message carries user plane bearer information of the VoIP corresponding to the first UE of the MGW;
  • the MME sends a sixth message to the SGSN, where the sixth message carries the user plane bearer information of the VoIP corresponding to the VoIP of the first UE.
  • a handover control method includes:
  • the SGSN receives the sixth message from the MME, where the sixth message carries the user plane bearer information of the VoIP corresponding to the first UE of the MGW.
  • the bearer modification message carries the user plane bearer information of the VoIP corresponding to the first UE of the MGW, and updates the user plane bearer of the VoIP corresponding to the VoIP of the SGW to the MGW.
  • a mobile switching center including:
  • a receiving module configured to receive a first message from the mobility management entity MME, where the first message carries a VoIP EPS bearer ID of the first user equipment, and the control data bearer information of the first UE and the PGW corresponding to the packet data gateway PGW User plane bearer information of a UE's VoIP;
  • a sending module configured to send, according to the control plane bearer information of the PGW to the first UE, a bearer modification request message, where the bearer modification request message carries a VoIP EPS bearer ID of the first user equipment and a corresponding corresponding to the media gateway MGW User plane bearer information of the VoIP of the first UE, and updating the user plane bearer of the VOIP corresponding to the VOIP of the first UE to the MGW;
  • the notification module is configured to notify the MGW of the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and update the user plane bearer of the VOIP corresponding to the first UE to the PGW.
  • a mobility management entity that includes:
  • a receiving module configured to receive an attach request message or a PDN activation request message from the first UE, where the acquiring module is configured to obtain address information of the MSC;
  • a sending module configured to send a GTP-C message to the SGW, where the GTP-C message carries the address information of the MSC, and triggers the SGW to establish a control plane bearer corresponding to the first UE with the MSC.
  • a mobile switching center including:
  • a first receiving module configured to receive a request from the SGW to establish a control plane bearer corresponding to the first UE a first session establishment request message, and a control plane bearer corresponding to the first UE corresponding to the SGW; and an obtaining module, configured to acquire, by the MSC, address information of the PGW;
  • the first sending module is configured to send a second session establishment request message to the PGW, and establish a control plane bearer corresponding to the first UE with the PGW.
  • a mobility management entity including:
  • a third sending module configured to send a second message to the MSC, where the second message carries user plane bearer information of the VoIP corresponding to the first UE by the SGW;
  • the receiving module receives a third message from the MSC, where the third message carries information about the user plane of the VoIP corresponding to the first UE of the MGW;
  • a fourth sending module configured to send a bearer modification message to the SGW, where the bearer modification message carries the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and the user of the VoIP corresponding to the first UE is updated on the surface of the SGW.
  • the bearer modification message carries the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and the user of the VoIP corresponding to the first UE is updated on the surface of the SGW.
  • a mobility management entity including:
  • a third receiving module configured to receive a fifth message from the MSC, where the fifth message carries user plane bearer information of the VoIP corresponding to the first UE of the MGW;
  • a sixth sending module configured to send, by the MME, a sixth message to the SGSN, where the sixth message carries user plane bearer information of the VoIP corresponding to the first UE of the MGW.
  • a service general packet service support node comprising:
  • the receiving module is configured to receive a sixth message from the MME, where the sixth message carries user plane bearer information of the VoIP of the first UE corresponding to the MGW.
  • the control plane bearer information of the UE and the PPG correspond to the user plane bearer information of the VoIP of the first UE, and the user plane bearer of the VoIP corresponding to the VoIP of the first UE is updated to the MGW by the bearer modification request message, and the MSC is not carried in the bearer modification message.
  • the control plane carries information, and does not correspond to the PGW corresponding to the first UE.
  • the control plane bearer is updated to the MSC, and the management node can maintain the order of the first UE control link. Since the control plane on the PGW is not converted to the MSC, the control message after the PGW is sent to the SGW, so that Interrupting the data service at the same time is beneficial to maintain the voice continuity of the network switching process.
  • FIG. 1 is a schematic diagram of a PS to CS switching architecture according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a handover control method according to Embodiment 1 of the present invention.
  • FIG. 3 is a flowchart of a handover control method according to Embodiment 2 of the present invention.
  • FIG. 5 is a flowchart of a handover control method according to Embodiment 3 of the present invention.
  • FIG. 6 is a flowchart of a handover control method according to Embodiment 3 of the present invention.
  • FIG. 9 is a flowchart of a handover control method according to Embodiment 5 of the present invention.
  • FIG. 11 is a flowchart of a handover control method according to Embodiment 7 of the present invention.
  • FIG. 12 is a flowchart of a handover control method according to Embodiment 8 of the present invention.
  • FIG. 13 is a flowchart of another handover control method according to Embodiment 8 of the present invention.
  • FIG. 14 is a schematic diagram of a mobile switching center according to Embodiment 9 of the present invention.
  • FIG. 15 is a schematic diagram of a mobility management entity according to Embodiment 10 of the present invention.
  • FIG. 16 is a schematic diagram of a mobile switching center according to Embodiment 11 of the present invention.
  • FIG. 17 is a schematic diagram of a mobility management entity according to Embodiment 12 of the present invention.
  • FIG. 18 is a schematic diagram of a mobility management entity according to Embodiment 13 of the present invention.
  • FIG. 19 is a schematic diagram of an SGSN according to Embodiment 9 of the present invention.
  • Embodiments of the present invention provide a handover control method and related equipment and system, which are beneficial for maintaining network switching. Change the voice continuity of the process.
  • the E-UTRAN is mainly composed of an evolved base station (eNB, Evolution-NodeB).
  • the core network part of the evolved network includes the Mobility Management Entity (MME) and the SEE Gateway (SAE Gateway).
  • MME Mobility Management Entity
  • SAE Gateway includes a Serving Gateway (SGW, Serving Gateway) and a Packet Data Network Gateway (PGW, PDN Gateway).
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • the MME is a control plane node of the core network part of the evolved network system, and bears the management function of the user equipment (UE) context and the user plane bearer; the SGW mainly bears the transmission function of the service data, and the PGW mainly bears the signaling transmission function.
  • the UTRAN/GERAM is the access network of the 2G/3G network.
  • the Mobile Switching Center (MSC) is mainly responsible for the bearer control of the voice service.
  • the SGSN is mainly responsible for the bearer control of the data service.
  • An Sv interface is introduced between the MME and the MSC.
  • MSCs both the MSC and the MSC server are collectively referred to as MSCs herein.
  • the VoIP VoIP can be switched to the CS domain through the Sv interface.
  • the data service needs to be processed. According to the different 2G/3G network capabilities, there are three ways to process the data service:
  • the UE performs the PS service suspension operation after switching to the 2G network;
  • the UE performs a routing area update operation after accessing the 2G network to continue the data service.
  • the GTP protocol is introduced below.
  • the GTP protocol is a bearer protocol and includes two types: GTP-C and GTP-U.
  • GTP uses a tunnel ID (TEID) to distinguish between users or bearers.
  • TEID tunnel ID
  • GTP tunnels are identified by (IP, TEID) pairs. A set of IP/TEIDs is called F-TEID.
  • GTP-C is the control plane protocol of GTP, and one GTP-C tunnel corresponds to one user.
  • GTP-U is the user plane protocol of GTP.
  • a GTP-U tunnel represents a certain bearer of a certain user. For example, for a certain user, the MME and the SGW need to establish a GTP-C tunnel to serve the user, if the user is in the same When multiple services are performed, multiple GTP-U tunnels can be established to carry different services of the user. The following describes the establishment of a bearer by using the main GTP protocol between network entities.
  • Embodiment 1 is the control plane protocol of GTP, and one GTP-C tunnel corresponds to one user.
  • GTP-U is the user plane protocol of GTP.
  • a GTP-U tunnel represents a certain bearer of a certain user. For example, for a certain user, the MME
  • a handover control method provided in Embodiment 1 may include:
  • the MSC receives the first message from the MME, where the first message carries the VoIP EPS bearer ID of the first UE, the control plane bearer information of the PGW corresponding to the first UE, and the user-side information of the VoIP corresponding to the VoIP of the first UE.
  • the control plane bearer information of the PGW corresponding to the first UE includes the GTP-C F-TEID of the PGW corresponding to the first UE
  • the user plane bearer information of the VoIP corresponding to the VoIP of the PGW includes the PGW corresponding to the first UE.
  • GTP-U F-TEID for VoIP.
  • the VoIP evolved packet system bearer ID (EPS bearer ID) of the first UE is a global identifier corresponding to the VoIP of the first UE. It can be considered that the VoIP EPS bearer ID of the first UE in the PGW is corresponding to the VoIP GTP-U F-TEID of the first UE.
  • the first message sent by the MME may be, for example, a PS to CS handover request message, and of course, the message may carry other information.
  • the MSC sends a bearer modification request message to the PGW based on the control plane bearer information of the PGW corresponding to the first UE, where the bearer modification request message may carry the VoIP EPS bearer ID of the first UE and the user plane of the VoIP corresponding to the VoIP of the first UE. Carrying information, updating the user plane bearer corresponding to the VOIP of the first UE to the MGW;
  • the MSC may obtain the user plane bearer information (including the GTP-U F-TEID) of the VoIP corresponding to the first UE allocated by the MGW, and the bearer corresponds to the control plane bearer information of the first UE (including GTP- C F-TEID ), sending a bearer modification request message carrying the VoIP EPS bearer ID of the first UE and the user plane bearer information of the VoIP corresponding to the VoIP of the first UE to the PGW, and updating the user plane bearer corresponding to the VOIP of the first UE to the PGW To the MGW.
  • the user plane bearer information including the GTP-U F-TEID
  • the bearer corresponds to the control plane bearer information of the first UE (including GTP- C F-TEID )
  • sending a bearer modification request message carrying the VoIP EPS bearer ID of the first UE and the user plane bearer information of the VoIP corresponding to the VoIP of the first UE to the PGW
  • the PGW may update the user plane bearer corresponding to the VOIP of the first UE to the MGW according to the VoIP EPS bearer ID of the first UE.
  • the subsequent PGW may send the VoIP data stream of the first UE to the MGW based on the user plane bearer updated to the MGW.
  • the MSC notifies the MGW of the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and updates the user plane bearer of the VOIP corresponding to the VOIP of the first UE to the PGW.
  • the MGW and the PGW respectively obtain the user plane bearer information of the VoIP corresponding to the first UE, the two-way user plane bearer between the MGW and the PGW is established.
  • the MSC obtains, from the MME, the control plane bearer information of the PGW corresponding to the first UE and the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and the PGW is separately associated with the first UE by using the bearer modification request message.
  • the user plane of the VoIP bearer is updated to the MGW, and the control plane bearer information of the MSC is not carried in the bearer modification message, so that the control plane bearer of the PGW corresponding to the first UE is not updated to the MSC, and the management node can be kept corresponding to the first UE control link.
  • the MSC only performs the process of updating the user plane bearer corresponding to the UE-A of the PGW to the MGW in the process of the UE-A switching from the PS domain to the CS domain.
  • a handover control method provided in Embodiment 3 may include:
  • UE-A sends a measurement report to ENB.
  • the ENB can send a message indicating that the UE-A measures the signal quality of the 2G/3G network.
  • the UE-A performs measurement reporting. If the ENB confirms that the signal quality of the 2G/3G network reported by the UE-A meets the preset signal quality requirement, step 302 is performed.
  • the ENB sends a handover request message to the MME.
  • the ENB carries the information required for the PS handover and the information required for the CS handover in the handover request message.
  • the ENB can separately construct the PS transparent container and the CS transparent container, respectively, for carrying the information required for the PS handover and the CS handover.
  • the information required for the PS handover and the CS handover, respectively, encapsulated in the PS transparent container and the CS transparent container follows the existing 2G/3G network specifications, and is generally the target ID corresponding to the PS handover and the target ID corresponding to the CS handover. , ENB can guarantee the same.
  • the MME selects an MSC, and sends a PS to CS handover request message to the MSC, where the message can carry a £01-$8? bearer ID of 11£-eight, and a GTP-C F-TEID of the PGW corresponding UE-A.
  • the PGW corresponds to the VOIP GTP-U F-TEID of UE-A, and of course can carry other information.
  • the MME can distinguish which bearers belong to the PS service and which bearers according to the bearer information. It belongs to the CS service to initiate CS service switching and PS service switching respectively.
  • the MSC selected by the MME is consistent with the MSC corresponding to the location area (LA, Local Area) of the target cell, the inconsistency will result in a cross-MSC handover (Inter MSC handover).
  • the MSC sends a GTP-U F-TEID corresponding to the VoIP of the UE-A to the MGW, and updates the user plane bearer of the VOIP corresponding to the first UE to the PGW.
  • the MSC receives the PS to CS handover request message from the MME. If the MSC determines that it is not the target MSC (which can be determined according to the target ID), the MSC initiates an Inter MSC handover, and sends an inter-MSC handover request to the target MSC.
  • the target MSC sends a handover request message to the target BSS/RNS, indicating that the target BSS/RNS prepares the CS resource.
  • the MME sends a handover request message to the serving general packet service support node (SGSN), where the handover request message may include information required for PS handover.
  • SGSN serving general packet service support node
  • the PS transparent container may be used to carry information required for PS handover, such as a target ID required for PS handover;
  • the SGSN sends a handover request message to the target BSS/RNS, indicating that the target BSS/RNS prepares the PS resource.
  • the target BSS/RNS determines that the PS resource is sufficient, the target BSS/RNS prepares the PS resource, and returns a handover request response message to the SGSN, where the prepared PS resource information is carried.
  • the SGSN returns a handover response message to the MME, where the handover response message includes PS resource information prepared by the target BSS/RNS.
  • the PS resource information prepared by the target BSS/RNS may include: a PS service air interface channel, a system message, and the like, and may be encapsulated in a PS transparent container, following an existing 2G/3G network CS domain specification.
  • steps 306 ⁇ 309 can be considered as the PS switching preparation phase of UE-A.
  • the target BSS/RNS After receiving the handover request message from the target MSC, if the target BSS/RNS determines that the CS resource is sufficient, the target BSS/RNS prepares the CS resource, and feeds back a handover request response message to the target MSC, where the message may include the target BSS.
  • CS resource information prepared by /RNS;
  • the target MSC sends an inter-MSC handover response to the MSC, where the message may include CS resource information prepared by the target BSS/RNS.
  • the MSC determines that the target MSC is itself, the MSC and the target are omitted.
  • the MSC sends a handover request message to the target BSS/RNS to indicate that the target BSS/RNS prepares the CS resource. If the CS resource is sufficient, the target BSS/RNS prepares the CS resource, and feeds back the handover request response message to the MSC.
  • the CS resource information prepared by the target BSS/RNS may be included in the message.
  • the MSC further triggers the IMS domain to perform session domain conversion; the IMS can notify the calling peer to update the media plane to the media gateway of the CS domain, and release the LTE access network session.
  • the MSC sends a PS to CS handover request response message to the MME, where the message may include CS resource information prepared by the target BSS/RNS.
  • the CS resource information prepared by the target BSS/RNS may include: a CS voice service, an air interface dedicated channel, and a system message, etc., which may be encapsulated in a CS transparent container and conform to the existing 2G/3G network CS domain specification.
  • steps 303 ⁇ 304, 310 ⁇ 313 can be considered as the 8 switch preparation phase of 11 £-eight. It can be understood that there is no necessary sequence between the PS switching preparation and the CS switching preparation, for example, it can be performed simultaneously.
  • the MME may combine the PS resource information received in steps 309 and 313 with the CS resource information, and the MME sends a handover command message to the ENB, where the handover command message may include the merged resource information.
  • the PS to CS handover complete message includes the CS resource information prepared by the target BSS/RNS (mainly including the CS voice service air interface dedicated channel and system message, etc., encapsulated in a CS transparent container, and follows the existing 2G/
  • the 3G network CS domain specification and the handover request response message contain PS resource information (mainly including PS service air interface channel and system message, etc., encapsulated in a PS transparent container, follow the existing 2G/3G network CS domain specification), and CS
  • the transparent container is merged with the PS transparent container, which is called a merged transparent container, and carries the resources prepared by the target BSS/RNS.
  • the ENB sends a handover command message to the UE-A, where the handover command message includes resource information prepared by the target BSS/RNS.
  • the UE-A accesses the 2G/3G network according to the resource information prepared by the target BSS/RNS, and may send a handover complete message to the target BSS/RNS.
  • the target BSS/RNS may send a handover complete message to the target MSC. Sending a handover complete message to the MSC; the target MSC may further send an ISUP response message to the MSC to complete bearer establishment between the MSCs.
  • the MSC sends a modify bearer request message to the PGW.
  • the bearer modification request carries the VOIP EPS bearer ID of the UE-A and the GTP-U F-TEID of the VoIP corresponding to the VoIP of the UE-A.
  • the MGW prepares a GTP-U bearer corresponding to UE-A VoIP, and the MSC acquires the VoIP GTP-U F-TEID of the MGW corresponding UE-A from the MGW.
  • the PGW receives the bearer modification request message from the MSC, and updates the GTP-U corresponding to the UE-A VoIP to the MGW.
  • the MSC only separately updates the GTP-U of the VoIP corresponding to the UE-A of the PGW to the MGW, and does not update the GTP-C of the PGW corresponding to the UE-A to the MSC.
  • This step can be performed after 303 without strict time limits.
  • the MSC sends a PS domain to the CS domain handover complete message to the MME, to notify the MME that the handover is complete.
  • the MSC initiates a location update to the HSS.
  • the target SGSN sends a handover complete message to the MME, and the MME responds to the acknowledgement message.
  • the SGSN sends a bearer modification request message to the SGW, where the message carries the GTP-C F-TEID of the UE-A corresponding to the SGSN, and updates the control plane bearer of the SGW corresponding to the UE-A to the SGSN.
  • the SGW receives the bearer modification request message sent by the SGSN, and updates the control plane bearer corresponding to the UE-A to the SGSN.
  • another switching control method in the second embodiment may include:
  • 401 ⁇ 405 can be the same as steps 301 ⁇ 305, and will not be described here.
  • 406 ⁇ 409 can be the same as steps 310 ⁇ 313, and will not be described here.
  • the MME sends a handover command message to the ENB, where the handover command message may include CS resource information prepared by the target BSS/RNS.
  • the ENB sends a handover command message to the UE, where the handover command message includes resource information prepared by the target BSS/RNS.
  • the UE accesses the 2G/3G network, and sends a handover complete message to the target BSS/RNS.
  • the target BSS/RNS sends a handover complete message to the target MSC.
  • the target MSC sends a handover complete message to the MSC.
  • the UE initiates a PS service suspension process, and the MME and the SGW suspend the PS service of the UE.
  • the MSC sends a bearer modification request message to the PGW.
  • the bearer modification request carries the VOIP EPS bearer ID of the UE-A, and the MGW pair.
  • the MGW prepares a GTP-U bearer corresponding to UE-A VoIP, and the MSC acquires the VoIP GTP-U F-TEID of the MGW corresponding UE-A from the MGW.
  • the PGW receives the bearer modification request message from the MSC, and updates the GTP-U corresponding to the UE-A VoIP to the MGW.
  • the MSC only separately updates the GTP-U of the VoIP corresponding to the UE-A of the PGW to the MGW, and does not update the GTP-C of the PGW corresponding to the UE-A to the MSC.
  • the MSC sends a PS domain to the CS domain handover complete message to the MME, to notify the MME that the handover is complete.
  • the MSC initiates a location update to the HSS.
  • the MSC obtains the control plane bearer information of the PGW corresponding to the UE-A and the user plane bearer information of the VoIP corresponding to the UE-A of the PGW from the MME, and separately uses the PGW to correspond to the UE-A VoIP by using the bearer modification request message.
  • the user plane carries the update to the MGW, and does not update the control plane bearer of the PGW corresponding to the UE-A to the MSC, and the SGW and the SGSN of the 2G/3G network establish a control plane bearer, and the handover control manner can keep the management node corresponding to the UE- A controls the order of the link, which is conducive to maintaining the voice continuity of the network switching process.
  • a handover control method provided in Embodiment 3 may include:
  • the MME receives the first UE attach request message or the PDN activation request message.
  • the MME obtains address information of the MSC.
  • the MME sends a GTP-C message to the SGW, where the GTP-C message carries the address information of the MSC, and the SGW is triggered to establish a control plane bearer corresponding to the first UE.
  • the SGW After receiving the GTP-C message from the MME, the SGW initiates a process of establishing a control plane bearer corresponding to the first UE with the MSC.
  • another switching control method provided by this embodiment, as shown in FIG. 6, may include:
  • the MSC receives a request from the SGW to establish a first session setup request message corresponding to the control plane bearer of the first UE, and establishes a control plane bearer corresponding to the first UE of the SGW.
  • the MSC obtains address information of the PGW.
  • the MSC sends a second session setup request message to the PGW, and establishes a control plane bearer corresponding to the first UE with the PGW.
  • the PGW After receiving the second session establishment request message from the MSC, the PGW establishes a control plane bearer corresponding to the first UE with the MSC.
  • the MSC is successfully inserted between the SGW and the PGW, and all the packets related to the UE-A that the subsequent SGW and the PGW interact with will pass through the MSC.
  • the method may further include:
  • the MSC receives a PS to CS handover request message from the MME;
  • the MSC sends a bearer modification request message to the PGW, where the bearer modification message carries the user plane bearer information of the VoIP corresponding to the first UE of the MGW;
  • the PGW After receiving the bearer modification request message from the MSC, the PGW updates the user plane bearer corresponding to the VoIP of the first UE to the MGW;
  • the MSC notifies the MGW of the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and updates the user plane bearer of the VOIP corresponding to the first UE of the PGW to the MGW.
  • the MSC sends a bearer modification message to the PGW, where the SGW corresponds to the user plane bearer information of the first UE.
  • the MSC when the first UE initiates the network attachment or the PDN activation, the MSC is inserted between the SGW and the PGW, and the subsequent MSC can offload the VoIP data stream of the first UE to the MGW or directly correspond to the PGW.
  • the user plane bearer of the VoIP of the first UE is updated to the MGW, and the handover control manner can maintain the order of the control node corresponding to the first UE control link, which is beneficial to maintaining the voice continuity of the network handover process.
  • a specific process of inserting the MSC into the SGW and the PGW in the process of initiating the network attachment or the PDN activation in the UE-A is taken as an example for description.
  • the MSC can be inserted into the SGW and the PGW only when connected to a specific service network, such as an IMS APN.
  • the process of inserting the MSC into the SGW and the PGW may include:
  • the UE-A sends an attach (PDN activation) request message to the MME.
  • the UE-A When the UE-A power-on request is attached to the network or a new PDN connection is activated, the UE-A may send an attach (or PDN activation) request message to the MME.
  • the MME obtains an MSC address.
  • one way may be to modify the PGW address corresponding to the IMS APN to the address of the MSC in the DNS.
  • the MME uses the IMS APN to look up the PGW address in the DNS, and the DNS feeds back the address of the MSC to the MME, and the MME obtains the address of the MSC and uses it as the address of the PGW to perform the subsequent process;
  • the address of the MSC and the PGW address corresponding to the IMS APN may be configured in the DNS.
  • the MME uses the IMS APN to look up the PGW address in the DNS, and the DNS feeds back the address of the MSC to the MME.
  • the address of the PGW the MME chooses to obtain the address of the MSC as the address of the PGW for the subsequent process;
  • Another way is to configure the MSC address directly in the MME.
  • the MME uses the address of the MSC as the PGW address for the subsequent process.
  • the MME selects the SGW and sends a GTP-C message to the SGW, where the MME sends the MSC address information, and triggers the SGW to establish a control plane bearer corresponding to the U E-A.
  • the SGW initiates a session establishment procedure corresponding to the UE-A, and sends a session establishment request message to the MSC, requesting to establish a control plane bearer corresponding to the UE-A.
  • the SGW sends the session establishment request message to the MSC by directly using the MSC address as the address of the PGW, and the GW sends the MSC address information instead of the PGW address.
  • the MSC acquires address information of the PGW.
  • the MSC may use the IMS APN to look up the PGW address in the DNS after receiving the session establishment request message from the SGW; the DNS feeds back the real PGW address to the MSC, and the MSC obtains the real PGW address.
  • the PGW address may be directly configured in the MSC.
  • the MSC directly obtains the PGW address from the local configuration information.
  • the MME may send the obtained real PGW address to the MSC through the SGW.
  • the MSC sends a session establishment request message to the PGW according to the searched PGW address, and requests to establish a control plane bearer corresponding to the UE-A.
  • the PGW receives a session establishment request message from the MSC, and establishes a control plane bearer corresponding to the UE-A, and sends a session establishment response message to the MSC.
  • the MSC sends a session establishment response message to the SGW.
  • the MSC is successfully inserted between the SGW and the PGW. All data packets related to UE-A that are exchanged between the subsequent SGW and the PGW pass through the MSC, MSC. It can be controlled or shunted.
  • 801 ⁇ 802 can be the same as steps 301 ⁇ 302, and will not be described here.
  • the MME selects an MSC, and sends a PS to CS handover request message to the MSC.
  • the MME may distinguish which bearers belong to the PS service according to the bearer information, and which bearers belong to the CS service, to initiate the CS service handover and the PS service handover respectively.
  • the MSC selected by the MME is consistent with the MSC corresponding to the location area (LA, Local Area) of the target cell, the inconsistency will result in a cross-MSC handover (Inter MSC handover).
  • 804 ⁇ 805 can be the same as steps 804 ⁇ 804, and will not be described here.
  • the MME sends a handover request message to the SGSN, where the handover request message may include information required for the PS handover, and may specifically include a PDP bearer context of the UE-A, where the PDP bearer context includes the GTP-C F of the MSC corresponding to the UE-A. -TEID.
  • the MSC sends a bearer modification request message to the PGW.
  • the bearer modification request carries the VOIP EPS bearer ID of the UE-A, and the GTP-U F-TEID of the VoIP corresponding to the UE-A of the MGW;
  • the MGW prepares a GTP-U bearer corresponding to UE-A VoIP, and the MSC acquires the VoIP GTP-U F-TEID of the MGW corresponding UE-A from the MGW.
  • the PGW receives the bearer modification request message from the MSC, and updates the GTP-U corresponding to the UE-A VoIP to the MGW.
  • the MSC sends a PS domain to CS domain handover complete message to the MME, to notify the MME that the handover is complete.
  • the MSC initiates a location update to the HSS.
  • the target SGSN sends a handover complete message to the MME, and the MME responds to the acknowledgement message.
  • the SGSN sends a bearer modification request message to the SGW, where the message carries the GTP-C F-TEID of the UE-A corresponding to the SGSN, and updates the control plane bearer corresponding to the UE-A of the SGW to the SGSN;
  • the SGW receives the bearer modification request message sent by the SGSN, and updates the control plane bearer corresponding to the UE-A to the SGSN, and sends a bearer modification request message to the MSC, where the SGW carries the GTP-U F-TEID information corresponding to the UE-A.
  • the MSC receives the bearer modification request message from the SGW, and sends a bearer modification request message to the PGW, where the SGW carries the GTP-U F-TEID information of the UE-A. So far, both the CS service and the PS service of the UE-A are switched to the 2G/3G network, and the control plane bearer corresponding to the UE-A includes the SGSN-SGW-MSC-PGW, which realizes the continuity of the control plane bearer corresponding to the UE-A. .
  • the user plane of the VoIP corresponding to the UE established between the PGW and the MGW carries the GTP-U, and the PGW can send the VoIP data stream of the UE-A to the MGW through the bearer.
  • the SGW and the PGW are based on the PMIP protocol, and the PMIP protocol is a protocol that does not distinguish between the control plane and the data plane bearer, at this time, the user of the UE-A VoIP may not be established between the PGW and the MGW.
  • GTP-U on the surface.
  • the MSC can distinguish the VoIP data stream corresponding to the UE-A from the PMIP tunnel with the PGW and forward it to the MGW, and the other data packets can be transparently transmitted between the SGW and the PGW.
  • the MSC when the UE-A initiates the network attachment or the PDN activation, the MSC is inserted between the SGW and the PGW, and the subsequent MSC can offload the VoIP data stream of the UE-A to the MGW or directly correspond to the PGW.
  • the UE-A VoIP user plane bearer is updated to the MGW.
  • the handover control mode can maintain the order of the UE-A control bearer corresponding to the management node, and is beneficial to maintaining the voice continuity of the network handover process.
  • a handover control method in Embodiment 5 may include:
  • the MME sends a second message to the MSC, where the second message carries the user plane bearer information of the VoIP corresponding to the first UE of the SGW.
  • the user plane bearer information of the VoIP corresponding to the first UE of the SGW includes the GTP-U F-TEID of the VoIP corresponding to the first UE of the SGW.
  • the second message sent by the MME may be, for example, a PS to CS handover request message.
  • the message may also carry other information.
  • the MSC further notifies the MGW of the user plane bearer information of the VoIP corresponding to the first UE by the SGW.
  • the MME receives a third message from the MSC, where the third message carries user plane bearer information of the VoIP corresponding to the first UE of the MGW.
  • the MSC may first obtain the user plane bearer information (including the GTP-U F-TEID) of the VoIP corresponding to the first UE allocated by the MGW, and notify the user of the VoIP of the first UE to the VoIP.
  • MME the user plane bearer information
  • the MME sends a bearer modification message to the SGW, where the bearer modification message carries the MGW corresponding to the first
  • the user plane bearer information of the VoIP of one UE updates the user plane bearer of the VoIP corresponding to the PDCCH of the first UE to the MGW.
  • the SGW After receiving the bearer modification message from the MME, the SGW updates the user plane bearer of the VoIP corresponding to the first UE to the MGW, and then forwards the VoIP data stream of the first UE to the MGW.
  • a handover control method in Embodiment 6 may include:
  • 1001 ⁇ 1002 can be the same as steps 301 ⁇ 302, and will not be described here.
  • the MME selects an MSC, and sends a PS to CS handover request message to the MSC, where the message may carry the VOIP GTP-U F-TEID of the UE-A corresponding to the SGW, and may of course carry other information.
  • the MME may distinguish which bearers belong to the PS service according to the bearer information, and which bearers belong to the CS service, to initiate the CS service handover and the PS service handover respectively.
  • the MSC selected by the MME is consistent with the MSC corresponding to the location area (LA, Local Area) of the target cell, the inconsistency will result in a cross-MSC handover (Inter MSC handover).
  • the MSC sends a GTP-U F-TEID corresponding to the VoIP of the UE-A to the MGW, and updates the user plane bearer of the VOIP corresponding to the first UE to the PGW.
  • 1004 ⁇ 1012 are the same as steps 304 ⁇ 312, and will not be described here.
  • the MSC sends a PS to CS handover request response message to the MME, where the message may include the CS resource information prepared by the target BSS/RNS, and the GTP-U F-TEID of the VoIP corresponding to the VoIP of the UE-A; UE-A VoIP GTP-U bearer, the MSC obtains the MGW corresponding UE-A VoIP GTP-U F-TEID from the MGW;
  • the MME sends a bearer modification request message to the SGW.
  • the bearer modification request carries the VOIP EPS bearer ID of the UE-A, and the GTP-U F-TEID of the VoIP corresponding to the UE-A of the MGW;
  • the SGW receives the tampering request message from the MME, and updates the GTP-U corresponding to the UE-A VoIP to the MGW.
  • the MME may combine the PS resource information and the CS resource information, and the MME sends a handover command message to the ENB, where the handover command message may include the merged resource information.
  • the ENB sends a handover command message to the UE-A, where the handover command message includes a target.
  • Resource information prepared by BSS/RNS;
  • the UE-A accesses the 2G/3G network according to the resource information prepared by the target BSS/RNS, and may send a handover complete message to the target BSS/RNS.
  • the target BSS/RNS may send a handover complete message to the target MSC. Sending a handover complete message to the MSC; the target MSC may further send an ISUP response message to the MSC to complete bearer establishment between the MSCs.
  • the MSC initiates a location update to the HSS.
  • the target SGSN sends a handover complete message to the MME, and the MME responds to the acknowledgement message.
  • the SGSN sends a bearer modification request message to the SGW, where the message carries the GTP-C F-TEID of the UE-A corresponding to the SGSN, and updates the control plane bearer corresponding to the UE-A of the SGW to the SGSN;
  • the SGW receives the bearer modification request message sent by the SGSN, and updates the control plane bearer corresponding to the UE-A to the SGSN.
  • both the CS service and the PS service of the UE-A are switched to the 2G/3G network, and the SGW corresponding UE-A only establishes the control plane bearer with the SGSN, and does not establish a control plane bearer with the MSC.
  • a handover control method in Embodiment 7 may include:
  • the MME sends a fourth message to the MSC, where the fourth message carries the user plane bearer information of the VoIP corresponding to the first UE of the SGW.
  • the user plane bearer information of the VoIP corresponding to the first UE of the SGW includes the GTP-U F-TEID of the VoIP corresponding to the first UE by the SGW.
  • the fourth message sent by the MME may be, for example, a PS to CS handover request message, and of course, the message may carry other information.
  • the MSC further notifies the MGW of the user plane bearer information of the VoIP corresponding to the first UE by the SGW.
  • the MME receives a fifth message from the MSC, where the fifth message carries information about the user plane of the VoIP corresponding to the first UE of the MGW.
  • the MSC may first obtain the user plane bearer information (including the GTP-U F-TEID) of the VoIP corresponding to the first UE allocated by the MGW, and notify the MME of the user plane bearer information.
  • the MME sends a bearer modification message to the SGW, where the user plane information of the VoIP corresponding to the first UE allocated by the MGW is included. 1130.
  • the MME sends a sixth message to the SGSN, where the sixth message carries the user plane bearer information of the VoIP corresponding to the VoIP of the first UE.
  • the sixth message sent by the MME may be, for example, a handover request message.
  • the message may further carry other information.
  • the SGSN may update the user plane bearer of the VoIP corresponding to the VoIP of the first UE to the MGW in the process of initiating the bearer modification to the SGW.
  • This implementation provides another handover control method from the perspective of the processing of the SGSN, and may include:
  • the SGSN receives the sixth message from the MME, where the sixth message carries the user plane bearer information of the VoIP corresponding to the first UE of the MGW.
  • the SGSN sends a bearer modification message to the SGW, and the bearer modification message carries the user plane bearer information of the VoIP corresponding to the first UE of the MGW, and updates the user plane bearer of the VoIP corresponding to the first UE to the MGW.
  • the SGW receives the bearer modification message from the SGSN, and updates the user plane bearer corresponding to the VoIP of the first UE to the MGW.
  • the SGSN updates the VoIP bearer of the SGW to the first UE to the MGW.
  • the target 2G/3G supports PS switching.
  • a handover control method in Embodiment 8 may include:
  • the MME selects an MSC, and sends a PS to CS handover request message to the MSC, where the message may carry the GTP-U F-TEID of the UE-A corresponding to the SGW, and may of course carry other information.
  • the MME may distinguish which bearers belong to the PS service according to the bearer information, and which bearers belong to the CS service, to initiate the CS service handover and the PS service handover respectively.
  • the MSC selected by the MME is consistent with the MSC corresponding to the location area (LA, Local Area) of the target cell, the inconsistency will result in a cross-MSC handover (Inter MSC handover).
  • the MSC notifies the MME of the GTP-U F-TEID of the MGW corresponding to the UE-A.
  • the MGW prepares a GTP-U bearer corresponding to the UE-A, and the MSC obtains the GTP-U F-TEID of the MGW corresponding to the UE-A from the MGW.
  • the MSC also notifies the MGW of the VoIP GTP-U F-TEID corresponding to the UE-A of the SGW. 1207.
  • the MME sends a handover request message to the SGSN, where the handover request message may include information required for the PS handover, and specifically carries information such as the GTP-U F-TEID of the UE-A corresponding to the MGW.
  • the PS transparent container may be used to carry information required for the foregoing PS handover, such as a target ID required for PS handover;
  • the SGSN sends a handover request message to the target BSS/RNS, indicating that the target BSS/RNS prepares the PS resource.
  • the target BSS/RNS determines that the PS resource is sufficient, the target BSS/RNS prepares the PS resource, and returns a handover request response message to the SGSN, where the prepared PS resource information is carried;
  • the SGSN returns a handover request response message to the MME, where the handover response message includes PS resource information prepared by the target BSS/RNS.
  • the PS resource information prepared by the target BSS/RNS may include: a PS service air interface channel, a system message, and the like, and may be encapsulated in a PS transparent container, following an existing 2G/3G network CS domain specification.
  • the SGSN finds that the SGW is changed, the SGSN acquires a new GTP-U F-TEID that is allocated by the SGSN to the VoIP bearer of the UE-A, and the handover request response message returned by the SGSN to the MME carries the new SGW as the UE.
  • -A VoIP bearer allocates new GTP-U F-TEID information.
  • the MME allocates a new GTP-U F-TEID allocated by the SGSN to the VoIP bearer of the UE-A and notifies the MSC, and the MSC can allocate the new SGW to the VoIP bearer of the UE-A.
  • the GTP-U F-TEID is notified to the MGW.
  • a user plane bearer corresponding to the UE-A VoIP is established between the MGW and the SGW, and the subsequent SGW can send the UE-A VoIP data stream to the MGW based on the user plane bearer. .
  • the target BSS/RNS After receiving the handover request message from the target MSC, if the target BSS/RNS determines that the CS resource is sufficient, the target BSS/RNS prepares the CS resource, and feeds back a handover request response message to the target MSC, where the message may include the target BSS.
  • CS resource information prepared by /RNS;
  • the target MSC sends an inter-MSC handover response to the MSC, where the message may include CS resource information prepared by the target BSS/RNS.
  • a bearer is established between the MSC and the target MSC.
  • the MSC determines that the target MSC is itself, the interaction between the MSC and the target MSC is omitted, and the MSC directly sends a handover request message to the target BSS/RNS, indicating that the target BSS/RNS prepares CS resources;
  • the target BSS/RNS prepares the CS resource, and feeds back a handover request response message to the MSC, where the message may include CS resource information prepared by the target BSS/RNS.
  • the MSC further triggers the IMS domain to perform session domain conversion; the IMS may notify the calling peer to update the media plane to the media gateway of the CS domain, and release the LTE access network session.
  • the MSC sends a PS to CS handover request response message to the MME, where the message may include CS resource information prepared by the target BSS/RNS.
  • the CS resource information prepared by the target BSS/RNS may include: a CS voice service, an air interface dedicated channel, and a system message, etc., which may be encapsulated in a CS transparent container and conform to the existing 2G/3G network CS domain specification.
  • steps 1203 ⁇ 1204, 1210 ⁇ 1214 can be considered as the CS switching preparation phase of UE-A. It can be understood that there is no necessary sequence between the PS switching preparation and the CS switching preparation, for example, it can be performed simultaneously.
  • the MSC sends a modify bearer request message to the SGW, where the message carries the GTP-U F-TEID of the UE-A corresponding to the MGW and the VOIP EPS bearer ID of the UE-A.
  • the SGW receives the bearer modification request message from the MSC, and updates the GTP-U corresponding to the UE-A VoIP to the MGW.
  • the step 1214 may not be performed.
  • the MSC only updates the GTP-U of the SGW corresponding to the UE-A VoIP to the MGW, and does not update the GTP-C corresponding to the UE-A to the MSC.
  • the MME may combine the received PS resource information and the CS resource information, and the MME sends a handover command message to the ENB, where the handover command message may include the merged resource information.
  • the ENB sends a handover command message to the UE-A, where the handover command message includes resource information prepared by the target BSS/RNS.
  • the UE-A accesses the 2G/3G network according to the resource information prepared by the target BSS/RNS, and may send a handover complete message to the target BSS/RNS.
  • the target BSS/RNS may send a handover complete message to the target MSC. Sending a handover complete message to the MSC; the target MSC may further send an ISUP response message to the MSC to complete bearer establishment between the MSCs.
  • the MSC sends a PS domain to the CS domain handover complete message to the MME, to notify the MME that the handover is complete.
  • the MSC initiates a location update to the HSS.
  • the target SGSN sends a handover complete message to the MME, and the MME responds to the acknowledgement message.
  • the SGSN sends a bearer modification request message to the SGW, where the message carries the SGSN corresponding The GTP-C F-TEID of UE-A and the obtained MGW correspond to the GTP-U F-TEID of UE-A.
  • the SGW receives the bearer modification request message sent by the SGSN, updates the control plane bearer corresponding to the UE-A to the SGSN, and updates the VoIP bearer corresponding to the UE-A of the SGW to the MGW.
  • the SGSN determines that the SGW has changed, the SGSN sends a session establishment request message to the SGW, where the message carries the GTP-C F-TEID of the UE-A corresponding to the SGSN and the obtained GTPU F-TEID of the UE-A corresponding to the MGW. ;
  • the SGW receives the session establishment request message from the SGSN, establishes the control plane bearer corresponding to the UE-A to the SGSN, and establishes the VoIP bearer corresponding to the UE-A of the SGW to the MGW.
  • Another switching control method in this embodiment may include:
  • 1301 ⁇ 1302 can be the same as steps 301 ⁇ 302, and will not be described here.
  • the MME selects an MSC, and sends a PS to CS handover request message to the MSC, where the message may carry the VOIP EPS bearer ID of the UE-A, and the GTP-C F-TEID and the GTP-U F- of the UE-A corresponding to the SGW.
  • TEID can carry other information.
  • the MME may distinguish which bearers belong to the PS service according to the bearer information, and which bearers belong to the CS service, to initiate the CS service handover and the PS service handover respectively.
  • the MSC selected by the MME is consistent with the MSC corresponding to the location area (LA, Local Area) of the target cell, the inconsistency will result in a cross-MSC handover (Inter MSC handover).
  • 1304 ⁇ 1305 can be the same as steps 304 ⁇ 305.
  • the MSC notifies the MME of the GTP-U F-TEID of the UE-A corresponding to the MGW.
  • the MGW prepares a GTP-U bearer corresponding to the UE-A, and the MSC obtains the GTP-U F-TEID of the MGW corresponding to the UE-A from the MGW.
  • 1307 ⁇ 1310 can be the same as steps 310 - 313;
  • the MSC sends a bearer modification request message to the SGW, where the message carries the GTP-U F-TEID of the UE-A corresponding to the MGW and the VOIP EPS bearer ID of the UE-A;
  • the SGW receives the bearer modification request message from the MSC, and updates the GTP-U corresponding to the UE-A VoIP to the MGW.
  • step 1214 may not be performed.
  • the MSC only updates the GTP-U of the SGW corresponding to the UE-A VoIP to the MGW, and does not update the GTP-C corresponding to the UE-A to the MSC.
  • the MME sends a handover command message to the ENB, where the handover command message may include CS resource information prepared by the target BSS/RNS.
  • the ENB sends a handover command message to the UE-A, where the handover command message includes resource information prepared by the target BSS/RNS.
  • the UE-A accesses the 2G/3G network according to the resource information prepared by the target BSS/RNS, and may send a handover complete message to the target BSS/RNS.
  • the UE-A sends a location update message to the target SGSN to initiate a location update.
  • the target SGSN sends a context request message corresponding to the UE-A to the MME, requesting to acquire context information of the UE-A.
  • the MME sends a context response message corresponding to the UE-A to the SGSN, where the MME carries the context information of the UE-A and the GTP-U F-TEID information of the UE-A corresponding to the MGW.
  • the SGSN sends a bearer modification request message to the SGW, where the message carries the GTP-C F-TEID of the UE-A corresponding to the SGSN and the GTP-U F-TEID of the obtained UE-A corresponding to the MGW.
  • the SGW receives the bearer modification request message sent by the SGSN, updates the control plane bearer corresponding to the UE-A to the SGSN, and updates the VoIP bearer corresponding to the UE-A of the SGW to the MGW.
  • the SGW may send a bearer modification response message to the SGSN, where the SGW carries the GTP-U F-TEID of the VoIP corresponding to the UE-A; the SGW sends a bearer modification request message to the PDW, and updates the related bearer;
  • the SGSN sends a context response confirmation message to the MME, where the SGW carries the GTP-U F-TEID of the VoIP of the UE-A. If the SGW changes, the new SGW corresponds to the GTP-U F-TEID of the UE-A and is fed back to the MSC through the MME.
  • the MME notifies the MSC of the obtained GGW-U F-TEID of the VoIP of the UE-A to the MSC;
  • the MSC further sends the GTP-U F-TEID of the VoIP corresponding to the UE-A to the MGW, and the user plane of the VoIP corresponding to the UE-A between the MGW and the SGW is established bidirectionally.
  • the target BSS/RNS may send a handover complete message to the target MSC; the target MSC may send a handover complete message to the MSC; the target MSC may further send an ISUP response message to the MSC to complete the bearer establishment between the MSCs.
  • the MSC sends a PS domain to the CS domain handover complete message to the MME, to notify the MME that the handover is complete. 1323.
  • the MSC initiates location update to the HSS.
  • both the CS service and the PS service of the UE-A are switched to the 2G/3G network, and the SGW corresponding UE-A only establishes a control plane bearer with the SGSN, and does not establish a control plane bearer with the MSC.
  • the MGW can also obtain information such as the codec of the VOIP, the packet interval, and the value of the RTP payload type before the session transfer is completed. These parameters can be obtained by modifying the session transfer process. Specifically, the MSC sends an INVITE message to the SCC AS; the SCC AS sends the SDP parameter of the VOIP to the MSC, and the MSC sends the parameters to the MGW. The MSC then sends a RE-INVITE or UPDATE message to the SCC AS, and the SCC AS performs a remote update operation.
  • an embodiment of the present invention further provides an apparatus for implementing the foregoing solution.
  • the mobile switching center 1400 of the ninth embodiment may include: a receiving module 1410, a sending module 1420, and a notifying module 1430.
  • the receiving module 1410 is configured to receive a first message from the mobility management entity MME, where the first message carries the VoIP EPS bearer ID of the first user equipment, the control data bearer information corresponding to the first UE of the packet data gateway PGW, and the PGW corresponding to the first message.
  • the sending module 1420 is configured to send, according to the control plane bearer information of the PGW corresponding to the first UE, a bearer modification request message to the PGW, where the bearer modification request message carries the VoIP EPS bearer ID of the first user equipment and the media gateway MGW corresponding to the first User plane bearer information of the VoIP of the UE, and updating the user plane bearer corresponding to the VOIP of the first UE to the MGW;
  • the notification module 1430 is configured to notify the MGW of the user plane bearer information of the VoIP corresponding to the first UE by the PGW, and update the user plane bearer of the VOIP corresponding to the first UE by the MGW to the PGW.
  • a mobility management entity 1500 of Embodiment 10 may include: a receiving module 1510, an obtaining module 1520, and a sending module 1530.
  • the receiving module 1510 is configured to receive an attach request message or a PDN activation request message from the first UE.
  • the obtaining module 1520 is configured to obtain address information of the MSC.
  • the sending module 1530 is configured to send a GTP-C message to the SGW, where the GTP-C message carries the address information of the MSC, and triggers the SGW to establish a control plane bearer corresponding to the first UE with the MSC.
  • a mobile switching center 1600 of Embodiment 11 may include: a first receiving module 1610, an obtaining module 1620, and a first sending module 1630.
  • the first receiving module 1610 is configured to receive a first session setup request message from the SGW to establish a control plane bearer corresponding to the first UE, and establish a control plane bearer corresponding to the first UE of the SGW.
  • the acquiring module 1620 is configured to be used by the MSC. Obtain the address information of the PGW;
  • the first sending module 1630 is configured to send a second session setup request message to the PGW, and establish a control plane bearer corresponding to the first UE with the PGW.
  • the mobile switching center 1600 can also include:
  • a second receiving module which receives a packet domain exchange from the corresponding first UE of the MME to a circuit switched domain handover message
  • a second sending module configured to send a bearer modification request message to the PGW, where the second bearer modification message carries user plane bearer information of the VoIP corresponding to the first UE of the MGW;
  • the notification module is configured to notify the MGW of the user plane bearer information of the VoIP corresponding to the first UE by the PGW, and update the user plane bearer of the VOIP corresponding to the first UE by the PGW to the MGW.
  • a mobility management entity 1700 of Embodiment 12 may include: a third sending module 1710, configured to send a second message to the MSC, where the second message carries a user plane bearer corresponding to the VoIP of the first UE by the SGW.
  • a third sending module 1710 configured to send a second message to the MSC, where the second message carries a user plane bearer corresponding to the VoIP of the first UE by the SGW.
  • the receiving module 1720 is configured to receive a third message from the MSC, where the third message carries information about the user plane of the VoIP corresponding to the first UE of the MGW;
  • the fourth sending module 1730 is configured to send a bearer modification message to the SGW, where the bearer modification message carries the user plane bearer information of the VoIP corresponding to the VoIP of the first UE, and updates the user plane of the VoIP corresponding to the first UE to the MGW.
  • a mobility management entity 1800 of Embodiment 13 may include: a fifth sending module 1810, configured to send a fourth message to the MSC, where the fourth message carries a user plane bearer corresponding to the VoIP of the first UE by the SGW. information;
  • the third receiving module 1820 is configured to receive a fifth message from the MSC, where the fifth message carries user plane bearer information of the VoIP corresponding to the first UE by the MGW;
  • the sixth sending module 1830 is configured to send, by the MME, a sixth message to the SGSN, where the sixth message carries the user plane bearer information of the VoIP corresponding to the first UE by the MGW.
  • an SGSN 1900 of Embodiment 14 includes:
  • the receiving module 1910 is configured to receive a sixth message from the MME, where the sixth message carries user plane bearer information of the VoIP of the MGW corresponding to the first UE.
  • the sending module 1920 is configured to send a bearer modification message to the SGW, where the bearer modification message carries the user plane bearer information of the VoIP corresponding to the first UE of the MGW, and updates the user plane bearer of the VoIP corresponding to the first UE to the MGW.
  • ROM Read Only Memory
  • RAM Random Access Memory
  • CD Compact Disc

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention porte sur un procédé, un dispositif et un système de commande de transfert. Le procédé comprend les étapes suivantes : un centre de commutation mobile (MSC) reçoit le premier message provenant d'une entité de gestion de mobilité (MME), le premier message contenant un identifiant (ID) de support de système par paquets évolué (EPS) de communication par voix sur protocole Internet (VoIP) du premier équipement utilisateur (UE), des informations de support de plan de commande du premier UE correspondant à une passerelle de réseau de données par paquets (PGW) et des informations de support de plan utilisateur de la communication VoIP du premier UE correspondant à la PGW (210); conformément aux informations de support de plan de commande du premier UE correspondant à la PGW, un message de requête de modification de support est envoyé à la PGW, et le message de requête de modification de support contient l'ID de support EPS de la communication VoIP du premier UE et des informations de support de plan utilisateur de la communication VoIP du premier UE correspondant à une passerelle multimédia (MGW), et le support de plan utilisateur de la communication VoIP du premier UE correspondant à la PGW est mis à jour par le support de plan utilisateur de la communication VoIP du premier UE correspondant à la MGW (220); les informations de support de plan utilisateur de la communication VoIP du premier UE correspondant à la PGW sont notifiées à la MGW, et le support de plan utilisateur de la communication VoIP du premier UE correspondant à la MGW est mis à jour par le support de plan utilisateur de la communication VoIP du premier UE correspondant à la PGW (230). La présente invention est bénéfique au maintien de la continuité vocale durant le transfert de réseau.
PCT/CN2011/070147 2010-01-13 2011-01-10 Procédé, dispositif et système de commande de transfert Ceased WO2011085668A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010004249.1 2010-01-13
CN201010004249.1A CN102131259B (zh) 2010-01-13 2010-01-13 切换控制方法和相关设备及系统

Publications (1)

Publication Number Publication Date
WO2011085668A1 true WO2011085668A1 (fr) 2011-07-21

Family

ID=44269125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070147 Ceased WO2011085668A1 (fr) 2010-01-13 2011-01-10 Procédé, dispositif et système de commande de transfert

Country Status (2)

Country Link
CN (1) CN102131259B (fr)
WO (1) WO2011085668A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114143793A (zh) * 2017-10-27 2022-03-04 Sk电信有限公司 在异构网络系统中提供服务的系统和接收服务的终端设备

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103298050A (zh) * 2012-02-29 2013-09-11 中兴通讯股份有限公司 语音业务的切换方法及装置
US9596628B2 (en) * 2013-10-31 2017-03-14 Intel Corporation Gateway arrangements for wireless communication networks
WO2018040232A1 (fr) * 2016-08-29 2018-03-08 华为技术有限公司 Procédé et dispositif de commutation
EP3506677B1 (fr) * 2016-09-30 2021-03-31 Huawei Technologies Co., Ltd. Procédé et dispositif d'établissement de support
WO2018058699A1 (fr) * 2016-09-30 2018-04-05 华为技术有限公司 Procédé et dispositif de commutation
CN106792936B (zh) * 2016-12-08 2020-04-03 上海华为技术有限公司 一种保持业务连续性的pgw切换方法及通信设备
WO2019071877A1 (fr) * 2017-10-13 2019-04-18 华为技术有限公司 Procédé de commutation vocale et dispositif associé
CN110167079B (zh) * 2018-02-12 2020-08-25 华为技术有限公司 承载处理方法、设备及系统
TWI704819B (zh) * 2019-10-05 2020-09-11 財團法人工業技術研究院 維持傳輸服務連續性的方法及服務中心

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291454A (zh) * 2007-04-17 2008-10-22 华为技术有限公司 实现语音会话的方法、语音连续性的方法及通信系统
CN101384081A (zh) * 2007-09-07 2009-03-11 华为技术有限公司 传递业务锚定点信息的方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291454A (zh) * 2007-04-17 2008-10-22 华为技术有限公司 实现语音会话的方法、语音连续性的方法及通信系统
CN101384081A (zh) * 2007-09-07 2009-03-11 华为技术有限公司 传递业务锚定点信息的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS", 3GPPTS 23.216 V9.2.0: SINGLE RADIO VOICE CALL CONTINUITY (SRVCC); STAGE 2. 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 10 December 2009 (2009-12-10), pages 24 - 25 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114143793A (zh) * 2017-10-27 2022-03-04 Sk电信有限公司 在异构网络系统中提供服务的系统和接收服务的终端设备

Also Published As

Publication number Publication date
CN102131259B (zh) 2013-06-05
CN102131259A (zh) 2011-07-20

Similar Documents

Publication Publication Date Title
CN102238676B (zh) 电路交换域到分组交换域的切换方法和设备及通信系统
US10674420B2 (en) Method, apparatus, and system for routing user plane data in mobile network
WO2011085668A1 (fr) Procédé, dispositif et système de commande de transfert
US8948127B2 (en) Method, apparatus and computer program for supporting a session identifier in case of a transfer between different radio access networks
US10708827B2 (en) Method and nodes for handling a UE which has moved from an old location to a new location
CN101291453B (zh) 一种实现会话的语音连续性的方法及装置
JP6184406B2 (ja) Ｕｔｌａｎからｌｔｅへの（ｒｓｒｖｃｃ）ハンドオーバ
CN101370261B (zh) 从cs域向ps域切换的资源准备方法及通信设备
WO2009024082A1 (fr) Procédé de transfert et procédé de relocalisation de terminal
WO2011006440A1 (fr) Procédé et dispositif de commutation
JP2013514705A (ja) Ｇｓｍ回線交換呼を確立する場合のｌｔｅにおけるパケット交換セッションの維持
CN102387557A (zh) 反向单一无线语音呼叫连续性的处理方法、设备及系统
WO2009026830A1 (fr) Réseau d'accès générique et procédé de réalisation de service utilisant le réseau d'accès générique
CN103313321A (zh) 一种将ue的ims话音通过ps域提供的能力通知ue的方法
WO2011143997A1 (fr) Procédé et dispositif de routage
WO2010105525A1 (fr) Procédé optimisé de transfert, dispositif et système de transfert
WO2010022611A1 (fr) Procédé, système et centre de commutation mobile destinés à un commutateur à continuité d’appel vocal
WO2009092260A1 (fr) Procédé, entité fonctionnelle d'interconnexion et équipement terminal pour réaliser la continuité d'un appel vocal
CN101978727B (zh) 单接收机语音连续切换及其数据传输的方法、装置和系统
WO2009149656A1 (fr) Procédé, dispositif et système permettant la mise en œuvre d'un transfert de service
CN111629406B (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
TW202101948A (zh) 支援網際網路協定多媒體子系統信令之方法及使用者設備
WO2013185618A1 (fr) Procédé, système et dispositif pour la transmission de données sur le plan usager
CN103329598B (zh) 分组数据网连接处理方法及系统、锚点设备和用户设备
WO2011023054A1 (fr) Procédé et système de synchronisation pour capacité multisession dans le sous-système multimédia ip (ims) de réseau d'infrastructure

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11732658

Country of ref document: EP

Kind code of ref document: A1