WO2016106559A1

WO2016106559A1 - Joint registration method and apparatus

Info

Publication number: WO2016106559A1
Application number: PCT/CN2014/095566
Authority: WO
Inventors: 吴晓波; 崇卫微
Original assignee: 华为技术有限公司
Priority date: 2014-12-30
Filing date: 2014-12-30
Publication date: 2016-07-07
Also published as: CN107113864B; CN107113864A

Abstract

Embodiments of the present invention provide a joint registration method and apparatus. An MME determines whether a UE supports an SRVCC-based eCSFB; if yes, the MME selects for the UE an MSC supporting the SRVCC-based eCSFB for registration, and if not, the MME selects for the UE an MSC not supporting the SRVCC-based eCSFB for registration by means of the method for an MSC to select for a UE an appropriate MSC for registration, the UE supporting an SRVCC-based eCSFB can trigger an SRVCC-based eCSFB procedure in the subsequent process of initiating a voice service, and CSFB call setup delay is greatly reduced by taking advantage of an SRVCC handover; the situation that the MSC with which the UE not supporting the SRVCC-based eCSFB registers is different from the MSC actually processing the voice service is avoided, and further the resulting problems of increased call setup delay and callee unreachability are also avoided.

Description

Joint registration method and device

Technical field

Embodiments of the present invention relate to the field of communications, and, more particularly, to a joint registration method and apparatus.

Background technique

Second Generation (Second Generation, 2G) or Third Generation (3G) networks such as Global System of Mobile communication (GSM) or Wideband Code Division Multiple Access (WCDMA) Basic coverage has been basically achieved. With the development of Long Term Evolution (LTE) network technologies, these LTE networks have covered some urban areas and traffic hotspots, so that in current communication networks, LTE networks coexist with 2G or 3G networks.

The core network of 2G/3G is composed of a Packet Switching (PS) domain and a Circuit Switching (CS) domain, in which voice and other CS supplementary services are supported by the CS domain. In the early stage of LTE deployment, the coverage of the LTE network is not wide enough. The voice service in the LTE system may not be mature enough. The user equipment (UE) may enter the 2G or 3G network from the LTE network during a call setup. The Circuit Switched Fallback (CSFB) technology is used by the user equipment (User Equipment, UE) under LTE coverage to process the voice service. The UE first falls back to the network with the CS domain.

The premise that the user can fall back to the 2G/3G network and perform the voice service through the CSFB process is that the UE must complete the joint registration process, register the Mobility Management Entity (MME) of the LTE network, and the CS domain of the 2G/3G network. Mobile Switching Center (MSC). In the joint registration process, the UE initiates a registration request to the MME, and the MME needs to select an MSC for the UE to register. After the joint registration, the UE camps on the LTE network side. When the UE initiates a voice service to initiate an extended service request to the LTE network side device, the network side device triggers the CSFB process. The method used in the current CSFB process to enable the UE to fall back may be a Single Radio Voice Call Continuity (SRVCC) mode, that is, the UE is switched from the LTE network to the GERAN/UTRAN network by using the SRVCC, thereby implementing the UE fallback. This way can speed up the original CSFB process and shorten the call setup time. The above process of implementing CSFB using SRVCC is simply referred to as SRVCC eCSFB (Enhanced CSFB, Enhanced CSFB). In the SRVCC-based eCSFB process, the MSC serving the UE must support both SRVCC and CSFB. We call it support for SRVCC eCSFB-based MSC (abbreviated as eCSFB MSC). However, in general, operators (such as China Mobile) have only upgraded a small number of MSCs to support eCSFB as a proxy MSC based on the original CSFB network in order to accelerate the commercial time of eCSFB and save deployment costs. Upgrade all MSCs.

In the prior art, when the UE initiates the joint registration process, the MME may uniformly allocate the UE supporting and not supporting the SRVCC eCSFB to a few eCSFB MSCs (proxy MSCs) for registration or uniformly assigning to the normal MSC for registration, or the UE may be absent. The rules are assigned to both MSCs.

If the normal UE (ie, the UE that does not support the SRVCC eCSFB) is allocated to the eCSFB MSC (proxy MSC) for registration, the ordinary UE caller cannot initiate the SRVCC eCSFB process after actually initiating the voice service request. The triggering of the normal CSFB process is handled by the normal MSC. However, since the normal MSC does not have the context of the UE, the LAU procedure must be triggered during the CSFB process to obtain the context from the registered eCSFB MSC, which additionally increases the delay of call setup. In the called scenario, if the normal UE is called to trigger the called CSFB, the paging message is sent by the registered eCSFB MSC (proxy MSC). The connected MSC that is backward of the UE is a normal MSC instead of its registered MSC. Since the called roaming retry (MTRR) or the called roaming forward (MTRF) function may not be deployed in the current network, an abnormality may occur. The scenario also causes the called party to fail, that is, the UE is called unreachable.

Therefore, in the UE joint registration process, how the MME selects a suitable MSC for the UE to register is an urgent problem to be solved.

Summary of the invention

The embodiment of the invention provides a method and a device for joint registration, which can solve how to select a suitable MSC for the UE to register in the UE joint registration overload.

In a first aspect, a method for joint registration is provided, where a mobility management entity MME receives a registration request message of a UE, and the MME determines, according to the registration request message, that the UE supports an enhanced type of SRVCC based on a single wireless voice call continuity. The circuit switch falls back eCSFB; the MME registers for the UE to select a mobile switching center MSC supporting the SRVCC based eCSFB.

With reference to the first aspect, in a first possible implementation manner, the determining, by the MME, that the UE supports the SRVCC-based eCSFB according to the registration request message includes: if the registration request message includes the UE supporting SRVCC-based The indication information of the eCSFB, the MME determines that the UE supports the SRCSCC-based eCSFB; or the registration request message includes the identifier of the UE, if the identifier of the UE that supports the SRVCC-based eCSFB saved by the MME is included The identity of the UE, the MME determines that the UE supports an SRVCC-based eCSFB.

With reference to the first possible implementation of the first aspect, in a second possible implementation, the registration request message further includes indication information that the UE supports the SRVCC, and the MME determines that the UE supports the SRVCC's eCSFB.

With reference to the first aspect, the first or the second possible implementation manner of the first aspect, in a third possible implementation manner, the MME determines that the UE does not support an SRCSCC-based eCSFB; UE selection does not support SRVCC based The eCSFB's MSC is registered.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation, the determining, by the MME, that the UE does not support the SRCSCC-based eCSFB, includes: if the registration request message includes the UE Supporting the indication information of the SRVCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE identifier that supports the SRVCC-based eCSFB saved in the MME does not include the registration request message. The identity of the UE, the MME determines that the UE does not support the SRVCC-based eCSFB.

With reference to the first or second possible implementation of the first aspect, in a fifth possible implementation, if the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark 3, Then the MME determines that the UE supports the eCSFB (LTE-> GSM SRVCC eCSFB) of the SRVCC handover from the long term evolution communication system to the global mobile communication system.

With reference to the first aspect, in a sixth possible implementation, the determining, by the MME, that the UE supports an SRCSCC-based eCSFB according to the registration request message, that: the registration request message includes an identifier of the UE, if The MME saves the identifier of the UE that supports the eCSFB (e-FB of the LTE-> GSM SRVCC) of the SRVCC handover from the long-term evolution communication system to the global mobile communication system, and the MME determines that the UE supports the slave eCSFB for SRVCC handover from long-term evolution communication system to global mobile communication system (eCSFB of LTE->GSM SRVCC).

With reference to the first aspect, any one of the first to sixth implementation manners of the first aspect, in a seventh possible implementation, if the registration request message includes the UE does not support SRVCC-based The indication information of the eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the classmark message of the UE in the registration request message does not include classmark 2 and classmark 3 at the same time, or The MME of the eCSFB supporting the LTE->GSM GSM SRVCC in the MME does not include the identifier of the UE in the registration request message, and the MME determines that the UE does not support the eCSFB of the LTE->GSM SRVCC; The MSC that does not support the SRVCC-based eCSFB is selected for registration by the UE.

With reference to the first or second possible implementation of the first aspect, in an eighth possible implementation, if the classmark information of the UE in the registration request message includes classmark 2; It is determined that the UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of SRVCC handover from the long term evolution communication system to the universal mobile communication system.

With reference to the first aspect, the first to the eighth possible implementation manners of the first aspect, in a ninth possible implementation manner, the MME determines, according to the registration request message, that the UE supports an SRCSCC-based eCSFB, The method includes: the registration request message includes an identifier of the UE, and if the MME saves a UE identifier that supports an eCSFB (eCSFB of an LTE-> UMTS SRVCC) of an SRVCC handover from a long term evolution communication system to a universal mobile communication system Including the identifier of the UE, then the The MME determines that the UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of SRVCC handover from the long term evolution communication system to the universal mobile communication system.

With reference to the first aspect, any one of the first to the eighth possible implementations of the first aspect, in the tenth possible implementation, if the registration request message includes the UE does not support SRVCC-based The indication information of the eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the classmark message of the UE in the registration request message does not include classmark 2, or is included in the MME. The identity of the UE in the registration request message is not included in the identifier of the UE supporting the eCSFB of the LTE-> UMTS SRVCC, and the MME determines that the UE does not support the eCSFB of the LTE->UMTS SRVCC, and the MME is the The UE selects an MSC that does not support SRVCC-based eCSFB for registration.

With the possible implementation of the fifth to the tenth aspects of the first aspect, in an eleventh possible implementation, if the codec type supported by the UE in the registration request message belongs to the GSM Encoding type and no UMTS codec type, or the UE identifier of the saved LTE->GSM GSM SRVCC supporting the MME includes the identifier of the UE, and the MME saves the eCSFB supporting LTE->UMTS SRVCC The MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC.

With the possible implementation of the fifth to the tenth aspects of the first aspect, in the twelfth possible implementation, if the codec type supported by the UE in the registration request message is The UMTS codec type has a GSM codec type, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved by the MME includes the identifier of the UE, and the saved MME supports the LTE->UMTS SRVCC. The identifier of the UE of the eCSFB includes the identifier of the UE, and the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

With the possible implementation of the fifth to the tenth aspects of the first aspect, in the thirteenth possible implementation, if the codec type supported by the UE in the registration request message belongs to the UMTS The codec type does not have a GSM codec type, or if the class type information carried in the registration request message includes only classmark 2, and does not include classmark 3; or the MME saves support for LTE- The identifier of the UE of the eCSFB of the UMTS SRVCC includes the identifier of the UE, and the identifier of the UE of the eCSFB of the LTE->GSM GSM SRVCC that is saved by the MME does not include the identifier of the UE, and the MME determines The UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC.

With reference to the first aspect, any one of the first to the thirteenth implementation manners of the first aspect, in the fourteenth possible implementation manner, the MME selects, for the UE, the SRVCC-based eCSFB The mobile switching center MSC performs registration, including: the MME selecting a mobile switching center MSC supporting the SRVCC-based eCSFB; the MME sending a location update request message to the MSC, so that the MSC initiates a location update procedure, as shown The location update request message includes the identity of the UE.

With reference to the first aspect, any one of the first to the fourteenth possible implementation manners of the first aspect, in the fifteenth possible implementation manner, the mobile switching center MSC supporting the SRVCC-based eCSFB refers to MSC that supports both CSFB and SRVCC functions.

With reference to the first aspect, the first to the fifteenth possible implementation manner of the first aspect, in the sixteenth possible implementation, the registration request message is an attach request message or a tracking Zone Update (TAU) request message.

With reference to the first aspect, any one of the first to the sixteenth aspects of the first aspect, in the seventeenth possible implementation, the registration request message includes a registration type cell, The registration type cell is set to the joint attachment or joint tracking area TA/location area LA update.

In a second aspect, a method for joint registration is provided, including: a mobility management entity MME receiving identifier information of a UE; and determining, by the MME, that the UE supports a single wireless voice call continuity SRVCC according to the identifier information of the UE The enhanced circuit switched fallback eCSFB; the MME registers for the UE to select a mobile switching center MSC that supports the SRVCC based eCSFB.

