WO2013048189A2 - Procédé destiné à favoriser la continuité d'un service vocal - Google Patents

Procédé destiné à favoriser la continuité d'un service vocal Download PDF

Info

Publication number
WO2013048189A2
WO2013048189A2 PCT/KR2012/007931 KR2012007931W WO2013048189A2 WO 2013048189 A2 WO2013048189 A2 WO 2013048189A2 KR 2012007931 W KR2012007931 W KR 2012007931W WO 2013048189 A2 WO2013048189 A2 WO 2013048189A2
Authority
WO
WIPO (PCT)
Prior art keywords
srvcc
mme
utran
geran
voice service
Prior art date
Application number
PCT/KR2012/007931
Other languages
English (en)
Other versions
WO2013048189A3 (fr
Inventor
Lixiang Xu
Hong Wang
Original Assignee
Samsung Electronics Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2013048189A2 publication Critical patent/WO2013048189A2/fr
Publication of WO2013048189A3 publication Critical patent/WO2013048189A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists

Definitions

  • the present invention relates to mobile communication technology, and more particularly to a method for supporting voice service continuity.
  • Fig. 1 shows a block diagram of an existing SAE system.
  • UE User equipment
  • E-UTRAN Evolved universal terrestrial radio access network
  • eNB evolved node B
  • MME Mobile management entity
  • Serving gateway (SWG) 104 is primarily for offering the functions of user plane.
  • the MME 103 and the SGW 104 can locate at the same physical entity.
  • LGW 105 is responsible for functions like accounting, legal monitoring, etc., and it is possible that both the SGW 104 and the LGW 105 locate at the same physical entity.
  • Policy and charging rules function (PCRF) 106 is for providing quality of service (QoS) policy and accounting criterion.
  • General packet radio service supporting node (SGSN) 108 is network node equipment which is for providing routing for data transmission in Universal mobile telecommunications systems (UNTS).
  • SGSN General packet radio service supporting node
  • UNTS Universal mobile telecommunications systems
  • Home subscriber server (HSS) 109 is the UE’s home subscriber sub-system, which is responsible for storing user’s information such as the UE’s current location, the serving node’s address, user’s security related information, and UE’s activated packet data protocol context and so on.
  • the voice service in the SAE system can be implemented through the following two ways.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • UE which receives voice service through the IMS in the Long Term Evolution (LTE) system moves to UTRAN or GSM EDGE Radio Access Network (GERAN) system
  • GERAN GSM EDGE Radio Access Network
  • SSRVCC Single Radio Voice Call Continuity
  • CSFB Circuit Switched Fallback
  • the MME determines whether the LTE system is used to provide voice service for the UE (i.e., Voice over LTE (voLTE)) or the CSFB way is used to provide voice service for the UE.
  • voLTE Voice over LTE
  • the voLTE it needs to try to ensure the continuity of voice service when the UE moves.
  • the UE can perform the interoperability Testing (IOT) of SRVCC to Global System for Mobile communications (GSM) and/or the IOT of SRVCC to Universal Mobile Telecommunications System (UMTS), and send IOT information to the eNB.
  • IOT interoperability Testing
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Telecommunications System
  • the UE also needs to use non-access (NAS) layer to instruct the MME (recorded as NAS layer instructions) the capability of the UE SRVCC to UTRAN/GERAN.
  • NAS non-access
  • 0 instructs supporting the SRVCC from the UTRAN HSPA or the E-UTRAN to the GERAN/UTRAN.
  • the designs of the access layer and the NAS layer are independent from each other. Some problems may be caused when the two are not improperly set.
  • the access layer instruction is: both of the IOT information of the UE SRVCC to GSM and the IOT information of the UE SRVCC to UMTS are no
  • the NAS layer instruction is: the UE supports SRVCC to GERAN/UTRAN; in this case, the MME will send voIMS indication as yes to the UE; if the current LTE coverage is not good but the GERAN/UTRAN coverage is very good, in this way, when the UE moves the LTE coverage, it will cause an interruption of the voice service.
  • the present invention provides a method for supporting voice service continuity, which can realize the continuity of the voice service.
  • a method for supporting voice service continuity includes:
  • the method can also include steps:
  • the base station deciding whether initiating a switching to UTRAN or GERAN, or deciding initiating a switching to which of UTRAN and GERAN.
  • a method for supporting voice service continuity includes:
  • the base station sending the received IOT information of SRVCC to GSM and the received IOT information of SRVCC to UMTS to MME;
  • a method for supporting voice service continuity includes:
  • MME setting an instruction of whether supporting provision of IMS voice in PS domain according to the IOT information sent by the eNB.
  • a method for supporting voice service continuity includes:
  • the MME decides the voIMS indication for the UE according to the information of whether supporting the capability of SRVCC to UTRAN of the NAS layer and the capability of SRVCC to GERAN of the NAS layer; or the MME decides the voIMS indication for the UE according to the capability of SRVCC to UTRAN/GERAN of the NAS layer and the IOT information of SRVCC to GSM of the access layer and/or the IOT information of SRVCC to UMTS, and sets the indication of whether supporting provision of IMS voice in PS domain, thereby achieving the continuity of the voice service.
  • the base station decides whether initiating a switching to UTRAN or GERAN or decides initiating a switching to which of UTRAN and GERAN according to the feasibility of SRVCC to UTRAN and the feasibility of SRVCC to GERAN, thereby ensuring successful switching.
  • Fig. 1 is a system structure diagram of an SAE
  • Fig. 2 is a flow chart of a method for supporting voice service continuity of a first embodiment of the present invention
  • Fig. 3 is a flow chart of a method for supporting voice service continuity of a second embodiment of the present invention.
  • Fig. 4 is a first embodiment of a process of the eNB deciding the SRVCC
  • Fig. 5 is a flow chart of a method for supporting voice service continuity of a third embodiment of the present invention.
  • Fig. 6 is a second embodiment of a process of the eNB deciding the SRVCC
  • Fig. 7 is a flow chart of a method for supporting voice service continuity of a fourth embodiment of the present invention.
  • Fig. 8 is a flow chart of a method for supporting voice service continuity of a fifth embodiment of the present invention.
  • the IOT information of the access layer SRVCC to GSM and/or the IOT information of the access layer SRVCC to UMTS when setting the capability of the NAS layer SRVCC to UTRAN/GERAN.
  • the capability of SRVCC to UTRAN/GERAN is set to support; or when the IOT information of SRVCC to GSM is yes, or when the IOT information of SRVCC to UMTS is yes, the capability of SRVCC to UTRAN/GERAN is set to support; it can be specifically set according to the actual situation, and it is not specifically limited here.
  • the above settings can solve to some extent the problem of the voice service continuity, but still cannot completely avoid all the problems. For example, if the above settings are: when both of the IOT information of SRVCC to GSM and the IOT information of SRVCC to UMTS are yes, the capability of SRVCC to UTRAN/GERAN is set to support, so, when the IOT information of SRVCC to GSM is yes while the IOT information of SRVCC to UMTS is no, the capability of SRVCC to UTRAN/GERAN is to not support, in this case, if the MMES does not establish the voLTE service for the UE, then when the current position where the UE locates is not covered by the UTRAN or the GERAN, the UE cannot enjoy voice service at the current position.
  • the capability of SRVCC to UTRAN/GERAN is set to support; in this case, the MME establishes the voLTE service for the UE, while when the UE moves to the UMTS coverage, it will cause an interruption of the voLTE service.
  • whether supporting SRVCC to UTRAN and whether supporting SRVCC to GERAN are sent to the MME by the UE.
  • the settings of whether supporting SRVCC to UTRAN and whether supporting SRVCC to GERAN includes two ways:
  • settings of the capability of SRVCC to UTRAN and SRVCC to GERAN need to refer the IOT information of SRVCC to GSM and the IOT information of SRVCC to UNTS.
  • the IOT information of SRVCC to GSM is ‘yes’
  • the capability of SRVCC to GERAN can be ‘support’.
  • the IOT information of SRVCC to UMTS is ‘yes’
  • the capability of SRVCC to UTRAN can be ‘support’. This can avoid the problem that the MME establishes voLTE for the UE but cannot ensure the service continuity caused by when the IOT of the access layer does not support but the NAS layer is set to support. The details will be described in the following embodiments.
  • SRVCC to UTRAN and SRVCC to GERAN is support, this also means that its corresponding IOT information is yes; when the IOT information of another access layer is also support, then the capability of another NAS layer is set to support.
  • SRVCC to UTRAN of the NAS layer is corresponding to the IOT information of SRVCC to UMTS of the access layer;
  • SRVCC to GERAN of the NAS layer is corresponding to the IOT information of SRVCC to GSM of the access layer.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the embodiment 1 is that the UE sends whether supporting SRVCC to UTRAN and whether supporting SRVCC to GERAN to the MME; after the MMES receives the information about whether supporting SRVCC to UTRAN and whether supporting SRVCC to GERAN, the MME can decide manners to provide voice service for the UE, i.e., through voLTE manner or the CSFB manner to provide voice service for the UE.
  • the MME can provide voice service for the UE through the voLTE; if the capability of SRVCC to UTRAN is support and the capability of SRVCC to GERAN is nonsupport, then, when the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE; when system only deploys GERAN and does not deploy the UTRAN, the MME can provide voice service for the UE through the CSFB, when both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service through the voLTE; if the capability of SRVCC to UTRAN is nonsupport and the capability of SRVCC to GERAN is support, then, when the system only deploys the UTRAN equipment (the MME can know according to the configuration) and does not deploy the GERAN
  • Fig. 2 is a flow chart provided in the embodiment 1 of the present invention. In this flow, the detailed description of steps which have nothing to do with the flow is omitted. As shown in Fig. 2, the flow can include the following steps:
  • Step 201 the UE sends NAS message such as attach message, TA update request message and so on to the eNB.
  • the UE can send the NAS message to the eNB through an uplink information transmission or Radio Resource Control (RRC) connection establishing completion.
  • RRC Radio Resource Control
  • the NAS message includes information about whether capability of the UE SRVCC to UTRAN is support and/or whether capability of the UE SRVCC to GERAN is support.
  • the following takes the NAS message, which includes the information about whether capability of the UE SRVCC to UTRAN is support and/or whether capability of the UE SRVCC to GERAN is support, as an example for illustration.
  • Step 202 the eNB sends the NAS message sent by the UE to the MME through an S1 access protocol (AP) message.
  • AP access protocol
  • the MME When the MME receives the NAS message, the MME stores information contained in the NAS message, i.e., information about whether supporting SRVCC to UTRAN of the UE and whether supporting SRVCC to GERAN of the UE. Then, the MME can set an instruction of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to this information. For example, when the foregoing are support, the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain. Of course, as an extension of the embodiment of the present invention, there are also other setting manners which do not affect the main content of the present invention. Preferably, in the present invention, it can also consider whether the MME supports the SRVCC when the MME sets whether supporting provision of the IMS voice in the PS domain.
  • the MME can decide how to provide voice service for the UE according to the stored above information, i.e., through the voLTE or the CSFB. For example, if both of the capabilities of SRVCC to UTRAN and SRVCC to GERAN are support, then the MME can provide voice service for the UE through the voLTE; if the capability of SRVCC to UTRAN is support and the capability of SRVCC to GERAN is nonsupport, then, when the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE; when system only deploys GERAN and does not deploy the UTRAN, the MME can provide voice service for the UE through the CSFB, when both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service for the UE through the voLTE or the CSFB.
  • the MME decides using which ways to provide the voice service for the UE according to one of the received capability of SRVCC to UTRAN and the received capability of SRVCC to GERAN.
  • the MME can also have other deciding manners.
  • the present invention does not limit specific behavior of the MME.
  • the specific manner of using the voLTE or the CSFB to establish bearer for the voice service and the manner of moving to the SRVCC of the UTRAM/GERAN after using the voLTE are the same as the existing technology, and the detailed description of those is omitted here.
  • Step 203 after the MME receives the NAS message, the MME performs the NAS authentication/safety process between the MME and the UE.
  • step 203 specifically whether the MME performs and how to perform the NAS authentication/safety process is existing technology, and it will not be repeated here.
  • Step 204 the MME sends an initial context establishment request message to the eNB.
  • the message contains NAS message connection accept.
  • Step 205 after the eNB receives the initial context establishment request message, the eNB establishes a radio bearer between the MME and the UE.
  • Step 206 after the establishment of the radio bearer between the eNB and the UE, the eNB sends an initial context establishment response message to the MME.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the embodiment 2 is that the UE sends whether supporting SRVCC to UTRAN and whether supporting SRVCC to GERAN to the MME.
  • the MME combines its capability of supporting the SRVCC with whether supporting SRVCC to UTRAN and whether supporting SRVCC to GERAN received from the UE, decides and sends information about whether SRVCC to UTRAN is feasible and whether SRVCC to GERAN is feasible to the service base station of the UE.
  • Whether SRVCC to UTRAN is feasible specifically is whether the SRVCC can switch to the UTRAN
  • whether SRVCC to GERAN is feasible specifically is whether the SRVCC can switch to the GERAN, this will be described in details in the following.
  • the base station can decide whether to perform SRVCC switching and switch the UE to which system according to the received information about whether SRVCC to UTRAN is feasible and whether SRVCC to GERAN is feasible from the MME
  • the base station can clearly know that SRVCC to which systems is feasible, switching to which systems has been tested by IOT, and signal quality of which systems is better, thereby initiating a proper switching process and ensuring successful switching to achieve the continuity of the voice service.
  • Fig. 3 is flow chart provided in the embodiment 2 of the present invention. In this flow, the detailed description of steps which have nothing to do with the flow is omitted. As shown in Fig. 3, the flow can include the following steps:
  • Step 301 the UE sends NAS message such as attach message, TA update request message and so on to the eNB.
  • the UE can send the NAS message to the eNB through an uplink information transmission or RRC connection establishing completion.
  • the NAS message includes information about whether SRVCC to UTRAN of the UE is support and whether SRVCC to GERAN of the UE is support.
  • Step 302 the eNB sends the NAS message sent by the UE to the MME through an S1 access protocol (AP) message.
  • AP access protocol
  • the MME When the MME receives the NAS message, the MME stores information contained in the NAS message, i.e., information about whether supporting SRVCC to UTRAN of the UE and whether supporting SRVCC to GERAN of the UE.
  • the MME can set an instruction of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to this information. For example, when the foregoing are support, the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain.
  • it can also consider whether the MME supports the SRVCC when the MME considers to set whether supporting provision of the IMS voice in the PS domain.
  • the MME can decide how to provide voice service for the UE according to the stored above information, i.e., through the voLTE or the CSFB. For example, if both of the capabilities of SRVCC to UTRAN and SRVCC to GERAN are support, then the MME can provide voice service for the UE through the voLTE; if the capability of SRVCC to UTRAN is support and the capability of SRVCC to GERAN is nonsupport, then, when the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE; when system only deploys GERAN and does not deploy the UTRAN, the MME can provide voice service for the UE through the CSFB, when both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service for the UE through the voLTE or the CSFB.
  • the MME decides using which ways to provide the voice service for the UE according to one of the received capability of SRVCC to UTRAN and the received capability of SRVCC to GERAN.
  • the MME can also have other deciding manners.
  • the present invention does not limit specific behavior of the MME.
  • the specific manner of using the voLTE or the CSFB to establish bearer for the voice service and the manner of moving to the SRVCC of the UTRAM/GERAN after using the voLTE are the same as the existing technology, and the detailed description of those is omitted here.
  • Step 303 after ht e MME receives the NAS message, the MME performs the NAS authentication/safety process between the MME and the UE.
  • step 303 specifically whether the MME performs and how to perform the NAS authentication/safety process is existing technology, and it will not be repeated here.
  • Step 304 the MME sends an initial context establishment request message to the eNB.
  • the message contains NAS message connection accept.
  • the MME decides whether the system can provide an SRVCC switching for the UE to the UTRAN GERAN according to the following information contained in the NAS information which is received from the UE: whether supporting SRVCC to UTRAN of the UE and whether supporting SRVCC to GERAN of the UE, and whether the MME itself supports the capability of SRVCC to UTRAN and the capability of SRVCC to GERAN.
  • the MME sends the feasibility information of SRVCC to UTRAN and the feasibility information of SRVCC to GERAN in the initial context request message, for example, able or unable.
  • Step 305 after the eNB receives the initial context establishment request message, the eNB establishes a radio bearer between the MME and the UE.
  • the eNB stores the received feasibility information of SRVCC to UTRAN and the received feasibility information of SRVCC to GERAN.
  • the eNB decides whether the UE can be switched to the UTRAN or the GERAN according to the information and the measurement report of the UE. This is described in the step 401.
  • Step 306 after the establishment of the radio bearer between the eNB and the UE, the eNB sends an initial context establishment response message to the MME.
  • Fig. 4 is a flow chart of the eNB deciding the SRVCC switching provided in the present invention. As shown in Fig. 4, the flow can include the following steps:
  • Step 401 the UE receives the voice service through the volte in the LTE.
  • Step 402 the source eNB decides whether initiating a switching for the UE.
  • the source eNB decides whether the UE can be switched to the UTRAN or the GERAN according to the stored feasibility information of SRVCC to UTRAN, the feasibility information of SRVCC to GERAN and the measurement report of the UE.
  • the source eNB can selectively initiate an SRVCC procedure to the UTRAN or an SRVCC procedure to the GERAN. It is not specifically limited here.
  • Step 403 the source eNB initiates corresponding target cell switching procedure according to the UTRAN or the GERAN needed to be switched to.
  • the target cell switching procedure in the step 403 is the same as the existing technology, and the detailed technical descriptions are ignored here.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the embodiment 3 is that the UE sends the IOT information of SRVCC to GSM and the IOT information of SRVCC to UMTS to the base station, the base station sends the received above IOT information to the MME.
  • the MME can set an instruction of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to this information and the capability of SRVCC to UTRAN/GERAN. For example, when the foregoing are support, the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain.
  • the present invention can also consider whether the MME supports the SRVCC when the MME sets whether supporting provision of the IMS voice in the PS domain.
  • the MME refers the IOT information of SRVCC to GSM and the IOT information of SRVCC to UMTS, and the capability of SRVCC to UTRAN/GERAN to decide using the voLTE or the CSFB to provide voice service for the UE.
  • the MME can provide voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support, the IOT information of SRVCC to GSM is no and the IOT information of SRVCC to UMTS is yes, if the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE, if the system only deploys GERAN and does not deploy the UTRAN, then the MME can provide voice service for the UE through the CSFB, if both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support,
  • Fig. 5 is flow chart provided in the embodiment 3 of the present invention. In this flow, the detailed description of steps which have nothing to do with the flow is omitted. As shown in Fig. 5, the flow can include the following steps:
  • Step 501 the UE sends NAS message such as attach message, TA update request message and so on to the eNB.
  • the UE can send the uplink NAS message to the eNB through an uplink information transmission or RRC connection establishing completion.
  • the NAS message includes information about whether SRVCC to GERAN/UTRAN is supported.
  • Step 502 the eNB obtains access layer capacity information of the UE, it specifically is: the eNB sends a UE capability request to the UE, the UE sends UE capability information to the base station.
  • the access layer capacity information can include IOT information of the UE SRVCC to GSM, and the IOT information of the UE SRVCC to UMTS.
  • Step 503 the eNB sends the NAS message sent by the UE to the MME through an S1 access protocol (AP) message.
  • the S1 AP message contains the NAS message, and also contains IOT information of the UE SRVCC to GSM or the IOT information of the UE SRVCC to UMTS.
  • the MME stores the received information.
  • the eNB can also first send the NAS information received from the UE to the MME, and then requests for access layer capacity information of the UE, corresponding to this method, the eNB can send the received IOT information of the UE SRVCC to GSM or the IOT information of the UE SRVCC to UMTS to the MME through another one existing S1AP message or a new message, rather than through the initial UE message of the step 503.
  • the MME can set an instruction of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to the IOT information of the UE SRVCC to GSM or the IOT information of the UE SRVCC to UMTS and the capability of SRVCC to UTRAN/GERAN.
  • the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain.
  • it can also consider whether the MME supports the SRVCC when the MME sets whether supporting provision of the IMS voice in the PS domain.
  • the MME can refer information about the IOT information of SRVCC to GSM, the IOT information of SRVCC to UMTS and whether the capability of the UE SRVCC to UTRAN/GERAN is support, to decide using the voLTE or the CSFB to provide voice service for the UE.
  • the MME can provide voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support, the IOT information of SRVCC to GSM is no and the IOT information of SRVCC to UMTS is yes, if the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE, if the system only deploys GERAN and does not deploy the UTRAN, then the MME can provide voice service for the UE through the CSFB, if both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support,
  • the MME decides using which ways to provide the voice service for the UE according to one of the received capability of SRVCC to UTRAN/GERAN, the IOT information of SRVCC to GSM and the IOT information of SRVCC to UMTS.
  • the MME can also have other deciding manners.
  • the present invention does not limit specific behavior of the MME.
  • Step 504 after the MME receives the NAS message, the MME performs the NAS authentication/safety process between the MME and the UE.
  • step 504 specifically whether performing and how to perform the NAS authentication/safety process is existing technology and it will not be repeated here.
  • Step 505 the MME sends an initial context establishment request message to the eNB.
  • the message contains NAS message connection accept.
  • Step 506 after the eNB receives the initial context establishment request message, the eNB establishes a radio bearer between the MME and the UE.
  • Step 507 after the establishment of the radio bearer between the eNB and the UE, the eNB sends an initial context establishment response message to the MME.
  • the present invention also provides another flow of the eNB deciding the SRVCC switching procedure, of which the details are shown in Fig. 6.
  • Fig. 6 is a flow chart of another flow of the eNB deciding the SRVCC switching procedure provided in the present invention. As shown in Fig. 6, the flow can include the following steps:
  • Step 601 the UE receives the voice service through the voLTE in the LTE.
  • Step 602 the source eNB decides whether initiating a switching for the UE.
  • the source eNB decides whether the UE can be switched to the UTRAN or the GERAN according to the stored feasibility information of SRVCC to GERAN/UTRAN, the IOT information of the access layer SRVCC to GSM, the IOT information of SRVCC to UMTS and the measurement report of the UE.
  • Step 603 the source eNB initiates corresponding target cell switching procedure according to the UTRAN or the GERAN needed to be switched to.
  • the target cell switching procedure in the step 603 is the same as the existing technology, and the detailed technical descriptions are ignored here.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the embodiment 4 is that the UE sends the IOT information of SRVCC to GSM and/or the IOT information of SRVCC to UMTS to the base station (eNB) through RRC connection establishing completion message, the eNB sends the received IOT information to the MME.
  • the MME can set an instruction of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to the received IOT information and the capability of SRVCC to UTRAN/GERAN. For example, when the foregoing are support, the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain.
  • the present invention can also consider whether the MME supports the SRVCC when the MME considers setting whether supporting provision of the IMS voice in the PS domain.
  • Fig. 7 is a flow chart provided in the embodiment 4 of the present invention. In this flow, the detailed description of steps which have nothing to do with the flow is omitted. As shown in Fig. 7, the flow can include the following steps:
  • Step 701 the UE sends an RRC connection request message to the eNB.
  • Step 702 the eNB sends an RRC connection establishing message to the UE.
  • Step 703 the UE sends an RRC connection establishing completion message to the eNB.
  • the RRC connection establishing completion message contains the IOT information of the UE SRVCC to GSM and/or the IOT information of SRVCC to UMTS.
  • Step 704 the UE sends NAS message such as attach message, TA update request message and so on to the eNB.
  • NAS message such as attach message, TA update request message and so on
  • the UE can send uplink NAS message to the eNB through an uplink information transmission.
  • the NAS message can also contained in the process of sending the RRC connection establishing completion message of the step 703, corresponding to this method, the step 704 can be omitted.
  • the NAS message contains information about whether SRVCC to GERAN/UTRAN is supported.
  • Step 705 the eNB sends an S1 AP message to the MME.
  • the S1 AP message contains the NAS message, and also contains the received IOT information of the UE SRVCC to GSM or the IOT information of the UE SRVCC to UMTS.
  • the MME stores the received information.
  • the MME can set an instruction of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to the IOT information of the UE SRVCC to GSM and/or the IOT information of the UE SRVCC to UMTS and the obtained capability of SRVCC to UTRAN/GERAN.
  • the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain.
  • it can also consider whether the MME supports the SRVCC when the MME sets whether supporting provision of the IMS voice in the PS domain.
  • the MME can refer information about the IOT information of SRVCC to GSM, the IOT information of SRVCC to UMTS and whether the capability of the UE SRVCC to UTRAN/GERAN is support, to decide using the voLTE or the CSFB to provide voice service for the UE.
  • the MME can provide voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support, the IOT information of SRVCC to GSM is no and the IOT information of SRVCC to UMTS is yes, if the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE, if the system only deploys GERAN and does not deploy the UTRAN, then the MME can provide voice service for the UE through the CSFB, if both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support,
  • the MME decides using which ways to provide the voice service for the UE according to one of the received capability of SRVCC to UTRAN/GERAN, the IOT information of SRVCC to GSM and the IOT information of SRVCC to UMTS.
  • the MME can also have other deciding manners.
  • the present invention does not limit specific behavior of the MME.
  • Step 706 to step 709 are the same as the step 504 to step 507, respectively, and it will not be repeated here.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the embodiment 5 is that the MME sends a message to the eNB to request for access layer capability of the UE; preferably, in the embodiment 5, the MME can send the message to the eNB to request for access layer capability of the UE after receiving the NAS message, the message sent by the MME can be S1 message; then, the eNB sends the obtained IOT information of the UE SRVCC to GSM and/or the IOT information of the UE SRVCC to UMTS to the MME; the MME can set an indication of whether supporting provision of the IMS voice in the PS domain according to the IOT information sent by the eNB.
  • the MME can set an indication of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to the IOT information sent by the eNB and the capability of SRVCC to UTRAN/GERAN. For example, when the foregoing are support, the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain. Of course, as an extension of the embodiment of the present invention, there are also other setting manners which do not affect the main content of the present invention. Preferably, in the present invention, it can also consider whether the MME supports the SRVCC when the MME considers setting whether supporting provision of the IMS voice in the PS domain.
  • the MME may not request for the access layer capability of the UE every time receiving the NAS message.
  • the access layer capability of the UE is requested only when the UE supports the SRVCC (indicated by the NAS layer) or the capability of the UE SRVCC to UTRAN/GERAN is support, or the access layer capability of the UE is requested only when the UE supports the SRVCC or the capability of the UE SRVCC to UTRAN/GERAN is support and the MME supports the SRVCC.
  • Fig. 8 is a flow chart provided in the embodiment 5 of the present invention. In this flow, the detailed description of steps which have nothing to do with the flow is omitted. As shown in Fig. 8, the flow can include the following steps:
  • Step 801 the UE sends NAS message such as attach message, TA update request message and so on to the eNB.
  • the UE can send the uplink NAS message to the eNB through an uplink information transmission or RRC connection establishing completion.
  • the NAS message includes information about whether SRVCC to GERAN/UTRAN is supported.
  • Step 802 the eNB sends the NAS message sent by the UE to the MME through an S1 AP message.
  • Step 803 after the MME receives the NAS message, the MME performs the NAS authentication/safety process between the MME and the UE.
  • step 803 specifically whether performing and how to perform the NAS authentication/safety process are existing technology and it will not be repeated here.
  • Step 804 the MME sends the access layer capability request message of the UE to the eNB.
  • the MME may not request for the capability of the UE every time receiving the NAS message. For example, the capability of the UE is requested only when the UE supports the SRVCC or the capability of SRVCC to UTRAN/GERAN is support, or the access layer capability of the UE is requested only when the UE supports the SRVCC or the capability of SRVCC to UTRAN/GERAN is support and the MME supports the SRVCC.
  • Step 805 the eNB obtains access layer capability information of the UE, it specifically is: the eNB sends a UE capability request to the UE, the UE sends UE access layer capability information to the base station.
  • the access layer capability information of the UE can include IOT information of the UE SRVCC to GSM and/or the IOT information of the UE SRVCC to UMTS.
  • Step 806 the eNB sends the access layer capability information of the UE to the MME.
  • the access layer capability information of the UE contains the IOT information of the UE SRVCC to GSM and/or the IOT information of the UE SRVCC to UMTS.
  • steps 804 to 806 there is no absolute sequence between the steps 804 to 806 and the step 803.
  • the steps 804 to 806 can be first performed, and then the step 803 is performed. If the step 804 is first performed, it is not necessary to perform the step 803 after receiving the response message of the step 806. The step 803 can be performed after the sending of the step 804.
  • the MME stores the received information and can set an indication of whether supporting provision of the IMS voice in the PS domain in the attach accept message according to the IOT information of the UE SRVCC to GSM and/or the IOT information of the UE SRVCC to UMTS and the capability of SRVCC to UTRAN/GERAN.
  • the MME can set supporting provision of the IMS voice service in the PS domain, or when one of the foregoing is support, the MME can set supporting provision of the IMS voice service in the PS domain.
  • it can also consider whether the MME supports the SRVCC when the MME sets whether supporting provision of the IMS voice in the PS domain.
  • the MME can refer information about the IOT information of SRVCC to GSM, the IOT information of SRVCC to UMTS and whether the capability of the UE SRVCC to UTRAN/GERAN is support, to decide using the voLTE or the CSFB to provide voice service for the UE.
  • the MME can provide voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support, the IOT information of SRVCC to GSM is no and the IOT information of SRVCC to UMTS is yes, if the system deploys the UTRAN equipment (the MME can know according to the configuration), the MME can provide voice service for the UE through the voLTE, if the system only deploys GERAN and does not deploy the UTRAN, then the MME can provide voice service for the UE through the CSFB, if both of the UTRAN and the GERAN are not in the current position of the UE, the MME provides the voice service for the UE through the voLTE; when the capability of SRVCC to UTRAN/GERAN is support,
  • the MME decides using which ways to provide the voice service for the UE according to one of the received capability of SRVCC to UTRAN/GERAN, the IOT information of SRVCC to GSM and the IOT information of SRVCC to UMTS.
  • the MME can also have other deciding manners.
  • the present invention does not limit specific behaviour of the MME.
  • Step 807 to step 809 are the same as the step 505 to step 507, respectively, and it will not be repeated here.
  • each of the UE, the MME, and the eNB may includes a receiver, a controller, and a transmitter. It will be assumed that the receiver, the controller, and the transmitter included in each of the UE, the MME, and the eNB(or BS) may be implemented as separate units, however it is possible that the receiver, the controller, and the transmitter included in each of the UE, the MME, and the eNB(or BS) may be incorporated into a single unit.

Landscapes

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

Abstract

La présente invention concerne un procédé destiné à favoriser la continuité d'un service vocal. L'un des procédés consiste à faire en sorte : A. qu'un équipement utilisateur (UE) envoie des informations indiquant s'il prend en charge une capacité SRVCC sur un réseau UTRAN et/ou des informations indiquant s'il peut prendre en charge une capacité SRVCC sur un réseau GERAN à destination d'une entité de gestion de mobilité (MME) ; B. que l'entité MME configure correctement une instruction indiquant s'il est possible de prendre en charge la fourniture d'un signal vocal IMS dans un domaine PS conformément aux informations envoyées par l'UE.
PCT/KR2012/007931 2011-09-29 2012-09-28 Procédé destiné à favoriser la continuité d'un service vocal WO2013048189A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201110304871 2011-09-29
CN201110304871.9 2011-09-29
CN201110352771.3 2011-11-04
CN2011103527713A CN103037452A (zh) 2011-09-29 2011-11-04 支持话音业务连续性的方法

Publications (2)

Publication Number Publication Date
WO2013048189A2 true WO2013048189A2 (fr) 2013-04-04
WO2013048189A3 WO2013048189A3 (fr) 2013-05-23

Family

ID=47996649

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/007931 WO2013048189A2 (fr) 2011-09-29 2012-09-28 Procédé destiné à favoriser la continuité d'un service vocal

Country Status (2)

Country Link
CN (1) CN103037452A (fr)
WO (1) WO2013048189A2 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103281757A (zh) * 2013-06-08 2013-09-04 华为终端有限公司 通信方法及装置
US9338718B2 (en) 2013-03-14 2016-05-10 Apple Inc. Voice call resumption on a legacy network
EP3105970A4 (fr) * 2014-02-10 2017-09-13 Samsung Electronics Co., Ltd. Procédé et appareil de contrôle de l'accès à un réseau selon les capacités d'un équipement utilisateur et des informations d'abonnement
WO2018065936A1 (fr) * 2016-10-07 2018-04-12 Telefonaktiebolaget Lm Ericsson (Publ) Prise en charge de continuité d'appel radio vocal unique dans des réseaux de la prochaine génération (5g)
US20190007936A1 (en) * 2016-03-09 2019-01-03 Huawei Technologies Co., Ltd. Voice service processing method and apparatus
US10462192B2 (en) 2014-09-10 2019-10-29 Apple Inc. Radio resource management for packet-switched voice communication
CN114449032A (zh) * 2016-01-11 2022-05-06 北京三星通信技术研究有限公司 决定iot业务方法和设备、iot业务行为控制方法和设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105636130B (zh) * 2015-04-30 2019-08-02 南京酷派软件技术有限公司 语音电话回落的方法及系统、服务器和移动终端
CN105392159B (zh) * 2015-11-02 2018-11-09 中国联合网络通信集团有限公司 确定终端语音策略的方法及装置
CN105451261A (zh) * 2015-12-02 2016-03-30 北京泰合佳通信息技术有限公司 一种基于移动智能终端的VoLTE无线网络测试方法
CN107548148A (zh) * 2016-06-24 2018-01-05 展讯通信（上海）有限公司 VoWiFi业务接入处理方法、装置及移动终端
CN108271192B (zh) * 2016-12-31 2021-03-23 中国移动通信集团吉林有限公司 一种VoLTE异常场景定位方法及移动性管理实体
CN109429212A (zh) * 2017-08-25 2019-03-05 中兴通讯股份有限公司 确定ue语音策略的方法、相应设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060009253A1 (en) * 2004-06-10 2006-01-12 Nokia Corporation Intersystem cell reselection from GERAN to UTRAN
WO2010084416A1 (fr) * 2009-01-22 2010-07-29 Telefonaktiebolaget L M Ericsson (Publ) Indicateur de solution de mobilité pour voix sur eps (evolved packet system)
WO2010122029A1 (fr) * 2009-04-23 2010-10-28 Telefonaktiebolaget L M Ericsson (Publ) Indicateur de transfert ps à cs

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060009253A1 (en) * 2004-06-10 2006-01-12 Nokia Corporation Intersystem cell reselection from GERAN to UTRAN
WO2010084416A1 (fr) * 2009-01-22 2010-07-29 Telefonaktiebolaget L M Ericsson (Publ) Indicateur de solution de mobilité pour voix sur eps (evolved packet system)
WO2010122029A1 (fr) * 2009-04-23 2010-10-28 Telefonaktiebolaget L M Ericsson (Publ) Indicateur de transfert ps à cs

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9338718B2 (en) 2013-03-14 2016-05-10 Apple Inc. Voice call resumption on a legacy network
CN103281757A (zh) * 2013-06-08 2013-09-04 华为终端有限公司 通信方法及装置
EP3105970A4 (fr) * 2014-02-10 2017-09-13 Samsung Electronics Co., Ltd. Procédé et appareil de contrôle de l'accès à un réseau selon les capacités d'un équipement utilisateur et des informations d'abonnement
US9872179B2 (en) 2014-02-10 2018-01-16 Samsung Electronics Co., Ltd Method and apparatus for controlling network access according to UE capability and subscription information
US10462192B2 (en) 2014-09-10 2019-10-29 Apple Inc. Radio resource management for packet-switched voice communication
CN114449032A (zh) * 2016-01-11 2022-05-06 北京三星通信技术研究有限公司 决定iot业务方法和设备、iot业务行为控制方法和设备
CN114449032B (zh) * 2016-01-11 2024-05-14 北京三星通信技术研究有限公司 决定iot业务方法和设备、iot业务行为控制方法和设备
US20190007936A1 (en) * 2016-03-09 2019-01-03 Huawei Technologies Co., Ltd. Voice service processing method and apparatus
US10966208B2 (en) * 2016-03-09 2021-03-30 Huawei Technolgies Co., Ltd. Voice service processing method and apparatus
WO2018065936A1 (fr) * 2016-10-07 2018-04-12 Telefonaktiebolaget Lm Ericsson (Publ) Prise en charge de continuité d'appel radio vocal unique dans des réseaux de la prochaine génération (5g)
EP3524008B1 (fr) * 2016-10-07 2022-05-04 Telefonaktiebolaget LM Ericsson (publ) Prise en charge de continuité d'appel radio vocal unique dans des réseaux de la prochaine génération (5g)

Also Published As

Publication number Publication date
CN103037452A (zh) 2013-04-10
WO2013048189A3 (fr) 2013-05-23

Similar Documents

Publication Publication Date Title
WO2013048189A2 (fr) Procédé destiné à favoriser la continuité d'un service vocal
WO2010050758A2 (fr) Procédé et système d'envoi de données pour un transfert vertical
WO2019160376A1 (fr) Procédé d'émission et de réception de signal par smf dans un système de communication sans fil et dispositif associé
WO2011136529A2 (fr) Appareil et procédé de prise en charge de resélection de nœud de passerelle dans un système de communication
WO2015115761A1 (fr) Procédé et appareil pour une mobilité d'ue dans un système de petite cellule
WO2013022167A1 (fr) Procédé de fourniture d'un service de repli cs pour distribution de charge, et dispositif de station de base et terminal mobile pour le procédé
WO2014104705A1 (fr) Procédé et système pour assister une reprise rapide d'un équipement utilisateur
WO2012093905A2 (fr) Procédé et appareil pour prendre en charge la mobilité d'équipements d'utilisateurs dans un système de communications sans fil
WO2013018970A1 (fr) Procédé de sélection de cellule pour un service de secours de commutation de circuits
WO2013168937A1 (fr) Procédé et appareil prenant en charge la détection de la cause d'une défaillance rlf ou la détection de la cause d'une défaillance de transfert
WO2016111603A1 (fr) Procédé de transmission et de réception de signaux associés à une récupération de connexion pdn dans un système de communication sans fil, et dispositif associé
WO2015037947A1 (fr) Procédé et dispositif pour paramétrer des supports de dérivation locaux
WO2011090339A2 (fr) Regroupement de messages 1x
WO2015126160A1 (fr) Appareil et procédé d'amélioration de la qualité de service de visiotéléphonie
WO2017026872A1 (fr) Procédé de transmission et de réception de signal par ue à distance dans un système de communication sans fil et dispositif associé
WO2018221943A1 (fr) Procédé d'émission-réception de signal en association avec un ajout de psa multiconnexion dans un système de communication sans fil, et appareil associé
EP2745432A2 (fr) Procédé et appareil pour la prise en charge efficace de plusieurs bandes de fréquences dans un système de communication mobile
WO2017026772A1 (fr) Procédé servant à sélectionner une fonction de commande de session d'appel de mandataire (p-cscf) et à transmettre un message de protocole d'initiation de session (sip) dans un système de communication sans fil et dispositif associé
WO2015020366A1 (fr) Procédés, systèmes et dispositifs de prise en charge de décrochage local dans une architecture de petite cellule
WO2018009025A1 (fr) Procédé permettant de transmettre et de recevoir des signaux se rapportant à une connexion au réseau de données par paquets (pdn) dans un système de communication sans fil et dispositif s'y rapportant
WO2013005992A2 (fr) Procédé permettant d'éviter l'échec du transfert intercellulaire
WO2021261843A1 (fr) Procédés et systèmes de gestion d'appel vocal sur une nouvelle radio par un équipement utilisateur
WO2013151332A1 (fr) Procédé et appareil pour un transfert de service à commutation de paquets dans des systèmes de communication sans fil
EP3420752A1 (fr) Procédé et dispositif de repli par commutation de circuits
WO2013009093A2 (fr) Signalisation perfectionnée dans un réseau sans fil

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12837112

Country of ref document: EP

Kind code of ref document: A2