3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;

IP multimedia call control protocol based on
3GPP TS 24.229
Session InitiationV16.8.0
Protocol(2020-12)
(SIP)
and Session Description Protocol (SDP);
Technical Specification

Stage 3
(Release 16)

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.
Release 16 2 3GPP TS 24.229 V16.8.0 (2020-12)

Keywords
UMTS, Network, IP, SIP, SDP, multimedia, LTE

3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.

© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association

3GPP
Release 16 3 3GPP TS 24.229 V16.8.0 (2020-12)

Contents
Foreword........................................................................................................................................................39
1 Scope....................................................................................................................................................40
2 References............................................................................................................................................41
3 Definitions and abbreviations...............................................................................................................55
3.1 Definitions.........................................................................................................................................................55
3.2 Abbreviations.....................................................................................................................................................63
3A Interoperability with different IP-CAN.................................................................................................66
4 General.................................................................................................................................................67
4.1 Conformance of IM CN subsystem entities to SIP, SDP and other protocols..................................................67
4.2 URI and address assignments............................................................................................................................71
4.2A Transport mechanisms.......................................................................................................................................72
4.2B Security mechanisms.........................................................................................................................................73
4.2B.1 Signalling security........................................................................................................................................73
4.2B.2 Media security..............................................................................................................................................75
4.3 Routeing principles of IM CN subsystem entities.............................................................................................77
4.4 Trust domain......................................................................................................................................................77
4.4.1 General.........................................................................................................................................................77
4.4.2 P-Asserted-Identity......................................................................................................................................78
4.4.3 P-Access-Network-Info...............................................................................................................................78
4.4.4 History-Info..................................................................................................................................................78
4.4.5 P-Asserted-Service.......................................................................................................................................79
4.4.6 Resource-Priority.........................................................................................................................................79
4.4.7 Reason (in a response).................................................................................................................................79
4.4.8 P-Profile-Key...............................................................................................................................................79
4.4.9 P-Served-User..............................................................................................................................................79
4.4.10 P-Private-Network-Indication......................................................................................................................79
4.4.11 P-Early-Media..............................................................................................................................................79
4.4.12 CPC and OLI................................................................................................................................................80
4.4.13 Feature-Caps................................................................................................................................................80
4.4.14 Priority.........................................................................................................................................................80
4.4.15 iotl................................................................................................................................................................80
4.4.16 Restoration-Info...........................................................................................................................................80
4.4.17 Relayed-Charge............................................................................................................................................80
4.4.18 Service-Interact-Info....................................................................................................................................80
4.4.19 Cellular-Network-Info.................................................................................................................................80
4.4.20 Response-Source..........................................................................................................................................81
4.4.21 Attestation-Info header field........................................................................................................................81
4.4.22 Origination-Id header field...........................................................................................................................81
4.4.23 Additional-Identity header field...................................................................................................................81
4.5 Charging correlation principles for IM CN subsystems....................................................................................81
4.5.1 Overview......................................................................................................................................................81
4.5.2 IM CN subsystem charging identifier (ICID)..............................................................................................82
4.5.2A Related ICID................................................................................................................................................82
4.5.3 Access network charging information.........................................................................................................83
4.5.3.1 General...................................................................................................................................................83
4.5.3.2 Access network charging information....................................................................................................83
4.5.4 Inter operator identifier (IOI).......................................................................................................................83
4.5.4A Transit inter operator identifier (Transit IOI)..............................................................................................85
4.5.5 Charging function addresses........................................................................................................................86
4.5.6 Relayed charge parameters..........................................................................................................................86
4.5.7 Loopback-indication parameter...................................................................................................................86
4.5.8 IM CN subsystem Functional Entity Identifier............................................................................................86
4.5.8.1 General...................................................................................................................................................86
4.5.8.2 Tracking of IM CN subsystem functional entities generating charging information.............................86

3GPP
Release 16 4 3GPP TS 24.229 V16.8.0 (2020-12)

4.5.8.3 Tracking of applications generating charging information....................................................................87

4.6 Support of local service numbers......................................................................................................................87
4.7 Emergency service.............................................................................................................................................87
4.7.1 Introduction..................................................................................................................................................87
4.7.2 Emergency calls generated by a UE............................................................................................................87
4.7.3 Emergency calls generated by an AS...........................................................................................................88
4.7.4 Emergency calls received from an enterprise network................................................................................88
4.7.5 Location in emergency calls........................................................................................................................88
4.7.6 eCall type of emergency service..................................................................................................................89
4.8 Tracing of signalling..........................................................................................................................................89
4.8.1 General.........................................................................................................................................................89
4.8.2 Trace depth...................................................................................................................................................89
4.9 Overlap signalling..............................................................................................................................................90
4.9.1 General.........................................................................................................................................................90
4.9.2 Overlap signalling methods.........................................................................................................................90
4.9.2.1 In-dialog method....................................................................................................................................90
4.9.2.1.1 General..............................................................................................................................................90
4.9.2.2 Multiple-INVITE method......................................................................................................................90
4.9.2.2.1 General..............................................................................................................................................90
4.9.3 Routeing impacts..........................................................................................................................................90
4.9.3.1 General...................................................................................................................................................90
4.9.3.2 Deterministic routeing............................................................................................................................90
4.9.3.3 Digit collection.......................................................................................................................................91
4.10 Dialog correlation for IM CN subsystems.........................................................................................................91
4.10.1 General.........................................................................................................................................................91
4.10.2 CONF usage.................................................................................................................................................91
4.11 Priority mechanisms..........................................................................................................................................91
4.12 Overload control................................................................................................................................................93
4.13 II-NNI traversal scenario...................................................................................................................................93
4.13.1 General.........................................................................................................................................................93
4.13.2 Identifying the II-NNI traversal scenario.....................................................................................................94
4.13.3 Security aspects............................................................................................................................................94
4.14 Restoration procedures......................................................................................................................................94
4.14.1 General.........................................................................................................................................................94
4.14.2 P-CSCF restoration procedures....................................................................................................................95
4.14.3 S-CSCF restoration procedures....................................................................................................................95
4.15 Resource sharing................................................................................................................................................95
4.16 Priority sharing..................................................................................................................................................96
4.17 3GPP PS data off...............................................................................................................................................96
4.18 Dynamic Service Interaction.............................................................................................................................97
4.19 Restricted Local Operator Services...................................................................................................................97
5 Application usage of SIP......................................................................................................................97
5.1 Procedures at the UE.........................................................................................................................................97
5.1.0 General.........................................................................................................................................................97
5.1.1 Registration and authentication....................................................................................................................98
5.1.1.1 General...................................................................................................................................................98
5.1.1.1A Parameters contained in the ISIM..........................................................................................................98
5.1.1.1B Parameters provisioned to a UE without ISIM or USIM.......................................................................99
5.1.1.1B.1 Parameters provisioned in the IMC..................................................................................................99
5.1.1.1B.2 Parameters when UE does not contain ISIM, USIM or IMC...........................................................99
5.1.1.2 Initial registration...................................................................................................................................99
5.1.1.2.1 General..............................................................................................................................................99
5.1.1.2.2 Initial registration using IMS AKA................................................................................................105
5.1.1.2.3 Initial registration using SIP digest without TLS...........................................................................106
5.1.1.2.4 Initial registration using SIP digest with TLS................................................................................106
5.1.1.2.5 Initial registration using NASS-IMS bundled authentication.........................................................107
5.1.1.2.6 Initial registration using GPRS-IMS-Bundled authentication........................................................107
5.1.1.3 Subscription to the registration-state event package............................................................................107
5.1.1.3A Void......................................................................................................................................................108
5.1.1.4 User-initiated reregistration and registration of an additional public user identity..............................108
5.1.1.4.1 General............................................................................................................................................108

3GPP
Release 16 5 3GPP TS 24.229 V16.8.0 (2020-12)

5.1.1.4.2 IMS AKA as a security mechanism...............................................................................................112

5.1.1.4.3 SIP digest without TLS as a security mechanism...........................................................................113
5.1.1.4.4 SIP digest with TLS as a security mechanism................................................................................114
5.1.1.4.5 NASS-IMS bundled authentication as a security mechanism........................................................114
5.1.1.4.6 GPRS-IMS-Bundled authentication as a security mechanism.......................................................114
5.1.1.5 Authentication......................................................................................................................................115
5.1.1.5.1 IMS AKA - general........................................................................................................................115
5.1.1.5.2 Void................................................................................................................................................116
5.1.1.5.3 IMS AKA abnormal cases..............................................................................................................116
5.1.1.5.4 SIP digest without TLS – general...................................................................................................117
5.1.1.5.5 SIP digest without TLS – abnormal procedures.............................................................................117
5.1.1.5.6 SIP digest with TLS – general........................................................................................................117
5.1.1.5.7 SIP digest with TLS – abnormal procedures..................................................................................118
5.1.1.5.8 NASS-IMS bundled authentication – general................................................................................118
5.1.1.5.9 NASS-IMS bundled authentication – abnormal procedures..........................................................118
5.1.1.5.10 GPRS-IMS-Bundled authentication – general................................................................................118
5.1.1.5.11 GPRS-IMS-Bundled authentication – abnormal procedures..........................................................118
5.1.1.5.12 Abnormal procedures for all security mechanisms........................................................................118
5.1.1.5A Network-initiated re-authentication.....................................................................................................119
5.1.1.5B Change of IPv6 address due to privacy................................................................................................119
5.1.1.6 User-initiated deregistration.................................................................................................................120
5.1.1.6.1 General............................................................................................................................................120
5.1.1.6.2 IMS AKA as a security mechanism...............................................................................................122
5.1.1.6.3 SIP digest without TLS as a security mechanism...........................................................................122
5.1.1.6.4 SIP digest with TLS as a security mechanism................................................................................123
5.1.1.6.5 NASS-IMS bundled authentication as a security mechanism........................................................123
5.1.1.6.6 GPRS-IMS-Bundled authentication as a security mechanism.......................................................123
5.1.1.7 Network-initiated deregistration..........................................................................................................124
5.1.2 Subscription and notification.....................................................................................................................125
5.1.2.1 Notification about multiple registered public user identities...............................................................125
5.1.2.2 General SUBSCRIBE requirements.....................................................................................................125
5.1.2A Generic procedures applicable to all methods excluding the REGISTER method....................................125
5.1.2A.1 UE-originating case..............................................................................................................................125
5.1.2A.1.1 General............................................................................................................................................125
5.1.2A.1.2 Structure of Request-URI...............................................................................................................131
5.1.2A.1.3 UE without dial string processing capabilities...............................................................................131
5.1.2A.1.4 UE with dial string processing capabilities....................................................................................132
5.1.2A.1.5 Setting the "phone-context" tel URI parameter..............................................................................132
5.1.2A.1.5A Policy on local numbers.................................................................................................................133
5.1.2A.1.6 Abnormal cases...............................................................................................................................134
5.1.2A.2 UE-terminating case.............................................................................................................................136
5.1.3 Call initiation - UE-originating case..........................................................................................................138
5.1.3.1 Initial INVITE request.........................................................................................................................138
5.1.4 Call initiation - UE-terminating case.........................................................................................................141
5.1.4.1 Initial INVITE request.........................................................................................................................141
5.1.4.2 Reliable 18x Policy..............................................................................................................................144
5.1.4A Session modification..................................................................................................................................145
5.1.4A.0 General.................................................................................................................................................145
5.1.4A.1 Generating session modification request..............................................................................................145
5.1.4A.2 Receiving session modification request...............................................................................................145
5.1.5 Call release.................................................................................................................................................145
5.1.5A Precondition disabling policy.....................................................................................................................146
5.1.6 Emergency service.....................................................................................................................................146
5.1.6.1 General.................................................................................................................................................146
5.1.6.2 Initial emergency registration...............................................................................................................147
5.1.6.2A New initial emergency registration......................................................................................................148
5.1.6.3 Initial subscription to the registration-state event package..................................................................148
5.1.6.4 User-initiated emergency reregistration...............................................................................................148
5.1.6.5 Authentication......................................................................................................................................149
5.1.6.6 User-initiated emergency deregistration..............................................................................................149
5.1.6.7 Network-initiated emergency deregistration........................................................................................149

3GPP
Release 16 6 3GPP TS 24.229 V16.8.0 (2020-12)

5.1.6.8 Emergency session setup......................................................................................................................149

5.1.6.8.1 General............................................................................................................................................149
5.1.6.8.2 Emergency session set-up in case of no registration......................................................................150
5.1.6.8.3 Emergency session set-up within an emergency registration.........................................................152
5.1.6.8.4 Emergency session setup within a non-emergency registration.....................................................154
5.1.6.9 Emergency session release...................................................................................................................155
5.1.6.10 Successful or provisional response to a request not detected by the UE as relating to an
emergency session................................................................................................................................155
5.1.6.11 eCall type of emergency service..........................................................................................................156
5.1.6.11.1 General............................................................................................................................................156
5.1.6.11.2 Initial INVITE request....................................................................................................................157
5.1.6.11.3 Transfer of an updated MSD..........................................................................................................158
5.1.6.12 Current location discovery during an emergency call..........................................................................159
5.1.6.12.1 General............................................................................................................................................159
5.1.6.12.2 Current location information requested..........................................................................................159
5.1.6.12.3 Providing current location information..........................................................................................159
5.1.7 Void............................................................................................................................................................159
5.1.8 Void............................................................................................................................................................159
5.1.9 P-CSCF addresses management.................................................................................................................159
5.2 Procedures at the P-CSCF...............................................................................................................................160
5.2.1 General.......................................................................................................................................................160
5.2.2 Registration................................................................................................................................................164
5.2.2.1 General.................................................................................................................................................164
5.2.2.2 IMS AKA as a security mechanism.....................................................................................................170
5.2.2.3 SIP digest without TLS as a security mechanism................................................................................173
5.2.2.4 SIP digest with TLS as a security mechanism.....................................................................................174
5.2.2.5 NASS-IMS bundled authentication as a security mechanism..............................................................176
5.2.2.6 GPRS-IMS-Bundled authentication as a security mechanism.............................................................176
5.2.2.7 P-CSCF reconfigured to not accept registrations.................................................................................177
5.2.3 Subscription to the user's registration-state event package........................................................................177
5.2.3A Void............................................................................................................................................................178
5.2.3B SUBSCRIBE request.................................................................................................................................178
5.2.4 Registration of multiple public user identities...........................................................................................178
5.2.5 Deregistration.............................................................................................................................................180
5.2.5.1 User-initiated deregistration.................................................................................................................180
5.2.5.2 Network-initiated deregistration..........................................................................................................181
5.2.6 General treatment for all dialogs and standalone transactions excluding the REGISTER method...........181
5.2.6.1 Introduction..........................................................................................................................................181
5.2.6.2 Determination of UE-originated or UE-terminated case......................................................................181
5.2.6.3 Requests initiated by the UE................................................................................................................182
5.2.6.3.1 General for all requests...................................................................................................................182
5.2.6.3.2 General for all responses................................................................................................................184
5.2.6.3.2A Abnormal cases...............................................................................................................................184
5.2.6.3.3 Initial request for a dialog...............................................................................................................185
5.2.6.3.4 Responses to an initial request for a dialog....................................................................................187
5.2.6.3.5 Target refresh request for a dialog..................................................................................................188
5.2.6.3.6 Responses to a target refresh request for a dialog..........................................................................188
5.2.6.3.7 Request for a standalone transaction..............................................................................................189
5.2.6.3.8 Responses to a request for a standalone transaction.......................................................................190
5.2.6.3.9 Subsequent request other than a target refresh request...................................................................191
5.2.6.3.10 Responses to a subsequent request other than a target refresh request...........................................191
5.2.6.3.11 Request for an unknown method that does not relate to an existing dialog...................................191
5.2.6.3.12 Responses to a request for an unknown method that does not relate to an existing dialog............193
5.2.6.4 Requests terminated by the UE............................................................................................................193
5.2.6.4.1 General for all requests...................................................................................................................193
5.2.6.4.2 General for all responses................................................................................................................194
5.2.6.4.3 Initial request for a dialog...............................................................................................................194
5.2.6.4.4 Responses to an initial request for a dialog....................................................................................195
5.2.6.4.5 Target refresh request for a dialog..................................................................................................197
5.2.6.4.6 Responses to a target refresh request for a dialog..........................................................................197
5.2.6.4.7 Request for a standalone transaction..............................................................................................198

3GPP
Release 16 7 3GPP TS 24.229 V16.8.0 (2020-12)

5.2.6.4.8 Responses to a request for a standalone transaction.......................................................................199

5.2.6.4.9 Subsequent request other than a target refresh request...................................................................200
5.2.6.4.10 Responses to a subsequent request other than a target refresh request...........................................200
5.2.6.4.11 Request for an unknown method that does not relate to an existing dialog...................................201
5.2.6.4.12 Responses to a request for an unknown method that does not relate to an existing dialog............201
5.2.7 Initial INVITE............................................................................................................................................201
5.2.7.1 Introduction..........................................................................................................................................201
5.2.7.2 UE-originating case..............................................................................................................................201
5.2.7.3 UE-terminating case.............................................................................................................................203
5.2.7.4 Access network charging information..................................................................................................203
5.2.8 Call release.................................................................................................................................................203
5.2.8.1 P-CSCF-initiated call release...............................................................................................................203
5.2.8.1.1 Cancellation of a session currently being established....................................................................203
5.2.8.1.2 Release of an existing session........................................................................................................204
5.2.8.1.3 Abnormal cases...............................................................................................................................206
5.2.8.1.4 Release of the existing dialogs due to registration expiration and deletion of the security
association, IP association or TLS session.....................................................................................207
5.2.8.2 Call release initiated by any other entity..............................................................................................207
5.2.8.3 Session expiration................................................................................................................................207
5.2.9 Subsequent requests...................................................................................................................................207
5.2.9.1 UE-originating case..............................................................................................................................207
5.2.9.2 UE-terminating case.............................................................................................................................207
5.2.10 Emergency service.....................................................................................................................................207
5.2.10.1 General.................................................................................................................................................207
5.2.10.2 General treatment for all dialogs and standalone transactions excluding the REGISTER method –
requests from an unregistered user.......................................................................................................209
5.2.10.2A General treatment for all dialogs and standalone transactions excluding the REGISTER method –
requests to an unregistered user...........................................................................................................211
5.2.10.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method
after emergency registration.................................................................................................................211
5.2.10.4 General treatment for all dialogs and standalone transactions excluding the REGISTER method -
non-emergency registration..................................................................................................................214
5.2.10.5 Abnormal and rejection cases..............................................................................................................216
5.2.11 Void............................................................................................................................................................218
5.2.12 Resource sharing........................................................................................................................................218
5.2.13 Priority sharing...........................................................................................................................................218
5.3 Procedures at the I-CSCF................................................................................................................................218
5.3.0 General.......................................................................................................................................................218
5.3.1 Registration procedure...............................................................................................................................218
5.3.1.1 General.................................................................................................................................................218
5.3.1.2 Normal procedures...............................................................................................................................219
5.3.1.3 Abnormal cases....................................................................................................................................219
5.3.2 Initial requests............................................................................................................................................220
5.3.2.1 Normal procedures...............................................................................................................................220
5.3.2.1A Originating procedures for requests containing the "orig" parameter..................................................224
5.3.2.2 Abnormal cases....................................................................................................................................226
5.3.3 Void............................................................................................................................................................227
5.3.3.1 Void......................................................................................................................................................227
5.3.3.2 Void......................................................................................................................................................227
5.3.3.3 Void......................................................................................................................................................227
5.3.4 Void............................................................................................................................................................227
5.3.5 Subsequent requests...................................................................................................................................227
5.4 Procedures at the S-CSCF...............................................................................................................................227
5.4.0 General.......................................................................................................................................................227
5.4.1 Registration and authentication..................................................................................................................228
5.4.1.1 Introduction..........................................................................................................................................228
5.4.1.2 Initial registration and user-initiated reregistration..............................................................................230
5.4.1.2.1 Unprotected REGISTER................................................................................................................230
5.4.1.2.1A Challenge with IMS AKA as security mechanism.........................................................................232
5.4.1.2.1B Challenge with SIP digest as security mechanism.........................................................................232
5.4.1.2.1C Challenge with SIP digest with TLS as security mechanism.........................................................233

3GPP
Release 16 8 3GPP TS 24.229 V16.8.0 (2020-12)

5.4.1.2.1D Initial registration and user-initiated reregistration for NASS-IMS bundled authentication.........233
5.4.1.2.1E Initial registration and user-initiated reregistration for GPRS-IMS-Bundled authentication.........234
5.4.1.2.2 Protected REGISTER with IMS AKA as a security mechanism...................................................236
5.4.1.2.2A Protected REGISTER with SIP digest as a security mechanism....................................................239
5.4.1.2.2B Protected REGISTER with SIP digest with TLS as a security mechanism...................................242
5.4.1.2.2C NASS-IMS bundled authentication as a security mechanism........................................................242
5.4.1.2.2D GPRS-IMS-Bundled authentication as a security mechanism.......................................................242
5.4.1.2.2E Protected REGISTER – Authentication already performed...........................................................243
5.4.1.2.2F Successful registration....................................................................................................................244
5.4.1.2.3 Abnormal cases - general...............................................................................................................246
5.4.1.2.3A Abnormal cases – IMS AKA as security mechanism.....................................................................247
5.4.1.2.3B Abnormal cases – SIP digest as security mechanism.....................................................................248
5.4.1.2.3C Abnormal cases – SIP digest with TLS as security mechanism.....................................................248
5.4.1.2.3D Abnormal cases – NASS-IMS bundled authentication as security mechanism.............................249
5.4.1.2.3E Abnormal cases – GPRS-IMS-Bundled authentication as security mechanism............................249
5.4.1.3 Authentication and reauthentication.....................................................................................................249
5.4.1.4 User-initiated deregistration.................................................................................................................249
5.4.1.4.1 Normal cases...................................................................................................................................249
5.4.1.4.2 Abnormal cases - IMS AKA as security mechanism.....................................................................250
5.4.1.4.4 Abnormal cases – SIP digest with TLS as security mechanism.....................................................251
5.4.1.4.5 Abnormal cases – NASS-IMS bundled authentication as security mechanism.............................251
5.4.1.4.6 Abnormal cases – GPRS-IMS-Bundled authentication as security mechanism............................251
5.4.1.5 Network-initiated deregistration..........................................................................................................251
5.4.1.6 Network-initiated reauthentication.......................................................................................................253
5.4.1.7 Notification of Application Servers about registration status..............................................................254
5.4.1.7A Including contents in the body of the third-party REGISTER request................................................256
5.4.1.8 Service profile updates.........................................................................................................................256
5.4.2 Subscription and notification.....................................................................................................................257
5.4.2.1 Subscriptions to S-CSCF events..........................................................................................................257
5.4.2.1.1 Subscription to the event providing registration state....................................................................257
5.4.2.1.2 Notification about registration state................................................................................................259
5.4.2.1.3 Void................................................................................................................................................263
5.4.2.1.4 Void................................................................................................................................................263
5.4.2.1A Outgoing subscriptions to load-control event......................................................................................263
5.4.2.2 Other subscriptions...............................................................................................................................263
5.4.3 General treatment for all dialogs and standalone transactions excluding requests terminated by the S-
CSCF..........................................................................................................................................................263
5.4.3.1 Determination of UE-originated or UE-terminated case......................................................................263
5.4.3.2 Requests initiated by the served user...................................................................................................264
5.4.3.3 Requests terminated at the served user................................................................................................275
5.4.3.4 Original dialog identifier......................................................................................................................287
5.4.3.5 Void......................................................................................................................................................287
5.4.3.6 SIP digest authentication procedures for all SIP request methods initiated by the UE excluding
REGISTER...........................................................................................................................................287
5.4.3.6.1 General............................................................................................................................................287
5.4.3.6.2 Abnormal cases...............................................................................................................................289
5.4.4 Call initiation..............................................................................................................................................289
5.4.4.1 Initial INVITE......................................................................................................................................289
5.4.4.2 Subsequent requests.............................................................................................................................290
5.4.4.2.1 UE-originating case........................................................................................................................290
5.4.4.2.2 UE-terminating case.......................................................................................................................290
5.4.5 Call release.................................................................................................................................................291
5.4.5.1 S-CSCF-initiated session release.........................................................................................................291
5.4.5.1.1 Cancellation of a session currently being established....................................................................291
5.4.5.1.2 Release of an existing session........................................................................................................291
5.4.5.1.2A Release of the existing dialogs due to registration expiration........................................................293
5.4.5.1.3 Abnormal cases...............................................................................................................................293
5.4.5.2 Session release initiated by any other entity........................................................................................293
5.4.5.3 Session expiration................................................................................................................................293
5.4.6 Call-related requests...................................................................................................................................294
5.4.6.1 ReINVITE............................................................................................................................................294

3GPP
Release 16 9 3GPP TS 24.229 V16.8.0 (2020-12)

5.4.6.1.1 Determination of served user..........................................................................................................294

5.4.6.1.2 UE-originating case........................................................................................................................294
5.4.6.1.3 UE-terminating case.......................................................................................................................294
5.4.7 Void............................................................................................................................................................294
5.4.7A GRUU management...................................................................................................................................294
5.4.7A.1 Overview of GRUU operation.............................................................................................................294
5.4.7A.2 Representation of public GRUUs.........................................................................................................295
5.4.7A.3 Representation of temporary GRUUs..................................................................................................296
5.4.7A.4 GRUU recognition and validity...........................................................................................................296
5.4.8 Emergency service.....................................................................................................................................297
5.4.8.1 General.................................................................................................................................................297
5.4.8.2 Initial emergency registration or user-initiated emergency reregistration...........................................297
5.4.8.3 User-initiated emergency deregistration..............................................................................................298
5.4.8.4 Network-initiated emergency deregistration........................................................................................298
5.4.8.5 Network-initiated emergency reauthentication....................................................................................298
5.4.8.6 Subscription to the event providing registration state..........................................................................298
5.4.8.7 Notification of the registration state.....................................................................................................298
5.5 Procedures at the MGCF.................................................................................................................................299
5.5.1 General.......................................................................................................................................................299
5.5.2 Subscription and notification.....................................................................................................................300
5.5.3 Call initiation..............................................................................................................................................300
5.5.3.1 Initial INVITE......................................................................................................................................300
5.5.3.1.1 Calls originated from circuit-switched networks............................................................................300
5.5.3.1.2 Calls terminating in circuit-switched networks..............................................................................300
5.5.3.2 Subsequent requests.............................................................................................................................301
5.5.3.2.1 Calls originating in circuit-switched networks...............................................................................301
5.5.3.2.2 Calls terminating in circuit-switched networks..............................................................................302
5.5.4 Call release.................................................................................................................................................302
5.5.4.1 Call release initiated by a circuit-switched network............................................................................302
5.5.4.2 IM CN subsystem initiated call release................................................................................................302
5.5.4.3 MGW-initiated call release..................................................................................................................303
5.5.5 Call-related requests...................................................................................................................................303
5.5.5.1 Session modification............................................................................................................................303
5.5.5.1.0 General............................................................................................................................................303
5.5.5.1.1 Session modifications originating from circuit-switched networks...............................................303
5.5.5.1.2 Session modifications terminating in circuit-switched networks...................................................303
5.5.6 Further initial requests...............................................................................................................................304
5.6 Procedures at the BGCF..................................................................................................................................304
5.6.1 General.......................................................................................................................................................304
5.6.2 Common BGCF procedures.......................................................................................................................304
5.6.3 Specific procedures for INVITE requests and responses...........................................................................306
5.6.4 Specific procedures for subsequent requests and responses......................................................................307
5.7 Procedures at the Application Server (AS)......................................................................................................307
5.7.1 Common Application Server (AS) procedures..........................................................................................307
5.7.1.0 General.................................................................................................................................................307
5.7.1.1 Notification about registration status...................................................................................................307
5.7.1.2 Extracting charging correlation information........................................................................................309
5.7.1.3 Access-Network-Info and Visited-Network-ID...................................................................................309
5.7.1.3A Determination of the served user.........................................................................................................310
5.7.1.3A.1 General............................................................................................................................................310
5.7.1.3A.2 AS serving an originating user.......................................................................................................310
5.7.1.3A.3 AS serving a terminating user........................................................................................................310
5.7.1.3B Determination of the used registration.................................................................................................310
5.7.1.4 User identity verification at the AS......................................................................................................310
5.7.1.5 Request authorization...........................................................................................................................313
5.7.1.6 Event notification throttling.................................................................................................................313
5.7.1.7 Local numbering..................................................................................................................................313
5.7.1.7.1 Interpretation of the numbers in a non-international format..........................................................313
5.7.1.7.2 Translation of the numbers in a non-international format..............................................................314
5.7.1.8 GRUU assignment and usage...............................................................................................................314
5.7.1.9 Use of ICSI and IARI values................................................................................................................315

3GPP
Release 16 10 3GPP TS 24.229 V16.8.0 (2020-12)

5.7.1.10 Carrier selection...................................................................................................................................316

5.7.1.11 Tracing.................................................................................................................................................317
5.7.1.12 Delivery of original destination identity..............................................................................................317
5.7.1.13 CPC and OLI........................................................................................................................................317
5.7.1.14 Emergency transactions........................................................................................................................317
5.7.1.15 Protecting against attacks using 3xx responses....................................................................................318
5.7.1.16 Support of Roaming Architecture for Voice over IMS with Local Breakout......................................318
5.7.1.16.1 Preservation of parameters.............................................................................................................318
5.7.1.16.2 Preference for loopback routeing not to occur...............................................................................318
5.7.1.17 Delivery of network provided location information.............................................................................319
5.7.1.18 Delivery of MRB address information.................................................................................................319
5.7.1.19 Overload control...................................................................................................................................319
5.7.1.19.1 Outgoing subscriptions to load-control event.................................................................................319
5.7.1.19.2 Incoming subscriptions to load-control event.................................................................................320
5.7.1.20 Procedures in the AS for resource sharing...........................................................................................320
5.7.1.20.1 General............................................................................................................................................320
5.7.1.20.2 UE-originating case........................................................................................................................320
5.7.1.20.3 UE-terminating case.......................................................................................................................321
5.7.1.20.3.1 Determine resource sharing using the initial SDP offer.................................................................321
5.7.1.20.3.2 Determine resource sharing using the initial SDP answer..............................................................322
5.7.1.20.4 Updating the resource sharing options...........................................................................................322
5.7.1.20.5 Abnormal cases...............................................................................................................................322
5.7.1.21 Dynamic Service Interaction................................................................................................................323
5.7.1.22 Service access number translation........................................................................................................323
5.7.1.23 Procedures in the AS for priority sharing.............................................................................................323
5.7.1.23.1 General............................................................................................................................................323
5.7.1.23.2 Session originating procedures.......................................................................................................323
5.7.1.23.3 Session terminating procedures......................................................................................................324
5.7.1.24 Handling re-INVITE request collisions...............................................................................................324
5.7.1.25 User verification using the Identity header field..................................................................................324
5.7.1.25.1 General............................................................................................................................................324
5.7.1.25.2 Originating procedures...................................................................................................................324
5.7.1.25.3 Terminating procedures..................................................................................................................325
5.7.1.25.4 Procedures over the Ms reference point.........................................................................................325
5.7.1.26 Procedures in the AS for 3GPP PS data off.........................................................................................325
5.7.2 Application Server (AS) acting as terminating UA, or redirect server......................................................326
5.7.3 Application Server (AS) acting as originating UA....................................................................................326
5.7.4 Application Server (AS) acting as a SIP proxy..........................................................................................328
5.7.5 Application Server (AS) performing 3rd party call control.......................................................................329
5.7.5.1 General.................................................................................................................................................329
5.7.5.2 Call initiation........................................................................................................................................331
5.7.5.2.1 Initial INVITE................................................................................................................................331
5.7.5.2.2 Subsequent requests........................................................................................................................331
5.7.5.3 Call release...........................................................................................................................................331
5.7.5.4 Call-related requests.............................................................................................................................331
5.7.5.5 Further initial requests..........................................................................................................................332
5.7.5.6 Transcoding services invocation using third-party call control...........................................................332
5.7.6 Void............................................................................................................................................................332
5.8 Procedures at the MRFC..................................................................................................................................332
5.8.1 General.......................................................................................................................................................332
5.8.2 Call initiation..............................................................................................................................................333
5.8.2.1 Initial INVITE......................................................................................................................................333
5.8.2.1.1 MRFC-terminating case.................................................................................................................333
5.8.2.1.1.1 Introduction...............................................................................................................................333
5.8.2.1.2 MRFC-originating case..................................................................................................................334
5.8.2.2 Subsequent requests.............................................................................................................................334
5.8.2.2.1 Tones and announcements..............................................................................................................334
5.8.2.2.2 Transcoding....................................................................................................................................334
5.8.3 Call release.................................................................................................................................................334
5.8.3.1 S-CSCF-initiated call release...............................................................................................................334
5.8.3.1.1 Tones and announcements..............................................................................................................334

3GPP
Release 16 11 3GPP TS 24.229 V16.8.0 (2020-12)

5.8.3.2 MRFC-initiated call release.................................................................................................................334

5.8.3.2.1 Tones and announcements..............................................................................................................334
5.8.4 Call-related requests...................................................................................................................................335
5.8.4.1 ReINVITE............................................................................................................................................335
5.8.4.1.1 MRFC-terminating case.................................................................................................................335
5.8.4.1.2 MRFC-originating case..................................................................................................................335
5.8.4.2 REFER.................................................................................................................................................335
5.8.4.2.1 MRFC-terminating case.................................................................................................................335
5.8.4.2.2 MRFC-originating case..................................................................................................................335
5.8.4.2.3 REFER initiating a new session.....................................................................................................335
5.8.4.2.4 REFER replacing an existing session.............................................................................................335
5.8.4.3 INFO.....................................................................................................................................................335
5.8.5 Further initial requests...............................................................................................................................335
5.8A Procedures at the MRB....................................................................................................................................335
5.9 Void.................................................................................................................................................................336
5.9.1 Void............................................................................................................................................................336
5.10 Procedures at the IBCF....................................................................................................................................336
5.10.1 General.......................................................................................................................................................336
5.10.2 IBCF as an exit point.................................................................................................................................337
5.10.2.1 Registration..........................................................................................................................................337
5.10.2.1A General.................................................................................................................................................337
5.10.2.2 Initial requests......................................................................................................................................338
5.10.2.3 Subsequent requests.............................................................................................................................339
5.10.2.4 IBCF-initiated call release....................................................................................................................340
5.10.3 IBCF as an entry point...............................................................................................................................340
5.10.3.1 Registration..........................................................................................................................................340
5.10.3.1A General.................................................................................................................................................341
5.10.3.2 Initial requests......................................................................................................................................341
5.10.3.3 Subsequent requests.............................................................................................................................344
5.10.3.4 IBCF-initiated call release....................................................................................................................344
5.10.3.5 Abnormal cases....................................................................................................................................345
5.10.4 THIG functionality in the IBCF.................................................................................................................345
5.10.4.1 General.................................................................................................................................................345
5.10.4.2 Encryption for network topology hiding..............................................................................................346
5.10.4.3 Decryption for network topology hiding..............................................................................................347
5.10.5 IMS-ALG functionality in the IBCF..........................................................................................................348
5.10.6 Screening of SIP signalling........................................................................................................................349
5.10.6.1 General.................................................................................................................................................349
5.10.6.2 IBCF procedures for SIP header fields................................................................................................349
5.10.6.3 IBCF procedures for SIP message bodies............................................................................................350
5.10.7 Media transcoding control.........................................................................................................................350
5.10.8 Privacy protection at the trust domain boundary.......................................................................................350
5.10.9 Roaming architecture for voice over IMS with local breakout..................................................................351
5.10.10 HTTP procedures over the Ms reference point..........................................................................................351
5.10.10.1 General.................................................................................................................................................351
5.10.10.2 Procedures for an IBCF acting as an entry point.................................................................................351
5.10.10.3 Procedures for an IBCF acting as an exit point....................................................................................352
5.11 Procedures at the E-CSCF...............................................................................................................................352
5.11.1 General.......................................................................................................................................................352
5.11.2 UE originating case....................................................................................................................................353
5.11.3 Use of an LRF............................................................................................................................................356
5.11.4 Subscriptions to E-CSCF events................................................................................................................358
5.11.4.1 Subscription to the event providing dialog state..................................................................................358
5.11.4.2 Notification about dialog state.............................................................................................................358
5.11.4.3 Subscription to the presence event package.........................................................................................359
5.11.4.4 Notification about presence..................................................................................................................360
5.11.5 Current location discovery during an emergency call...............................................................................361
5.11.5.1 General.................................................................................................................................................361
5.11.5.2 Requesting current location informaton...............................................................................................361
5.11.5.3 Receiving current location informaton.................................................................................................361
5.12 Location Retrieval Function (LRF).................................................................................................................361

3GPP
Release 16 12 3GPP TS 24.229 V16.8.0 (2020-12)

