CN105900484B - Switching method, related device and system for voice service bearer - Google Patents
Switching method, related device and system for voice service bearer Download PDFInfo
- Publication number
- CN105900484B CN105900484B CN201480021489.9A CN201480021489A CN105900484B CN 105900484 B CN105900484 B CN 105900484B CN 201480021489 A CN201480021489 A CN 201480021489A CN 105900484 B CN105900484 B CN 105900484B
- Authority
- CN
- China
- Prior art keywords
- management entity
- switching
- service bearer
- request
- mobility management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 230000009977 dual effect Effects 0.000 claims description 75
- 238000004891 communication Methods 0.000 claims description 9
- 238000006243 chemical reaction Methods 0.000 claims description 8
- 238000005259 measurement Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000007774 longterm Effects 0.000 description 3
- 241000760358 Enodes Species 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000005641 tunneling Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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
Abstract
The invention discloses a switching method of voice service bearing, a related device and a system. The method comprises the following steps: a mobile management entity obtains a double-switching request sent by an evolution base station, wherein the double-switching request is used for requesting to switch a voice service bearer and a data service bearer of a terminal; the mobility management entity determining that the data traffic bearer cannot be successfully handed over; the mobile management entity converts the double switching request into a single switching request, and the single switching request is used for requesting to switch the voice service bearer; and the mobile management entity sends the single switching request to a mobile switching center. The switching method, the related device and the system can improve the switching success rate of the voice service bearing.
Description
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 voice service bearers.
Background
LTE (Long Term Evolution) is a Long Term Evolution of The UMTS (Universal mobile telecommunications System) technical standard established by The 3GPP (The 3rd generation partnership Project) organization. The long-term goal of LTE is to simplify and redesign the network architecture to make it an IP-enabled network.
An Evolved Packet Core (EPC) network of LTE is a Core network of 4G technology. LTE/EPC can enable all IP bearers, flat networks, control and bearer separation, and can reduce per-bit bearer cost.
However, in the initial stage of the construction of the LTE/EPC network, hot-spot coverage is generally adopted, and a deployment manner of a point and a plane is gradually performed, so that the coverage area of the LTE/EPC network is relatively limited. When a user carries a terminal and moves from the coverage area of the LTE/EPC network to an area which is not covered by the LTE/EPC network, the voice service bearer of the terminal needs to be switched to other networks from the LTE/EPC network.
In the prior art, when the Voice service bearer of the terminal is switched from the LTE/EPC network to another network, an SRVCC (Single Radio Voice Call Continuity) technology may be used. 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. This simultaneous handover of voice traffic bearers and data traffic bearers may be referred to as a dual handover.
In the prior art, when double handover is performed, as long as one of two bearers, namely a voice service bearer and a data service bearer, cannot be switched, the double handover cannot be completed. That is, when the data service bearer cannot be switched, the voice service bearer cannot be switched either. This results in a low success rate of handover of the voice traffic bearer in the prior art.
Disclosure of Invention
In view of the above, the present invention provides a method, a related apparatus and a system for switching a voice service bearer, which convert a dual handover request into a single handover request, thereby solving the problem of a low success rate of switching the voice service bearer in the prior art. The specific scheme is as follows:
according to a first possible implementation manner of the first aspect of the present application, the present application provides a method for switching a voice service bearer, including:
a mobile management entity obtains a double-switching request sent by an evolution base station, wherein the double-switching request is used for requesting to switch a voice service bearer and a data service bearer of a terminal;
the mobility management entity determining that the data traffic bearer cannot be successfully handed over;
the mobile management entity converts the double switching request into a single switching request, and the single switching request is used for requesting to switch the voice service bearer;
and the mobile management entity sends the single switching 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 handed over includes:
the mobility management entity determines that the mobility management entity does not support data service bearer switching.
With reference to the first or second possible implementation manner of the first aspect, the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over includes:
the mobile management entity determines that a target GPRS service support node does not support data service bearer switching.
With reference to 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 handed over includes:
and the mobile management entity determines that the link required for switching the data service bearer has a fault.
With reference to the first specific implementation manner of the second possible implementation manner of the first aspect, the determining, by the mobility management entity, that the mobility management entity does not support bearer switching for the data service includes:
the mobility management entity determines that the terminal is a non-emergency call subscriber and determines that the mobility management entity does not support handover of the non-emergency call subscriber.
With reference to the second specific implementation manner of the second possible implementation manner of the first aspect, the determining, by the mobility management entity, that the mobility management entity does not support bearer switching for the data service includes:
the mobility management entity determines that the mobility management entity does not support Packet Switched (PS) handover of 2G or 3G;
or, the mobility management entity determines 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 first aspect, the determining, by the mobility management entity, that the target GPRS service support node does not support bearer handover for the data service includes:
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 determining, by the mobility management entity, that the target GPRS service support node does not support bearer handover for the data service includes:
and the mobile management entity determines that the version of the GPRS tunnel protocol control plane of the target GPRS service support node does not support the data service bearer switching.
With reference to any one of 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 a handover request type is a dual handover type; the converting the dual handover request into a single handover request by the mobility management entity comprises:
and the mobile management entity modifies the first identifier in the double-switching request into a second identifier, wherein the second identifier is used for indicating that the type of the switching request is a single-switching type.
With reference to any one of the nine possible implementation manners of the first aspect, a field value of an IU instance Number of IU Instances field in the source-to-target transparent container in the dual switch request is 2; the modifying, by the mobility management entity, the first identity to a second identity in the dual handover request comprises:
the mobility management entity modifies the field value of the Number of IuInstances field in the source-to-target transparent container in the dual handover request from 2 to 1.
According to a first possible implementation manner of the second aspect of the present application, the present application provides an apparatus for switching a voice service bearer, including:
an obtaining unit, configured to obtain a dual handover request sent by an evolved base station, where the dual handover request is used to request to switch a voice service bearer and a data service bearer of a terminal;
a determining unit, configured to determine that the data service bearer cannot be successfully switched;
a conversion 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 the sending unit is used for sending the single switching request to a mobile switching center.
With reference to the second possible implementation manner of the second aspect, the determining unit is specifically configured to:
and determining that the mobility management entity does not support data service bearer switching.
With reference to the first or second possible implementation manner of the second aspect, the determining unit is specifically configured to:
determining that the target GPRS service support node does not support data service bearer switching.
With reference to any one of the first to third possible implementation manners of the second aspect, the determining unit is specifically configured to:
and determining that the link required for switching the data service bearer has a fault.
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 non-emergency call subscriber and determining that the mobility management entity does not support handover of the non-emergency call subscriber.
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;
or, determining 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 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 second aspect, the determining unit is specifically configured to:
and determining that the version of the GPRS tunnel protocol control plane of the target GPRS service support node does not support data service bearer switching.
With reference to any one of 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 a handover request type is a dual handover type; the conversion unit is specifically configured to:
and modifying the first identifier in the double-switching request into a second identifier, wherein the second identifier is used for indicating that the type of the switching request is a single-switching type.
With reference to any one of the nine possible implementations of the second aspect, a field value of an IU instance Number of IU Instances field in the source-to-target transparent container in the dual switch request is 2; the conversion unit is specifically configured to:
modifying the field value of the Number of IuInstances field in the source-to-target transparent container in the dual-switch request from 2 to 1.
According to a first possible implementation manner of the third aspect of the present application, the present application provides a system for switching a voice service bearer, where the system includes an evolved base station and a mobility management entity;
the evolution base station is used for sending a dual handover request to the mobile management entity; the double-switching request is used for requesting the switching of the voice service bearing and the data service bearing of the terminal;
the mobile management entity is used for acquiring the double switching request; determining that the data traffic bearer cannot be successfully switched; converting the double-switching request into a single-switching request, wherein the single-switching request is used for requesting to switch the voice service bearer; and sending the single switching request to a mobile switching center.
According to a first possible implementation manner of the fourth aspect of the present application, the present application provides another system for switching a voice service bearer, where the system includes a mobility management entity and a mobile switching center;
the mobile management entity is used for acquiring a double-switching request sent by an evolution base station, wherein the double-switching request is used for requesting to switch a voice service bearer and a data service bearer of a terminal; determining that the data traffic bearer cannot be successfully switched; converting the double-switching request into a single-switching request, wherein the single-switching request is used for requesting to switch the voice service bearer; sending the single handover request to the mobile switching center;
the mobile switching center is used for receiving the single switching 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 present application provides an apparatus for switching a voice service bearer, including: a processor, a memory, a bus, and a communication interface;
the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the device for switching the voice service bearer is operated, the processor executes the computer execution instructions stored in the memory, so that the processor executes the aforementioned switching method of the voice service bearer.
According to a first possible implementation manner of the sixth aspect of the present application, the present application provides a computer-readable medium, which includes computer-executable instructions, so that when a processor of a computer executes the computer-executable instructions, the computer executes the foregoing method for switching a voice service bearer.
It can be seen from the above technical solutions that, in the method, the related apparatus and the system for switching voice service bearers, after receiving a dual handover request for switching a voice service bearer and a data service bearer of a terminal, by determining that the data service bearer cannot be successfully switched, the dual handover request is converted into a single handover request indicating that the voice service bearer of the terminal needs to be switched, and the single handover request is sent to a mobile switching center, so that the switching of the voice service bearer can be continued; that is to say, in this embodiment, when the system has the capability of performing the handover of the voice service bearer but cannot complete the handover of the data service bearer, the handover of the voice service bearer can still be completed, thereby solving the problems in the prior art and improving the success rate of the handover of the voice service bearer. On the other hand, the main purpose of voice service is to enable voice communication, such as making a call, between terminals. And making a call is the most basic function of a terminal (handset). Preferentially ensuring that the function can be realized and improving the use experience of the user.
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 description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
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 a method for switching a voice service bearer according to another embodiment of the present invention;
fig. 3 is a flowchart of a method for switching a voice service bearer according to another 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 component 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 will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection 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 may include:
step 101: a mobile management entity acquires a dual handover request sent by an evolution base station eNodeB; the double switching request indicates that the voice service bearing and the data service bearing of the terminal need to be switched;
in practical applications, 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 the measurement report back to the eNodeB. The measurement report may include information such as the received signal strength of the terminal.
The eNodeB can analytically determine whether the current channel condition of the terminal is good or not according to the measurement report. When the eNodeB determines that the terminal needs to perform the dual handover, the eNodeB may send the dual handover request to the mobility management entity. In the invention, the voice service mainly refers to a service that a terminal carries out voice call through a mobile network, and the data service mainly refers to a service that the terminal carries out packet transmission through the mobile network; the simultaneous handover of voice service bearer and data service bearer may be referred to as dual handover.
Step 102: the mobility management entity determining that the data traffic bearer cannot be successfully handed over;
the network element involved in the data service bearer switching may include: mobility Management Entity (MME), Serving GPRS Support Node (SGSN), and the like.
The mobility management entity may determine that the data service bearer cannot be successfully handed over. 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 mobile management entity converts the double switching request into a single switching request which represents that the voice service bearing of the terminal needs to be switched;
when the mobile management entity determines that the data service bearer cannot be successfully switched, the dual-switching request can be converted into a single-switching request indicating that the voice service bearer of the terminal needs to be switched, so as to solve the problem that the voice service bearer cannot be switched due to the fact that the data service bearer cannot be switched when the dual-switching is performed in the prior art.
Step 104: and the mobile management entity sends the single switching request to a mobile switching center.
After the mobile switching center receives the single switching request, the switching of the voice service bearing can be completed through subsequent steps.
In the prior art, the handover process of data service bearer in dual handover mainly includes: the MME sends a Forward Relocation Request message to a target SGSN, and after receiving the Forward Relocation Request message sent by the MME, the target SGSN sends the Relocation Request message to a Radio Network Controller (RNC) so as to Request the RNC to allocate Packet Switching (PS) resources. The PS resource is a resource used for carrying data service after handover. The switching process of the voice service bearer in the dual handover mainly comprises the following steps: a Mobile Switching Center (MSC) sends a Relocation Request message to an RNC to Request the RNC to allocate a Circuit Switched (CS) resource. The CS resource is a resource used for carrying a voice service after handover.
However, in the existing dual handover procedure, the RNC is configured to respond to the Relocation Request message sent by the SGSN and then respond to the Relocation Request message sent by the MSC. Therefore, when the RNC cannot receive the location Request message, the RNC cannot respond to the location 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 handed over.
In this embodiment, when it is determined that the data service bearer cannot be successfully switched, the dual-handover request is converted into a single-handover request indicating that the voice service bearer of the terminal needs to be switched, so that the voice service bearer can be continuously switched; that is to say, in this embodiment, when the system has the capability of performing the handover of the voice service bearer but cannot complete the handover of the data service bearer, the handover of the voice service bearer can still be completed, thereby solving the problems in the prior art and improving the success rate of the handover of the voice service bearer. On the other hand, the main purpose of voice service is to enable voice communication, such as making a call, between terminals. And making a call is the most basic function of a terminal (handset). Preferentially ensuring that the function can be realized and improving the use experience of the user.
Fig. 2 is a flowchart of a method for switching a voice service bearer according to another embodiment of the present invention. As shown in fig. 2, the method may include:
step 201: a mobile management entity acquires a dual handover request sent by an eNodeB; the double switching request indicates that the voice service bearing and the data service bearing of the terminal need to be switched;
step 202: the mobile management entity determines that the mobile management entity does not support data service bearer switching; or, the mobility management entity determines that the target SGSN does not support the data service bearer switching; or, the mobility management entity determines that a link required for switching the data service bearer has a fault.
If the mobile management entity does not support the data service bearer switching; or the target SGSN does not support data service bearing switching; or, if a failure occurs in a link required for switching the data Service bearer, the data Service bearer cannot be successfully switched, for example, if a GTP-C link between the MME and the target SGSN or a General Packet Radio Service (GPRS) tunneling protocol control plane (GTP-C) link between the target SGSN and the RNC fails, the data Service bearer cannot be switched. At this time, the dual 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 Relocation Request (Forward Relocation Request) sent by the mobility management entity when performing data service bearer handover. The mobility management entity may determine whether the target SGSN supports the data service bearer switching according to software configuration information or software version information of the target SGSN. In addition, the mobility management entity may determine whether or not it supports the data service bearer switching according to its software configuration information and/or hardware configuration information.
The case that the mobility management entity does not support the data service bearer switching may include the following: the terminal (or user) corresponding to the dual handover request is a non-card emergency call user, and the mobility management entity does not support data service bearer handover of the non-card emergency call user; or, the network type to which the data service bearer is requested to be switched in the eNode B-initiated dual handover request is not the network type of the data service bearer switching supported by the mobility management entity, for example, the data service bearer is requested to be switched to the 2G network in the eNode B-initiated dual handover request, and the mobility management entity is configured to support the data service bearer to be switched to the 3G network; or, the mobility management entity is not authorized for dual handover in SRVCC technology. Thus, the determining, by the mobility management entity, that the mobility management entity does not support the data traffic bearer handover comprises: the mobility management entity determines that the terminal is a non-emergency call subscriber and determines that the mobility management entity does not support handover of the non-emergency call subscriber. Or, the mobility management entity determines that the mobility management entity does not support Packet Switching (PS) handover of 2G or 3G; or, the mobility management entity determines that the mobility management entity does not support Single Radio Voice Call Continuity (SRVCC) dual handover.
The case that the target SGSN does not support the data service bearer switching may include the following: when the domain name resolution of the target SGSN fails, or when the domain name resolution of the target SGSN is performed, it is recognized that a version of a GPRS tunneling protocol control plane (GTP-C) of the target SGSN is a V0 version, it may be determined that the target SGSN does not support the data service bearer switching. Wherein, since the GTP-C version V0 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. Thus, the determining, by the mobility management entity, that the target SGSN does not support the data traffic bearer handover may comprise: the mobility management entity determines that the mobility management entity cannot successfully resolve the domain name of the target SGSN. Or, the mobility management entity determines that the version of GTP-C of the target SGSN does not support data service bearer switching.
Step 203: and the mobile management entity converts the double-switching request into a single-switching request which represents that the voice service bearer of the terminal needs to be switched.
If at least one of the mobile management entity and the target SGSN does not support the data service bearer switching or a link required for switching the data service bearer has a fault, the mobile management entity converts the double switching request into a single switching request which indicates that the voice service bearer of the terminal needs to be switched.
It should be noted that, the mobility management entity does not support data service bearer switching, the target GPRS service support node does not support data service bearer switching, and a link required for switching the data service bearer has a fault, and among these three conditions, as long as any one of the three conditions is satisfied, 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, as will be understood by those skilled in the art, when any combination of a plurality of the above three conditions is satisfied, 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 also be performed.
It should be further noted that, at least one of the mobility management entity and the target SGSN does not support the data service bearer handover, which may include the following cases: the mobility management entity does not support the data service bearer switching, or the target SGSN does not support the data service bearer switching, or both the mobility management entity and the target SGSN do not support the data service bearer switching.
At this time, the dual 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 field value used for indicating a handover type in the dual handover request may be modified from a first identity to a second identity.
The first identification represents that the type of the switching request is a double switching type, and the second identification represents that the type of the switching request is a single switching type.
Step 204: and the mobile management entity sends the single switching request to a mobile switching center.
Fig. 3 is a flowchart of a method for switching a voice service bearer according to another embodiment of the present invention. As shown in fig. 3, the method may include:
step 301: a User Equipment (UE) transmits a measurement Report (Measure Report) to a Source evolved base station (Source eNodeB).
The measurement report may include information such as the received signal strength of the UE. The source enb means an enb to which the UE currently belongs.
Step 302: and the eNodeB judges that the dual-switching process needs to be triggered according to the measurement report.
The eNodeB can analytically determine whether the current channel condition of the terminal is good or not according to the measurement report. When the eNodeB determines that the terminal needs to perform dual handover, the eNodeB may send the dual handover request to an MME.
Step 303: the eNodeB sends a Handover request (Handover Required) to the Source (Source) MME.
The source MME refers to the MME to which the eNodeB currently belongs.
According to the 3rd Generation Partnership Project (3 GPP), when the Number of IU Instances (Number of IU Instances) field value in the Source to Target transparent container (Source to Target transparent container) in the Handover Required message is 2, it indicates that the Handover request is a dual Handover request; when the Number of Iu Instances field value is 1, it indicates that the handover request is a single handover request.
In this step, the Number of Iu Instances field value in the handover request is 2, which indicates that the request is a dual handover request.
Step 304: and the Source MME judges that the related network element equipment or the current link does not support the data service bearer switching.
Specifically, the relevant network element device or the current link does not support the data service bearer switching, which may specifically include the following cases: at least one of the mobility management entity and the target SGSN does not support the data service bearer switching, or a GTP-C link between the MME and the SGSN fails, or a 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 Number of Iu Instances field value in the handover request may be modified to 1.
Step 306: and sending the single switching request to a mobile switching Server (MSC Server).
Step 307: the MSC Server transmits a Prepare Handover Request (Prepare Handover Request) to a Target mobile switching center (Target MSC).
It should be noted that this step is an optional step. In practical application, the method can be selected and used according to actual requirements.
Step 308: the MSC Server sends a Relocation Request (Relocation Request) to the target RNC.
The relocation request is for requesting the target RNC to allocate CS resources for carrying voice traffic.
Step 309: the target RNC transmits a Relocation request acknowledge (Relocation request acknowledge) message to the target MSC.
Step 310: the target MSC sends a Prepare handover request response (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: and establishing circuit connection between the target MSC and the MSC Server.
This step is also an optional step.
And finishing the switching process of the voice service bearer of the UE.
In this embodiment, by modifying the field value of the Number of Iu fields in the Source to Target transitiontainer in the dual handover request from 2 to 1, the dual handover request can be converted into a single handover request indicating that the voice service bearer of the terminal needs to be switched, without changing the existing handover flow greatly, and the handover of the voice service bearer can be completed at a low cost.
The embodiment of the application also provides a device for switching the voice service bearer. The apparatus may be a mobility management entity.
Fig. 4 is a schematic diagram of an apparatus for performing handover on a voice service bearer according to an embodiment of the present invention. As shown in fig. 4, the apparatus may include:
an obtaining unit 401, configured to obtain a dual handover request sent by an enodeb, where the dual handover request is used to request to switch a voice service bearer and a data service bearer of a terminal;
in practical applications, 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 the measurement report back to the eNodeB. The measurement report may include information such as the received signal strength of the terminal.
The eNodeB can analytically determine whether the current channel condition of the terminal is good or not according to the measurement report. When the eNodeB determines that the terminal needs to perform the dual handover, the eNodeB may send the dual handover request to the mobility management entity. In the invention, the voice service mainly refers to a service that a terminal carries out voice call through a mobile network, and the data service mainly refers to a service that the terminal carries out packet transmission through the mobile network; the simultaneous handover of voice service bearer and data service bearer may be referred to as dual handover.
A determining unit 402, configured to determine that the data service bearer cannot be successfully switched;
the data service mainly refers to a service in which a terminal accesses the internet through data traffic of a mobile network. The network element involved in the data service bearer switching may include: mobility Management Entity (MME), Serving GPRS Support Node (SGSN), and so on.
The mobility management entity may determine that the data service bearer cannot be successfully handed over. 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.
A converting unit 403, 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-switching request can be converted into a single-switching request indicating that the voice service bearer of the terminal needs to be switched, so as to solve the problem that the voice service bearer cannot be switched due to the fact that the data service bearer cannot be switched when the dual-switching is performed in the prior art.
A sending unit 404, configured to send the single handover request to a mobile switching center.
After the mobile switching center receives the single switching request, the switching of the voice service bearing can be completed through subsequent steps.
In the prior art, the handover process of data service bearer in dual handover mainly includes: the MME sends a Forward Relocation Request message to a target SGSN, and after receiving the Forward Relocation Request message sent by the MME, the target SGSN sends the Relocation Request message to a Radio Network Controller (RNC) so as to Request the RNC to allocate Packet Switching (PS) resources. The PS resource is a resource used for carrying data service after handover. The switching process of the voice service bearer in the dual handover mainly comprises the following steps: a Mobile Switching Center (MSC) sends a Relocation Request message to an RNC to Request the RNC to allocate a Circuit Switched (CS) resource. The CS resource is a resource used for carrying a voice service after handover.
However, in the existing dual handover procedure, the RNC is configured to respond to the Relocation Request message sent by the SGSN and then respond to the Relocation Request message sent by the MSC. Therefore, when the RNC cannot receive the location Request message, the RNC cannot respond to the location 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 handed over.
In this embodiment, when it is determined that the data service bearer cannot be successfully switched, the dual-handover request is converted into a single-handover request indicating that the voice service bearer of the terminal needs to be switched, so that the voice service bearer can be continuously switched; that is to say, in this embodiment, when the system has the capability of performing the handover of the voice service bearer but cannot complete the handover of the data service bearer, the handover of the voice service bearer can still be completed, thereby solving the problems in the prior art and improving the success rate of the handover of the voice service bearer. On the other hand, the main purpose of voice service is to enable voice communication, such as making a call, between terminals. And making a call is the most basic function of a terminal (handset). Preferentially ensuring that the function can be realized and improving the use experience of the user.
In practical applications, the determining unit 402 may be specifically configured to:
and determining that the mobility management entity does not support data service bearer switching.
In practical applications, the determining unit 402 may be further configured to:
determining that the target GPRS service support node does not support data service bearer switching.
In practical applications, the determining unit 402 may be further configured to:
and determining that the link required for switching the data service bearer has a fault.
In practical applications, the determining unit 402 may be further configured to:
determining that the terminal is a non-emergency call subscriber and determining that the mobility management entity does not support handover of the non-emergency call subscriber.
In practical applications, the determining unit 402 may be further configured to:
determining that the mobility management entity does not support 2G or 3G Packet Switched (PS) handover;
or, determining that the mobility management entity does not support single wireless voice call continuity (SRVCC) dual handover.
In practical applications, the determining unit 402 may be further configured to:
determining that the mobility management entity cannot successfully resolve the domain name of the target GPRS service support node.
In practical applications, the determining unit 402 may be further configured to:
and determining that the version of the GPRS tunnel protocol control plane of the target GPRS service support node does not support data service bearer switching.
In practical application, the dual handover request may include a first identifier, where the first identifier is used to indicate that the handover request type is a dual handover type; the conversion unit 403 may specifically be configured to:
and modifying the first identifier in the double-switching request into a second identifier, wherein the second identifier is used for indicating that the type of the switching request is a single-switching type.
In practical application, the field value of the IU instance Number of IuInstances field in the source-to-target transparent container in the dual-switch request is 2; the conversion unit 403 may specifically be configured to:
modifying the field value of the Number of Iu Instances field in the source-to-target transparent container in the dual-switch request from 2 to 1.
The embodiment of the application also provides a system for switching the voice service bearer. The system may include an evolved base station and a mobility management entity;
the evolution base station is used for sending a dual handover request to the mobile management entity; the double-switching request is used for requesting the switching of the voice service bearing and the data service bearing of the terminal;
the mobile management entity is used for acquiring the double switching request; determining that the data traffic bearer cannot be successfully switched; converting the double-switching request into a single-switching request, wherein the single-switching request is used for requesting to switch the voice service bearer; and sending the single switching request to a mobile switching center.
The embodiment of the application also provides another system for switching the voice service bearer. The system comprises a mobile management entity and a mobile switching center;
the mobile management entity is used for acquiring a double-switching request sent by an evolution base station, wherein the double-switching request is used for requesting to switch a voice service bearer and a data service bearer of a terminal; determining that the data traffic bearer cannot be successfully switched; converting the double-switching request into a single-switching request, wherein the single-switching request is used for requesting to switch the voice service bearer; sending the single handover request to the mobile switching center;
the mobile switching center is used for receiving the single switching request.
In practical 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, another apparatus for switching a voice service bearer is provided in this embodiment of the present application, where the apparatus may be a host server including computing capability, or a personal computer PC, or a portable computer or terminal, and the present application does not limit a specific implementation of the apparatus.
Fig. 5 is a schematic structural component 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 (processor)510, a communication Interface (Communications Interface)520, a memory (memory)530, and a bus 540.
In particular, the computer execution instructions 532 may 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 embodiments of the present application.
Memory 530 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The memory 530 is used for storing computer-executable instructions, and the processor 510 is connected to the memory 530 through the bus, and when the apparatus for switching a voice service bearer is operated, the processor 510 executes the computer-executable instructions 532 stored in the memory 530, so that the processor executes the method for switching a voice service bearer provided in the embodiment of the present application.
The present application also provides a computer readable medium. The computer-readable medium includes computer-executable instructions, so that when a processor of a computer executes the computer-executable instructions, the computer executes the method for switching the voice service bearer provided in the embodiment of the present application.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of electronic hardware and computer software. To clearly illustrate this interchangeability of parts of hardware and software, various illustrative components and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or a combination of hardware and software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (19)
1. A method for switching voice service bearer is characterized in that the method comprises the following steps:
a mobile management entity obtains a double-switching request sent by an evolution base station, wherein the double-switching request is used for requesting to switch a voice service bearer and a data service bearer of a terminal;
the mobility management entity determining that the data traffic bearer cannot be successfully handed over;
the mobile management entity converts the double switching request into a single switching request, and the single switching request is used for requesting to switch the voice service bearer;
the mobile management entity sends the single switching request to a mobile switching center;
the determining, by the mobility management entity, that the data traffic bearer cannot be successfully handed over comprises:
the mobile management entity determines that the mobile management entity does not support data service bearer switching;
and/or the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over comprises:
the mobile management entity determines that a target GPRS service support node does not support data service bearer switching;
and/or the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over comprises:
and the mobile management entity determines that the link required for switching the data service bearer has a fault.
2. The method of claim 1, wherein the determining, by the mobility management entity, that the mobility management entity does not support data traffic bearer switching comprises:
the mobility management entity determines that the terminal is a non-emergency call subscriber and determines that the mobility management entity does not support handover of the non-emergency call subscriber.
3. The method of claim 1, wherein the determining, by the mobility management entity, 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 Packet Switched (PS) handover of 2G or 3G;
or, the mobility management entity determines that the mobility management entity does not support single wireless voice call continuity (SRVCC) dual handover.
4. The method of claim 1, wherein the determining by the mobility management entity that the target GPRS serving support node does not support data service bearer switching comprises:
the mobility management entity determines that the mobility management entity cannot successfully resolve the domain name of the target GPRS service support node.
5. The method of claim 1, wherein the determining by the mobility management entity that the target GPRS serving support node does not support data service bearer switching comprises:
and the mobile management entity determines that the version of the GPRS tunnel protocol control plane of the target GPRS service support node does not support the data service bearer switching.
6. The method according to any of claims 1-5, 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 converting the dual handover request into a single handover request by the mobility management entity comprises:
and the mobile management entity modifies the first identifier in the double-switching request into a second identifier, wherein the second identifier is used for indicating that the type of the switching request is a single-switching type.
7. The method of claim 6, wherein the field value of IU instance Number of IU Instances field in the source-to-target transparent container in the dual switch request is 2; the modifying, by the mobility management entity, the first identity to a second identity in the dual handover request comprises:
the mobility management entity modifies the field value of the Number of IuInstances field in the source-to-target transparent container in the dual handover request from 2 to 1.
8. An apparatus for handing over a voice traffic bearer, comprising:
an obtaining unit, configured to obtain a dual handover request sent by an evolved base station, where the dual handover request is used to request to switch a voice service bearer and a data service bearer of a terminal;
a determining unit, configured to determine that the data service bearer cannot be successfully switched;
a conversion 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 a mobile switching center;
the determining unit is specifically configured to:
determining that the mobility management entity does not support data service bearer switching;
and/or the determining unit is specifically configured to:
determining that a target GPRS service support node does not support data service bearer switching;
and/or the determining unit is specifically configured to:
and determining that the link required for switching the data service bearer has a fault.
9. The apparatus according to claim 8, wherein the determining unit is specifically configured to:
determining that the terminal is a non-emergency call subscriber and determining that the mobility management entity does not support handover of the non-emergency call subscriber.
10. The apparatus according to claim 8, wherein the determining unit is specifically configured to:
determining that the mobility management entity does not support 2G or 3G Packet Switched (PS) handover;
or, determining that the mobility management entity does not support single wireless voice call continuity (SRVCC) dual handover.
11. The apparatus according to claim 8, 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.
12. The apparatus according to claim 8, wherein the determining unit is specifically configured to:
and determining that the version of the GPRS tunnel protocol control plane of the target GPRS service support node does not support data service bearer switching.
13. The apparatus according to any of claims 8-12, 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 conversion unit is specifically configured to:
and modifying the first identifier in the double-switching request into a second identifier, wherein the second identifier is used for indicating that the type of the switching request is a single-switching type.
14. The apparatus according to any of claims 8-12, wherein the field value of the IU instance Number of IU Instances field in the source-to-target transparent container in the dual handover request is 2; the conversion unit is specifically configured to:
modifying the field value of the Number of Iu Instances field in the source-to-target transparent container in the dual-switch request from 2 to 1.
15. A system for handover of a voice service bearer, the system comprising an evolved base station and a mobility management entity;
the evolution base station is used for sending a dual handover request to the mobile management entity; the double-switching request is used for requesting the switching of the voice service bearing and the data service bearing of the terminal;
the mobile management entity is used for acquiring the double switching request; determining that the data traffic bearer cannot be successfully switched; converting the double-switching request into a single-switching request, wherein the single-switching request is used for requesting to switch the voice service bearer; sending the single switching request to a mobile switching center;
the determining, by the mobility management entity, that the data traffic bearer cannot be successfully handed over comprises:
the mobile management entity determines that the mobile management entity does not support data service bearer switching;
and/or the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over comprises:
the mobile management entity determines that a target GPRS service support node does not support data service bearer switching;
and/or the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over comprises:
and the mobile management entity determines that the link required for switching the data service bearer has a fault.
16. A system for handover of a voice service bearer, the system comprising a mobility management entity and a mobile switching center;
the mobile management entity is used for acquiring a double-switching request sent by an evolution base station, wherein the double-switching request is used for requesting to switch a voice service bearer and a data service bearer of a terminal; determining that the data traffic bearer cannot be successfully switched; converting the double-switching request into a single-switching request, wherein the single-switching request is used for requesting to switch the voice service bearer; sending the single handover request to the mobile switching center;
the mobile switching center is used for receiving the single switching request;
the determining, by the mobility management entity, that the data traffic bearer cannot be successfully handed over comprises:
the mobile management entity determines that the mobile management entity does not support data service bearer switching;
and/or the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over comprises:
the mobile management entity determines that a target GPRS service support node does not support data service bearer switching;
and/or the determining, by the mobility management entity, that the data service bearer cannot be successfully handed over comprises:
and the mobile management entity determines that the link required for switching the data service bearer has a fault.
17. The system of claim 16, further comprising an evolved base station configured to send the dual handover request to the mobility management entity.
18. An apparatus for handing over a voice traffic bearer, comprising: a processor, a memory, a bus, and a communication interface;
the memory is used for storing computer-executable instructions, the processor is connected with the memory through the bus, when the device for switching voice service bearer is operated, the processor executes the computer-executable instructions stored in the memory, so that the processor executes the method for switching voice service bearer according to any one of claims 1-7.
19. A computer-readable medium comprising computer-executable instructions for a processor of a computer to perform the method for handover of a voice traffic bearer according to any one of claims 1 to 7 when the computer executes the computer-executable instructions.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2014/085632 WO2016029479A1 (en) | 2014-08-30 | 2014-08-30 | Voice service bearer switching method, relevant apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105900484A CN105900484A (en) | 2016-08-24 |
| CN105900484B true CN105900484B (en) | 2020-02-14 |
Family
ID=55398684
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201480021489.9A Active CN105900484B (en) | 2014-08-30 | 2014-08-30 | Switching method, related device and system for voice service bearer |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105900484B (en) |
| WO (1) | WO2016029479A1 (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101999244A (en) * | 2008-01-14 | 2011-03-30 | 诺泰网络有限公司 | Single radio voice call continuity (SR-VCC) |
| CN102067669A (en) * | 2008-06-16 | 2011-05-18 | 三星电子株式会社 | Method and system for managing handover in radio access networks |
| CN103202066A (en) * | 2010-11-04 | 2013-07-10 | 株式会社Ntt都科摩 | Mobile communications method, wireless access network device, and mobile management node |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102238679B (en) * | 2010-05-04 | 2016-01-20 | 中兴通讯股份有限公司 | Single radio voice call continuity realization method and system |
| CN102958054B (en) * | 2012-11-26 | 2016-01-06 | 中国联合网络通信集团有限公司 | network handover process method, mobile management entity, base station and network system |
| WO2014121825A1 (en) * | 2013-02-06 | 2014-08-14 | Telefonaktiebolaget L M Ericsson (Publ) | A node and method for a combined single radio voice call continuity and a packet switched handover |
-
2014
- 2014-08-30 WO PCT/CN2014/085632 patent/WO2016029479A1/en active Application Filing
- 2014-08-30 CN CN201480021489.9A patent/CN105900484B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101999244A (en) * | 2008-01-14 | 2011-03-30 | 诺泰网络有限公司 | Single radio voice call continuity (SR-VCC) |
| CN102067669A (en) * | 2008-06-16 | 2011-05-18 | 三星电子株式会社 | Method and system for managing handover in radio access networks |
| CN103202066A (en) * | 2010-11-04 | 2013-07-10 | 株式会社Ntt都科摩 | Mobile communications method, wireless access network device, and mobile management node |
Non-Patent Citations (1)
| Title |
|---|
| Correction on PS HO failure;NTT DOCOMO;《3GPP TSG SA WG2 Meeting #82 S2-105367》;20101109;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105900484A (en) | 2016-08-24 |
| WO2016029479A1 (en) | 2016-03-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6669233B2 (en) | Wireless communication system, first wireless station, second wireless station, and communication control method | |
| US11432351B2 (en) | Service continuity ensuring method, control plane gateway, and mobility management network element | |
| CN107734573B (en) | Switching method, base station and communication system | |
| US11463981B2 (en) | Location information reporting method and apparatus | |
| US10986543B2 (en) | Method and device for determining a bearer identifier, and storage medium therefor | |
| US11184827B2 (en) | Network switching method, network device, and terminal device | |
| US10517121B2 (en) | Service processing method, related apparatus, and system | |
| JP2016513418A (en) | Service control method, mobility management entity, and mobile switching center | |
| CN110519842B (en) | Communication method and device | |
| RU2732736C1 (en) | Communication method, secondary network node and terminal | |
| CN109600805B (en) | Communication method, device and system | |
| KR101432510B1 (en) | Method and apparatus for processing call of mixing heterogeneous mobile communication | |
| JP2017519392A (en) | Indication of IMEISV via MAP for inter-MSC handover | |
| EP3627891A1 (en) | Communication method, network device, and terminal device | |
| CN105900484B (en) | Switching method, related device and system for voice service bearer | |
| CN112469077B (en) | Method and device for forwarding service data packet | |
| CN106576278B (en) | Method, device and system for transmitting SRVCC capability information | |
| CN107277866B (en) | Data service switching method, device, base station and system | |
| KR102121970B1 (en) | Method and apparatus for processing call | |
| KR101817267B1 (en) | Paging apparatus for providing voice service on heterogeneous network and method thereof | |
| CN116686339A (en) | Method and apparatus for switching between different RATs | |
| KR20200070174A (en) | Method and apparatus for processing call | |
| KR20140046235A (en) | Apparatus and method for controlling loads | |
| KR20140017277A (en) | Apparatus and method for managing location information of subscribers | |
| KR20150040131A (en) | Method And Apparatus for Providing Downlink Data Notification |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |