CN107113864B

CN107113864B - Combined registration method and device

Info

Publication number: CN107113864B
Application number: CN201480084417.9A
Authority: CN
Inventors: 吴晓波; 崇卫微
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2014-12-30
Filing date: 2014-12-30
Publication date: 2020-02-14
Anticipated expiration: 2034-12-30
Also published as: WO2016106559A1; CN107113864A

Abstract

The embodiment of the invention provides a method and a device for combined registration, wherein an MME judges whether UE supports eCSFB based on SRVCC or not, if so, the MME selects MSC supporting the eCSFB based on SRVCC for the UE to perform registration, and if not, the MME selects MSC not supporting the eCSFB based on SRVCC for the UE to perform registration. The MSC selects a proper MSC for the UE to register, so that the UE supporting the eCSFB based on the SRVCC can trigger the eCSFB flow based on the SRVCC in the subsequent voice service initiating process, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; the difference between the MSC which does not support the registration of the UE of the eCSFB based on the SRVCC and the MSC which actually processes the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are avoided.

Description

Combined registration method and device

Technical Field

The embodiment of the invention relates to the field of communication, in particular to a joint registration method and device.

Background

Second Generation (2G) or Third Generation (3G) networks, such as Global System for Mobile communications (GSM) or Wideband Code Division Multiple Access (WCDMA), have achieved substantially full coverage. With the development of Long Term Evolution (LTE) network technology, these LTE networks have covered some urban areas and traffic hot spots, so that in the current communication network, the LTE network coexists with a 2G or 3G network.

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

The premise that a user can fall back to the 2G/3G network through the CSFB procedure and perform a voice service is that the UE must complete a joint registration procedure, and register on a Mobility Management Entity (MME) of the LTE network and a Mobile Switching Center (MSC) of the CS domain of the 2G/3G network. In the process of joint registration, the UE initiates a registration request to the MME, and the MME needs to select an MSC for the UE to register. After the UE is jointly registered, the UE resides on the LTE network side, and after the UE initiates a voice service and initiates an extended service request to LTE network side equipment, the network side equipment triggers a CSFB flow. The current CSFB procedure can use a Single Radio Voice Call Continuity (SRVCC) procedure, that is, the SRVCC is used to switch the UE from the LTE network to the GERAN/UTRAN network, so as to implement the UE fallback. The above procedure for implementing CSFB by SRVCC is simply referred to as SRVCC-based eCSFB (Enhanced CSFB). In the SRVCC eCSFB based procedure, an MSC serving a UE must support both SRVCC and CSFB, which we refer to as an MSC supporting SRVCC eCSFB (abbreviated as eCSFB MSC). However, in general, in order to accelerate the business time of the eCSFB and save the deployment cost for the operator (e.g. china mobile), only a few MSCs are upgraded on the basis of the original CSFB distribution network to support the eCSFB as a proxy (proxy) MSC, and not all MSCs are upgraded.

In the prior art, when a UE initiates a joint registration procedure, an MME may uniformly allocate UEs that support or do not support SRVCCeCSFB to a few eCSFB MSCs (proxy MSCs) for registration or to a common MSC for registration, or randomly allocate UEs to two MSCs.

If a common UE (i.e., a UE that does not support SRVCC eCSFB) is allocated to an eCSFB MSC (proxy MSC) for registration, after the call of the common UE initiates a voice service request, it is impossible to trigger the SRVCC eCSFB-based procedure, and actually only the common CSFB procedure can be triggered to be processed by the common MSC continuously, but since the common MSC does not have the context of the UE, the LAU procedure must be triggered to obtain the context from the registered eCSFB MSC in the CSFB procedure, which may additionally increase the delay of call setup. In a called scene, if a common UE is paged to trigger a called CSFB process, a registered eCSFB MSC (proxy MSC) issues a paging message. The connected MSC after the UE fallback is a normal MSC rather than a registered MSC thereof, and since a called roaming retry (MTRR) or a called roaming forwarding (MTRF) function may not be deployed in the current network, an abnormal scenario may occur and cause a called failure, that is, the UE is not reachable.

Therefore, how to select a suitable MSC for the UE to register by the MME in the UE joint registration process is a problem that needs to be solved at present.

Disclosure of Invention

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

In a first aspect, a method for joint registration is provided, in which a mobility management entity MME receives a registration request message of a UE; the MME determines that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the registration request message; and the MME selects a mobile switching center MSC supporting the eCSFB based on the SRVCC for the UE to register.

With reference to the first aspect, in a first possible implementation manner, the determining, by the MME, that the UE supports an eCSFB based on SRVCC according to the registration request message includes: if the registration request message comprises indication information that the UE supports the eCSFB based on the SRVCC, the MME determines that the UE supports the eCSFB based on the SRVCC; or, the registration request message includes the identifier of the UE, and if the identifier of the UE supporting the eCSFB based on SRVCC stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB based on SRVCC.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, if the registration request message further includes indication information that the UE supports SRVCC, the MME determines that the UE supports an eCSFB based on SRVCC.

With reference to the first aspect, the first or second possible implementation manner of the first aspect, in a third possible implementation manner, the MME determines that the UE does not support an eCSFB based on SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the determining, by the MME, that the UE does not support an eCSFB based on SRVCC includes: if the registration request message contains the indication information that the UE does not support the eCSFB based on the SRVCC, or the registration request message contains the indication information that the UE does not support the SRVCC, or the UE identifier which is stored in the MME and supports the eCSFB based on the SRVCC does not include the UE identifier in the registration request message, the MME determines that the UE does not support the eCSFB based on the SRVCC.

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

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

With reference to the first aspect and any one of the first to sixth possible implementation manners of the first aspect, in a seventh possible implementation manner, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not simultaneously include classmark2 and classmark3, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the MME does not include the identity of the UE in the registration request message, it is determined that the UE does not support an eCSFB of LTE- > GSM SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

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

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

With reference to the first aspect and any one of the first to eighth possible implementation manners of the first aspect, in a tenth possible implementation manner, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not include classmark2, or an identifier of the UE that supports an eCSFB of LTE- > UMTS SRVCC, which is included 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 an eCSFB of LTE- > UMTS SRVCC, and the MME selects, for the UE, an eCSFB that does not support an eCSFB based on SRVCC to register.

With reference to any one of the fifth to tenth possible implementation manners of the first aspect, in an eleventh possible implementation manner, if the codec type supported by the UE in the registration request message belongs to a GSM codec type and does not have a UMTS codec type, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME does not include the UE identity, the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC.

With reference to any one of the fifth to tenth possible implementation manners of the first aspect, in a twelfth possible implementation manner, if the codec type supported by the UE in the registration request message is both a UMTS codec type and a GSM codec type, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME includes the UE identity, the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the eCSFB based on LTE- > UMTS SRVCC.

With reference to any one of the fifth to tenth possible implementation manners of the first aspect, in a thirteenth possible implementation manner, if the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if user type identifier (classmark) information carried in the registration request message only includes classmark2 and does not include classmark 3; or the identity of the UE supporting the eCSFB of LTE- > UMTS SRVCC stored by the MME includes the identity of the UE, and the identity of the UE supporting the eCSFB of LTE- > GSM SRVCC stored by the MME does not include the identity of the UE, then the MME determines that the UE supports the eCSFB of LTE- > UMTS SRVCC but does not support the eCSFB of LTE- > GSM SRVCC.

With reference to the first aspect and any one of the first to the thirteenth possible implementation manners of the first aspect, in a fourteenth possible implementation manner, the selecting, by the MME, a mobile switching center MSC that supports an eCSFB based on SRVCC for the UE to register includes: the MME selects a mobile switching center MSC supporting eCSFB based on SRVCC; and the MME sends a location updating request message to the MSC so as to enable the MSC to initiate a location updating process, wherein the location updating request message comprises the identity of the UE.

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

With reference to the first aspect and any one of the first to fifteenth possible implementation manners of the first aspect, in a sixteenth possible implementation manner, the registration request message is an Attach request message or a Tracking Area Update (TAU) request message.

With reference to the first aspect and any one of the first to the sixteenth possible implementation manners of the first aspect, in a seventeenth possible implementation manner, the registration request message includes a registration type information element, and the registration type information element is set to be a joint attachment or a 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 receives identification information of UE; the MME determines that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the identification information of the UE; and the MME selects a mobile switching center MSC supporting the eCSFB based on the SRVCC for the UE to register.

With reference to the second aspect, in a first possible implementation manner, the determining, by the MME, that the UE supports an eCSFB based on SRVCC according to the identity of the UE includes: and if the identification of the UE supporting the eCSFB based on the SRVCC stored by the MME comprises the identification of the UE, the MME determines that the UE supports the eCSFB based on the SRVCC.

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 eCSFB based on SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

With reference to the second possible implementation manner of the second aspect, in a third possible implementation manner, the determining, by the MME, that the UE does not support an eCSFB based on SRVCC includes: and if the UE identification which is stored in the MME and supports the eCSFB based on the SRVCC does not comprise the identification of the UE, the MME determines that the UE does not support the eCSFB based on the SRVCC.

With reference to the second aspect and any one of the first to third possible implementation manners of the second aspect, in a fourth possible implementation manner, the determining, by the MME, that the UE supports an eCSFB based on SRVCC according to the identity of the UE includes: if the UE identity of the eCSFB (eCSFB for LTE-SRVCC) which supports SRVCC handover from a long term evolution communication system to a global system for mobile communication stored by the MME includes the UE identity, the MME determines that the UE supports the eCSFB for SRVCC handover from the long term evolution communication system to the global system for mobile communication (eCSFB for LTE-SRVCC).

With reference to the second aspect and any one of the first to fourth possible implementation manners of the second aspect, in a fifth possible implementation manner, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the MME does not include the UE identity in the registration request message, the MME determines that the UE does not support the eCSFB supporting LTE- > GSM SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

With reference to the second aspect and any one of the first to fifth possible implementation manners of the second aspect, in a sixth possible implementation manner, the determining, by the MME, that the UE supports an eCSFB based on SRVCC according to the identity of the UE includes: if the UE identity of the eCSFB (eCSFB of LTE-UMTS SRVCC) which supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system stored by the MME comprises the UE identity, the MME determines that the UE supports the eCSFB (eCSFB of LTE-UMTS SRVCC) which supports SRVCC handover from the long term evolution communication system to the universal mobile telecommunications system.

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

With reference to any one of the third to seventh possible implementation manners of the second aspect, in an eighth possible implementation manner, the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME does not include the UE identity, so that the MME determines that the UE supports eCSFB supporting LTE- > GSM SRVCC and does not support eCSFB based on LTE- > UMTS SRVCC.

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

With reference to any one of the third to seventh possible implementation manners of the second aspect, in a tenth possible implementation manner, if the UE identifier of the UE that supports the eCSFB of LTE- > UMTS SRVCC stored in the MME includes the UE identifier, and the UE identifier of the eCSFB that supports LTE- > GSM SRVCC stored in the MME does not include the UE identifier, the MME determines that the UE supports the eCSFB of LTE- > UMTS SRVCC but does not support the eCSFB of LTE- > GSM SRVCC.

With reference to the second aspect and the first to tenth possible implementation manners of the second aspect, in an eleventh possible implementation manner, the mobile switching center MSC supporting an eCSFB based on SRVCC refers to an MSC supporting both a CSFB function and an SRVCC function.

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

In a third aspect, a joint registration apparatus is provided, including: a receiving module, configured to receive a registration request message of a 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 the mobile switching center MSC is also used for selecting the mobile switching center MSC supporting the eCSFB based on the SRVCC for registering the UE.

With reference to the third aspect, in a first possible implementation manner, the determining, by the processing module, that the UE supports an eCSFB based on SRVCC according to the registration request message includes: if the registration request message includes indication information that the UE supports the eCSFB based on the SRVCC, the processing module is configured to determine that the UE supports the eCSFB based on the SRVCC; or, the registration request message includes an identifier of the UE, and if the identifier of the UE supporting the eCSFB based on SRVCC stored in the apparatus includes the identifier of the UE, the processing module is configured to determine that the UE supports the eCSFB based on SRVCC.

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 indication information that the UE supports SRVCC, the processing module is further configured to determine that the UE supports an eCSFB based on SRVCC.

With reference to the third aspect, the first or second possible implementation manner of the third aspect, in a third possible implementation manner, the processing module is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

With reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, the determining that the UE does not support an eCSFB based on SRVCC by the processing module 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 indication information that the UE does not support the SRVCC, or the UE identifier that supports the SRVCC-based eCSFB stored in the device does not include the UE identifier in the registration request message, the processing module is configured to determine that the UE does not support the SRVCC-based eCSFB.

With reference to the first or second possible implementation manner of the third aspect, in a fifth possible implementation manner, if the UE type identifier (classmark) information in the registration request message includes classmark2 and classmark3, 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 system for mobile communications.

With reference to the third aspect, in a sixth possible implementation manner, the determining, by the processing module, that the UE supports an eCSFB based on SRVCC according to the registration request message includes: the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) supporting SRVCC handover from the long term evolution communication system to the global system for mobile communications stored in the device includes the identifier of the UE, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) supporting SRVCC handover from the long term evolution communication system to the global system for mobile communications.

With reference to the third aspect and any one of the first to sixth possible implementation manners of the third aspect, in a seventh possible implementation manner, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not simultaneously include classmark2 and classmark3, or the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus does not include the UE identifier in the registration request message, the processing module is configured to determine that the UE does not support an eCSFB of LTE- > GSM SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

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

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

With reference to the third aspect and any one of the first to ninth possible implementation manners of the third aspect, in a tenth possible implementation manner, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not include classmark2, or an identifier of the UE that supports an eCSFB of LTE- > UMTS SRVCC, which is included in the processing module, 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 an eCSFB of LTE- > UMTS SRVCC, and the processing module is further configured to select an MSC that does not support an eCSFB based on SRVCC for registration.

With reference to any one of the fifth to tenth possible implementation manners of the third aspect, in an eleventh possible implementation manner, if the codec type supported by the UE in the registration request message belongs to a GSM codec type and does not have a UMTS codec type, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus does not include the UE identity, the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC.

With reference to any one of the fifth to tenth possible implementation manners of the third aspect, in a twelfth possible implementation manner, if the codec type supported by the UE in the registration request message is both a UMTS codec type and a GSM codec type, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identity, the processing module is configured to determine that the UE supports sfb of LTE- > GSM SRVCC and supports eCSFB based on LTE- > UMTS SRVCC.

With reference to any one of the fifth to tenth possible implementation manners of the third aspect, in a thirteenth possible implementation manner, if the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if user type identifier (classmark) information carried in the registration request message only includes classmark2 and does not include classmark 3; or the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus does not include the UE identifier, the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > UMTS SRVCC but does not support the eCSFB supporting LTE- > GSM SRVCC.

With reference to the third aspect and any one of the first to the thirteenth possible implementation manners of the third aspect, in a fourteenth possible implementation manner, the selecting, by the processing module, a mobile switching center MSC that supports an eCSFB based on SRVCC for the UE to register includes: the processing module is used for selecting a mobile switching center MSC supporting eCSFB based on SRVCC; the device further comprises a sending module, wherein the sending module is configured to send a location update request message to the MSC, so that the MSC initiates a location update procedure, and the location update request message includes the identity of the UE.

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

With reference to the third aspect and any one of the first to fifteenth possible implementation manners of the third aspect, in a sixteenth possible implementation manner, the registration request message is an Attach request message or a Tracking Area Update (TAU) request message.

With reference to the third aspect and any one of the first to sixteenth possible implementation manners of the third aspect, in a seventeenth possible implementation manner, the registration request message includes a registration type information element, and the registration type information element is set to be a joint attachment or joint tracking area TA/location area LA update.

In a fourth aspect, a joint registration apparatus is provided, including: a receiving module, configured to receive identification information of a UE; the processing module is used for determining that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the identification information of the UE; the processing module is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the determining, by the processing module, that the UE supports an eCSFB based on SRVCC according to the identity of the UE includes: if the UE identifier for supporting the SRVCC-based eCSFB stored in the apparatus includes the UE identifier, the processing module is configured to determine that the UE supports the SRVCC-based eCSFB.

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the processing module is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

With reference to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, the determining that the UE does not support an eCSFB based on SRVCC by the processing module includes: if the UE identifier that supports the SRVCC-based eCSFB stored in the apparatus does not include the UE identifier, the processing module is configured to determine that the UE does not support the SRVCC-based eCSFB.

With reference to the fourth aspect and any one of the first to third possible implementation manners of the fourth aspect, in a fourth possible implementation manner, the determining, by the processing module, that the UE supports an eCSFB based on SRVCC according to the identity of the UE includes: if the UE identity of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM includes the UE identity, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM.

With reference to the fourth aspect and any one of the first to fourth possible implementation manners of the fourth aspect, in a fifth possible implementation manner, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus does not include the UE identity in the registration request message, the processing module is configured to determine that the UE does not support the eCSFB supporting LTE- > GSM SRVCC, and the processing module is configured to select an MSC that does not support the eCSFB based on SRVCC for the UE to register.

With reference to the fourth aspect and any one of the first to fifth possible implementation manners of the fourth aspect, in a sixth possible implementation manner, the determining, by the processing module, that the UE supports an eCSFB based on SRVCC according to the identity of the UE includes: if the UE identity of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system stored in the apparatus includes the UE identity, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