5.12.1 General.......................................................................................................................................................361
5.12.2 Treatment of incoming initial requests for a dialog and standalone requests............................................361
5.12.3 Subscription and notification.....................................................................................................................363
5.12.3.1 Notification about dialog state.............................................................................................................363
5.12.3.2 Notification about UE location............................................................................................................364
5.13 ISC gateway function......................................................................................................................................364
5.13.1 General.......................................................................................................................................................364
5.13.2 ISC gateway function as an exit point.......................................................................................................365
5.13.2.1 Registration..........................................................................................................................................365
5.13.2.2 General.................................................................................................................................................365
5.13.2.3 Initial requests......................................................................................................................................365
5.13.2.4 Subsequent requests.............................................................................................................................367
5.13.2.5 Call release initiated by ISC gateway function....................................................................................367
5.13.3 ISC gateway function as an entry point.....................................................................................................367
5.13.3.1 Registration..........................................................................................................................................367
5.13.3.2 General.................................................................................................................................................367
5.13.3.3 Initial requests......................................................................................................................................368
5.13.3.4 Subsequent requests.............................................................................................................................369
5.13.3.5 Call release initiated by the ISC gateway function..............................................................................369
5.13.4 THIG functionality in the ISC gateway function.......................................................................................370
5.13.5 IMS-ALG functionality in the ISC gateway function................................................................................370
5.13.6 Screening of SIP signalling........................................................................................................................370
6 Application usage of SDP...................................................................................................................370
6.1 Procedures at the UE.......................................................................................................................................370
6.1.1 General.......................................................................................................................................................370
6.1.2 Handling of SDP at the originating UE.....................................................................................................372
6.1.3 Handling of SDP at the terminating UE.....................................................................................................375
6.1.4 Session modification..................................................................................................................................378
6.1.4.1 General.................................................................................................................................................378
6.1.4.2 Generating session modification request..............................................................................................378
6.1.4.3 Receiving session modification request...............................................................................................378
6.2 Procedures at the P-CSCF...............................................................................................................................378
6.3 Procedures at the S-CSCF...............................................................................................................................380
6.4 Procedures at the MGCF.................................................................................................................................380
6.4.1 Calls originating from circuit-switched networks......................................................................................380
6.4.2 Calls terminating in circuit-switched networks.........................................................................................381
6.4.3 Optimal Media Routeing (OMR)...............................................................................................................381
6.4.4 Explicit congestion control support in MGCF...........................................................................................381
6.5 Procedures at the MRFC..................................................................................................................................381
6.6 Procedures at the AS........................................................................................................................................381
6.6.1 General.......................................................................................................................................................381
6.6.2 Transcoding................................................................................................................................................382
6.6.3 AS procedures to support WebRTC media optimization procedure..........................................................382
6.7 Procedures at the IMS-ALG functionality.......................................................................................................383
6.7.1 IMS-ALG in IBCF.....................................................................................................................................383
6.7.1.1 General.................................................................................................................................................383
6.7.1.2 IMS-ALG in IBCF for support of ICE.................................................................................................383
6.7.1.2.1 General............................................................................................................................................383
6.7.1.2.2 IBCF full ICE procedures for UDP based streams.........................................................................383
6.7.1.2.2.1 General......................................................................................................................................383
6.7.1.2.2.2 IBCF receiving SDP offer.........................................................................................................383
6.7.1.2.2.3 IBCF sending SDP offer...........................................................................................................384
6.7.1.2.2.4 IBCF receiving SDP answer.....................................................................................................384
6.7.1.2.2.5 IBCF sending SDP answer........................................................................................................384
6.7.1.2.3 IBCF ICE lite procedures for UDP based streams.........................................................................384
6.7.1.2.4 ICE procedures for TCP based streams..........................................................................................385
6.7.1.2.4.1 General......................................................................................................................................385
6.7.1.2.4.2 IBCF receiving SDP offer.........................................................................................................385
6.7.1.2.4.3 IBCF sending SDP offer...........................................................................................................385
6.7.1.2.4.4 IBCF receiving SDP answer.....................................................................................................385
6.7.1.2.4.5 IBCF sending SDP answer........................................................................................................385

3GPP
Release 16 13 3GPP TS 24.229 V16.8.0 (2020-12)

6.7.1.3 IMS-ALG in IBCF for transcoding......................................................................................................385

6.7.1.4 IMS-ALG in IBCF for NA(P)T and NA(P)T-PT controlled by the IBCF...........................................386
6.7.1.4.1 General............................................................................................................................................386
6.7.1.5 IMS-ALG procedure in IBCF to support WebRTC media optimization procedure............................386
6.7.2 IMS-ALG in P-CSCF................................................................................................................................387
6.7.2.1 General.................................................................................................................................................387
6.7.2.2 IMS-ALG in P-CSCF for media plane security...................................................................................387
6.7.2.3 IMS-ALG in P-CSCF for explicit congestion control support............................................................391
6.7.2.3.1 General............................................................................................................................................391
6.7.2.3.2 Incoming SDP offer with ECN.......................................................................................................391
6.7.2.3.3 Incoming SDP offer without ECN..................................................................................................392
6.7.2.4 IMS-ALG in P-CSCF for Optimal Media Routeing (OMR)...............................................................392
6.7.2.5 IMS-ALG in P-CSCF for NA(P)T and NA(P)T-PT controlled by the P-CSCF..................................392
6.7.2.5.1 General............................................................................................................................................392
6.7.2.6 IMS-ALG in P-CSCF for support of hosted NAT...............................................................................393
6.7.2.6.1 General............................................................................................................................................393
6.7.2.6.2 Hosted NAT traversal for TCP based streams................................................................................393
6.7.2.7 IMS-ALG in P-CSCF for support of ICE............................................................................................393
6.7.2.7.1 General............................................................................................................................................393
6.7.2.7.2 P-CSCF full ICE procedures for UDP based streams....................................................................393
6.7.2.7.2.1 General......................................................................................................................................393
6.7.2.7.2.2 P-CSCF receiving SDP offer....................................................................................................394
6.7.2.7.2.3 P-CSCF sending SDP offer.......................................................................................................394
6.7.2.7.2.4 P-CSCF receiving SDP answer.................................................................................................394
6.7.2.7.2.5 P-CSCF sending SDP answer...................................................................................................394
6.7.2.7.3 P-CSCF ICE lite procedures for UDP based streams.....................................................................395
6.7.2.7.4 ICE procedures for TCP based streams..........................................................................................395
6.7.2.7.4.1 General......................................................................................................................................395
6.7.2.7.4.2 P-CSCF receiving SDP offer....................................................................................................395
6.7.2.7.4.3 P-CSCF sending SDP offer.......................................................................................................395
6.7.2.7.4.4 P-CSCF receiving SDP answer.................................................................................................395
6.7.2.7.4.5 P-CSCF sending SDP answer...................................................................................................395
6.7.2.8 IMS-ALG in P-CSCF for transcoding.................................................................................................395
6.7.3 IMS-ALG in ISC gateway function...........................................................................................................396
6.7.3.1 General.................................................................................................................................................396
6.7.3.2 IMS-ALG in application gateway function for support of ICE...........................................................396
7 Extensions within the present document.............................................................................................396
7.1 SIP methods defined within the present document..........................................................................................396
7.2 SIP header fields defined within the present document...................................................................................396
7.2.0 General.......................................................................................................................................................396
7.2.1 Void............................................................................................................................................................397
7.2.2 Void............................................................................................................................................................397
7.2.3 Void............................................................................................................................................................397
7.2.4 Void............................................................................................................................................................397
7.2.5 Void............................................................................................................................................................397
7.2.6 Void............................................................................................................................................................397
7.2.7 Void............................................................................................................................................................397
7.2.8 Void............................................................................................................................................................397
7.2.9 Void............................................................................................................................................................397
7.2.10 Void............................................................................................................................................................397
7.2.11 Definition of Restoration-Info header field...............................................................................................397
7.2.11.1 Introduction..........................................................................................................................................397
7.2.11.2 Applicability statement for the Restoration-Info header field..............................................................397
7.2.11.3 Usage of the Restoration-Info header field..........................................................................................398
7.2.11.4 Procedures at the UA............................................................................................................................398
7.2.11.5 Procedures at the proxy........................................................................................................................398
7.2.11.6 Security considerations........................................................................................................................398
7.2.11.7 Syntax...................................................................................................................................................398
7.2.11.8 Examples of usage................................................................................................................................398
7.2.12 Relayed-Charge header field......................................................................................................................399
7.2.12.1 Introduction..........................................................................................................................................399

3GPP
Release 16 14 3GPP TS 24.229 V16.8.0 (2020-12)

7.2.12.2 Applicability statement for the Relayed-Charge header field..............................................................399

7.2.12.3 Usage of the Relayed-Charge header field...........................................................................................399
7.2.12.4 Procedures at the UA............................................................................................................................399
7.2.12.5 Procedures at the proxy........................................................................................................................400
7.2.12.6 Security considerations........................................................................................................................400
7.2.12.7 Syntax...................................................................................................................................................400
7.2.12.8 Examples of usage................................................................................................................................400
7.2.13 Resource-Share header field......................................................................................................................400
7.2.13.1 Introduction..........................................................................................................................................400
7.2.13.2 Applicability statement for the Resource-Share header field...............................................................401
7.2.13.3 Usage of the Resource-Share header field...........................................................................................401
7.2.13.4 Procedures at the UA............................................................................................................................401
7.2.13.5 Procedures at the proxy........................................................................................................................401
7.2.13.6 Security considerations........................................................................................................................401
7.2.13.7 Syntax...................................................................................................................................................401
7.2.13.8 Operation..............................................................................................................................................402
7.2.13.8.1 General............................................................................................................................................402
7.2.13.8.2 The "origin" header field parameter...............................................................................................402
7.2.13.8.3 The "rules" header field parameter.................................................................................................402
7.2.13.8.4 The "timestamp" header field parameter........................................................................................403
7.2.13.9 Examples of usage................................................................................................................................403
7.2.13.9.1 Example overview..........................................................................................................................403
7.2.13.9.2 The P-CSCF indicates in the REGISTER request that P-CSCF supports receiving information
about resource sharing....................................................................................................................403
7.2.13.9.3 The application server sends information about potential resource sharing to the P-CSCF..........404
7.2.13.9.4 The P-CSCF extracts resource sharing information for media-streams.........................................404
7.2.14 Definition of Service-Interact-Info header field........................................................................................405
7.2.14.1 Introduction..........................................................................................................................................405
7.2.14.2 Applicability statement for the Service-Interact-Info header field......................................................405
7.2.14.3 Usage of the Service-Interact-Info header field...................................................................................405
7.2.14.4 Procedures at the UA............................................................................................................................406
7.2.14.5 Procedures at the proxy........................................................................................................................406
7.2.14.6 Security considerations........................................................................................................................406
7.2.14.7 Syntax...................................................................................................................................................406
7.2.15 Definition of Cellular-Network-Info header field......................................................................................406
7.2.15.1 Introduction..........................................................................................................................................406
7.2.15.2 Applicability statement for the Cellular-Network-Info header field....................................................406
7.2.15.3 Usage of the Cellular-Network-Info header field................................................................................406
7.2.15.4 Procedures at the UA............................................................................................................................408
7.2.15.5 Procedures at the proxy........................................................................................................................408
7.2.15.6 Security considerations........................................................................................................................408
7.2.15.7 Syntax...................................................................................................................................................408
7.2.16 Priority-Share header field.........................................................................................................................409
7.2.16.1 Introduction..........................................................................................................................................409
7.2.16.2 Applicability statement for the Priority-Share header field.................................................................409
7.2.16.3 Usage of the Priority-Share header field..............................................................................................409
7.2.16.4 Procedures at the UA............................................................................................................................409
7.2.16.5 Procedures at the proxy........................................................................................................................410
7.2.16.6 Security considerations........................................................................................................................410
7.2.16.7 Syntax...................................................................................................................................................410
7.2.16.8 Examples of usage................................................................................................................................410
7.2.17 Definition of Response-Source header field..............................................................................................410
7.2.17.1 Introduction..........................................................................................................................................410
7.2.17.2 Applicability statement for the Response-Source header field............................................................410
7.2.17.3 Usage of the Response-Source header field.........................................................................................411
7.2.17.4 Procedures at the UA............................................................................................................................411
7.2.17.5 Procedures at the proxy........................................................................................................................411
7.2.17.6 Security considerations........................................................................................................................411
7.2.17.7 Syntax...................................................................................................................................................411
7.2.18 Definition of Attestation-Info header field................................................................................................413
7.2.18.1 Introduction..........................................................................................................................................413

3GPP
Release 16 15 3GPP TS 24.229 V16.8.0 (2020-12)

7.2.18.2 Applicability statement for the Attestation-Info header field..............................................................413

7.2.18.3 Usage of the Attestation-Info header field...........................................................................................413
7.2.18.4 Procedures at the UA............................................................................................................................414
7.2.18.5 Procedures at the proxy........................................................................................................................414
7.2.18.6 Security considerations........................................................................................................................414
7.2.18.7 Syntax...................................................................................................................................................414
7.2.18.8 Examples of usage................................................................................................................................414
7.2.19 Definition of Origination-Id header field...................................................................................................414
7.2.19.1 Introduction..........................................................................................................................................414
7.2.19.2 Applicability statement for the Origination-Id header field.................................................................415
7.2.19.3 Usage of the Origination-Id header field..............................................................................................415
7.2.19.4 Procedures at the UA............................................................................................................................415
7.2.19.5 Procedures at the proxy........................................................................................................................415
7.2.19.6 Security considerations........................................................................................................................415
7.2.19.7 Syntax...................................................................................................................................................415
7.2.19.8 Examples of usage................................................................................................................................415
7.2.20 Definition of Additional-Identity header field...........................................................................................416
7.2.20.1 Introduction..........................................................................................................................................416
7.2.20.2 Applicability statement for the Additional-Identity header field.........................................................416
7.2.20.3 Usage of the Additional-Identity header field......................................................................................416
7.2.20.4 Procedures at the UA............................................................................................................................416
7.2.20.5 Procedures at the proxy........................................................................................................................417
7.2.20.6 Security considerations........................................................................................................................417
7.2.20.7 Syntax...................................................................................................................................................417
7.2.20.8 Examples of usage................................................................................................................................417
7.2A Extensions to SIP header fields defined within the present document............................................................417
7.2A.1 Extension to WWW-Authenticate header field.........................................................................................417
7.2A.1.1 Introduction..........................................................................................................................................417
7.2A.1.2 Syntax...................................................................................................................................................417
7.2A.1.3 Operation..............................................................................................................................................418
7.2A.2 Extension to Authorization header field....................................................................................................418
7.2A.2.1 Introduction..........................................................................................................................................418
7.2A.2.2 Syntax...................................................................................................................................................418
7.2A.2.2.1 integrity-protected...........................................................................................................................418
7.2A.2.3 Operation..............................................................................................................................................418
7.2A.3 Tokenized-by header field parameter definition (various header fields)...................................................419
7.2A.3.1 Introduction..........................................................................................................................................419
7.2A.3.2 Syntax...................................................................................................................................................419
7.2A.3.3 Operation..............................................................................................................................................419
7.2A.4 P-Access-Network-Info header field.........................................................................................................420
7.2A.4.1 Introduction..........................................................................................................................................420
7.2A.4.2 Syntax...................................................................................................................................................420
7.2A.4.3 Additional coding rules for P-Access-Network-Info header field.......................................................421
7.2A.5 P-Charging-Vector header field.................................................................................................................425
7.2A.5.1 Introduction..........................................................................................................................................425
7.2A.5.2 Syntax...................................................................................................................................................425
7.2A.5.2.1 General............................................................................................................................................425
7.2A.5.2.2 GPRS as IP-CAN............................................................................................................................427
7.2A.5.2.3 Evolved Packet Core (EPC) via WLAN as IP-CAN......................................................................427
7.2A.5.2.4 xDSL as IP-CAN............................................................................................................................428
7.2A.5.2.5 DOCSIS as IP-CAN.......................................................................................................................428
7.2A.5.2.6 cdma2000® packet data subsystem as IP-CAN..............................................................................428
7.2A.5.2.7 EPS as IP-CAN...............................................................................................................................429
7.2A.5.2.8 Ethernet as IP-CAN........................................................................................................................429
7.2A.5.2.9 Fiber as IP-CAN.............................................................................................................................429
7.2A.5.2.10 5GS as IP-CAN..............................................................................................................................429
7.2A.5.3 Operation..............................................................................................................................................430
7.2A.6 Orig parameter definition...........................................................................................................................430
7.2A.6.1 Introduction..........................................................................................................................................430
7.2A.6.2 Syntax...................................................................................................................................................430
7.2A.6.3 Operation..............................................................................................................................................430

3GPP
Release 16 16 3GPP TS 24.229 V16.8.0 (2020-12)

7.2A.7 Extension to Security-Client, Security-Server and Security-Verify header fields.....................................430

7.2A.7.1 Introduction..........................................................................................................................................430
7.2A.7.2 Syntax...................................................................................................................................................430
7.2A.7.2.1 General............................................................................................................................................430
7.2A.7.2.2 "mediasec" header field parameter.................................................................................................431
7.2A.7.3 Operation..............................................................................................................................................431
7.2A.7.4 IANA registration.................................................................................................................................432
7.2A.7.4.1 "mediasec" header field parameter.................................................................................................432
7.2A.7.4.2 "sdes-srtp" security mechanism......................................................................................................432
7.2A.7.4.3 "msrp-tls" security mechanism.......................................................................................................432
7.2A.7.4.4 "bfcp-tls" security mechanism........................................................................................................433
7.2A.7.4.5 "udptl-dtls" security mechanism.....................................................................................................433
7.2A.8 IMS Communication Service Identifier (ICSI)..........................................................................................434
7.2A.8.1 Introduction..........................................................................................................................................434
7.2A.8.2 Coding of the ICSI...............................................................................................................................434
7.2A.9 IMS Application Reference Identifier (IARI)............................................................................................434
7.2A.9.1 Introduction..........................................................................................................................................434
7.2A.9.2 Coding of the IARI...............................................................................................................................435
7.2A.10 "phone-context" tel URI parameter............................................................................................................435
7.2A.10.1 Introduction..........................................................................................................................................435
7.2A.10.2 Syntax...................................................................................................................................................435
7.2A.10.3 Additional coding rules for "phone-context" tel URI parameter.........................................................435
7.2A.11 Void............................................................................................................................................................436
7.2A.11.1 Void......................................................................................................................................................436
7.2A.11.2 Void......................................................................................................................................................436
7.2A.11.3 Void......................................................................................................................................................436
7.2A.12 CPC and OLI tel URI parameter definition...............................................................................................436
7.2A.12.1 Introduction..........................................................................................................................................436
7.2A.12.2 Syntax...................................................................................................................................................436
7.2A.12.3 Operation..............................................................................................................................................437
7.2A.13 "sos" SIP URI parameter............................................................................................................................437
7.2A.13.1 Introduction..........................................................................................................................................437
7.2A.13.2 Syntax...................................................................................................................................................438
7.2A.13.3 Operation..............................................................................................................................................438
7.2A.14 P-Associated-URI header field..................................................................................................................438
7.2A.15 Void............................................................................................................................................................438
7.2A.16 Void............................................................................................................................................................438
7.2A.16.1 Void......................................................................................................................................................438
7.2A.16.2 Void......................................................................................................................................................438
7.2A.16.3 Void......................................................................................................................................................438
7.2A.17 "premium-rate" tel URI parameter definition............................................................................................438
7.2A.17.1 Introduction..........................................................................................................................................438
7.2A.17.2 Syntax...................................................................................................................................................438
7.2A.17.3 Operation..............................................................................................................................................439
7.2A.17.4 IANA registration.................................................................................................................................439
7.2A.18 Reason header field....................................................................................................................................439
7.2A.18.1 Introduction..........................................................................................................................................439
7.2A.18.2 Syntax...................................................................................................................................................439
7.2A.18.3 IANA registration of EMM protocol value..........................................................................................440
7.2A.18.4 IANA registration of ESM protocol value...........................................................................................440
7.2A.18.5 IANA registration of S1AP radio network layer protocol value..........................................................440
7.2A.18.6 IANA registration of S1AP transport layer protocol value..................................................................440
7.2A.18.7 IANA registration of S1AP non-access stratum protocol value..........................................................441
7.2A.18.8 IANA registration of S1AP miscellaneous protocol value..................................................................441
7.2A.18.8A IANA registration of S1AP protocol protocol value............................................................................441
7.2A.18.9 IANA registration of DIAMETER protocol value...............................................................................441
7.2A.18.10 IANA registration of IKEV2 protocol value........................................................................................442
7.2A.18.11 IANA registration of RELEASE_CAUSE protocol value...................................................................442
7.2A.18.11.1 Introduction....................................................................................................................................442
7.2A.18.11.2 IANA considerations......................................................................................................................442
7.2A.18.12 IANA registration of FAILURE_CAUSE protocol value...................................................................443

3GPP
Release 16 17 3GPP TS 24.229 V16.8.0 (2020-12)

7.2A.18.12.1 Introduction....................................................................................................................................443
7.2A.18.12.2 IANA considerations......................................................................................................................443
7.2A.19 Thig-path....................................................................................................................................................443
7.2A.19.1 Introduction..........................................................................................................................................443
7.2A.19.2 Coding of the thig-path........................................................................................................................443
7.2A.20 "verstat" tel URI parameter definition.......................................................................................................444
7.2A.20.1 Introduction..........................................................................................................................................444
7.2A.20.2 Syntax...................................................................................................................................................444
7.2A.20.3 Operation..............................................................................................................................................444
7.2A.20.4 IANA registration.................................................................................................................................444
7.2A.21 Extension to "isub-encoding" tel URIparameter........................................................................................445
7.2A.21.1 Introduction..........................................................................................................................................445
7.2A.21.2 Syntax...................................................................................................................................................445
7.2A.21.3 IANA registration of "user-specified" tel URI parameter value..........................................................445
7.2A.21.3.1 Introduction....................................................................................................................................445
7.2A.21.3.2 IANA considerations......................................................................................................................445
7.3 Option-tags defined within the present document...........................................................................................446
7.4 Status-codes defined within the present document..........................................................................................446
7.5 Session description types defined within the present document.....................................................................446
7.5.1 General.......................................................................................................................................................446
7.5.2 End-to-access-edge media plane security..................................................................................................446
7.5.2.1 General.................................................................................................................................................446
7.5.2.2 Syntax...................................................................................................................................................446
7.5.2.3 IANA registration.................................................................................................................................447
7.5.3 Optimal Media Routeing (OMR) attributes...............................................................................................447
7.5.3.1 General.................................................................................................................................................447
7.5.3.2 Semantics.............................................................................................................................................447
7.5.3.3 Syntax...................................................................................................................................................448
7.5.3.4 IANA registration.................................................................................................................................449
7.5.3.4.1 visited-realm attribute.....................................................................................................................449
7.5.3.4.2 secondary-realm attribute...............................................................................................................450
7.5.3.4.3 omr-s-cksum attribute.....................................................................................................................450
7.5.3.4.4 omr-m-cksum attribute...................................................................................................................450
7.5.3.4.5 omr-codecs attribute.......................................................................................................................451
7.5.3.4.6 omr-m-att attribute..........................................................................................................................451
7.5.3.4.7 omr-s-att attribute...........................................................................................................................451
7.5.3.4.8 omr-m-bw attribute.........................................................................................................................451
7.5.3.4.9 omr-s-bw attribute..........................................................................................................................452
7.5.4 Media plane optimization for WebRTC.....................................................................................................452
7.5.4.1 General.................................................................................................................................................452
7.5.4.2 Semantics.............................................................................................................................................452
7.5.4.3 Syntax...................................................................................................................................................453
7.5.4.4 IANA registration.................................................................................................................................454
7.5.4.4.1 tra-contact.......................................................................................................................................454
7.5.4.4.2 tra-m-line........................................................................................................................................454
7.5.4.4.3 tra-att...............................................................................................................................................454
7.5.4.4.4 tra-bw..............................................................................................................................................454
7.5.4.4.5 tra-SCTP-association......................................................................................................................455
7.5.4.4.6 tra- media-line-number...................................................................................................................455
7.5.5 Void............................................................................................................................................................455
7.6 3GPP IM CN subsystem XML body...............................................................................................................455
7.6.1 General.......................................................................................................................................................455
7.6.2 Document Type Definition........................................................................................................................456
7.6.3 XML Schema description..........................................................................................................................456
7.6.4 MIME type definition................................................................................................................................457
7.6.4.1 Introduction..........................................................................................................................................457
7.6.4.2 Syntax...................................................................................................................................................457
7.6.4.3 Operation..............................................................................................................................................458
7.6.5 IANA Registration.....................................................................................................................................458
7.7 SIP timers........................................................................................................................................................459
7.8 IM CN subsystem timers.................................................................................................................................460

3GPP
Release 16 18 3GPP TS 24.229 V16.8.0 (2020-12)

7.9 Media feature tags defined within the current document................................................................................462

7.9.1 General.......................................................................................................................................................462
7.9.2 Definition of media feature tag g.3gpp.icsi-ref..........................................................................................462
7.9.3 Definition of media feature tag g.3gpp.iari-ref..........................................................................................462
7.9.4 Void............................................................................................................................................................463
7.9.5 Void............................................................................................................................................................463
7.9.6 Void............................................................................................................................................................463
7.9.7 Definition of media feature tag g.3gpp.registration-token.........................................................................463
7.9.8 Definition of media feature tag g.3gpp.ps-data-off....................................................................................464
7.9.9 Definition of media feature tag g.3gpp.rlos...............................................................................................464
7.9A Feature-capability indicators defined within the current document................................................................465
7.9A.1 General.......................................................................................................................................................465
7.9A.2 Definition of feature-capability indicator g.3gpp.icsi-ref..........................................................................465
7.9A.3 Definition of feature-capability indicators g.3gpp.trf................................................................................465
7.9A.4 Definition of feature-capability indicator g.3gpp.loopback.......................................................................466
7.9A.5 Definition of feature-capability indicator g.3gpp.home-visited.................................................................466
7.9A.6 Definition of feature-capability indicator g.3gpp.mrb...............................................................................467
7.9A.7 Void............................................................................................................................................................468
7.9A.8 Definition of feature-capability indicator g.3gpp.registration-token.........................................................468
7.9A.9 Definition of feature-capability indicator g.3gpp.thig-path.......................................................................468
7.9A.10 Definition of feature-capability indicator g.3gpp.priority-share................................................................469
7.9A.11 Definition of feature-capability indicator g.3gpp.verstat...........................................................................469
7.9A.12 Definition of feature-capability indicator g.3gpp.anbr..............................................................................470
7.10 Reg-event package extensions defined within the current document..............................................................470
7.10.1 General.......................................................................................................................................................470
7.10.2 Reg-Event package extension to transport wildcarded public user identities............................................470
7.10.2.1 Structure and data semantics................................................................................................................470
7.10.2.2 XML Schema.......................................................................................................................................471
7.10.3 Reg-event package extension for policy transport.....................................................................................471
7.10.3.1 Scope....................................................................................................................................................471
7.10.3.2 Structure and data semantics................................................................................................................471
7.10.3.3 XML Schema.......................................................................................................................................472
7.11 URNs defined within the present document....................................................................................................472
7.11.1 Country specific emergency service URN.................................................................................................472
7.11.1.1 Introduction..........................................................................................................................................472
7.11.1.2 Syntax...................................................................................................................................................473
7.11.1.3 Operation..............................................................................................................................................473
7.11.1.4 Void......................................................................................................................................................473
7.11.2 ICSI value for RLOS.................................................................................................................................473
7.11.2.1 Introduction..........................................................................................................................................473
7.11.2.2 URN.................................................................................................................................................................473
7.11.2.3 Description.......................................................................................................................................................473
7.11.2.4 Reference.........................................................................................................................................................473
7.11.2.5 Contact.............................................................................................................................................................474
7.11.2.6 Registration of subtype....................................................................................................................................474
7.11.2.7 Remarks...........................................................................................................................................................474
7.12 Info package definitions and associated MIME type definitions....................................................................474
7.12.1 DTMF info package and session-info MIME type....................................................................................474
7.12.1.1 DTMF info package.............................................................................................................................474
7.12.1.1.1 General............................................................................................................................................474
7.12.1.1.2 Overall description.........................................................................................................................474
7.12.1.1.3 Applicability...................................................................................................................................474
7.12.1.1.4 Info package name..........................................................................................................................474
7.12.1.1.5 Info package parameters.................................................................................................................474
7.12.1.1.6 SIP option tags................................................................................................................................475
7.12.1.1.7 INFO message body parts...............................................................................................................475
7.12.1.1.8 Info package usage restrictions.......................................................................................................475
7.12.1.1.9 Rate of INFO requests....................................................................................................................475
7.12.1.1.10 Info package security considerations..............................................................................................475
7.12.1.2 Overlap digit message body.................................................................................................................475
7.12.1.2.1 Scope..............................................................................................................................................475

3GPP
Release 16 19 3GPP TS 24.229 V16.8.0 (2020-12)

7.12.1.2.2 MIME type.....................................................................................................................................475

7.12.1.2.3 ABNF..............................................................................................................................................475
7.12.1.2.4 IANA registration template............................................................................................................476
7.12.1.3 Implementation details and examples..................................................................................................477
7.12.2 g.3gpp.current-location-discovery info package and request-for-current-location body..........................477
7.12.2.1 g.3gpp.current-location-discovery info package..................................................................................477
7.12.2.1.1 General............................................................................................................................................477
7.12.2.1.2 Overall description.........................................................................................................................477
7.12.2.1.3 Applicability...................................................................................................................................477
7.12.2.1.4 Info package name..........................................................................................................................478
7.12.2.1.5 Info package parameters.................................................................................................................478
7.12.2.1.6 SIP option tags................................................................................................................................478
7.12.2.1.7 INFO message body parts...............................................................................................................478
7.12.2.1.8 Info package usage restrictions.......................................................................................................478
7.12.2.1.9 Rate of INFO requests....................................................................................................................479
7.12.2.1.10 Info package security considerations..............................................................................................479
7.12.2.2 Request-for-current-location body.......................................................................................................479
7.12.2.2.1 General............................................................................................................................................479
7.12.2.2.2 XML schema..................................................................................................................................479
7.12.2.2.3 Additional syntax rules...................................................................................................................480
7.12.2.2.4 Semantic.........................................................................................................................................481
7.12.2.2.5 IANA registration...........................................................................................................................481
7.13 JSON Web Token claims defined within the present document.....................................................................482
7.13.1 General.......................................................................................................................................................482
7.13.2 3GPP-WAF................................................................................................................................................483
7.13.3 3GPP-WWSF.............................................................................................................................................483
7.13.4 identityHeader............................................................................................................................................483
7.13.5 verstatValue...............................................................................................................................................483
7.13.6 identityHeaders..........................................................................................................................................483
7.13.7 divResult....................................................................................................................................................483
8 SIP compression.................................................................................................................................484
8.1 SIP compression procedures at the UE............................................................................................................484
8.1.1 SIP compression.........................................................................................................................................484
8.1.2 Compression of SIP requests and responses transmitted to the P-CSCF...................................................484
8.1.3 Decompression of SIP requests and responses received from the P-CSCF...............................................485
8.2 SIP compression procedures at the P-CSCF....................................................................................................485
8.2.1 SIP compression.........................................................................................................................................485
8.2.2 Compression of SIP requests and responses transmitted to the UE...........................................................485
8.2.3 Decompression of SIP requests and responses received from the UE.......................................................486
9 IP-Connectivity Access Network aspects when connected to the IM CN subsystem..........................486
9.1 Introduction.....................................................................................................................................................486
9.2 Procedures at the UE.......................................................................................................................................486
9.2.1 Connecting to the IP-CAN and P-CSCF discovery...................................................................................486
9.2.2 Handling of the IP-CAN............................................................................................................................487
9.2.2A P-CSCF restoration procedure...................................................................................................................487
9.2.3 Special requirements applying to forked responses...................................................................................487
10 Media control.....................................................................................................................................488
10.1 General.............................................................................................................................................................488
10.2 Procedures at the AS........................................................................................................................................488
10.2.1 General.......................................................................................................................................................488
10.2.2 Tones and announcements.........................................................................................................................488
10.2.2.1 General.................................................................................................................................................488
10.2.2.2 Basic network media services with SIP...............................................................................................489
10.2.2.3 SIP interface to VoiceXML media services.........................................................................................489
10.2.2.4 Media control channel framework and packages.................................................................................489
10.2.3 Ad-hoc conferences....................................................................................................................................489
10.2.3.1 General.................................................................................................................................................489
10.2.3.2 Basic network media services with SIP...............................................................................................489
10.2.3.3 Media control channel framework and packages.................................................................................489
10.2.4 Transcoding................................................................................................................................................490

3GPP
Release 16 20 3GPP TS 24.229 V16.8.0 (2020-12)

10.2.4.1 General.................................................................................................................................................490
10.2.4.2 Basic network media services with SIP...............................................................................................490
10.2.4.3 Media control channel framework and packages.................................................................................490
10.3 Procedures at the MRFC..................................................................................................................................490
10.3.1 General.......................................................................................................................................................490
10.3.2 Tones and announcements.........................................................................................................................490
10.3.2.1 General.................................................................................................................................................490
10.3.2.2 Basic network media services with SIP...............................................................................................491
10.3.2.3 SIP interface to VoiceXML media services.........................................................................................491
10.3.2.4 Media control channel framework and packages.................................................................................491
10.3.3 Ad-hoc conferences....................................................................................................................................491
10.3.3.1 General.................................................................................................................................................491
10.3.3.2 Basic network media services with SIP...............................................................................................491
10.3.3.3 Media control channel framework and packages.................................................................................491
10.3.4 Transcoding................................................................................................................................................492
10.3.4.1 General.................................................................................................................................................492
10.3.4.2 Basic network media services with SIP...............................................................................................492
10.3.4.3 Media control channel framework and packages.................................................................................492
10.4 Procedures at the MRB....................................................................................................................................492

Annex A (normative): Profiles of IETF RFCs for 3GPP usage...............................................................493

A.1 Profiles...............................................................................................................................................493
A.1.1 Relationship to other specifications.................................................................................................................493
A.1.2 Introduction to methodology within this profile..............................................................................................493
A.1.3 Roles................................................................................................................................................................495
A.2 Profile definition for the Session Initiation Protocol as used in the present document........................501
A.2.1 User agent role.................................................................................................................................................501
A.2.1.1 Introduction................................................................................................................................................501
A.2.1.2 Major capabilities.......................................................................................................................................502
A.2.1.3 PDUs..........................................................................................................................................................515
A.2.1.4 PDU parameters.........................................................................................................................................516
A.2.1.4.1 Status-codes..........................................................................................................................................516
A.2.1.4.2 ACK method........................................................................................................................................519
A.2.1.4.3 BYE method.........................................................................................................................................521
A.2.1.4.4 CANCEL method.................................................................................................................................529
A.2.1.4.5 Void......................................................................................................................................................532
A.2.1.4.6 INFO method........................................................................................................................................532
A.2.1.4.7 INVITE method....................................................................................................................................539
A.2.1.4.7A MESSAGE method..............................................................................................................................554
A.2.1.4.8 NOTIFY method..................................................................................................................................563
A.2.1.4.9 OPTIONS method................................................................................................................................571
A.2.1.4.10 PRACK method....................................................................................................................................580
A.2.1.4.10A PUBLISH method................................................................................................................................587
A.2.1.4.11 REFER method....................................................................................................................................597
A.2.1.4.12 REGISTER method..............................................................................................................................606
A.2.1.4.13 SUBSCRIBE method...........................................................................................................................614
A.2.1.4.14 UPDATE method.................................................................................................................................624
A.2.2 Proxy role........................................................................................................................................................631
A.2.2.1 Introduction................................................................................................................................................631
A.2.2.2 Major capabilities.......................................................................................................................................632
A.2.2.3 PDUs..........................................................................................................................................................641
A.2.2.4 PDU parameters.........................................................................................................................................642
A.2.2.4.1 Status-codes..........................................................................................................................................642
A.2.2.4.2 ACK method........................................................................................................................................646
A.2.2.4.3 BYE method.........................................................................................................................................648
A.2.2.4.4 CANCEL method.................................................................................................................................656
A.2.2.4.5 Void......................................................................................................................................................659
A.2.2.4.6 INFO method........................................................................................................................................659
A.2.2.4.7 INVITE method....................................................................................................................................666
A.2.2.4.7A MESSAGE method..............................................................................................................................681

3GPP
Release 16 21 3GPP TS 24.229 V16.8.0 (2020-12)

A.2.2.4.8 NOTIFY method..................................................................................................................................691

A.2.2.4.9 OPTIONS method................................................................................................................................699
A.2.2.4.10 PRACK method....................................................................................................................................708
A.2.2.4.10A PUBLISH method................................................................................................................................716
A.2.2.4.11 REFER method....................................................................................................................................726
A.2.2.4.12 REGISTER method..............................................................................................................................736
A.2.2.4.13 SUBSCRIBE method...........................................................................................................................745
A.2.2.4.14 UPDATE method.................................................................................................................................755
A.3 Profile definition for the Session Description Protocol as used in the present document....................762
A.3.1 Introduction.....................................................................................................................................................762
A.3.2 User agent role.................................................................................................................................................763
A.3.2.1 Major capabilities.......................................................................................................................................764
A.3.2.2 SDP types...................................................................................................................................................767
A.3.2.3 Void............................................................................................................................................................774
A.3.2.4 Void............................................................................................................................................................774
A.3.3 Proxy role........................................................................................................................................................774
A.3.3.1 Major capabilities.......................................................................................................................................775
A.3.3.2 SDP types...................................................................................................................................................777
A.3.3.3 Void............................................................................................................................................................783
A.3.3.4 Void............................................................................................................................................................783
A.4 Profile definition for other message bodies as used in the present document.....................................783
Annex B (normative): IP-Connectivity Access Network specific concepts when using GPRS to
access IM CN subsystem............................................................................784
B.1 Scope..................................................................................................................................................784
B.2 GPRS aspects when connected to the IM CN subsystem....................................................................784
B.2.1 Introduction.....................................................................................................................................................784
B.2.2 Procedures at the UE.......................................................................................................................................784
B.2.2.1 PDP context activation and P-CSCF discovery.........................................................................................784
B.2.2.1A Modification of a PDP context used for SIP signalling.............................................................................787
B.2.2.1B Re-establishment of the PDP context for SIP signalling...........................................................................787
B.2.2.1C P-CSCF restoration procedure...................................................................................................................788
B.2.2.2 Session management procedures...............................................................................................................788
B.2.2.3 Mobility management procedures..............................................................................................................789
B.2.2.4 Cell selection and lack of coverage............................................................................................................789
B.2.2.5 PDP contexts for media..............................................................................................................................789
B.2.2.5.1 General requirements...........................................................................................................................789
B.2.2.5.1A Activation or modification of PDP contexts for media by the UE.......................................................789
B.2.2.5.1B Activation or modification of PDP contexts for media by the core network.......................................790
B.2.2.5.1C Deactivation of PDP context for media................................................................................................791
B.2.2.5.2 Special requirements applying to forked responses.............................................................................791
B.2.2.5.3 Unsuccessful situations........................................................................................................................791
B.2.2.6 Emergency service.....................................................................................................................................791
B.2.2.6.1 General.................................................................................................................................................791
B.2.2.6.1A Type of emergency service derived from emergency service category value.....................................793
B.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................793
B.2.2.6.2 eCall type of emergency service..........................................................................................................794
B.2.2.6.3 Current location discovery during an emergency call..........................................................................794
B.2A Usage of SDP.....................................................................................................................................794
B.2A.0 General.............................................................................................................................................................794
B.2A.1 Impact on SDP offer / answer of activation or modification of PDP contexts for media by the core
network............................................................................................................................................................794
B.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................794
B.2A.3 Emergency service...........................................................................................................................................795
B.3 Application usage of SIP....................................................................................................................795
B.3.1 Procedures at the UE.......................................................................................................................................795
B.3.1.0 Registration and authentication..................................................................................................................795

