WO2016029479A1

WO2016029479A1 - Voice service bearer switching method, relevant apparatus and system

Info

Publication number: WO2016029479A1
Application number: PCT/CN2014/085632
Authority: WO
Inventors: 陈波
Original assignee: 华为技术有限公司
Priority date: 2014-08-30
Filing date: 2014-08-30
Publication date: 2016-03-03
Also published as: CN105900484B; CN105900484A

Abstract

Disclosed are a voice service bearer switching method, and a relevant apparatus and system. The method comprises: acquiring, by a mobility management entity, a dual-switching request sent by an evolved node B (eNodeB), the dual-switching request being used for requesting to switch a voice service bearer and a data service bearer of a terminal; determining, by the mobility management entity, that the data service bearer cannot be successfully switched; converting, by the mobility management entity, the dual-switching request to a single-switching request, the single-switching request being used for requesting to switch the voice service bearer; and sending, by the mobility management entity, the single-switching request to a mobile switching centre. By means of the switching method and the relevant apparatus and system in the present invention, the switching success rate of a voice service bearer can be improved.

Description

Handover method, related device and system for voice service bearer

Technical field

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.

Background technique

LTE (Long Term Evolution) is a long-term evolution of the UMTS (Universal Mobile Telecommunications System) technology standard developed by the 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.

However, in the initial stage of LTE/EPC network construction, hotspot coverage is usually adopted, and the point-to-face deployment method is gradually adopted. Therefore, the coverage area of the LTE/EPC network is relatively limited. When the user carries the terminal and moves from the coverage area of the LTE/EPC network to the area that has not been covered by the LTE/EPC network, the voice service bearer of the terminal needs to be handed over from the LTE/EPC network to other networks.

In the prior art, when the voice service bearer of the terminal is switched from the LTE/EPC network to another network, SRVCC technology (Single Radio Voice Call Continuity) may be adopted. Since the terminal usually has a data service in the LTE/EPC network, in the prior art, when 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.

In the prior art, when dual handover is performed, as long as one of the two bearers of the voice service bearer and the data service bearer cannot be switched, the dual handover cannot be completed. That is to say, when the data service bearer cannot be switched, the voice service bearer cannot be switched. This results in a lower handover success rate of voice service bearers in the prior art.

Summary of the invention

In view of the above, 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:

According to the first possible implementation manner of the first aspect of the application, 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.

With reference to the second possible implementation manner of the first aspect, 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.

In conjunction with the first or second possible implementation of the first aspect, 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.

In combination with any one of the first to third possible implementation manners of the first aspect, 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.

With reference to the first specific implementation manner of the second possible implementation manner of the first aspect, 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.

With reference to the second specific implementation manner of the second possible implementation manner of the first aspect, 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;

Alternatively, the mobility management entity determines that the mobility management entity does not support a single wireless voice call continuity SRVCC dual handover.

With reference to the first specific implementation manner of the third possible implementation manner of the first aspect, 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.

With reference to the second specific implementation manner of the third possible implementation manner of the first aspect, 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.

With reference to any one of the eight possible implementation manners of the first aspect, 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.

In combination with any one of the nine possible implementation manners of the first aspect, 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.

According to the first possible implementation manner of the second aspect of the present application, 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;

And a sending unit, configured to send the single handover request to the mobile switching center.

With reference to the second possible implementation of the second aspect, the determining unit is specifically configured to:

It is determined that the mobility management entity does not support data service bearer switching.

With reference to the first or second possible implementation of the second aspect, the determining unit is specifically configured to:

Determining the target general packet radio service technology GPRS service support node does not support data service bearer handover.

With reference to any one of the first to third possible implementation manners of the second aspect, the determining unit is specifically configured to:

It is determined that the link required to switch the data service bearer is faulty.

With reference to the first specific implementation manner of the second possible implementation manner of the second aspect, the determining unit is specifically configured to:

Determining that the terminal is a cardless emergency call user and determining that the mobility management entity does not support cardless emergency call user handover.

With reference to the second specific implementation manner of the second possible implementation manner of the second aspect, the determining unit is specifically configured to:

Determining that the mobility management entity does not support 2G or 3G packet switched PS handover;

Alternatively, it is determined that the mobility management entity does not support single wireless voice call continuity SRVCC dual handover.

With reference to the first specific implementation manner of the third possible implementation manner of the second aspect, the determining unit is specifically configured to:

Determining that the mobility management entity cannot successfully parse the domain of the target GPRS service support node name.

With reference to the second specific implementation manner of the third possible implementation manner of the second aspect, the determining unit is specifically configured to:

Determining that the version of the GPRS tunneling protocol control plane of the target GPRS service support node does not support data service bearer switching.

With reference to any one of the eight possible implementation manners of the second aspect, 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:

Modifying 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.

With reference to any one of the nine possible implementation manners of the second aspect, 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.

According to a first possible implementation manner of the third aspect of the present application, 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.

According to a first possible implementation manner of the fourth aspect of the present application, 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.

With reference to the second possible implementation manner of the fourth aspect, 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.

According to a first possible implementation manner of the fifth aspect of the present application, 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.

According to a first possible implementation manner of the sixth aspect of the present application, 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.

It can be seen from the above technical solution that 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. On the other hand, 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.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

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;

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.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope 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.

In an actual application, 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. When the eNodeB determines that the terminal needs to perform dual handover, the dual handover request may be sent to the mobility management entity. In the present invention, the voice service mainly refers to a service in which a terminal performs a voice call through a mobile network, and 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.

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.

When the mobility management entity determines that the data service bearer cannot be successfully 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. When the data service bearer cannot be switched, the voice service bearer cannot be switched.

Step 104: The mobility management entity sends the single handover request to a mobile switching center.

After receiving the single handover request, the mobile switching center may complete the handover of the voice service bearer by using a subsequent step.

In the prior art, 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. The 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.

However, in the existing dual handover procedure, 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.

In this embodiment, 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. 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, which solves the problems in the prior art and improves. The switching success rate of the voice service bearer. On the other hand, 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. 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.

If 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. At this time, 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.

In the present invention, 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. In addition, 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. Therefore, 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.

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 When the domain name resolution is performed, 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. When the GTP-C version of the target SGSN is V0, the target SGSN does not support the data service bearer switching. Therefore, 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.

If at least one of the mobility management entity and the target SGSN does not support the data service bearer handover, or the link required to switch the data service bearer is faulty, 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.

It should be noted that the mobility management entity does not support the data service bearer handover, and the target GPRS service support node does not support the data service bearer handover, and the link required to switch the data service bearer is faulty. As long as any one of the conditions is met, 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. Moreover, those skilled in the art may know that when the combination of any of the above three conditions is satisfied, 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. A step of.

It should be noted that, 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.

At this time, 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. For example, 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.

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.

According to the 3rd Generation Partnership Project (3GPP), in the Handover Required message, 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.

In this step, 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.

Specifically, 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.

Specifically, 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).

Step 307: The MSC Server sends a Prepare Handover Request to the target mobile switching center (Target MSC).

It should be noted that 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.

This step is an optional step. If 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.

So far, the handover process for the voice service bearer of the UE is completed.

In this embodiment, by changing the 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 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 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.

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;

When it is determined that the data service bearer cannot be successfully switched, 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 problem that the voice service bearer cannot be switched because the bearer cannot be switched.

The sending unit 404 is configured to send the single handover request to the mobile switching center.

After the mobile switching center receives the single handover request, the mobile switching center may complete the Switching of voice service bearers.

In the prior art, 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. The 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.

In an actual application, the determining unit 402 may be specifically configured to:

In an actual application, the determining unit 402 may specifically be used to:

Determining that the mobility management entity cannot successfully resolve the domain name of the target GPRS service support node.

In an actual application, the determining unit 402 may specifically be used to:

In an actual application, 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:

In an actual application, the IU instance number in the source-to-target transparent container in the double-switching request has a field value of 2, and the conversion unit 403 is specifically configured to:

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 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;

In an actual application, the 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.

In addition, 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 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.

In particular, 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.

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 various embodiments in the present specification are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the various embodiments may be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