With reference to the fourth aspect and any one of the first to sixth possible implementation manners of the fourth aspect, in a seventh possible implementation manner, if the identity of the UE that supports the eCSFB of LTE- > UMTS SRVCC included in the apparatus does not include the identity of the UE, the processing module is configured to determine that the UE does not support the eCSFB of LTE- > UMTS SRVCC, and select an MSC that does not support the eCSFB based on SRVCC for the UE to register.

With reference to any one of the third to seventh possible implementation manners of the fourth aspect, in an eighth possible implementation manner, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus does not include the UE identity, the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based LTE- > UMTS SRVCC.

With reference to any one of the third to seventh possible implementation manners of the fourth aspect, in a ninth possible implementation manner, the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identity, then the processing module is configured to determine that the UE supports eCSFB supporting LTE- > GSM SRVCC, and supports eCSFB based on LTE- > UMTS SRVCC.

With reference to any one of the third to seventh possible implementation manners of the fourth aspect, in a tenth possible implementation manner, the identifier of the UE that supports eCSFB of LTE- > UMTS SRVCC stored by the apparatus includes the identifier of the UE, and the identifier of the UE that supports eCSFB of LTE- > GSM SRVCC stored by the apparatus does not include the identifier of the UE, then the processing module is configured to determine that the UE supports eCSFB of LTE- > UMTS SRVCC but does not support eCSFB of LTE- > GSM SRVCC.

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

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

Based on the technical scheme provided by the embodiment of the invention, whether the UE supports the eCSFB based on the SRVCC is judged by the MME, if so, the MME selects the MSC supporting the eCSFB based on the SRVCC for the UE to register, and if not, the MME selects the MSC not supporting the eCSFB based on the SRVCC for the UE to register. The MSC selects a proper MSC for the UE to register, so that the UE supporting the eCSFB based on the SRVCC can trigger the eCSFB flow based on the SRVCC in the subsequent voice service initiating process, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; the difference between the MSC which does not support the registration of the UE of the eCSFB based on the SRVCC and the MSC which actually processes the voice service is avoided, and the problems of increased call setup delay and unreachable called party are further avoided.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments of the present invention or in the description of the prior art will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

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

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

Fig. 3 shows a schematic flowchart of a joint registration method according to an embodiment of the present invention.

Fig. 4 shows a schematic flowchart of a joint registration method according to an embodiment of the present invention.

Fig. 5 is a schematic block diagram illustrating a device for joint registration according to an embodiment of the present invention.

Fig. 6 is a schematic block diagram illustrating a device for joint registration according to an embodiment of the present invention.

Fig. 7 is a schematic block diagram of a device for joint registration according to an embodiment of the present invention.

Fig. 8 is a schematic block diagram of a device for joint registration according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, shall fall within the scope of protection of the present invention.

Fig. 1 shows a schematic diagram of a network architecture on which an embodiment of the present invention is based. 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, and the embodiment of the present invention is not limited thereto.

As shown in fig. 1, in a network architecture composed of UE, eNodeB (Evolved Node B), MME, MSC, BSC/RNC, and HSS/HLR, the UE may initiate a registration request to an LTE network side device, where the registration request indicates that the registration type is joint registration. And the registration request message indicates whether the UE itself supports SRVCC eCSFB; the eNodeB may transmit a registration request message for the UE to the MME; the MME can receive a combined registration request message sent by the UE, determine whether the UE supports SRVCCeCSFB and specifically supports which type of SRVCC eCSFB, select a proper MSC for the determined UE to register, send a location update request message to the MSC to trigger a location update process, thereby completing the CS domain registration process of the UE; the MSC related to the invention may be an MSC only supporting common CSFB, or an MSC supporting SRVCC eCSSFB (i.e. supporting SRVCC and CSFB simultaneously), wherein the former has only an SGS port with the MME, and the latter has both an SGS port and an SV port with the MME.

The network architecture and devices therein of the present invention may be applied to other embodiments of the present invention, which are not described herein again.

Fig. 2 shows 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 fig. 2, the method includes:

s201, a mobility management entity MME receives a registration request message of UE;

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

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

specifically, the determining, by the MME, that the UE supports an eCSFB based on SRVCC includes: if the registration request message includes indication information that the UE supports the eCSFB based on the SRVCC, the MME determines that the UE supports the eCSFB based on the SRVCC.

Or, the MME determining that the UE supports an eCSFB based on SRVCC includes: if the registration request message includes indication information that the UE supports the eCSFB based on the SRVCC, and the registration request message further includes indication information that the UE supports the SRVCC, the MME determines that the UE supports the eCSFB based on the SRVCC.

Or, the registration request message includes the identifier of the UE, and if the identifier of the UE supporting the eCSFB based on SRVCC stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB based on SRVCC. Specifically, the determining, by the MME, that the UE supports an eCSFB based on SRVCC includes: the MME maintains an eCSFB user form (white list/mapping table), where identification information (identity) supporting an SRVCC-based eCSFB user is recorded in the white list/mapping table, and the identity information may specifically be IMSI, IMEI, and the like. And if the registration request message sent by the UE carries the identity information of the UE and is contained in the white list/mapping table, the MME determines that the UE supports eCSFB based on SRVCC. Optionally, in another embodiment of the present invention, the identification information of the UE may be that the UE sends the registration request message to the MME, or that the UE sends the identification information of the UE to the MME, and the MME actively acquires the identification information of the UE. The MME may maintain the white list/mapping table periodically or aperiodically, e.g., the MME may periodically update the table, add new user identity information supporting SRVCC eCSFB to the table, delete aged user identity information, and the like.

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

Or, in one embodiment of the present invention, the determining, by the MME according to the registration request message, that the UE supports an eCSFB based on SRVCC includes: the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications and that is stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications. That is, if the identity of the UE carried in the registration request message belongs to the UE white list of the eCSFB (eCSFB of LTE- > GSM SRVCC) that is stored by the MME and supports SRVCC handover from the LTE to the GSM, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM. In particular, reference may be made to the above-described embodiment related steps.

Or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the identity of the UE, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME does not include the identity of the UE, so that the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC. That is, the identity of the UE carried in the registration request message belongs to the UE white list of the eCSFB (eCSFB of LTE- > GSM SRVCC) that is stored by the MME and supports SRVCC handover from a long term evolution communication system to a global system for mobile communications, and does not belong to the UE white list of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that is stored by the MME and supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system, then the MME determines that the UE supports the eCSFB of LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC. Or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the identity of the UE, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME includes the identity of the UE, then the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the eCSFB based on LTE- > UMTS SRVCC. That is, the identity of the UE carried in the registration request message belongs to the UE white list of the stored eCSFB (eCSFB of LTE- > GSM SRVCC) of the MME that supports SRVCC handover from the LTE to the GSM, and also belongs to the UE white list of the stored eCSFB (eCSFB of LTE- > UMTS SRVCC) of the MME that supports SRVCC handover from the LTE to the UMTS, then the MME determines that the UE supports the eCSFB of LTE- > GSM SRVCC and supports the sfb based on LTE- > UMTS SRVCC.

Or, if the classmark information of the UE in the registration request message includes classmark2, the MME determines that the UE supports an eCSFB (eCSFB of LTE- > UMTS SRVCC) for SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system. If the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if the user type identifier (classmark) information carried in the registration request message only contains classmark2 and does not contain classmark 3; the MME determines that the UE supports eCSFB with LTE- > UMTS SRVCC and does not support eCSFB with LTE- > GSM SRVCC.

Or the identity of the UE supporting the eCSFB of LTE- > UMTS SRVCC stored by the MME includes the identity of the UE, and the identity of the UE supporting the eCSFB of LTE- > GSM SRVCC stored by the MME does not include the identity of the UE, then the MME determines that the UE supports the eCSFB of LTE- > UMTS SRVCC but does not support the eCSFB of LTE- > GSM SRVCC. That is, the identity of the UE carried in the registration request message belongs to the UE white list of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that is stored by the MME and supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system, and does not belong to the UE white list of the eCSFB (eCSFB of LTE- > GSM SRVCC) that is stored by the MME and supports SRVCC handover from a long term evolution communication system to a global system for mobile communications.

S203, the MME selects a mobile switching center MSC supporting the eCSFB based on the SRVCC for the UE to register.

Specifically, the MME selects (according to an internal mapping relationship or internal configuration) one mobile switching center MSC that supports an eCSFB based on SRVCC; and the MME sends a location updating request message to the MSC so as to enable the MSC to initiate a location updating process, wherein the location updating request message comprises the identity of the UE. The mobile switching center MSC supporting the eCSFB based on SRVCC refers to an MSC supporting both CSFB and SRVCC capabilities.

