WO2019196012A1 - Continuité d'appel vocal radio unique pour réseaux sans fil 5g - Google Patents

Continuité d'appel vocal radio unique pour réseaux sans fil 5g Download PDF

Info

Publication number
WO2019196012A1
WO2019196012A1 PCT/CN2018/082527 CN2018082527W WO2019196012A1 WO 2019196012 A1 WO2019196012 A1 WO 2019196012A1 CN 2018082527 W CN2018082527 W CN 2018082527W WO 2019196012 A1 WO2019196012 A1 WO 2019196012A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
request
communication operations
communication
target
Prior art date
Application number
PCT/CN2018/082527
Other languages
English (en)
Inventor
Zhendong Li
Fei Lu
Original Assignee
Zte Corporation
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 Zte Corporation filed Critical Zte Corporation
Priority to CN201880092184.5A priority Critical patent/CN111955028B/zh
Priority to PCT/CN2018/082527 priority patent/WO2019196012A1/fr
Publication of WO2019196012A1 publication Critical patent/WO2019196012A1/fr

Links

Images

Classifications

    • 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/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H04W36/00226—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB] wherein the core network technologies comprise IP multimedia system [IMS], e.g. single radio voice call continuity [SRVCC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks

Definitions

  • This document is directed generally to wireless communications.
  • Wireless communication technologies are moving the world toward an increasingly connected and networked society.
  • the rapid growth of wireless communications and advances in technology has led to greater demand for capacity and connectivity.
  • Other aspects, such as energy consumption, device cost, spectral efficiency, and latency are also important to meeting the needs of various communication scenarios.
  • next generation systems and wireless communication techniques need to provide compatibility between existing systems and new emerging networked systems.
  • This document relates to methods, systems, and devices for single radio voice call continuity (SRVCC) for 5G wireless networks.
  • SSVCC single radio voice call continuity
  • embodiments are able to maintain voice call and Internet Protocol (IP) continuity when switching services from older generation 2G or 3G networks to emerging 5G (e.g. New Radio (NR) ) implementations.
  • IP Internet Protocol
  • a wireless communication method includes transmitting, upon determining that a voice service in a first network has terminated, a request to join a second network, where the request includes an identifier associated with the second network that is mapped from an identifier associated with a third network, and where the mapping indicates that the wireless device is joining the second network from the third network, and performing a first set of communication operations in the second network using Internet Protocol (IP) information that was used to perform a second set of communication operations in the third network, and where the second set of communication operations were performed prior to performing the voice service in the first network.
  • IP Internet Protocol
  • a wireless communication method includes transmitting, upon determining that a voice service in a first network has terminated, a request to join a second network, where the request includes a mobility registration type, and performing a first set of communication operations in the second network using Internet Protocol (IP) information that was used to perform a second set of communication operations in the second network, and where the second set of communication operations were performed prior to performing the voice service in the first network.
  • IP Internet Protocol
  • a wireless communication method includes performing a first set of communication operations in a first network using Internet Protocol (IP) information, transmitting a suspend command for each of the first set of communication operations, performing, subsequent to transmitting the suspend command, a second set of communication operations in a second network, and performing a third set of communication operations in the first network using the IP information.
  • IP Internet Protocol
  • the above-described methods are embodied in the form of processor-executable code and stored in a computer-readable program medium.
  • a device that is configured or operable to perform the above-described methods is disclosed.
  • FIG. 1 shows an example of a base station (BS) and user equipment (UE) in wireless communication, in accordance with some embodiments of the presently disclosed technology.
  • BS base station
  • UE user equipment
  • FIGS. 2A and 2B show an example of SRVCC from a 4G network to a 2G network.
  • FIG. 3 shows an example of SRVCC from a 5G network to a 2G/3G network.
  • FIGS. 4A and 4B show examples of maintaining voice call and IP continuity when switching from a 2G/3G network to a 5G network.
  • FIG. 5 shows an example of releasing resources after 5G SRVCC.
  • FIG. 6 shows an example of maintaining voice call and IP continuity when switching from a 2G/3G network to a 4G network.
  • FIG. 7 shows another example of maintaining voice call and IP continuity when switching from a 2G/3G network to a 5G network.
  • FIG. 8 shows an example of a wireless communication method for SRVCC for 5G.
  • FIG. 9 shows another example of another wireless communication method for SRVCC for 5G wireless networks.
  • FIG. 10 shows yet another example of yet another wireless communication method for SRVCC for 5G wireless networks.
  • FIG. 11 is a block diagram representation of a portion of an apparatus, in accordance with some embodiments of the presently disclosed technology.
  • FIG. 1 shows an example of a wireless communication system that includes a BS 120 and one or more user equipment (UE) 111, 112 and 113.
  • the UEs may transmit a request or other command (131, 132, 133) to the BS, which allows it to maintain its IP address for subsequent communication (141, 142, 143) from the BS to the UEs.
  • the UE may be, for example, a smartphone, a tablet, a mobile computer, a machine to machine (M2M) device, an Internet of Things (IoT) device, and so on.
  • M2M machine to machine
  • IoT Internet of Things
  • the UE may perform the A/Gb mode GPRS Attach procedure or the Iu mode GPRS Attach procedure. And upon mobility from GERAN/UTRAN to a 5G system (e.g. upon selecting an NG-RAN cell) , the UE shall perform the Registration procedure using an “initial registration” type.
  • the UE when the UE is registered in a 5G system (5GS) , it may establish one or more Packet Data Unit (PDU) sessions. When it moves to a 2G/3G system, it perform the A/Gb mode GPRS Attach procedure or Iu mode GPRS Attach procedure. Due to no interworking between the two networks, there is no IP continuity. The UE typically receives a new IP address to connect to the data network. After the UE returns to the 5G network, it performs the “initial registration” procedure. This results in the 5G network assigning a new Access and Mobility Function (AMF) to the UE, and all the previously created PDU sessions are lost.
  • AMF Access and Mobility Function
  • FIGS. 2A and 2B show an example of SRVCC from E-UTRAN (4G network) to GERAN (2G network) without Dual Transfer Mode (DTM) support.
  • DTM support is part of a special handover type in which the source base station system (BSS) requests the target BSS to allocate both circuit-switched (CS) and packet-switched resources for a particular UE.
  • BSS source base station system
  • step (1) the UE sends measurement reports to E-UTRAN.
  • step (2) and based on the UE measurement reports the source E-UTRAN decides to trigger an SRVCC handover to GERAN.
  • step (3) the source E-UTRAN sends a Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO Indication) message to the source Mobile Management Entity (MME) .
  • the E-UTRAN places the ‘old BSS to new BSS information IE” for the CS domain in the generic Source to Target Transparent Container.
  • the SRVCC HO indication indicates to the MME that the target is only CS-capable, hence FIGS. 2A and 2B are an example of a SRVCC handover operation only toward the CS domain.
  • the message includes an indication that the UE is not available for the packet-switched (PS) service in the target cell.
  • PS packet-switched
  • step (4) and based on the QoS Class Indicator (QCI) associated with the voice bearer (QCI 1) and the SRVCC HO indication, the source MME splits the voice bearer from the non-voice bearers and initiates the PS-CS handover procedure for the voice bearer only towards Mobile Switching Center (MSC) Server.
  • QCI QoS Class Indicator
  • MSC Mobile Switching Center
  • the MME sends a SRVCC PS-to-CS Request (IMSI, Target ID, STN-SR, C-MSISDN, generic Source to Target Transparent Container, MM Context, Emergency Indication) message to the MSC Server.
  • SRVCC PS-to-CS Request IMSI, Target ID, STN-SR, C-MSISDN, generic Source to Target Transparent Container, MM Context, Emergency Indication
  • the MME also includes priority indication in SRVCC PS-to-CS Request if it detects the SRVCC requires priority handling. The detection is based on the ARP associated with the EPS bearer used for IMS signaling. The priority indication corresponds to the ARP information element.
  • the Emergency Indication and the equipment identifier are included if the ongoing session is emergency session. Authenticated IMSI and C-MSISDN shall also be included, if available.
  • the MME received STN-SR and C-MSISDN from the HSS as part of the subscription profile downloaded during the E-UTRAN attach procedure.
  • the MM Context contains security related information.
  • the CS security key may be derived by the MME from the E-UTRAN/EPS domain key, and may be sent in the MM Context.
  • the MSC Server interworks the PS-CS handover request with a CS inter-MSC handover request by sending a Prepare Handover Request message to the target MSC.
  • the MSC Server receives the priority indication (e.g. ARP) in the SRVCC PS-to-CS Request
  • the MSC server/MGW sends Prepare Handover Request message to the Target MSC with priority indication mapped from the ARP.
  • the MSC Server maps the ARP to the priority level, pre-emption capability/vulnerability for CS services based on local regulation or operator settings.
  • the priority indication indicates the CS call priority during handover for GSM/EDGE.
  • the MSC Server assigns a default SAI as Source ID on the interface to the target BSS and uses BSSMAP encapsulated for the Prepare Handover Request.
  • the value of the default SAI is configured in the MSC and allows the BSC to identify that the source for the SRVCC Handover is E-UTRAN. To ensure correct statistics in the target BSS the default SAI should be different from the SAIs used in UTRAN.
  • step (7) the target MSC performs resource allocation with the target BSS by exchanging Handover Request/Acknowledge messages. If the MSC Server indicated priority, the target BSS allocates the radio resource based on the existing procedures with priority indication.
  • step (8) the target MSC sends a Prepare Handover Response message to the MSC Server.
  • step (9) the circuit connection between the target MSC and the MGW associated with the MSC Server e.g. using ISUP IAM and ACM messages, is established.
  • the MSC Server initiates the Session Transfer by using the STN-SR e.g. by sending an ISUP IAM (STN-SR) message towards the IMS.
  • STN-SR ISUP IAM
  • the MSC Server includes priority indication to the IMS and the IMS entity handles the session transfer procedure with priority.
  • the priority indication in the Session Transfer is mapped by the MSC Server from the priority indication (e.g. ARP) in the SRVCC PS to CS Request received in step (5) .
  • the mapping of the priority level is based on operator policy and/or local configuration, and the IMS priority indicator should be the same as for the original IMS created over PS.
  • the MSC Server initiates the Session Transfer by using the locally configured E-STN-SR and by including the equipment identifier.
  • IMS Service Continuity or Emergency IMS Service Continuity procedures are applied for execution of the Session Transfer.
  • step (10) may be started after step (8) .
  • the initiation of the session transfer for non-emergency session may fail if the subscriber profile including Customized Applications for Mobile network Enhanced Logic (CAMEL) triggers is not available prior to the handover, and may also fail if CAMEL triggers are available and local anchor transfer function is used. If the subscriber profile is available prior handover then CAMEL triggers others than those used in a specific set are not used during the transfer.
  • CAMEL Customized Applications for Mobile network Enhanced Logic
  • step (11) during the execution of the Session Transfer procedure the remote end is updated with the SDP of the CS access leg.
  • the downlink flow of VoIP packets is switched towards the CS access leg at this point.
  • step (12) the source IMS leg is released.
  • steps (11) and (12) are independent of step (13) .
  • step (13) the MSC Server sends a SRVCC PS-to-CS Response (Target to Source Transparent Container) message to the source MME.
  • SRVCC PS-to-CS Response Target to Source Transparent Container
  • step (14) the source MME sends a Handover Command (Target to Source Transparent Container) message to the source E-UTRAN.
  • the message includes information about the voice component only.
  • step (15) the source E-UTRAN sends a Handover from E-UTRAN Command message to the UE.
  • step (16) the UE tunes to GERAN.
  • step (17) the Handover Detection at the target BSS occurs, then the target BSS sends Handover Detection message to the target MSC.
  • the target MSC can send/receive voice data.
  • the UE sends a Handover Complete message via the target BSS to the target MSC. If the target MSC is not the MSC Server, then the Target MSC sends an SES (Handover Complete) message to the MSC Server.
  • step (18) the UE starts a Suspend procedure and the TLLI and RAI pair are derived from the GUTI. This triggers the Target SGSN to send a Suspend Notification message to the Source MME. The MME returns a Suspend Acknowledge to the Target SGSN.
  • step (18) may take place in parallel with steps (19) - (22) .
  • the MME might not be able to derive the GUTI from the received P-TMSI and RAI pair and therefore it might not be able to identify which UE context is associated with the Suspend Notification message. Also in this case the bearers are deactivated and/or suspended as in step (22a) .
  • step (19) the target BSS sends a Handover Complete message to the target MSC.
  • this step may take place immediately after Handover Detection at the target BSS occurs in step (17) , before the BSS has received a Suspend message from the UE.
  • step (20) the target MSC sends an SES (Handover Complete) message to the MSC Server.
  • the speech circuit is through connected in the MSC Server/MGW.
  • step (21) the establishment procedure is completed with an ISUP Answer message to the MSC Server.
  • step (22) the MSC Server sends a SRVCC PS-to-CS Complete Notification message to the source MME, informing it that the UE has arrived on the target side.
  • Source MME acknowledges the information by sending a SRVCC PS-to-CS Complete Acknowledge message to the MSC Server.
  • step (22a) the MME deactivates bearers used for voice and other GBR bearers. All GBR bearers are deactivated towards S-GW and P-GW by initiating a MME-initiated Dedicated Bearer Deactivation procedure. The PS-to-CS handover indicator is notified to P-GW for voice bearer during the bearer deactivation procedure.
  • the S-GW requests the P-GW to delete all GBR bearer contexts by sending a Delete Bearer Command message. If dynamic PCC is deployed, the P-GW may interact with PCRF. For PMIP-based S5/S8, S-GW interacts with the PCRF which in turn updates PCC rules for GBR traffic in the P-GW.
  • the MME starts preservation and suspension of non-GBR bearers by sending Suspend Notification message towards S-GW.
  • the S-GW releases S1-U bearers for the UE and sends Suspend Notification message to the P-GW (s) .
  • the MME stores in the UE context that UE is in suspended status.
  • the preserved non-GBR bearers are marked as suspended status in the S-GW and P-GW.
  • the P-GW may discard packets if received for the suspended UE.
  • step (22b) the source MME requests the release of the resources, including release of the S1 signalling connection, to the Source eNodeB.
  • the Source eNodeB releases its resources related to the UE and responds back to the MME.
  • step (23a) for non-emergency sessions and if the HLR is to be updated, e.g. if the IMSI is authenticated but unknown in the VLR, the MSC Server performs a TMSI reallocation towards the UE using its own non-broadcast LAI and, if the MSC Server and other MSC/VLRs serve the same (target) LAI, with its own Network Resource Identifier (NRI) .
  • NNI Network Resource Identifier
  • the TMSI reallocation is performed by the MSC Server towards the UE via target MSC.
  • the HLR will not be updated for emergency services sessions, and TMSI reallocation may be performed based on IMSI presence.
  • step (23b) for non-emergency sessions and if the MSC Server performed a TMSI reallocation in step (23a) , and if this TMSI reallocation was completed successfully, the MSC Server performs a MAP Update Location to the HSS/HLR.
  • this Update Location is not initiated by the UE.
  • the source MME or the MSC Server may send a Subscriber Location Report carrying the identity of the MSC Server to a GMLC associated with the source or target side, respectively, to support location continuity.
  • any configuration of the choice between a source MME versus MSC Server update to a GMLC needs to ensure that a single update occurs from one of these entities when the control plane location solution is used on the source and/or target sides.
  • SRVCC from E-UTRAN (4G network) to UTRAN (3G network) without DTM support is similar to the procedure described in the context of FIGS. 2A and 2B.
  • Some exceptions in the procedure include the Suspend procedure (step (18) and step (22a) in FIG. 2B) is not performed and that the MME only deactivates bearers used for voice (step (22a) in FIG. 2B) and sets the PS-to-CS handover indicator.
  • the E-UTRAN places in the generic Source to Target Transparent Container the “old BSS to new BSS information IE” , while if the target is UTRAN, the generic Source to Target Transparent container is encoded according to the Source RNC to Target RNC Transparent Container IE definition.
  • the remaining PS resources are re-established when the UE performs the Routing Area update procedure.
  • the PS service can be re-established in 2/3G because the P-GW are shared among 2/3G and 4G.
  • FIG. 3 includes multiple steps that are similar to those described in the context of FIGS. 2A and 2B.
  • Step (305) in FIG. 3 is the same to steps (6) to (9) in FIG. 2A.
  • the eMSC and target MSC are shown separately.
  • the 5G-CS-IWF may collocate with MME, AMF or SMF.
  • the method shown in FIG. 3 include step (300) , where the UE registers in the 5GS and establishes PDU session for IMS.
  • the 5GS has allocated 5G GUTI to UE.
  • the UE perform IMS registration and have at least one IMS voice session.
  • the source 5G RAN sends Handover Required (Target ID, generic Source to Target Transparent Container, SRVCC HO Indication) message to the source AMF.
  • the 5G RAN places the “old RNC/BSS to new RNC/BSS information IE” for the CS domain in the generic Source to Target Transparent Container.
  • the SRVCC HO indication indicates to the AMF that target is only CS capable, hence this is a SRVCC handover operation only towards the CS domain.
  • the message includes an indication that the UE is not available for the PS service in the target cell.
  • step (302) the AMF requests SMF the SM context for PS-to-CS handover.
  • step (303) the AMF send PS-to-CS handover request to 5G-CS-IWF.
  • step (304) the 5G-CS-IWF sends a SRVCC PS-to-CS Request (generic Source to Target Transparent Container, MM Context, etc. ) message to the eMSC Server.
  • SRVCC PS-to-CS Request Generic Source to Target Transparent Container, MM Context, etc.
  • step (305) the eMSC reserve the resource in the target system. If target is the 2G, it reserve the radio resource with BSS. If target is the 3G, it reserve the radio resource with RNS.
  • FIG. 3 does not show the interaction between eMSC and target MSC for simplification.
  • step (306) the eMSC sends a 5G SRVCC PS to CS Response (Target to Source Transparent Container) message to 5G-CS-IWF.
  • step (307) the 5G-CS-IWF sends a 5G SRVCC PS to CS Response (Target to Source Transparent Container) message to source AMF.
  • step (308) the eMSC Server initiates the Session Transfer towards the IMS.
  • the IMS updates the remote call leg.
  • step (309) the source AMF sends a Handover Command (Target to Source Transparent Container) message to the 5G RAN.
  • the 5G RAN sends a Handover Command message to the UE.
  • step (310) the UE tunes to 2/3G. Handover Detection at the target BSS/RNS occurs, then the target BSS/RNS sends Handover Detection message to the target MSC. At this stage, the target MSC can send/receive voice data. The UE sends a Handover Complete message via the target BSS/RNS to the target MSC. If the target MSC is not the eMSC Server, then the Target MSC sends an SES (Handover Complete) message to the eMSC Server.
  • SES Handover Complete
  • step (311) the MSC Server sends a SRVCC PS-to-CS Complete Notification message to the 5G-CS-IWF.
  • step (312) the 5G-CS-IWF sends a SRVCC PS-to-CS Complete Notification message to source AMF.
  • step (313) after the CS voice completes, the UE may initiate the Location Update procedure.
  • the UE uses CS voice in the 2G/3G network, and on its termination, needs to return to the 5G network.
  • FIG. 4A shows an example of maintaining voice call and IP continuity when switching from a 2G/3G network to a 5G network.
  • the UE keeps the 5G UE context, and releases all the GBR QoS flows and preserves the non-GBR QoS flows locally for each PDU session.
  • the AMF receives PS-to-CS handover Complete, and the AMF sends an N2 UE Context Release Command 5G RAN.
  • the AMF sends an N2 UE Context Release Command 5G RAN.
  • the 5G RAN confirms the N2 Release by returning an N2 UE Context Release Complete (List of PDU Session ID (s) with active N3 user plane) message to the AMF.
  • N2 UE Context Release Complete List of PDU Session ID (s) with active N3 user plane
  • the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, PDU Session Deactivation, Cause, Operation Type) .
  • the Nsmf_PDUSession_UpdateSMContext Request that suspends the PDU session may be invoked by the AMF after step (1) .
  • the AMF may invoke the suspension of the PDU sessions after receiving PS-to-CS handover Complete by sending the necessary commands to the SMF.
  • step (5) the SMF release CN Tunnel. And the SMF release all the GBR QoS flows and preserve the non-GBR QoS flows according to the Cause in the request in step (4) .
  • the SMF sends Nsmf_PDUSession_UpdateSMContext Response to AMF for step (3) .
  • FIG. 4B shows another example of maintaining voice call and IP continuity when switching from a 2G/3G network to a 5G network, and includes steps that are similar to those shown in FIG. 4A, and which are not explicitly described in the context of this embodiment.
  • the UE keeps the 5G UE context, and releases all the GBR QoS flows and preserves the non-GBR QoS flows locally for each PDU session, and at step (1) , the AMF receives PS-to-CS handover Complete.
  • the AMF transmits a suspend command to the SMF, which responds with a corresponding acknowledgement at step (5) .
  • the MSC inform the RNS/BSS to release the radio with PLMN information, as shown in FIG. 5.
  • the RNS/BSS redirection is for the UE to EPS/5GS.
  • the UE has a voice call with the remote end in the CS domain.
  • step (2) the voice call is terminated.
  • the MSC requests RNS/BSS release of an RR connection that was established for SRVCC.
  • the RNS/BSS release the radio resource and redirects the UE to EPS/5GS.
  • FIG. 6 shows the procedure that is followed, and if the UE is directed to 5GS, FIG. 7 shows the corresponding procedure.
  • FIG. 6 shows an example of maintaining voice call and IP continuity when switching from a 2G/3G network to a 4G network.
  • the UE receives the RRC release (with optional redirection information) , and the UE accesses the 4G system.
  • the UE send TAU request to MME via eNB.
  • the UE includes EPS GUTI that is mapped from 5G-GUTI as old Native GUTI and indicates that it is moving from 5GC.
  • the MME sends the Context Request to AMF for UE context.
  • the AMF verifies the integrity of the TAU request message. For each PDU session the UE has in the 5GS, the AMF requests the SMF+PGW-C to provide SM Context.
  • the AMF responses the MME with the UE context.
  • the MME sends the Create Session Request to S-GW.
  • the S-GW sends the Modify Bearer Request to SMF+PGW-C.
  • the SMF+PGW-C sends the Modify Bearer Response to S-GW.
  • the S-GW sends the Create Session Response to MME.
  • the MME sends the Update Location to UDM/HSS.
  • the UDM/HSS invokes
  • the UDM/HSS sends the Update Location Ack to MME.
  • the MME sends the TAU accept to UE.
  • the UE behavior includes step (2) , where the UE sends the TAU to the MME after return from 5G SRVCC.
  • FIG. 7 shows an example of maintaining voice call and IP continuity when switching from a 2G/3G network to a 5G network.
  • the UE may access the 5G system.
  • the UE send Registration to AMF via 5G RAN.
  • the UE includes the 5G-GUTI and set registration type to Mobility Registration Update.
  • the tAMF invokes Namf_Communication_UEContextTransfer service operation to the old AMF for UE verification and UE context.
  • the 5GS may optionally verify and authenticate the UE identity.
  • the tAMF AMF registers with the UDM using Nudm_UECM_Registration.
  • the UDM/HSS UDM to initiate a Nudm_UECM_DeregistrationNotification to the sAMF for cancel location.
  • the steps (3) and (6) may be skipped.
  • the AMF invokes the Nsmf_PDUSession_UpdateSMContext to SMF of PDU session.
  • the AMF sends Registration Accept to UE.
  • the UE behavior includes the UE sending the Registration to the AMF with the registration type setting to Mobility Registration Update after return from 5G SRVCC.
  • FIG. 8 shows an example of a wireless communication method 800, which may be implemented at a UE, for SRVCC for 5G wireless networks.
  • the method 800 includes, at step 810, transmitting, upon determining that a voice service in a first network has terminated, a request to join a second network, where the request includes an identifier associated with the second network that is mapped from an identifier associated with a third network, and where the mapping indicates that the wireless device is joining the second network from the third network.
  • the method 800 includes determining whether the voice service in the first network has terminated.
  • the voice service may be a circuit-switched (CS) voice service in a 2G or 3G (GERAN or UTRAN, respectively) network.
  • the request is a Tracking Area Update (TAU) which is not communicated using IP.
  • the method 800 may include additional steps, as described in the context of FIG. 6.
  • the request includes the identifier associated with the second network that may be an Evolved Packet System (EPS) Globally Unique Temporary Identifier (GUTI) , the identifier associated with the third network that is a 5G-GUTI, and where the mapping comprises the EPS GUTI being an old Native GUTI.
  • EPS Evolved Packet System
  • GUI Globally Unique Temporary Identifier
  • the method includes, at step 820, performing a first set of communication operations in the second network using Internet Protocol (IP) information that was used to perform a second set of communication operations in the third network, and where the second set of communication operations were performed prior to performing the voice service in the first network.
  • IP Internet Protocol
  • the UE performs IP operations in a 5G network prior to moving to a 2G/3G network, wherein it may perform CS voice operations, and then move to a 4G or 5G network, such that the IP information used for subsequent communications in the 4G or 5G network is similar to that originally used in the 5G network (prior to the 2G/3G operation) .
  • FIG. 9 shows an example of a wireless communication method 900, which may be implemented at a UE, for SRVCC for 5G wireless networks.
  • the method 900 includes, at step 910, transmitting, upon determining that a voice service in a first network has terminated, a request to join a second network, where the request comprises a mobility registration type.
  • the method includes, at step 920, performing a first set of communication operations in the second network using Internet Protocol (IP) information that was used to perform a second set of communication operations in the second network, and where the second set of communication operations were performed prior to performing the voice service in the first network.
  • IP Internet Protocol
  • the method 900 may include additional steps, as described in the context of FIG. 7.
  • the UE performs IP operations in a 5G network prior to moving to a 2G/3G network, wherein it may perform CS voice operations, and then move back to the 5G network, such that the IP information used for subsequent communications in the 5G network is similar to that originally used in the 5G network (prior to the 2G/3G operation) .
  • the request further includes the 5G-GUTI.
  • the use of the “mobility registration” instead of the “initial access registration” ensures that IP continuity is maintained, despite the intervening 2G/3G operation. In an example, this ensures that PDU sessions that were set up in the initial set of communications are not lost when the UE returns to the 5G network.
  • FIG. 10 shows an example of a wireless communication method 1000, which may be implemented at a UE, for SRVCC for 5G wireless networks.
  • the method 1000 includes, at step 1110, performing a first set of communication operations in a first network using Internet Protocol (IP) information.
  • IP Internet Protocol
  • the first network is a 5G network.
  • the UE may perform IP or non-IP based operations in the 5G network, and uses IP information (e.g. IP addresses) for one or more PDU sessions.
  • IP information e.g. IP addresses
  • the method 1000 includes, at step 1120, transmitting a suspend command for each of the first set of communication operations.
  • a suspend command is transmitted for each of the PDU sessions in the 5G network.
  • the method 1000 includes, at step 1130, performing, subsequent to transmitting the suspend command, a second set of communication operations in a second network.
  • the suspend commands may switch over to a 2G/3G network, in which it may perform CS voice or other communication operations.
  • the method 1000 includes, at step 1140, performing a third set of communication operations in the first network using the IP information.
  • the UE returns to the 5G network, and may perform both IP and non-IP communication operations, and uses the same IP information as in the original 5G session prior to the 2G/3G operations.
  • the suspend commands transmitted prior to switching to the 2G/3G networks ensures that IP continuity is maintained when the UE returns to the 5G network.
  • FIG. 11 is a block diagram representation of a portion of an apparatus, in accordance with some embodiments of the presently disclosed technology.
  • An apparatus 1105 such as a base station or a wireless device (or UE) , can include processor electronics 1110 such as a microprocessor that implements one or more of the techniques presented in this document.
  • the apparatus 1105 can include transceiver electronics 1115 to send and/or receive wireless signals over one or more communication interfaces such as antenna (s) 1120.
  • the apparatus 1105 can include other communication interfaces for transmitting and receiving data.
  • Apparatus 1105 can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions.
  • the processor electronics 1110 can include at least a portion of the transceiver electronics 1115.
  • at least some of the disclosed techniques, modules or functions, including methods 800, 900 and/or 1000, are implemented using the apparatus 1105.
  • a computer-readable medium may include removable and non-removable storage devices including, but not limited to, Read Only Memory (ROM) , Random Access Memory (RAM) , compact discs (CDs) , digital versatile discs (DVD) , etc. Therefore, the computer-readable media can include a non-transitory storage media.
  • program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • Computer-or processor-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.
  • a hardware circuit implementation can include discrete analog and/or digital components that are, for example, integrated as part of a printed circuit board.
  • the disclosed components or modules can be implemented as an Application Specific Integrated Circuit (ASIC) and/or as a Field Programmable Gate Array (FPGA) device.
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • DSP digital signal processor
  • the various components or sub-components within each module may be implemented in software, hardware or firmware.
  • the connectivity between the modules and/or components within the modules may be provided using any one of the connectivity methods and media that is known in the art, including, but not limited to, communications over the Internet, wired, or wireless networks using the appropriate protocols.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs pour une continuité d'appel vocal radio unique (SRVCC) dans des réseaux 5G. Un procédé de maintien de la continuité d'appel vocal et de protocole Internet (IP) comprend la transmission, sur détermination du fait qu'un service vocal dans un premier réseau s'est terminé, d'une demande pour rejoindre un deuxième réseau, la demande contenant un identificateur associé au deuxième réseau qui est mis en correspondance à partir d'un identificateur associé à un troisième réseau, et la mise en correspondance indiquant que le dispositif sans fil rejoint le deuxième réseau depuis le troisième réseau, et la mise en œuvre d'une opération de communication dans le deuxième réseau en utilisant les informations IP qui étaient utilisées pour la mise en œuvre du service vocal dans le premier réseau. Dans un autre procédé, la demande contient un type d'enregistrement de mobilité.
