CSFB 3GPP TS 23272-a.doc

3GPP TS 23.272 V10.2.1 (2011-01)Technical Specification3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Circuit Switched (CS) fallback in Evolved Packet System (EPS);Stage 2(Release 10)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices.3GPP TS 23.272 V10.2.1 (2011-01)79Release 10KeywordsLTE, circuit mode, UMTS, GSM3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16InternetCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS is a Trade Mark of ETSI registered for the benefit of its members3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM AssociationContentsForeword61Scope72References73Definitions and abbreviations93.1Definitions93.2Abbreviations94Overall Description94.1General Considerations94.2Reference Architecture104.2.1Reference points104.3Functional entities104.3.1UE104.3.2MME114.3.3MSC124.3.4E-UTRAN124.3.5SGSN124.3.6BSS124.4Control plane134.4.1MME - MSC Server134.5Co-existence with IMS services134.6Emergency Calls134.7CSFB Priority Call Handling135Mobility Management145.1General145.1ATAI list and LAI allocation145.2Attach procedure145.3Detach procedure165.3.1UE-initiated Detach procedure165.3.1AUE-initiated Detach procedure for GERAN/UTRAN with ISR activated175.3.2MME-initiated Detach procedure175.3.2ASGSN-initiated Detach procedure with ISR activated185.3.3HSS-initiated Detach procedure185.3.4Administration of the MME - MSC/VLR Association185.4TA/LA Update procedure195.4.0General195.4.1Combined TA/LA Update Procedure195.4.2Periodic TA and LA Update Procedure205.4.3Non-EPS Alert procedure215.4.4Void215.5Idle Mode Signalling Reduction215.6Mobility Management for SMS over SGs only UEs226Mobile Originating Call226.1General226.2Mobile Originating call in Active Mode - PS HO supported236.3Mobile Originating call in Active Mode No PS HO support256.4Mobile Originating call in Idle Mode296.5Returning back to E-UTRAN296.6Mobile Originated or Mobile terminated call rejected by the MME307Mobile Terminating Call317.1General317.2Mobile Terminating call in idle mode317.3Mobile Terminating call in Active Mode - PS HO supported337.4Mobile Terminating call in Active Mode - No PS HO support367.5Roaming Retry for CS fallback397.6Returning back to E-UTRAN407.7Interaction with ISR417.7.1Void417.7.2Mobile Terminating Call when ISR is active and SGs is active between MSC/VLR and MME417.7.3Void427.8Mobile Terminating Call when SGs is not active428Other CS Services428.1General428.2Short Message Service (SMS)428.2.1General428.2.2Mobile originating SMS in Idle Mode428.2.3Mobile originating SMS in Active Mode448.2.3aMultiple Mobile originating SMSs448.2.4Mobile terminating SMS in idle mode448.2.5Mobile terminating SMS in Active Mode458.2.5aMultiple Mobile terminating SMSs458.2.5bSimultaneous Mobile terminating and Mobile originating SMSs458.2.5cUnsuccessful Mobile terminating SMS delivery attempt458.2.5dNon-SMS Mobile terminating activity during SMS delivery468.2.5eNon-SMS Mobile originating activity during SMS delivery468.2.5fMobile Terminating SMS when ISR is active and SGs is active between MSC/VLR and MME468.2.6Co-Existence with SMS over generic 3GPP IP access468.3Location Services (LCS)478.3.1MO-LR procedure4General4MO-LR in Active Mode with IMS VoIP session - PS HO supported4MO-LR in Active Mode with IMS VoIP session - No PS HO supported488.3.2MT-LR procedure4MT-LR procedure if UE is not in IMS VoIP session4MT-LR procedure while UE is in IMS VoIP session508.3.3NI-LR procedure518.3.4Returning back to E-UTRAN518.3.5Co-Existence with Other Location Services5Co-Existence with SUPL518.4Call Independent Supplementary Services518.4.1Mobile-Initiated Call Independent SS procedure518.4.2NW-Initiated Call Independent SS procedure528.4.3Returning back to E-UTRAN52Annex A:Void53Annex B (normative):CS Fallback to 1xRTT54B.1Overall Description54B.1.1General Considerations54B.1.2Reference Architecture54B.1.2.1Reference points55B.1.3Functional entities55B.1.3.1UE55B.1.3.2MME55B.1.3.3E-UTRAN56B.1.4Co-existence with IMS services56B.1.5CSFB Priority Call Handling56B.2Procedures57B.2.1Mobility Management57B.2.1.11x RTT CS Pre-Registration over EPS Procedure57B.2.1.2S102 Tunnel Redirection58B.2.1.3UE-initiated Detach Procedure59B.2.2Mobile Originating Call in Active Mode59B.2.2aMobile Originating call in Idle Mode61B.2.3Mobile Terminating Call61B.2.3aEnhanced CS fallback to 1xRTT Procedure63B.2.3a.1General63B.2.3a.2Mobile Originating Call without concurrent PS handover, or with concurrent non-optimised PS handover or optimised idle-mode PS handover64B.2.3a.3Mobile Originating Call with concurrent optimised PS handover67B.2.3a.4Mobile Terminating Call without PS handover, or with concurrent non-optimised PS handover or optimised idle-mode PS handover68B.2.3a.5Mobile Terminating Call with concurrent optimised PS handover69B.2.3a.6Interaction between enhanced CS Fallback to 1xRTT and optimised PS handover70B.2.3bMobile Originated or Mobile terminated call rejected by the MME70B.2.4Short Message Service (SMS)72B.2.4.1General72B.2.4.2Mobile originating SMS72B.2.4.3Mobile terminating SMS73B.2.5Emergency Calls74B.3CS Fallback for UEs with dual Rx configuration74B.3.1General Considerations74B.3.2Procedures for leaving E-UTRAN75B.3.3Procedures for returning to E-UTRAN76Annex C (informative):Change history77ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:xthe first digit:1presented to TSG for information;2presented to TSG for approval;3or greater indicates TSG approved document under change control.ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when editorial only changes have been incorporated in the document.1ScopeThis document defines the Stage 2 architecture and specification for the CS Fallback and for SMS over SGs for EPS or CS Fallback and SMS over S102. The scope of this document includes the architecture enhancements for functionality to enable fallback from E-UTRAN access to UTRAN/GERAN CS domain access and to CDMA 1x RTT CS domain access, and functionality to reuse of voice and other CS-domain services (e.g. CS UDI video / LCS / USSD) by reuse of the CS domain. The functionality specified to support SMS over SGs does not trigger any CS Fallback to UTRAN/GERAN. The functionality specified to support SMS over S102 does not trigger any CS Fallback to CDMA 1xRTT CS domain.The architecture enhancements to support CS fallback to CDMA 1x RTT CS domain access for UEs with single and dual receiver configurations are specified in AnnexB.In this Release of the specification no mechanisms are specified to support CS Fallback to both UTRAN/GERAN and CDMA 1xRTT in the same PLMN. So, even when a UE has the capability to support both CS Fallback to UTRAN/GERAN CS domain and CS Fallback to CDMA 1xRTT CS domain in a given PLMN, the PLMN implements only one of the two.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.13GPPTR21.905: Vocabulary for 3GPP Specifications.23GPPTS23.401: GPRS Enhancements for E-UTRAN Access.33GPPTS23.060: General Packet Radio Service (GPRS); Service description; Stage2.43GPPTS44.018: Mobile radio interface layer 3 specification Radio Resource Control (RRC) protocol.53GPPTS23.018: Basic call handling; Technical realization.63GPPTS48.008: MSC-BSS interface layer 3 specification; Protocol specification.73GPPTS25.331: Radio Resource Control (RRC); Protocol specification.83GPP TS23.271: Functional stage 2 description of Location Services (LCS).9Open Mobile Alliance, OMA AD SUPL: Secure User Plane Location Architecture,.103GPPTS23.090: Unstructured Supplementary Service Data (USSD); Stage 2.11Void.123GPPTS44.060: MS-BSS interface; RLC/MAC protocol .133GPPTS24.010: Supplementary services specification; General aspects.143GPPTS23.040: Technical realization of the Short Message Service (SMS).153GPPTS23.204: Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access.163GPP2A.S0008-C: Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network.173GPP2A.S0009-C: Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function.183GPP2A.S0013-C: Interoperability Specification (IOS) for cdma2000 Access Network Interfaces part 3 Features.193GPPTR36.938: Improved Network Controlled Mobility between E-UTRAN and 3GPP2/Mobile WiMAX Radio Technologies.203GPPTS23.216: Single Radio Voice Call Continuity (SRVCC); Stage 2.213GPPTS24.008: Mobile radio interface Layer3 specification; Core network protocols; Stage3.223GPP2X.S0042-0: Voice Call Continuity between IMS and Circuit Switched System.233GPPTS23.236: Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes.243GPPTS43.055: Radio Access Network; Dual Transfer Mode (DTM); Stage 2.253GPPTS23.292: IMS Centralised Services (ICS); Stage 2.263GPPTS23.221: Architectural Requirements.273GPPTS23.402: Architecture enhancements for non-3GPP accesses.283GPPTS24.011: Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface.293GPPTS25.413: UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling.303GPPTS48.018: General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP).313GPPTS23.082: Call Forwarding (CF) supplementary services; Stage2.323GPP2C.S0005-A: Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems - Release A, Addendum 2.333GPPTS36.331: Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC)343GPPTS24.301: Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3.353GPPTS36.413: S1 Application Protocol (S1AP).363GPPTS22.153: Multimedia Priority Services.373GPPTS22.067: enhanced Multi Level Precedence and Pre emption service (eMLPP) - Stage 1.383GPPTS22.011: Service accessibility.393GPP2A.S0008-C: Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network.403GPP2A.S0009-C: Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function.3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in TR21.9051 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR21.9051.1xCS: The 3GPP2 legacy circuit Switched signalling system as defined in 3GPP2X.S0042-022.CSMT flag: A flag in LA update request message used in CS fallback for MT call to avoid missing paging in roaming retry.CSMO flag: A flag in CM Service Request and LA Update request message used in CS fallback for MO calls.Service User: See TS22.15336.3.2AbbreviationsFor the purposes of the present document, the abbreviations given in TR21.9051 apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR21.9051.1xCS IWSCircuit Switched fallback Interworking solution Function for 3GPP2 1xCS.CSMTCircuit Switched fallback Mobile Terminated call.CSMOCircuit Switched fallback Mobile Originated call.eMLPPenhanced Multi Level Precedence and Pre emptionICSIMS Centralised ServicesMPSMultimedia Priority ServiceNEAFNon-EPS Alert Flag.SRVCCSingle Radio Voice Call Continuity4Overall Description4.1General ConsiderationsThe CS fallback in EPS enables the provisioning of voice and other CS-domain services (e.g. CS UDI video/ LCS/ USSD) by reuse of CS infrastructure when the UE is served by EUTRAN. A CS fallback enabled terminal, connected to EUTRAN may use GERAN or UTRAN to connect to the CSdomain. This function is only available in case EUTRAN coverage is overlapped by either GERAN coverage or UTRAN coverage.CS Fallback and IMSbased services shall be able to co-exist in the same operators network.The ICS architecture as defined in TS23.29225 shall be able to co-exist with utilising CS Fallback as the CS domain in the same operators network.This specification also specifies the architecture required for SMS over SGs. The MO SMS and MT SMS are signalled over SGs and do not cause any CS Fallback to GERAN/UTRAN RATs, and consequently does not require any overlapped GERAN/UTRAN coverage.The support of SMS over SGs is mandatory for UE and MME and MSC supporting CS fallback, whereas UE and MME and MSC supporting SMS over SGs are not required to support CS fallback.NOTE:An MME supporting only SMS over SGs (i.e. not supporting CS fallback) will either reply with SMS-only or reject an IMSI attach.The support of CS fallback (and to a lesser extent SMS over SGs) can impose some operational constraints on Tracking Area boundary planning and the use of the tracking area list concept (see TS23.4012).4.2Reference ArchitectureThe CS fallback and SMS over SGs in EPS function is realized by using the SGs interface mechanism between the MSC Server and the MME.The SGs interface functionality is based on the mechanisms specified for the Gs interface, TS23.0603.Figure 4.2-1: EPS architecture for CS fallback and SMS over SGsNOTE1:The MGW is not shown in the figure4.21 since neither CS fallback in EPS nor SMS over SGs has any impacts on the Uplane handling.NOTE2:SGSN and S3 have additional functionality related to ISR and CS fallback/SMS over SGs. If ISR is not used, this functionality is not required.4.2.1Reference pointsSGs:It is the reference point between the MME and MSC server. The SGs reference point is used for the mobility management and paging procedures between EPS and CS domain, and is based on the Gs interface procedures. The SGs reference point is also used for the delivery of both mobile originating and mobile terminating SMS. Additional procedures for alignment with the Gs reference point are not precluded.S3:It is defined in TS23.4012 with the additional functionality to support ISRIdle state Signalling Reduction (ISR)。空闲状态的信令优化/压缩，ISR激活时，用于减少空闲UE在E-UTRAN和GERAN/UTRAN间选择时引起的频繁的TAU/RAU，可有效压缩UE和网络间的更新信令及网络间的信令，来减轻网络负担。 for CS fallback/SMS over SGs as defined in this specification.4.3Functional entities4.3.1UEThe CS fallback capable UE supports access to E-UTRAN/EPC as well as access to the CS domain over GERAN and/or UTRAN.The SMS over SGs capable UE supports access to E-UTRAN/EPC and may support access to the CS domain over GERAN and/or UTRAN.The support of SMS over SGs is mandatory for a UE that supports CS fallback, whereas a UE that supports SMS over SGs is not required to support CS fallback.These UEs support the following additional functions:-Combined procedures specified in this document for EPS/IMSI attach, up