Optionally, the method further comprises: the MME determines that the UE does not support eCSFB based on SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register. The MME determines that the UE does not support eCSFB based on SRVCC, including: if the registration request message includes indication information that the UE does not support the SRVCC-based eCSFB, or the registration request message includes indication information that the UE does not support the SRVCC, or the UE identifier that supports the SRVCC-based eCSFB stored in the MME does not include the UE identifier in the registration request message, that is, the UE identifier carried in the registration request message is not included in the white list/mapping table stored in the MME, the MME determines that the UE does not support the SRVCC-based eCSFB.

Further, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the MME does not include the UE identity in the registration request message, that is, the identity of the UE carried in the registration request message is not included in the white list/mapping table stored in the MME, or the classmark message of the UE in the registration request message does not include both classmark2 and classmark3, the MME determines that the UE does not support an eCSFB supporting LTE- > GSM SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

Further, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or an identifier of the UE that supports an eCSFB based on LTE- > UMTS SRVCC included 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 is not included in the white list/mapping table stored by the MME, or a classmark2 is not included in the classmark message of the UE in the registration request message, the MME determines that the UE does not support an eCSFB based on LTE- > UMTS SRVCC, and the MME selects an MSC that does not support an eCSFB based on SRVCC for the UE to register.

Therefore, according to the registration method provided by the embodiment of the present invention, in the process of performing a combined registration on the UE, the MME determines whether the UE supports an eCSFB based on SRVCC, if so, the MME selects an MSC supporting the eCSFB based on SRVCC for the UE to perform registration, and if not, the MME selects an MSC not supporting the eCSFB based on SRVCC for the UE to perform registration. The MSC selects a proper MSC for the UE to register, so that the UE supporting the eCSFB based on the SRVCC can trigger the eCSFB flow based on the SRVCC in the subsequent voice service initiating process, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; the difference between the MSC which does not support the registration of the UE of the eCSFB based on the SRVCC and the MSC which actually processes the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are avoided.

Other embodiments of the present invention and the embodiment of the present invention shown in fig. 2 may be referred to each other, and the comparison of the present invention is not repeated.

Fig. 3 is a schematic flowchart of a joint registration method according to an embodiment of the present invention, which is a specific embodiment of the embodiment shown in fig. 2.

As shown in fig. 3, the method includes:

s301, UE sends a registration request message to MME;

when a UE supporting CSFB is started up and accesses a certain LTE network due to startup network selection, roaming or network reselection and the like, a combined registration process is initiated. The UE sends a registration request message to the MME, wherein the registration request message comprises a registration type cell, and the registration type is specifically set as joint registration or joint tracking area TA/location area LA update and is used for informing the MME that the UE requires joint registration in a Packet Core Evolution (EPS) domain of a 4G network and a CS domain of a 2G/3G network. The registration request message includes indication information that the UE supports an eCSFB based on SRVCC, and the registration request message may further include indication information that the UE supports SRVCC.

The registration request message includes an identifier of the UE, where the identifier of the UE may be an IMSI or an IMEI 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 for informing MME of the network capability of the UE, and the network capability related to the invention is the capability of whether the UE supports SRVCC, namely the indication information that the UE supports SRVCC; and a capability of whether the UE supports the SRVCC-based eCSFB, that is, the indication information that the UE supports the SRVCC-based eCSFB, which is not limited in the present invention.

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

S302, after the MME receives the registration request message sent by the UE, the registration process of the UE in the EPS domain is carried out.

S303, after the MME receives the registration request message sent by the UE, judging whether the UE supports eCSFB based on SRVCC.

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

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

if the UE meets the conditions, the MME can determine that the UE supports eCSFB based on SRVCC.

Optionally, in addition to the condition 1, the MME may further need to determine whether the UE satisfies the following condition:

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

if the UE simultaneously satisfies the two conditions 1 and 2, the MME may determine that the UE supports an eCSFB based on SRVCC.

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

3. the registration request message comprises the identification of the UE, and if the identification of the UE supporting the eCSFB based on the SRVCC stored by the MME comprises the identification of the UE, the MME determines that the UE supports the eCSFB based on the SRVCC.

Specifically, the identity of the UE carried in the registration request message sent by the UE is included in a white list/mapping table stored by the MME, where the white list/mapping table records identity information supporting SRVCC-based eCSFB users, and the identity information may specifically be IMSI, IMEI, and the like;

if the UE satisfies the condition 3, the MME may determine that the UE supports an eCSFB based on SRVCC.

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

And if the UE supports the eCSFB based on the SRVCC, the MME selects an MSC supporting the eCSFB based on the SRVCC for the UE to register.

Specifically, the MME selects an MSC supporting an eCSFB based on SRVCC through an internally configured mapping relationship (the mapping relationship may be used to indicate a mapping relationship between a Tracking Area (TA) of an LTE network where the UE is located and a Location Area (LA) of a GSM/UMTS network, and a mapping relationship between the TA, the LA and the eCSFBMSC and the common CSFB MSC, as shown in the following schematic diagram), and sends a location update request message to the MSC, so that the MSC initiates a location update procedure, where the location update request message includes an identifier of the UE, and is used to notify the MSC of starting a CS domain attach/location area update procedure for the UE.

The MSC and MME supporting SRVCC eCSFB may have both SGs and Sv interfaces, which may support both CSFB and SRVCC functions.

If the UE is determined not to support the eCSFB based on the SRVCC, the MME selects an MSC (common MSC) which does not support the eCSFB based on the SRVCC for the UE to register.

There may be no SV port but only an SGS port between the MSC and the MME which do not support the eCSFB based on SRVCC, that is, only the CSFB function is supported but the SRVCC function is not supported.

Specifically, the MME selects an MSC that does not support an eCSFB based on SRVCC through an internally configured mapping relationship (see the relevant description in S304), and sends a location update request message to the MSC, where the location update request message includes an identifier of the UE, and is used to notify the MSC of starting a CS domain attach/location area update procedure for the UE.

S305, the MSC executes a CS domain attach/location area update procedure of the UE.

S306, the MSC sends a location update acceptance message to the MME.

S307, the MME completes the EPS registration process.

Therefore, according to the method provided by the embodiment of the present invention, in the process of performing the joint registration on the UE, the MME determines whether the UE supports the eCSFB based on SRVCC, if so, the MME selects the MSC supporting the eCSFB based on SRVCC for the UE to perform registration, and if not, the MME selects the MSC not supporting the eCSFB based on SRVCC for the UE to perform registration. The MSC selects a proper MSC for the UE to register, so that the UE supporting the eCSFB based on the SRVCC can trigger the eCSFB flow based on the SRVCC in the subsequent voice service initiating process, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; the difference between the MSC which does not support the registration of the UE of the eCSFB based on the SRVCC and the MSC which actually processes the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are avoided.

Currently, some operators only deploy eCSFB (eCSFB of LTE- > GSM SRVCC) based SRVCC handover from LTE to GSM (Global System for Mobile communications), and not deploy eCSFB (eCSFB of LTE- > UMTS SRVCC) based SRVCC handover from LTE to UMTS (Universal Mobile telecommunications System).

For example, a GSM network of china mobile is superior to a UMTS network, and china mobile only deploys a CSFB function of UE falling back from an LTE network to the GSM network, that is, china mobile only supports eCSFB of LTE- > GSM SRVCC and does not support eCSFB of LTE- > UMTS SRVCC. After a UE that only supports the eCSFB based on LTE- > UMTS SRVCC accesses the LTE-mobile-LTE network and initiates a voice service, the network side cannot initiate the eCSFB process based on LTE- > UMTS SRVCC, cannot initiate the eCSFB process based on LTE- > GSM SRVCC due to the capability of the UE, and can only initiate a normal CSFB process, so the SRVCC-based eCSFB capability of the UE in this scenario has no practical significance. If the MME selects and registers the UE on the MSC supporting SRVCC eCSFB based on the network capability of the UE, the UE may only execute the normal CSFB procedure after initiating the voice service, and then the UE may fall back to a normal MSC and execute the voice service, which may cause the MSC registered by the UE to be different from a serving MSC actually executing the voice service by the UE, thereby causing a problem of extension during calling and unreachable called party.

Therefore, in another embodiment of the present invention, after the MME has determined that the UE supports the SRVCC-based eCSFB capability, it is also necessary to further determine whether the UE also supports the eCSFB based on LTE- > GSM SRVCC. And if so, selecting an MSC supporting the eCSFB based on the SRVCC for the UE to register. And if not, selecting an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

In particular, reference is made to the embodiment of the invention shown in fig. 3.

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

4. the user type identifier (classmark) information carried in the registration request message sent by the UE includes classmark2 and classmark3 at the same time.

The classmark2 is used to indicate that the UE supports SRVCC handover (the MSsupports SRVCC to GERAN or UTRAN) to GERAN or UTRAN.

The classmark3 is used for indicating that the UE supports SRVCC handover to GERAN.

In cooperation with condition 1, or 1 and 2 in S303, if the UE also satisfies 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 condition:

5. the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications and that is stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications.

That is, if the identity of the UE carried in the registration request message belongs to the UE white list of the eCSFB (eCSFB of LTE- > GSM SRVCC) that is stored by the MME and supports SRVCC handover from the LTE to the GSM, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM.

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

If the MME determines that the UE supports the eCSFB of LTE- > GSM SRVCC, the MME selects an MSC supporting the eCSFB based on SRVCC for the UE to register. If the MME determines that the UE does not support eCSFB of LTE- > GSM SRVCC, the MME selects an MSC which does not support eCSFB based on SRVCC for the UE to register. Refer to the relevant step in S304.

Other steps in the embodiment of the present invention may refer to related steps in the embodiment shown in fig. 3, and the embodiment of the present invention is a specific embodiment of the present invention shown in fig. 2, and the present invention is not described herein again.

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 LTE- > GSM SRVCC, in addition to determining whether the UE supports the eCSFB based on SRVCC. If so, the MME selects an MSC supporting the eCSFB based on the SRVCC for the UE to register, otherwise, the MME selects an MSC not supporting the eCSFB based on the SRVCC for the UE to register. According to the method for differentially registering the UE, under the condition that a network side can only trigger the eCSFB based on LTE- > UMTS SRVCC, on one hand, the method is beneficial to supporting the eCSFB flow based on LTE- > GSM SRVCC in the process that the UE of the eCSFB can subsequently initiate the voice service, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; on the other hand, the difference between the MSC registered by the UE which does not support the eCSFB based on LTE- > GSM SRVCC and the MSC actually processing the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are further avoided.

After determining that the UE supports the eCSFB based on LTE- > GSM SRVCC, the MME can further judge whether the UE only supports the eCSFB based on LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC; or the MME judges whether the UE simultaneously supports the eCSFB of the LTE- > GSM SRVCC and the eCSFB based on the LTE- > UMTS SRVCC.

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

5. the coding and decoding types supported by the UE carried in the registration request message sent by the UE all belong to GSM coding and decoding types and do not have UMTS coding and decoding types;

6. the coding and decoding types supported by the UE carried in the registration request message sent by the UE are both UMTS coding and decoding types and GSM coding and decoding types;

in cooperation with the above conditions, if the MME determines that the UE further satisfies condition 5, the MME may determine that the UE only supports eCSFB based on LTE- > GSMSRVCC and does not support eCSFB based on LTE- > UMTS SRVCC, and the MME selects an MSC supporting eCSFB based on SRVCC for the UE to register.

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

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

7. the UE identification of the eCSFB supporting LTE- > GSM SRVCC stored by the MME comprises the identification of the UE, and the identification of the UE of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME does not comprise the identification of the UE, so that the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC;

the MME can determine that the UE only supports eCSFB based on LTE- > GSM SRVCC and does not support eCSFB based on LTE- > UMTSSRVCC, and the MME selects an MSC supporting the eCSFB based on SRVCC for the UE to register.

8. The UE identification of the eCSFB supporting LTE- > GSM SRVCC stored by the MME comprises the identification of the UE, and the UE identification of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME comprises the identification of the UE,

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

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

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

2. the user type identifier (classmark) information carried in the registration request message sent by the UE includes classmark 2.

The classmark2 is used to indicate that the UE supports SRVCC handover (the MSsupports SRVCC to GERAN or UTRAN) to GERAN or UTRAN. If the UE simultaneously meets the 2 conditions, the MME determines that the UE supports eCSFB of LTE- > UMTS SRVCC.

Optionally, in addition to the above two conditions, the MME may further need to determine whether the UE satisfies the following condition, so as to determine whether the UE supports eCSFB of LTE- > UMTS SRVCC:

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

4. the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system and is stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

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

Other steps of the present invention can refer to 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 present invention shown in fig. 2, and the present invention is not described herein again.

Therefore, based on the method provided by the embodiment of the present invention, in the process of performing the joint registration by the UE, the MME needs to determine whether the UE supports the eCSFB based on SRVCC, and further determines whether the UE supports the eCSFB based on LTE- > UMTS SRVCC. If so, the MME selects an MSC supporting the eCSFB based on the SRVCC for the UE to register, otherwise, the MME selects a common MSC for the UE to register. In the method for differentially registering the UE, under the condition that a network side can only trigger the eCSFB based on LTE- > UMTSSRVCC, on one hand, the method is beneficial to supporting the eCSFB flow based on LTE- > UMTS SRVCC in the process that the UE of the eCSFB can subsequently initiate the voice service, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; on the other hand, the difference between the MSC registered by the UE which does not support the eCSFB based on LTE- > UMTS SRVCC and the MSC actually processing the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are further avoided.

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

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

5. the coding and decoding types supported by the UE carried in the registration request message sent by the UE all belong to UMTS coding and decoding types and do not have GSM coding and decoding types; or,

the user type identifier (classmark) information carried in the registration request message sent by the UE only contains classmark2, but not classmark 3.

If the MME judges that the UE meets the conditions of 1, 2 and 5 or 1, 2, 3 and 5, the MME determines that the UE only supports eCSFB based on LTE- > UMTS SRVCC and does not support eCSFB based on LTE- > GSM SRVCC, and the MME selects an MSC supporting the eCSFB based on SRVCC for the UE to register.

Optionally, the MME determines that the UE satisfies the following condition:

6. the UE identification of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME comprises the UE identification, and the UE identification of the eCSFB supporting LTE- > GSM SRVCC stored by the MME does not comprise the UE identification, so that the MME determines that the UE supports the eCSFB supporting LTE- > UMTS SRVCC but does not support the eCSFB supporting LTE- > GSM SRVCC.

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

Fig. 4 shows a schematic flow chart of a joint registration method provided by an embodiment of the present invention, which may be performed by any suitable device, for example, by an MME, which is not limited in this respect.

As shown in fig. 4, the method includes:

s401, a mobility management entity MME receives identification information of UE;

specifically, the identity information of the UE may be carried by the UE in the registration request message and sent to the MME, or may be carried by the UE in another process message (such as an authentication process or an identity obtaining process) after sending the registration request message and sent to the MME, which is not limited in this embodiment of the invention.

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

S402, the MME determines that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the identification information of the UE;

specifically, if the UE identifier stored by the MME and supporting the SRVCC-based eCSFB includes the UE identifier, the MME determines that the UE supports the SRVCC-based eCSFB.

Optionally, if the UE identity of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM includes the UE identity, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM.

Further, the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the MME does not include the UE identifier, so that the MME determines that the UE supports eCSFB supporting LTE- > UMTS SRVCC but does not support eCSFB supporting LTE- > GSM SRVCC. Or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME includes the UE identity, then the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the eCSFB based on LTE- > UMTS SRVCC.

Optionally, if the UE identity of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system stored by the MME includes the UE identity, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

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

S403, the MME selects a mobile switching center MSC supporting the eCSFB based on the SRVCC for the UE to register.

The mobile switching center MSC supporting the eCSFB based on SRVCC is an MSC supporting both the CSFB function and the SRVCC function.

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

Optionally, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the MME does not include the UE identity in the registration request message, the MME determines that the UE does not support the eCSFB supporting LTE- > GSM SRVCC; and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

Optionally, the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC included in the MME does not include the UE identifier, the MME determines that the UE does not support the eCSFB supporting LTE- > UMTS SRVCC, and the MME selects an MSC that does not support the eCSFB based on SRVCC for the UE to register.

In the embodiment of the present invention, reference may be made to the relevant steps shown in fig. 2 and fig. 3 in the embodiment of the present invention, that is, in the embodiment, after receiving the UE identifier, the MME in the embodiment determines whether the UE supports an eCSFB based on SRVCC, and reference may be made to the relevant steps in fig. 2 and fig. 3. The present invention is not described in detail herein.

Therefore, based on the method provided by the embodiment of the present invention, the UE sends the UE identification information to the MME, the MME determines whether the UE supports the eCSFB based on the SRVCC according to the UE identification information, if so, the MME selects the MSC supporting the eCSFB based on the SRVCC for the UE to perform registration, and if not, the MME selects the MSC not supporting the eCSFB based on the SRVCC for the UE to perform registration. The MSC selects a proper MSC for the UE to register, so that the UE supporting the eCSFB based on the SRVCC can trigger the eCSFB flow based on the SRVCC in the subsequent voice service initiating process, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; the difference between the MSC which does not support the registration of the UE of the eCSFB based on the SRVCC and the MSC which actually processes the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are avoided.

Fig. 5 shows a schematic block diagram of an apparatus for joint registration according to an embodiment of the present invention, which may be any suitable apparatus, for example, the apparatus may be an MME, but the present invention is not limited thereto. The apparatus may perform the methods provided by the embodiments of the present invention shown in fig. 2 and 3.

