WO2016029479A1 - Procédé de commutation de porteuse de service vocal, appareil et système adaptés - Google Patents

Procédé de commutation de porteuse de service vocal, appareil et système adaptés Download PDF

Info

Publication number
WO2016029479A1
WO2016029479A1 PCT/CN2014/085632 CN2014085632W WO2016029479A1 WO 2016029479 A1 WO2016029479 A1 WO 2016029479A1 CN 2014085632 W CN2014085632 W CN 2014085632W WO 2016029479 A1 WO2016029479 A1 WO 2016029479A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility management
management entity
service bearer
handover request
handover
Prior art date
Application number
PCT/CN2014/085632
Other languages
English (en)
Chinese (zh)
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 CN201480021489.9A priority Critical patent/CN105900484B/zh
Priority to PCT/CN2014/085632 priority patent/WO2016029479A1/fr
Publication of WO2016029479A1 publication Critical patent/WO2016029479A1/fr

Links

Images

Classifications

    • 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

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method, a related device, and a system for switching a voice service bearer.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • 3GPP The 3rd Generation Partnership Project
  • the long-term goal of LTE is to simplify and redesign the network architecture to become an IP network.
  • LTE's Evolved Packet Core (EPC) network is the core network of 4G technology.
  • LTE/EPC can implement all-IP bearers, flatten the network, control and bearer separation, and reduce the cost per bit of bearer.
  • the coverage area of the LTE/EPC network is relatively limited.
  • the voice service bearer of the terminal needs to be handed over from the LTE/EPC network to other networks.
  • SRVCC technology Single Radio Voice Call Continuity
  • the terminal usually has a data service in the LTE/EPC network
  • the SRVCC technology is used to switch the voice service bearer of the terminal
  • the data service bearer of the terminal is also switched.
  • the simultaneous switching of the voice service bearer and the data service bearer can be referred to as dual handover.
  • the present invention provides a method for switching a voice service bearer, a related device, and a system, which solves the problem of low handover success rate of a voice service bearer in the prior art by converting a dual handover request into a single handover request.
  • the specific plan is as follows:
  • the application provides a method for switching a voice service bearer, including:
  • the mobility management entity acquires a dual handover request sent by the evolved base station, where the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal;
  • the mobility management entity determines that the data service bearer cannot be successfully switched
  • the mobility management entity converts the dual handover request into a single handover request, where the single handover request is used to request to switch the voice service bearer;
  • the mobility management entity sends the single handover request to a mobile switching center.
  • the determining, by the mobility management entity, that the data service bearer cannot be successfully switched includes:
  • the mobility management entity determines that the mobility management entity does not support data traffic bearer switching.
  • the mobility management entity determines that the data service bearer cannot be successfully switched, including:
  • the mobility management entity determines that the target general packet radio service technology GPRS service support node does not support data traffic bearer handover.
  • the determining, by the mobility management entity, that the data service bearer cannot be successfully switched includes:
  • the mobility management entity determines that the link required to switch the data traffic bearer is faulty.
  • the mobility management entity determines that the mobility management entity does not support data service bearer switching, including:
  • the mobility management entity determines that the terminal is a cardless emergency call user and determines that the mobility management entity does not support cardless emergency call user handover.
  • the mobile management entity determines that the mobility management entity does not support data service bearer switching, including:
  • the mobility management entity determines that the mobility management entity does not support 2G or 3G packet switched PS handover;
  • the mobility management entity determines that the mobility management entity does not support a single wireless voice call continuity SRVCC dual handover.
  • the mobile management entity determines that the target GPRS service support node does not support the data service bearer switching, including:
  • the mobility management entity determines that the mobility management entity cannot successfully resolve the domain name of the target GPRS service support node.
  • the mobile management entity determines that the target GPRS service support node does not support the data service bearer handover, including:
  • the mobility management entity determines that the version of the GPRS tunneling protocol control plane of the target GPRS service support node does not support data traffic bearer switching.
  • the dual handover request includes a first identifier, where the first identifier is used to indicate that the handover request type is a dual handover type; Converting the dual handover request to a single handover request includes:
  • the mobility management entity modifies the first identifier in the dual handover request to a second identifier, where the second identifier is used to indicate that the handover request type is a single handover type.
  • the IU instance number in the source-to-target transparent container in the dual handover request has a field value of 2;
  • the mobility management entity Modifying the first identifier in the dual handover request to the second identifier includes:
  • the mobility management entity modifies a field value of the Number of Iu Instances field in the source-to-target transparent container in the dual handover request from 2 to 1.
  • the application provides an apparatus for switching a voice service bearer, including:
  • An acquiring unit configured to acquire a dual handover request sent by the evolved base station, where the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal;
  • a determining unit configured to determine that the data service bearer cannot be successfully switched
  • a converting unit configured to convert the dual handover request into a single handover request, where the single handover request is used to request to switch the voice service bearer;
  • a sending unit configured to send the single handover request to the mobile switching center.
  • the determining unit is specifically configured to:
  • the determining unit is specifically configured to:
  • the determining unit is specifically configured to:
  • the determining unit is specifically configured to:
  • the determining unit is specifically configured to:
  • the mobility management entity does not support single wireless voice call continuity SRVCC dual handover.
  • the determining unit is specifically configured to:
  • the determining unit is specifically configured to:
  • the dual handover request includes a first identifier, where the first identifier is used to indicate that the handover request type is a dual handover type; Used for:
  • the number of IU instances in the source-to-target transparent container in the dual handover request has a field value of 2; the conversion unit, Specifically used for:
  • the field value of the Number of Iu Instances field in the source-to-target transparent container in the double switch request is modified from 2 to 1.
  • the application provides a system for switching a voice service bearer, where the system includes an evolved base station and a mobility management entity;
  • the evolved base station is configured to send a dual handover request to the mobility management entity; the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal;
  • the mobility management entity is configured to acquire the dual handover request; determine that the data service bearer cannot be successfully switched; convert the dual handover request into a single handover request, where the single handover request is used to request the voice service
  • the bearer performs handover; the single handover request is sent to the mobile switching center.
  • the application provides another system for switching a voice service bearer, where the system includes a mobility management entity and a mobile switching center;
  • the mobility management entity is configured to acquire a dual handover request sent by the evolved base station, where the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal; and determine that the data service bearer cannot be successfully switched;
  • the double handover request is converted into a single handover request, where the single handover request is used to request to switch the voice service bearer; and the single handover request is sent to the mobile switching center;
  • the mobile switching center is configured to receive the single handover request.
  • the system further includes an evolved base station, where the evolved base station is configured to send the dual handover request to the mobility management entity.
  • the application provides an apparatus for switching a voice service bearer, including: a processor, a memory, a bus, and a communication interface;
  • the memory is configured to store a computer to execute instructions
  • the processor is coupled to the memory via the bus, and when the device for switching a voice service bearer is executed, the processor executes the memory storage
  • the computer executes instructions to cause the processor to perform the aforementioned method of switching a voice service bearer.
  • the application provides a computer readable medium, including a computer executing instruction, when the processor of the computer executes the computer execution instruction, the computer performs the foregoing The switching method of voice service bearer.
  • the method, the related device and the system for switching the voice service bearer of the present application after receiving the double handover request that needs to switch the voice service bearer and the data service bearer of the terminal, determine the The data service bearer cannot be successfully switched, and the dual handover request is converted into a single handover request indicating that the voice service bearer needs to be switched, and the single handover request is sent to the mobile switching center, so that the voice service bearer can be continued. That is, in this embodiment, when the system is capable of performing the switching of the voice service bearer, but the data service bearer switching cannot be completed, the voice service bearer can still be switched, and the problems in the prior art are solved. Lift The handover success rate of the voice service bearer is high.
  • the main purpose of voice services is to implement voice calls between terminals, such as making calls. Calling is the most basic function of the terminal (mobile phone). Priority is given to ensuring that this feature is implemented and can enhance the user experience.
  • FIG. 1 is a flowchart of a method for switching a voice service bearer according to an embodiment of the present invention
  • FIG. 2 is a flowchart of still another method for switching a voice service bearer according to an embodiment of the present invention
  • FIG. 3 is a flowchart of still another method for switching a voice service bearer according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of an apparatus for switching a voice service bearer according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another apparatus for switching a voice service bearer according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for switching a voice service bearer according to an embodiment of the present invention. As shown in FIG. 1, the method can include:
  • Step 101 The mobility management entity acquires a dual handover request sent by the eNodeB eNodeB.
  • the dual handover request indicates that the voice service bearer and the data service bearer of the terminal need to be switched.
  • the eNodeB may send a measurement signal to the terminal, and the terminal may generate a measurement report based on the measurement signal and feed back to the eNodeB.
  • the measurement report may include information such as the received signal strength of the terminal.
  • the eNodeB may analyze, according to the measurement report, whether the current channel condition of the terminal is good.
  • the dual handover request may be sent to the mobility management entity.
  • the voice service mainly refers to a service in which a terminal performs a voice call through a mobile network
  • the data service mainly refers to a service in which a terminal transmits a packet through a mobile network; and at the same time, a voice service bearer and a data service bearer are switched, which may be called Double switching.
  • Step 102 The mobility management entity determines that the data service bearer cannot be successfully switched.
  • the network element involved in the data service bearer handover may include: a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), and the like.
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • the mobility management entity may determine whether the data service bearer can be successfully switched. When the mobility management entity determines that the data service bearer cannot be successfully switched, step 103 may be further performed, so that the voice service bearer can be subsequently switched.
  • Step 103 The mobility management entity converts the dual handover request into a single handover request indicating that a voice service bearer needs to be switched.
  • the dual handover request may be converted into a single handover request indicating that the voice service bearer needs to be switched, to solve the problem in the prior art.
  • the voice service bearer cannot be switched.
  • Step 104 The mobility management entity sends the single handover request to a mobile switching center.
  • the mobile switching center may complete the handover of the voice service bearer by using a subsequent step.
  • the handover process of the data service bearer in the dual handover is mainly: the MME sends a Forward Relocation Request message to the target SGSN, and the target SGSN receives the Forward Relocation Request message sent by the MME, and then sends the Forward Relocation Request message to the radio network controller (Radio).
  • the Network Controller (RNC) sends a Relocation Request message to request the RNC to allocate Packet Switching (PS) resources.
  • PS resource is a resource used to carry data services after handover.
  • the handover process of the voice service bearer in the dual handover is mainly: the mobile switching center (Mobile The Switching Center (MSC) sends a Relocation Request message to the RNC to request the RNC to allocate Circuit Switch (CS) resources.
  • the CS resource is a resource used to carry the voice service after the handover.
  • the RNC is configured to respond to the Relocation Request message sent by the SGSN first, and then respond to the Relocation Request message sent by the MSC. Therefore, when the RNC fails to receive the Relocation Request message, the RNC cannot respond to the Relocation Request message sent by the MSC in time, and the handover of the voice service bearer fails. In this case, even if the corresponding network element device has the capability of supporting the handover of the voice service bearer, the voice service bearer cannot be successfully switched.
  • the voice service bearer may continue to be performed by converting the dual handover request to a single handover request indicating that the voice service bearer needs to be handed over when the data service bearer cannot be successfully switched.
  • the voice service bearer can still be switched, which solves the problems in the prior art and improves.
  • the switching success rate of the voice service bearer is to implement voice calls between terminals, such as making calls. Calling is the most basic function of the terminal (mobile phone). Priority is given to ensuring that this feature is implemented and can enhance the user experience.
  • FIG. 2 is a flowchart of still another method for switching a voice service bearer according to an embodiment of the present invention. As shown in FIG. 2, the method may include:
  • Step 201 The mobility management entity acquires the dual handover request sent by the eNodeB.
  • the dual handover request indicates that the voice service bearer and the data service bearer of the terminal need to be switched.
  • Step 202 The mobility management entity determines that the mobility management entity does not support data service bearer handover; or the mobility management entity determines that the target SGSN does not support data service bearer handover; or the mobility management entity determines the data The link required for the service bearer to perform the handover is faulty.
  • the mobility management entity does not support the data service bearer handover; or the target SGSN does not support the data service bearer handover; or the link required to switch the data service bearer exists If the fault occurs, the data service bearer handover cannot be successfully switched, for example, if the GTP-C link between the MME and the target SGSN, or the general packet radio service technology between the target SGSN and the RNC (General Packet)
  • the radio service, GPRS) tunnel protocol control plane (GTP-C) link is faulty, which prevents data service bearer switching.
  • the double handover request may be converted into a single handover request indicating that the voice service bearer of the terminal needs to be switched.
  • the target SGSN may be an SGSN that needs to receive a Forward Relocation Request sent by the mobility management entity when performing data service bearer handover.
  • the mobility management entity may determine, according to the software configuration information of the target SGSN, or the software version information, whether the target SGSN supports the data service bearer handover.
  • the mobility management entity may determine, according to its own software configuration information, and/or hardware configuration information, whether it supports the data service bearer switching.
  • the mobility management entity does not support the data service bearer handover, and may include the following: the terminal (or user) corresponding to the dual handover request is a cardless emergency call user, and the mobility management entity does not support none.
  • the data service bearer switching of the card emergency call user; or the network type that the eNode B initiates the double handover request to switch the data service bearer to, is not the network type of the data service bearer handover supported by the mobility management entity, for example, eNode
  • the B-initiated double handover request requests to switch the data service bearer to the 2G network, and the mobility management entity is configured to support switching the data service bearer to the 3G network; or the mobility management entity does not obtain the double in the SRVCC technology Switching authorization.
  • the mobility management entity determines that the mobility management entity does not support the data service bearer handover: the mobility management entity determines that the terminal is a cardless emergency call user and determines that the mobility management entity does not support cardless emergency Call the user to switch. Alternatively, the mobility management entity determines that the mobility management entity does not support 2G or 3G Packet Switching (PS) handover; or the mobility management entity determines that the mobility management entity does not support single wireless voice call continuity (Single Radio Voice Call Continuity, SRVCC) double switching.
  • PS Packet Switching
  • the target SGSN does not support the data service bearer switching, and may include the following: when domain name resolution fails for the target SGSN, or when performing the target SGSN
  • the version of the GPRS tunneling protocol control plane (GTP-C) of the target SGSN is identified as the V0 version, and it can be determined that the target SGSN does not support the data service bearer switching.
  • the GTP-C of the V0 version does not support the data service bearer switching.
  • the target SGSN does not support the data service bearer switching.
  • the determining, by the mobility management entity, that the target SGSN does not support the data service bearer handover may include: the mobility management entity determines that the mobility management entity cannot successfully resolve the domain name of the target SGSN. Alternatively, the mobility management entity determines that the version of the GTP-C of the target SGSN does not support data service bearer switching.
  • Step 203 The mobility management entity converts the dual handover request into a single handover request indicating that a voice service bearer of the terminal needs to be switched.
  • the mobility management entity will The double handover request is converted into a single handover request indicating that the voice service bearer of the terminal needs to be switched.
  • the mobility management entity does not support the data service bearer handover
  • the target GPRS service support node does not support the data service bearer handover
  • the link required to switch the data service bearer is faulty.
  • the step of converting the dual handover request into a single handover request indicating that the voice service bearer of the terminal needs to be switched may be performed.
  • the single handover request may be performed to convert the dual handover request into a single handover request indicating that the voice service bearer needs to be switched.
  • At least one of the mobility management entity and the target SGSN does not support the data service bearer handover, and may include the following situation: the mobility management entity does not support the data service bearer handover, or The target SGSN does not support the data service bearer handover, or the mobility management entity and the target SGSN do not support the data service bearer handover.
  • the double handover request may be converted into a single handover request indicating that the voice service bearer of the terminal needs to be switched.
  • a word indicating the type of switching in the double switching request may be used
  • the segment value is modified from the first identifier to the second identifier.
  • the first identifier indicates that the type of the handover request is a dual handover type, and the second identifier indicates that the type of the handover request is a single handover type.
  • Step 204 The mobility management entity sends the single handover request to a mobile switching center.
  • FIG. 3 is a flowchart of still another method for switching a voice service bearer according to an embodiment of the present invention. As shown in FIG. 3, the method may include:
  • Step 301 The User Equipment (UE) sends a measurement report (Measure Report) to the source eNodeB.
  • UE User Equipment
  • the measurement report may include information such as the received signal strength of the UE.
  • the source evolved base station is an evolved base station to which the UE is currently assigned.
  • Step 302 The eNodeB determines, according to the measurement report, that a dual handover procedure needs to be triggered.
  • the eNodeB may analyze, according to the measurement report, whether the current channel condition of the terminal is good. When the eNodeB determines that the terminal needs to perform dual handover, the dual handover request may be sent to the MME.
  • Step 303 The eNodeB sends a handover request (Handover Required) to the source MME.
  • the source MME refers to the MME to which the eNodeB is currently assigned.
  • the value of the Number of Iu Instances field in the Source to Target Transparent Container is 2 , indicating that the handover request is a dual handover request; when the value of the Number of Iu Instances field is 1, it indicates that the handover request is a single handover request.
  • the value of the Number of Iu Instances field in the handover request is 2, indicating that the request is a dual handover request.
  • Step 304 The Source MME determines that the related network element device or the current link does not support the data service bearer switching.
  • the related network element device or the current link does not support the data service bearer switching, and specifically includes the following situation: at least one of the mobility management entity and the target SGSN does not support the The data service bearers the handover, or the GTP-C link between the MME and the SGSN fails, or the GTP-C link between the SGSN and the RNC fails.
  • Step 305 The Source MME converts the dual handover request into a single handover request.
  • the value of the Number of Iu Instances field in the handover request may be modified to 1.
  • Step 306 Send the single handover request to a mobile switching server (MSC Server).
  • MSC Server mobile switching server
  • Step 307 The MSC Server sends a Prepare Handover Request to the target mobile switching center (Target MSC).
  • this step is an optional step. In practical applications, you can choose to use according to actual needs.
  • Step 308 The MSC Server sends a Relocation Request to the target RNC.
  • the relocation request is used to request the target RNC to allocate CS resources for carrying voice services.
  • Step 309 The target RNC sends a Relocation Request Acknowledge message to the target MSC.
  • Step 310 The target MSC sends a Prepare Handover Response to the MSC Server.
  • step 7 is performed, step 10 should also be performed.
  • Step 311 Establish a circuit connection between the target MSC and the MSC Server.
  • This step is also an optional step.
  • the dual handover request can be converted to indicate that the voice needs to be used for the terminal.
  • the service carries a single handover request for handover, without having to make a large change to the existing handover procedure, and the handover of the voice service bearer can be completed at a small cost.
  • the embodiment of the present application further provides an apparatus for switching a voice service bearer.
  • the device can be a mobility management entity.
  • FIG. 4 is a schematic diagram of an apparatus for switching a voice service bearer according to an embodiment of the present invention. As shown in FIG. 4, the device may include:
  • the obtaining unit 401 is configured to acquire a dual handover request sent by the evolved base station, where the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal;
  • the eNodeB may send a measurement signal to the terminal, and the terminal may generate a measurement report based on the measurement signal and feed back to the eNodeB.
  • the measurement report may include information such as the received signal strength of the terminal.
  • the eNodeB may analyze, according to the measurement report, whether the current channel condition of the terminal is good.
  • the dual handover request may be sent to the mobility management entity.
  • the voice service mainly refers to a service in which a terminal performs a voice call through a mobile network
  • the data service mainly refers to a service in which a terminal transmits a packet through a mobile network; and at the same time, a voice service bearer and a data service bearer are switched, which may be called Double switching.
  • the determining unit 402 is configured to determine that the data service bearer cannot be successfully switched
  • the data service mainly refers to the service in which the terminal accesses the Internet through the data traffic of the mobile network.
  • the network element involved in the data service bearer handover may include: a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), and the like.
  • MME Mobility Management Entity
  • SGSN Serving GPRS Support Node
  • the mobility management entity may determine whether the data service bearer can be successfully switched. When the mobility management entity determines that the data service bearer cannot be successfully switched, step 103 may be further performed, so that the voice service bearer can be subsequently switched.
  • the converting unit 403 is configured to convert the dual handover request into a single handover request, where the single handover request is used to request to switch the voice service bearer;
  • the dual handover request may be converted into a single handover request indicating that the voice service bearer needs to be switched, so as to solve the data service in the prior art when performing dual handover.
  • the sending unit 404 is configured to send the single handover request to the mobile switching center.
  • the mobile switching center may complete the Switching of voice service bearers.
  • the handover process of the data service bearer in the dual handover is mainly: the MME sends a Forward Relocation Request message to the target SGSN, and the target SGSN receives the Forward Relocation Request message sent by the MME, and then sends the Forward Relocation Request message to the radio network controller (Radio).
  • the Network Controller (RNC) sends a Relocation Request message to request the RNC to allocate Packet Switching (PS) resources.
  • PS resource is a resource used to carry data services after handover.
  • the handover process of the voice service bearer in the dual handover is mainly: the Mobile Switching Center (MSC) sends a Relocation Request message to the RNC to request the RNC to allocate Circuit Switch (CS) resources.
  • the CS resource is a resource used to carry the voice service after the handover.
  • the RNC is configured to respond to the Relocation Request message sent by the SGSN first, and then respond to the Relocation Request message sent by the MSC. Therefore, when the RNC fails to receive the Relocation Request message, the RNC cannot respond to the Relocation Request message sent by the MSC in time, and the handover of the voice service bearer fails. In this case, even if the corresponding network element device has the capability of supporting the handover of the voice service bearer, the voice service bearer cannot be successfully switched.
  • the voice service bearer may continue to be performed by converting the dual handover request to a single handover request indicating that the voice service bearer needs to be handed over when the data service bearer cannot be successfully switched.
  • the voice service bearer can still be switched, which solves the problems in the prior art and improves.
  • the switching success rate of the voice service bearer is to implement voice calls between terminals, such as making calls. Calling is the most basic function of the terminal (mobile phone). Priority is given to ensuring that this feature is implemented and can enhance the user experience.
  • the determining unit 402 may be specifically configured to:
  • the determining unit 402 may specifically be used to:
  • the determining unit 402 may specifically be used to:
  • the determining unit 402 may specifically be used to:
  • the determining unit 402 may specifically be used to:
  • the mobility management entity does not support single wireless voice call continuity SRVCC dual handover.
  • the determining unit 402 may specifically be used to:
  • the determining unit 402 may specifically be used to:
  • the dual-switching request may include a first identifier, where the first identifier is used to indicate that the handover request type is a dual-switching type, and the converting unit 403 may be specifically configured to:
  • the IU instance number in the source-to-target transparent container in the double-switching request has a field value of 2
  • the conversion unit 403 is specifically configured to:
  • the field value of the Number of Iu Instances field in the source-to-target transparent container in the double switch request is modified from 2 to 1.
  • the embodiment of the present application further provides a system for switching a voice service bearer.
  • Said The system can include an evolved base station and a mobility management entity;
  • the evolved base station is configured to send a dual handover request to the mobility management entity; the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal;
  • the mobility management entity is configured to acquire the dual handover request; determine that the data service bearer cannot be successfully switched; convert the dual handover request into a single handover request, where the single handover request is used to request the voice service
  • the bearer performs handover; the single handover request is sent to the mobile switching center.
  • the embodiment of the present application further provides another system for switching a voice service bearer.
  • the system includes a mobility management entity and a mobile switching center;
  • the mobility management entity is configured to acquire a dual handover request sent by the evolved base station, where the dual handover request is used to request to switch the voice service bearer and the data service bearer of the terminal; and determine that the data service bearer cannot be successfully switched;
  • the double handover request is converted into a single handover request, where the single handover request is used to request to switch the voice service bearer; and the single handover request is sent to the mobile switching center;
  • the mobile switching center is configured to receive the single handover request.
  • system may further include an evolved base station, where the evolved base station is configured to send the dual handover request to the mobility management entity.
  • the embodiment of the present application further provides another apparatus for switching a voice service bearer, where the apparatus may be a host server including computing capabilities, or a personal computer PC, or a portable computer or terminal. Etc.
  • the apparatus may be a host server including computing capabilities, or a personal computer PC, or a portable computer or terminal. Etc.
  • the specific embodiments of the present application do not limit the specific implementation of the device.
  • FIG. 5 is a schematic structural diagram of another apparatus for switching a voice service bearer according to an embodiment of the present invention. As shown in FIG. 5, the apparatus 500 includes:
  • a processor 510 a communications interface 520, a memory 530, and a bus 540.
  • the processor 510, the communication interface 520, and the memory 530 complete communication with each other via the bus 540.
  • the processor 510 is configured to execute a computer to execute the instruction 532.
  • computer executable instructions 532 can include program code.
  • the processor 510 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • the memory 530 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the memory 530 is configured to store computer execution instructions
  • the processor 510 is coupled to the memory 530 via the bus, and when the apparatus for switching a voice service bearer is executed, the processor 510 executes The computer stored in the memory 530 executes the instruction 532 to enable the processor to perform the switching method of the voice service bearer provided in the embodiment of the present application.
  • the application also provides a computer readable medium.
  • the computer readable medium includes a computer-executable instruction for the processor of the computer to execute the instruction to switch the voice service bearer provided in the embodiment of the present application.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented directly in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

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