With reference to the second aspect, in a first possible implementation, the determining, by the MME, that the UE supports the SRVCC-based eCSFB according to the identifier of the UE, includes: if the MME saves the UE that supports the SRVCC-based eCSFB The identifier includes the identifier of the UE, and the MME determines that the UE supports an SRVCC-based eCSFB.

With reference to the second aspect, or the first possible implementation manner of the second aspect, in a second possible implementation manner, the MME determines that the UE does not support an SRCSCC-based eCSFB; and the MME selects not for the UE The MSC supporting SRVCC-based eCSFB is registered.

With reference to the second possible implementation of the second aspect, in a third possible implementation, the MME determines that the UE does not support the SRVCC-based eCSFB, and includes: supporting the SRVCC-based eCSFB saved in the MME The MME does not include the identifier of the UE, and the MME determines that the UE does not support the SRCSC-based eCSFB.

With reference to the second aspect, any one of the first to the third possible implementation manners of the second aspect, in a fourth possible implementation manner, the MME determines, according to the identifier of the UE, that the UE supports the SRVCC based The eCSFB includes: if the MME saves the UE identifier of the eCSFB (e-FB of the LTE->GSM SRVCC) supporting the SRVCC handover from the long term evolution communication system to the global mobile communication system, the identifier of the UE is included The MME determines that the UE supports eCSFB (eCSFB of LTE->GSM SRVCC) for SRVCC handover from the long term evolution communication system to the global mobile communication system.

With reference to the second aspect, any one of the first to fourth implementation manners of the second aspect, in a fifth possible implementation manner, the UE that supports the LTE->GSM GSM SRVCC eCSFB saved in the MME The identifier does not include the identifier of the UE in the registration request message, and the MME determines that the UE does not support the eCSFB of the LTE->GSM SRVCC; the MME is the UE The MSC that does not support SRVCC-based eCSFB is selected for registration.

With reference to the second aspect, any one of the first to fifth implementation manners of the second aspect, in a sixth possible implementation manner, the MME determines, according to the identifier of the UE, that the UE supports the SRVCC based The eCSFB includes: if the MME saves the identifier of the UE that supports the eCSFB (e-FB of the LTE-> UMTS SRVCC) that supports the SRVCC handover from the long term evolution communication system to the universal mobile communication system, The MME determines that the UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of SRVCC handover from the long term evolution communication system to the universal mobile communication system.

With reference to the second aspect, any one of the first to sixth implementation manners of the second aspect, in a seventh possible implementation manner, the UE that supports the LTE->UMTS SRVCC eCSFB included in the MME The MME determines that the UE does not support the eCSFB of the LTE->UMTS SRVCC, and the MME selects, for the UE, the MSC that does not support the SRCSCC-based eCSFB to register.

With reference to any of the possible implementations of the third to seventh aspects of the second aspect, in an eighth possible implementation manner, the UE identifier of the saved LTE->GSM GSM SRVCC supporting eCSFB is included in the MME. The identifier of the UE is not included in the identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC, and the MME determines that the UE supports the eCSFB of the LTE->GSM SRVCC, Supports eCSFB based on LTE->UMTS SRVCC.

With reference to any one of the third to seventh possible implementations of the second aspect, in a ninth possible implementation manner, the UE identifier of the eCSFB that supports the LTE->GSM GSM SRVCC that is saved by the MME includes the The identity of the UE, and the identifier of the UE of the MME->UMTS SRVCC supporting the eCSFB of the MME includes the identifier of the UE, and the MME determines that the UE supports the eCSFB of the LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

With reference to any of the possible implementation manners of the third to the seventh aspect of the second aspect, in the tenth possible implementation manner, the identifier of the saved UE supporting the LTE->UMTS SRVCC eCSFB is included in the identifier of the MME. The MME determines that the UE supports the eCSFB of the LTE->UMTS SRVCC, if the identifier of the UE is not included in the identifier of the UE that supports the eCSFB of the LTE->GSM SRVCC. It does not support eCSFB for LTE->GSM SRVCC.

With reference to the second aspect, the first to the tenth possible implementation manners of the second aspect, in the eleventh possible implementation manner, the mobile switching center MSC supporting the SRVCC-based eCSFB refers to supporting the CSFB function. Also supports MSCs with SRVCC functionality.

With reference to the second aspect, the first to the eleventh possible implementation manners of the second aspect, in the twelfth possible implementation manner, the identifier information of the UE is an IMSI or an IMEI of the UE.

The third aspect provides a joint registration apparatus, including: a receiving module, configured to receive a registration request message of the UE; and a processing module, configured to determine, according to the registration request message, that the UE supports a single wireless voice call continuity SRVCC Enhanced circuit switched fallback eCSFB; also used to select a mobile switching center supporting SRCSCC-based eCSFB for the UE The MSC registers.

With reference to the third aspect, in a first possible implementation, the processing module is configured to determine, according to the registration request message, that the UE supports an SRVCC-based eCSFB, including: if the registration request message includes the UE support And the processing module is configured to determine that the UE supports the SRVCC-based eCSFB; or the registration request message includes the identifier of the UE, if the device saves the support of the SRVCC-based eCSFB The identifier of the UE includes the identifier of the UE, and the processing module is configured to determine that the UE supports an SRVCC-based eCSFB.

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner, if the registration request message further includes the indication information that the UE supports the SRVCC, the processing module is further configured to determine The UE supports SRVCC based eCSFB.

With reference to the third aspect, the first or the second possible implementation manner of the third aspect, in a third possible implementation, the processing module is further configured to determine that the UE does not support the SRCSCC-based eCSFB; The UE selects an MSC that does not support the SRVCC-based eCSFB for registration.

With the third possible implementation of the third aspect, in a fourth possible implementation, the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB, including: if the registration request message includes The UE does not support the indication information of the SRVCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE identifier that supports the SRVCC-based eCSFB saved in the apparatus does not include the registration. And the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB.