As shown in fig. 5, the apparatus includes:

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

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

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

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

Or,

the registration request message includes an identifier of the UE, and if the identifier of the UE supporting the eCSFB based on SRVCC stored in the apparatus includes the identifier of the UE, the processing module 502 determines that the UE supports the eCSFB based on SRVCC.

Optionally, if the UE type identifier (classmark) information in the registration request message includes classmark2 and classmark3, the processing module 502 is further configured to determine that the UE supports eCSFB (eCSFB of LTE- > GSM SRVCC) for SRVCC handover from a long term evolution communication system to a global system for mobile communications.

Or, the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications and that is stored in the apparatus includes the identifier of the UE, the processing module 502 is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications.

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

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

the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus includes the UE identity, then the processing module 502 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the 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 eCSFB for SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system (LTE- > eCSFB for UMTS SRVCC).

Or, the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > UMTS SRVCC) supporting SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system, which is saved by the apparatus, includes the identifier of the UE, the processing module 502 is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) supporting SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

If the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if the user type identifier (classmark) information carried in the registration request message only contains classmark2 and does not contain classmark 3; or, the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus does not include the UE identifier, then the processing module 502 is configured to determine that the UE supports eCSFB supporting LTE- > UMTS SRVCC but does not support eCSFB supporting LTE- > GSM SRVCC.

The processing module 502 is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register.

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

the apparatus 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 procedure, where the location update request message includes an identity of the UE.

Optionally, the processing module 502 is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE. Specifically, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the UE identifier that supports an eCSFB based on SRVCC stored in the apparatus does not include the UE identifier in the registration request message, the processing module 502 is configured to determine that the UE does not support an eCSFB based on SRVCC.

If the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not include classmark2 and classmark3 at the same time, or the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored in the device does not include the UE identifier in the registration request message, the processing module 502 is configured to determine that the UE does not support an eCSFB supporting LTE- > GSM SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

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

Based on the device provided by the embodiment of the invention, in the process of performing combined registration on the UE, the MME judges whether the UE supports the eCSFB based on the SRVCC, if so, the MME selects the MSC supporting the eCSFB based on the SRVCC for the UE to perform registration, and if not, the MME selects the MSC not supporting the eCSFB based on the SRVCC for the UE to perform registration. The MSC selects a proper MSC for the UE to register, so that the UE supporting the eCSFB based on the SRVCC can trigger the eCSFB flow based on the SRVCC in the subsequent voice service initiating process, and the time delay of CSFB call establishment is greatly shortened by utilizing the advantage of SRVCC switching; the difference between the MSC which does not support the registration of the UE of the eCSFB based on the SRVCC and the MSC which actually processes the voice service is avoided, and the problems of increased call setup delay and unreachable called party caused by the difference are avoided.

Fig. 6 shows a schematic block diagram of an apparatus for joint registration according to an embodiment of the present invention, which may be any suitable apparatus, for example, the apparatus may be an MME, but the present invention is not limited thereto. The apparatus may perform the methods provided by the embodiments of the present invention shown in fig. 2 and 3.

As shown in fig. 6, the apparatus includes:

a receiver 601, configured to receive a registration request message of a UE;

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

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

Or,

the registration request message includes an identifier of the UE, and if the identifier of the UE supporting the SRVCC-based eCSFB stored in the apparatus includes the identifier of the UE, the processor 602 determines that the UE supports the SRVCC-based eCSFB.

Optionally, if the UE type identifier (classmark) information in the registration request message includes classmark2 and classmark3, the processor 602 is further configured to determine that the UE supports eCSFB (eCSFB of LTE- > GSM SRVCC) for SRVCC handover from a long term evolution communication system to a global system for mobile communications.

Or, the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) supporting SRVCC handover from the long term evolution communication system to the global system for mobile communications, which is stored in the apparatus, includes the identifier of the UE, the processor 602 is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) supporting SRVCC handover from the long term evolution communication system to the global system for mobile communications.

Further, if the codec type supported by the UE in the registration request message belongs to a GSM coding type and does not have a UMTS codec type, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus does not include the UE identity, the processor 602 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC.

the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus includes the UE identity, then the processor 602 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and support the 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 eCSFB for SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system (LTE- > eCSFB for UMTS SRVCC).

Or, the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > UMTS SRVCC) supporting SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system, which is saved by the apparatus, includes the identifier of the UE, the processor 602 is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) supporting SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

If the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if the user type identifier (classmark) information carried in the registration request message only contains classmark2 and does not contain classmark 3; or, the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus does not include the UE identifier, then the processor 602 is configured to determine that the UE supports the eCSFB supporting LTE- > UMTS SRVCC but does not support the eCSFB supporting LTE- > GSM SRVCC.

The processor 602 is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register.

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

the apparatus further includes a transmitter 603, where the transmitting module is configured to transmit a location update request message to the MSC, so that the MSC initiates a location update procedure, where the location update request message includes an identity of the UE.

Optionally, the processor 602 is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE. Specifically, if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the UE identifier that supports an eCSFB based on SRVCC stored in the apparatus does not include the UE identifier in the registration request message, the processor 602 is configured to determine that the UE does not support an eCSFB based on SRVCC.

If the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not include classmark2 and classmark3 at the same time, or the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored in the device does not include the UE identifier in the registration request message, the processor 602 is configured to determine that the UE does not support an eCSFB supporting LTE- > GSM SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

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

Fig. 7 shows a schematic block diagram of an apparatus for joint registration according to an embodiment of the present invention, which may be any suitable apparatus, for example, the apparatus may be an MME, but the present invention is not limited thereto. The apparatus may perform the method provided by the embodiment of the present invention shown in fig. 4.

As shown in fig. 7, the apparatus includes:

a receiving module 701, configured to receive identity information of a UE;

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

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

if the UE identifier of the UE supporting the eCSFB based on SRVCC stored in the apparatus includes the UE identifier, the processing module 702 is configured to determine that the UE supports the eCSFB based on SRVCC.

