ForewordIntroduction1 Scope2 References3 Definitions, symbols and abbreviations4 High level principles and architectural requirements5 Architecture model and reference points6 Procedures and flows for Access Transfer6.0 Introduction6.1 Registration6.2 Origination and Termination6.3 Access Transfer6.3.1 Access Transfer Procedure6.3.2 Access Transfer Information flows6.3.3 Media Adding/Deleting6.3.4 Void6.3.5 Service continuity for ICS UE using MSC Server assisted mid-call feature while maintaining CS media6.4 Operator Policy and User Preferences6.5 Execution of supplementary services6a Procedures and flows for Inter‑UE Transfer6a.0 Introduction6a.1 IUT general procedures6a.2 Information flows for Collaborative Session establishment6a.3 Media Transfer within Collaborative Session6a.4 Media adding/deleting/modifying within Collaborative Session6a.4.1 Controller UE initiated add new media on Controller UE6a.4.2 Controller UE initiated add new media on Controllee UE6a.4.3 Controller UE Initiated Release Media (media flow on the Controller UE)6a.4.4 Controller UE Initiated Release Media (media flow on the Controllee UE)6a.4.4a Controller UE initiated modify media (media flow on the Controllee UE)6a.4.5 Controllee UE initiated release media on itself6a.4.6 Controllee UE initiated modify media on itself6a.4.6a Controllee UE initiated add new media on another Controllee UE6a.4.7 Remote party initiated add new media6a.4.8 Remote party initiated release media6a.4.9 Remote party initiated media modification6a.4a Transfer of Collaborative Session Control6a.5 Collaborative Session release6a.6 Inter‑UE Transfer without establishing a Collaborative Session6a.7 Execution of supplementary services6a.8 IUT target discovery6a.9 Inter-UE Transfer Initiated by Target UE6a.10 Media Flow Replication by network6a.11 Session Replication by remote party6a.12 User authorisation and preferences6b Void6c Procedures and flows for SRVCC Emergency Session6d Procedures and flows for DRVCC Emergency Session for WLAN7 Security8 ChargingA.1 GeneralB.1 GeneralB.2 Minimize the transcoding for SRVCCB.3 Reject SRVCC due to UE call state incompatibilityC.1 GeneralC.2 ATCF enhancements SRVCC ArchitectureC.3 ATCF in architectures with Mx as a roaming interface without media anchored in ATGW 6.3.4 Void 23.2373GPPIP Multimedia Subsystem (IMS) Service ContinuityRelease 17Stage 2TS Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM