Tech-invite 3GPP-Specs Features Entities Interfaces SBIs Identifiers T_i+

full Table of Contents for TS 24.229 Word version: 16.3.0

1… 4.5… 5… 5.1.2… 5.2… 5.2.7… 5.4… 5.5… 5.7… 5.8… 5.11… 6… 7… 7.2A… 7.3… 7.9A… 8… A… B… C… E… F… H… I… K… L… M… N… O… Q… R… S… T… U… V… W…

U.1 Scope U.2 IP-CAN aspects when connected to the IM CN subsystem U.2A Usage of SDP U.3 Application usage of SIP U.4 3GPP specific encoding for SIP header field extensions U.5 Use of circuit-switched domain
...

U (Normative) IP-Connectivity Access Network specific concepts when using 5GS to access IM CN subsystem [R15] Word-p. 933

U.2 IP-CAN aspects when connected to the IM CN subsystem

U.2.1 Introduction

U.2.2 Procedures at the UE

U.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery

U.2.2.1A Modification of the PDU session of the 5GS QoS flow used for SIP signalling Word-p. 935

U.2.2.1B Re-establishment of the PDU session with the 5GS QoS flow used for SIP signalling

U.2.2.1C P-CSCF restoration procedure Word-p. 936

U.2.2.2 Session management procedures Word-p. 937

U.2.2.3 Mobility management procedures

U.2.2.4 Cell selection and lack of coverage

U.2.2.5 5GS QoS flow for media

U.2.2.5.1 General requirements

U.2.2.5.1A Activation or modification of QoS flows for media by the UE

U.2.2.5.1B Activation or modification of QoS flows for media by the network

U.2.2.5.1C Deactivation of a QoS flow for media

U.2.2.5.1D Default QoS flow usage restriction policy Word-p. 938

U.2.2.5.2 Special requirements applying to forked responses

U.2.2.5.3 Unsuccessful situations Word-p. 939

U.2.2.6 Emergency service

U.2.2.6.1 General

U.2.2.6.1A Type of emergency service derived from emergency service category value Word-p. 941

U.2.2.6.1B Type of emergency service derived from extended local emergency number list Word-p. 942

U.2.2.6.2 eCall type of emergency service

U.2.2.6.3 Current location discovery during an emergency call Word-p. 943

U.2.2.6.4 Emergency services in single-registration mode

U.2.2.6.5 Emergency services in dual registration mode Word-p. 946

U.2A Usage of SDP Word-p. 948

U.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network

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 Word-p. 949

U.2A.3 Emergency service

U.3 Application usage of SIP

U.3.1 Procedures at the UE

U.3.1.0 Registration and authentication

U.3.1.1 P-Access-Network-Info header field Word-p. 950

U.3.1.1A Cellular-Network-Info header field

U.3.1.2 Availability for calls

U.3.1.2A Availability for SMS Word-p. 952

U.3.1.3 Authorization header field Word-p. 953

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

U.3.1.5 3GPP PS data off

U.3.1.6 RLOS [R16] Word-p. 955

U.3.1.7 SIP handling at the originating UE when redirecting the UE from NG-RAN to E-UTRAN fails [R16]

U.3.2 Procedures at the P-CSCF

U.3.2.0 Registration and authentication

U.3.2.1 Determining network to which the originating user is attached

U.3.2.2 Location information handling

U.3.2.3 Prohibited usage of PDU session for emergency services

U.3.2.4 Support for paging policy differentiation

U.3.2.6 Resource sharing Word-p. 956

U.3.2.7 Priority sharing

U.3.2.8 RLOS [R16]

U.3.2.9 Support of ANBR and RAN-assisted codec adaptation [R16]

U.3.3 Procedures at the S-CSCF

U.3.3.1 Notification of AS about registration status

U.3.3.2 RLOS [R16]

U.4 3GPP specific encoding for SIP header field extensions Word-p. 957

U.5 Use of circuit-switched domain