Optionally, if the UE identity of the eCSFB (eCSFB for LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM includes the UE identity, the processing module 702 is configured to determine that the UE supports the eCSFB (eCSFB for LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM.

Further, if the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the identifier of the UE, and the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus does not include the identifier of the UE, the processing module 702 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC. Or,

the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus includes the UE identity, then the processing module 702 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the eCSFB based on LTE- > UMTS SRVCC.

Optionally, if the UE identity of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system stored by the apparatus includes the UE identity, the processing module 702 is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

Further, if the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus does not include the UE identifier, the processing module 702 is configured to determine that the UE supports eCSFB supporting LTE- > UMTS SRVCC but does not support eCSFB supporting LTE- > GSM SRVCC.

The processing module 702 is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register.

Optionally, the processing module 702 is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE. If the UE identifier that supports the SRVCC-based eCSFB stored in the apparatus does not include the UE identifier, the processing module 702 is configured to determine that the UE does not support the SRVCC-based eCSFB.

In another embodiment of the present invention, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus does not include the identity of the UE in the registration request message, the processing module 702 is configured to determine that the UE does not support the eCSFB supporting LTE- > GSM SRVCC,

the embodiment of the present invention may refer to the relevant steps shown in fig. 2 and fig. 3 in the embodiment of the present invention, that is, the device in the embodiment may refer to the relevant steps in fig. 2 and fig. 3 for determining whether the UE supports the eCSFB based on SRVCC after receiving the UE identifier. The present invention is not described in detail herein.

Fig. 8 is a schematic block diagram of an apparatus for joint registration according to an embodiment of the present invention, which may be any suitable apparatus, for example, the apparatus may be an MME, but the present invention is not limited thereto. The apparatus may perform the method provided by the embodiment of the present invention shown in fig. 4.

As shown in fig. 8, the apparatus includes:

a receiver 801 for receiving identification information of a UE;

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

A processor 802 configured to determine, according to the identification information of the UE, that the UE supports an enhanced circuit switched fallback eCSFB based on single radio voice call continuity, SRVCC;

if the UE identifier stored in the apparatus for supporting an eCSFB based on SRVCC includes the UE identifier, the processor 802 is configured to determine that the UE supports an eCSFB based on SRVCC.

Optionally, if the UE identity of the eCSFB (eCSFB for LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM includes the UE identity, the processor 802 is configured to determine that the UE supports the eCSFB (eCSFB for LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM.

Further, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus does not include the UE identity, the processor 802 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC. Or,

the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus includes the UE identity, then the processor 802 is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the eCSFB based on LTE- > UMTS SRVCC.

Optionally, if the UE identity of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system stored in the apparatus includes the UE identity, the processor 802 is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

Further, if the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus does not include the UE identifier, the processor 802 is configured to determine that the UE supports eCSFB supporting LTE- > UMTS SRVCC but does not support eCSFB supporting LTE- > GSM SRVCC.

The processor 802 is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register.

Optionally, the processor 802 is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE. If the UE identifier that supports the SRVCC-based eCSFB stored in the apparatus does not include the UE identifier, the processor 802 is configured to determine that the UE does not support the SRVCC-based eCSFB.

In another embodiment of the present invention, if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus does not include the UE identity in the registration request message, the processor 802 is configured to determine that the UE does not support the eCSFB supporting LTE- > GSM SRVCC,

It should be understood that in the embodiments 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 (DSP), Application Specific Integrated Circuits (ASIC), Field Programmable Gate Arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and so on. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

In implementation, the above steps may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor. To avoid repetition, it is not described in detail here.

Those of ordinary skill in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both, and that the steps and elements of the various embodiments have been described above generally in terms of their functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a 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 stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A co-registration method, comprising:

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

the MME determines that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the registration request message;

the MME selects a mobile switching center MSC supporting eCSFB based on SRVCC for the UE to register;

the MME determines that the UE supports the eCSFB based on the SRVCC according to the registration request message, and the method comprises the following steps:

if the registration request message comprises indication information that the UE supports the eCSFB based on the SRVCC, the MME determines that the UE supports the eCSFB based on the SRVCC; or, the registration request message includes the identifier of the UE, and if the identifier of the UE supporting the eCSFB based on SRVCC stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB based on SRVCC;

the MME selects a mobile switching center MSC supporting the eCSFB based on the SRVCC for the UE to register, and the registration comprises the following steps:

the MME selects a mobile switching center MSC supporting eCSFB based on SRVCC;

and the MME sends a location updating request message to the MSC so as to enable the MSC to initiate a location updating process, wherein the location updating request message comprises the identity of the UE.

2. The method of claim 1, wherein the registration request message further includes indication information that the UE supports SRVCC, and wherein the MME determines that the UE supports an eCSFB based on SRVCC.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the MME determines that the UE does not support eCSFB based on SRVCC;

and the MME selects an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

4. The method of claim 3, wherein the MME determining that the UE does not support an eCSFB based on SRVCC, comprises:

if the registration request message contains the indication information that the UE does not support the eCSFB based on the SRVCC, or the registration request message contains the indication information that the UE does not support the SRVCC, or the UE identifier which is stored in the MME and supports the eCSFB based on the SRVCC does not include the UE identifier in the registration request message, the MME determines that the UE does not support the eCSFB based on the SRVCC.

5. The method according to claim 1 or 2, characterized in that the method further comprises:

if the UE type identifier (classmark) information in the registration request message includes classmark2 and classmark3, the MME determines that the UE supports eCSFB (eCSFB of LTE- > GSM SRVCC) for SRVCC handover from a long term evolution communication system to a global system for mobile communications.

6. The method of claim 1, wherein the MME determining that the UE supports an eCSFB based on SRVCC according to the registration request message comprises:

the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications and that is stored by the MME includes the identifier of the UE, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the long term evolution communication system to the global system for mobile communications.

7. The method according to claim 1 or 2, characterized in that the method further comprises:

if the registration request message contains indication information that the UE does not support the eCSFB based on the SRVCC, or the registration request message contains indication information that the UE does not support the SRVCC, or the classmark message of the UE in the registration request message does not contain classmark2 and classmark3 at the same time, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the MME does not contain the UE identity in the registration request message, the MME determines that the UE does not support the eCSFB supporting LTE- > GSM SRVCC;

8. The method according to claim 1 or 2, characterized in that the method further comprises:

if the classmark information of the UE in the registration request message contains classmark 2; the MME determines that the UE supports eCSFB (eCSFB of LTE- > UMTSSRVCC) for SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system.

9. The method of claim 1 or 2, wherein the MME determining that the UE supports SRVCC-based eCSFB according to the registration request message comprises:

the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that is stored by the MME and supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system includes the identifier of the UE, the MME determines that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from the long term evolution communication system to the universal mobile telecommunications system.

10. The method according to claim 1 or 2, characterized in that the method further comprises:

if the registration request message includes indication information that the UE does not support the eCSFB based on the SRVCC, or the registration request message includes 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 classmark2, or the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC included in the MME does not include the UE identifier in the registration request message, the MME determines that the UE does not support the eCSFB of LTE- > UMTS SRVCC,

11. The method of claim 5, further comprising:

if the codec type supported by the UE in the registration request message belongs to a GSM coding type and does not have a UMTS codec type, or the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the MME includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME does not include the UE identity, the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC.

12. The method of claim 5, further comprising:

and the UE identification of the eCSFB supporting LTE- > GSM SRVCC stored by the MME comprises the identification of the UE, and the UE identification of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME comprises the identification of the UE, so that the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and supports the eCSFB based on LTE- > UMTS SRVCC.

13. The method of claim 5, further comprising:

if the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if the user type identifier (classmark) information carried in the registration request message only contains classmark2 and does not contain classmark 3; or the identity of the UE supporting the eCSFB of LTE- > UMTS SRVCC stored by the MME includes the identity of the UE, and the identity of the UE supporting the eCSFB of LTE- > GSM SRVCC stored by the MME does not include the identity of the UE, then the MME determines that the UE supports the eCSFB of LTE- > UMTS SRVCC but does not support the eCSFB of LTE- > GSM SRVCC.

14. The method according to claim 1 or 2, wherein the mobile switching center MSC supporting the SRVCC-based eCSFB refers to an MSC supporting both CSFB and SRVCC functions.

15. The method of claim 1 or 2, wherein the registration request message is an Attach (Attach) request message or a Tracking Area Update (TAU) request message.

16. The method according to claim 1 or 2, wherein the registration request message includes a registration type information element, and the registration type information element is configured as a joint attachment or joint tracking area TA/location area LA update.

17. A co-registration method, comprising:

a mobility management entity MME receives identification information of UE;

the MME determines that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the identification information of the UE;

the MME determines that the UE supports the eCSFB based on the SRVCC according to the identification of the UE, and the method comprises the following steps:

if the identification of the UE supporting the eCSFB based on the SRVCC stored by the MME comprises the identification of the UE, the MME determines that the UE supports the eCSFB based on the SRVCC;

the MME selects a mobile switching center MSC supporting eCSFB based on SRVCC;

18. The method of claim 17, further comprising:

the MME determines that the UE does not support eCSFB based on SRVCC;

19. The method of claim 18, wherein the MME determining that the UE does not support an eCSFB based on SRVCC comprises:

and if the UE identification which is stored in the MME and supports the eCSFB based on the SRVCC does not comprise the identification of the UE, the MME determines that the UE does not support the eCSFB based on the SRVCC.

20. The method as claimed in any of claims 17-19, wherein the MME determining that the UE supports an eCSFB based on SRVCC according to the identity of the UE comprises:

if the UE identity of the eCSFB (eCSFB for LTE-SRVCC) which supports SRVCC handover from a long term evolution communication system to a global system for mobile communication stored by the MME includes the UE identity, the MME determines that the UE supports the eCSFB for SRVCC handover from the long term evolution communication system to the global system for mobile communication (eCSFB for LTE-SRVCC).

21. The method according to any one of claims 17-19, further comprising:

the UE identification of the eCSFB supporting LTE- > GSM SRVCC stored in the MME does not comprise the identification of the UE in the registration request message, and the MME determines that the UE does not support the eCSFB supporting LTE- > GSM SRVCC;

22. The method as claimed in any of claims 17-19, wherein the MME determining that the UE supports an eCSFB based on SRVCC according to the identity of the UE comprises:

if the UE identity of the eCSFB (eCSFB of LTE-UMTS SRVCC) which supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system and is stored by the MME comprises the UE identity, the MME determines that the UE supports the eCSFB (eCSFB of LTE-UMTS SRVCC) which supports SRVCC handover from the long term evolution communication system to the universal mobile telecommunications system.

23. The method according to any one of claims 17-19, further comprising:

the UE identification of the eCSFB supporting LTE- > UMTS SRVCC included in the MME does not include the UE identification, then the MME determines that the UE does not support the eCSFB supporting LTE- > UMTS SRVCC,

24. The method of claim 19, further comprising:

the UE identification of the eCSFB supporting LTE- > GSM SRVCC stored by the MME comprises the identification of the UE, and the UE identification of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME does not comprise the identification of the UE, so that the MME determines that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC.

25. The method of claim 19, further comprising:

26. The method of claim 19, further comprising:

the UE identification of the eCSFB supporting LTE- > UMTS SRVCC stored by the MME comprises the UE identification, and the UE identification of the eCSFB supporting LTE- > GSM SRVCC stored by the MME does not comprise the UE identification, so that the MME determines that the UE supports the eCSFB supporting LTE- > UMTS SRVCC but does not support the eCSFB supporting LTE- > GSM SRVCC.

27. The method according to any of claims 17-19, wherein said mobile switching center MSC supporting an SRVCC-based eCSFB refers to an MSC supporting both CSFB and SRVCC functionalities.

28. The method according to any of claims 17-19, wherein the identity information of the UE is the IMSI or IMEI of the UE.

29. A joint registration apparatus, comprising:

a receiving module, configured to receive a registration request message of a 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; the mobile switching center MSC is also used for selecting the mobile switching center MSC supporting the eCSFB based on the SRVCC for registering;

the processing module is configured to determine, according to the registration request message, that the UE supports an eCSFB based on SRVCC, and includes:

if the registration request message includes indication information that the UE supports the eCSFB based on the SRVCC, the processing module is configured to determine that the UE supports the eCSFB based on the SRVCC; or, the registration request message includes an identifier of the UE, and if the identifier of the UE supporting the eCSFB based on SRVCC stored in the apparatus includes the identifier of the UE, the processing module is configured to determine that the UE supports the eCSFB based on SRVCC;

the processing module is configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register, and includes:

the processing module is used for selecting a mobile switching center MSC supporting eCSFB based on SRVCC;

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 procedure, where the location update request message includes the identity of the UE.

30. The apparatus of claim 29, wherein if the registration request message further includes indication information that the UE supports SRVCC, the processing module is further configured to determine that the UE supports an eCSFB based on SRVCC.

31. The apparatus of claim 29 or 30,

the processing module is further configured to determine that the UE does not support an eCSFB based on SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

32. The apparatus of claim 31, wherein the processing module configured to determine that the UE does not support an eCSFB based on SRVCC comprises:

if the registration request message includes indication information that the UE does not support the SRVCC-based eCSFB, or the registration request message includes indication information that the UE does not support the SRVCC, or the UE identifier that supports the SRVCC-based eCSFB stored in the device does not include the UE identifier in the registration request message, the processing module is configured to determine that the UE does not support the SRVCC-based eCSFB.

33. The apparatus of claim 29 or 30,

if the UE type identifier (classmark) information in the registration request message includes classmark2 and classmark3, the processing module is further configured to determine that the UE supports eCSFB (eCSFB of LTE- > GSM SRVCC) for SRVCC handover from a long term evolution communication system to a global system for mobile communications.

34. The apparatus of claim 29, wherein the processing module is configured to determine that the UE supports an eCSFB based on SRVCC from the registration request message, and wherein the determining comprises:

the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > GSM SRVCC) supporting SRVCC handover from the long term evolution communication system to the global system for mobile communications stored in the device includes the identifier of the UE, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) supporting SRVCC handover from the long term evolution communication system to the global system for mobile communications.

35. The apparatus of claim 29 or 30,

if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not include classmark2 and classmark3 at the same time, or the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored in the device does not include the UE identifier in the registration request message, the processing module is configured to determine that the UE does not support an eCSFB supporting LTE- > GSM SRVCC; and selecting an MSC (mobile switching center) which does not support the eCSFB based on the SRVCC for registering for the UE.

36. The apparatus of claim 29 or 30,

if the classmark information of the UE in the registration request message contains classmark 2; the processing module is configured to determine that the UE supports eCSFB for SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system (LTE- > eCSFB for UMTS SRVCC).

37. The apparatus of claim 29, wherein the processing module is configured to determine that the UE supports an eCSFB based on SRVCC from the registration request message, and wherein the determining comprises:

the registration request message includes an identifier of the UE, and if the UE identifier of the eCSFB (eCSFB of LTE- > UMTS SRVCC) supporting SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system, which is saved by the apparatus, includes the identifier of the UE, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) supporting SRVCC handover from the long term evolution communication system to the universal mobile telecommunications system.

38. The apparatus of claim 29 or 30,

if the registration request message includes indication information that the UE does not support an eCSFB based on SRVCC, or the registration request message includes indication information that the UE does not support SRVCC, or the classmark message of the UE in the registration request message does not include classmark2, or the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC included in the processing module does not include the UE identifier in the registration request message, the processing module is configured to determine that the UE does not support an eCSFB supporting LTE- > UMTS SRVCC, and the processing module is further configured to select an MSC that does not support an sfb based on SRVCC for the UE to register.

39. The apparatus of claim 29 or 30,

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

40. The apparatus of claim 33,

the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored by the device includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored by the device includes the UE identity, then the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and support the eCSFB based on LTE- > UMTS SRVCC.

41. The apparatus of claim 33,

if the codec type supported by the UE in the registration request message belongs to a UMTS codec type and does not have a GSM codec type, or if the user type identifier (classmark) information carried in the registration request message only contains classmark2 and does not contain classmark 3; or the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored by the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored by the apparatus does not include the UE identifier, the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > UMTS SRVCC but does not support the eCSFB supporting LTE- > GSM SRVCC.

42. The apparatus according to claim 29 or 30, wherein the mobile switching center MSC supporting an eCSFB based on SRVCC refers to an MSC supporting both CSFB and SRVCC functions.

43. The apparatus according to claim 29 or 30, wherein the registration request message is an Attach (Attach) request message or a Tracking Area Update (TAU) request message.

44. The apparatus according to claim 29 or 30, wherein the registration request message includes a registration type information element configured as a joint attachment or joint tracking area TA/location area LA update.

45. A joint registration apparatus, comprising:

a receiving module, configured to receive identification information of a UE;

the processing module is used for determining that the UE supports enhanced circuit switched fallback eCSFB based on single wireless voice call continuity (SRVCC) according to the identification information of the UE; the processing module is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register;

the processing module is configured to determine, according to the identifier of the UE, that the UE supports an eCSFB based on SRVCC, and includes:

if the identifier of the UE supporting the eCSFB based on SRVCC stored in the apparatus includes the identifier of the UE, the processing module is configured to determine that the UE supports the eCSFB based on SRVCC;

the processing module is further configured to select a mobile switching center MSC supporting an eCSFB based on SRVCC for the UE to register, including:

the processing module is configured to select a mobile switching center MSC that supports an eCSFB based on SRVCC, and send a location update request message to the MSC, so that the MSC initiates a location update procedure, where the location update request message includes the identity of the UE.

46. The apparatus of claim 45,

47. The apparatus of claim 46, wherein the processing module configured to determine that the UE does not support an eCSFB based on SRVCC comprises:

if the UE identifier that supports the SRVCC-based eCSFB stored in the apparatus does not include the UE identifier, the processing module is configured to determine that the UE does not support the SRVCC-based eCSFB.

48. The apparatus of any of claims 45-47, wherein the processing module configured to determine that the UE supports an eCSFB based on SRVCC from the identity of the UE comprises:

if the UE identity of the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM includes the UE identity, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > GSM SRVCC) that supports SRVCC handover from the LTE to the GSM.

49. The apparatus of any one of claims 45-47,

if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus does not include the UE identity in the registration request message, the processing module is configured to determine that the UE does not support the eCSFB supporting LTE- > GSM SRVCC,

the processing module is used for selecting an MSC which does not support the eCSFB based on the SRVCC for the UE to register.

50. The apparatus of any of claims 45-47, wherein the processing module configured to determine that the UE supports an eCSFB based on SRVCC from the identity of the UE comprises:

if the UE identity of the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from a long term evolution communication system to a universal mobile telecommunications system stored in the apparatus includes the UE identity, the processing module is configured to determine that the UE supports the eCSFB (eCSFB of LTE- > UMTS SRVCC) that supports SRVCC handover from the long term evolution communication system to the universal mobile telecommunications system.

51. The apparatus of any one of claims 45-47,

if the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC included in the device does not include the UE identifier, the processing module is configured to determine that the UE does not support the eCSFB supporting LTE- > UMTS SRVCC, and select an MSC that does not support the eCSFB based on SRVCC for the UE to register.

52. The apparatus of claim 47,

if the UE identity of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus includes the UE identity, and the UE identity of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus does not include the UE identity, the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > GSM SRVCC and does not support the eCSFB based on LTE- > UMTS SRVCC.

53. The apparatus of claim 47,

54. The apparatus of claim 47,

the UE identifier of the eCSFB supporting LTE- > UMTS SRVCC stored in the apparatus includes the UE identifier, and the UE identifier of the eCSFB supporting LTE- > GSM SRVCC stored in the apparatus does not include the UE identifier, so that the processing module is configured to determine that the UE supports the eCSFB supporting LTE- > UMTS SRVCC but does not support the eCSFB supporting LTE- > GSM SRVCC.

55. The apparatus of any of claims 45-47, wherein the mobile switching center MSC supporting SRVCC-based eCSFB refers to an MSC that supports both CSFB and SRVCC functions.

56. The apparatus of any of claims 45-47, wherein the UE identity information is an IMSI or IMEI of the UE.