With reference to the first or second possible implementation of the third aspect, in a fifth possible implementation, if the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark 3, The processing module is further configured to determine an eCSFB (eCSFB of LTE->GSM SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a global mobile communication system.

With reference to the third aspect, in a sixth possible implementation, the processing module is configured to determine, according to the registration request message, that the UE supports an SRVCC-based eCSFB, including: the registration request message includes an identifier of the UE If the device identifier of the eCSFB (eCSFB of LTE->GSM SRVCC) supporting the SRVCC handover of the long-term evolution communication system to the global mobile communication system is included in the apparatus, the processing module is used to The eCSFB (eCSFB of LTE->GSM SRVCC) that supports the SRVCC handover from the long term evolution communication system to the global mobile communication system is determined.

With reference to the third aspect, any one of the first to sixth implementation manners of the third aspect, in a seventh possible implementation, if the registration request message includes the UE does not support SRVCC-based The indication information of the eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the classmark message of the UE in the registration request message does not include classmark 2 and classmark 3 at the same time, or Support saved in the device The UE identifier of the eCSFB of the LTE-> GSM SRVCC does not include the identifier of the UE in the registration request message, and the processing module is configured to determine that the UE does not support the eCSFB of the LTE->GSM SRVCC; The UE selects an MSC that does not support SRVCC-based eCSFB for registration.

With reference to the first or second possible implementation of the third aspect, in an eighth possible implementation, if the classmark information of the UE in the registration request message includes classmark 2; The module is configured to determine eCSFB (eCSFB of LTE->UMTS SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a universal mobile communication system.

With reference to the third aspect, in a ninth possible implementation manner of the third aspect, the processing module is configured to determine, according to the registration request message, that the UE supports an SRVCC-based eCSFB, including: the registration request message includes: The identifier of the UE, if the UE identifier of the eCSFB (eCSFB of LTE->UMTS SRVCC) supporting the SRVCC handover from the long term evolution communication system to the universal mobile communication system is included in the apparatus, the identifier of the UE is included. The processing module is configured to determine eCSFB (eCSFB of LTE->UMTS SRVCC) that the UE supports SRVCC handover from the long term evolution communication system to the universal mobile communication system.

With reference to the third aspect, any one of the first to the ninth possible implementation manners of the third aspect, in the tenth possible implementation manner, if the registration request message includes the UE does not support SRVCC-based The instruction information of the eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the classmark message of the UE in the registration request message does not include the classmark 2, or the processing module includes The identifier of the UE that supports the eCSFB of the LTE-> UMTS SRVCC does not include the identifier of the UE in the registration request message, and the processing module is configured to determine that the UE does not support the eCSFB of the LTE->UMTS SRVCC, The processing module is further configured to register, for the UE, an MSC that does not support the SRVCC-based eCSFB.

With the possible implementation of the fifth to the tenth aspects of the third aspect, in the eleventh possible implementation, if the codec type supported by the UE in the registration request message belongs to the GSM Encoding type and no UMTS codec type, or the UE identifier of the saved ECU->GSM GSM SRVCC supporting the CSCS includes the identifier of the UE, and the device saves the eCSFB supporting LTE->UMTS SRVCC The identifier of the UE is not included in the identifier of the UE, and the processing module is configured to determine that the UE supports the eCSFB of the LTE->GSM SRVCC, and does not support the eCSFB based on the LTE->UMTS SRVCC.

With the possible implementation of the fifth to the tenth aspects of the third aspect, in the twelfth possible implementation, if the codec type supported by the UE in the registration request message is The UMTS codec type has a GSM codec type, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved by the device includes the identifier of the UE, and the saved of the device supports LTE->UMTS SRVCC The identifier of the UE of the eCSFB includes the identifier of the UE, and the processing module is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

With the possible implementation of the fifth to the tenth aspects of the third aspect, in the thirteenth possible implementation, if the codec type supported by the UE in the registration request message belongs to the UMTS Codec type, but no GSM codec type, or if the class type information carried in the registration request message only contains classmark 2, does not include classmark 3; or the device saves support LTE-> The identifier of the UE of the eCSFB of the UMTS SRVCC includes the identifier of the UE, and the identifier of the UE that does not include the eCSFB of the LTE->GSM GSM SRVCC is not included in the identifier of the UE, and the processing module is used by the processing module. It is determined that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC.

With reference to the third aspect, any one of the first to the thirteenth implementation manners of the third aspect, in the fourteenth possible implementation manner, the processing module is configured to select support for the UE based on the SRVCC The mobile switching center MSC of the eCSFB is registered, including: the processing module is configured to select a mobile switching center MSC supporting the SRVCC-based eCSFB; the apparatus further includes a sending module, the sending module is configured to send to the MSC a location update request message, so that the MSC initiates a location update procedure, where the location update request message includes the identity identifier of the UE.

With reference to the third aspect, any one of the first to the fourteenth possible implementation manners of the third aspect, in the fifteenth possible implementation manner, the mobile switching center MSC supporting the SRVCC-based eCSFB is Refers to an MSC that supports both CSFB and SRVCC functions.

In conjunction with the third aspect, the first to the fifteenth possible implementation manner of the third aspect, in the sixteenth possible implementation, the registration request message is an attach request message or Tracking Area Update (TAU) request message.

With reference to the third aspect, any one of the first to the sixteenth aspects of the third aspect, in the seventeenth possible implementation, the registration request message includes a registration type cell, where The registration type cell is set to the joint attachment or joint tracking area TA/location area LA update.

A fourth aspect provides a joint registration apparatus, including: a receiving module, configured to receive identifier information of a UE, and a processing module, configured to determine, according to the identifier information of the UE, that the UE supports a single wireless voice call continuity SRVCC The enhanced circuit switched fallback eCSFB; the processing module is further configured to register for the UE to select a mobile switching center MSC supporting the SRVCC-based eCSFB.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the processing module is configured to determine, according to the identifier of the UE, that the UE supports an SRCSCC-based eCSFB, including: if the device saves support The identifier of the UE of the SRVCC-based eCSFB includes the identifier of the UE, and the processing module is configured to determine that the UE supports the SRCSCC-based eCSFB.

With reference to the fourth aspect, or the first possible implementation manner of the fourth aspect, in a second possible implementation, the processing module is further configured to: determine that the UE does not support an SRCSCC-based eCSFB; Choose not to support SRVCC based The MSC of eCSFB is registered.

In conjunction with the second possible implementation of the fourth aspect, in a third possible implementation, the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB, including: if the device saves the support The processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB, if the identifier of the UE is not included in the UE identifier of the SRVCC-based eCSFB.

With reference to the fourth aspect, any one of the first to the third possible implementation manners of the fourth aspect, in a fourth possible implementation, the processing module is configured to determine, according to the identifier of the UE, the UE Supporting the SRVCC-based eCSFB includes: if the MME saves the UE identifier of the eCSFB (LTE-> GSM SRVCC eCSFB) supporting the SRVCC handover from the long-term evolution communication system to the global mobile communication system, including the identifier of the UE, The processing module is then configured to determine eCSFB (eCSFB of LTE->GSM SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a global mobile communication system.

With reference to the fourth aspect, any one of the first to fourth implementation manners of the fourth aspect, in a fifth possible implementation, if the eCSFB supporting the LTE->GSM SRVCC is saved in the device The UE identifier does not include the identifier of the UE in the registration request message, and the processing module is configured to determine that the UE does not support the eCSFB of the LTE->GSM SRVCC, and the processing module is configured to select the UE The MSC of the SRVCC-based eCSFB is not supported for registration.

With reference to the fourth aspect, any one of the first to fifth implementation manners of the fourth aspect, in a sixth possible implementation, the processing module is configured to determine, according to the identifier of the UE, the UE Supporting the SRVCC-based eCSFB includes: including, if the device holds, the UE identifier of the eCSFB (e-FB of the LTE->UMTS SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the universal mobile communication system And the processing module is configured to determine eCSFB (eCSFB of LTE->UMTS SRVCC) that the UE supports SRVCC handover from the long term evolution communication system to the universal mobile communication system.

With reference to the fourth aspect, any one of the first to sixth implementation manners of the fourth aspect, in a seventh possible implementation, if the device includes an eCSFB supporting LTE->UMTS SRVCC The processing module is configured to determine that the UE does not support the eCSFB of the LTE->UMTS SRVCC, and select, for the UE, the MSC that does not support the SRCSCC-based eCSFB to register.

In conjunction with any of the possible implementations of the third to seventh aspects of the fourth aspect, in an eighth possible implementation, if the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device is included An identifier of the UE, where the identifier of the UE that supports the eCSFB of the LTE-> UMTS SRVCC is not included in the identifier of the UE, the processing module is configured to determine that the UE supports LTE->GSM SRVCC eCSFB does not support eCSFB based on LTE->UMTS SRVCC.

With reference to any of the possible implementations of the third to seventh aspects of the fourth aspect, in a ninth possible implementation, the device identifier of the eCSFB supporting the LTE->GSM GSM SRVCC saved by the device includes the The identity of the UE and the device The identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC includes the identifier of the UE, and the processing module is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports LTE->UMTS SRVCC eCSFB.

With reference to any of the possible implementations of the third to seventh aspects of the fourth aspect, in the tenth possible implementation, the identifier of the UE that supports the LTE->UMTS SRVCC-enabled eCSFB is included in the apparatus. And the processing module is configured to determine that the UE supports LTE->UMTS SRVCC, where the identifier of the UE is not included in the identifier of the UE that supports the eCSFB of the LTE->GSM SRVCC. eCSFB does not support eCSFB for LTE->GSM SRVCC.

With reference to the fourth aspect, any one of the first to the tenth implementation manners of the fourth aspect, in the eleventh possible implementation manner, the mobile switching center MSC supporting the SRVCC-based eCSFB refers to An MSC that supports the CSFB function and supports the SRVCC function.

With reference to the fourth aspect, any one of the first to the eleventh possible implementation manners of the fourth aspect, in the twelfth possible implementation manner, the identifier information of the UE is an IMSI or an IMEI of the UE .

Based on the technical solution provided by the embodiment of the present invention, the MME determines whether the UE supports the eCSFB based on the SRVCC. If supported, the MME selects the MSC that supports the SRCSCC-based eCSFB for the UE to register. If not, the MME does not support the UE selection. The MSC of the SRVCC-based eCSFB is registered. The foregoing MSC is a method for the UE to select a suitable MSC for registration, so that the UE supporting the SRVCC-based eCSFB can trigger the SRCSCC-based eCSFB process in the subsequent process of initiating the voice service, and the advantage of the SRVCC handover is greatly shortened when the CSFB call is established. The MSC that does not support the UE registration of the eCSFB based on the SRVCC is also different from the MSC that actually processes the voice service, thereby avoiding the problem of increased call setup delay and unreachable call.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention or the description of the prior art will be briefly described below. Obviously, the drawings described below are only the present invention. For some embodiments, other drawings may be obtained from those of ordinary skill in the art without departing from the drawings.

FIG. 1 is a schematic diagram of a network architecture based on an embodiment of the present invention.

FIG. 2 is a schematic flowchart of a joint registration method according to an embodiment of the present invention.

FIG. 3 is a schematic flowchart of a joint registration method provided by an embodiment of the present invention.

FIG. 4 is a schematic flowchart of a joint registration method provided by an embodiment of the present invention.

FIG. 5 is a schematic block diagram of an apparatus for joint registration provided by an embodiment of the present invention.

FIG. 6 is a schematic block diagram of an apparatus for joint registration provided by an embodiment of the present invention.

FIG. 7 is a schematic block diagram of an apparatus for joint registration provided by an embodiment of the present invention.

FIG. 8 is a schematic block diagram of an apparatus for joint registration provided by 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 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 shall fall within the scope of the present invention.

FIG. 1 is a schematic diagram of a network architecture based on an embodiment of the present invention. It should be understood that the network architecture shown in FIG. 1 is a preferred application architecture of the embodiment of the present invention, but the embodiment of the present invention may also be based on other network architectures, which is not limited by the embodiment of the present invention.

As shown in FIG. 1 , in a network architecture consisting of a UE, an eNodeB (Evolved Node B), an MME, an MSC, a BSC/RNC, and an HSS/HLR, the UE may initiate a registration request to the LTE network side device, where the registration request is Indicates that the registration type is a joint registration. And the registration request message indicates whether the UE supports the SRVCC eCSFB; the eNodeB can transmit the registration request message of the UE to the MME; the MME can accept the joint registration request message sent by the UE, determine whether the UE supports the SRVCC eCSFB, and specifically support which type The SRVCC eCSFB selects a suitable MSC for the determined UE to register, and sends a location update request message to the MSC to trigger a location update procedure, thereby completing the CS domain registration procedure of the UE; the MSC may receive the MME location update request message, triggering In the CS domain registration process, the MSC involved in the present invention may be an MSC supporting only the ordinary CSFB, or may support an MSC based on the SRVCC eCSFB (ie, supporting both SRVCC and CSFB), and the SGS port is only between the former and the MME, and the latter There are both SGS port and SV port between the MME and the MME.

The network architecture of the present invention and the devices therein can be applied to other embodiments of the present invention, and the present invention does not describe them.

FIG. 2 is a schematic flowchart of a joint registration method according to an embodiment of the present invention. The method may be performed by any suitable means, such as by an MME, although embodiments of the invention are not limited thereto.

As shown in Figure 2, the method includes:

S201. The mobility management entity MME receives a registration request message of the UE.

The registration request message is an Attach request message or a Tracking Area Update (TAU) request message. The registration request message includes a registration type cell, and the registration type cell is set to a joint attachment or joint tracking area TA/location area LA update.

S202. The MME determines, according to the registration request message, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC;

Specifically, the MME determines that the UE supports the SRCSCC-based eCSFB, and if the registration request message includes the UE supports the SRVCC-based eCSFB, the MME determines that the UE supports the SRVCC-based eCSFB. .

Or the determining, by the MME, that the UE supports the SRCSCC-based eCSFB, if the registration request message includes the indication information that the UE supports the SRVCC-based eCSFB, and the registration request message further includes the UE supporting the SRVCC The indication information, the MME determines that the UE supports the SRVCC-based eCSFB. Or the registration request message includes an identifier of the UE, and if the identifier of the UE that supports the SRVCC-based eCSFB saved by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB based on the SRVCC. . Specifically, the MME determines that the UE supports the SRCSCC-based eCSFB, including: the MME saves an eCSFB user form (whitelist/map table), and the whitelist/map table records the support of the SRVCC eCSFB-based user. Identification information (identity identifier), which may specifically be an IMSI, an IMEI, or the like. If the registration request message sent by the UE carries the identity information of the UE in the whitelist/map table, the MME determines that the UE supports the SRVCC-based eCSFB. Optionally, in another embodiment of the present invention, the identifier information of the UE may be sent by the UE to the MME in the registration request message, or the UE may send the identifier information of the UE to the MME, and the MME actively acquires the identifier of the UE. information. The MME may maintain the whitelist/map table periodically or irregularly. For example, the MME may periodically update the form, add new user identity information based on the SRVCC eCSFB to the form, and delete the aging user identity information.

Further, if the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark 3, the MME determines that the UE supports eCSFB (LTE) of SRVCC handover from the long term evolution communication system to the global mobile communication system. -> GSM SRVCC eCSFB). The classmark 2 is used to indicate that the UE supports SRVCC handover to GERAN or UTRAN (the MS supports SRVCC to GERAN or UTRAN); the classmark 3 is used to indicate that the UE supports SRVCC handover to the GERAN. Further, if the codec type supported by the UE in the registration request message has both a UMTS codec type and a GSM codec type, the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, And supporting LTE->UMTS SRVCC-based eCSFB; or if the codec type supported by the UE in the registration request message does not have a UMTS codec type and only a GSM codec type, the MME determines that the UE only supports eCSFB of LTE->GSM SRVCC does not support eCSFB based on LTE->UMTS SRVCC.

Or, in an embodiment of the present invention, the MME determines, according to the registration request message, that the UE supports an SRVCC-based eCSFB, including: the registration request message includes an identifier of the UE, if the MME saves The UE identifies the UE identifier of the eCSFB (LTE-> GSM SRVCC eCSFB) of the SRVCC handover from the long-term evolution communication system to the global mobile communication system, and the MME determines that the UE supports the long-term evolution communication System to global mobile communication system SRVCC handover eCSFB (LTE-> GSM SRVCC eCSFB). That is, the identity identifier of the UE carried in the registration request message belongs to the saved MME supporting the SRVCC supporting the long-term evolution communication system to the global mobile communication system. In the UE white list of the switched eCSFB (LTE-> GSM SRVCC eCSFB), the MME determines that the UE supports the eCSFB of the SRVCC handover from the long term evolution communication system to the global mobile communication system (LTE-> GSM SRVCC eCSFB) ). Specifically, reference may be made to the related steps of the foregoing embodiments.

Or, the UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC of the MME includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the MME does not include the The identity of the UE, the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC. That is, the identity of the UE carried by the registration request message belongs to the UE white list of the eCSFB (e-CSFB of the LTE->GSM SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system. And in the UE white list of the eCSFB (e-FB of the LTE-> UMTS SRVCC) that is not supported by the MME and supports the SRVCC handover from the long-term evolution communication system to the universal mobile communication system, the MME determines the The UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC. Or the UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC that is saved by the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC of the MME includes the UE. The MME determines that the UE supports eCSFB of LTE->GSM SRVCC and supports eCSFB based on LTE->UMTS SRVCC. That is, the identity of the UE carried by the registration request message belongs to the UE white of the eCSFB (e-CSFB of LTE->GSM SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system. In the list, and in the UE white list of the eCSFB (e-FB of the LTE-> UMTS SRVCC) that is supported by the MME and supports the SRVCC handover from the long-term evolution communication system to the universal mobile communication system, the MME determines The UE supports eCSFB of LTE->GSM SRVCC and supports eCSFB based on LTE->UMTS SRVCC.

Or if the classmark information of the UE in the registration request message includes classmark 2, the MME determines that the UE supports the eCSFB (LTE->UMTS SRVCC) of the SRVCC handover from the long term evolution communication system to the universal mobile communication system. eCSFB). If the codec type supported by the UE in the registration request message belongs to the UMTS codec type, but does not have the GSM codec type, or if the user type identifier (classmark) information carried in the registration request message is included only Classmark 2, excluding classmark 3; then the MME determines that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC.

Or the identifier of the UE of the eCSFB supporting the LTE->UMTS SRVCC of the MME is included in the identifier of the UE, and the identifier of the UE of the eCSFB supporting the LTE->GSM SRVCC of the MME is not included in the identifier of the UE. The identity of the UE, the MME determines that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC. That is, the identity of the UE carried in the registration request message belongs to the UE white of the eCSFB (eCSFB of LTE->UMTS SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the universal mobile communication system. The eCSFB in the list, which does not belong to the MME, supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system. (UE-> GSM SRVCC eCSFB) UE whitelist.

S203. The MME registers, for the UE, a mobile switching center MSC that supports an SRCSCC-based eCSFB.

Specifically, the MME (according to an internal mapping relationship or an internal configuration) selects a mobile switching center MSC supporting an SRVCC-based eCSFB; the MME sends a location update request message to the MSC, so that the MSC initiates a location update process. The location update request message shown includes the identity of the UE. The mobile switching center MSC supporting the SRVCC-based eCSFB refers to an MSC that supports both CSFB and SRVCC capabilities.

Optionally, the method further includes: the MME determines that the UE does not support an SRVCC-based eCSFB; and the MME selects, for the UE, an MSC that does not support the SRVCC-based eCSFB to register. The determining, by the MME, that the UE does not support the SRCSCC-based eCSFB, includes: if the registration request message includes indication information that the UE does not support the SRVCC-based eCSFB, or the registration request message includes that the UE does not support the SRVCC The indication information, or the identifier of the UE that supports the SRVCC-based eCSFB saved in the MME, does not include the identifier of the UE in the registration request message, that is, the identity of the UE carried in the registration request message. Not included in the whitelist/map table saved by the MME, the MME determines that the UE does not support the SRVCC-based eCSFB.

Further, if the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the support saved in the MME The UE identifier of the eCSFB of the LTE-> GSM SRVCC does not include the identifier of the UE in the registration request message, that is, the identity of the UE carried in the registration request message is not included in the location saved by the MME. In the whitelist/map table, or the classmark message of the UE in the registration request message does not include both classmark 2 and classmark 3, the MME determines that the UE does not support the eCSFB of LTE->GSM SRVCC; The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.

Further, if the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the support included in the MME The identifier of the UE of the eCSFB of the LTE-> UMTS SRVCC does not include the identifier of the UE in the registration request message, that is, the identity of the UE carried in the registration request message is not included in the MME. In the whitelist/mapping table, or the classmark message of the UE in the registration request message does not include classmark 2, the MME determines that the UE does not support eCSFB of LTE->UMTS SRVCC, and the MME is The UE selects an MSC that does not support the SRVCC-based eCSFB for registration.

Therefore, in the registration method provided by the embodiment of the present invention, in the process of the UE performing the joint registration, the MME determines whether the UE supports the eCSFB based on the SRVCC. If supported, the MME selects the MSC that supports the SRCSCC-based eCSFB for the UE to register, if not To support, the MME selects, for the UE, the MSC that does not support the SRVCC-based eCSFB to register. The above MSC selects a suitable one for the UE. The MSC performs the registration method, so that the UE supporting the SRVCC-based eCSFB can trigger the SRVCC-based eCSFB process in the subsequent process of initiating the voice service, and the advantage of the SRVCC handover greatly shortens the CSFB call setup delay; The MSC of the UE that is based on the SRVCC-based eCSFB is different from the MSC that actually processes the voice service, thereby avoiding the call setup delay and the called unreachable problem.

Other embodiments of the present invention and the embodiment of the present invention shown in FIG. 2 can be referred to each other, and the present invention is not described in detail.

FIG. 3 is a schematic flowchart of a joint registration method according to an embodiment of the present invention. This embodiment is a specific embodiment of the embodiment shown in FIG. 2.

As shown in FIG. 3, the method includes:

S301. The UE sends a registration request message to the MME.

A UE supporting CSFB will initiate a joint registration process when it is connected to an LTE network due to reasons such as booting, roaming, or network reselection. The UE sends a registration request message to the MME, where the registration request message includes a registration type cell, and the registration type is specifically set to the joint registration or the joint tracking area TA/location area LA update, and is used to notify the MME that the UE requests joint registration. The Evolved Packet Core (EPS) domain and the 2G/3G network CS domain of the 4G network. The registration request message includes indication information that the UE supports the SRVCC-based eCSFB, and the registration request message may further include indication information that the UE supports the SRVCC.

The registration request message includes an identifier of the UE, and the identifier of the UE may be an IMSI, an IMEI, or the like of the UE.

Specifically, the registration request message may further include a network capability and a type identifier of the UE. The network capability is used to inform the MME of the network capability that the UE has, and the network capability related to the present invention is that the UE supports the SRVCC, that is, the indication information that the UE supports the SRVCC; and whether the UE is The capability of the SRVCC-based eCSFB is supported, that is, the indication information of the SRVCC-based eCSFB is supported by the UE, and the present invention is not limited thereto.

The joint registration process may specifically be a joint attach process or a joint tracking area TA/location area LA update process, and the registration request message may specifically be an Attach request message or a Tracking Area Update (TAU) request message. The registration type is specifically set to joint attachment or joint TA/LA update.

S302. After receiving the registration request message sent by the UE, the MME performs a registration process of the UE in the EPS domain.

S303. After receiving the registration request message sent by the UE, the MME determines whether the UE supports the eCSFB based on the SRVCC.

Specifically, the MME may determine whether the UE satisfies the following conditions:

1. The registration request message sent by the UE carries indication information indicating that the UE supports an eCSFB based on an SRVCC;

If the UE satisfies the above conditions, the MME may determine that the UE supports the SRVCC-based eCSFB.

Optionally, in addition to the foregoing condition 1, the MME may further determine whether the UE meets the following conditions:

2. The registration request message sent by the UE carries indication information indicating that the UE supports the SRVCC;

If the UE satisfies both conditions 1 and 2 above, the MME may determine that the UE supports the SRVCC-based eCSFB.

Alternatively, the MME may determine whether the UE satisfies the following conditions:

The registration request message includes the identifier of the UE. If the identifier of the UE that supports the SRCSCC-based eCSFB is included in the MME, the MME determines that the UE supports the eCSFB based on the SRVCC. .

Specifically, the identity identifier of the UE that is carried in the registration request message sent by the UE is included in a whitelist/map table saved by the MME, and the whitelist/map table records support for an eCSFB user based on the SRVCC. Identity information, the identity information may specifically be IMSI, IMEI, etc.;

If the UE satisfies the above condition 3, the MME may determine that the UE supports the SRVCC-based eCSFB.

S304. The MME selects an MSC for the UE, and sends a location update request message to the selected MSC.

If it is determined that the UE supports the SRVCC-based eCSFB, the MME selects an MSC that supports the SRVCC-based eCSFB for the UE to register.

Specifically, the MME adopts an internally configured mapping relationship (the mapping relationship may be used to indicate a mapping relationship between a tracking area (TA) of the LTE network where the UE is located and a GSM/UMTS network location area (LA), and the TA, The mapping relationship between the LA and the eCSFB MSC and the normal CSFB MSC, as shown in the following figure, selects an MSC that supports the SRVCC-based eCSFB, and sends a location update request message to the MSC, so that the MSC initiates a location update process. The location update request message includes an identifier of the UE, and is used to notify the MSC to start a CS domain attach/location area update procedure for the UE.

The support between the MSC and the MME supporting the SRVCC eCSFB may have both an SGs interface and an Sv interface, which can support both the CSFB function and the SRVCC function.

If it is determined that the UE does not support the SRVCC-based eCSFB, the MME selects an MSC (Ordinary MSC) that does not support the SRVCC-based eCSFB for the UE to register.

The SV port may be absent between the MSC and the MME that does not support the SRVCC-based eCSFB, and only the SGS port is supported, that is, only the CSFB function is supported and the SRVCC function is not supported.

Specifically, the MME selects an MSC that does not support the SRVCC-based eCSFB by using an internally configured mapping relationship (which can participate in the related description in S304), and sends a location update request message to the MSC, where the location update request message includes the UE. The identifier is used to notify the MSC to start a CS domain attach/location area update procedure for the UE.

S305. The MSC performs a CS domain attach/location area update process of the UE.

S306. The MSC sends a location update accept message to the MME.

S307. The MME completes an EPS registration process.

Therefore, according to the method provided by the embodiment of the present invention, in the process of the UE performing the joint registration, the MME determines whether the UE supports the eCSFB based on the SRVCC. If supported, the MME selects the MSC that supports the SRCSCC-based eCSFB for the UE to register, if not supported. Then, the MME selects, for the UE, the MSC that does not support the SRCSCC-based eCSFB to register. The foregoing MSC is a method for the UE to select a suitable MSC for registration, so that the UE supporting the SRVCC-based eCSFB can trigger the SRCSCC-based eCSFB process in the subsequent process of initiating the voice service, and the advantage of the SRVCC handover is greatly shortened when the CSFB call is established. The MSC that does not support the UE registration of the eCSFB based on the SRVCC is also different from the MSC that actually processes the voice service, thereby avoiding the call setup delay and the called unreachable problem.

Currently, some operators only deploy eCSFB (LTE->GSM CSVCC eCSFB) based on LTE to GSM (Global System of Mobile communication) SRVCC handover, and LTE to UMTS (Universal Mobile Telecommunications System, Universal) Mobile Telecommunication System) The eCSFB for SRVCC handover (LTE-> UMTS SRVCC eCSFB).

For example, China Mobile's GSM network is superior to the UMTS network. China Mobile currently only deploys the CSFB function of the UE from the LTE network to the GSM network. That is, China Mobile only supports eCSFB of LTE->GSM SRVCC, and does not support LTE->UMTS. SRVCC's eCSFB. When a UE supporting only LTE->UMTS SRVCC-based eCSFB accesses the China Mobile LTE network and initiates voice service, the network side cannot initiate the eCSFB process based on LTE->UMTS SRVCC, and cannot initiate LTE-based due to the capability of the UE. -> The eCSFB process of GSM SRVCC can only initiate a normal CSFB process. Therefore, the SRVCC eCSFB capability of the UE in this scenario has no practical significance. If the MME selects and registers the UE based on the network capability of the UE and supports the SRVCC eCSFB-based MSC, the UE can only perform the normal CSFB process after the UE initiates the voice service, and the UE will fall back to a normal MSC and then perform the voice service. This will cause the MSC registered by the UE to be different from the serving MSC in which the UE actually performs the voice service, thereby causing the problem of prolonged call and unreachable call.

Therefore, in another embodiment of the present invention, after the MME has determined that the UE supports the SRVCC eCSFB-based capability, it is further necessary to further determine whether the UE further supports eCSFB based on LTE->GSM SRVCC. If supported, the UE Select an MSC that supports SRVCC-based eCSFB for registration. If not, the UE is selected to register with the MSC that does not support the SRVCC-based eCSFB.

Specifically, reference is made to the embodiment of the invention illustrated in FIG.

After the MME determines that the UE satisfies the condition of S303, it further includes determining whether the following conditions are simultaneously met:

4. The class type information carried in the registration request message sent by the UE includes classmark 2 and classmark 3.

The classmark 2 is used to indicate that the UE supports SRVCC handover to GERAN or UTRAN (the MS supports SRVCC to GERAN or UTRAN).

The classmark 3 is used to indicate that the UE supports SRVCC handover to the GERAN.

In conjunction with condition 1, or 1 and 2 in S303, if the UE also satisfies the above condition 4, the MME determines that the UE supports eCSFB of LTE->GSM SRVCC.

Alternatively, in another embodiment of the present invention, the MME determines that the UE satisfies the following conditions:

The registration request message includes the identifier of the UE, and is included in the UE identifier of the eCSFB (e-CSFB of the LTE->GSM SRVCC) that is supported by the MME and supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system. The MME determines that the UE supports the eCSFB (LTE-> GSM SRVCC eCSFB) of the SRVCC handover from the long term evolution communication system to the global mobile communication system.

That is, the identity of the UE carried by the registration request message belongs to the UE white of the eCSFB (e-CSFB of LTE->GSM SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system. In the list, the MME determines that the UE supports eCSFB (eCSFB of LTE->GSM SRVCC) of SRVCC handover from the long term evolution communication system to the global mobile communication system.

If the MME satisfies the above condition 5, the MME determines that the UE supports the eCSFB of the LTE->GSM SRVCC.

If the MME determines that the UE supports the eCSFB of the LTE->GSM SRVCC, the MME selects an MSC supporting the SRVCC-based eCSFB for the UE to register. If the MME determines that the UE does not support the eCSFB of the LTE->GSM SRVCC, the MME selects an MSC that does not support the SRCSCC-based eCSFB for the UE to register. For details, refer to related steps in S304.

The other steps of the embodiment of the present invention may be referred to the related steps in the embodiment shown in FIG. 3. The embodiment of the present invention is a specific embodiment of the embodiment of the present invention shown in FIG. 2, and the present invention is not described herein.

Therefore, based on the method provided by the embodiment of the present invention, in the registration process of the UE, the MME further determines whether the UE supports the eCSFB based on the LTE->GSM SRVCC, in addition to determining whether the UE supports the eCSFB based on the SRVCC. If supported, the MME selects the MSC that supports the SRVCC-based eCSFB for the UE to register. Otherwise, the MME selects the MSC that does not support the SRVCC-based eCSFB for the UE to register. The method of registering the UE differently in this way can only trigger based on LTE->UMTS on the network side. In the scenario of the eCSFB of the SRVCC, on the one hand, the UE supporting the eCSFB based on the LTE->GSM SRVCC can trigger the eCSFB process based on the LTE->GSM SRVCC in the process of subsequently initiating the voice service, and the advantage of using the SRVCC handover is greatly shortened. On the other hand, the MSC that does not support UE registration based on LTE->GSM GSM SRVCC is different from the MSC that actually handles voice service, so as to avoid the call setup delay and callee. Unreachable problem.

After determining that the UE supports the eCSFB based on the LTE->GSM SRVCC, the MME may further determine whether the UE supports only the eCSFB based on the LTE->GSM SRVCC, and does not support the eCSFB based on the LTE->UMTS SRVCC; or the MME determines whether the UE supports the UE at the same time. LTE-> eCSFB for GSM SRVCC and eCSFB for LTE->UMTS SRVCC.

Specifically, after determining that the UE satisfies the foregoing conditions 1 and 4, or 1, 2, and 4, the MME further includes determining whether the UE satisfies the following conditions:

5. The codec types supported by the UE carried in the registration request message sent by the UE all belong to the GSM codec type and have no UMTS codec type;

6. The codec type supported by the UE carried in the registration request message sent by the UE has both a UMTS codec type and a GSM codec type;

In cooperation with the above conditions, if the MME determines that the UE further satisfies the condition 5, the MME may determine that the UE only supports eCSFB based on LTE->GSM SRVCC, does not support eCSFB based on LTE->UMTS SRVCC, and the MME selects one support for the UE based on SRVCC. The MSC of eCSFB is registered.

In cooperation with the above conditions, if the MME determines that the UE further satisfies the condition 6, the MME may determine that the eCSFB supporting LTE->GSM SRVCC and the eCSFB based on LTE->UMTS SRVCC are simultaneously supported, and the MME selects an MSC that supports the SRVCC eCSFB for the UE. registered.

In another embodiment of the present invention, optionally, if the MME satisfies the following conditions:

The UE identifier of the eCSFB that supports the LTE->GSM GSM SRVCC of the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC that is saved by the MME does not include the The identity of the UE, the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC;

The MME may determine that the UE only supports eCSFB based on LTE->GSM SRVCC, does not support eCSFB based on LTE->UMTS SRVCC, and the MME selects one for the UE to support registration based on SRVCC eCSFB.

The UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC that is stored by the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC of the MME includes the UE. Logo,

Then the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC, and the MME selects an MSC that supports the SRVCC eCSFB to register for the UE.

Optionally, in another embodiment of the present invention, the scenario in which the operator only deploys eCSFB of LTE->UMTS SRVCC Next, the MME determines whether the UE supports eCSFB based on LTE->UMTS SRVCC.

Specifically, the MME may determine whether the UE satisfies the following conditions at the same time:

2. The classmark information carried in the registration request message sent by the UE includes classmark 2.

The classmark 2 is used to indicate that the UE supports SRVCC handover to GERAN or UTRAN (the MS supports SRVCC to GERAN or UTRAN). If the UE satisfies the above two conditions at the same time, the MME determines that the UE supports the eCSFB of the LTE->UMTS SRVCC.

Optionally, in addition to the foregoing two conditions, the MME may further determine whether the UE meets the following conditions to determine whether the UE supports the eCSFB of the LTE->UMTS SRVCC:

3. The registration request message sent by the UE carries indication information indicating that the UE supports the SRVCC.

Optionally, the MME may determine whether the UE satisfies the following conditions:

The registration request message includes the identifier of the UE, if the MME holds the UE identifier of the eCSFB (e-CSFB of the LTE->UMTS SRVCC) supporting the SRVCC handover from the long-term evolution communication system to the universal mobile communication system. Including the identity of the UE, the MME determines that the UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of SRVCC handover from the long term evolution communication system to the universal mobile communication system.

If the MME determines that the UE supports the eCSFB of the LTE->UMTS SRVCC, the MME selects an MSC supporting the SRVCC-based eCSFB for the UE to register. If the MME determines that the UE does not support the SRVCC of LTE->UMTS, the MME selects an MSC that does not support the SRCSCC-based eCSFB for the UE to register.

The other steps of the present invention may be referred to the related steps of the embodiment of the present invention shown in FIG. 3. The embodiment of the present invention is a specific embodiment of the embodiment of the present invention shown in FIG. 2, and the present invention is not described herein.

Therefore, based on the method provided by the embodiment of the present invention, in the process of the UE performing the joint registration, the MME further determines whether the UE supports the eCSFB based on the LTE->UMTS SRVCC, in addition to determining whether the UE supports the eCSFB based on the SRVCC. If supported, the MME selects the MSC that supports the SRVCC-based eCSFB for the UE to register, and the MME selects the normal MSC for the UE to register. In the scenario that the UE is registered in the LTE->UMTS SRVCC-based eCSFB, the UE that supports the eCSFB based on the LTE->UMTS SRVCC is in the process of subsequently initiating the voice service. The eCSFB process based on LTE->UMTS SRVCC can be triggered to greatly shorten the delay of CSFB call setup by taking advantage of SRVCC handover; on the other hand, avoid MSCs that do not support UE registration based on LTE->UMTS SRVCC eCSFB and actually process voice The MSCs of the service are different, thereby avoiding the call setup delay and the called unreachable problem.

After determining that the UE supports the LTE->UMTS SRVCC-based eCSFB, the MME may further determine whether the UE supports only eCSFB based on LTE->UMTS SRVCC, and does not support eCSFB based on LTE->GSM SRVCC.

Specifically, the MME further determines, on the basis of determining that the UE satisfies the conditions of 1 and 2, or 1, 2, and 3 described above:

5. The codec types supported by the UE carried in the registration request message sent by the UE all belong to the UMTS codec type and have no GSM codec type; or

The user type identifier (classmark) information carried in the registration request message sent by the UE includes only classmark 2 and does not include classmark 3.

If the MME determines that the UE satisfies the conditions of 1, 2, and 5, or 1, 2, 3, and 5 above, the MME determines that the UE supports only eCSFB based on LTE->UMTS SRVCC, and does not support eCSFB based on LTE->GSM SRVCC The MME selects, for the UE, a registration that supports the SRVCC eCSFB-based MSC.

Optionally, the MME determines that the UE meets the following conditions:

The identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC that is saved by the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->GSM SRVCC of the MME is not included. The identity of the UE, the MME determines that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC.

If the MME determines that the UE satisfies the above condition, the MME determines that the UE only supports eCSFB based on LTE->UMTS SRVCC, does not support eCSFB based on LTE->GSM SRVCC, and the MME selects an MSC that supports SRVCC eCSFB to register for the UE. .

FIG. 4 is a schematic flowchart of a joint registration method according to an embodiment of the present invention. The method may be performed by any suitable device, for example, by an MME, which is not limited by the present invention.

As shown in FIG. 4, the method includes:

S401. The mobility management entity MME receives the identifier information of the UE.

Specifically, the identifier information of the UE may be carried by the UE in the registration request message and sent to the MME, or may be in other process messages (such as an authentication process or an identifier acquisition process, etc.) after the UE sends the registration request message. The present invention is not limited by the present invention and is carried to the MME.

The identification information of the UE may be an IMSI or an IMEI of the UE.

S402. The MME determines, according to the identifier information of the UE, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC.

Specifically, if the identifier of the UE that supports the SRVCC-based eCSFB saved by the MME includes the identifier of the UE, the MME determines that the UE supports the SRVCC-based eCSFB.

Optionally, if the MME saves the identifier of the UE that supports the eCSFB (e-FB of the LTE->GSM SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system, the MME Determining the UE branch eCSFB (LTE->GSM CSVCC eCSFB) with SRVCC handover from long-term evolution communication system to global mobile communication system.

Further, the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC of the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->GSM SRVCC of the MME is not Including the identity of the UE, the MME determines that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC. Or the UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC that is saved by the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC of the MME includes the UE. The MME determines that the UE supports eCSFB of LTE->GSM SRVCC and supports eCSFB based on LTE->UMTS SRVCC.

Optionally, if the MME saves the identifier of the UE that supports the eCSFB (e-FB of the LTE-> UMTS SRVCC) that supports the SRVCC handover from the long term evolution communication system to the universal mobile communication system, The MME determines that the UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of SRVCC handover from the long term evolution communication system to the universal mobile communication system.

Further, the UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC that is stored by the MME includes the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC of the MME includes the The identity of the UE, the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

S403. The MME registers, for the UE, a mobile switching center MSC that supports the SRCSCC-based eCSFB.

The mobile switching center MSC supporting the SRVCC-based eCSFB refers to an MSC that supports both CSFB and SRVCC functions.

Optionally, in another embodiment of the present invention, the MME determines that the UE does not support an SRVCC-based eCSFB; the MME selects, for the UE, an MSC that does not support the SRVCC-based eCSFB to register. Specifically, the UE that supports the SRVCC-based eCSFB saved in the MME does not include the identifier of the UE, and the MME determines that the UE does not support the SRVCC-based eCSFB.

Optionally, if the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the MME does not include the identifier of the UE in the registration request message, the MME determines that the UE does not support LTE->GSM The eCSFB of the SRVCC; the MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.

Optionally, the identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC included in the MME does not include the identifier of the UE, and the MME determines that the UE does not support the eCSFB of the LTE->UMTS SRVCC, where the MME The MSC that does not support the SRVCC-based eCSFB is selected for registration by the UE.

In the embodiment of the present invention, reference may be made to the related steps of the embodiment of the present invention shown in FIG. 2 and FIG. 3, that is, in the embodiment, after receiving the UE identifier, the MME determines whether the UE supports the eCSFB based on the SRVCC, and may refer to the figure. 2 and the relevant steps in Figure 3. The present invention does not describe this.

Therefore, the UE sends the UE identification information to the MME according to the method provided by the embodiment of the present invention. The MME determines whether the UE supports the eCSFB based on the SRVCC according to the identifier information of the UE. If supported, the MME selects the MSC that supports the eCSFB based on the SRVCC for the UE. Registration, if not supported, the MME selects for the UE to register with the MSC that does not support the SRVCC-based eCSFB. The foregoing MSC is a method for the UE to select a suitable MSC for registration, so that the UE supporting the SRVCC-based eCSFB can trigger the SRCSCC-based eCSFB process in the subsequent process of initiating the voice service, and the advantage of the SRVCC handover is greatly shortened when the CSFB call is established. The MSC that does not support the UE registration of the eCSFB based on the SRVCC is also different from the MSC that actually processes the voice service, thereby avoiding the call setup delay and the called unreachable problem.

FIG. 5 is a schematic block diagram of a device for joint registration provided by an embodiment of the present invention. The device may be any suitable device. For example, the device may be an MME, but the present invention is not limited thereto. The apparatus can perform the methods provided by the embodiments of the present invention illustrated in Figures 2 and 3.

As shown in Figure 5, the device includes:

The receiving module 501 is configured to receive a registration request message of the UE.

The registration request message is an Attach request message or a Tracking Area Update (TAU) request message.

The processing module 502 is configured to determine, according to the registration request message, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC;

Specifically, if the registration request message includes indication information that the UE supports the SRVCC-based eCSFB, the processing module 502 determines that the UE supports the SRVCC-based eCSFB; then the processing module determines that the UE supports the SRVCC-based eCSFB. Further, if the registration request message further includes the indication information that the UE supports the SRVCC, the processing module 502 is further configured to determine that the UE supports the SRVCC-based eCSFB.

or,

The registration request message includes an identifier of the UE. If the identifier of the UE that supports the SRVCC-based eCSFB is included in the apparatus, the processing module 502 determines that the UE supports the eCSFB based on the SRVCC. .

Optionally, if the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark 3, the processing module 502 is further configured to determine that the UE supports the long-term evolution communication system to global mobile communication. System's SRVCC handover eCSFB (LTE-> GSM SRVCC eCSFB).

Alternatively, the registration request message includes an identifier of the UE, and is included in a UE identifier of an eCSFB (eCSFB of LTE->GSM SRVCC) that supports the SRVCC handover from the long term evolution communication system to the global mobile communication system. For the identifier of the UE, the processing module 502 is configured to determine that the UE supports the eCSFB (eCSFB of the LTE->GSM SRVCC) of the SRVCC handover from the long term evolution communication system to the global mobile communication system.

Further, if the codec type supported by the UE in the registration request message belongs to the GSM coding type and is not There is a UMTS codec type, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE that holds the eCSFB supporting LTE->UMTS SRVCC is saved by the device. The processing module 502 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC.

If the codec type supported by the UE in the registration request message has both a UMTS codec type and a GSM codec type, or

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the device includes the identifier of the UE. The processing module 502 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

In another embodiment of the present invention, if the classmark information of the UE in the registration request message includes classmark 2, the processing module 502 is configured to determine that the UE supports the long-term evolution communication system to the universal mobile eCSFB for SRVCC handover of the communication system (eCSFB of LTE->UMTS SRVCC).

Or the registration request message includes the identifier of the UE, if the device saves the UE identifier of the eCSFB (e-FB of the LTE->UMTS SRVCC) supporting the SRVCC handover from the long-term evolution communication system to the universal mobile communication system Including the identifier of the UE, the processing module 502 is configured to determine that the UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of the SRVCC handover from the long term evolution communication system to the universal mobile communication system.

If the codec type supported by the UE in the registration request message belongs to the UMTS codec type, but does not have the GSM codec type, or if the user type identifier (classmark) information carried in the registration request message is included only Classmark 2, does not include classmark 3; or, the identifier of the UE that supports the eCSFB supporting LTE->UMTS SRVCC saved by the device includes the identifier of the UE, and the device saves eCSFB supporting LTE->GSM SRVCC The identifier of the UE is not included in the identifier of the UE, and the processing module 502 is configured to determine that the UE supports the eCSFB of the LTE->UMTS SRVCC, and does not support the eCSFB of the LTE->GSM SRVCC.

The processing module 502 is further configured to select, for the UE, a mobile switching center MSC that supports the SRVCC-based eCSFB to register.

Specifically, the processing module 502 is configured to select a mobile switching center MSC that supports the SRVCC-based eCSFB;

The device further includes a sending module 503, where the sending module is configured to send a location update request message to the MSC, so that the MSC initiates a location update process, where the location update request message includes the identity identifier of the UE.

Optionally, the processing module 502 is further configured to determine that the UE does not support the SRVCC-based eCSFB; and select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register. Specifically, if the registration request message includes that the UE does not support The indication information of the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE identifier that supports the SRVCC-based eCSFB saved in the apparatus does not include the registration request message. The identifier of the UE, the processing module 502 is configured to determine that the UE does not support the SRCSC-based eCSFB.

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message If the classmark 2 and the classmark 3 are not included in the classmark message, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device does not include the identifier of the UE in the registration request message, The processing module 502 is configured to determine that the UE does not support the eCSFB of the LTE->GSM SRVCC; and select, for the UE, the MSC that does not support the SRCSCC-based eCSFB to register.

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message The classmark 2 does not include the classmark 2, or the identifier of the UE in the registration request message is not included in the identifier of the UE supporting the eCSFB of the LTE->UMTS SRVCC included in the processing module, and the processing module is The processing module 502 is further configured to select, for the UE, an MSC that does not support the SRVCC-based eCSFB to register, by using the eCSFB that the UE does not support the LTE->UMTS SRVCC.

According to the apparatus provided by the embodiment of the present invention, the MME determines whether the UE supports the eCSFB based on the SRVCC in the process of the UE performing the joint registration. If supported, the MME selects the MSC that supports the eCSFB based on the SRVCC for the UE to register, if not, The MME selects an MSC that does not support the SRVCC-based eCSFB for the UE to register. The foregoing MSC is a method for the UE to select a suitable MSC for registration, so that the UE supporting the SRVCC-based eCSFB can trigger the SRCSCC-based eCSFB process in the subsequent process of initiating the voice service, and the advantage of the SRVCC handover is greatly shortened when the CSFB call is established. The MSC that does not support the UE registration of the eCSFB based on the SRVCC is also different from the MSC that actually processes the voice service, thereby avoiding the call setup delay and the called unreachable problem.

FIG. 6 is a schematic block diagram of a device for joint registration provided by an embodiment of the present invention. The device may be any suitable device. For example, the device may be an MME, but the present invention is not limited thereto. The apparatus can perform the methods provided by the embodiments of the present invention illustrated in Figures 2 and 3.

As shown in Figure 6, the device includes:

The receiver 601 is configured to receive a registration request message of the UE.

The processor 602 is configured to determine, according to the registration request message, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC;

Specifically, if the registration request message includes indication information that the UE supports the SRVCC-based eCSFB, the processor 602 determines that the UE supports the SRVCC-based eCSFB; then the processing module determines that the UE supports the SRVCC-based eCSFB. Further, if the registration request message further includes the indication information that the UE supports the SRVCC, the processor 602 is further configured to determine that the UE supports the SRVCC-based eCSFB.

or,

The registration request message includes an identifier of the UE. If the identifier of the UE that supports the SRVCC-based eCSFB saved by the device includes the identifier of the UE, the processor 602 determines that the UE supports the eCSFB based on the SRVCC. .

Optionally, if the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark 3, the processor 602 is further configured to determine that the UE supports the long-term evolution communication system to global mobile communication. System's SRVCC handover eCSFB (LTE-> GSM SRVCC eCSFB).

Alternatively, the registration request message includes an identifier of the UE, and is included in a UE identifier of an eCSFB (eCSFB of LTE->GSM SRVCC) that supports the SRVCC handover from the long term evolution communication system to the global mobile communication system. The identifier of the UE is used by the processor 602 to determine eCSFB (eCSFB of LTE->GSM SRVCC) that the UE supports SRVCC handover from the long term evolution communication system to the global mobile communication system.

Further, if the codec type supported by the UE in the registration request message belongs to the GSM coding type and does not have the UMTS codec type, or the saved UE identifier of the eCSFB supporting the LTE->GSM SRVCC The identifier of the UE is included in the identifier of the UE that is used by the device to save the eCSFB of the LTE-> UMTS SRVCC, and the processor 602 is configured to determine that the UE supports LTE-> eCSFB of GSM SRVCC does not support eCSFB based on LTE->UMTS SRVCC.

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the device includes the identifier of the UE. The processor 602 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

In another embodiment of the present invention, if the classmark information of the UE in the registration request message includes classmark 2, the processor 602 is configured to determine that the UE supports the long-term evolution communication system to the universal mobile eCSFB for SRVCC handover of the communication system (eCSFB of LTE->UMTS SRVCC).

Or the registration request message includes the identifier of the UE, if the device saves the UE identifier of the eCSFB (e-FB of the LTE->UMTS SRVCC) supporting the SRVCC handover from the long-term evolution communication system to the universal mobile communication system Including the identifier of the UE, the processor 602 is configured to determine that the UE supports from a long term evolution communication system to a universal mobile communication The system's SRVCC switch eCSFB (LTE->UMTS SRVCC eCSFB).

If the codec type supported by the UE in the registration request message belongs to the UMTS codec type, but does not have the GSM codec type, or if the user type identifier (classmark) information carried in the registration request message is included only Classmark 2, does not include classmark 3; or, the identifier of the UE that supports the eCSFB supporting LTE->UMTS SRVCC saved by the device includes the identifier of the UE, and the device saves eCSFB supporting LTE->GSM SRVCC The identifier of the UE is not included in the identifier of the UE, and the processor 602 is configured to determine that the UE supports the eCSFB of the LTE->UMTS SRVCC, and does not support the eCSFB of the LTE->GSM SRVCC.

The processor 602 is further configured to select, for the UE, a mobile switching center MSC that supports the SRVCC-based eCSFB to register.

Specifically, the processor 602 is configured to select a mobile switching center MSC that supports the SRVCC-based eCSFB;

The device further includes a transmitter 603, where the sending module is configured to send a location update request message to the MSC, so that the MSC initiates a location update process, where the location update request message includes the identity identifier of the UE.

Optionally, the processor 602 is further configured to determine that the UE does not support an SRVCC-based eCSFB; and select, for the UE, an MSC that does not support the SRVCC-based eCSFB to register. Specifically, if the registration request message includes indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes indication information that the UE does not support the SRVCC, or the support saved in the device is based on the SRVCC. The processor of the eCSFB does not include the identifier of the UE in the registration request message, and the processor 602 is configured to determine that the UE does not support the SRCSCC-based eCSFB.

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message If the classmark 2 and the classmark 3 are not included in the classmark message, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device does not include the identifier of the UE in the registration request message, The processor 602 is configured to determine that the UE does not support the eCSFB of the LTE->GSM SRVCC; and select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register.

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message The classmark 2 does not include the classmark 2, or the identifier of the UE in the registration request message is not included in the identifier of the UE supporting the eCSFB of the LTE->UMTS SRVCC included in the processing module, and the processing module is For determining that the UE does not support the eCSFB of the LTE->UMTS SRVCC, the processor 602 is further configured to select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register.

FIG. 7 is a schematic block diagram of a device for joint registration provided by an embodiment of the present invention. The device may be any suitable device. For example, the device may be an MME, but the present invention is not limited thereto. The apparatus can perform the method provided by the embodiment of the invention illustrated in FIG.

As shown in Figure 7, the device includes:

The receiving module 701 is configured to receive identifier information of the UE.

The identification information of the UE is an IMSI or an IMEI of the UE.

The processing module 702 is configured to determine, according to the identifier information of the UE, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC;

If the identifier of the UE that supports the SRVCC-based eCSFB is included in the apparatus, the processing module 702 is configured to determine that the UE supports the SRVCC-based eCSFB.

Optionally, if the MME saves the identifier of the UE that supports the eCSFB (e-FB of the LTE->GSM SRVCC) that supports the SRVCC handover from the long term evolution communication system to the global mobile communication system, the processing is performed. The module 702 is configured to determine an eCSFB (eCSFB of LTE->GSM SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a global mobile communication system.

Further, if the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device includes the identifier of the UE, the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC is not included in the identifier of the UE. For the identifier of the UE, the processing module 702 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC. or,

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the device includes the identifier of the UE. The processing module 702 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

Optionally, if the saved identifier of the eCSFB (eCSFB of the LTE->UMTS SRVCC) that is saved by the apparatus and supports the SRVCC handover of the universal mobile communication system from the long-term evolution communication system includes the identifier of the UE, The treatment The module 702 is configured to determine an eCSFB (eCSFB of LTE->UMTS SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a universal mobile communication system.

Further, the identifier of the UE that supports the LTE->UMTS SRVCC-enabled eCSFB is included in the identifier of the UE, and the identifier of the UE that supports the LTE->GSM GSM SRVCC-supported eCSFB is not included in the identifier of the UE. For the identifier of the UE, the processing module 702 is configured to determine that the UE supports the eCSFB of the LTE->UMTS SRVCC, and does not support the eCSFB of the LTE->GSM SRVCC.

The processing module 702 is further configured to select, for the UE, a mobile switching center MSC that supports the SRCSCC-based eCSFB to register.

Optionally, the processing module 702 is further configured to determine that the UE does not support the SRVCC-based eCSFB; and select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register. If the identifier of the UE that supports the SRCSCC-based eCSFB is not included in the apparatus, the processing module 702 is configured to determine that the UE does not support the SRCSCC-based eCSFB.

In another embodiment of the present invention, if the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device does not include the identifier of the UE in the registration request message, the processing module 702 For determining that the UE does not support eCSFB of LTE->GSM SRVCC,

The embodiment of the present invention may refer to the related steps of the embodiment of the present invention shown in FIG. 2 and FIG. 3, that is, the apparatus in this embodiment determines whether the UE supports the eCSFB based on the SRVCC after receiving the identifier of the UE, and may refer to the figure. 2 and the relevant steps in Figure 3. The present invention does not describe this.

FIG. 8 is a schematic block diagram of a device for joint registration provided by an embodiment of the present invention. The device may be any suitable device. For example, the device may be an MME, but the present invention is not limited thereto. The apparatus can perform the method provided by the embodiment of the invention illustrated in FIG.

As shown in Figure 8, the device includes:

The receiver 801 is configured to receive identifier information of the UE.

The identification information of the UE is an IMSI or an IMEI of the UE.

The processor 802 is configured to determine, according to the identifier information of the UE, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC;

If the identifier of the UE that supports the SRVCC-based eCSFB is included in the apparatus, the processor 802 is configured to determine that the UE supports the SRVCC-based eCSFB.

Optionally, if the MME saves the identifier of the UE that supports the eCSFB (e-FB of the LTE->GSM SRVCC) that supports the SRVCC handover from the long term evolution communication system to the global mobile communication system, the processing is performed. The 802 is configured to determine an eCSFB (eCSFB of LTE->GSM SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a global mobile communication system.

Further, if the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device includes the identifier of the UE, the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC is not included in the identifier of the UE. For the identifier of the UE, the processor 802 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC. or,

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the device includes the identifier of the UE. The processor 802 is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.

Optionally, if the saved identifier of the eCSFB (eCSFB of the LTE->UMTS SRVCC) that is saved by the apparatus and supports the SRVCC handover of the universal mobile communication system from the long-term evolution communication system includes the identifier of the UE, The processor 802 is configured to determine an eCSFB (eCSFB of LTE->UMTS SRVCC) that the UE supports SRVCC handover from a long term evolution communication system to a universal mobile communication system.

Further, the identifier of the UE that supports the LTE->UMTS SRVCC-enabled eCSFB is included in the identifier of the UE, and the identifier of the UE that supports the LTE->GSM GSM SRVCC-supported eCSFB is not included in the identifier of the UE. For the identifier of the UE, the processor 802 is configured to determine that the UE supports the eCSFB of the LTE->UMTS SRVCC, and does not support the eCSFB of the LTE->GSM SRVCC.

The processor 802 is further configured to select, for the UE, a mobile switching center MSC that supports the SRVCC-based eCSFB to register.

Optionally, the processor 802 is further configured to: determine that the UE does not support an SRCSCC-based eCSFB; select, not for the UE The MSC supporting SRVCC-based eCSFB is registered. If the identifier of the UE that supports the SRCSCC-based eCSFB saved in the device does not include the identifier of the UE, the processor 802 is configured to determine that the UE does not support the SRCSCC-based eCSFB.

In another embodiment of the present invention, if the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device does not include the identifier of the UE in the registration request message, the processor 802 For determining that the UE does not support eCSFB of LTE->GSM SRVCC,

It should be understood that, in the embodiment of the present invention, the processor may be a central processing unit ("CPU"), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration. Circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

In the implementation process, the above steps may be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

Those skilled in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the steps and composition of the various embodiments have been generally described in terms of function in the foregoing description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. General skill in the art Personnel may use different methods to implement the described functionality for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a USB flash drive, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a disk or a CD. A variety of media that can store program code.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any equivalent person can be easily conceived within the technical scope of the present invention by any person skilled in the art. Modifications or substitutions are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A joint registration method, comprising:

The mobility management entity MME receives a registration request message of the UE;

Determining, by the MME, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC according to the registration request message;

The MME registers for the UE to select a mobile switching center MSC supporting the SRVCC-based eCSFB.
The method according to claim 1, wherein the MME determines, according to the registration request message, that the UE supports an SRCSCC-based eCSFB, including:

If the registration request message includes indication information that the UE supports the SRVCC-based eCSFB, the MME determines that the UE supports the SRVCC-based eCSFB; or

The registration request message includes an identifier of the UE. If the identifier of the UE that supports the SRVCC-based eCSFB saved by the MME includes the identifier of the UE, the MME determines that the UE supports the SRCSCC-based eCSFB.
The method according to claim 2, wherein the registration request message further includes indication information that the UE supports the SRVCC, and the MME determines that the UE supports the SRVCC-based eCSFB.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The MME determines that the UE does not support an SRCSC-based eCSFB;

The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.
The method according to claim 4, wherein the MME determines that the UE does not support the SRCSCC-based eCSFB, including:

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the SRVCC-supported eCSFB saved in the MME The UE identifier does not include the identifier of the UE in the registration request message, and the MME determines that the UE does not support the SRCSCC-based eCSFB.
The method according to claim 2 or 3, wherein the method further comprises:

If the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark3, the MME determines that the UE supports the eCSFB of the SRVCC handover from the long term evolution communication system to the global mobile communication system (LTE-> eCSFB of GSM SRVCC).
The method according to claim 1, wherein the MME determines, according to the registration request message, that the UE supports an SRCSCC-based eCSFB, including:

The registration request message includes an identifier of the UE, and if the MME saves support from a long-term evolution communication system to the entire The UE identifier of the eCSFB (LTE-> GSM SRVCC eCSFB) of the SRVCC handover of the ball mobile communication system includes the identifier of the UE, and the MME determines that the UE supports the SRVCC from the long-term evolution communication system to the global mobile communication system. Switched eCSFB (e-CSFB of LTE->GSM SRVCC).
The method according to any one of claims 1-7, wherein the method further comprises:

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message The classmark message does not include the classmark 2 and the classmark 3, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the MME does not include the identifier of the UE in the registration request message, and the MME determines The UE does not support eCSFB of LTE->GSM SRVCC;

The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.
The method according to claim 2 or 3, wherein the method further comprises:

If the classmark information of the UE in the registration request message includes classmark 2; the MME determines that the UE supports eCSFB (LTE->UMTSSRVCC of SRVCC handover from the long term evolution communication system to the universal mobile communication system) eCSFB).
The method according to any one of claims 1-9, wherein the MME determines, according to the registration request message, that the UE supports an SRCSCC-based eCSFB, including:

The registration request message includes an identifier of the UE, and includes a UE identifier of an eCSFB (eCSFB of LTE->UMTS SRVCC) that supports the SRVCC handover from the long term evolution communication system to the universal mobile communication system. Determining the identity of the UE, the MME determines that the UE supports the eCSFB (eCSFB of LTE->UMTS SRVCC) of the SRVCC handover from the long term evolution communication system to the universal mobile communication system.
The method according to any one of claims 1-9, wherein the method further comprises:

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message The classmark message is not included in the classmark message, or the identifier of the UE in the registration request message is not included in the identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC included in the MME, and the MME determines the UE. eCSFB for LTE->UMTS SRVCC is not supported,

The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.
The method according to any one of claims 6-11, wherein the method further comprises:

If the codec type supported by the UE in the registration request message belongs to the GSM coding type and does not have the UMTS codec type, or the UE identifier of the eCSFB of the MME that supports the LTE->GSM SRVCC is included in the MME. Said the identity of the UE, The MME does not include the identifier of the UE of the UE supporting the LTE->UMTS SRVCC eCSFB, and the MME determines that the UE supports the eCSFB of the LTE->GSM SRVCC, and does not support the LTE-based eCSFB for UMTS SRVCC.
The method according to any one of claims 6-11, wherein the method further comprises:

If the codec type supported by the UE in the registration request message has both a UMTS codec type and a GSM codec type, or

The UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC that is stored by the MME includes the identifier of the UE, and the identifier of the UE that is the eCSFB of the LTE->UMTS SRVCC that is saved by the MME includes the identifier of the UE. And the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.
The method according to any one of claims 6-11, wherein the method further comprises:

If the codec type supported by the UE in the registration request message belongs to the UMTS codec type, but does not have the GSM codec type, or if the user type identifier (classmark) information carried in the registration request message is included only The classmark 2 includes no classmark 3; or the identifier of the UE of the MME that supports the LTE->UMTS SRVCC eCSFB includes the identifier of the UE, and the saved MME supports LTE->GSM SRVCC The identifier of the UE of the eCSFB does not include the identifier of the UE, and the MME determines that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC.
The method according to any one of claims 1 to 14, wherein the MME registers for the UE to select a mobile switching center MSC supporting the SRCSCC-based eCSFB, including:

The MME selects a mobile switching center MSC supporting an SRVCC-based eCSFB;

The MME sends a location update request message to the MSC, so that the MSC initiates a location update process, where the location update request message includes the identity identifier of the UE.
The method according to any one of claims 1 to 15, wherein the mobile switching center MSC supporting the SRVCC-based eCSFB refers to an MSC that supports both CSFB and SRVCC functions.
The method according to any one of claims 1 to 16, wherein the registration request message is an Attach request message or a Tracking Area Update (TAU) request message.
The method according to any one of claims 1-17, wherein the registration request message includes a registration type cell, and the registration type cell is set to jointly attach or joint tracking area TA/location area LA update. .
A joint registration method, comprising:

The mobility management entity MME receives the identification information of the UE;

Determining, by the MME, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC according to the identification information of the UE;

The MME registers for the UE to select a mobile switching center MSC supporting the SRVCC-based eCSFB.
The method according to claim 19, wherein the MME determines, according to the identifier of the UE, that the UE supports an SRCSCC-based eCSFB, including:

If the identifier of the UE that supports the SRVCC-based eCSFB saved by the MME includes the identifier of the UE, the MME determines that the UE supports the SRCSCC-based eCSFB.
The method according to claim 19 or 20, wherein the method further comprises:

The MME determines that the UE does not support an SRCSC-based eCSFB;

The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.
The method according to claim 21, wherein the MME determines that the UE does not support the SRCSCC-based eCSFB, including:

The MME that supports the SRVCC-based eCSFB is not included in the MME, and the MME determines that the UE does not support the SRVCC-based eCSFB.
The method according to any one of claims 19 to 22, wherein the MME determines, according to the identifier of the UE, that the UE supports an SRCSCC-based eCSFB, including:

If the MME saves the identity of the UE that supports the eCSFB (e-FB of the LTE->GSM GSM SRVCC) supporting the SRVCC handover from the long term evolution communication system to the global mobile communication system, the MME determines the UE Supports eCSFB (LTE-> GSM SRVCC eCSFB) for SRVCC handover from long-term evolution communication systems to global mobile communication systems.
The method according to any one of claims 19-23, wherein the method further comprises:

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the MME does not include the identifier of the UE in the registration request message, and the MME determines that the UE does not support the eCSFB of the LTE->GSM SRVCC;

The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.
The method according to any one of claims 19 to 24, wherein the MME determines that the UE supports the SRCSCC-based eCSFB according to the identifier of the UE, including:

If the MME holds an identifier of the UE that supports the eCSFB (eCSFB of the LTE->UMTS SRVCC) supporting the SRVCC handover from the long term evolution communication system to the universal mobile communication system, the MME determines the The UE supports eCSFB (eCSFB of LTE->UMTS SRVCC) of SRVCC handover from the long term evolution communication system to the universal mobile communication system.
The method of any of claims 19-25, wherein the method further comprises:

The identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC included in the MME does not include the identifier of the UE, and the MME determines that the UE does not support the eCSFB of the LTE->UMTS SRVCC.

The MME registers for the UE to select an MSC that does not support the SRVCC-based eCSFB.
The method according to any one of claims 22-26, wherein the method further comprises:

The UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC of the MME includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC of the MME does not include the UE. The MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC.
The method according to any one of claims 22-26, wherein the method further comprises:

The UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC that is stored by the MME includes the identifier of the UE, and the identifier of the UE that is the eCSFB of the LTE->UMTS SRVCC that is saved by the MME includes the identifier of the UE. And the MME determines that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.
The method according to any one of claims 22-26, wherein the method further comprises:

The identifier of the UE of the eCSFB supporting the LTE->UMTS SRVCC of the MME is included in the identifier of the UE, and the identifier of the UE of the eCSFB supporting the LTE->GSM SRVCC of the MME is not included in the identifier of the UE. The identity of the UE, the MME determines that the UE supports eCSFB of LTE->UMTS SRVCC, and does not support eCSFB of LTE->GSM SRVCC.
The method according to any one of claims 19-29, characterized in that said mobile switching center MSC supporting SRVCC-based eCSFB refers to an MSC supporting both CSFB function and SRVCC function.
The method according to any one of claims 19 to 30, wherein the identification information of the UE is an IMSI or an IMEI of the UE.
A joint registration device, comprising:

a receiving module, configured to receive a registration request message of the UE;

a processing module, configured to determine, according to the registration request message, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC; and is further configured to select, for the UE, a mobile switching center MSC that supports an SRVCC-based eCSFB Sign up.
The device according to claim 32, wherein the processing module is configured to determine, according to the registration request message, that the UE supports an SRVCC-based eCSFB, including:

If the registration request message includes the indication information that the UE supports the SRVCC-based eCSFB, the processing module is configured to determine that the UE supports the SRVCC-based eCSFB; or

The registration request message includes an identifier of the UE, and if the identifier of the UE that supports the SRVCC-based eCSFB is included in the apparatus, the processing module is configured to determine that the UE supports the SRVCC-based eCSFB.
The apparatus according to claim 33, wherein if the registration request message further includes the indication information that the UE supports the SRVCC, the processing module is further configured to determine that the UE supports the SRVCC-based eCSFB.
A device according to any of claims 32-34, wherein

The processing module is further configured to determine that the UE does not support the SRVCC-based eCSFB; and select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register.
The apparatus according to claim 35, wherein the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB, including:

If the registration request message includes indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes indication information that the UE does not support the SRVCC, or the SRVCC-supported eCSFB saved in the device The UE identifier does not include the identifier of the UE in the registration request message, and the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB.
A device according to claim 33 or 34, wherein

If the UE type identifier (classmark) information in the registration request message includes classmark 2 and classmark3, the processing module is further configured to determine that the UE supports the eCSFB of the SRVCC handover from the long term evolution communication system to the global mobile communication system. (LTE-> eCSFB of GSM SRVCC).
The device according to claim 32, wherein the processing module is configured to determine, according to the registration request message, that the UE supports an SRVCC-based eCSFB, including:

The registration request message includes an identifier of the UE, and the UE identifier of the eCSFB (eCSFB of the LTE->GSM SRVCC) that supports the SRVCC handover from the long-term evolution communication system to the global mobile communication system is included in the apparatus. The identifier of the UE, the processing module is configured to determine that the UE supports eCSFB (eCSFB of LTE->GSM SRVCC) of the SRVCC handover from the long term evolution communication system to the global mobile communication system.
A device according to any of claims 32-38, characterized in that

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message If the classmark 2 and the classmark 3 are not included in the classmark message, or the UE identifier of the eCSFB supporting the LTE->GSM SRVCC saved in the device does not include the identifier of the UE in the registration request message, The processing module is configured to determine that the UE does not support the eCSFB of the LTE->GSM SRVCC; and select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register.
A device according to claim 33 or 34, wherein

If the classmark information of the UE in the registration request message includes classmark 2, the processing module is configured to determine eCSFB (LTE-) that the UE supports SRVCC handover from the long term evolution communication system to the universal mobile communication system. > UMTS SRVCC eCSFB).
The apparatus according to claim 32, wherein said processing module is configured to cancel according to said registration request Determining that the UE supports SRVCC-based eCSFB, including:

The registration request message includes an identifier of the UE, and includes, in the UE identifier of an eCSFB (eCSFB of LTE->UMTS SRVCC) that supports the SRVCC handover from the long term evolution communication system to the universal mobile communication system. The identifier of the UE is used by the processing module to determine eCSFB (eCSFB of LTE->UMTS SRVCC) that the UE supports SRVCC handover from the long term evolution communication system to the universal mobile communication system.
A device according to any of claims 32-41, wherein

If the registration request message includes the indication information that the UE does not support the SRCSCC-based eCSFB, or the registration request message includes the indication information that the UE does not support the SRVCC, or the UE in the registration request message The classmark 2 does not include the classmark 2, or the identifier of the UE in the registration request message is not included in the identifier of the UE supporting the eCSFB of the LTE->UMTS SRVCC included in the processing module, and the processing module is For determining that the UE does not support the eCSFB of the LTE->UMTS SRVCC, the processing module is further configured to select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register.
Apparatus according to any of claims 37-42, wherein

If the codec type supported by the UE in the registration request message belongs to the GSM coding type and does not have the UMTS codec type, or the UE identifier of the saved eCSFB supporting the LTE->GSM SRVCC is included in the device. For the identifier of the UE, the identifier of the UE that supports the eCSFB of the LTE->UMTS SRVCC is not included in the identifier of the UE, and the processing module is configured to determine that the UE supports the eCSFB of the LTE->GSM SRVCC. , eCSFB based on LTE->UMTS SRVCC is not supported.
Apparatus according to any of claims 37-42, wherein

If the codec type supported by the UE in the registration request message has both a UMTS codec type and a GSM codec type, or

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the device includes the identifier of the UE. The processing module is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.
Apparatus according to any of claims 37-42, wherein

If the codec type supported by the UE in the registration request message belongs to the UMTS codec type, but does not have the GSM codec type, or if the user type identifier (classmark) information carried in the registration request message is included only Classmark 2, does not include classmark 3; or, the identifier of the UE that supports the eCSFB supporting LTE->UMTS SRVCC saved by the device includes the identifier of the UE, and the device saves eCSFB supporting LTE->GSM SRVCC The identifier of the UE is not included in the identifier of the UE, and the processing module is configured to determine that the UE supports the eCSFB of the LTE->UMTS SRVCC, It does not support eCSFB for LTE->GSM SRVCC.
The device according to any one of claims 32-45, wherein the processing module is configured to register, for the UE, a mobile switching center MSC that supports the SRCSCC-based eCSFB, including:

The processing module is configured to select a mobile switching center MSC supporting an SRVCC-based eCSFB;

The device further includes a sending module, where the sending module is configured to send a location update request message to the MSC, so that the MSC initiates a location update process, where the location update request message includes the identity identifier of the UE.
The apparatus according to any one of claims 32-46, wherein said mobile switching center MSC supporting SRVCC-based eCSFB refers to an MSC that supports both CSFB and SRVCC functions.
The apparatus according to any one of claims 32-47, wherein the registration request message is an Attach request message or a Tracking Area Update (TAU) request message.
The device according to any one of 32-48, wherein the registration request message includes a registration type cell, and the registration type cell is set to jointly attach or joint tracking area TA/location area LA update.
A joint registration device, comprising:

a receiving module, configured to receive identifier information of the UE;

a processing module, configured to determine, according to the identifier information of the UE, that the UE supports an enhanced circuit switched fallback eCSFB based on a single wireless voice call continuity SRVCC; the processing module is further configured to select, for the UE, support an SRCSCC-based eCSFB The mobile switching center MSC registers.
The apparatus according to claim 50, wherein the processing module is configured to determine, according to the identifier of the UE, that the UE supports an SRCSCC-based eCSFB, including:

If the identifier of the UE that supports the SRVCC-based eCSFB is included in the apparatus, the processing module is configured to determine that the UE supports the SRVCC-based eCSFB.
Device according to claim 50 or 51, characterized in that

The processing module is further configured to determine that the UE does not support the SRVCC-based eCSFB; and select, for the UE, the MSC that does not support the SRVCC-based eCSFB to register.
The device according to claim 52, wherein the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB, including:

If the identifier of the UE that supports the SRCSCC-based eCSFB is not included in the apparatus, the processing module is configured to determine that the UE does not support the SRCSCC-based eCSFB.
The device according to any one of claims 50-53, wherein the processing module is configured to determine, according to the identifier of the UE, that the UE supports an SRCSCC-based eCSFB, including:

The processing module is configured to determine, if the MME maintains an identifier of the UE that supports an eCSFB (eCSFB of an LTE->GSM SRVCC) that supports SRVCC handover from a long term evolution communication system to a global mobile communication system. The UE supports eCSFB (LTE-> GSM SRVCC eCSFB) for SRVCC handover from a long term evolution communication system to a global mobile communication system.
A device according to any of claims 50-54, wherein

If the identifier of the UE in the registration request message is not included in the UE identifier of the eCSFB that supports the LTE->GSM GSM SRCC, the processing module is configured to determine that the UE does not support LTE-> eCSFB of GSM SRVCC,

The processing module is configured to register, for the UE, an MSC that does not support the SRVCC-based eCSFB.
The device according to any one of claims 50-55, wherein the processing module is configured to determine, according to the identifier of the UE, that the UE supports an SRCSCC-based eCSFB, including:

If the device saves the saved UE ID that supports the eCSFB (e-FB of the LTE-> UMTS SRVCC) of the SRVCC handover from the long-term evolution communication system to the universal mobile communication system, the processing module is included. An eCSFB (eCSFB of LTE->UMTS SRVCC) for determining that the UE supports SRVCC handover from a long term evolution communication system to a universal mobile communication system.
A device according to any of claims 50-56, wherein

If the identifier of the UE of the eCSFB supporting the LTE->UMTS SRVCC is not included in the apparatus, the processing module is configured to determine that the UE does not support the eCSFB of the LTE->UMTS SRVCC, The UE selects an MSC that does not support the SRVCC-based eCSFB for registration.
A device according to any of claims 53-57, wherein

If the UE identifier of the eCSFB supporting the LTE->GSM GSM SRVCC is included in the device, the identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC is not included in the identifier of the UE. And the processing module is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and does not support eCSFB based on LTE->UMTS SRVCC.
A device according to any of claims 53-57, wherein

The UE identifier of the eCSFB supporting the LTE->GSM SRVCC that is saved by the device includes the identifier of the UE, and the identifier of the UE of the eCSFB that supports the LTE->UMTS SRVCC that is saved by the device includes the identifier of the UE. The processing module is configured to determine that the UE supports eCSFB of LTE->GSM SRVCC, and supports eCSFB based on LTE->UMTS SRVCC.
A device according to any of claims 53-57, wherein

The identifier of the UE that supports the eCSFB supporting the LTE->UMTS SRVCC is included in the identifier of the UE, and the identifier of the UE that supports the eCSFB supporting the LTE->GSM SRVCC is not included in the identifier of the UE. And the processing module is configured to determine that the UE supports the eCSFB of the LTE->UMTS SRVCC, and does not support the eCSFB of the LTE->GSM SRVCC.
The apparatus according to any one of claims 50-60, wherein said mobile switching center MSC supporting SRVCC-based eCSFB refers to an MSC that supports both CSFB and SRVCC functions.
The apparatus according to any one of claims 50-61, wherein the identification information of the UE is an IMSI or an IMEI of the UE.