Tech-invite  3GPP-Specs  Features  Entities  Interfaces  SBIs  Identifiers  Ti+  Search in Tech-invite
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 23.237 (SA2) ★
IMS Service Continuity –
Stage 2

3GPP‑Page   ETSI‑search   short‑ToC   full‑ToC
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V16.3.0 (Wzip)  2019/09  189 p.
V15.2.0 (PDF)  2019/09  185 p.
V14.2.0  2016/12  183 p.
V13.1.0  2015/12  172 p.
V12.10.0  2015/12  172 p.
V11.11.0  2015/12  171 p.
V10.13.0  2015/12  158 p.
V9.10.0  2012/12  86 p.
V8.7.0  2010/03  42 p.
3GPP 23.237 - IMS Service Centralization and Continuity Reference Architecture when using ATCF
Rapporteur:  Mr. Song, Jae seung
IMS based services can be provided with use of PS bearers and CS bearers for the media. When using CS bearer for media transport of IMS sessions, interworking solutions for IMS Centralized Services (ICS) as specified in TS 23.292 are used. ICS allows IMS sessions using CS bearers to be treated as standard IMS sessions for the purpose of IMS Service Continuity (ISC). ICS defines signalling mechanisms between the UE and IMS for transport of information as needed for service continuity when using CS access for media transport. Both ICS and ISC specify functions which are provided by a SIP application server.
This TS specifies the architectural requirements and procedures for delivery of IMS Service Continuity (ISC). The solution is restricted to service continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN level are not within the scope of this specification.

short Table of Contents for  TS 23.237  Word version:   16.3.0

each title links to the equivalent title in the full ToC

 

Here   Top

 

1  Scope  Word-p. 11
2  References  Word-p. 11
3  Definitions, symbols and abbreviations  Word-p. 13
4  High level principles and architectural requirements  Word-p. 15
5  Architecture model and reference points  Word-p. 23
6  Procedures and flows for Access Transfer  Word-p. 33
6.0  Introduction  Word-p. 33
6.1  Registration  Word-p. 33
6.2  Origination and Termination  Word-p. 36
6.3  Access Transfer  Word-p. 45
6.4  Operator Policy and User Preferences  Up  Word-p. 102
6.5  Execution of supplementary services  Word-p. 103
6a  Procedures and flows for Inter-UE Transfer [R9]  Word-p. 106
6a.0  Introduction  Word-p. 106
6a.1  IUT general procedures  Word-p. 106
6a.2  Information flows for Collaborative Session establishment  Word-p. 106
6a.3  Media Transfer within Collaborative Session  Word-p. 111
6a.4  Media adding/deleting/modifying within Collaborative Session  Word-p. 119
6a.4a  Transfer of Collaborative Session Control [R10]  Word-p. 134
6a.5  Collaborative Session release  Word-p. 141
6a.6  Inter-UE Transfer without establishing a Collaborative Session  Word-p. 142
6a.7  Execution of supplementary services  Word-p. 145
6a.8  IUT target discovery  Up  Word-p. 148
6a.9  Inter-UE Transfer Initiated by Target UE [R10]  Word-p. 151
6a.10  Media Flow Replication by network [R10]  Word-p. 158
6a.11  Session Replication by remote party [R10]  Word-p. 164
6a.12  User authorisation and preferences [R10]  Word-p. 168
6b  Void
6c  Procedures and flows for SRVCC Emergency Session [R9]  Word-p. 169
6d  Procedures and flows for DRVCC Emergency Session for WLAN [R14]  Word-p. 176
7  Security  Word-p. 178
8  Charging  Word-p. 178
A  Controller UE and Controllee UE operations [R9]  Word-p. 180
B (Normative)  Additional enhancements for SRVCC [R14]  Word-p. 182
C (Normative)  ATCF in Architectures without IMS-level roaming interfaces [R16]  Word-p. 185
D  Change history  Word-p. 188

Up   Top