Abstract

L'invention concerne un procédé de commutation de porteuse de service vocal, ainsi qu'un appareil et un système adaptés. Le procédé comprend : l'acquisition, par une entité de gestion de mobilité, d'une demande de double-commutation envoyée par un nœud évolué B (eNodeB), la demande de double commutation étant utilisée pour demander de commuter une porteuse de service vocal et une porteuse de service de données d'un terminal ; la détermination, par l'entité de gestion de mobilité, qu'il est impossible de réussir à commuter la porteuse de service de données ; la conversion, par l'entité de gestion de mobilité, de la demande de commutation double en une demande de commutation unique, la demande de commutation unique étant utilisée pour demander la commutation de la porteuse de service vocal ; et l'envoi, par l'entité de gestion de mobilité, de la demande de commutation unique à un centre de commutation mobile. Au moyen du procédé de commutation et de l'appareil et du système adaptés selon la présente invention, le taux de réussite de commutation d'une porteuse de service vocal peut être amélioré.
PCT/CN2014/085632 2014-08-30 2014-08-30 Procédé de commutation de porteuse de service vocal, appareil et système adaptés WO2016029479A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201480021489.9A CN105900484B (zh) 2014-08-30 2014-08-30 一种语音业务承载的切换方法、相关装置及系统
PCT/CN2014/085632 WO2016029479A1 (fr) 2014-08-30 2014-08-30 Procédé de commutation de porteuse de service vocal, appareil et système adaptés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/085632 WO2016029479A1 (fr) 2014-08-30 2014-08-30 Procédé de commutation de porteuse de service vocal, appareil et système adaptés