PCT/CN2018/082527 2018-04-10 2018-04-10 Continuité d'appel vocal radio unique pour réseaux sans fil 5g WO2019196012A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880092184.5A CN111955028B (zh) 2018-04-10 2018-04-10 用于5g无线网络的单射频语音呼叫连续性
PCT/CN2018/082527 WO2019196012A1 (fr) 2018-04-10 2018-04-10 Continuité d'appel vocal radio unique pour réseaux sans fil 5g

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/082527 WO2019196012A1 (fr) 2018-04-10 2018-04-10 Continuité d'appel vocal radio unique pour réseaux sans fil 5g

Publications (1)

Publication Number Publication Date
WO2019196012A1 true WO2019196012A1 (fr) 2019-10-17

Family

ID=68163418

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082527 WO2019196012A1 (fr) 2018-04-10 2018-04-10 Continuité d'appel vocal radio unique pour réseaux sans fil 5g

Country Status (2)

Country Link
CN (1) CN111955028B (fr)
WO (1) WO2019196012A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021109095A1 (fr) * 2019-12-05 2021-06-10 华为技术有限公司 Procédé, appareil et système d'interfonctionnement entre réseaux
CN114286301A (zh) * 2021-12-31 2022-04-05 展讯通信（上海）有限公司 语音业务控制方法及装置、存储介质、终端设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117793811A (zh) * 2022-09-21 2024-03-29 维沃移动通信有限公司 通信方法、装置及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104918292A (zh) * 2014-03-13 2015-09-16 中国移动通信集团江苏有限公司 一种业务控制方法和系统
US20170238247A1 (en) * 2014-09-30 2017-08-17 Nokia Solutions And Networks Oy Method and apparatus for tracking idle devices
CN107431917A (zh) * 2015-03-06 2017-12-01 华为技术有限公司 分离会话锚点与转发锚点的方法和系统
CN107454660A (zh) * 2017-08-08 2017-12-08 北京小米移动软件有限公司 鉴权失败后的驻网方法和装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8594069B2 (en) * 2007-08-06 2013-11-26 Qualcomm Incorporated In-order data delivery during handover in a wireless communication system
CN101827093A (zh) * 2010-03-18 2010-09-08 孙干 无线多媒体传播控制系统及其操作方法
US8630607B2 (en) * 2011-07-15 2014-01-14 Verizon Patent And Licensing Inc. Emergency call handoff between heterogeneous networks
EP2810519A4 (fr) * 2012-01-31 2015-10-14 Nokia Corp Procédé et appareil pour faciliter une continuité de session de communication
CN103906158A (zh) * 2012-12-28 2014-07-02 展讯通信（上海）有限公司 一种从2g/3g网络返回lte网络的方法
EP3025540A4 (fr) * 2013-07-26 2017-03-15 Intel IP Corporation Signalisation d'informations d'interférence pour aider un matériel utilisateur
US20160135093A1 (en) * 2014-11-10 2016-05-12 Samsung Electronics Co., Ltd. Apparatus and method for handling single radio voice call continuity handover
US9930591B2 (en) * 2015-03-02 2018-03-27 Samsung Electronics Co., Ltd. Method and apparatus for providing service in wireless communication system
CN105898805A (zh) * 2015-12-15 2016-08-24 乐视移动智能信息技术（北京）有限公司 网络切换方法及终端
US10362511B2 (en) * 2016-05-17 2019-07-23 Lg Electronics Inc. Method and apparatus for determining PDU session identity in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104918292A (zh) * 2014-03-13 2015-09-16 中国移动通信集团江苏有限公司 一种业务控制方法和系统
US20170238247A1 (en) * 2014-09-30 2017-08-17 Nokia Solutions And Networks Oy Method and apparatus for tracking idle devices
CN107431917A (zh) * 2015-03-06 2017-12-01 华为技术有限公司 分离会话锚点与转发锚点的方法和系统
CN107454660A (zh) * 2017-08-08 2017-12-08 北京小米移动软件有限公司 鉴权失败后的驻网方法和装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021109095A1 (fr) * 2019-12-05 2021-06-10 华为技术有限公司 Procédé, appareil et système d'interfonctionnement entre réseaux
CN114286301A (zh) * 2021-12-31 2022-04-05 展讯通信（上海）有限公司 语音业务控制方法及装置、存储介质、终端设备
CN114286301B (zh) * 2021-12-31 2023-09-22 展讯通信（上海）有限公司 语音业务控制方法及装置、存储介质、终端设备