3GPP
Release 16 22 3GPP TS 24.229 V16.8.0 (2020-12)

B.3.1.0a IMS_Registration_handling policy............................................................................................................795

B.3.1.1 P-Access-Network-Info header field.........................................................................................................796
B.3.1.1A Cellular-Network-Info header field...........................................................................................................796
B.3.1.2 Availability for calls...................................................................................................................................796
B.3.1.2A Availability for SMS..................................................................................................................................797
B.3.1.3 Authorization header field.........................................................................................................................797
B.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................797
B.3.1.5 3GPP PS data off.......................................................................................................................................798
B.3.1.6 Transport mechanisms...............................................................................................................................799
B.3.1.7 RLOS.........................................................................................................................................................799
B.3.2 Procedures at the P-CSCF...............................................................................................................................799
B.3.2.0 Registration and authentication..................................................................................................................799
B.3.2.1 Determining network to which the originating user is attached................................................................799
B.3.2.2 Location information handling...................................................................................................................799
B.3.2.3 Prohibited usage of PDN connection for emergency bearer services........................................................799
B.3.2.5 Void............................................................................................................................................................800
B.3.2.6 Resource sharing........................................................................................................................................800
B.3.2.7 Priority sharing...........................................................................................................................................800
B.3.2.8 RLOS.........................................................................................................................................................800
B.3.3 Procedures at the S-CSCF...............................................................................................................................800
B.3.3.1 Notification of AS about registration status...............................................................................................800
B.3.3.2 RLOS.........................................................................................................................................................800
B.4 3GPP specific encoding for SIP header field extensions....................................................................800
B.4.1 Void.................................................................................................................................................................800
B.5 Use of circuit-switched domain..........................................................................................................800
Annex C (normative): UICC and USIM Aspects for access to the IM CN subsystem...............801
C.1 Scope..................................................................................................................................................801
C.2 Derivation of IMS parameters from USIM.........................................................................................801
C.3 ISIM Location in 3GPP Systems........................................................................................................801
C.3A UICC access to IMS...........................................................................................................................801
C.4 Update of IMS parameters on the UICC.............................................................................................802
Annex D (normative): Void 803
Annex E (normative): IP-Connectivity Access Network specific concepts when using xDSL, Fiber
or Ethernet to access IM CN subsystem....................................................804
E.1 Scope..................................................................................................................................................804
E.2 Fixed broadband aspects when connected to the IM CN subsystem...................................................804
E.2.1 Introduction.....................................................................................................................................................804
E.2.2 Procedures at the UE.......................................................................................................................................804
E.2.2.1 Activation and P-CSCF discovery.............................................................................................................804
E.2.2.1A Modification of a fixed-broadband connection used for SIP signalling....................................................805
E.2.2.1B Re-establishment of a fixed-broadband connection used for SIP signalling.............................................805
E.2.2.1C P-CSCF restoration procedure...................................................................................................................805
E.2.2.2 Void............................................................................................................................................................805
E.2.2.3 Void............................................................................................................................................................805
E.2.2.4 Void............................................................................................................................................................805
E.2.2.5 Fixed-broadband bearer(s) for media.........................................................................................................805
E.2.2.5.1 General requirements...........................................................................................................................805
E.2.2.5.1A Activation or modification of fixed-broadband bearers for media by the UE.....................................805
E.2.2.5.1B Activation or modification of fixed-broadband bearers for media by the network..............................805
E.2.2.5.1C Deactivation of fixed-broadband bearers for media.............................................................................806
E.2.2.5.2 Special requirements applying to forked responses.............................................................................806

3GPP
Release 16 23 3GPP TS 24.229 V16.8.0 (2020-12)

E.2.2.5.3 Unsuccessful situations........................................................................................................................806

E.2.2.6 Emergency service.....................................................................................................................................806
E.2.2.6.1 General.................................................................................................................................................806
E.2.2.6.1A Type of emergency service derived from emergency service category value.....................................806
E.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................806
E.2.2.6.2 eCall type of emergency service..........................................................................................................806
E.2.2.6.3 Current location discovery during an emergency call..........................................................................806
E.2A Usage of SDP.....................................................................................................................................806
E.2A.0 General.............................................................................................................................................................806
E.2A.1 Impact on SDP offer / answer of activation or modification of xDSL bearer for media by the network.......806
E.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................807
E.2A.3 Emergency service...........................................................................................................................................807
E.3 Application usage of SIP....................................................................................................................807
E.3.1 Procedures at the UE.......................................................................................................................................807
E.3.1.0 Registration and authentication..................................................................................................................807
E.3.1.0a IMS_Registration_handling policy............................................................................................................808
E.3.1.1 P-Access-Network-Info header field.........................................................................................................808
E.3.1.1A Cellular-Network-Info header field...........................................................................................................808
E.3.1.2 Availability for calls...................................................................................................................................808
E.3.1.2A Availability for SMS..................................................................................................................................808
E.3.1.3 Authorization header field.........................................................................................................................808
E.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................809
E.3.1.5 3GPP PS data off.......................................................................................................................................809
E.3.1.6 Transport mechanisms...............................................................................................................................809
E.3.1.7 RLOS.........................................................................................................................................................809
E.3.2 Procedures at the P-CSCF...............................................................................................................................809
E.3.2.0 Registration and authentication..................................................................................................................809
E.3.2.1 Determining network to which the originating user is attached................................................................810
E.3.2.2 Location information handling...................................................................................................................810
E.3.2.3 Void............................................................................................................................................................810
E.3.2.4 Void............................................................................................................................................................810
E.3.2.5 Void............................................................................................................................................................810
E.3.2.6 Resource sharing........................................................................................................................................810
E.3.2.7 Priority sharing...........................................................................................................................................810
E.3.2.8 RLOS.........................................................................................................................................................810
E.3.3 Procedures at the S-CSCF...............................................................................................................................810
E.3.3.1 Notification of AS about registration status...............................................................................................810
E.3.3.2 RLOS.........................................................................................................................................................810
E.4 3GPP specific encoding for SIP header field extensions....................................................................811
E.4.1 Void.................................................................................................................................................................811
E.5 Use of circuit-switched domain..........................................................................................................811
Annex F (normative): Additional procedures in support for hosted NAT.............................................812
F.1 Scope..................................................................................................................................................812
F.2 Application usage of SIP....................................................................................................................812
F.2.1 UE usage of SIP...............................................................................................................................................812
F.2.1.1 General.......................................................................................................................................................812
F.2.1.2 Registration and authentication..................................................................................................................812
F.2.1.2.1 General.................................................................................................................................................812
F.2.1.2.1A Parameters contained in the ISIM........................................................................................................812
F.2.1.2.1B Parameters provisioned to a UE without ISIM or USIM.....................................................................813
F.2.1.2.2 Initial registration.................................................................................................................................813
F.2.1.2.3 Initial subscription to the registration-state event package..................................................................814
F.2.1.2.4 User-initiated re-registration................................................................................................................814
F.2.1.2.5 Authentication......................................................................................................................................815

3GPP
Release 16 24 3GPP TS 24.229 V16.8.0 (2020-12)

F.2.1.2.5.1 IMS AKA - general........................................................................................................................815

F.2.1.2.5.2 Void................................................................................................................................................815
F.2.1.2.5.3 IMS AKA abnormal cases..............................................................................................................815
F.2.1.2.5.4 SIP digest – general........................................................................................................................815
F.2.1.2.5.5 SIP digest – abnormal procedures..................................................................................................815
F.2.1.2.5.6 SIP digest with TLS – general........................................................................................................815
F.2.1.2.5.7 SIP digest with TLS – abnormal procedures..................................................................................815
F.2.1.2.5.8 Abnormal procedures for all security mechanisms........................................................................815
F.2.1.2.5A Network-initiated re-authentication.....................................................................................................816
F.2.1.2.5B Change of IPv6 address due to privacy................................................................................................816
F.2.1.2.6 User-initiated deregistration.................................................................................................................816
F.2.1.2.7 Network-initiated deregistration..........................................................................................................816
F.2.1.3 Subscription and notification.....................................................................................................................816
F.2.1.4 Generic procedures applicable to all methods excluding the REGISTER method....................................816
F.2.1.4.1 UE originating case..............................................................................................................................816
F.2.1.4.2 UE terminating case.............................................................................................................................817
F.2.2 P-CSCF usage of SIP.......................................................................................................................................818
F.2.2.1 Introduction................................................................................................................................................818
F.2.2.2 Registration................................................................................................................................................818
F.2.3 S-CSCF usage of SIP.......................................................................................................................................820
F.2.3.1 S-CSCF usage of SIP.................................................................................................................................820
F.2.3.1.1 Protected REGISTER with IMS AKA as a security mechanism.........................................................820
F.3 Void....................................................................................................................................................821
F.4 P-CSCF usage of SIP in case UDP encapsulated IPsec is not employed............................................821
F.4.1 Introduction.....................................................................................................................................................821
F.4.2 Registration......................................................................................................................................................821
F.4.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method.................822
F.4.3.1 Introduction................................................................................................................................................822
F.4.3.2 Request initiated by the UE.......................................................................................................................822
F.4.3.3 Request terminated by the UE...................................................................................................................823
F.5 NAT traversal for media flows...........................................................................................................824
Annex G (informative): Void.....................................................................................................................825
Annex H (normative): IP-Connectivity Access Network specific concepts when using DOCSIS to
access IM CN subsystem............................................................................826
H.1 Scope..................................................................................................................................................826
H.2 DOCSIS aspects when connected to the IM CN subsystem................................................................826
H.2.1 Introduction.....................................................................................................................................................826
H.2.2 Procedures at the UE.......................................................................................................................................826
H.2.2.1 Activation and P-CSCF discovery.............................................................................................................826
H.2.2.1A Modification of IP-CAN used for SIP signalling.......................................................................................826
H.2.2.1B Re-establishment of the IP-CAN used for SIP signalling..........................................................................826
H.2.2.1C P-CSCF restoration procedure...................................................................................................................826
H.2.2.2 Void............................................................................................................................................................827
H.2.2.3 Void............................................................................................................................................................827
H.2.2.4 Void............................................................................................................................................................827
H.2.2.5 Handling of the IP-CAN for media............................................................................................................827
H.2.2.5.1 General requirements...........................................................................................................................827
H.2.2.5.1A Activation or modification of IP-CAN for media by the UE...............................................................827
H.2.2.5.1B Activation or modification of IP-CAN for media by the network.......................................................827
H.2.2.5.1C Deactivation of IP-CAN for media......................................................................................................827
H.2.2.5.2 Special requirements applying to forked responses.............................................................................827
H.2.2.5.3 Unsuccessful situations........................................................................................................................827
H.2.2.6 Emergency service.....................................................................................................................................827
H.2.2.6.1 General.................................................................................................................................................827
H.2.2.6.1A Type of emergency service derived from emergency service category value.....................................827
H.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................827

3GPP
Release 16 25 3GPP TS 24.229 V16.8.0 (2020-12)

H.2.2.6.2 eCall type of emergency service..........................................................................................................828

H.2.2.6.3 Current location discovery during an emergency call..........................................................................828
H.2A Usage of SDP...................................................................................................................................................828
H.2A.0 General.............................................................................................................................................................828
H.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network.........828
H.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE........................................................828
H.2A.3 Emergency service...........................................................................................................................................828
H.3 Application usage of SIP....................................................................................................................828
H.3.1 Procedures at the UE.......................................................................................................................................828
H.3.1.0 Void............................................................................................................................................................828
H.3.1.0a IMS_Registration_handling policy............................................................................................................828
H.3.1.1 P-Access-Network-Info header field.........................................................................................................828
H.3.1.1A Cellular-Network-Info header field...........................................................................................................828
H.3.1.2 Availability for calls...................................................................................................................................829
H.3.1.2A Availability for SMS..................................................................................................................................829
H.3.1.3 Authorization header field.........................................................................................................................829
H.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................829
H.3.1.5 3GPP PS data off.......................................................................................................................................829
H.3.1.6 Transport mechanisms...............................................................................................................................829
H.3.1.7 RLOS.........................................................................................................................................................829
H.3.2 Procedures at the P-CSCF...............................................................................................................................829
H.3.2.0 Registration and authentication..................................................................................................................829
H.3.2.1 Determining network to which the originating user is attached................................................................829
H.3.2.2 Location information handling...................................................................................................................830
H.3.2.3 Void............................................................................................................................................................830
H.3.2.4 Void............................................................................................................................................................830
H.3.2.5 Void............................................................................................................................................................830
H.3.2.6 Resource sharing........................................................................................................................................830
H.3.2.7 RLOS.........................................................................................................................................................830
H.3.3 Procedures at the S-CSCF...............................................................................................................................830
H.3.3.1 Notification of AS about registration status...............................................................................................830
H.3.3.2 RLOS.........................................................................................................................................................830
H.4 3GPP specific encoding for SIP header field extensions....................................................................830
H.4.1 Void.................................................................................................................................................................830
H.5 Use of circuit-switched domain..........................................................................................................830
Annex I (normative): Additional routeing capabilities in support of traffics in IM CN subsystem.....831
I.1 Scope..................................................................................................................................................831
I.1A General...............................................................................................................................................831
I.2 Originating, transit and interconnection routeing procedures.............................................................832
I.3 Providing IMS application services in support of transit & interconnection traffics...........................833
I.3.1 Introduction.....................................................................................................................................................833
I.3.2 Procedures.......................................................................................................................................................833
I.3.2.1 Treatment for dialog and standalone transactions......................................................................................833
I.3.2.1A Handling of header fields related to charging............................................................................................834
I.3.2.2 Original dialog identifier for transit function.............................................................................................835
I.4 Loopback routeing procedures............................................................................................................836
I.4.1 Introduction.....................................................................................................................................................836
I.4.2 TRF procedure.................................................................................................................................................836
I.5 Overload control.................................................................................................................................838
I.5.1 Introduction.....................................................................................................................................................838
I.5.2 Outgoing subscriptions to load-control event..................................................................................................838

3GPP
Release 16 26 3GPP TS 24.229 V16.8.0 (2020-12)

Annex J (normative): Void 839

Annex K (normative): Additional procedures in support of UE managed NAT traversal...................840
K.1 Scope..................................................................................................................................................840
K.2 Application usage of SIP....................................................................................................................840
K.2.1 Procedures at the UE.......................................................................................................................................840
K.2.1.1 General.......................................................................................................................................................840
K.2.1.2 Registration and authentication..................................................................................................................840
K.2.1.2.1 General.................................................................................................................................................840
K.2.1.2.1A Parameters contained in the ISIM........................................................................................................840
K.2.1.2.1B Parameters provisioned to a UE without ISIM or USIM.....................................................................840
K.2.1.2.2 Initial registration.................................................................................................................................841
K.2.1.2.2.1 General............................................................................................................................................841
K.2.1.2.2.2 Initial registration using IMS AKA................................................................................................842
K.2.1.2.2.3 Initial registration using SIP digest without TLS...........................................................................842
K.2.1.2.2.4 Initial registration using SIP digest with TLS................................................................................842
K.2.1.2.2.5 Initial registration using NASS-IMS bundled authentication.........................................................842
K.2.1.2.3 Initial subscription to the registration-state event package..................................................................842
K.2.1.2.4 User-initiated re-registration................................................................................................................842
K.2.1.2.4.1 General............................................................................................................................................842
K.2.1.2.4.2 IMS AKA as a security mechanism...............................................................................................843
K.2.1.2.4.3 SIP Digest without TLS as a security mechanism..........................................................................843
K.2.1.2.4.4 SIP Digest with TLS as a security mechanism...............................................................................843
K.2.1.2.4.5 NASS-IMS bundled authentication as a security mechanism........................................................843
K.2.1.2.5 Authentication......................................................................................................................................843
K.2.1.2.5.1 IMS AKA – general........................................................................................................................843
K.2.1.2.5.2 Void................................................................................................................................................844
K.2.1.2.5.3 IMS AKA abnormal cases..............................................................................................................844
K.2.1.2.5.4 SIP digest without TLS – general...................................................................................................844
K.2.1.2.5.5 SIP digest without TLS – abnormal procedures.............................................................................844
K.2.1.2.5.6 SIP digest with TLS – general........................................................................................................844
K.2.1.2.5.7 SIP digest with TLS – abnormal procedures..................................................................................844
K.2.1.2.5.8 NASS-IMS bundled authentication – general................................................................................844
K.2.1.2.5.9 NASS-IMS bundled authentication – abnormal procedures..........................................................844
K.2.1.2.5.10 Abnormal procedures for all security mechanisms........................................................................844
K.2.1.2.5A Network initiated re-authentication......................................................................................................844
K.2.1.2.5B Change of IPv6 address due to privacy................................................................................................845
K.2.1.2.6 User-initiated deregistration.................................................................................................................845
K.2.1.2.6.1 General............................................................................................................................................845
K.2.1.2.6.2 IMS AKA as a security mechanism...............................................................................................845
K.2.1.2.6.3 SIP digest as a security mechanism................................................................................................845
K.2.1.2.6.4 SIP digest with TLS as a security mechanism................................................................................845
K.2.1.2.6.5 Initial registration using NASS-IMS bundled authentication.........................................................845
K.2.1.2.7 Network-initiated deregistration..........................................................................................................845
K.2.1.3 Subscription and notification.....................................................................................................................846
K.2.1.4 Generic procedures applicable to all methods excluding the REGISTER method....................................846
K.2.1.4.1 UE-originating case..............................................................................................................................846
K.2.1.4.2 UE-terminating case.............................................................................................................................846
K.2.1.5 Maintaining flows and detecting flow failures..........................................................................................847
K.2.1.6 Emergency services....................................................................................................................................847
K.2.1.6.1 General.................................................................................................................................................847
K.2.1.6.2 Initial emergency registration...............................................................................................................847
K.2.1.6.2A New initial emergency registration......................................................................................................847
K.2.1.5A.3 Initial subscription to the registration-state event package..................................................................847
K.2.1.6.4 User-initiated emergency reregistration...............................................................................................847
K.2.1.6.5 Authentication......................................................................................................................................847
K.2.1.6.6 User-initiated emergency deregistration..............................................................................................847
K.2.1.6.7 Network-initiated emergency deregistration........................................................................................848
K.2.1.6.8 Emergency session setup......................................................................................................................848
K.2.1.6.8.1 General............................................................................................................................................848

3GPP
Release 16 27 3GPP TS 24.229 V16.8.0 (2020-12)

K.2.1.6.8.2 Emergency session set-up in case of no registration......................................................................848

K.2.1.6.8.3 Emergency session set-up with an emergency registration............................................................848
K.2.1.6.8.4 Emergency session set-up within a non-emergency registration....................................................848
K.2.1.6.9 Emergency session release...................................................................................................................848
K.2.2 Procedures at the P-CSCF...............................................................................................................................848
K.2.2.1 Introduction................................................................................................................................................848
K.2.2.2 Registration................................................................................................................................................848
K.2.2.2.1 General.................................................................................................................................................848
K.2.2.2.2 IMS AKA as a security mechanism.....................................................................................................848
K.2.2.2.3 SIP digest without TLS as a security mechanism................................................................................850
K.2.2.2.4 SIP digest with TLS as a security mechanism.....................................................................................850
K.2.2.2.5 NASS-IMS bundled authentication as a security mechanism..............................................................850
K.2.2.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method...........850
K.2.2.3.1 Requests initiated by the UE................................................................................................................850
K.2.2.3.1.1 General for all requests...................................................................................................................850
K.2.2.3.1.2 General for all responses................................................................................................................851
K.2.2.3.1.2A Abnormal cases...............................................................................................................................851
K.2.2.3.1.3 Initial request for a dialog...............................................................................................................851
K.2.2.3.1.4 Responses to an initial request for a dialog....................................................................................851
K.2.2.3.1.5 Target refresh request for a dialog..................................................................................................851
K.2.2.3.1.6 Responses to a target refresh request for a dialog..........................................................................851
K.2.2.3.1.7 Request for a standalone transaction..............................................................................................851
K.2.2.3.1.8 Responses to a request for a standalone transaction.......................................................................851
K.2.2.3.1.9 Subsequent request other than a target refresh request...................................................................851
K.2.2.3.1.10 Responses to a subsequent request other than a target refresh request...........................................851
K.2.2.3.1.11 Request for an unkown method that does not relate to an existing dialog.....................................851
K.2.2.3.1.12 Responses to a request for an unkown method that does not relate to an existing dialog..............851
K.2.2.3.2 Requests terminated by the UE............................................................................................................852
K.2.2.3.2.1 General for all requests...................................................................................................................852
K.2.2.3.2.2 General for all responses................................................................................................................852
K.2.2.3.2.3 Initial request for a dialog...............................................................................................................852
K.2.2.3.2.4 Responses to an initial request for a dialog....................................................................................852
K.2.2.3.2.5 Target refresh request for a dialog..................................................................................................852
K.2.2.3.2.6 Responses to a target refresh request for a dialog..........................................................................852
K.2.2.3.2.7 Request for a standalone transaction..............................................................................................852
K.2.2.3.2.8 Responses to a request for a standalone transaction.......................................................................852
K.2.2.3.2.9 Subsequent request other than a target refresh request...................................................................852
K.2.2.3.2.10 Responses to a subsequent request other than a target refresh request...........................................852
K.2.2.3.2.11 Request for an unknown method that does not relate to an existing dialog...................................853
K.2.2.3.2.12 Responses to a request for an unknown method that does not relate to an existing dialog............853
K.2.2.4 Void............................................................................................................................................................853
K.2.2.5 Emergency services....................................................................................................................................853
K.2.2.5.1 General.................................................................................................................................................853
K.2.2.5.2 General treatment for all dialogs and standalone transactions excluding the REGISTER method –
from an unregistered user.....................................................................................................................853
K.2.2.5.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method
after emergency registration.................................................................................................................853
K.2.2.5.4 General treatment for all dialogs and standalone transactions excluding the REGISTER method –
non-emergency registration..................................................................................................................853
K.2.2.5.5 Abnormal cases....................................................................................................................................854
K.2.3 Void.................................................................................................................................................................854
K.2.4 Void.................................................................................................................................................................854
K.3 Application usage of SDP...................................................................................................................854
K.3.1 UE usage of SDP.............................................................................................................................................854
K.3.2 P-CSCF usage of SDP.....................................................................................................................................854
K.4 Void....................................................................................................................................................854
K.5 Application usage of ICE....................................................................................................................854
K.5.1 Introduction.....................................................................................................................................................854
K.5.2 UE usage of ICE..............................................................................................................................................854
K.5.2.1 General.......................................................................................................................................................854

3GPP
Release 16 28 3GPP TS 24.229 V16.8.0 (2020-12)

K.5.2.2 Call initiation – UE-origination case.........................................................................................................855

K.5.2.3 Call termination – UE-termination case.....................................................................................................855
K.5.3 P-CSCF support of ICE...................................................................................................................................856
K.5.4 Void.................................................................................................................................................................856

Annex L (normative): IP-Connectivity Access Network specific concepts when using EPS to access
IM CN subsystem........................................................................................857
L.1 Scope..................................................................................................................................................857
L.2 EPS aspects when connected to the IM CN subsystem via E-UTRAN...............................................857
L.2.1 Introduction.....................................................................................................................................................857
L.2.2 Procedures at the UE.......................................................................................................................................857
L.2.2.1 EPS bearer context activation and P-CSCF discovery...............................................................................857
L.2.2.1A Modification of a EPS bearer context used for SIP signalling..................................................................860
L.2.2.1B Re-establishment of the EPS bearer context for SIP signalling.................................................................861
L.2.2.1C P-CSCF restoration procedure...................................................................................................................861
L.2.2.2 Session management procedures...............................................................................................................862
L.2.2.3 Mobility management procedures..............................................................................................................862
L.2.2.4 Cell selection and lack of coverage............................................................................................................862
L.2.2.5 EPS bearer contexts for media...................................................................................................................862
L.2.2.5.1 General requirements...........................................................................................................................862
L.2.2.5.1A Activation or modification of EPS bearer contexts for media by the UE............................................863
L.2.2.5.1B Activation or modification of EPS bearer contexts for media by the network....................................863
L.2.2.5.1C Deactivation of EPS bearer context for media.....................................................................................863
L.2.2.5.1D Default EPS bearer context usage restriction policy............................................................................863
L.2.2.5.2 Special requirements applying to forked responses.............................................................................864
L.2.2.5.3 Unsuccessful situations........................................................................................................................864
L.2.2.6 Emergency service.....................................................................................................................................864
L.2.2.6.1 General.................................................................................................................................................864
L.2.2.6.1A Type of emergency service derived from emergency service category value.....................................866
L.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................867
L.2.2.6.2 eCall type of emergency service..........................................................................................................867
L.2.2.6.3 Current location discovery during an emergency call..........................................................................868
L.2A Usage of SDP.....................................................................................................................................868
L.2A.0 General.............................................................................................................................................................868
L.2A.1 Impact on SDP offer / answer of activation or modification of EPS bearer context for media by the
network............................................................................................................................................................868
L.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................868
L.2A.3 Emergency service...........................................................................................................................................869
L.3 Application usage of SIP....................................................................................................................869
L.3.1 Procedures at the UE.......................................................................................................................................869
L.3.1.0 Registration and authentication..................................................................................................................869
L.3.1.0a IMS_Registration_handling policy............................................................................................................869
L.3.1.1 P-Access-Network-Info header field.........................................................................................................870
L.3.1.1A Cellular-Network-Info header field...........................................................................................................870
L.3.1.2 Availability for calls...................................................................................................................................870
L.3.1.2A Availability for SMS..................................................................................................................................872
L.3.1.3 Authorization header field.........................................................................................................................872
L.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................873
L.3.1.5 3GPP PS data off.......................................................................................................................................873
L.3.1.6 Transport mechanisms...............................................................................................................................874
L.3.1.7 RLOS.........................................................................................................................................................874
L.3.1.7.1 General.................................................................................................................................................874
L.3.1.7.2 Registration..........................................................................................................................................874
L.3.1.7.3.1 Void................................................................................................................................................875
L.3.1.7.3.2 RLOS session set-up in case of unsuccessful registration..............................................................875
L.3.1.7.3.3 RLOS session set-up in case of successful registration..................................................................877

3GPP
Release 16 29 3GPP TS 24.229 V16.8.0 (2020-12)

L.3.2 Procedures at the P-CSCF...............................................................................................................................877

L.3.2.0 Registration and authentication..................................................................................................................877
L.3.2.1 Determining network to which the originating user is attached................................................................877
L.3.2.2 Location information handling...................................................................................................................877
L.3.2.3 Prohibited usage of PDN connection for emergency bearer services........................................................877
L.3.2.4 Support for paging policy differentiation...................................................................................................877
L.3.2.5 Void............................................................................................................................................................878
L.3.2.6 Resource sharing........................................................................................................................................878
L.3.2.6.1 Registration..........................................................................................................................................878
L.3.2.6.2 UE-originating case..............................................................................................................................878
L.3.2.6.3 UE-terminating case.............................................................................................................................879
L.3.2.6.3.1 The initial INVITE request contains an initial SDP offer..............................................................879
L.3.2.6.3.2 The 18x response or the 2xx responses contains an initial SDP offer............................................879
L.3.2.6.4 Abnormal cases....................................................................................................................................880
L.3.2.6.5 Resource sharing options updated by AS.............................................................................................880
L.3.2.7 Priority sharing...........................................................................................................................................880
L.3.2.7.1 General.................................................................................................................................................880
L.3.2.7.2 Registration procedure.........................................................................................................................881
L.3.2.7.3 Session establishment procedure..........................................................................................................881
L.3.2.7.4 Subsequent request procedure..............................................................................................................881
L.3.2.8 RLOS.........................................................................................................................................................881
L.3.2.8.1 General.................................................................................................................................................881
L.3.2.8.2 Registration..........................................................................................................................................881
L.3.2.8.3.1 General............................................................................................................................................882
L.3.2.8.3.2 General treatment for RLOS session setup – requests from an unregistered user..........................882
L.3.2.8.3.3 General treatment for RLOS session setup – requests from a registered user................................883
L.3.2.9 Support of ANBR and RAN-assisted codec adaptation.............................................................................883
L.3.3 Procedures at the S-CSCF...............................................................................................................................883
L.3.3.1 Notification of AS about registration status...............................................................................................883
L.3.3.2 RLOS.........................................................................................................................................................883
L.3.3.2.1 General.................................................................................................................................................883
L.3.3.2.2 Registration..........................................................................................................................................883
L.4 3GPP specific encoding for SIP header field extensions....................................................................886
L.4.1 Void.................................................................................................................................................................886
L.5 Use of circuit-switched domain..........................................................................................................886
Annex M (normative): IP-Connectivity Access Network specific concepts when using cdma2000 ®
packet data subsystem to access IM CN subsystem.................................888
M.1 Scope..................................................................................................................................................888
M.2 cdma2000® packet data subsystem aspects when connected to the IM CN subsystem.......................888
M.2.1 Introduction.....................................................................................................................................................888
M.2.2 Procedures at the UE.......................................................................................................................................888
M.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery..........................................................................888
M.2.2.1A Modification of IP-CAN used for SIP signalling.......................................................................................889
M.2.2.1B Re-establishment of the IP-CAN used for SIP signalling..........................................................................889
M.2.2.1C P-CSCF restoration procedure...................................................................................................................889
M.2.2.2 Void............................................................................................................................................................889
M.2.2.3 IP-CAN bearer control point support of DHCP based P-CSCF discovery................................................889
M.2.2.4 Void............................................................................................................................................................890
M.2.2.5 Handling of the IP-CAN for media............................................................................................................890
M.2.2.5.1 General requirements...........................................................................................................................890
M.2.2.5.1A Activation or modification of IP-CAN for media by the UE...............................................................890
M.2.2.5.1B Activation or modification of IP-CAN for media by the network.......................................................890
M.2.2.5.1C Deactivation of IP-CAN for media......................................................................................................890
M.2.2.5.2 Special requirements applying to forked responses.............................................................................890
M.2.2.5.3 Unsuccessful situations........................................................................................................................890
M.2.2.6 Emergency service.....................................................................................................................................890
M.2.2.6.1 General.................................................................................................................................................890
M.2.2.6.1A Type of emergency service derived from emergency service category value.....................................890

3GPP
Release 16 30 3GPP TS 24.229 V16.8.0 (2020-12)

M.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................891
M.2.2.6.2 eCall type of emergency service..........................................................................................................891
M.2.2.6.3 Current location discovery during an emergency call..........................................................................891
M.2A Usage of SDP.....................................................................................................................................891
M.2A.0 General.............................................................................................................................................................891
M.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network...............891
M.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................891
M.2A.3 Emergency service...........................................................................................................................................891
M.3 Application usage of SIP....................................................................................................................891
M.3.1 Procedures at the UE.......................................................................................................................................891
M.3.1.0 Void............................................................................................................................................................891
M.3.1.0a IMS_Registration_handling policy............................................................................................................891
M.3.1.1 P-Access-Network-Info header field.........................................................................................................891
M.3.1.1A Cellular-Network-Info header field...........................................................................................................892
M.3.1.2 Availability for calls...................................................................................................................................892
M.3.1.2A Availability for SMS..................................................................................................................................892
M.3.1.3 Authorization header field.........................................................................................................................892
M.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................892
M.3.1.5 3GPP PS data off.......................................................................................................................................892
M.3.1.6 Transport mechanisms...............................................................................................................................892
M.3.1.7 RLOS.........................................................................................................................................................892
M.3.2 Procedures at the P-CSCF...............................................................................................................................892
M.3.2.0 Registration and authentication..................................................................................................................892
M.3.2.1 Determining network to which the originating user is attached................................................................893
M.3.2.2 Location information handling...................................................................................................................893
M.3.2.3 Void............................................................................................................................................................893
M.3.2.4 Void............................................................................................................................................................893
M.3.2.5 Void............................................................................................................................................................893
M.3.2.6 Resource sharing........................................................................................................................................893
M.3.2.7 Priority sharing...........................................................................................................................................893
M.3.2.8 RLOS.........................................................................................................................................................893
M.3.3 Procedures at the S-CSCF...............................................................................................................................893
M.3.3.1 Notification of AS about registration status...............................................................................................893
M.3.3.2 RLOS.........................................................................................................................................................893
M.4 3GPP specific encoding for SIP header field extensions....................................................................894
M.4.1 Void.................................................................................................................................................................894
M.5 Use of circuit switched domain...........................................................................................................894
Annex N (Normative): Functions to support overlap signalling.............................................................895
N.1 Scope..................................................................................................................................................895
N.2 Digit collection function.....................................................................................................................895
N.2.1 General.............................................................................................................................................................895
N.2.2 Collection of digits..........................................................................................................................................895
N.2.2.1 Initial INVITE request...............................................................................................................................895
N.2.2.2 Collection of additional digits....................................................................................................................896
N.2.2.3 Handling of 404 (Not Found) / 484 (Address Incomplete) responses.......................................................896
N.2.3 Forwarding of SIP messages by the digit collection function.........................................................................897
N.3 En-bloc conversion function...............................................................................................................897
N.3.1 General.............................................................................................................................................................897
N.3.2 Multiple-INVITE method.......................................................................................................................................898
N.3.3 In-dialog method..............................................................................................................................................898

Annex O (normative): IP-Connectivity Access Network specific concepts when using the EPC via
cdma2000® HRPD to access IM CN subsystem........................................900

3GPP
Release 16 31 3GPP TS 24.229 V16.8.0 (2020-12)

O.1 Scope..................................................................................................................................................900
O.2 IP-CAN aspects when connected to the IM CN subsystem................................................................900
O.2.1 Introduction.....................................................................................................................................................900
O.2.2 Procedures at the UE.......................................................................................................................................900
O.2.2.1 IP-CAN bearer context activation and P-CSCF discovery........................................................................900
O.2.2.1A Modification of an IP-CAN bearer context used for SIP signalling..........................................................901
O.2.2.1B Re-establishment of the IP-CAN bearer context for SIP signalling..........................................................901
O.2.2.1C P-CSCF restoration procedure...................................................................................................................902
O.2.2.2 Session management procedures...............................................................................................................902
O.2.2.3 Mobility management procedures..............................................................................................................902
O.2.2.4 Cell selection and lack of coverage............................................................................................................902
O.2.2.5 IP-CAN bearer contexts for media.............................................................................................................902
O.2.2.5.1 General requirements...........................................................................................................................902
O.2.2.5.1A Activation or modification of IP-CAN bearer contexts for media by the UE......................................902
O.2.2.5.1B Activation or modification of IP-CAN bearer contexts for media by the network..............................903
O.2.2.5.1C Deactivation of of IP-CAN bearer contexts for media.........................................................................903
O.2.2.5.2 Special requirements applying to forked responses.............................................................................903
O.2.2.5.3 Unsuccessful situations........................................................................................................................903
O.2.2.6 Emergency service.....................................................................................................................................903
O.2.2.6.1 General.................................................................................................................................................903
O.2.2.6.1A Type of emergency service derived from emergency service category value.....................................903
O.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................904
O.2.2.6.2 eCall type of emergency service..........................................................................................................904
O.2.2.6.3 Current location discovery during an emergency call..........................................................................904
O.2A Usage of SDP.....................................................................................................................................904
O.2A.0 General.............................................................................................................................................................904
O.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN bearer context for media by the
network............................................................................................................................................................904
O.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................904
O.2A.3 Emergency service...........................................................................................................................................904
O.3 Application usage of SIP....................................................................................................................905
O.3.1 Procedures at the UE.......................................................................................................................................905
O.3.1.0 Void............................................................................................................................................................905
O.3.1.0a IMS_Registration_handling policy............................................................................................................905
O.3.1.1 P-Access-Network-Info header field.........................................................................................................905
O.3.1.1A Cellular-Network-Info header field...........................................................................................................905
O.3.1.2 Availability for calls...................................................................................................................................905
O.3.1.2A Availability for SMS..................................................................................................................................905
O.3.1.3 Authorization header field.........................................................................................................................905
O.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................905
O.3.1.5 3GPP PS data off.......................................................................................................................................905
O.3.1.6 Transport mechanisms...............................................................................................................................906
O.3.1.7 RLOS.........................................................................................................................................................906
O.3.2 Procedures at the P-CSCF...............................................................................................................................906
O.3.2.0 Registration and authentication..................................................................................................................906
O.3.2.1 Determining network to which the originating user is attached................................................................906
O.3.2.2 Location information handling...................................................................................................................906
O.3.2.3 Void............................................................................................................................................................906
O.3.2.4 Void............................................................................................................................................................906
O.3.2.5 Void............................................................................................................................................................906
O.3.2.6 Resource sharing........................................................................................................................................906
O.3.2.7 Priority sharing...........................................................................................................................................906
O.3.2.8 RLOS.........................................................................................................................................................906
O.3.3 Procedures at the S-CSCF...............................................................................................................................907
O.3.3.1 Notification of AS about registration status...............................................................................................907
O.3.3.2 RLOS.........................................................................................................................................................907

3GPP
Release 16 32 3GPP TS 24.229 V16.8.0 (2020-12)

O.4 3GPP specific encoding for SIP header field extensions....................................................................907