Publications (1)

Publication Number Publication Date
WO2016029479A1 true WO2016029479A1 (fr) 2016-03-03

Family

ID=55398684

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/085632 WO2016029479A1 (fr) 2014-08-30 2014-08-30 Procédé de commutation de porteuse de service vocal, appareil et système adaptés

Country Status (2)

Country Link
CN (1) CN105900484B (fr)
WO (1) WO2016029479A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101999244A (zh) * 2008-01-14 2011-03-30 诺泰网络有限公司 单次无线电语音呼叫连续性(sr-vcc)
CN102238679A (zh) * 2010-05-04 2011-11-09 中兴通讯股份有限公司 单信道语音连续性实现方法及系统
CN102958054A (zh) * 2012-11-26 2013-03-06 中国联合网络通信集团有限公司 网络切换处理方法、移动管理实体、基站及网络系统
WO2014121825A1 (fr) * 2013-02-06 2014-08-14 Telefonaktiebolaget L M Ericsson (Publ) Nœud et procédé pour une procédure combinée de continuité d'appel vocal radio unique et de transfert intercellulaire dans un réseau à commutation de paquets

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010005180A2 (fr) * 2008-06-16 2010-01-14 Samsung Electronics Co., Ltd. Procédé et système de gestion de transfert dans les réseaux d’accès sans fil
JP5380419B2 (ja) * 2010-11-04 2014-01-08 株式会社エヌ・ティ・ティ・ドコモ 移動通信方法、無線アクセスネットワーク装置及び移動管理ノード

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101999244A (zh) * 2008-01-14 2011-03-30 诺泰网络有限公司 单次无线电语音呼叫连续性(sr-vcc)
CN102238679A (zh) * 2010-05-04 2011-11-09 中兴通讯股份有限公司 单信道语音连续性实现方法及系统
CN102958054A (zh) * 2012-11-26 2013-03-06 中国联合网络通信集团有限公司 网络切换处理方法、移动管理实体、基站及网络系统
WO2014121825A1 (fr) * 2013-02-06 2014-08-14 Telefonaktiebolaget L M Ericsson (Publ) Nœud et procédé pour une procédure combinée de continuité d'appel vocal radio unique et de transfert intercellulaire dans un réseau à commutation de paquets