A person skilled in the art will further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in a combination of electronic hardware or electronic hardware and computer software. To clearly illustrate the interchangeability of some of the hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the above description. Whether these functions are performed in hardware or a combination of hardware and software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

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.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but the scope of the invention is to be accorded

Claims

A method for switching a voice service bearer, comprising:

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 method according to claim 1, wherein the determining, by the mobility management entity, that the data service bearer cannot be successfully switched comprises:

The mobility management entity determines that the mobility management entity does not support data traffic bearer switching.
The method according to claim 1 or 2, wherein the mobility management entity determines that the data service bearer cannot be successfully switched comprises:

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 method according to any one of claims 1-3, wherein the mobility management entity determines that the data service bearer cannot be successfully switched comprises:

The mobility management entity determines that the link required to switch the data traffic bearer is faulty.
The method according to claim 2, wherein the determining that the mobility management entity does not support data traffic bearer switching comprises:

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 method according to claim 2, wherein the determining that the mobility management entity does not support data traffic bearer switching comprises:

The mobility management entity determines that the mobility management entity does not support 2G or 3G packet switched PS handover;

Alternatively, the mobility management entity determines that the mobility management entity does not support a single wireless voice call continuity SRVCC dual handover.
The method according to claim 3, wherein the mobility management entity determines that the target GPRS service support node does not support the data service bearer handover comprises:

The mobility management entity determines that the mobility management entity cannot successfully resolve the domain name of the target GPRS service support node.
The method according to claim 3, wherein the mobility management entity determines that the target GPRS service support node does not support the data service bearer handover comprises:

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 method according to any one of claims 1-8, wherein the dual handover request includes a first identifier, and the first identifier is used to indicate that the handover request type is a dual handover type; The entity converting the dual handover request into 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 method according to any one of claims 1 to 9, wherein a field value of the number of IU instances in the source-to-target transparent container in the double-switching request is 2; the mobility management Modifying, by the entity, 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.
An apparatus for switching a voice service bearer, comprising:

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;

And a sending unit, configured to send the single handover request to the mobile switching center.
The device according to claim 11, wherein the determining unit is specifically configured to:

It is determined that the mobility management entity does not support data service bearer switching.
The device according to claim 11 or 12, wherein the determining unit is specifically configured to:

Determining the target general packet radio service technology GPRS service support node does not support data service bearer handover.
The device according to any one of claims 11 to 13, wherein the determining unit is specifically configured to:

It is determined that the link required to switch the data service bearer is faulty.
The device according to claim 12, wherein the determining unit is specifically configured to:

Determining that the terminal is a cardless emergency call user and determining that the mobility management entity does not support cardless emergency call user handover.
The device according to claim 12, wherein the determining unit is specifically configured to:

Determining that the mobility management entity does not support 2G or 3G packet switched PS handover;

Alternatively, it is determined that the mobility management entity does not support single wireless voice call continuity SRVCC dual handover.
The device according to claim 13, wherein the determining unit is specifically configured to:

Determining that the mobility management entity cannot successfully resolve the domain name of the target GPRS service support node.
The device according to claim 13, wherein the determining unit is specifically configured to:

Determining that the version of the GPRS tunneling protocol control plane of the target GPRS service support node is not supported Data service bearer switching.
The device according to any one of claims 11 to 18, wherein the dual handover request includes a first identifier, and the first identifier is used to indicate that the handover request type is a dual handover type; Specifically used for:

Modifying 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 device according to any one of claims 11 to 19, wherein a field value of the number of IU instances in the source-to-target transparent container in the double-switching request is 2; the conversion unit Specifically 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.
A system for switching a voice service bearer, the system comprising 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.
A system for switching a voice service bearer, the system comprising 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 of claim 22 wherein said system further comprises an evolved base And the evolved base station is configured to send the dual handover request to the mobility management entity.
An apparatus for switching a voice service bearer, comprising: 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 method of switching a voice service bearer according to any one of claims 1-10.
A computer readable medium, comprising: a computer executing instructions for execution by a processor of a computer to execute a voice service bearer according to any one of claims 1-10 Switching method.