O.4.1 Void.................................................................................................................................................................907
O.5 Use of circuit-switched domain..........................................................................................................907
Annex P (informative): Void908
Annex Q (normative): IP-Connectivity Access Network specific concepts when using the
cdma2000® 1x Femtocell Network to access IM CN subsystem..............909
Q.1 Scope..................................................................................................................................................909
Q.2 cdma2000® 1x Femtocell Network aspects when connected to the IM CN subsystem.......................909
Q.2.1 Introduction.....................................................................................................................................................909
Q.2.2 Procedures at the UE.......................................................................................................................................909
Q.2.2.1 Activation and P-CSCF discovery.............................................................................................................909
Q.2.2.1A Modification of IP-CAN used for SIP signalling.......................................................................................910
Q.2.2.1B Re-establishment of IP-CAN used for SIP signalling................................................................................910
Q.2.2.2 Void............................................................................................................................................................910
Q.2.2.3 Void............................................................................................................................................................910
Q.2.2.4 Void............................................................................................................................................................910
Q.2.2.5 Handling of the IP-CAN for media............................................................................................................910
Q.2.2.5.1 General requirements...........................................................................................................................910
Q.2.2.5.1A Activation or modification of IP-CAN for media by the UE...............................................................910
Q.2.2.5.1B Activation or modification of IP-CAN for media by the network.......................................................910
Q.2.2.5.1C Deactivation of IP-CAN for media......................................................................................................910
Q.2.2.5.2 Special requirements applying to forked responses.............................................................................910
Q.2.2.5.3 Unsuccessful situations........................................................................................................................910
Q.2.2.6 Emergency service.....................................................................................................................................910
Q.2.2.6.1 General.................................................................................................................................................910
Q.2.2.6.1A Type of emergency service derived from emergency service category value.....................................910
Q.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................910
Q.2.2.6.2 eCall type of emergency service..........................................................................................................911
Q.2.2.6.3 Current location discovery during an emergency call..........................................................................911
Q.2A Usage of SDP.....................................................................................................................................911
Q.2A.0 General.............................................................................................................................................................911
Q.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network...............911
Q.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................911
Q.2A.3 Emergency service...........................................................................................................................................911
Q.3 Application usage of SIP....................................................................................................................911
Q.3.1 Procedures at the UE.......................................................................................................................................911
Q.3.1.0 Void............................................................................................................................................................911
Q.3.1.0a IMS_Registration_handling policy............................................................................................................911
Q.3.1.1 P-Access-Network-Info header field.........................................................................................................911
Q.3.1.1A Cellular-Network-Info header field...........................................................................................................911
Q.3.1.2 Availability for calls...................................................................................................................................912
Q.3.1.2A Availability for SMS..................................................................................................................................912
Q.3.1.3 Authorization header field.........................................................................................................................912
Q.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................912
Q.3.1.5 3GPP PS data off.......................................................................................................................................912
Q.3.1.6 Transport mechanisms...............................................................................................................................912
Q.3.1.7 RLOS.........................................................................................................................................................912
Q.3.2 Procedures at the P-CSCF...............................................................................................................................912
Q.3.2.0 Registration and authentication..................................................................................................................912
Q.3.2.1 Determining network to which the originating user is attached................................................................912
Q.3.2.2 Location information handling...................................................................................................................912
Q.3.2.3 Void............................................................................................................................................................913
Q.3.2.4 Void............................................................................................................................................................913

3GPP
Release 16 33 3GPP TS 24.229 V16.8.0 (2020-12)

Q.3.2.5 Void............................................................................................................................................................913
Q.3.2.6 Resource sharing........................................................................................................................................913
Q.3.2.7 Priority sharing...........................................................................................................................................913
Q.3.2.8 RLOS.........................................................................................................................................................913
Q.3.3 Procedures at the S-CSCF...............................................................................................................................913
Q.3.3.1 Notification of AS about registration status...............................................................................................913
Q.3.3.2 RLOS.........................................................................................................................................................913
Q.4 3GPP specific encoding for SIP header field extensions....................................................................913
Q.4.1 Void.................................................................................................................................................................913
Q.5 Use of circuit-switched domain..........................................................................................................913
Annex R (normative): IP-Connectivity Access Network specific concepts when using the EPC via
WLAN to access IM CN subsystem...........................................................914
R.1 Scope..................................................................................................................................................914
R.2 IP-CAN aspects when connected to the IM CN subsystem................................................................914
R.2.1 Introduction.....................................................................................................................................................914
R.2.2 Procedures at the UE.......................................................................................................................................914
R.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery..........................................................................914
R.2.2.1A Modification of an IP-CAN used for SIP signalling..................................................................................917
R.2.2.1B Re-establishment of the IP-CAN used for SIP signalling..........................................................................917
R.2.2.1C P-CSCF restoration procedure...................................................................................................................917
R.2.2.2 Void............................................................................................................................................................918
R.2.2.3 IP-CAN support of DHCP based P-CSCF discovery................................................................................918
R.2.2.4 Void............................................................................................................................................................918
R.2.2.5 Tunnel procedures for media.....................................................................................................................918
R.2.2.5.1 General requirements...........................................................................................................................918
R.2.2.5.1A Modification of tunnel for media by the UE........................................................................................918
R.2.2.5.1B Modification of tunnel for media by the network................................................................................919
R.2.2.5.1C Deactivation of tunnel for media..........................................................................................................919
R.2.2.5.2 Special requirements applying to forked responses.............................................................................919
R.2.2.5.3 Unsuccessful situations........................................................................................................................919
R.2.2.6 Emergency service.....................................................................................................................................919
R.2.2.6.1 General.................................................................................................................................................919
R.2.2.6.1A Type of emergency service derived from emergency service category value.....................................922
R.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................923
R.2.2.6.2 eCall type of emergency service..........................................................................................................923
R.2.2.6.3 Current location discovery during an emergency call..........................................................................923
R.2A Usage of SDP.....................................................................................................................................923
R.2A.0 General.............................................................................................................................................................923
R.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network...............923
R.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................924
R.2A.3 Emergency service...........................................................................................................................................924
R.3 Application usage of SIP....................................................................................................................924
R.3.1 Procedures at the UE.......................................................................................................................................924
R.3.1.0 Registration and authentication..................................................................................................................924
R.3.1.0a IMS_Registration_handling policy............................................................................................................925
R.3.1.1 P-Access-Network-Info header field.........................................................................................................925
R.3.1.1A Cellular-Network-Info header field...........................................................................................................925
R.3.1.2 Availability for calls...................................................................................................................................926
R.3.1.2A Availability for SMS..................................................................................................................................926
R.3.1.3 Authorization header field.........................................................................................................................926
R.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................926
R.3.1.5 3GPP PS data off.......................................................................................................................................926
R.3.1.6 Transport mechanisms...............................................................................................................................926
R.3.1.7 RLOS.........................................................................................................................................................926

3GPP
Release 16 34 3GPP TS 24.229 V16.8.0 (2020-12)

R.3.2 Procedures at the P-CSCF...............................................................................................................................927

R.3.2.0 Registration and authentication..................................................................................................................927
R.3.2.1 Determining network to which the originating user is attached................................................................927
R.3.2.2 Location information handling...................................................................................................................927
R.3.2.3 Prohibited usage of PDN connection for emergency bearer services........................................................927
R.3.2.4 Void............................................................................................................................................................928
R.3.2.5 Void............................................................................................................................................................928
R.3.2.6 Resource sharing........................................................................................................................................928
R.3.2.7 Priority sharing...........................................................................................................................................928
R.3.2.8 RLOS.........................................................................................................................................................928
R.3.3 Procedures at the S-CSCF...............................................................................................................................928
R.3.3.1 Notification of AS about registration status...............................................................................................928
R.3.3.2 RLOS.........................................................................................................................................................928
R.4 3GPP specific encoding for SIP header field extensions....................................................................928
R.4.1 Void.................................................................................................................................................................928
R.5 Use of circuit-switched domain..........................................................................................................928
Annex S (normative): IP-Connectivity Access Network specific concepts when using DVB-RCS2
to access IM CN subsystem........................................................................929
S.1 Scope..................................................................................................................................................929
S.2 DVB-RCS2 aspects when connected to the IM CN subsystem..........................................................929
S.2.1 Introduction.....................................................................................................................................................929
S.2.2 Procedures at the UE.......................................................................................................................................929
S.2.2.1 Activation and P-CSCF discovery.............................................................................................................929
S.2.2.1A Modification of IP-CAN bearer used for SIP signalling............................................................................929
S.2.2.1B Re-establishment of IP-CAN bearer used for SIP signalling.....................................................................929
S.2.2.1C P-CSCF restoration procedure...................................................................................................................930
S.2.2.2 Void............................................................................................................................................................930
S.2.2.3 Void............................................................................................................................................................930
S.2.2.4 Void............................................................................................................................................................930
S.2.2.5 Handling of the IP-CAN for media............................................................................................................930
S.2.2.5.1 General requirements...........................................................................................................................930
S.2.2.5.1A Activation or modification of IP-CAN for media by the UE...............................................................930
S.2.2.5.1B Activation or modification of IP-CAN for media by the network.......................................................930
S.2.2.5.1C Deactivation of IP-CAN for media......................................................................................................930
S.2.2.5.2 Special requirements applying to forked responses.............................................................................930
S.2.2.5.3 Unsuccessful situations........................................................................................................................930
S.2.2.6 Emergency service.....................................................................................................................................930
S.2.2.6.1 General.................................................................................................................................................930
S.2.2.6.1A Type of emergency service derived from emergency service category value.....................................930
S.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................930
S.2.2.6.2 eCall type of emergency service..........................................................................................................931
S.2.2.6.3 Current location discovery during an emergency call..........................................................................931
S.2A Usage of SDP.....................................................................................................................................931
S.2A.0 General.............................................................................................................................................................931
S.2A.1 Impact on SDP offer / answer of activation or modification of satellite bearer for media by the network.....931
S.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................931
S.2A.3 Emergency service...........................................................................................................................................931
S.3 Application usage of SIP....................................................................................................................931
S.3.1 Procedures at the UE.......................................................................................................................................931
S.3.1.0 Void............................................................................................................................................................931
S.3.1.0a IMS_Registration_handling policy............................................................................................................931
S.3.1.1 P-Access-Network-Info header field.........................................................................................................931
S.3.1.1A Cellular-Network-Info header field...........................................................................................................931
S.3.1.2 Availability for calls...................................................................................................................................932
S.3.1.2A Availability for SMS..................................................................................................................................932
S.3.1.3 Authorization header field.........................................................................................................................932

3GPP
Release 16 35 3GPP TS 24.229 V16.8.0 (2020-12)

S.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................932
S.3.1.5 3GPP PS data off.......................................................................................................................................932
S.3.1.6 Transport mechanisms...............................................................................................................................932
S.3.1.7 RLOS.........................................................................................................................................................932
S.3.2 Procedures at the P-CSCF...............................................................................................................................932
S.3.2.0 Registration and authentication..................................................................................................................932
S.3.2.1 Determining network to which the originating user is attached................................................................932
S.3.2.2 Location information handling...................................................................................................................933
S.3.2.3 Void............................................................................................................................................................933
S.3.2.4 Void............................................................................................................................................................933
S.3.2.5 Void............................................................................................................................................................933
S.3.2.6 Resource sharing........................................................................................................................................933
S.3.2.7 Priority sharing...........................................................................................................................................933
S.3.2.8 RLOS.........................................................................................................................................................933
S.3.3 Procedures at the S-CSCF...............................................................................................................................933
S.3.3.1 Notification of AS about registration status...............................................................................................933
S.3.3.2 RLOS.........................................................................................................................................................933
S.4 3GPP specific encoding for SIP header field extensions....................................................................933
S.4.1 Void.................................................................................................................................................................933
S.5 Use of circuit-switched domain..........................................................................................................933
Annex T (Normative): Network policy requirements for the IM CN subsystem...................................934
T.1 Scope..................................................................................................................................................934
T.2 Application of network policy for the support of transcoding............................................................934
Annex U (normative): IP-Connectivity Access Network specific concepts when using 5GS to
access IM CN subsystem............................................................................935
U.1 Scope..................................................................................................................................................935
U.2 IP-CAN aspects when connected to the IM CN subsystem................................................................935
U.2.1 Introduction.....................................................................................................................................................935
U.2.2 Procedures at the UE.......................................................................................................................................935
U.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery..........................................................................935
U.2.2.1A Modification of the PDU session of the 5GS QoS flow used for SIP signalling.......................................937
U.2.2.1B Re-establishment of the PDU session with the 5GS QoS flow used for SIP signalling............................937
U.2.2.1C P-CSCF restoration procedure...................................................................................................................938
U.2.2.2 Session management procedures...............................................................................................................939
U.2.2.3 Mobility management procedures..............................................................................................................939
U.2.2.4 Cell selection and lack of coverage............................................................................................................939
U.2.2.5 5GS QoS flow for media............................................................................................................................939
U.2.2.5.1 General requirements...........................................................................................................................939
U.2.2.5.1A Activation or modification of QoS flows for media by the UE...........................................................939
U.2.2.5.1B Activation or modification of QoS flows for media by the network....................................................939
U.2.2.5.1C Deactivation of a QoS flow for media.................................................................................................940
U.2.2.5.1D Default QoS flow usage restriction policy...........................................................................................940
U.2.2.5.2 Special requirements applying to forked responses.............................................................................940
U.2.2.5.3 Unsuccessful situations........................................................................................................................941
U.2.2.6 Emergency service.....................................................................................................................................941
U.2.2.6.1 General.................................................................................................................................................941
U.2.2.6.1A Type of emergency service derived from emergency service category value.....................................943
U.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................944
U.2.2.6.2 eCall type of emergency service..........................................................................................................945
U.2.2.6.3 Current location discovery during an emergency call..........................................................................945
U.2.2.6.4 Emergency services in single-registration mode..................................................................................945
U.2.2.6.5 Emergency services in dual registration mode.....................................................................................948
U.2A Usage of SDP.....................................................................................................................................950

3GPP
Release 16 36 3GPP TS 24.229 V16.8.0 (2020-12)

U.2A.0 General.............................................................................................................................................................950
U.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network...............950
U.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................950
U.2A.3 Emergency service...........................................................................................................................................951
U.3 Application usage of SIP....................................................................................................................951
U.3.1 Procedures at the UE.......................................................................................................................................951
U.3.1.0 Registration and authentication..................................................................................................................951
U.3.1.0A IMS_Registration_handling policy............................................................................................................951
U.3.1.1 P-Access-Network-Info header field.........................................................................................................952
U.3.1.1A Cellular-Network-Info header field...........................................................................................................952
U.3.1.2 Availability for calls...................................................................................................................................952
U.3.1.2A Availability for SMS..................................................................................................................................954
U.3.1.3 Authorization header field.........................................................................................................................955
U.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................955
U.3.1.5 3GPP PS data off.......................................................................................................................................955
U.3.1.6 RLOS.........................................................................................................................................................956
U.3.1.7 SIP handling at the originating UE when redirecting the UE from NG-RAN to E-UTRAN fails......957
U.3.1.8 Unified Access Control..............................................................................................................................957
U.3.1.9 Abnormal cases..........................................................................................................................................957
U.3.2 Procedures at the P-CSCF...............................................................................................................................958
U.3.2.0 Registration and authentication..................................................................................................................958
U.3.2.1 Determining network to which the originating user is attached................................................................958
U.3.2.2 Location information handling...................................................................................................................958
U.3.2.3 Prohibited usage of PDU session for emergency services.........................................................................958
U.3.2.4 Support for paging policy differentiation...................................................................................................958
U.3.2.5 Void............................................................................................................................................................959
U.3.2.6 Resource sharing........................................................................................................................................959
U.3.2.7 Priority sharing...........................................................................................................................................959
U.3.2.8 RLOS.........................................................................................................................................................959
U.3.2.9 Support of ANBR and RAN-assisted codec adaptation.............................................................................959
U.3.3 Procedures at the S-CSCF...............................................................................................................................959
U.3.3.1 Notification of AS about registration status...............................................................................................959
U.3.3.2 RLOS.........................................................................................................................................................959
U.4 3GPP specific encoding for SIP header field extensions....................................................................959
U.4.1 Void.................................................................................................................................................................959
U.5 Use of circuit-switched domain..........................................................................................................959
Annex V (normative): HTTP Profiling.....................................................................................................960
V.1 Scope..................................................................................................................................................960
V.2 Ms reference point..............................................................................................................................960
V.2.1 General.............................................................................................................................................................960
V.2.2 Resource structure...........................................................................................................................................960
V.2.3 Request requirements......................................................................................................................................961
V.2.3.1 General.......................................................................................................................................................961
V.2.3.2 Request header requirements...............................................................................................................................961
V.2.4 Response requirements....................................................................................................................................962
V.2.4.1 General.......................................................................................................................................................962
V.2.4.2 Response header requirements...................................................................................................................962
V.2.4.3 Error response requirements......................................................................................................................962
V.2.4.3.1 General.................................................................................................................................................962
V.2.4.3.2 Service errors........................................................................................................................................963
V.2.4.3.3 Policy errors.........................................................................................................................................963
V.2.5 signing.............................................................................................................................................................963
V.2.5.1 General.......................................................................................................................................................963
V.2.5.2 Data types...................................................................................................................................................963

3GPP
Release 16 37 3GPP TS 24.229 V16.8.0 (2020-12)

V.2.6 verification.......................................................................................................................................................965
V.2.6.1 General.......................................................................................................................................................965
V.2.6.2 Data types...................................................................................................................................................965

Annex W (normative): IP-Connectivity Access Network specific concepts when using the 5GCN
via WLAN to access IM CN subsystem.....................................................966
W.1 Scope..................................................................................................................................................966
W.2 IP-CAN aspects when connected to the IM CN subsystem................................................................966
W.2.1 Introduction.....................................................................................................................................................966
W.2.2 Procedures at the UE.......................................................................................................................................966
W.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery..........................................................................966
W.2.2.1A Modification of an IP-CAN used for SIP signalling..................................................................................966
W.2.2.1B Re-establishment of the IP-CAN used for SIP signalling..........................................................................966
W.2.2.1C P-CSCF restoration procedure...................................................................................................................967
W.2.2.2 Session management procedures...............................................................................................................967
W.2.2.3 Mobility management procedures..............................................................................................................967
W.2.2.4 Cell selection and lack of coverage............................................................................................................967
W.2.2.5 5GS QoS flow for media............................................................................................................................967
W.2.2.5.1 General requirements...........................................................................................................................967
W.2.2.5.1A Activation or modification of QoS flows for media by the UE...........................................................967
W.2.2.5.1B Activation or modification of QoS flows for media by the network....................................................967
W.2.2.5.1C Deactivation of a QoS flow for media.................................................................................................967
W.2.2.5.2 Special requirements applying to forked responses.............................................................................967
W.2.2.5.3 Unsuccessful situations........................................................................................................................968
W.2.2.6 Emergency service.....................................................................................................................................968
W.2.2.6.1 General.................................................................................................................................................968
W.2.2.6.1A Type of emergency service derived from emergency service category value.....................................970
W.2.2.6.1B Type of emergency service derived from extended local emergency number list...............................970
W.2.2.6.2 eCall type of emergency service..........................................................................................................970
W.2.2.6.3 Current location discovery during an emergency call..........................................................................970
W.2A Usage of SDP.....................................................................................................................................970
W.2A.0 General.............................................................................................................................................................970
W.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network...............970
W.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN
performs network-initiated resource reservation for terminating UE..............................................................970
W.2A.3 Emergency service...........................................................................................................................................970
W.3 Application usage of SIP....................................................................................................................970
W.3.1 Procedures at the UE.......................................................................................................................................970
W.3.1.0 Registration and authentication..................................................................................................................970
W.3.1.0a IMS_Registration_handling policy............................................................................................................971
W.3.1.1 P-Access-Network-Info header field.........................................................................................................971
W.3.1.1A Cellular-Network-Info header field...........................................................................................................972
W.3.1.2 Availability for calls...................................................................................................................................972
W.3.1.2A Availability for SMS..................................................................................................................................972
W.3.1.3 Authorization header field.........................................................................................................................972
W.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE
request, the terminating UE does not have resources available and IP-CAN performs network-
initiated resource reservation for the terminating UE................................................................................972
W.3.1.5 3GPP PS data off.......................................................................................................................................972
W.3.1.6 Transport mechanisms...............................................................................................................................972
W.3.1.7 RLOS.........................................................................................................................................................972
W.3.2 Procedures at the P-CSCF...............................................................................................................................972
W.3.2.0 Registration and authentication..................................................................................................................972
W.3.2.1 Determining network to which the originating user is attached................................................................972
W.3.2.2 Location information handling...................................................................................................................972
W.3.2.3 Prohibited usage of PDN connection for emergency bearer services........................................................973
W.3.2.4 Support for paging policy differentiation...................................................................................................973
W.3.2.5 Void............................................................................................................................................................973
W.3.2.6 Resource sharing........................................................................................................................................973

3GPP
Release 16 38 3GPP TS 24.229 V16.8.0 (2020-12)

W.3.2.7 Priority sharing...........................................................................................................................................973

W.3.2.8 RLOS.........................................................................................................................................................973
W.3.3 Procedures at the S-CSCF...............................................................................................................................973
W.3.3.1 Notification of AS about registration status...............................................................................................973
W.3.3.2 RLOS.........................................................................................................................................................973
W.4 3GPP specific encoding for SIP header field extensions....................................................................973
W.4.1 Void.................................................................................................................................................................973
W.5 Use of circuit-switched domain..........................................................................................................973
Annex X (informative): Support of SBA in IMS......................................................974
X.1 Scope..................................................................................................................................................974
X.2 Reference points to support SBA in IMS............................................................................................974
X.3 Services to support SBA in IMS.........................................................................................................974
Annex Y (informative): Change history........................................................................................................976

3GPP
Release 16 39 3GPP TS 24.229 V16.8.0 (2020-12)

Foreword
This 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.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP
Release 16 40 3GPP TS 24.229 V16.8.0 (2020-12)

1 Scope
The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem
based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).

The present document is applicable to:

- the interface between the User Equipment (UE) and the Call Session Control Function (CSCF);

- the interface between the CSCF and any other CSCF;

- the interface between the CSCF and an Application Server (AS);

- the interface between the CSCF and an ISC gateway function;

- the interface between the ISC gateway function and an Application Server (AS);

- the interface between the CSCF and the Media Gateway Control Function (MGCF);

- the interface between the S-CSCF and the Multimedia Resource Function Controller (MRFC);

- the interface between the Application Server (AS) and the Multimedia Resource Function Controller (MRFC);

- the interface between the S-CSCF and the Media Resource Broker (MRB);

- the interface between the AS and the MRB;

- the interface between the MRB and the MRFC;

- the interface between the CSCF and the Breakout Gateway Control Function (BGCF);

- the interface between the BGCF and the MGCF;

- the interface between the CSCF and an IBCF;

- the interface between the IBCF and AS, MRFC or MRB;

- the interface between the E-CSCF and the Location Retrieval Function (LRF);

- the interface between the BGCF and any other BGCF;

- the interface between the CSCF and an external Multimedia IP network;

- the interface between the E-CSCF and the EATF;

- the interface between the E-CSCF and the terminating IMS network;

- the interface between the P-CSCF and the ATCF;

- the interface between the ATCF and the I-CSCF;

- the interface between the ATCF and the IBCF; and

- the interface between the transit function and the AS.

Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP are
defined within the present document. The document has therefore been structured in order to allow both forms of
specification.

As the IM CN subsystem is designed to interwork with different IP-Connectivity Access Networks (IP-CANs), the IP-
CAN independent aspects of the IM CN subsystem are described in the main body and annex A of this specification.
Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in
the annexes or in separate documents.

The document also specificies:

3GPP
Release 16 41 3GPP TS 24.229 V16.8.0 (2020-12)

- HTTP for use by an AS and by an MRB in support of the provision of media resources; and

- HTTP for use by an IBCF and by an AS in support of the invocation of attestation and verification functions.

The document also specifies media-related requirements for the NAT traversal mechanisms defined in this
specification.

NOTE: The present document covers only the usage of SIP and SDP to communicate with the enitities of the IM
CN subsystem. It is possible, and not precluded, to use the capabilities of IP-CAN to allow a terminal
containing a SIP UA to communicate with SIP servers or SIP UAs outside the IM CN subsystem, and
therefore utilise the services provided by those SIP servers. The usage of SIP and SDP for communicating
with SIP servers or SIP UAs outside the IM CN subsystem is outside the scope of the present document.

2 References
The 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
non-specific.

- 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.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[1A] 3GPP TS 22.101: "Service aspects; Service principles".

[1B] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".

[1C] 3GPP TS 22.011: "Service accessibility".

[2] 3GPP TS 23.002: "Network architecture".

[3] 3GPP TS 23.003: "Numbering, addressing and identification".

[4] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".

[4A] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".

[4B] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".

[4C] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle
mode".

[4D] 3GPP TS 23.140 Release 6: "Multimedia Messaging Service (MMS); Functional description;

Stage 2".

[5] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IM call model".

[6] 3GPP TS 23.221: "Architectural requirements".

[7] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2".

[7A] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System
description".

[7B] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".

[7C] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2".

[7D] 3GPP TS 23.380: "IMS Restoration Procedures".

3GPP
Release 16 42 3GPP TS 24.229 V16.8.0 (2020-12)

[7E] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".

[7F] 3GPP TS 23.334: "IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-
AGW) interface".

[7G] 3GPP TS 24.103: "Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem
(IMS); Stage 3".

[8] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3".

[8A] 3GPP TS 24.141: "Presence service using the IP Multimedia (IM) Core Network (CN) subsystem;
Stage 3".

[8B] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem;
Stage 3".

[8C] 3GPP TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; WLAN
User Equipment (WLAN UE) to network protocols; Stage 3".

[8D] Void.

[8E] 3GPP TS 24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS)
services, stage 3, Release 7".

[8F] 3GPP TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN)
subsystem; Stage 3".

[8G] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3".

[8H] 3GPP TS 24.173: "IMS Multimedia telephony communication service and supplementary

services; Stage 3".

[8I] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network
(CN) subsystem; Protocol specification".

[8J] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS);
Stage 3".

[8K] 3GPP TS 24.323: "3GPP IMS service level tracing management object (MO)".

[8L] 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3".

[8M] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".

[8N] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN)
subsystem".

[8O] 3GPP TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS);
Stage 3".

[8P] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Supplementary Services".

[8Q] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol
specification".

[8R] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol
specification".

[8S] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM)

Core Network (CN) subsystem".

[8T] 3GPP TS 24.305: "Selective Disabling of 3GPP User Equipment Capabilities (SDoUE)

Management Object (MO)".

[8U] 3GPP TS 24.302: "Access to the Evolved Packet Core (EPC) via non-3GPP access networks;
Stage 3".

3GPP
Release 16 43 3GPP TS 24.229 V16.8.0 (2020-12)

[8V] 3GPP TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6".

[8W] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM)
Core Network (CN) subsystem IMS".

[8X] 3GPP TS 24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 3".

[8Y] 3GPP TS 24.322: "UE access to IMS services via restrictive access networks - stage 3".

[8Z] 3GPP TS 24.371: "Web Real Time Communication (WebRTC) Access to IMS".

[8ZA] 3GPP TS 24.525: "Business trunking; Architecture and functional description".

[8ZB] 3GPP TS 24.244: "Wireless LAN control plane protocol for trusted WLAN access to EPC;
Stage 3".

[8ZC] 3GPP TS 24.337: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem
(IMS) inter-UE transfer; Stage 3".

[8ZD] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services

(ProSe) Function Protocol aspects; Stage 3".

[8ZE] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Stage 3".

[8ZF] 3GPP TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core
Network (CN) subsystem; Protocol specification".

[8ZG] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network
(CN) subsystem; Protocol specification".

[9] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell
reselection in connected mode".

[9A] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification".

[9B] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and
interaction".

[9C] 3GPP TS 26.267: "eCall Data Transfer; In-band modem solution; General description".

[10] Void.

[10A] 3GPP TS 27.060: "Mobile Station (MS) supporting Packet Switched Services".

[11] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
Packet Based Services and Packet Data Networks (PDN)".

[11A] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks".

[11B] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem
and Circuit Switched (CS) networks".

[11C] 3GPP TS 29.161: "Interworking between the Public Land Mobile Network (PLMN) supporting
Packet Based Services with Wireless Local Access and Packet Data Networks (PDN)"

[11D] 3GPP TS 29.079: "Optimal Media Routeing within the IP Multimedia Subsystem".

[12] 3GPP TS 29.207 Release 6: "Policy control over Go interface".

[12A] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".

[13] Void.

[13A] 3GPP TS 29.209 Release 6: "Policy control over Gq interface".

[13B] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".

3GPP
Release 16 44 3GPP TS 24.229 V16.8.0 (2020-12)

[13C] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS)
parameter mapping".

[13D] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".

[14] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and
message contents".

[15] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol, Protocol details".

[15A] 3GPP TS 29.311: "Service Level Interworking for Messaging Services".

[15B] 3GPP TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM)

application".

[15C] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM)

application".

[15D] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)".

[16] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging

architecture and principles".

[17] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia

Subsystem (IMS) charging".

[17A] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace

control and configuration management".

[18] 3GPP TS 33.102: "3G Security; Security architecture".

[19] 3GPP TS 33.203: "Access security for IP based services".

[19A] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".

[19B] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode".

[19C] 3GPP TS 33.328: "IP Multimedia Subsystem (IMS) media plane security".

[19D] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".

[19E] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1

Application Protocol (S1AP)".

[19F] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification".

[19G] 3GPP TS 38.331: " NR; Radio Resource Control (RRC); Protocol specification".

[20] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC)
protocol".

[20A] RFC 2401 (November 1998): "Security Architecture for the Internet Protocol".

[20B] RFC 1594 (March 1994): "FYI on Questions and Answers to Commonly asked "New Internet
User" Questions".

[20C] Void.

[20D] Void.

[20E] RFC 2462 (November 1998): "IPv6 Stateless Address Autoconfiguration".

[20F] RFC 2132 (March 1997): "DHCP Options and BOOTP Vendor Extensions".

[20G] RFC 2234 (November 1997): "Augmented BNF for Syntax Specification: ABNF".

3GPP
Release 16 45 3GPP TS 24.229 V16.8.0 (2020-12)

[21] RFC 2617 (June 1999): "HTTP Authentication: Basic and Digest Access Authentication".

[22] RFC 3966 (December 2004): "The tel URI for Telephone Numbers".

[23] RFC 4733 (December 2006): "RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals".

[24] RFC 6116 (March 2011): "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation
Discovery System (DDDS) Application (ENUM)".

[25] RFC 6086 (October 2009): "Session Initiation Protocol (SIP) INFO Method and Package
Framework".

[25A] RFC 3041 (January 2001): "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".

[26] RFC 3261 (June 2002): "SIP: Session Initiation Protocol".

[27] RFC 3262 (June 2002): "Reliability of provisional responses in Session Initiation Protocol (SIP)".

[27A] RFC 3263 (June 2002): "Session Initiation Protocol (SIP): Locating SIP Servers".

[27B] RFC 3264 (June 2002): "An Offer/Answer Model with Session Description Protocol (SDP)".

[28] RFC 6665 (July 2012): "SIP Specific Event Notification".

[28A] Void.

[29] RFC 3311 (September 2002): "The Session Initiation Protocol (SIP) UPDATE method".

[30] RFC 3312 (October 2002): "Integration of resource management and Session Initiation Protocol
(SIP)".

[31] RFC 3313 (January 2003): "Private Session Initiation Protocol (SIP) Extensions for Media
Authorization".

[32] RFC 3320 (March 2002): "Signaling Compression (SigComp)".