Also Published As

Publication number Publication date
CN111955028B (zh) 2022-02-22
CN111955028A (zh) 2020-11-17

Similar Documents

Publication Publication Date Title
US9521590B2 (en) Multi-bearer connection control
US11178582B2 (en) Transcoding avoidance during single radio voice call continuity (SRVCC)
US9277460B2 (en) System and method for providing voice service in a multimedia mobile network
KR101783699B1 (ko) 핸드오버 중에 단일 무선 영상 통화 연속성을 지원하는 방법 및 시스템
JP6388952B2 (ja) 回路交換フォールバック
US8670414B2 (en) Mobile communication system including the radio access network not supporting circuit switching (CS) and the radio access network supporting CS
KR101446028B1 (ko) 패킷 스위칭된 도메인으로부터 회로 스위칭된 도메인으로 비디오 호를 핸드 오버하기 위한 방법 및 디바이스
US20140051443A1 (en) Methods and Apparatus for Enhancing Circuit-Switched Call Fallback (CSFB) Service for a Shared Network Node
CN107079281B (zh) 用于处理更新的订户数据的方法和节点
US9813946B2 (en) Direct handover method and device
KR20170005064A (ko) Ｕｅ를 전용 코어 네트워크 노드에 리디렉트하기 위한 방법들 및 이동성 관리 엔티티(ｍｍｅ)
US11729675B2 (en) Method and apparatus for performing a voice service handover to a circuit switched domain voice service
KR20150131902A (ko) 음성 호 서비스 품질을 높이는 방법 및 장치
WO2019196012A1 (fr) Continuité d'appel vocal radio unique pour réseaux sans fil 5g
CN108924893B (zh) 一种承载释放方法、装置、mme及sae-gw
US11470528B2 (en) Technique for preparing user equipment mobility
CN116686339A (zh) 用于在不同rat之间切换的方法和装置
JP2011233987A (ja) 移動通信システム及びサーバ装置
KR20140046235A (ko) 부하제어장치 및 방법
KR101982204B1 (ko) 다운링크 데이터 처리장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18914787

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 04/02/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18914787

Country of ref document: EP

Kind code of ref document: A1