Also Published As

Publication number Publication date
CN105900484A (zh) 2016-08-24
CN105900484B (zh) 2020-02-14

Similar Documents

Publication Publication Date Title
US11432351B2 (en) Service continuity ensuring method, control plane gateway, and mobility management network element
WO2017091960A1 (fr) Procédé, dispositif, et système de commutation entre plates-formes mobile edge computing
CN105052201B (zh) 从使用未许可频谱的网络到电路交换网络的通信切换
US20200221539A1 (en) Data Forwarding Method, Apparatus, and System
JP2020523944A (ja) 情報処理方法および関連装置
CN108632928B (zh) 一种切换核心网的方法及装置
CN108024296B (zh) 切换网络的方法、系统和移动性管理网元
WO2019129115A1 (fr) Procédé de transfert de système et entité de communication
WO2019095119A1 (fr) Procédé de commutation de réseau, dispositif de réseau et dispositif de terminal
US11700553B2 (en) Method of apparatus for monitoring for a radio link failure associated with a secondary cell of a secondary base station
US20230013493A1 (en) Information processing method and device
JP2021510030A (ja) 無線通信方法及び装置
WO2012055093A1 (fr) Procédé et dispositif de traitement d'appel dans une réserve de centres de commutation de communications mobiles
WO2022007484A1 (fr) Procédé de redirection, dispositif de réseau, dispositif terminal et support de stockage lisible
CN104380799A (zh) 电路域回退的方法及设备
EP3280178A1 (fr) Procédé, dispositif de réseau et système permettant un repli sur commutation de circuits
WO2016041208A1 (fr) Procede et appareil associe pour la selection d'operateurs de domaine a commutation de circuits et de domaine a commutation de paquets de reseau de partage cible
WO2015043494A1 (fr) Procédé et dispositif d'établissement d'une connexion de service
JP6473171B2 (ja) Ｍｓｃ間ハンドオーバのためのｍａｐを介したｉｍｅｉｓｖの指示
CN116686339A (zh) 用于在不同rat之间切换的方法和装置
WO2017214921A1 (fr) Procédé de communication sans fil, appareil, terminal, et station de base
WO2016029479A1 (fr) Procédé de commutation de porteuse de service vocal, appareil et système adaptés
WO2019140560A1 (fr) Procédé et dispositif de transfert intercellulaire et support de stockage informatique
CN106576278B (zh) 一种srvcc能力信息的传输方法、装置及系统
KR102121970B1 (ko) 호 처리 방법 및 장치

Legal Events

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

Ref document number: 14900579

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: 14900579

Country of ref document: EP

Kind code of ref document: A1