[33] RFC 3323 (November 2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".

[34] RFC 3325 (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for
Network Asserted Identity within Trusted Networks".

[34A] RFC 3326 (December 2002): "The Reason Header Field for the Session Initiation Protocol (SIP)".

[35] RFC 3327 (December 2002): "Session Initiation Protocol Extension Header Field for Registering
Non-Adjacent Contacts".

[35A] RFC 3361 (August 2002): "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for
Session Initiation Protocol (SIP) Servers".

[36] RFC 3515 (April 2003): "The Session Initiation Protocol (SIP) REFER method".

[37] RFC 3420 (November 2002): "Internet Media Type message/sipfrag".

[37A] RFC 3605 (October 2003): "Real Time Control Protocol (RTCP) attribute in Session Description
Protocol (SDP)".

[38] RFC 3608 (October 2003): "Session Initiation Protocol (SIP) Extension Header Field for Service
Route Discovery During Registration".

[39] RFC 4566 (June 2006): "SDP: Session Description Protocol".

[40] RFC 3315 (July 2003): "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".

[40A] RFC 2131 (March 1997): "Dynamic host configuration protocol".

[41] RFC 3319 (July 2003): "Dynamic Host Configuration Protocol (DHCPv6) Options for Session
Initiation Protocol (SIP) Servers".

3GPP
Release 16 46 3GPP TS 24.229 V16.8.0 (2020-12)

[42] RFC 3485 (February 2003): "The Session Initiation Protocol (SIP) and Session Description
Protocol (SDP) static dictionary for Signaling Compression (SigComp)".

[43] RFC 3680 (March 2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".

[44] Void.

[45] Void.

[46] Void.

[47] Void.

[48] RFC 3329 (January 2003): "Security Mechanism Agreement for the Session Initiation Protocol
(SIP)".

[49] RFC 3310 (September 2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using
Authentication and Key Agreement (AKA)".

[50] RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".

[51] Void.

[52] RFC 7315 (July 2014): "Private Header (P-Header) Extensions to the Session Initiation Protocol
(SIP) for the 3GPP".

[52A] RFC 7976 (September 2016): "Updates to Private Header (P-Header) Extension Usage in Session
Initiation Protocol (SIP) Requests and Responses".

[52B] draft-jesske-update-p-visited-network-01 (March 2019): "Update to Private Header Field P-

Visited-Network-ID in Session Initiation Protocol (SIP) Requests and Responses".

Editor's note (WI: IMSProtoc9, CR#5979): The above document cannot be formally referenced until it is published
as an RFC.

[53] RFC 3388 (December 2002): "Grouping of Media Lines in Session Description Protocol".

[54] RFC 3524 (April 2003): "Mapping of Media Streams to Resource Reservation Flows".

[55] RFC 3486 (February 2003): "Compressing the Session Initiation Protocol (SIP)".

[55A] RFC 3551 (July 2003): "RTP Profile for Audio and Video Conferences with Minimal Control".

[56] RFC 3556 (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP
Control Protocol (RTCP) Bandwidth".

[56A] RFC 3581 (August 2003): "An Extension to the Session Initiation Protocol (SIP) for Symmetric
Response Routing".

[56B] RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".

[56C] RFC 3646 (December 2003): "DNS Configuration options for Dynamic Host Configuration
Protocol for IPv6 (DHCPv6)".

[57] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".

[58] RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".

[59] RFC 3892 (September 2004): "The Session Initiation Protocol (SIP) Referred-By Mechanism".

[60] RFC 3891 (September 2004): "The Session Inititation Protocol (SIP) "Replaces" Header".

[61] RFC 3911 (October 2004): "The Session Inititation Protocol (SIP) "Join" Header".

[62] RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol
(SIP)".

[63] RFC 3861 (August 2004): "Address Resolution for Instant Messaging and Presence".

3GPP
Release 16 47 3GPP TS 24.229 V16.8.0 (2020-12)

[63A] RFC 3948 (January 2005): "UDP Encapsulation of IPsec ESP Packets".

[64] RFC 4032 (March 2005): "Update to the Session Initiation Protocol (SIP) Preconditions

Framework".

[65] RFC 3842 (August 2004) "A Message Summary and Message Waiting Indication Event Package
for the Session Initiation Protocol (SIP)"

[65A] RFC 4077 (May 2005): "A Negative Acknowledgement Mechanism for Signaling Compression".

[66] RFC 7044 (February 2014): "An Extension to the Session Initiation Protocol (SIP) for Request
History Information".

[67] RFC 5079 (December 2007): "Rejecting Anonymous Requests in the Session Initiation Protocol
(SIP)".

[68] RFC 4458 (January 2006): "Session Initiation Protocol (SIP) URIs for Applications such as
Voicemail and Interactive Voice Response (IVR)".

[69] RFC 5031 (January 2008): "A Uniform Resource Name (URN) for Emergency and Other Well-
Known Services".

[70] RFC 3903 (October 2004): "An Event State Publication Extension to the Session Initiation
Protocol (SIP)".

[71] Void.

[72] RFC 3857 (August 2004): "A Watcher Information Event Template Package for the Session
Initiation Protocol (SIP)".

[74] RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".

[74A] RFC 3603 (October 2003): "Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions
for Supporting the PacketCable Distributed Call Signaling Architecture".

[74B] RFC 3959 (December 2004): "The Early Session Disposition Type for the Session Initiation
Protocol (SIP)".

[75] RFC 4662 (August 2006): "A Session Initiation Protocol (SIP) Event Notification Extension for
Resource Lists".

[77] RFC 5875 (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol
(XCAP) Diff Event Package".

[78] RFC 4575 (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference
State".

[79] RFC 5049 (December 2007): "Applying Signaling Compression (SigComp) to the Session

Initiation Protocol (SIP)".

[80] Void.

[81] Void.

[82] RFC 4457 (April 2006): "The Session Initiation Protocol (SIP) P-User-Database Private-Header
(P-header)".

[83] RFC 4145 (September 2005): "TCP-Based Media Transport in the Session Description Protocol
(SDP)".

[84] RFC 4320 (January 2006): "Actions Addressing Identified Issues with the Session Initiation
Protocol's (SIP) Non-INVITE Transaction".

[85] 3GPP2 C.S0005-D (March 2004): "Upper Layer (Layer 3) Signaling Standard for cdma2000
Standards for Spread Spectrum Systems".

3GPP
Release 16 48 3GPP TS 24.229 V16.8.0 (2020-12)

[86] 3GPP2 C.S0024-B v3.0 (September 2009): "cdma2000 High Rate Packet Data Air Interface
Standard".

[86A] 3GPP2 C.S0084-000 (April 2007): "Overview for Ultra Mobile Broadband (UMB) Air Interface
Specification".

[86B] 3GPP2 X.S0060-0 v1.0: "HRPD Support for Emergency Services".

[86C] 3GPP2 X.S0057-B v2.0: "E-UTRAN - eHRPD Connectivity and Interworking: Core Network
Aspects".

[86D] 3GPP2 C.S0014-C v1.0: "Enhanced Variable Rate Codec, Speech Service Options 3, 68, and 70
for Wideband Spread Spectrum Digital Systems".

[86E] 3GPP2 X.S0059-200-A v1.0: "cdma2000 Femtocell Network: 1x and IMS Network Aspects".

[86F] 3GPP2 S.R0048-A v4.0: "3G Mobile Equipment Identifier (MEID) - Stage 1".

[87] ITU-T Recommendation J.112, "Transmission Systems for Interactive Cable Television Services"

[88] PacketCable Release 2 Technical Report, PacketCable™ Architecture Framework Technical

Report, PKT-TR-ARCH-FRM.

[89] RFC 6442 (December 2011): "Location Conveyance for the Session Initiation Protocol".

[90] RFC 4119 (December 2005) "A Presence-based GEOPRIV Location Object Format".

[91] RFC 5012 (January 2008): "Requirements for Emergency Context Resolution with Internet
Technologies".

[91A] Void.

[92] RFC 5626 (October 2009): "Managing Client Initiated Connections in the Session Initiation
Protocol (SIP)".

[93] RFC 5627 (October 2009): "Obtaining and Using Globally Routable User Agent URIs (GRUUs)
in the Session Initiation Protocol (SIP)".

[94] RFC 5628 (October 2009): "Registration Event Package Extension for Session Initiation Protocol
(SIP) Globally Routable User Agent URIs (GRUUs)".

[95] Void.

[96] RFC 4168 (October 2005): "The Stream Control Transmission Protocol (SCTP) as a Transport for
the Session Initiation Protocol (SIP)".

[97] RFC 5002 (August 2007): "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-
Header)".

[98] ETSI ES 283 035 (V1.1.1): "Telecommunications and Internet Converged Services and Protocols
for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); e2 interface based
on the DIAMETER protocol".

[99] RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network
Address Translator (NAT) Traversal for Offer/Answer Protocols".

[100] RFC 5389 (October 2008): "Session Traversal Utilities for NAT (STUN)".

[101] RFC 5766 (April 2010): "Traversal Using Relays around NAT (TURN): Relay Extensions to
Session Traversal Utilities for NAT (STUN)".

[102] RFC 5768 (April 2010): "Indicating Support for Interactive Connectivity Establishment (ICE) in
the Session Initiation Protocol (SIP)".

[103] RFC 4967 (July 2007): "Dial String Parameter for the Session Initiation Protocol Uniform
Resource Identifier".

3GPP
Release 16 49 3GPP TS 24.229 V16.8.0 (2020-12)

[104] RFC 5365 (October 2008): "Multiple-Recipient MESSAGE Requests in the Session Initiation

Protocol (SIP)".

[105] RFC 5368 (October 2008): "Referring to Multiple Resources in the Session Initiation Protocol
(SIP)".

[106] RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the

Session Initiation Protocol (SIP)".

[107] RFC 5367 (October 2008): "Subscriptions to Request-Contained Resource Lists in the Session

Initiation Protocol (SIP)".

[108] RFC 4583 (November 2006): "Session Description Protocol (SDP) Format for Binary Floor
Control Protocol (BFCP) Streams".

[109] RFC 5009 (September 2007): "Private Header (P-Header) Extension to the Session Initiation
Protocol (SIP) for Authorization of Early Media".

[110] RFC 4354 (January 2006): "A Session Initiation Protocol (SIP) Event Package and Data Format
for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service".

[111] RFC 4964 (September 2007): "The P-Answer-State Header Extension to the Session Initiation
Protocol for the Open Mobile Alliance Push to Talk over Cellular".

[112] RFC 4694 (October 2006): "Number Portability Parameters for the 'tel' URI".

[113] Void.

[114] RFC 4769 (November 2006): "IANA Registration for an Enumservice Containing Public Switched
Telephone Network (PSTN) Signaling Information".

[115] RFC 4411 (February 2006): "Extending the Session Initiation Protocol (SIP) Reason Header for
Preemption Events".

[116] RFC 4412 (February 2006): "Communications Resource Priority for the Session Initiation
Protocol (SIP)".

[117] RFC 5393 (December 2008): "Addressing an Amplification Vulnerability in Session Initiation

Protocol (SIP) Forking Proxies".

[118] RFC 4896 (June 2007): "Signaling Compression (SigComp) Corrections and

ClarificationsImplementer's Guide for SigComp".

[119] RFC 5112 (January 2008): "The Presence-Specific Static Dictionary for Signaling Compression
(Sigcomp)".

[120] RFC 5688 (January 2010): "A Session Initiation Protocol (SIP) Media Feature Tag for MIME
Application Subtype".

[121] RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification
of Services".

[122] Void.

[123] Void.

[124] RFC 3986 (January 2005): "Uniform Resource Identifiers (URI): Generic Syntax".

[125] RFC 5360 (October 2008): "A Framework for Consent-Based Communications in the Session
Initiation Protocol (SIP)".

[126] RFC 7433 (January 2015): "A Mechanism for Transporting User-to-User Call Control Information
in SIP".

[126A] RFC 7434 (January 2015): "Interworking ISDN Call Control User Information with SIP".

[127] 3GPP2 X.S0011-E: "cdma2000 Wireless IP Network Standard ".

3GPP
Release 16 50 3GPP TS 24.229 V16.8.0 (2020-12)

[130] RFC 6432 (November 2011): "Carrying Q.850 Codes in Reason Header Fields in SIP (Session
Initiation Protocol) Responses".

[131] RFC 6544 (March 2012): "TCP Candidates with Interactive Connectivity Establishment (ICE)".

[132] RFC 3023 (January 2001): "XML Media Types".

[133] RFC 5502 (April 2009): "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP
Multimedia (IM) Core Network (CN) Subsystem".

[134] RFC 7316 (July 2014): "The Session Initiation Protocol (SIP) P-Private-Network-Indication

PrivateHeader (P-Header)".

[135] RFC 4585 (July 2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-
Based Feedback (RTP/AVPF)".

[136] RFC 5104 (February 2008): "Codec Control Messages in the RTP Audio-Visual Profile with
Feedback (AVPF)".

[137] RFC 5939 (September 2010): "Session Description Protocol (SDP) Capability Negotiation".

[138] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture Release 1".

[139] Void.

[140] RFC 8497 (November 2018): "Marking SIP Messages to Be Logged".

[141] Void.

[142] RFC 6228 (May 2011): "Response Code for Indication of Terminated Dialog".

[143] RFC 6223 (April 2011): "Indication of support for keep-alive".

[144] RFC 4240 (December 2005): "Basic Network Media Services with SIP".

[145] RFC 5552 (May 2009): "SIP Interface to VoiceXML Media Services".

[146] RFC 6230 (May 2011): "Media Control Channel Framework".

[147] RFC 6231 (May 2011): "An Interactive Voice Response (IVR) Control Package for the Media
Control Channel Framework".

[148] RFC 6505 (March 2012): "A Mixer Control Package for the Media Control Channel Framework".

[149] RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media
Types".

[150] RFC 5621 (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)".

[151] RFC 3862 (August 2004): "Common Presence and Instant Messaging (CPIM): Message Format".

[152] RFC 3890 (September 2004): "A Transport Independent Bandwidth Modifier for the Session
Description Protocol (SDP)".

[153] RFC 7254 (May 2014): "A Uniform Resource Name Namespace for the Global System for Mobile
Communications Association (GSMA) and the International Mobile station Equipment Identity
(IMEI)".

[154] RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".

[155] RFC 7195 (May 2014): "Session Description Protocol (SDP) Extension for Setting Audio Media
Streams over Circuit-Switched Bearers in the Public Switched Telephone Network (PSTN)".

[156] RFC 7006 (September 2013): "Miscellaneous Capabilities Negotiation in the Session Description

Protocol (SDP)".

3GPP
Release 16 51 3GPP TS 24.229 V16.8.0 (2020-12)

[157] RFC 5438 (January 2009): "Instant Message Disposition Notification (IMDN)".

[158] RFC 5373 (November 2008): "Requesting Answering Modes for the Session Initiation Protocol
(SIP)".

[160] Void.

[161] RFC 4288 (December 2005): "Media Type Specifications and Registration Procedures".

[162] RFC 7989 (October 2016): "End-to-End Session Identification in IP-Based Multimedia

Communication Networks".

[163] RFC 6026 (September 2010): "Correct Transaction Handling for 2xx Responses to Session
Initiation Protocol (SIP) INVITE Requests".

[164] RFC 5658 (October 2009): "Addressing Record-Route issues in the Session Initiation Protocol
(SIP)".

[165] RFC 5954 (August 2010): "Essential Correction for IPv6 ABNF and URI Comparison in
RFC3261".

[166] RFC 4117 (June 2005): "Transcoding Services Invocation in the Session Initiation Protocol (SIP)
using Third Party Call Control (3pcc)".

[167] RFC 4567 (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and
Real Time Streaming Protocol (RTSP)".

[168] RFC 4568 (July 2006): "Session Description Protocol (SDP) Security Descriptions for Media
Streams".

[169] RFC 3711 (March 2004): "The Secure Real-time Transport Protocol (SRTP)".

[170] RFC 6043 (March 2011): "MIKEY-TICKET: Ticket-Based Modes of Key Distribution in

Multimedia Internet KEYing (MIKEY)".

[171] RFC 4235 (November 2005): "An INVITE-Initiated Dialog Event Package for the Session
Initiation Protocol (SIP)".

[172] RFC 6871 (February 2013): "SDP media capabilities Negotiation".

[173] RFC 4488 (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit
Subscription".

[174] Void.

[175] RFC 7462 (March 2015): "URNs for the Alert-Info Header Field of the Session Initiation Protocol
(SIP)".

[176] ANSI/J-STD-036-B: "Enhanced Wireless 9-1-1, Phase 2".

[177] Void.

[178] RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)".

[179] RFC 3859 (August 2004): "Common Profile for Presence (CPP)".

[180] RFC 3860 (August 2004): "Common Profile for Instant Messaging (CPIM)".

[181] RFC 2368 (July 1998): "The mailto URL scheme".

[182] RFC 4745 (February 2007): "Common Policy: A Document Format for Expressing Privacy
Preferences".

[183] RFC 5318 (December 2008): "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-
Header (P-Header)".

3GPP
Release 16 52 3GPP TS 24.229 V16.8.0 (2020-12)

[184] RFC 4538 (June 2006): "Request Authorization through Dialog Identification in the Session
Initiation Protocol (SIP)".

[185] RFC 5547 (May 2009): "A Session Description Protocol (SDP) Offer/Answer Mechanism to
Enable File Transfer".

[186] RFC 4483 (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP)
Messages".

[187] RFC 8464 (September 2018): "A URN Namespace for Device Identity and Mobile Equipment
Identity (MEID)".

[188] RFC 6679 (August 2012): "Explicit Congestion Notification (ECN) for RTP over UDP".

[189] RFC 3168 (September 2001): "The Addition of Explicit Congestion Notification (ECN) to IP".

[190] RFC 6809 (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the
Session Initiation Protocol (SIP)".

[191] RFC 6140 (March 2011): "Registration for Multiple Phone Numbers in the Session Initiation
Protocol (SIP)".

[192] RFC 6917 (April 2013): "Media Resource Brokering".

[193] ETSI TS 101 454-1 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB

Interactive Satellite System (DVB-RCS2); Part 1: Overview and System Level specification".

[194] ETSI EN 301 545-2 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB

Interactive Satellite System (DVB-RCS2); Part 2: Lower Layers for Satellite standard".

[195] ETSI TS 101 545-3 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB

Interactive Satellite System (DVB-RCS2); Part 3: Higher Layers Satellite Specification".

[196] RFC 2616 (June 1999): "Hypertext Transfer Protocol -- HTTP/1.1".

[197] RFC 7135 (May 2014): "IANA Registering a SIP Resource Priority Header Field Namespace for
Local Emergency Communications".

[198] RFC 6357 (August 2011): "Design Considerations for Session Initiation Protocol (SIP) Overload
Control".

[199] RFC 7339 (September 2014): "Session Initiation Protocol (SIP) Overload Control".

[200] RFC 7415 (February 2015): "Session Initiation Protocol (SIP) Rate Control".

[201] RFC 7200 (April 2014): "A Session Initiation Protocol (SIP) Load-Control Event Package".

[202] ITU-T Recommendation T.38 (September 2010): "Procedures for real-time Group 3 facsimile
communication over IP networks".

[203] ISO 8601 (December 2004): "Date elements and interchange formats – Information interchange –
Representation of dates and times".

[204] RFC 5506 (April 2009): "Support for Reduced-Size Real-Time Transport Control Protocol
(RTCP)".

[205] RFC 3611 (November 2003): "RTP Control Protocol Extended Reports (RTCP XR)".

[206] RFC 4796 (February 2007): "The Session Description Protocol (SDP) Content Attribute".

[207] ISO 3166-1 (2006): "Codes for the representation of names of countries and their subdivisions –
Part 1: Country codes".

[208] RFC 8055 (January 2017): "Session Initiation Protocol (SIP) Via Header Field Parameter to
Indicate Received Realm".

[209] RFC 7090 (April 2014): "Public Safety Answering Point (PSAP) Callback".

3GPP
Release 16 53 3GPP TS 24.229 V16.8.0 (2020-12)

[210] RFC 5285 (July 2008): "A General Mechanism for RTP Header Extensions".

[211] RFC 6236 (May 2011): "Negotiation of Generic Image Attributes in the Session Description
Protocol (SDP)".

[212] RFC 20 (May 2011): "ASCII format for Network Interchange".

[213] RFC 5280 (May 2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile".

[214] RFC 6714 (August 2012): "Connection Establishment for Media Anchoring (CEMA) for the
Message Session Relay Protocol (MSRP)".

[215] RFC 6135 (February 2011): "An Alternative Connection Model for the Message Session Relay
Protocol (MSRP)".

[216] Void.

[217] RFC 7345 (August 2014): "UDP Transport Layer (UDPTL) over Datagram Transport Layer
Security (DTLS)".

[218] RFC 4279 (December 2005): "Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)".

[219] draft-ietf-mmusic-sctp-sdp-26 (April 2017): "Session Description Protocol (SDP) Offer/Answer

Procedures For Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer
Security (DTLS) Transport".

Editor's note (WI: eIMS_TELEP, CR#4856): The above document cannot be formally referenced until it is
published as an RFC.

[220] RFC 2817 (May 2000): "Upgrading to TLS Within HTTP/1.1".

[221] RFC 6062 (November 2010): "Using Relays around NAT (TURN) Extensions for TCP
Allocations".

[222] RFC 5763 (May 2010): "Framework for Establishing a Secure Real-time Transport Protocol
(SRTP) Security Context Using Datagram Transport Layer Security (DTLS)".

[223] RFC 5764 (May 2010): " Datagram Transport Layer Security (DTLS) Extension to Establish Keys
for the Secure Real-time Transport Protocol (SRTP)".

[224] RFC 7675 (October 2015): "STUN Usage for Consent Freshness".

[225] RFC 7549 (May 2015): "3GPP SIP URI Inter Operator Traffic Leg Parameter".

[226] Void.

[227] RFC 4169 (November 2005): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using
Authentication and Key Agreement (AKA) Version-2".

[228] RFC 6947 (May 2013): "The Session Description Protocol (SDP) Alternate Connectivity (ALTC)
Attribute".

[229] Void.

[230] RFC 8119 (March 2017): "SIP "cause" URI Parameter for Service Number Translation".

[231] RFC 7647 (September 2015): "Clarifications for the Use of REFER with RFC6665".

[232] RFC 7614 (August 2015): "Explicit Subscriptions for the REFER Method".

[233] RFC 7621 (August 2015): "A Clarification on the Use of Globally Routable User Agent URIs
(GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework".

[234] RFC 7913 (June 2016): "P-Access-Network-Info ABNF Update".

[235] RFC 7519 (May 2015): "JSON Web Token (JWT)".

3GPP
Release 16 54 3GPP TS 24.229 V16.8.0 (2020-12)

[236] Void.

[237] RFC 5761 (April 2010): "Multiplexing RTP Data and Control Packets on a Single Port".

[237A] RFC 8035 (November 2016): "Session Description Protocol (SDP) Offer/Answer Clarifications

for RTP/RTCP Multiplexing".

[238] draft-ietf-mmusic-data-channel-sdpneg-28 (May 2019): "SDP-based Data Channel Negotiation".

Editor's note [WI: eWebRTCi_CT, CR#5553]: The above document cannot be formally referenced until it is
published as an RFC.

[239] RFC 8498 (February 2019): "A P-Served-User Header Field Parameter for an Originating Call
Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)".

[240] draft-ietf-mmusic-dtls-sdp-32 (October 2017): "Session Description Protocol (SDP) Offer/Answer

Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security
(TLS)".

Editor's note [WI: eMEDIASEC-CT, CR#5617]: The above document cannot be formally referenced until it is
published as an RFC.

[241] RFC 8122 (March 2017): "Connection-Oriented Media Transport over the Transport Layer
Security (TLS) Protocol in the Session Description Protocol (SDP)".[242] RFC 3863
(August 2004): "Presence Information Data Format".

[243] RFC 4661 (September 2006): "An Extensible Markup Language (XML) Based Format for Event
Notification Filtering".

[244] RFC 8147 (May 2017): "Next-Generation Pan-European eCall".

[245] CEN EN 15722:2015 (April 2015): "Intelligent transport systems - ESafety - ECall minimum set
of data".

[246] draft-ietf-mmusic-mux-exclusive-12 (May 2017): "Indicating Exclusive Support of RTP/RTCP

Multiplexing using SDP".

Editor's note [WI: TEI14, IMS-WebRTC, CR#5615]: The above document cannot be formally referenced until it is
published as an RFC.

[247] RFC 7303 (July 2014): "XML Media Types".

[248] IEEE Std 802.11-2016: "IEEE Standard for Information technology - Telecommunications and

information exchange between systems - Local and metropolitan area networks - Specific
requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".

[249] draft-ietf-mmusic-sdp-simulcast-14 (March 2019): "Using Simulcast in SDP and RTP Sessions".

Editor's note [WI: MMCMH_Enh-CT, CR#5739]: The above document cannot be formally referenced until it is
published as an RFC.

[250] draft-ietf-mmusic-rid-15 (May 2018): "RTP Payload Format Restrictions".

Editor's note [WI: MMCMH_Enh-CT, CR#5739]: The above document cannot be formally referenced until it is
published as an RFC.

[251] RFC 7728 (February 2016): "RTP Stream Pause and Resume".

[252] RFC 8224 (February 2018): "Authenticated Identity Management in the Session Initiation Protocol

(SIP)".

[253] RFC 5279 (July 2008): "A Uniform Resource Name (URN) Namespace for the 3rd Generation
Partnership Project (3GPP)".

[254] RFC 8197 (July 2017): "A SIP Response Code for Unwanted Calls".

3GPP
Release 16 55 3GPP TS 24.229 V16.8.0 (2020-12)

[255] RFC 8606 (June 2019): "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason
Header Field".

[256] RFC 8262 (October 2017): "Content-ID Header Field in the Session Initiation Protocol (SIP)".

[257] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".

[258] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (5GS);
Stage 3".

[259] RFC 4715 (November 2006): "The Integrated Services Digital Network (ISDN) Subaddress

Encoding Type for tel URI".

[260] 3GPP TS 38.304: " NR; User Equipment (UE) procedures in idle mode and in RRC Inactive
state".

[261] RFC 8588 (May 2019): "Personal Assertion Token (PaSSporT) Extension for Signature-based

Handling of Asserted information using toKENs (SHAKEN)".

[262] RFC 8225 (February 2018): "PASSporT: Personal Assertion Token"

[263] 3GPP TS 24.502: " Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access
Networks (N3AN); Stage 3".

[264] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-
connectivity; Stage 2".

[265] IETF draft-ietf-stir-passport-divert-08 (March 2020): "PASSporT Extension for Diverted Calls".

Editor's note [WI: eSPECTRE, CR#6185]: The above document cannot be formally referenced until it is
published as an RFC.

[266] RFC 8787 (May 2020): "Location Source Parameter for the SIP Geolocation Header Field".

[267] RFC 5491 (March 2009): "GEOPRIV Presence Information Data Format Location Object (PIDF-
LO) Usage Clarification, Considerations, and Recommendations".

[268] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".

[269] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification".

[270] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".

[271] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".

[272] 3GPP TS 23.221: "Architectural requirements".

[273] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".

[274] 3GPP TS 29.562: "Home Subscriber Server (HSS) Services for Interworking with the IP
Multimedia Subsystem (IMS); Stage 3".

[275] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".

[276] 3GPP TS 26.238: "Uplink Streaming".

[277] IETF RFC 4574 (August 2006): "The Session Description Protocol (SDP) Label Attribute".

3GPP
Release 16 56 3GPP TS 24.229 V16.8.0 (2020-12)

3 Definitions and abbreviations

3.1 Definitions
For the purposes of the present document, the following terms and definitions apply.

3GPP PS data off status: indicates state of usage of the 3GPP PS data off. 3GPP PS data off status at the UE can be
either "active" or "inactive".

Country: For the purposes of emergency service URNs in the present document, i.e. a service URN with a top-level
service type of "sos" as specified in RFC 5031 [69], an ISO 3166-1 alpha-2 code as specified in ISO 3166-1 [207] is
used to identify a region or a country.

Entry point: In the case that "border control concepts", as specified in 3GPP TS 23.228 [7], are to be applied in an IM
CN subsystem, then these are to be provided by capabilities within the IBCF, and the IBCF acts as an entry point for
this network (instead of the I-CSCF). In this case the IBCF and the I-CSCF can be co-located as a single physical node.
If "border control concepts" are not applied, then the I-CSCF is considered as an entry point of a network. If the P-
CSCF is in the home network, then the I-CSCF is considered as an entry point for this document. Similary, in case that
"border control concepts", as specified in 3GPP TS 23.218 [5], are to be applied in an ISC interface, then these are to be
provided by capabilities within the ISC gateway function, and the ISC gateway function acts as an entry point for this
network.

Exit point: If operator preference requires the application of "border control concepts" as specified in
3GPP TS 23.228 [7], then these are to be provided by capabilities within the IBCF, and requests sent towards another
network are routed via a local network exit point (IBCF), which will then forward the request to the other network
(discovering the entry point if necessary). Similary, in case that "border control concepts", as specified in
3GPP TS 23.218 [5], are to be applied in an ISC interface, then these are to be provided by capabilities within the ISC
gateway function, and requests sent towards another network are routed via a local network exit point (ISC gateway
function).

Geo-local number: Either a geo-local service number as specified in 3GPP TS 23.228 [7] or a number in non-
international format according to an addressing plan used at the current physical location of the user.

Home-local number: Either a home local service number as specified in 3GPP TS 23.228 [7] or a number in non-
international format according to an addressing plan used in the home network of the user.

Main URI: In the case that the UE supports RFC 6140 [191] and performs the functions of an external attached
network, the main URI is the URI which is used for the registration procedures in the To header of the REGISTER
request as specified in RFC 6140 [191]; it represents the public user identities associated to that UE.

Newly established set of security associations: Two pairs of IPsec security associations that have been created at the
UE and/or the P-CSCF after the 200 (OK) response to a REGISTER request was received.

Old set of security associations: Two pairs of IPsec security associations still in existence after another set of security
associations has been established due to a successful authentication procedure.

Temporary set of security associations: Two pairs of IPsec security associations that have been created at the UE
and/or the P-CSCF, after an authentication challenge within a 401 (Unauthorized) response to a REGISTER request was
received. The SIP level lifetime of such created security associations will be equal to the value of reg-await-auth timer.

Integrity protected: See 3GPP TS 33.203 [19]. Where a requirement exists to send information "integrity-protected"
the mechanisms specified in 3GPP TS 33.203 [19] are used for sending the information. Where a requirement exists to
check that information was received "integrity-protected", then the information received is checked for compliance with
the procedures as specified in 3GPP TS 33.203 [19].

Instance ID: An URN generated by the device that uniquely identifies a specific device amongst all other devices, and
does not contain any information pertaining to the user (e.g., in GPRS instance ID applies to the Mobile Equipment
rather than the UICC). The public user identity together with the instance ID uniquely identifies a specific UA instance.
If the device has an IMEI available, it generates an instance ID based on its IMEI as defined in 3GPP TS 23.003 [3]
clause 13. If the device has an MEID as defined in 3GPP2 S.R0048-A [86F] available, it generates an instance ID based
on its MEID as defined in RFC 8464 [187]. If the device does not have an IMEI available and does not have an MEID
available, the instance ID is generated as a string representation of a UUID as a URN as defined in RFC 4122 [154].

3GPP
Release 16 57 3GPP TS 24.229 V16.8.0 (2020-12)

Resource reservation: Mechanism for reserving bearer resources that is required for certain access technologies.

Local preconditions: The indication of segmented status preconditions for the local reservation of resources as
specified in RFC 3312 [30].

Alias URI, Alias SIP URI: A URI is an alias of another URI if the treatment of both URIs is identical, i.e. both URIs
belong to the same set of implicitly registered public user identities, and are linked to the same service profile, and are
considered to have the exact same service configuration for each and every service.

NOTE 1: The S-CSCF recognizes that a given URI is an alias of another URI using the grouping sent from the HSS
(see 3GPP TS 29.228 [14]).

Globally Routeable SIP URI: a SIP URI of which the hostname part can be resolved to the IP address of the entry
entity of the network reponsible for the identity represented by the userpart.

Initial registration: The registration procedure for a public user identity initiated by the UE in the absence of any valid
registration.

Registration expiration interval: An indication on how long a registration is valid, indicated using the Expires header
field, or the "expires" header field parameter within the Contact header field, according to the procedures specified in
RFC 3261 [26].

Re-registration: The registration procedure initiated by the UE to refresh or update an already existing registration for
a public user identity.

Registration of an additional public user identity: The registration procedure initiated by the UE to explicitly register
an additional public user identity during the life time of the registration of another registered public user identity, where
both public user identities have the same contact address and P-CSCF.

Emergency registration: A special registration that relates to binding of a public user identity to a contact address used
for emergency service.

Initial emergency registration: An emergency registration that is also an initial registration.

Emergency reregistration: An emergency registration that is also a reregistration.

Back-to-Back User Agent (B2BUA): As given in RFC 3261 [26]. In addition, for the usage in the IM CN subsystem, a
SIP element being able to handle a collection of "n" User Agents (behaving each one as UAC and UAS, according to
SIP rules), which are linked by some application logic that is fully independent of the SIP rules.

UE private IP address: It is assumed that the NAT device performs network address translation between a private and
a public network with the UE located in the private network and the IM CN subsystem in the public network. The UE is
assumed to be configured with a private IP address. This address will be denoted as UE private IP address.

UE public IP address: The NAT device is assumed to be configured with one (or perhaps more) public address(es).
When the UE sends a request towards the public network, the NAT replaces the source address in the IP header of the
packet, which contains the UE private IP address, with a public IP addressed assigned to the NAT. This address will be
denoted as UE public IP address.

Encapsulating UDP header: For the purpose of performing UDP encapsulation according to RFC 3948 [63A] each
IPsec ESP packet is wrapped into an additional UDP header. This header is denoted as Encapsulating UDP header.

Port_Uenc: In most residential scenarios, when the NAT device performs address translation, it also performs
translation of the source port found in the transport layer (TCP/UDP) headers. Following RFC 3948 [63A], the UE will
use port 4500 as source port in the encapsulating UDP header when sending a packet. This port is translated by the
NAT into an arbitrarily chosen port number which is denoted as port_Uenc.

Multiple registrations: An additional capability of the UE, P-CSCF and S-CSCF, such that the UE (as identified by the
private user identity and instance-id), can create multiple simultaneous registration bindings (flows), associated with
one or more contact addresses, to any public user identity, Without this capability, a new registration from the UE for a
public user identity replaces the existing registration binding, rather than merely creating an additional binding.

IMS flow set: An IMS flow set is a set of flows as defined in RFC 5626 [92]. The flows in an IMS flow set are
determined by a combination of transport protocol, IP addresses, and ports. An IMS flow set is established by a
successful IMS registration procedure.

3GPP
Release 16 58 3GPP TS 24.229 V16.8.0 (2020-12)

NOTE 2: For IPsec, the ports associated with the flow set include protected client ports and protected server ports
as defined in 3GPP TS 33.203 [19] and an IMS flow set is made up of the following four flows:

- Flow 1: (IP address UE, port_uc) <--> (IP address P-CSCF, port_ps) over TCP;

- Flow 2: (IP address UE, port_uc) <--> (IP address P-CSCF, port_ps) over UDP;

- Flow 3: (IP address UE, port_us) <--> (IP address P-CSCF, port_pc) over TCP; and

- Flow 4: (IP address UE, port_us) <--> (IP address P-CSCF, port_pc) over UDP.

NOTE 3: For IPsec, according to 3GPP TS 33.203 [19], the P-CSCF can only select among flows 1, 3, or 4 when
forwarding requests towards the UE, where flow 1 is only possible in case of TCP connection re-use.
According to 3GPP TS 33.203 [19], flow 2 is only used for UE originated requests and corresponding
responses. The P-CSCF uses flow 2 to identify the correct IMS flow set.

NOTE 4: An IMS flow set can be considered as a realisation of a logical flow as used in RFC 5626 [92]. But this
definition does not depend on any particular definition of a logical flow.

NOTE 5: For TLS, the ports associated with the flow set include a protected client port and a protected server port
and an IMS flow set is made up of the following flow:

- (IP address UE, port) <--> (IP address P-CSCF, port) over TCP.

NOTE 6: For SIP digest without TLS, an IMS flow set is as defined in RFC 5626 [92].

IMS flow token: A IMS flow token is uniquely associated with a IMS flow set. When forwarding a request destined
towards the UE, the P-CSCF selects the flow from the IMS flow set denoted by the IMS flow token as appropriate
according to 3GPP TS 33.203 [19] and RFC 3261 [26].

IP Association: A mapping at the P-CSCF of a UE's packet source IP address, the "sent-by" parameter in the Via
header field, and, conditionally, the port with the identities of the UE. This association corresponds to the IP address
check table specified in 3GPP TS 33.203 [19].

Authorised Resource-Priority header field: a Resource-Priority header field that is either received from another
entity in the trust domain relating to the Resource-Priority header field, or which has been identified as generated by a
subscriber known to have such priority privileges for the resource priority namespace and level of priority used within
that namespace.

Temporarily authorised Resource-Priority header field: a Resource Priority header field that has been temporarily
approved by the P-CSCF, the S-CSCF, or an IBCF. Temporarily authorised Resource-Priority heaer field appears in an
INVITE request only, and is applied only in the direction P-CSCF to S-CSCF to AS, S-CSCF to AS, or IBCF to S-
CSCF to AS, for the request, and the reverse direction for 1xx responses to that request. Subsequent requests in the
same dialog will require an authorised Resource-Priority header field in order to obtain priority privileges. It is only
valid when all entities are in the same trust domain for the Resource-Priority header field.

Network-initiated resource reservation: A mechanism of resource reservation where the IP-CAN on the behalf of
network initiates the resources to the UE.

Trace depth: When SIP signalling is logged for debugging purposes, trace depth is the level of detail of what is logged.

P-CSCF restoration procedures: the procedures for the IP-CAN and the UE to handle P-CSCF service interruption
scenarios (see 3GPP TS 23.380 [7D]).

HSS based P-CSCF restoration procedures: the procedures for the IP-CAN, the IM CN subsystem, the HSS and the
UE to handle P-CSCF service interruption scenarios (see 3GPP TS 23.380 [7D]). In 5GS the procedure is called
UDM/HSS based P-CSCF restoration (see 3GPP TS 23.380 [7D]) since the UDM participates in the procedure.

PCRF based P-CSCF restoration procedures: the procedures for the IP-CAN, the IM CN subsystem, the PCRF and
the UE to handle P-CSCF service interruption scenarios (see 3GPP TS 23.380 [7D]). In 5GS the procedure is called
PCF based P-CSCF restoration (see 3GPP TS 23.380 [7D]) since the PCF takes the role of the PCRF.

Public network traffic: traffic sent to the IM CN subsystem for processing according to normal rules of the NGN. This
type of traffic is known as public network traffic.

3GPP
Release 16 59 3GPP TS 24.229 V16.8.0 (2020-12)

Private network traffic: traffic sent to the IM CN subsystem for processing according to an agreed set of rules specific
to an enterprise. This type of traffic is known as private network traffic. Private network traffic is normally within a
single enterprise, but private network traffic can also exist between two different enterprises if not precluded for
regulatory reasons.

NOTE 7: An IP-PBX or application functionality within the IM CN subsystem can change private network traffic
to public network traffic and vice versa, by functionality known as "breakout" or "breakin" to the private
network. As such a SIP transaction can be variously private network traffic and public network traffic on
different hops across a SIP network.

Privileged sender: A privileged sender is allowed to send SIP messages where the identities in P-Asserted-Identity will
be passed on in the P-CSCF and are not subject to further processing in the P-CSCF.

S-CSCF restoration procedures: the procedures for the IM CN subsystem and the UE to handle S-CSCF service
interruption scenarios (see 3GPP TS 23.380 [7D]).

Loopback routeing: A method of routeing a SIP request back to the visited network for local breakout according to the
roaming architecture for voice over IMS with local breakout as specified in 3GPP TS 23.228 [7].

UE performing the functions of an external attached network: an independent network connected to an IMS
network over the Gm interface, through a single point and which is seen by the IMS network as a specific UE; e.g. an
IP-PBX.

Static Mode of Operation: a mode of operation where the UE performing the functions of an external attached
network does not initiate any IMS level registration procedures towards the operator IMS.

Canonical form of a SIP URI: Canoncial form of a SIP URI takes the form "sip:username@domain" as specified in
RFC 3261 [26] subclause 10.3. SIP URI comparisons are performed as defined in RFC 3261 [26] subclause 19.1.4.

Originating home network: the home network of a user originating a transaction, and if applicable, the associated
dialog.

Originating visited network: the visited network of a user originating a transaction, and if applicable, the associated
dialog.

Terminating home network: the home network of a user terminating a transaction, and if applicable, the associated
dialog.

Terminating visited network: the visited network of a user terminating a transaction, and if applicable, the associated
dialog.

Type of emergency service: The type of emergency service is either an emergency call type standardized by 3GPP (see
3GPP TS 22.101 [8] subclause 10.1) or a similar capability not standardised by 3GPP and defined by national
regulatory requirements. The generic (sos) service, identified by urn:service:sos, does not have a type of emergency
service (even though usage of the generic (sos) service in the emergency call is defined).

Resource sharing: one dedicated EPS bearer is sharing resources among several ongoing sessions such that the highest
GBR (and optionally MBR) to be shared for the set of PCC/QoS rules bound to the same bearer is used as input for the
calculation of the GBR (and optionally MBR) of that bearer among the sessions sharing the resources.

Fully-Qualified Domain Name (FQDN): the syntax of the FQDN used in this specification is defined in
RFC 3261 [26] subclause 25.1.

Trusted WLAN: A trusted non-3GPP access, where the non-3GPP access is a WLAN IP access.

Untrusted WLAN: An untrusted non-3GPP access, where the non-3GPP access is a WLAN IP access.

Calling number verification status determination: A feature which enables the terminating UE to determine whether
number has been verified by the network as specified in RFC 8224 [252].

Calling number verification using signature verification and attestation information: A feature which enables a
calling identity validation as specified in RFC 8224 [252] and uses an attestation information to vouch for the accuracy
of the source of origin of the call. Attestation information consists of an attestation level and an origination identifier
and may be included in the Identity header field as defined in RFC 8588 [261] and in the Attestation-Info and
Origination-Id header fields as defined in subclauses 7.2.18 and 7.2.19.

3GPP
Release 16 60 3GPP TS 24.229 V16.8.0 (2020-12)

For the purposes of the present document, the following terms and definitions given in RFC 3261 [26] apply (unless
otherwise specified see clause 6).

Client
Dialog
Final response
Header
Header field
Loose routeing
Method
Option-tag (see RFC 3261 [26] subclause 19.2)
Provisional response
Proxy, proxy server
Recursion
Redirect server
Registrar
Request
Response
Server
Session
(SIP) transaction
Stateful proxy
Stateless proxy
Status-code (see RFC 3261 [26] subclause 7.2)
Tag (see RFC 3261 [26] subclause 19.3)
Target Refresh Request
User agent client (UAC)
User agent server (UAS)
User agent (UA)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.002 [2]
subclause 4.1.1.1 and subclause 4a.7 apply:

3GPP AAA proxy

3GPP AAA server
Breakout Gateway Control Function (BGCF)
Call Session Control Function (CSCF)
Home Subscriber Server (HSS)
Location Retrieval Function (LRF)
Media Gateway Control Function (MGCF)
MSC Server enhanced for IMS centralized services
Multimedia Resource Function Processor (MRFP)
Packet Data Gateway (PDG)
Subscription Locator Function (SLF)
WLAN UE

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.122 [4C] apply:

Equivalent Home PLMN (EHPLMN)

Home PLMN (HPLMN)
Visited PLMN (VPLMN)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.218 [5]
subclauses 3.1, 8 and 13 apply:

Filter criteria
Initial filter criteria
Initial request
ISC gateway function
Media Resource Broker (MRB)
Multimedia Resource Function Controller (MRFC)
Standalone transaction
Subsequent request

3GPP
Release 16 61 3GPP TS 24.229 V16.8.0 (2020-12)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [7]
subclauses 3.1, 4.3.3.1, 4.3.6, 4.6, 4.13, 4.15a, 5.2, 5.4.12.1, 5.10, annex U, and annex W apply:

Border control concepts

Geo-local service number
Home local service number
Implicit registration set
Interconnection Border Control Function (IBCF)
Interrogating-CSCF (I-CSCF)
IMS Application Level Gateway (IMS-ALG)
IMS application reference
IMS Application Reference Identifier (IARI)
IMS communication service
IMS Communication Service Identifier (ICSI)
IMS Services for roaming users in deployments without IMS-level roaming interfaces
Local service number
IP-Connectivity Access Network (IP-CAN)
P-CSCF enhanced for WebRTC (eP-CSCF)
Policy and Charging Rule Function (PCRF)
Private user identity
Proxy-CSCF (P-CSCF)
Public Service Identity (PSI)
Public user identity
Roaming Architecture for Voice over IMS with Local Breakout
Serving-CSCF (S-CSCF)
Statically pre-configured PSI
WebRTC IMS Client (WIC)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.292 [7C] apply:

ICS UE
SCC AS

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.167 [4B] apply:

eCall over IMS

Emergency-CSCF (E-CSCF)
Geographical location information
Location identifier
Location information

For the purposes of the present document, the following terms and definitions given in 3GPP TR 33.203 [19] apply:

GPRS-IMS-Bundled Authentication (GIBA)

Port_pc
Port_ps
Port_uc
Port_us
Protected server port
Protected client port
spi_uc
spi_us

For the purposes of the present document, the following terms and definitions given in 3GPP TR 21.905 [1] apply:

IMS Credentials (IMC)

International Mobile Equipment Identity (IMEI)
IMS SIM (ISIM)
Serial NumbeR (SNR)
Type Approval Code (TAC)
Universal Integrated Circuit Card (UICC)
Universal Subscriber Identity Module (USIM)
User Equipment (UE)

3GPP
Release 16 62 3GPP TS 24.229 V16.8.0 (2020-12)

For the purposes of the present document, the following terms and definitions given in RFC 2401 [20A] Appendix A
apply:

Security association

A number of different security associations exist within the IM CN subsystem and within the underlying access
transport. Within this document this term specifically applies to either:

i) the security association that exists between the UE and the P-CSCF. For this usage of the term, the term
"security association" only applies to IPsec. This is the only security association that has direct impact on SIP; or

ii) the security association that exists between the WLAN UE and the PDG. This is the security association that is
relevant to the discussion of Interworking WLAN as the underlying IP-CAN.

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.234 [7A] apply.

Interworking WLAN

For the purposes of the present document, the following terms and definitions given in ITU-T E.164 [57] apply:

International public telecommunication number

For the purposes of the present document, the following terms and definitions given in RFC 5012 [91] apply:

Emergency service identifier

Emergency service URN
Public Safety Answering Point (PSAP)
PSAP URI

For the purposes of the present document, the following terms and definitions given in RFC 5627 [93] apply:

Globally Routable User Agent URI (GRUU)

For the purposes of the present document, the following terms and definitions given in RFC 5626 [92] apply:

Flow

For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.310 [19D] annex E
and documents referenced therein:

TLS session

For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.292 [8O] apply:

CS media

For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.301 [8J] apply:

IMS Voice over PS Session (IMSVoPS) indicator

Persistent EPS bearer context

For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.328 [19C] apply:

End-to-access edge security

For the purposes of the present document, the following terms and definitions given in 3GPP2 S.R0048-A v4.0 [86F]
apply:

Mobile Equipment Identity (MEID)

Manufacturer code
Serial number

For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.302 [8U] apply:

Restrictive non-3GPP access network

S2a
S2b

3GPP
Release 16 63 3GPP TS 24.229 V16.8.0 (2020-12)

S2c
Trusted non-3GPP access
Untrusted non-3GPP access
Unauthenticated IMSI
Firewall traversal tunnel

For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.240 [16] apply:

Charging Data Function (CDF);

Charging Data Record (CDR)
Online Charging Function (OCF)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 32.260 [17] apply:

IM CN subsystem Charging Identifier (ICID)

For the purposes of the present document, the following terms and definitions given in RFC 8119 [230] apply:

Service access number

For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.101 [1A] apply:

eCall
Minimum Set of Data (MSD)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.011 [1C] apply:

3GPP PS data off

3GPP PS data off exempt services

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.402 [7E] apply.

TWAN

For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.604 [8ZG] apply.

Diverting user
Diverted-to party

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.221 [272] apply:

Restricted Local Operator Services

For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [257] apply:

Stand-alone Non-Public Network

3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:

1xx A status-code in the range 101 through 199, and excluding 100
2xx A status-code in the range 200 through 299
5GC 5G Core Network
5GS 5G System
5G-AN 5G Access Network
AAA Authentication, Authorization and Accounting
ANBR Access Network Bitrate Recommendation
APN Access Point
APN Access Point Name
AS Application Server
ATCF Access Transfer Control Function
AUTN Authentication TokeN
AVP Attribute-Value Pair
B2BUA Back-to-Back User Agent

3GPP
Release 16 64 3GPP TS 24.229 V16.8.0 (2020-12)

BFCP Binary Floor Control Protocol

BGCF Breakout Gateway Control Function
c conditional
BRAS Broadband Remote Access Server
BSSID Basic Service Set Identifier
CCF Charging Collection Function
CDF Charging Data Function
CDR Charging Data Record
CK Ciphering Key
CN Core Network
CPC Calling Party's Category
CLF Connectivity session Location and repository Function
CSCF Call Session Control Function
DHCP Dynamic Host Configuration Protocol
DNN Data Network Name
DNS Domain Name System
DOCSIS Data Over Cable Service Interface Specification
DRVCC Dual Radio Voice Call Continuity
DTD Document Type Definition
DTLS Datagram Transport Layer Security
DTMF Dual Tone Multi Frequency
DVB Digital Video Broadcast
DVB-RCS2 Second Generation DVB Interactive Satellite System
e2ae-security End-to-access edge security
EATF Emergency Access Transfer Function
EC Emergency Centre
ECF Event Charging Function
ECI E-UTRAN Cell Identity
ECN Explicit Congestion Notification
E-CSCF Emergency CSCF
EF Elementary File
eP-CSCF P-CSCF enhanced for WebRTC
ePDG Evolved Packet Data Gateway
EPS Evolved Packet System
FAP cdma2000® 1x Femtocell Access Point
FQDN Fully Qualified Domain Name
GBA Generic Bootstrapping Architecture
GBR Guaranteed Bit Rate
GCID GPRS Charging Identifier
GGSN Gateway GPRS Support Node
GPON Gigabit-capable Passive Optical Networks
GPRS General Packet Radio Service
GRUU Globally Routable User agent URI
GSTN General Switched Telephone Network
HPLMN Home PLMN
HSS Home Subscriber Server
HTTP HyperText Transfer Protocol
i irrelevant
IARI IMS Application Reference Identifier
IBCF Interconnection Border Control Function
ICE Interactive Connectivity Establishment
I-CSCF Interrogating CSCF
ICS Implementation Conformance Statement
ICID IM CN subsystem Charging Identifier
ICSI IMS Communication Service Identifier
ID Identifier
IK Integrity Key
IKEv2 Internet Key Exchange Protocol Version 2
IM IP Multimedia
IMC IMS Credentials
IMEI International Mobile Equipment Identity

3GPP
Release 16 65 3GPP TS 24.229 V16.8.0 (2020-12)

IMS IP Multimedia core network Subsystem

IMS-AGW IMS Access Gateway
IMS-ALG IMS Application Level Gateway
IMSI International Mobile Subscriber Identity
IMSVoPS IMS Voice over PS Session
IOI Inter Operator Identifier
IP Internet Protocol
IP-CAN IP-Connectivity Access Network
IPsec IP security
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISC IP Multimedia Subsystem Service Control
ISIM IM Subscriber Identity Module
I-WLAN Interworking – WLAN
IWF Interworking Function
KMS Key Management Service
LRF Location Retrieval Function
m mandatory
MAC Message Authentication Code
MBR Maximum guaranteed Bit Rate
MCC Mobile Country Code
MCPTT Mission Critical Push To Talk
MEID Mobile Equipment IDentity
MGCF Media Gateway Control Function
MGW Media Gateway
MNC Mobile Network Code
MRB Media Resource Broker
MRFC Multimedia Resource Function Controller
MRFP Multimedia Resource Function Processor
MSC Mobile-services Switching Centre
MSD Minimum Set of emergency related Data
MSRP Message Session Relay Protocol
n/a not applicable
NAI Network Access Identifier
NA(P)T Network Address (and Port) Translation
NASS Network Attachment Subsystem
NAT Network Address Translation
NCC Network Control Center
NCC_ID Network Control Center Identifier
NID Network Identifier
NP Number Portability
o optional
OCF Online Charging Function
OLI Originating Line Information
OMR Optimal Media Routeing
PCC Policy and Charging Control
PCF Policy Control Function
PCO Protocol Configuration Options
PCRF Policy and Charging Rules Function
P-CSCF Proxy CSCF
PDG Packet Data Gateway
PDN Packet Data Network
PDP Packet Data Protocol
PDU Protocol Data Unit
P-GW PDN Gateway
PICS Protocol Implementation Conformance Statement
PIDF-LO Presence Information Data Format Location Object
PLMN Public Land Mobile Network
PSAP Public Safety Answering Point
PSI Public Service Identity
PSTN Public Switched Telephone Network

3GPP
Release 16 66 3GPP TS 24.229 V16.8.0 (2020-12)

QCI QoS Class Identifier

QoS Quality of Service
RAND RANDom challenge
RCS Return Channel via Satellite
RCST Return Channel via Satellite Terminal
RES RESponse
RLOS Restricted Local Operator Services
RTCP Real-time Transport Control Protocol
RTP Real-time Transport Protocol
SAC Service Area Code
SAI Service Area Identifier
SBA Service Based Architecture
SBI Service Based Interface
S-CSCF Serving CSCF
SCTP Stream Control Transmission Protocol
SDES Session Description Protocol Security Descriptions for Media Streams
SDP Session Description Protocol
SDU Service Data Unit
SIP Session Initiation Protocol
SLF Subscription Locator Function
SNPN Stand-alone Non-Public Network
SNR Serial Number
SQN SeQuence Number
SRVCC Single Radio Voice Call Continuity
STUN Session Traversal Utilities for NAT
SVN Satellite Virtual Network
SVN-MAC SVN Medium Access Control label
TAC Type Approval Code
TFT Traffic Flow Template
TP Telepresence
TLS Transport Layer Security
TRF Transit and Roaming Function
TURN Traversal Using Relay NAT
TWAG Trusted WLAN Access Gateway
TWAN Trusted WLAN
UA User Agent
UAC User Agent Client
UAS User Agent Server
UDM Unified Data Management
UDPTL UDP Transport Layer
UDVM Universal Decompressor Virtual Machine
UE User Equipment
UICC Universal Integrated Circuit Card
URI Uniform Resource Identifier
URL Uniform Resource Locator
URN Uniform Resource Name
USAT Universal Subscriber Identity Module Application Toolkit
USIM Universal Subscriber Identity Module
VPLMN Visited PLMN
WebRTC Web Real-Time Communication
WIC WebRTC IMS Client
WLAN Wireless Local Area Network
x prohibited
xDSL Digital Subscriber Line (all types)
XGPON1 10 Gigabit-capable Passive Optical Networks
XMAC expected MAC
XML eXtensible Markup Language

3GPP
Release 16 67 3GPP TS 24.229 V16.8.0 (2020-12)

3A Interoperability with different IP-CAN

The IM CN subsystem can be accessed by UEs resident in different types of IP-CAN. The main body of this document,
and annex A, are general to UEs and IM CN subsystems that are accessed using any type of IP-CAN. Requirements that
are dependent on the type of IP-CAN are covered in annexes B, E, H, L, M, O, Q, R, S, U and W.

At any given time, for a given SIP transaction or dialog, the UE sees only one type of IP-CAN, as reported to it by the
lower layers. The UE follows the procedures of the IP-CAN specific annex related to the last type of IP-CAN reported,
even if it is different to one used previously. In particular, handover at the radio layers between two different access
technologies can result in such a change while the dialog or transaction proceeds.

At any given time, for a given SIP transaction or dialog, the P-CSCF sees only one type of IP-CAN, as determined by
interface to a particular resource architecture, e.g. policy and charging control, and by the access technology reported to
it over that interface, or in the absence of this, by preconfiguration in the system. The P-CSCF follows the procedures of
the IP-CAN specific annex related to the last type of IP-CAN determined, even if it is different to one used previously.
In particular, handover at the radio layers between two different access technologies can result in such a change while
the dialog or transaction proceeds.

It is the responsibility of the IP-CAN to ensure that usage of different bearer resources are synchronised on the
handover from one IP-CAN to another, e.g. so that a signalling bearer provided by one IP-CAN is a signalling bearer (if
provided by that IP-CAN) after handover, and that the appropriate QoS and resource reservation exists after handover.
There is no SIP signalling associated with handover at the IP-CAN, and therefore no change in SIP state at one entity is
signalled to the peer SIP entity when handover occurs.

In particular the following constraints exist that can have an impact on P-CSCF usage:

1) some IP-CANs can explicitly label a bearer as a signalling bearer, while others provide a bearer that has
appropriate QoS, but no explicit labelling. Therefore if handover occurs from an IP-CAN with explicit labelling,
to an IP-CAN with no explicit labelling, and then back to an IP-CAN with explicit labelling, the signalling will
then be on a bearer that is not explicitly labelled; and

2) some IP-CANs support signalling of grouping of media within particular bearers, while others do not. Therefore
if handover occurs from an IP-CAN with grouping, to an IP-CAN with no grouping, and then back to an IP-CAN
with grouping, the signalled grouping can have been lost.

When a UE supports multiple IP-CANs, but does not support handover between those IP-CANs, the annex specific to
that IP-CAN applies unmodified.

Where handover between IP-CANs occurs without a reregistration in the IM CN subsystem, the same identies and
security credentials for access to the IM CN subsystem are used before and after the handover.

At the P-CSCF, the access technology can variously use the PCRF or PCF or NASS in support of both signalling and
media bearer provision (or indeed use neither). How to determine which applies is up to network dependent rules, but
can be specific to the access technology used by each different UE. Not all access technologies are defined for use with
NASS, and not all access technologies are defined for use with the PCRF or PCF.

4 General

4.1 Conformance of IM CN subsystem entities to SIP, SDP and

other protocols
SIP defines a number of roles which entities can implement in order to support capabilities. These roles are defined in
annex A.

Each IM CN subsystem functional entity using an interface at the Gm reference point, the Ma reference point, the Mg
reference point, the Mi reference point, the Mj reference point, the Mk reference point, the Ml reference point, the Mm
reference point, the Mr reference point, the Mr' reference point, the Cr reference point, the Mw reference point, the I2
reference point, the I4 reference point and the Ici reference point, and also using the IP multimedia Subsystem Service

3GPP
Release 16 68 3GPP TS 24.229 V16.8.0 (2020-12)

Control (ISC) Interface, shall implement SIP, as defined by the referenced specifications in Annex A, and in accordance
with the constraints and provisions specified in annex A, according to the following roles.

Each IM CN subsystem entity using an interface at the Rc reference point and the Ms reference point shall implement
HTTP as defined in RFC 2616 [196].

Each IM CN subsystem entity using an interface at the W2 reference point may implement SIP as an option. The
detailed procedures of W2 interface are defined in 3GPP TS 24.371 [8Z].

The Gm reference point, the W2 reference point, the Ma reference point, the Mg reference point, the Mi reference point,
the Mj reference point, the Mk reference point, the Ml reference point, the Mm reference point, the Mr reference point,
the Mw reference point, the Cr reference point, the I2 reference point, the I4 reference point and the ISC reference point
are defined in 3GPP TS 23.002 [2]. The Ici reference point and the Ms reference point are defined in
3GPP TS 23.228 [7]. The Mr' reference point and the Rc reference point are defined in 3GPP TS 23.218 [5].

For SIP:

- The User Equipment (UE) shall provide the User Agent (UA) role, with the exceptions and additional
capabilities to SIP as described in subclause 5.1, with the exceptions and additional capabilities to SDP as
described in subclause 6.1, and with the exceptions and additional capabilities to SigComp as described in
subclause 8.1. The UE shall also provide the access technology specific procedures described in the appropriate
access technology specific annex (see subclause 3A and subclause 9.2.2). The UE may include one or several
interconnected SIP elements registered as a single logical entity when the UE performs the functions of an
external attached network (e.g. an enterprise network). This specification does not place any constraint on the
SIP role played by each of the elements as long as the compound entity appears to the IM CM subsystem as a
SIP UA with the aforementioned exceptions and additional capabilities except for the modifications defined by
the UE performing the functions of an external attached network modifying role in annex A.

NOTE 1: When the UE performs the functions of an external attached network (e.g. an enterprise network), the
internal structure of this UE is outside the scope of this specification. It is expected that in the most
common case, several SIP elements will be connected to an additional element directly attached to the IM
CN subsystem.

- The P-CSCF shall provide the proxy role, with the exceptions and additional capabilities to SIP as described in
subclause 5.2, with the exceptions and additional capabilities to SDP as described in subclause 6.2, and with the
exceptions and additional capabilities to SigComp as described in subclause 8.2. Under certain circumstances, if
the P-CSCF provides an application level gateway functionality (IMS-ALG), the P-CSCF shall provide the UA
role with the additional capabilities, as follows:

a) when acting as a subscriber to or the recipient of event information (see subclause 5.2);

b) when performing P-CSCF initiated dialog-release, even when acting as a proxy for the remainder of the
dialog (see subclause 5.2);

c) when performing NAT traversal procedures (see subclause 6.7.2); and

d) when performing media plane security procedures (see subclause 5.2).

The P-CSCF shall also provide the access technology specific procedures described in the appropriate access
technology specific annex (see subclause 3A and subclause 9.2.2).

- The I-CSCF shall provide the proxy role, with the exceptions and additional capabilities as described in
subclause 5.3.

- The S-CSCF shall provide the proxy role, with the exceptions and additional capabilities as described in
subclause 5.4, and with the exceptions and additional capabilities to SDP as described in subclause 6.3. Under
certain circumstances as described in subclause 5.4, the S-CSCF shall provide the UA role with the additional
capabilities, as follows:

a) the S-CSCF shall also act as a registrar. When acting as a registrar, or for the purposes of executing a third-
party registration, the S-CSCF shall provide the UA role;

b) as the notifier of event information the S-CSCF shall provide the UA role;

3GPP
Release 16 69 3GPP TS 24.229 V16.8.0 (2020-12)

c) when providing a messaging mechanism by sending the MESSAGE method, the S-CSCF shall provide the
UA role; and

d) when performing S-CSCF initiated dialog release the S-CSCF shall provide the UA role, even when acting as
a proxy for the remainder of the dialog.

- The MGCF shall provide the UA role, with the exceptions and additional capabilities as described in
subclause 5.5, and with the exceptions and additional capabilities to SDP as described in subclause 6.4.

- The BGCF shall provide the proxy role, with the exceptions and additional capabilities as described in
subclause 5.6.

- The AS, acting as terminating UA, or redirect server (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.1), shall
provide the UA role, with the exceptions and additional capabilities as described in subclause 5.7.2, and with the
exceptions and additional capabilities to SDP as described in subclause 6.6.

- The AS, acting as originating UA (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.2), shall provide the UA
role, with the exceptions and additional capabilities as described in subclause 5.7.3, and with the exceptions and
additional capabilities to SDP as described in subclause 6.6.

- The AS, acting as a SIP proxy (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.3), shall provide the proxy
role, with the exceptions and additional capabilities as described in subclause 5.7.4.

- The AS, performing 3rd party call control (as defined in 3GPP TS 23.218 [5] subclause 9.1.1.4), shall provide
the UA role, with the exceptions and additional capabilities as described in subclause 5.7.5, and with the
exceptions and additional capabilities to SDP as described in subclause 6.6. An AS performing media control of
an MRFC shall also support the procedures and methods described in subclause 10.2.

NOTE 2: Subclause 5.7 and its subclauses define only the requirements on the AS that relate to SIP. Other
requirements are defined in 3GPP TS 23.218 [5].

- The AS, receiving third-party registration requests, shall provide the UA role, with the exceptions and additional
capabilities as described in subclause 5.7.

- The MRFC shall provide the UA role, with the exceptions and additional capabilities as described in
subclause 5.8, and with the exceptions and additional capabilities to SDP as described in subclause 6.5. The
MRFC shall also support the procedures and methods described in subclause 10.3 for media control.

- In inline aware mode, the MRB shall provide the UA role, with the exceptions and additional capabilities as
described in subclause 5.8A. In inline unaware mode, the MRB shall provide the proxy role, with the exceptions
and additional capabilities as described in subclause 5.8A. The MRB shall also support the procedures and
methods described in subclause 10.4 for media control.

- The IBCF shall provide the proxy role, with the exceptions and additional capabilities to SIP as described in
subclause 5.10. If the IBCF provides an application level gateway functionality (IMS-ALG), then the IBCF shall
provide the UA role, with the exceptions and additional capabilities to SIP as described in subclause 5.10, and
with the exceptions and additional capabilities to SDP as described in subclause 6.7. If the IBCF provides
screening functionality, then the IBCF may provide the UA role, with the exceptions and additional capabilities
to SIP as described in subclause 5.10.

- The E-CSCF shall provide the proxy role, with the exceptions and additional capabilities as described in
subclause 5.11. Under certain circumstances as described in subclause 5.11, the E-CSCF shall provide the UA
role in accordance with RFC 3323 [33], with the additional capabilities, as follows:

a) when operator policy (e.g. determined by national regulatory requirements applicable to emergency services)
allows user requests for suppression of public user identifiers and location information, then the E-CSCF
shall provide the UA role, with the exceptions and additional capabilities to SIP as described in
subclause 5.11;

b) when performing E-CSCF initiated dialog release the E-CSCF shall provide the UA role, even when acting
as a proxy for the remainder of the dialog, e.g. for any of the reasons specified in RFC 6442 [89] or
RFC 3323 [33];

c) when acting as a notifier for the dialog event package the E-CSCF shall provide the UA role; and

3GPP
Release 16 70 3GPP TS 24.229 V16.8.0 (2020-12)

d) if operator policy allows any LRF to provide a location by value using the mechanism defined in
subclause 5.11.3. the E-CSCF shall provide the UA role.

- The LRF shall provide the UA role.

- The ISC gateway function shall provide the proxy role, with the exceptions and additional capabilities to SIP as
described in subclause 5.13. If the ISC gateway function provides an application level gateway functionality
(IMS-ALG), then the ISC gateway function shall provide the UA role, with the exceptions and additional
capabilities to SIP as described in subclause 5.13, and with the exceptions and additional capabilities to SDP as
described in subclause 6.7.

- The MSC Server enhanced for ICS shall provide the UA role, with the exceptions and additional capabilities as
described in 3GPP TS 24.292 [8O].

- The MSC server enhanced for SRVCC using SIP interface shall provide the UA role, with the exceptions and
additional capabilities as described in 3GPP TS 24.237 [8M].

- The MSC server enhanced for DRVCC using SIP interface shall provide the UA role, with the exceptions and
additional capabilities as described in 3GPP TS 24.237 [8M].

- The EATF shall provide the UA role, with the exceptions and additional capabilities as described in
3GPP TS 24.237 [8M].

- The ATCF shall:

a) provide the proxy role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M];
and

b) provide the UA role, with the exceptions and additional capabilities as described in 3GPP TS 24.237 [8M].

- Where access to the IM CN subsystem is provided using Web Real-Time Communication (WebRTC) in
accordance with 3GPP TS 24.371 [8Z], the eP-CSCF shall act as the P-CSCF in regard to the Mw reference
point. For SIP, conformance of the eP-CSCF and WIC (or whatever functionality is downloaded to the WIC) is
not specified by this document unless 3GPP TS 24.371 [8Z] specifies that these entities act as specified for the
interface Gm reference point, in which case existing P-CSCF and UE procedures apply, with the exceptions and
additional capabilities as described in 3GPP TS 24.371 [8Z]. For SDP, these entities act as specified for the
interface Gm reference point, in which case existing P-CSCF and UE procedures apply, with the exceptions and
additional capabilities as described in 3GPP TS 24.371 [8Z].

In addition to the roles specified above, the P-CSCF, the I-CSCF, the IBCF, the S-CSCF, the BGCF, the E-CSCF and
the ISC gateway function can act as a UA when providing server functionality to return a final response for any of the
reasons specified in RFC 3261 [26].

In addition to the roles specified above the S-CSCF, AS and an entity hosting the additional routeing capabilities as
specified in subclause I.3 can act as a UA when providing either client or server functionality when the event package
associated with overload control is deployed.

NOTE 3: Annex A can change the status of requirements in referenced specifications. Particular attention is drawn
to table A.4 and table A.162 for capabilities within referenced SIP specifications, and to table A.317 and
table A.328 for capabilities within referenced SDP specifications. The remaining tables build on these
initial tables.

NOTE 4: The allocated roles defined in this clause are the starting point of the requirements from the IETF SIP
specifications, and are then the basis for the description of further requirements. Some of these extra
requirements formally change the proxy role into a B2BUA. In all other respects other than those more
completely described in subclause 5.2 the P-CSCF implements proxy requirements. Despite being a
B2BUA a P-CSCF does not implement UA requirements from the IETF RFCs, except as indicated in this
specification, e.g., relating to registration event subscription.

NOTE 5: Except as specified in clause 5 or otherwise permitted in RFC 3261, the functional entities providing the
proxy role are intended to be transparent to data within received requests and responses. Therefore these
entities do not modify message bodies. If local policy applies to restrict such data being passed on, the
functional entity has to assume the UA role and reject a request, or if in a response and where such
procedures apply, to pass the response on and then clear the session using the BYE method.

3GPP
Release 16 71 3GPP TS 24.229 V16.8.0 (2020-12)

All the above entities are functional entities that could be implemented in a number of different physical platforms
coexisting with a number of other functional entities. The implementation shall give priority to transactions at one
functional entity, e.g. that of the E-CSCF, over non-emergency transactions at other entities on the same physical
implementation. Such priority is similar to the priority within the functional entities themselves specified elsewhere in
this document.

Additional routeing functionality can be provided to support the ability for the IM CN subsystem to provide transit
functionality as specified in Annex I. The additional routeing functionality shall assume the proxy role.

4.2 URI and address assignments

In order for SIP and SDP to operate, the following prerequisite conditions apply:

1) I-CSCFs used in registration are allocated SIP URIs. Other IM CN subsystem entities may be allocated SIP
URIs. For example sip:pcscf.home1.net and sip:<impl-specific-info>@pcscf.home1.net are valid SIP URIs. If
the user part exists, it is an essential part of the address and shall not be omitted when copying or moving the
address. How these addresses are assigned to the logical entities is up to the network operator. For example, a
single SIP URI may be assigned to all I-CSCFs, and the load shared between various physical boxes by
underlying IP capabilities, or separate SIP URIs may be assigned to each I-CSCF, and the load shared between
various physical boxes using DNS SRV capabilities.

2) All IM CN subsystem entities are allocated IP addresses. Any IM CN subsystem entities can be allocated IPv4
only, IPv6 only or both IPv4 and IPv6 addresses. For systems providing access to IM CN subsystem using a
GPRS IP-CAN or an EPS IP-CAN this is specified in 3GPP TS 23.221 [6] subclause 5.1. For systems providing
access to IM CN subsystem using a cdma2000® packet data subsystem IP-CAN this is specified in
subclause M.2.2.1. For systems providing access to IM CN subsystem using a 5GS IP-CAN this is specified in
3GPP TS 23.501 [257], subclause 5.8.2.2.

3) The subscriber is allocated a private user identity by the home network operator. This private user identity is
available to the SIP application within the UE. Depending on the network operator, various arrangements exist
within the UE for retaining this information:

a) where an ISIM is present, within the ISIM, see subclause 5.1.1.1A;

b) where no ISIM is present but USIM is present, the private user identity is derived (see subclause 5.1.1.1A);

c) neither ISIM nor USIM is present, but IMC is present, within IMC (see subclause 5.1.1.1B.1);

d) when neither ISIM nor USIM nor IMC is present, the private user identity is available to the UE via other
means (see subclause 5.1.1.1B.2).

NOTE 1: 3GPP TS 33.203 [19] specifies that a UE attached to a 3GPP network has an ISIM or a USIM.

NOTE 2: The SIP URIs can be resolved by using any of public DNSs, private DNSs, or peer-to-peer agreements.

4) The subscriber is allocated one or more public user identities by the home network operator. The public user
identity shall take the form of SIP URI as specified in RFC 3261 [26] or tel URI as specified in RFC 3966 [22].
At least one of the public user identities is a SIP URI. All registered public user identities are available to the SIP
application within the UE, after registration. Depending on the network operator, various arrangements exist
within the UE for retaining this information:

a) where an ISIM is present, at least one public user identity, which is a SIP URI, within the ISIM, see
subclause 5.1.1.1A;

b) where no ISIM is present but USIM is present, a temporary public user identity is derived (see
subclause 5.1.1.1A);

c) neither ISIM nor USIM is present, but IMC is present, within IMC (see subclause 5.1.1.1B.1);

d) when neither ISIM nor USIM nor IMC is present, the public user identities are available to the UE via other
means (see subclause 5.1.1.1B.2).

NOTE 3: 3GPP TS 33.203 [19] specifies that a UE attached to a 3GPP network has an ISIM or a USIM.

3GPP
Release 16 72 3GPP TS 24.229 V16.8.0 (2020-12)

5) If the UE supports GRUU (see table A.4, item A.4/53) or multiple registrations, then it shall have an Instance ID,
in conformance with the mandatory requirements for Instance IDs specified in RFC 5627 [93] and
RFC 5626 [92].

6) For each tel URI, there is at least one alias SIP URI in the set of implicitly registered public user identities that is
used to implicitly register the associated tel URI.

NOTE 4: For each tel URI, there always exists a SIP URI that has identical user part as the tel URI and the "user"
SIP URI parameter equals "phone" (see RFC 3261 [26] subclause 19.1.6), that represents the same public
user identity. If a tel URI identifies a subscriber served by the IM CN subsystem, then the hostport
parameter of the respective SIP URI contains the home network domain name of the IM CN subsystem to
which the subscriber belongs.

6A) Identification of the UE to a PSAP with point of presence in the CS domain is not possible if a tel URI is not
included in the set of implicitly registered public user identities. If the included tel URI is associated either with
the first entry in the list of public user identities provisioned in the UE or with the temporary public user identity,
then a PSAP can uniquely identify the UE if emergency registration is performed.

NOTE 5: The tel URI uniquely identifies the UE by not sharing any of the implicit registered public user identities
in the implicit registration set that contains this tel URI.

NOTE 6: Emergency registration is not always needed or supported.

7) The public user identities may be shared across multiple UEs. A particular public user identity may be
simultaneously registered from multiple UEs that use different private user identities and different contact
addresses. When reregistering and deregistering a given public user identity and associated contact address, the
UE will use the same private user identity that it had used during the initial registration of the respective public
user identity and associated contact address. If the tel URI is a shared public user identity, then the associated
alias SIP URI is also a shared public user identity. Likewise, if the alias SIP URI is a shared public user identity,
then the associated tel URI is also a shared public user identity.

8) For the purpose of access to the IM CN subsystem, UEs can be allocated IPv4 only, IPv6 only or both IPv4 and
IPv6 addresses. For systems providing access to IM CN subsystem using a GPRS IP-CAN or an EPS IP-CAN
this is specified in 3GPP TS 23.221 [6] subclause 5.1 (see subclause 9.2.1 for the assignment procedures). For
systems providing access to IM CN subsystem using a cdma2000® network this is specified in
subclause M.2.2.1. For systems providing access to IM CN subsystem using a 5GS IP-CAN this is specified in
3GPP TS 23.501 [257], subclause 5.8.2.2.

9) For the purpose of indicating an IMS communication service to the network, UEs are assigned ICSI values
appropriate to the IMS communication services supported by the UE, coded as URNs as specified in
subclause 7.2A.8.2.

NOTE 7: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA).

10)E-CSCFs are allocated multiple SIP URIs. The SIP URI configured in the P-CSCF, AS or IBCF to reach the E-
CSCF is distinct from the one given by the E-CSCF to the EATF such that EATF can reach the E-CSCF.

11)If the UE supports RFC 6140 [191] and performs the functions of an external attached network, the subscriber is
allocated one or usually more public user identities by the home network operator. The public user identity(s)
shall be allocated as global numbers in the international format.

4.2A Transport mechanisms

This document makes no requirement on the transport protocol used to transfer signalling information over and above
that specified in RFC 3261 [26] clause 18, unless such requirement is defined in the access technology specific annex
for the current access technology (see subclause 3A). However, the UE and IM CN subsystem entities shall transport
SIP messages longer than 1300 bytes according to the procedures of RFC 3261 [26] subclause 18.1.1, even if a
mechanism exists of discovering a maximum transmission unit size longer than 1500 bytes.

NOTE 1: Support of SCTP as specified in RFC 4168 [96] is optional for IM CN subsystem entities implementing
the role of a UA or proxy. SCTP transport between the UE and P-CSCF is not supported in the present
document. Support of the SCTP transport is currently not described in 3GPP TS 33.203 [19].

3GPP
Release 16 73 3GPP TS 24.229 V16.8.0 (2020-12)

For initial REGISTER requests, the UE and the P-CSCF shall apply port handling according to subclause 5.1.1.2 and
subclause 5.2.2.

The UE and the P-CSCF shall send and receive request and responses other than initial REGISTER requests on the
protected ports as described in 3GPP TS 33.203 [19].

In case of an emergency session if the UE does not have sufficient credentials to authenticate with the IM CN
subsystem and regulations allow, the UE and P-CSCF shall send request and responses other than initial REGISTER
requests on non protected ports.

NOTE 2: When TCP is used to carry SIP signalling between the UE and the P-CSCF, it is known that there is no
NAT between the UE and the P-CSCF and neither TLS nor the multiple registration mechanism is used,
then both the UE and the P-CSCF can decide to close an existing TCP connection subject to the
conditions described in RFC 3261 [26].

4.2B Security mechanisms

4.2B.1 Signalling security
3GPP TS 33.203 [19] defines the security features and mechanisms for secure access to the IM CN subsystem. This
document defines a number of access security mechanisms, as summarised in table 4-1.

3GPP
Release 16 74 3GPP TS 24.229 V16.8.0 (2020-12)

Table 4-1: Summary of access security mechanisms to the IM CN subsystem

Mechanism Authenticati Integrity Use of security Support (as defined

on protection agreement in in
accordance with 3GPP TS 33.203 [19])
RFC 3329 [48]
IMS AKA plus IPsec IMS AKA IPsec ESP Yes Mandatory for all UEs
ESP (see containing a UICC,
3GPP TS 33.203 [19] else optional.
clause 6) Mandatory for all P-
CSCF, I-CSCF, S-
CSCF
IMS AKA using HTTP IMS AKA TLS No Mandatory for all UEs
Digest AKAv2 without session containing a WIC able
IPSec security (note 7) to access to UICC.
association (see Mandatory for all eP-
3GPP TS 33.203 [19] CSCF, Optional for S-
annex X) CSCF
SIP digest plus check SIP digest None No Optional for UEs
of IP association (see (note 3) Optional for P-CSCF,
3GPP TS 33.203 [19] I-CSCF, S-CSCF
annex N) (note 2)
SIP digest plus Proxy SIP digest None No Optional for UEs
Authentication (see (note 3) Optional for P-CSCF,
3GPP TS 33.203 [19] I-CSCF, S-CSCF
annex N) (note 2)
SIP digest with TLS SIP digest TLS Yes Optional for UEs
(see session Optional for P-CSCF,
3GPP TS 33.203 [19] I-CSCF, S-CSCF
annex N and
annex O)
NASS-IMS bundled not None No No UE support
authentication (see applicable (note 3) required
3GPP TS 33.203 [19] (note 1) Optional for P-CSCF,
annex R) (notes 4, 5) I-CSCF, S-CSCF
GPRS-IMS-Bundled not None No Optional for UEs
authentication (see applicable (note 3) Optional for P-CSCF,
3GPP TS 33.203 [19] (note 1) I-CSCF, S-CSCF
annex S) (note 5)
Trusted node not None No No UE support
authentication (see applicable (note 3) required
3GPP TS 33.203 [19] (note 6) Optional for I-CSCF,
annex U) S-CSCF
SIP over TLS with TLS client TLS No Mandatory for a UE
client certificate certificate session performing the
authentication (see functions of an
3GPP TS 33.203 [19] external attached
annex O) network operating in
static mode

Optional for IBCF and

P-CSCF
NOTE 1: Authentication is not provided as part of the IM CN subsystem signalling.
NOTE 2: The term "SIP digest without TLS" is used in this specification to refer to both "SIP digest
plus check of IP association" and "SIP digest plus Proxy Authentication".
NOTE 3: This security mechanism does not allow SIP requests to be protected using an IPsec
security association because it does not perform a key agreement procedure.
NOTE 4: A P-Access-Network-Info aware P-CSCF is required in order to provide NASS-IMS
bundled authentication.
NOTE 5: The P-CSCF is restricted to the home network when performing this security mechanism.
NOTE 6: Trusted node authentication. For example the MSC server enhanced for IMS centralized
services has authenticated the UE and as a consequence S-CSCF will skip
authentication.
NOTE 7: SIP requests received at the eP-CSCF are protected by a TLS session established prior
registration (see 3GPP TS 33.203 [19] annex X).

3GPP
Release 16 75 3GPP TS 24.229 V16.8.0 (2020-12)

Specification of the mechanisms identified within table 4-1 within this document are provided in clause 5. Subclauses
where security procedures are required consist of a general subclause applicable whichever security mechanisms are in
use, and a separate subclause for each security mechanism identified by a row within table 4-1.

For access to the IM CN subsystem different than WebRTC TLS is optional to implement and is used only in
combination with SIP digest authentication. For WebRTC based access to the IM CN subsystem TLS can be used in
combination with IMS AKA using HTTP Digest AKAv2 without IPSec security association. Authentication associated
with registration to the IM CN subsystem is applicable to IMS AKA and SIP digest and is covered in subclause 5.1.1
for the UE, subclause 5.2.2 for the P-CSCF and subclause 5.4.1 for the S-CSCF. Additionally, SIP digest allows for
authentication to also occur on an initial request for a dialog or a request for a standalone transaction, this additional
capability is covered in subclause 5.1.2A and subclause 5.4.3.2.

If a UE that implements SIP digest is configured not to use TLS, then the UE does not establish a TLS session toward
the P-CSCF. If a UE supports TLS, then the UE supports TLS as described in 3GPP TS 33.203 [19].

For SIP digest authentication, the P-CSCF can be configured to have TLS required or disabled:

- if TLS is required, the P-CSCF requires the establishment of a TLS session from all SIP digest UEs, in order to
access IMS subsequent to registration; or

- if TLS is disabled, the P-CSCF does not allow the establishment of a TLS session from any UE.

NOTE: The mechanism to configure the P-CSCF to have TLS required or disabled is outside the scope of this
specification.

SIP digest cannot be used in conjunction with the procedures of Annex F.

For emergency calls, 3GPP TS 33.203 [19] specifies some relaxations, which are further described in the subclauses of
this document relating to emergency calls.

3GPP TS 33.210 [19A] defines the security architecture for network domain IP based control planes.
3GPP TS 33.210 [19A] applies for security mechanisms between entities in the IM CN subsystem.

4.2B.2 Media security

3GPP TS 33.328 [19C] defines mechanisms for support of security on the media plane.

This document defines the required elements for signalling the support of media security.

The media security mechanisms are summarised as shown in table 4-2.

3GPP
Release 16 76 3GPP TS 24.229 V16.8.0 (2020-12)

Table 4-2: Summary of media security mechanisms to the IM CN subsystem

3GPP
Release 16 77 3GPP TS 24.229 V16.8.0 (2020-12)

Mechanism Applicable to media Support required Support required Network support

by UE by IM CN outside IM CN
subsystem entities subsystem entities
End-to-access-edge RTP based media Support RFC 3329 P-CSCF (IMS-ALG) Not applicable.
media security using only. additions specified in is required.
SDES. subclause 7.2A.7 P-CSCF support of
and SDP extensions RFC 3329 additions
specified in table specified in
A.317, items subclause 7.2A.7
A.317/34, A.317/36 and SDP extensions
and A.317/37. specified in table
A.317, items
A.317/34, A.317/36
and A.317/37.
(NOTE)
End-to-access-edge MSRP based media Support RFC 3329 P-CSCF (IMS-ALG) Not applicable.
media security for only. additions specified in is required.
MSRP using TLS subclause 7.2A.7 P-CSCF support of
and certificate and SDP extensions RFC 3329 additions
fingerprints. specified in specified in
table A.317, items subclause 7.2A.7
A.317/40, A.317/40A, and SDP extensions
A.317/51 and specified in
A.317/37A. table A.317, items
A.317/40, A.317/40A,
A.317/51 and
A.317/37A.
(NOTE)
End-to-access-edge BFCP based media Support RFC 3329 P-CSCF (IMS-ALG) Not applicable.
media security for only. additions specified in is required.
BFCP using TLS and subclause 7.2A.7 P-CSCF support of
certificate and SDP extensions RFC 3329 additions
fingerprints. specified in specified in
table A.317, items subclause 7.2A.7
A.317/28, A.317/51 and SDP extensions
and A.317/37B. specified in
table A.317, items
A.317/28, A.317/51
and A.317/37B.
(NOTE)
End-to-access-edge UDPTL based media Support RFC 3329 P-CSCF (IMS-ALG) Not applicable.
media security for only. additions specified in is required.
UDPTL using DTLS subclause 7.2A.7 P-CSCF support of
and certificate and SDP extensions RFC 3329 additions
fingerprints. specified in specified in
table A.317, items subclause 7.2A.7
A.317/52, A.317/51 and SDP extensions
and A.317/37C. specified in
table A.317, items
A.317/52, A.317/51
and A.317/37C.
(NOTE)
End-to-end media RTP based media Support SDP Not applicable. Not applicable.
security using SDES. only. extensions specified
in table A.317, items
A.317/34 and
A.317/36.
End-to-end media RTP based media Support SDP Not applicable. GBA and KMS
security using KMS. only. extensions specified support required.
in table A.317, items
A.317/34 and
A.317/35.
End-to-end media MSRP based media Support SDP Not applicable. GBA and KMS
security for MSRP only. extensions specified support required.
using TLS and KMS. in table A.317, items
A.317/40, A.317/40A
and A.317/35, and
support

3GPP
Release 16 78 3GPP TS 24.229 V16.8.0 (2020-12)

RFC 4279 [218].
NOTE: Support of end-to-access-edge media security is determined entirely by the network operator of the P-
CSCF, which need not be the same network operator as that of the S-CSCF.

For RTP media security, the UE supports the SDES key management protocol and optionally the KMS key
management protocol as defined in 3GPP TS 33.328 [19C] and SRTP as defined in RFC 3711 [169] for secure transport
of media.

For end-to-access-edge media security for MSRP using TLS and certificate fingerprints, the UE supports MSRP over
TLS as defined in RFC 4975 [178] and RFC 6714 [214] with certificate fingerprints as defined in
3GPP TS 33.328 [19C].

For end-to-access-edge media security for BFCP using TLS and certificate fingerprints, the UE supports BFCP over
TLS as defined in RFC 4583 [108] with certificate fingerprints as defined in 3GPP TS 33.328 [19C].

For end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, the UE supports UDPTL
over DTLS as defined in RFC 7345 [217] and draft-ietf-mmusic-dtls-sdp [240], with certificate fingerprints as defined
in 3GPP TS 33.328 [19C].

For end-to-end media security for MSRP using TLS and KMS, the UE supports MSRP over TLS as defined in
RFC 4975 [178] and RFC 6714 [214] with pre-shared key ciphersuites as defined in RFC 4279 [218] and the KMS key
management protocol as defined in 3GPP TS 33.328 [19C]. The certificate fingerprints are not indicated.

There is no support for media security in the MGCF, because there would be no end-to-end media security support on
calls interworked with the CS domain and the CS user. In this release of this document, there is no support for media
security in the MRF. End-to-access-edge media security is not impacted by this absence of support.

For emergency calls, it is not expected that PSAPs would support end-to-end media security and therefore the
procedures of this document do not allow the UE to establish such sessions with end-to-end media security. End-to-
access-edge media security is not impacted and can be used on emergency calls.

When the UE performs the functions of an external attached network (e.g. an enterprise network):

- where end-to-access-edge media security is used, the UE functionality is expected to be in the gateway of the
external attached network, and support for further media security is outside the scope of this document; and

- where end-to-end media security is used, the UE functionality is expected to be supported by the endpoints in the
attached network.

4.3 Routeing principles of IM CN subsystem entities

Each IM CN subsystem functional entity shall apply loose routeing policy as described in RFC 3261 [26], when
processing a SIP request. In cases where the I-CSCF, IBCF, S-CSCF and the E-CSCF may interact with strict routers in
non IM CN subsystem networks, the I-CSCF, IBCF, S-CSCF and E-CSCF shall use the routeing procedures defined in
RFC 3261 [26] to ensure interoperability with strict routers.

4.4 Trust domain

4.4.1 General
A trust domain can apply for specific header fields, tel URI parameters and SIP URI parameters within the IM CN
subsystem.

For the IM CN subsystem, this trust domain consists of the functional entities that belong to the same operator's
network (P-CSCF, the eP-CSCF, the E-CSCF, the I-CSCF, the IBCF, the S-CSCF, the BGCF. the MGCF, the MRFC,
the MRB, the EATF, the ATCF, the ISC gateway function, and all ASs that are included in the trust domain).
Additionally, other nodes within the IM CN subsystem that are not part of the same operator's domain may or may not
be part of the trust domain, depending on whether an interconnect agreement exists with the remote network. SIP
functional entities that belong to a network for which there is an interconnect agreement are part of the trust domain.

3GPP
Release 16 79 3GPP TS 24.229 V16.8.0 (2020-12)

ASs outside the operator's network can also belong to the trust domain if they have a trusted relationship with the home
network.

NOTE 1: Whether any peer functional entity is regarded as part of the same operator's domain, and therefore part of
the same trust domain, is dependent on operator policy which is preconfigured into each functional entity.

NOTE 2: For the purpose of this document, the PSAP is typically regarded as being within the trust domain, except
where indicated. National regulator policy applicable to emergency services determines the trust domain
applicable to certain header fields. This means that e.g. the handling of the P-Access-Network-Info header
field, P-Asserted-Identity header field and the History-Info header field can be as if the PSAP is within
the trust domain, and trust domain issues will be resolved accordingly.

The trust domain can exist for a number of purposes:

a) for the protection of information specific to an operator;

b) to provide for privacy requirements of the end user; or

c) to ensure that information is only passed to another entity if certain responsibilities related to that information are
met by the receiving entity, for example that the signalled requirements in the Privacy header field will be met
(see subclause 4.4.2 and 4.4.4).

Within the IM CN subsystem trust domains will be applied to a number of header fields. These trust domains do not
necessarily contain the same functional entities or cover the same operator domains. The procedures in this subclause
apply to the functional entities in clause 5 in the case where a trust domain boundary for that header field, tel URI
parameter, or SIP URI parameter, exists at that functional entity.

Where the IM CN subsystem supports business communication, different trust domains can apply to public network
traffic, and to private network traffic belonging to each supported corporate network.

NOTE 3: Where an external attached network (e.g. an enterprise network) is in use, the edges of the trust domains
need not necessarily lie at the P-CSCF. In this release of the specification, the means by which the P-
CSCF learns of such attached devices, and therefore different trust domain requirements to apply, is not
provided in the specification and is assumed to be by configuration or by a mechanism outside the scope
of this release of the specification.

A trust domain applies for the purpose of the following header fields: P-Asserted-Identity, P-Access-Network-Info,
History-Info, Resource-Priority, P-Asserted-Service, Reason (only in a response), P-Profile-Key, P-Private-Network-
Indication, P-Served-User, P-Early-Media, Feature-Caps Restoration-Info, Relayed-Charge, Service-Interact-Info,
Cellular-Network-Info, Response-Source, Attestation-Info, Origination-Id and Additional-Identity. A trust domain
applies for the purpose of the CPC and OLI tel URI parameters. A trust domain applies for the iotl SIP URI parameter.
The trust domains of these header fields and parameters need not have the same boundaries. Clause 5 defines additional
procedures concerning these header fields, tel URI parameters and SIP URI parameter.

4.4.2 P-Asserted-Identity
RFC 3325 [34] provides for the existence and trust of an asserted identity within a trust domain. A functional entity at
the boundary of the trust domain will need to determine whether to remove the P-Asserted-Identity header field
according to RFC 3325 [34] when SIP signalling crosses the boundary of the trust domain. The priv-value "id" shall not
be removed from the Privacy header field when SIP signalling crosses the boundary of the trust domain. Subclause 5.4
identifies additional cases for the removal of the P-Asserted-Identity header field.

4.4.3 P-Access-Network-Info
A functional entity at the boundary of the trust domain shall remove any P-Access-Network-Info header field according
to RFC 7315 [52].

4.4.4 History-Info
A functional entity at the boundary of the trust domain will need to determine whether to remove the History-Info
header field according to RFC 7044 [66] subclause 10.1.2 when SIP signalling crosses the boundary of the trust domain.
Subclause 5.4 identifies additional cases for the removal of the History-Info header field.

3GPP
Release 16 80 3GPP TS 24.229 V16.8.0 (2020-12)

4.4.5 P-Asserted-Service
A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Asserted-
Service header field according to RFC 6050 [121] when SIP signalling crosses the boundary of the trust domain.

4.4.6 Resource-Priority
A functional entity shall only include a Resource-Priority header field in a request or response forwarded to another
entity within the trust domain. If a request or response is forwarded to an entity outside the trust domain, the functional
entity shall remove the Resource-Priority header field from the forwarded request or response. If a request or response
is received from an untrusted entity (with the exception requests or responses received by the P-CSCF from the UE for
which procedures are defined in subclause 5.2) that contains the Resource-Priority header field, the functional entity
shall remove the Resource-Priority header field before forwarding the request or response within the trust domain.

NOTE: Alternate treatments can be applied when a non-trusted Resource-Priority header field is received over the
boundary of trust domain. The exact treatment (e.g. removal, modification, or passing of the Resource-
Priority header field) is left to national regulation and network configuration.

4.4.7 Reason (in a response)

A functional entity shall only include a Reason header field in a response forwarded to another entity within the trust
domain (as specified in RFC 6432 [130]). If a response is forwarded to an entity outside the trust domain, the functional
entity shall remove the Reason header field from the forwarded response.

NOTE: A Reason header field can be received in a response from outside the trust domain and will not be
removed.

4.4.8 P-Profile-Key
A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Profile-Key
header field as defined in RFC 5002 [97] when SIP signalling crosses the boundary of the trust domain.

4.4.9 P-Served-User
A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Served-User
header field according to RFC 5502 [133] when SIP signalling crosses the boundary of the trust domain.

4.4.10 P-Private-Network-Indication
A functional entity shall only include a P-Private-Network-Indication header field in a request forwarded to another
entity within the trust domain. If a request is forwarded to an entity outside the trust domain, the functional entity shall
remove the P-Private-Network-Indication header field from the forwarded request. If a request is received from an
untrusted entity that contains the P-Private-Network-Indication header field, the functional entity shall remove the P-
Private-Network-Indication header field before forwarding the request within the trust domain.

NOTE 1: Other entities within the enterprise will frequently be part of this trust domain.

NOTE 2: The presence of the P-Private-Network-Indication header field is an indication that the request constitutes
private network traffic. This can modify the trust domain behaviour for other header fields.

NOTE 3: If a trust domain boundary is encountered for this header field without appropriate business
communication processing, then this can be an indication that misconfiguration has occurred in the IM
CN subsystem. Removal of this header field changes the request from private network traffic to public
network traffic.

4.4.11 P-Early-Media
A functional entity at the boundary of the trust domain will need to determine whether to remove the P-Early-Media
header field as defined in RFC 5009 [109] when SIP signalling crosses the boundary of the trust domain.

3GPP
Release 16 81 3GPP TS 24.229 V16.8.0 (2020-12)

4.4.12 CPC and OLI

Entities in the IM CN subsystem shall restrict "cpc" and "oli" URI parameters to specific domains that are trusted and
support the "cpc" and "oli" URI parameters. Therefore for the purpose of the "cpc" and "oli" URI parameters within this
specification, a trust domain also applies.

SIP functional entities within the trust domain shall remove the "cpc" and "oli" URI parameters when the SIP signalling
crosses the boundary of the trust domain.

4.4.13 Feature-Caps
A functional entity at the boundary of the trust domain shall remove all Feature-Caps header fields received from UEs
and external networks outside the trust domain.

NOTE: A UE that is a privileged sender is considered as part of the trust domain.

4.4.14 Priority
Based on local policy, a functional entity at the boundary of the trust domain shall remove all Priority header fields with
a "psap-callback" header field value.

4.4.15 iotl
Entities in the IM CN subsystem shall restrict "iotl" URI parameter to specific domains that are trusted and support the
"iotl" URI parameter. Support implies that the parameter is removed before the containing request is sent over an
interface of a different type. Therefore for the purpose of the "iotl" URI parameter within this specification, a trust
domain also applies.

SIP functional entities within the trust domain shall remove the "iotl" URI parameter when the SIP signalling crosses
the boundary of the trust domain.

4.4.16 Restoration-Info
A functional entity at the boundary of the trust domain will need to determine whether to remove the Restoration-Info
header field when SIP signalling crosses the boundary of the trust domain.

4.4.17 Relayed-Charge
Entities in the IM CN subsystem shall restrict the Relayed-Charge header field to specific domains that are trusted and
support the Relayed-Charge header field. Trust implies that the sending domain intends the receiving domain to have
the contents of this header field. Therefore for the purpose of the Relayed-Charge header field within this specification,
a trust domain also applies.

SIP functional entities within the trust domain shall remove the Relayed-Charge header field when the SIP signalling
crosses the boundary of the trust domain.

4.4.18 Service-Interact-Info
A functional entity at the boundary of the trust domain shall remove all Service-Interact-Info header fields defined in
subclause 7.2.when SIP signalling crosses the boundary of the trust domain.

4.4.19 Cellular-Network-Info
A functional entity shall only include a Cellular-Network-Info header field in a request forwarded to another entity
within the trust domain. If a request is forwarded to an entity outside the trust domain, the functional entity shall remove
the Cellular-Network-Info header field from the forwarded request. If a request is received from an untrusted entity that
contains the Cellular-Network-Info header field, the functional entity shall remove Cellular-Network-Info header field
before forwarding the request within the trust domain.

3GPP
Release 16 82 3GPP TS 24.229 V16.8.0 (2020-12)

4.4.20 Response-Source
A functional entity at the boundary of the trust domain will need to determine whether to remove the Response-Source
header field according to subclause 7.2.17. when SIP signalling crosses the boundary of the trust domain.

4.4.21 Attestation-Info header field

A functional entity at the boundary of the trust domain will need to determine whether to remove the Attestation-Info
header field according to subclause 7.2.18. when SIP signalling crosses the boundary of the trust domain.

4.4.22 Origination-Id header field

A functional entity at the boundary of the trust domain will need to determine whether to remove the Origination-Id
header field according to subclause 7.2.19 when SIP signalling crosses the boundary of the trust domain.

4.4.23 Additional-Identity header field

A functional entity at the boundary of the trust domain will need to determine whether to remove the Additional-
Identity header field according to subclause 7.2.20 when SIP signalling crosses the boundary of the trust domain.

4.5 Charging correlation principles for IM CN subsystems

4.5.1 Overview
This subclause describes charging correlation principles to aid with the readability of charging related procedures in
clause 5. See 3GPP TS 32.240 [16] and 3GPP TS 32.260 [17] for further information on charging.

The IM CN subsystem generates and retrieves the following charging correlation information for later use with offline
and online charging:

1. IM CN subsystem Charging Identifier (ICID);

2. Access network charging information;

3. Inter Operator Identifier (IOI);

4. Charging function addresses:

a. Charging Data Function (CDF);

b. Online Charging Function (OCF);

5. IM CN subsystem Functional Entity Identifier.

How to use and where to generate the parameters in IM CN subsystems are described further in the subclauses that
follow. The charging correlation information is encoded in the P-Charging-Vector header field as defined in
subclause 7.2A.5 and in RFC 7315 [52]. The P-Charging-Vector header field contains the following header field
parameters: "icid-value", "icid-generated-at", "related-icid", "related-icid-generated-at", "access-network-charging-
info", "orig-ioi", "term-ioi", "transit-ioi" and "fe-identifier".

The offline and online charging function addresses are encoded in the P-Charging-Function-Addresses as defined in
RFC 7315 [52]. The P-Charging-Function-Addresses header field contains the following header field parameters: "ccf"
for CDF and "ecf" for OCF.

NOTE: P-Charging-Function-Addresses parameters were defined using previous terminology.

3GPP
Release 16 83 3GPP TS 24.229 V16.8.0 (2020-12)

4.5.2 IM CN subsystem charging identifier (ICID)

The ICID is the session level data shared among the IM CN subsystem entities including ASs in both the calling and
called IM CN subsystems. The ICID is used also for session unrelated messages (e.g. SUBSCRIBE request, NOTIFY
request, MESSAGE request) for the correlation with CDRs generated among the IM CN subsystem entities.

The first IM CN subsystem entity involved in a SIP transaction will generate the ICID and include it in the "icid-value"
header field parameter of the P-Charging-Vector header field in the SIP request.

For a dialog relating to a session, the generation of the ICID will be performed only on the initial request. This ICID
will be used for the initial request and any response to the initial request, and all subsequent SIP messages ina P-
Charging-Vector header field.

For all other transactions, generation of the ICID will be performed on each SIP request. This ICID will be used for the
SIP request and any response to the SIP request in a P-Charging-Vector header field.

The "icid-value" header field parameter is inserted in the IM CN subsystem, as summarised in table 4-2A.

NOTE: This summary is also applicable for SIP messages which are not specified in clause 5, although each
procedure for the P-Charging-Vector header field in clause 5 is described only for specific SIP message(s)
(e.g. only for a 200 (OK) response).

Table 4-2A: Summary of ICID insertion in the IM CN subsystem

Inserted in For initial or standalone SIP message For subsequent SIP message
Any request The first IM CN subsystem entity receiving The first IM CN subsystem entity receiving
the request inserts the "icid-value" header the request inserts the "icid-value" header
field parameter populated as specified in field parameter set to the value populated in
3GPP TS 32.260 [17]. the initial request for the dialog.
Any response to The first IM CN subsystem entity receiving The first IM CN subsystem entity receiving
the request the response inserts the "icid-value" header the response inserts the "icid-value" header
field parameter set to the value populated in field parameter set to the value populated in
the initial request for the dialog or the the initial request for the dialog.
standalone request.

See 3GPP TS 32.260 [17] for requirements on the format of ICID. The P-CSCF will generate an ICID for UE-
originated calls. The I-CSCF will generate an ICID for UE-terminated calls if there is no ICID received in the initial
request (e.g. the calling party network does not behave as an IM CN subsystem). The AS will generate an ICID when
acting as an originating UA. The MGCF will generate an ICID for PSTN/PLMN originated calls. The MSC server will
generate an ICID for ICS and SRVCC originated calls. Each entity that processes the SIP request will extract the ICID
for possible later use in a CDR. The I-CSCF and S-CSCF are also allowed to generate a new ICID for UE-terminated
calls received from another network.

There is also an ICID generated by the P-CSCF with a REGISTER request that is passed in a unique instance of P-
Charging-Vector header field. The valid duration of the ICID is specified in 3GPP TS 32.260 [17].

The "icid-value" header field parameter is included in any request and response that includes the P-Charging-Vector
header field. However, the P-Charging-Vector (and ICID) is not passed to the UE.

The ICID is also passed from the P-CSCF to the IP-CAN via PCRF. The interface supporting this operation is outside
the scope of this document.

4.5.2A Related ICID

During the process of SRVCC access transfer the MSC server or the P-CSCF generates an ICID for the target access
leg. For the purpose of charging correlation between the source access leg and the target access leg when the user is
roaming the SCC AS and the ATCF includes the ICID used on the source access leg in the "related-icid" header field
parameter of the P-Charging-Vector header field returned in 1xx and 2xx responses to the initial INVITE request.

During the process of dual radio access transfer the MSC server or the P-CSCF generates an ICID for the target access
leg. For the purpose of charging correlation between the source access leg and the target access leg when the user is
roaming the SCC AS includes the ICID used on the source access leg in the "related-icid" header field parameter of the
P-Charging-Vector header field returned in 1xx and 2xx responses to the initial INVITE request.

3GPP
Release 16 84 3GPP TS 24.229 V16.8.0 (2020-12)

4.5.3 Access network charging information

4.5.3.1 General
The access network charging information are the media flow level data shared among the IM CN subsystem entities for
one side of the session (either the calling or called side). GPRS charging information (GGSN identifier and PDP context
information) is an example of access network charging information.

4.5.3.2 Access network charging information

The IP-CAN provides the access network charging information to the IM CN subsystem. This information is used to
correlate IP-CAN CDRs with IM CN subsystem CDRs, i.e. the access network charging information is used to correlate
the bearer level with the session level.

The access network charging information is generated at the first opportunity after the resources are allocated at the IP-
CAN. The access network charging information is passed from IP-CAN to P-CSCF via PCRF, over the Rx and Gx
interfaces. Access network charging information will be updated with new information during the session as media
flows are added or removed. The P-CSCF provides the access network charging information to the S-CSCF. The S-
CSCF may also pass the information to an AS, which may be needed for online pre-pay applications. The access
network charging information for the originating network is used only within that network, and similarly the access
network charging information for the terminating network is used only within that network. Thus the access network
charging information are not shared between the calling and called networks. The access network charging information
is not passed towards the external ASs from its own network.

The access network charging information is populated in the P-Charging-Vector header field.

The access network charging information can be included in a P-Charging-Vector header field in dialog forming
requests, mid-dialog requests, and responses. This is dependant on when updated information is avialable in the P-
CSCF.

4.5.4 Inter operator identifier (IOI)

The Inter Operator Identifier (IOI) is a globally unique identifier to share between sending and receiving networks,
service providers or content providers.

The sending network populates the "orig-ioi" header field parameter of the P-Charging-Vector header field in a request
and thereby identifies the operator network from which the request was sent. The "term-ioi" header field parameter is
left out of the P-Charging-Vector header field in this request. The sending network retrieves the "term-ioi" header field
parameter from the P-Charging-Vector header field in a response to the request, which identifies the operator network
from which the response was sent.

The receiving network retrieves the "orig-ioi" header field parameter from the P-Charging-Vector header field in the
request, which identifies the operator network from which the request was sent. The receiving network populates the
"term-ioi" header field parameter of the P-Charging-Vector header field in the response to the request, which identifies
the operator network from which the response was sent.

The "orig-ioi" and "term-ioi" header field parameters are inserted in the IM CN subsystem, as summarised in table 4-
2B.

NOTE: This summary is also applicable for SIP messages which are not specified in clause 5, although each
procedure for the P-Charging-Vector header field in clause 5 is described only for specific SIP message(s)
(e.g. only for a 200 (OK) response).

3GPP
Release 16 85 3GPP TS 24.229 V16.8.0 (2020-12)

Table 4-2B: Summary of IOI insertion in the IM CN subsystem

Inserted in For initial, standalone or subsequent SIP message

Any request The IM CN subsystem entity in the sending network:
1) removes any received "orig-ioi" header field parameter, if present;
2) inserts the "orig-ioi" header field parameter to a value that identifies the sending network of
the request; and
3) does not insert the "term-ioi" header field parameter.
Any response to The IM CN subsystem entity in the receiving network:
the request 1) removes any received "orig-ioi" and "term-ioi" header field parameters, if present;
2) inserts the "orig-ioi" header field parameter set to the previously received value of "orig-ioi"
header field parameter, if received in the request; and
3) inserts the "term-ioi" header field parameter to a value that identifies the receiving network
from which the response is sent.

There are three types of IOI:

a) Type 1 IOI, between the visited network and the home network. This includes the following cases:

- between the P-CSCF (possibly in the visited network) and the S-CSCF in the home network. This is
exchanged in REGISTER requests and responses, and in all session-related and session-unrelated requests
and responses;

- between the SCC AS in the home network and the ATCF (possible in the visited network). This is exchanged
in MESSAGE requests and responses;

NOTE: For applications where the primary relationship is home and visited network, request and responses to the
request will normally contain a type 1 IOI value.

- between the MSC server (possibly in the visited network) and the S-CSCF in the home network. This is
exchanged in REGISTER requests and responses, and in all session-related and session-unrelated requests
and responses; and

- when using Roaming Architecture for Voice over IMS with Local Breakout and loopback routeing occurs,
between the S-CSCF of the home network and the TRF of the visited network or between the BGCF of the
home network and the TRF of the visited network. This is exchanged in all session-related requests and
responses.

b) Type 2 IOI, between originating network and the terminating network. This includes the following cases:

- between the S-CSCF of the home originating network and the S-CSCF of the home terminating network or
between the S-CSCF of the home originating network and the MGCF when a call/session is terminated at the
PSTN/PLMN;

- between the MGCF and the S-CSCF of the home terminating network when a call/session is originated from
the PSTN/PLMN or with a PSI AS when accessed across I-CSCF; and

- when using Roaming Architecture for Voice over IMS with Local Breakout and loopback routeing occurs,
between the TRF of the visited network and the S-CSCF of the home terminating network.

This is exchanged in all session-related and session-unrelated requests and responses.

Additionally, for emergency transactions, a type 2 IOI is exchanged between the E-CSCF and the MGCF or
IBCF where the request is routed to a PSAP. In scenarios where the E-CSCF receives emergency requests from
an S-CSCF, a type 2 IOI is exchanged. This can also occur where the E-CSCF receives emergency requests from
an IBCF.

c) Type 3 IOI, between the S-CSCF or I-CSCF of the home operator network and any AS. Type 3 IOI are also used
between E-CSCF and LRF, between E-CSCF and EATF, and between transit function and AS. The type 3 IOI is
exchanged in all session-related and session-unrelated requests and responses.

Each entity that processes the SIP request will extract the IOI for possible later use in a CDR. The valid duration of the
IOI is specified in 3GPP TS 32.240 [16].

3GPP
Release 16 86 3GPP TS 24.229 V16.8.0 (2020-12)

4.5.4A Transit inter operator identifier (Transit IOI)

The Transit Inter Operator Identifier (Transit IOI) is a globally unique identifier to share between sending, transit and
receiving networks, service providers or content providers.

A network sending a request can retrieve the "transit-ioi" header field parameter value(s) from the P-Charging-Vector
header field in the response to the sent request, which identify the operator network(s) which the response was
transitting.

The transit network(s) populate(s) the "transit-ioi" header field parameter value(s) of the P-Charging-Vector header
field in a request and thereby identify(ies) the operator network(s) which the request was transitting. The "transit-ioi"
header field parameter is an indexed value that is incremented each time a value is added. When the index is calculated
then "void" entries are taken into account.

The transit network(s) populate(s) the "transit-ioi" header field parameter value(s) of the P-Charging-Vector header
field in the response to the request and thereby identify(ies) the operator network(s) which the response was transitting.
The "transit-ioi" header field parameter is an indexed value that is incremented each time a value is added. When the
index is calculated then "void" entries are taken into account.

A network receiving a request can retrieve the "transit-ioi" header field parameter value(s) from the P-Charging-Vector
header field in the request, which identify the operator network(s) which the request was transitting.

EXAMPLE:

Transit-IOI in a request when arriving on the terminating side:

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-ioi=home1.net; transit-

ioi="operatorA.1, void, operatorB.3"

Transit-IOI in the corresponding response when arriving on the originating side:

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-ioi=home1.net; term-

ioi=home2.net; transit-ioi="operatorB.1, void, operatorA.3"

The Transit IOI is exchanged between functional entities, as summarised in table 4-3.

Table 4-3: Summary of Transit IOI exchange in the IM CN subsystem

Item Entities adding Transt IOI Entities deleting Transit IOI

(NOTE 1) (NOTE 1)
1 additional routeing functions as defined in annex I S-CSCF of the home network;
or IBCF (NOTE 2) in the transit network located P-CSCF of the visited network; or
between the visited network and the home TRF of the visited originating network when using
network Roaming Architecture for Voice over IMS with
Local Breakout and loopback routeing occurs
2 additional routeing functions as defined in annex I S-CSCF of the home terminating network;
or IBCF (NOTE 2) in the transit network located S-CSCF of the home originating network;
between originating network and the terminating MGCF when a call/session is terminated at the
network PSTN/PLMN; or
TRF of the visited originating network when using
Roaming Architecture for Voice over IMS with
Local Breakout and loopback routeing occurs
3 additional routeing functions as defined in annex I S-CSCF of the home terminating network
colocated with MGCF when a call/session was
transitting the PSTN/PLMN
NOTE 1: Transit IOIs can also be exchanged with non 3GPP networks, e.g. IPX networks.
NOTE 2: In the transit network, the IBCF acting as an entry point adds the Transit IOI in requests and the IBCF
acting as an exit point adds the Transit IOI in responses, as described in subclause 5.10.

Each entity that processes the SIP requests and responses may extract the Transit IOI for charging purposes, as
described in 3GPP TS 32.260 [17].

3GPP
Release 16 87 3GPP TS 24.229 V16.8.0 (2020-12)

4.5.5 Charging function addresses

Charging function addresses are distributed to each of the IM CN subsystem entities in the home network for one side
of the session (either the calling or called side) and provide a common location for each entity to send charging
information. Charging Data Function (CDF) addresses are used for offline billing. Online Charging Function (OCF)
addresses are used for online billing.

There may be multiple addresses for CDF and OCF addresses populated into the P-Charging-Function-Addresses
header field of the SIP request or response. The header field parameters are "ccf" and "ecf" for CDF and OCF,
respectively. At least one instance of either "ccf" or "ecf" header field paramter is required. If "ccf" header field
parameter is included for offline charging, then a secondary "ccf" header field paramter may be included by each
network for redundancy purposes, but the first instance of "ccf" header field parameter is the primary address. If ecf
address is included for online charging, then a secondary instance may also be included for redundancy.

The CDF and/or OCF addresses are retrieved from an Home Subscriber Server (HSS) via the Cx interface and passed
by the S-CSCF to subsequent entities. The charging function addresses are passed from the S-CSCF to the IM CN
subsystem entities in its home network, but are not passed to the visited network or the UE. When the P-CSCF is
allocated in the visited network, then the charging function addresses are obtained by means outside the scope of this
document. The AS receives the charging function addresses from the S-CSCF via the ISC interface. CDF and/or OCF
addresses may be allocated as locally preconfigured addresses. The AS can also retrieve the charging function address
from the HSS via Sh interface.

4.5.6 Relayed charge parameters

Where there is a desire to pass charging information to an entity over an interface to which the charging information is
not directly related, then the Relayed-Charge header field is used. This is used only in accordance with the capabilities
specified in this document, which currently specify only the relay of a transit IOI to an associated AS.

4.5.7 Loopback-indication parameter

When there is a desire to send the information that loopback has been applied to an entity, then the loopback-indication
parameter is used. This parameter can e.g. be evaluated when processing the P-CSCF CDR and possibly the ATCF
CDR to know whether or not to attempt to locate a correlated TRF CDR even for the non-loopback scenario when no
such CDR exists. It is used only in accordance with the capabilities specified in this document.

4.5.8 IM CN subsystem Functional Entity Identifier

4.5.8.1 General
Different rules for generating and processing of charging information apply. In order to inform the billing domain
which IM CN subsystem functional entities have created charging information, the IM CN subsystem functional entities
and ASs include an "fe-identifier" header field parameter as additional information in the P-Charging-Vector header
field when generating charging information as specified in 3GPP TS 32.260 [17].

NOTE: Within the billing domain this information given within the "fe-identifier" header field in a final response
allows the billing domain to compare the generated data records for specific IM CN subsystem functional
entities with the recorded addresses/identifiers of the IM CN subsystem functionial entities themselves.
Thus information can be compared and missing information can be identified.

4.5.8.2 Tracking of IM CN subsystem functional entities generating charging

information
Each IM CN subsystem functional entity that generates charging events, includes its own address or specific IM CN
subsystem functional entity identifier within the "fe-addr" element of the "fe-identifier" header field parameter of the P-
Charging-Vector header field into the initial SIP request to be sent from own domain.

The last element of the operator domain stores the "fe-identifier" header field parameter in the P-Charging-Vector
header field and removes the "fe-identifier" header field parameter from the P-Charging-Vector header field.

3GPP
Release 16 88 3GPP TS 24.229 V16.8.0 (2020-12)

When receiving the final SIP response sent back to its own domain, the last element of the operator domain deletes, if
received, the "fe-identifier" header field parameter from the P-Charging-Vector header field, adds the stored "fe-
identifier" and adds its own "fe-addr" to the "fe-identifier".

4.5.8.3 Tracking of applications generating charging information

Each application for which the hosting AS is generating charging events, includes the address or specific identifier of
the AS within the "as-addr" element and the application identifier within the "ap-id" element of the "fe-identifier"
header field parameter of the P-Charging-Vector header field into the initial SIP request to be sent.

The final SIP response sent back by the last element of the operator domain supporting the "fe-identifier" header field
contains the list of addresses and application identifiers received within the initial SIP request.

4.6 Support of local service numbers

For the IM CN subsystem, the support of local service numbers is provided by an AS in the subscriber's home network
as described in subclause 5.7.1.7.

4.7 Emergency service

4.7.1 Introduction
The need for support of emergency calls in the IM CN subsystem is determined by national regulatory requirements.

4.7.2 Emergency calls generated by a UE

If the UE cannot detect the emergency call attempt, the UE initiates the request as per normal procedures as described in
subclause 5.1.2A. Depending on network policies, for a non-roaming UE or for a roaming UE where the P-CSCF is in
the same network where the UE is roaming an emergency call attempt can succeed even if the UE did not detect that an
emergency session is being requested, otherwise the network rejects the request indicating to the UE that the attempt
was for an emergency service.

The UE procedures for UE detectable emergency calls are defined in subclause 5.1.6.

The P-CSCF, S-CSCF, IBCF, and E-CSCF procedures for emergency service are described in subclause 5.2.10, 5.4.8,
5.10.3.2 and 5.11, respectively.

Access dependent aspects of emergency service (e.g. whether the access technology defines emergency bearers,
emergency registration support and location provision) are defined in the access technology specific annexes for each
access technology.

There are a number of variants within these procedures and which variant gets used depends on a number of issues.
These conditions are defined more specifically in 3GPP TS 23.167 [4B] and, where appropriate, in the access
technology specific annex, but are summarised as follows:

a) if the UE knows that it is in its own home network, then an existing registration is permitted to be used for
signalling the emergency call, except where item c) applies. The access technology specific annexes define the
mechanism by which home network determination is made;

b) if emergency calls are permitted without security credentials (or additionally where the authentication is not
possible or has failed), then the emergency call is made directly without use of any security association created
by a registration, and therefore without the registration; and

c) where the access technology defines emergency bearers for the support of emergency calls, a new emergency
registration is required so that these emergency bearers can be used for both signalling and media, unless an
existing emergency registration exists on those emergency bearers.

3GPP
Release 16 89 3GPP TS 24.229 V16.8.0 (2020-12)

4.7.3 Emergency calls generated by an AS

In certain circumstances an AS can identify that a request is an emergency call. This may relate to a request received
from a UE (or subscription-based business trunking), or may be a call generated by an AS on behalf of a UE as far as
the IM CN subsystem operation is concerned. These applications are outside the scope of this document to define.

Procedures in support of an AS initiating emergency calls are provided in subclause 5.7.1.14.

4.7.4 Emergency calls received from an enterprise network

An IBCF can also route emergency calls received from an enterprise network (peering-based business trunking) to an E-
CSCF.

4.7.5 Location in emergency calls

A number of mechanisms also exist for providing location in support of emergency calls, both for routeing to a PSAP,
and for use by the PSAP itself, in the IM CN subsystem:

a) by the inclusion by the UE of the Geolocation header field containing a location by reference or by value (see
RFC 6442 [89]);

b) by the inclusion by the UE of a P-Access-Network-Info header field, which contains a cell identifier or location
identitifier, which is subsequently mapped, potentially by the recipient, into a real location;

c) by the inclusion by the P-CSCF of a P-Access-Network-Info header field based on information supplied by
either the PCRF or the NASS, and which contains a cell identifier or location identitifier, which is subsequently
mapped, potentially by the recipient, into a real location;

d) by the allocation of a location reference that relates to the call by the LRF. Location is then supplied to the
recipient over the Le interface (see 3GPP TS 23.167 [4B] for a definition of the Le interface) along with other
call information. The LRF can obtain the location from entities outside the IM CN subsystem, e.g. by the e2
interface from the NASS (see ETSI TS 283 035 [98] or from the Gateway Mobile Location Centre (GMLC); and

e) by the inclusion by the S-CSCF of a P-Access-Network-Info header field based on information supplied by HSS,
and which contains a location identitifier, which is subsequently mapped, potentially by the recipient, into a real
location.

Mechanisms also exist for providing emergency-related information to a PSAP, in requests subsequent to routeing an
initial request to a PSAP, in the IM CN subsystem:

a) by the inclusion by the UE of the Geolocation header field containing a location by reference or by value (see
RFC 6442 [89]);

b) by the inclusion by the UE of a P-Access-Network-Info header field, which contains a cell identifier or location
identitifier, which is subsequently mapped, potentially by the recipient, into a real location;

c) by the inclusion by the P-CSCF of a P-Access-Network-Info header field based on information supplied by
either the PCRF or the NASS, and which contains a cell identifier or location identitifier, which is subsequently
mapped, potentially by the recipient, into a real location;

d) by the inclusion by the UE of the emergency-related information as specified in subclause 5.1.6.10;

e) by the inclusion by the S-CSCF of a P-Access-Network-Info header field based on information supplied by HSS,
and which contains a location identitifier, which is subsequently mapped, potentially by the recipient, into a real
location; and

f) by LRF requesting the location from the UE via E-CSCF as specified in subclause 5.12.3.2, subclause 5.11.4.3,
subclause 5.11.4.4, subclause 5.11.5 and subclause 5.1.6.12.

The E-CSCF routes such a subsequent request to the PSAP using normal SIP procedures.

NOTE 1: Mechanisms independent from SIP for providing the emergency related information to a PSAP after
session setup exist and are not listed. The use of such mechanisms is not precluded.

3GPP
Release 16 90 3GPP TS 24.229 V16.8.0 (2020-12)

Which means of providing location is used depends on local regulatory and operator requirements. One or more
mechanisms can be used. Location can be subject to privacy constraints.

NOTE 2: A similar variety of mechanisms also exists for normal calls, where location can be made use of by the
recipient or by an intermediate AS, again subject to privacy constraints. The LRF is not involved in a
normal call, but an AS can obtain location from the e2 interface from the NASS (see
ETSI TS 283 035 [98] or from the Gateway Mobile Location Centre (GMLC).

4.7.6 eCall type of emergency service

A PSAP supporting eCall over IMS supports:

- receipt of the minimum set of emergency related data (MSD) in an INVITE or INFO request;

- the EmergencyCallData.eCall.MSD Info-Package and the ability to request an updated MSD by including an
"application/EmergencyCallData.Control+xml" MIME body part containing a "request" element with an
"action" attribute set to "send-data" and a "datatype" attribute set to "eCall.MSD" in an INFO request as defined
in RFC 8147 [244];

- sending of an acknowledgement for an MSD received in an INVITE request by including, in the final response
to the INVITE request, an "application/EmergencyCallData.Control+xml" MIME body part with an "ack"
element containing a "received" attribute set to "true" or "false" and a "ref" attribute set to the Content-ID of the
MIME body part containing the MSD sent by the UE, as defined in RFC 8147 [244];

- receipt of the MSD using audio media stream encoded as described in 3GPP TS 26.267 [9C];

- the ability to request an updated MSD using audio media stream encoded as described in 3GPP TS 26.267 [9C];
and

- the ability to request an updated MSD using audio media stream encoded as described in 3GPP TS 26.267 [9C],
if the remote UA modifies an IMS emergency call of the eCall type of emergency service and stops supporting
the EmergencyCallData.eCall.MSD Info-Package defined in RFC 8147 [244].

NOTE: The remote UA modifies an IMS emergency call of the eCall type of emergency service and stops
supporting the EmergencyCallData.eCall.MSD Info-Package defined in RFC 8147 [244] when SRVCC
access transfer takes place.

4.8 Tracing of signalling

4.8.1 General
IM CN subsystem entities can log SIP signalling, for debugging or tracing purposes, as described in
3GPP TS 32.422 [17A]. Debugging of SIP signalling is configured using the 3GPP IMS service level tracing
management object (MO), specified in 3GPP TS 24.323 [8K]. This management object can provide configuration data
to a UE or an S-CSCF, including in a visited network. Logging always begins with the initial request that creates a
dialog and ends when a pre-configured stop trigger occurs or the dialog ends, whichever occurs first, as described in
RFC 8497 [140] and configured in the trace management object defined in 3GPP TS 24.323 [8K].

4.8.2 Trace depth

The depth parameter in trace control and configuration indicates which SIP requests and responses are logged. If the
trace depth is "maximum" then all requests and responses within a dialog or standalone transaction are logged. If the
trace depth is "minimum" then all requests and responses except for non-reliable 1xx responses (including 100 (Trying)
responses) and the ACK request are logged.

3GPP
Release 16 91 3GPP TS 24.229 V16.8.0 (2020-12)

4.9 Overlap signalling

4.9.1 General
This subclause explains the overlap signalling impacts on the core entities of the IM CN subsystem.

The support of overlap signalling, and each of the overlap signalling method, within the IM CN subsystem, are optional
and is dependent on the network policy.

Only one overlap signalling method shall be used within one IM CN subsystem.

NOTE: Interworking between the overlap signalling methods is not specified in this release.

4.9.2 Overlap signalling methods

4.9.2.1 In-dialog method

4.9.2.1.1 General
The in-dialog method uses INFO requests or INVITE requests in order to transport additional digits. Before an early
dialog has been established, upon reception of a 404 (Not Found) or 484 (Address Incomplete) response to an earlier
INVITE request, new INVITE requests will be sent to transfer additional digits (as specified in 3GPP TS 29.163 [11B]).
Once an entity establishes an early dialog, by sending a provisional response to a INVITE request, INFO requests will
be sent to carry additional digits on the early dialog.

The message body, and associated header values, which is used to carry additional digits in INFO requests is defined in
3GPP TS 29.163 [11B].

4.9.2.2 Multiple-INVITE method

4.9.2.2.1 General
The multiple-INVITE method uses INVITE requests with the same Call ID and From header in order to transport digits
(as specified in 3GPP TS 29.163 [11B]).

4.9.3 Routeing impacts

4.9.3.1 General
If overlap dialing is supported, the IM CN subsystem needs to be configured in such a manner that erroneous routeing
of INVITE requests with incomplete numbers towards others entities than the corresponding INVITE requests with full
numbers is avoided, for instance towards a default destination for unknown numbers such as a PSTN. Possibly impacted
nodes include the S-CSCF for the UE-originated case, the transit routeing function, the I-CSCF, and application servers.

A misrouteing can be avoided by configuring the entity sending overlap signalling in such a manner that it will send the
first INVITE request with a sufficient number of digits to find a suitable entry in the translation database. If ENUM is
used, the ENUM database in a typical deployment contains sufficient information about the first digits, as required to
identify the destination IP domain. Therefore, ENUM is able to handle incomplete numbers in such deployments. As
another alternative, the routeing entity can reject calls with unknown numbers with a 404 (Not Found) response, using
entries in the routeing database to identify calls towards the PSTN. The S-CSCF for the UE-originated case could also
forward calls with unknown numbers to the BGCF, if the BGCF is configured to reject calls to unknown destinations
with a 404 (Not Found) response.

4.9.3.2 Deterministic routeing

If the multiple-INVITE method is used for overlap signalling, if an entity receives a INVITE request outside an existing
dialog with the same Call ID and From header field as a previous INVITE request during a certain period of time, the
entity shall route the new INVITE request to the same next hop as the previous INVITE request.

3GPP
Release 16 92 3GPP TS 24.229 V16.8.0 (2020-12)

NOTE: INVITE requests with the same Call ID and From header fields received in sequence during a certain
period of time belong to the same call. The routeing towards the same next hop could be achieved by an
appropriately configured database or by the entity comparing the Call ID and From header fields of each
INVITE request outside an existing dialog with Call IDs and "tag" From header field parameters of
previous INVITE requests. If the entity compares the Call ID and From header field, it stores the
information about received Call ID and From header fields at least for a time in the order of call setup
times. If paths have been established at registration time, deterministic routeing will be automatic for
entities on these paths.

4.9.3.3 Digit collection

Entities performing routeing decicisions may require additional digits for a decision where to route an INVITE request.
These entities may interact with a routeing database to reach this decision.

If no suitable entry in a database is found for the digits received in a INVITE request, an entity can reject the INVITE
request with a 404 (Not Found) or 484 (Address Incomplete) response. This method of digit collection can be
performed by a SIP proxy and is suitable both for the in-dialog and multiple-INVITE overlap signalling methods.
Replying with a 404 (Not Found) response avoids the need to keep apart uncomplete and unknown numbers. The 484
(Address Incomplete) response requires the recognition of incomplete numbers.

NOTE: An HSS does not support the recognition of incomplete numbers. A routeing database being queried by
ENUM also does not support the recognition of incomplete numbers.

As an alternative for the in-dialogue method, the digit collection function described in annex N.2 may be invoked. It
shall be performed by an entity acting as a B2BUA. The digit collection function requires the ability to recognise
incomplete number.

4.10 Dialog correlation for IM CN subsystems

4.10.1 General
The Call-ID header field in combination with the tags in the From header field and in the To header field is the standard
mechanism to identify SIP messages which belong to the same dialog. However the Call-ID header field is often
changed by B2BUAs and other SIP intermediaries in the end-to-end message path.

To solve this problem, a Session-ID header field containing a globally unique session identifier, as defined in
RFC 7989 [162], can be used to correlate SIP messages belonging to the same session. In the case of a concatenation of
dialogs, the dialog correlation mechanism indicates that these dialogs belong to the same session.

The usage of the Session-ID header field is specified in annex A.

4.10.2 CONF usage

In case of the activation of a 3PTY conference, in the INVITE request to the CONF AS the Session-ID header field is
added to the URIs in the URI list, in order to indicate the dialogs which are to be included to the 3PTY conference at the
CONF AS, as described in 3GPP TS 24.147 [8B].

4.11 Priority mechanisms

In support of priority, the IM CN subsystem uses the mechanisms of RFC 4412 [116]. The request for prioritisation of a
transaction / dialog may, for some deployments, be marked with the Resource-Priority header field by the UE. For other
deployments, the request is not marked for priority by the UE, but the request is instead identified as a priority request
and marked for priority (via a Resource-Priority header field) by a functional entity (e.g., P-CSCF) within the network.
Subsequent to successful authorisation at an authorisation point (e.g. AS), request is considered to be authorised.

The characteristics of any priority scheme is defined by the namespace that is used. This determines how priority is
applied to the SIP signalling, to the bearer carrying the SIP signalling, and to the bearers carrying any media. Different
priority levels exist within each namespace. Priority levels in one namespace have no relationship to the priority levels

3GPP
Release 16 93 3GPP TS 24.229 V16.8.0 (2020-12)

in any other namespace, i.e. priority level "1" in namespace "A" may have an entirely different level and characteristic
of priority treatment to an identically labelled priority level "1" in namespace "B".

A network can support multiple namespaces. It is up to the network operator (potentially based on regulatory or
contractural obligations) to define the relationship between the priority mechanisms for each namespace, and indeed
with calls that are not given any priority. It is normal that prioritised calls do not have access to 100% of any available
resource and indeed are limited to a much lower figure. Priority is optional, and this document places no requirement on
a conformant IM CN subsystem implementation to support priority, or indeed any namespace in a priority scheme.
Regulators can however place their own requirements on an operator. Emergency transactions or dialogs (see
subclause 4.7) can also have their own priority scheme.

RFC 4412 [116] specifies several resource priority namespaces. For example, certain national MPS implementations
use resource priority namespaces of ETS (Emergency Telecommunications Service) and WPS (Wireless Priority
Service).

Several ways of using priority exist, depending on the authorisation mechanism adopted. These are identified as
follows. In each of these authorisation means authorisation to use the service, the namespace, and the priority level
within that namespace:

1) Authorisation based on subscription in the IM CN subsystem only, priority requested by the UE using the
Resource Priority header field. Whether the user is allowed to use priority or not, and the appropriate namespace
and priority levels, is stored as part of the user profile in the HSS. As part of the reg event package subscription,
this information is given to the P-CSCF when the contact information for any public user identity changes, and
based on this information, the P-CSCF acts as the authorisation point for priority on individual requests. At the
P-CSCF, when a Resource-Priority header field is received from the UE, if the requested priority equates to a
value (namespace and priority level) that the P-CSCF knows is allowed for that public user identity, the priority
is authorised.

2) Authorisation based on a database deployed by an AS; priority requested by the UE using a special dialstring. In
this case the user requires no priority subscription information in the HSS. Specific dialstrings are configured in
the P-CSCF. When a request is received from the UE by the P-CSCF, if the request contains a specific dialstring
that is recognised by the P-CSCF as being eligible for priority treatment, the request is marked for temporary
priority, subject to subsequent authorisation by an authorisation point (i.e., AS). And all such requests are routed
to an AS. Final authorisation is granted by the AS, based on a PIN or password exchange with the UE.
Subsequent requests or responses after authorisation are only given priority by the P-CSCF and S-CSCF if some
backwards indication is received for that specific dialog. The definition of this backwards indication is outside
the scope of this document (because non-standardised mechanisms have already been implemented in
association with this approach).

3) Authorisation based on subscription in the IM CN subsystem and on a database deployed by an AS; priority
requested by the UE using a special dialstring. Specific dialstrings are configured in the P-CSCF. When a request
is received from the UE by the P-CSCF, if the request contains a specific dialstring that is recognised by the P-
CSCF as being eligible for priority treatment, the request is marked for temporary priority, subject to subsequent
authorisation by an authorisation point (i.e., AS). Based on iFC functionality that exists at the S-CSCF (from the
users subscription in the HSS), such requests are routed to an AS. Final authorisation is granted by the AS, based
on a PIN or password exchange with the UE or based on user profile. Subsequent requests or responses after
authorisation are only given priority by the P-CSCF and S-CSCF if some backwards indication is received for
that specific dialog. The definition of this backwards indication is outside the scope of this document (because
non-standardised mechanisms have already been implemented in association with this approach).

Some administrations can require the use of multiple approaches in the same network.

For the cases of interworking with other networks, where the P-CSCF of the other network does not support priority,
but it is intended or required to give users of that P-CSCF priority in the home network, provision is made for
recognition of dialstrings by the IBCF and the S-CSCF. In such scenarios, when the IBCF or S-CSCF recognize that a
request contains a dialstring as being eligible for priority treatment, the request is marked by the IBCF or S-CSCF for
temporary priority, subject to subsequent authorisation by an authorisation point (i.e. AS). This mechanism does not
have an impact on the network where the P-CSCF resides.

Where the network has a requirement to prioritise emergency calls, it can either perform this function by the use of the
"esnet" namespace in the Resource-Priority header field (as defined in RFC 7135 [197]), or by recognition of the
presence of the service URN relating to an emergency. Where the Resource-Priority header field is used for this
purpose, it is inserted by the entity identifying the emergency call, i.e. the P-CSCF or the IBCF. There is no usage of

3GPP
Release 16 94 3GPP TS 24.229 V16.8.0 (2020-12)

this namespace from the UE, and when this namespace is used, the trust domain implementation is set to remove it if it
occurs from the UE.

4.12 Overload control

Usage of overload control is independent of the nature of any SIP using entity, i.e. there are no specific requirements for
any particular IMS functional entity implementing SIP. The capability however is not extended to the UE except when
performing the function of an externally attached network.

Two mechanisms are defined as follows:

- a feedback based mechanism defined in RFC 7339 [199], where the feedback is given in the Via header field of
signalling messages supporting the traffic. RFC 7339 [199] also defines the default algorithm for usage of the
feedback based mechanism in the IM CN subsystem (i.e. loss-based algorithm). Additional algorithms are either
already defined, e.g. the rate-based scheme defined in RFC 7415 [200] or can also be defined in the future. As it
is carried in the Via header fields the nature of the mechanism is hop by hop.

- an event package for distributing load filters defined in RFC 7200 [201], which can be either used in a hop-by-
hop manner between adjacent entities in a similar manner to the feedback based mechanism, or can be used on a
wider basis across the network, subject to the restrictions given in annex A. In this manner it can be used to
address expected overload situations, e.g. for voting calls initiated by a specific television programme.

When the load filters based mechanism is used in the IMS, the default algorithm is loss-based (i.e. the filter specifies the
relative percentage of incoming requests that can be accepted).

The S-CSCF, application servers and entities that implement the additional routeing capability can use both
mechanisms in parallel on the same interfaces.

There are no specific reasons why one protocol mechanism should be specified over another, although some discussion
is given in the documents specifying the mechanisms themselves. It is regarded as a deployment issue as to which
mechanisms are supported, and which algorithms are supported within those mechanisms, beyond those that the
mechanisms themselves identify as mandatory. An operator will need to take a network wide view to planning their
overload control strategy, it cannot be performed on ad-hoc basis as nodes are deployed.

For the distribution of load filters mechanism, typical deployments might include an S-CSCF subscribing to the load
control event package at an AS, an AS subscribing to the load control event package at an AS, and an entity hosting
additional routeing capabilities as specified in subclause I.3 subscribing to the load-control event package at the AS.

Based on regional/national requirements and network operator policy, priority calls (e.g., multimedia priority service)
are exempted from SIP overload controls up to the point where further exemption would cause network instability.
Therefore, SIP messages related to priority calls have the highest priority, and are last to be dropped or rejected, when
an IM CN subsystem functional entity decides it is necessary to apply traffic reduction. The interaction between SIP
overload control and priority services is covered in RFC 7339 [199] and RFC 7200 [201].

Based on regional/national requirements and network operator policy, emergency calls are exempted from SIP overload
controls up to a configured threshold. Therefore, when an IM CN subsystem functional entity decides it is necessary to
apply traffic reduction due to overload control, SIP messages related to emergency calls are not dropped while the
configured threshold regarding the amount of the ongoing emergency calls is not reached.

Mid-dialog SIP messages have higher priority with regard to initial SIP requests, and therefore are last to be dropped or
rejected, when an IM CN subsystem functional entity decides it is necessary to apply traffic reduction due to overload
control.

Operation between two network operators is supported. If two network operators wish to implement overload control, it
is a matter for bilateral agreement as to what is supported.

Operation with enterprise networks is supported. The network operator and the enterprise operator will need to agree on
the overload control options to be supported.

3GPP
Release 16 95 3GPP TS 24.229 V16.8.0 (2020-12)

4.13 II-NNI traversal scenario

4.13.1 General
Within the IM CN subsystem, the signalling path between a calling user and a called user can be divided into one or
more traffic legs, referred to as II-NNI traversal scenarios. Each II-NNI traversal scenario can span networks belonging
to different operators and will have its own characteristics that can be different from other II-NNI traversal scenarios in
the same call.

Dialog creating SIP requests and standalone requests can contain an "iotl" SIP URI parameter as specified in
RFC 7549 [225] in a Request-URI or in one or more Route header fields. The "iotl" SIP URI parameter is appended to
the URI representing the end of the II-NNI traversal scenario. The value of "iotl" SIP URI parameter can be used to
identify the II-NNI traversal scenario.

If the "iotl" SIP URI parameter is not included in a dialog creating SIP requests or a standalone request, the II-NNI
traversal scenario type can be determined by analysing the content of the SIP request or using a default II-NNI traversal
scenario type.

NOTE: How the content of the SIP request can be used to determine the II-NNI traversal scenario is
implementation dependent and outside the scope of this specification.

The "iotl" SIP URI parameter is included by the start of the II-NNI traversal scenario (e.g. P-CSCF, S-CSCF, BGCF or
SCC AS) and removed by the end of the II-NNI traversal scenario (e.g. S-CSCF, TRF or P-CSCF).

4.13.2 Identifying the II-NNI traversal scenario

The "iotl" SIP URI parameter specified in RFC 7549 [225] containing traffic leg information can be used to identify the
II-NNI traversal scenario type. The II-NNI traversal scenario type can be used by intermediary entities (e.g. IBCF and
transit networks) to make policy decisions related to e.g. media anchoring, screening of SIP signalling, insertion of
media functions (e.g. transcoder) and charging.

One example on how the "iotl" SIP URI parameter is included in the Route header field by the P-CSCF in a visited
network when sending a request towards the home network is shown below.

EXAMPLE: Route: <sip:ibcf-vA1.visited-A.net;lr>,<sip:[email protected];lr:iotl=visitedA-

homeA>

If neither the Request-URI nor any of the Route header fields included in the SIP request contains the "iotl" SIP URI
parameter, the II-NNI traversal scenario type can be determined by analysing the content of the SIP request or using a
default II-NNI traversal scenario type. The recommended II-NNI traversal scenario type default value is "homeA-
homeB".

NOTE: How the content of the SIP request can be used to determine the II-NNI traversal scenario is
implementation dependent and outside the scope of this specification.

4.13.3 Security aspects

When receiving a dialog creating SIP request or a standalone SIP request from outside the trust domain the IBCF acting
as an entry point removes any "iotl" SIP URI parameter according to subclause 4.4.15 and assume the default II-NNI
traversal scenario type or can use trusted elements of the SIP request to determine the II-NNI traversal scenario type.

NOTE: Examples of trusted elements are protocol elements within the trust domain and protocol elements
manipulated, checked or added by a previous hop secured by network domain security.

4.14 Restoration procedures

4.14.1 General
The present document includes optional restoration procedures for failure of P-CSCF and S-CSCF. The general
mechanism is to inform the UE that one of the entities along its registration path is not working, and hence the UE

3GPP
Release 16 96 3GPP TS 24.229 V16.8.0 (2020-12)

needs to perform an initial registration. For systems providing access to IM CN subsystem using a GPRS IP-CAN, EPS
IP-CAN or a 5GS IP-CAN, the mechanism to trigger the UE can be to use the Protocol Configuration Options IE or
extended Protocol Configuration Options IE specified in 3GPP TS 24.008 [8], include an 3GPP IM CN subsystem
XML body in a 504 (Server Time-out) response, or disconnect the PDN connection.

4.14.2 P-CSCF restoration procedures

P-CSCF restoration procedures are implemented in the S-CSCF, the IBCF and the UE.

When the UE originates a session it can detect that a P-CSCF is not reachable based on no response from the P-CSCF in
which case the UE selects another P-CSCF if possible and performs a new initial registration.

UDM/HSS or HSS based P-CSCF restoration applies to UE terminating requests where the SIP entity neighbouring the
P-CSCF (S-CSCF, IBCF) can detect that a P-CSCF is not reachable. When the neighbouring entity is the S-CSCF, the
S-CSCF can in this case initiate the P-CSCF restoration. The S-CSCF sends an indication to the HSS to initiate the
restoration. If the terminating user is roaming, the neighbouring entity is an entry IBCF which uses the Restoration-Info
header field to inform the S-CSCF about the failure in a 408 (Request Timeout) response for INVITE requests or a 504
(Server Time-out) response for non-INVITE requests and the S-CSCF can send an indication to the HSS to initiate the
restoration.

PCF or PCRF based P-CSCF restoration applies to UE terminating INVITE requests. For PCF or PCRF based P-CSCF
restoration the S-CSCF uses the Restoration-Info header field to send the IMSI in initial INVITE requests to an
alternative P-CSCF. When the user is roaming, the IBCF selects an alternative P-CSCF and forwards the IMSI of the
terminating user in a Restoration-Info header field.

Restoration can also be initiated when the P-CSCF has restarted, and lost all bindings for a particular user. In this case
the P-CSCF rejects the incoming request with a 404 (Not Found) response. If the home network applies UDM/HSS or
HSS based P-CSCF restoration the S-CSCF initiates the restoration procedure by sending an indication to the HSS. If
PCF or PCRF based restoration is used, the S-CSCF initiate the PCF or PCRF based P-CSCF restoration procedure for
the served user by including the IMSI in a Restoration-Header field included in an initial INVITE request.

NOTE: In the rest of the present document where the "PCRF based P-CSCF restoration" procedure is mentioned
the "PCF based P-CSCF restoration" procedure also applies, and where the "HSS based P-CSCF
restoration" procedure is mentioned the "UDM/HSS based P-CSCF restoration" procedure also applies.

4.14.3 S-CSCF restoration procedures

The P-CSCF can inform the UE about S-CSCF failures in a 504 (Server Time-out) response using the 3GPP IM CN
subsystem XML body defined in subclause 7.6, in accordance with subclause 5.2.6.3.2A, when the P-CSCF is unable to
forward a request to an S-CSCF.

When the S-CSCF receives a request initiated by the served user for which the S-CSCF does not have the user profile or
does not trust the data that it has (e.g. due to restart) the S-CSCF can if it fails to retrieve the data from the HSS trigger a
registration by sending a 504 (Server Time-out) response using the 3GPP IM CN subsystem XML body defined in
subclause 7.6 to the UE, in accordance with subclause 5.4.3.2.

An I-CSCF can reselect S-CSCF if the previously selected S-CSCF is not available.

If an IBCF acting as an entry point in the originating home network cannot forward the request the IBCF can trigger the
UE to perform initial registration by including the 3GPP IM CN subsystem XML body in a 504 (Server Time-out)
response, in accordance with subclause 5.10.3.5.

4.15 Resource sharing

Resource sharing allows two or more sessions to use the same resources for one or more media streams in uplink,
downlink or both uplink and downlink direction.

A P-CSCF that supports resource sharing can determine that there is a potential for resource sharing based on local
configuration or defer the determination of potential resource sharing to an AS in the home network.

If the determination of potential resource sharing is deferred to an AS in the home network:

3GPP
Release 16 97 3GPP TS 24.229 V16.8.0 (2020-12)

- the P-CSCF on the originating side indicates that resource sharing is supported in the initial REGISTER request
in the Resource-Share header field defined in subclause 7.2.13. The Resource-Share header field is included in
the third-party REGISTER request towards the AS; and

- if the "message/sip" MIME body in the third-party REGISTER request included the Resource-Share header field
with the value "supported", the AS in the home network includes the Resource-Share header field containing the
rules for resource sharing in responses and requests towards the P-CSCF.

If the rules for resource sharing are updated, the updated rule will be sent to P-CSCF in one of the sessions that share
resources. The updated resource sharing rules will then be applied for all sessions that are sharing resources.

NOTE: In this release of the technical specification the UE cannot indicate support of resource sharing. However,
the Resource-Share header field is not removed from requests and responses towards the UE and the UE
can use the information in the header field to adapt its behaviour according to the information.

4.16 Priority sharing

Priority sharing allows two or more sessions with different priority to share the same bearer.

The determination of the use of priority sharing is deferred to an AS in the home network:

1) if P-CSCF supports priority sharing and if according to local policy, the P-CSCF indicate that priority sharing is
supported by including the g.3gpp.priority-share feature-capability indicator defined in subclause 7.9A.10 in a
Feature-Caps header field in the REGISTER request;

NOTE: The Feature-Caps header field with the g.3gpp.priority-share feature-capability indicator is included in
the "message/sip" MIME body in the third-party REGISTER request sent over the ISC interface.

2) if the "message/sip" MIME body in the third-party REGISTER request included the g.3gpp.priority-share
feature-capability indicator and:

a) if the AS determined to enable priority sharing, the AS includes the Priority-Share header field with a value
"allowed" in a request or response sent towards the P-CSCF; or

b) if the AS determined to disable priority sharing, the AS includes the Priority-Share header field with a value
"not-allowed" in a request or response sent towards the P-CSCF.

4.17 3GPP PS data off

The UE and the network can support the 3GPP PS data off.

When 3GPP PS data off is supported and active, IP packets that are associated with services that are not a 3GPP PS data
off exempt service are prevented from transport over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN as specified in
3GPP TS 23.228 [7]. The UE may be configured by the HPLMN or the EHPLMN with up to two indications whether a
3GPP IMS service is a 3GPP PS Data Off exempt service, one indication is valid for the UE is in the HPLMN or the
EHPLMN and the other indication is valid for the UE is in the VPLMN. When the UE is only configured with the
indication valid for the UE camping in the HPLMN or the EHPLMN, the UE shall use this indication also when the UE
is in the VPLMN.

When 3GPP PS data off is supported and active and the UE is configured, either as specified in 3GPP TS 24.167 [8G]
or in 3GPP TS 31.102 [15C], with services that are 3GPP PS data off exempt, then the UE will not send uplink IP
packets related to any services that are not 3GPP PS data off exempt over EPS IP-CAN, GPRS IP-CAN and 5GS IP-
CAN. The UE informs the network about its 3GPP PS data off status by including a g.3gpp.ps-data-off media feature
tag specified in subclauce 7.9.8 in all REGISTER requests sent over GPRS IP-CAN, EPS IP-CAN or 5GS IP-CAN. The
UE reregisters over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN every time the 3GPP PS data off status is changed
or the UE is provided by the network with a new list of 3GPP PS data off exempt services while the 3GPP PS data off
status is "active".

An AS handling a service is configured with information whether the service is a 3GPP PS data off exempt service. If
the 3GPP PS data off status is active and the service is not a 3GPP PS data off exempt service, the AS prevents
downlink IP packets of the service from reaching the UE over EPS IP-CAN, GPRS IP-CAN and 5GS IP-CAN. The AS
shall be configured with up to two indications whether a 3GPP IMS service is a 3GPP PS Data Off exempt service, one

3GPP
Release 16 98 3GPP TS 24.229 V16.8.0 (2020-12)

indication is valid for non-roaming users, and the other indication is valid for users roaming in the various VPLMNs
with whom roaming agreements exist. When the AS is only configured with the indication valid for the UE camping in
the HPLMN or the EHPLMN, the AS shall use this indication also when the UE is in the VPLMN.

4.18 Dynamic Service Interaction

Dynamic Service Interaction allows that different ASs involved in the same IMS session (within an operator network or
across networks) exchange information about executed services to avoid conflicting interactions between these services.
Dynamic Service Interaction information is included in a SIP header field Service-Interact-Info defined in
subclause 7.2.14.

If an AS which supports dynamic service interaction:

- provides one or more services:

a) the AS inserts in a SIP message the Service-Interact-Info header field with the identities of the services which
have been performed; and

b) if the AS identified services which should be further avoided the AS adds the identities of those services in
the Service-Interact-Info header field; and

- receives a SIP message containing the Service-Interact-Info header field, the AS takes the received Service-
Interact-Info header field information into account as described in subclause 7.2.14.3.

4.19 Restricted Local Operator Services

The UE and the network can support Restricted Local Operator Services (RLOS).

RLOS services are operator defined services that are offered to UEs when using an EPS IP-CAN as specified in
annex L in the following scenarios:

- UE is successfully registered using IMS AKA or GPRS-IMS bundled authentication; or

- UE has attempted to register and the registration is rejected from the network with a 403 (Forbidden) response.

RLOS services are offered only for the UE-originating case.

RLOS services can be offered to an operator's own subscribers and roaming subscribers.

5 Application usage of SIP

5.1 Procedures at the UE

5.1.0 General
The UE procedures for UE detectable emergency calls are defined in subclause 5.1.6. Exceptions to UE procedures for
SIP that do not relate to emergency, are documented in subclause 5.1.6 and shall apply. These exceptions include
handling of a response to a request not detected by the UE as relating to an emergency.

When sending a failure response to any received request, depending on operator policy, the UE may insert a Response-
Source header field with an "fe" header field parameter constructed with the URN namespace "urn:3gpp:fe", the fe-id
part of the URN set to "ue" and optionally an appropriate fe-param part of the URN set in accordance with
subclause 7.2.17. A UE when sending a failure response will add in the URN the "side" header field parameter set to:

- "orig" for a UE-originating case; and

- "term" for a UE-terminating case.

3GPP
Release 16 99 3GPP TS 24.229 V16.8.0 (2020-12)

5.1.1 Registration and authentication

5.1.1.1 General
The UE shall register public user identities (see table A.4/1 and dependencies on that major capability).

NOTE 1: The UE can use multiple Contact header field values simultaneously containing the same IP address and
port number in the contact address.

In case a UE registers several public user identities at different points in time, the procedures to re-register, deregister
and subscribe to the registration-state event package for these public user identities can remain uncoordinated in time.

The UE can register any one of its public user identities with any IP address acquired by the UE. The same public user
identity can be bound to more than one IP address of the UE. While having valid registrations of previously registered
public user identities, the UE can register any additional public user identity with any of its IP addresses. When binding
any one of its public user identities to an additional contact address, the UE shall follow the procedures described in
RFC 5626 [92].

If SIP digest without TLS is used, the UE shall not include signalling plane security mechanisms in the header fields
defined in RFC 3329 [48] in any SIP messages.

NOTE 2: The UE determines if SIP digest is used with or without TLS based on device configuration. If SIP digest
with TLS is used, then the UE includes the TLS signalling plane security mechanism in the header fields
defined in RFC 3329 [48] as described in subclause 5.1.1.2.4.

SIP requests that indicate security mechanisms for both the signalling plane and the media plane can contain multiple
instances or a single instance of the Security-Client, Security-Verify, or Security-Server header fields defined in
RFC 3329 [48].

In case a device performing address and/or port number conversions is provided by a NA(P)T or NA(P)T-PT, the UE
may need to modify the SIP contents according to the procedures described in either annex F or annex K.

NOTE 3: If UE populates the display-name of the Contact header field included in the REGISTER request with UE
name, other UEs of the user can discover the UE name of the UE in the reg event package notification.
The UE name is a text string chosen by the user allowing the user to distinguish individual UEs of the
same user.

5.1.1.1A Parameters contained in the ISIM

This subclause applies when a UE contains either an ISIM or a USIM.

The ISIM shall always be used for authentication to the IM CN subsystem, if it is present, as described in
3GPP TS 33.203 [19].

The ISIM is preconfigured with all the necessary parameters to initiate the registration to the IM CN subsystem. These
parameters include:

- the private user identity;

- one or more public user identities; and

- the home network domain name used to address the SIP REGISTER request

The first public user identity in the list stored in the ISIM is used in emergency registration requests.

In case the UE does not contain an ISIM, the UE shall:

- generate a private user identity;

- generate a temporary public user identity; and

- generate a home network domain name to address the SIP REGISTER request to;

in accordance with the procedures in clause C.2.

3GPP
Release 16 100 3GPP TS 24.229 V16.8.0 (2020-12)

The temporary public user identity is only used in REGISTER requests, i.e. initial registration, re-registration, UE-
initiated deregistration.

The UE shall not reveal to the user the temporary public user identity if the temporary public user identity is barred. The
temporary public user identity is not barred if received by the UE in the P-Associated-URI header field.

If the UE is unable to derive the parameters in this subclause for any reason, then the UE shall not proceed with the
request associated with the use of these parameters and will not be able to register to the IM CN subsystem.

5.1.1.1B Parameters provisioned to a UE without ISIM or USIM

5.1.1.1B.1 Parameters provisioned in the IMC

In case the UE contains neither an ISIM nor a USIM, but IMC is present the UE shall use preconfigured parameters in
the IMC to initiate the registration to the IM CN subsystem and for authentication.

The following IMS parameters are assumed to be available to the UE:

- a private user identity;

- a public user identity; and

- a home network domain name to address the SIP REGISTER request to.

These parameters may not necessarily reside in a UICC.

The first public user identity in the list stored in the IMC is used in emergency registration requests.

5.1.1.1B.2 Parameters when UE does not contain ISIM, USIM or IMC

If the UE contains neither ISIM, nor USIM nor IMC, the UE shall generate a temporary public user identity, a private
user identity and a home network domain name to address the SIP REGISTER request to, according
3GPP TS 23.003 [3].

5.1.1.2 Initial registration

5.1.1.2.1 General
The initial registration procedure consists of the UE sending an unprotected REGISTER request and, if challenged
depending on the security mechanism supported for this UE, sending the integrity-protected REGISTER request or
other appropriate response to the challenge. The UE can register a public user identity with any of its contact addresses
at any time after it has acquired an IP address, discovered a P-CSCF, and established an IP-CAN bearer that can be used
for SIP signalling. However, the UE shall only initiate a new registration procedure when it has received a final
response from the registrar for the ongoing registration, or the previous REGISTER request has timed out.

When registering any public user identity belonging to the UE, the UE shall either use an already active pair of security
associations or a TLS session to protect the REGISTER requests, or register the public user identity via a new initial
registration procedure.

When binding any one of its public user identities to an additional contact address via a new initial registration
procedure, the UE shall follow the procedures described in RFC 5626 [92]. The set of security associations or a TLS
session resulting from this initial registration procedure will have no impact on the existing set of security associations
or TLS sessions that have been established as a result of previous initial registration procedures. However, if the UE
registers any one of its public user identities with a new contact address via a new initial registration procedure and does
not employ the procedures described in RFC 5626 [92], then the new set of security associations or TLS session shall
replace any existing set of security association or TLS session.

If the UE detects that the existing security associations or TLS sessions associated with a given contact address are no
longer active (e.g., after receiving no response to several protected messages), the UE shall:

- consider all previously registered public user identities bound to this security associations or TLS session that are
only associated with this contact address as deregistered; and

3GPP
Release 16 101 3GPP TS 24.229 V16.8.0 (2020-12)

- stop processing all associated ongoing dialogs and transactions that were using the security associations or TLS
session associated with this contact address, if any (i.e. no further SIP signalling will be sent by the UE on behalf
of these transactions or dialogs).

The UE shall send the unprotected REGISTER requests to the port advertised to the UE during the P-CSCF discovery
procedure. If the UE does not receive any specific port information during the P-CSCF discovery procedure, or if the
UE was pre-configured with the P-CSCF's IP address or domain name and was unable to obtain specific port
information, the UE shall send the unprotected REGISTER request to the SIP default port values as specified in
RFC 3261 [26].

NOTE 1: The UE will only send further registration and subsequent SIP messages towards the same port of the P-
CSCF for security mechanisms that do not require to use negotiated ports for exchanging protected
messages.

The UE shall extract or derive a public user identity, the private user identity, and the domain name to be used in the
Request-URI in the registration, according to the procedures described in subclause 5.1.1.1A or subclause 5.1.1.1B. A
public user identity may be input by the end user.

On sending an unprotected REGISTER request, the UE shall populate the header fields as follows:

a) a From header field set to the SIP URI that contains:

1) if the UE supports RFC 6140 [191] and performs the functions of an external attached network, the main URI
of the UE; else

2) the public user identity to be registered;

b) a To header field set to the SIP URI that contains:

1) if the UE supports RFC 6140 [191] and performs the functions of an external attached network, the main URI
of the UE; else

2) the public user identity to be registered;

c) a Contact header field set to include SIP URI(s) containing the IP address or FQDN of the UE in the hostport
parameter. If the UE:

1) supports GRUU (see table A.4, item A.4/53);

2) supports multiple registrations;

3) has an IMEI available; or

4) has an MEID available;

the UE shall include a "+sip.instance" header field parameter containing the instance ID. Only the IMEI shall be
used for generating an instance