Tech-invite  3GPP-Specs  Features  Entities  Interfaces  SBIs  Identifiers  Ti+  Search in Tech-invite

full Table of Contents for  TS 24.229  Word version:   16.4.0

Top   Up   Prev   Next
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… 
L [N] IP-Connectivity Access Network specific concepts when using EPS to access IM CN subsystem  L.1 Scope  L.2 EPS aspects when connected to the IM CN subsystem via E-UTRAN  L.2A Usage of SDP  L.3 Application usage of SIP  L.3.1 Procedures at the UE  L.3.2 Procedures at the P-CSCF  L.3.3 Procedures at the S-CSCF  L.4 3GPP specific encoding for SIP header field extensions  L.5 Use of circuit-switched domain 
...

 

L (Normative)  IP-Connectivity Access Network specific concepts when using EPS to access IM CN subsystem [R8]  Word-p. 858
L.1  Scope
L.2  EPS aspects when connected to the IM CN subsystem via E-UTRAN
L.2.1  Introduction
L.2.2  Procedures at the UE  Up
L.2.2.1  EPS bearer context activation and P-CSCF discovery
L.2.2.1A  Modification of a EPS bearer context used for SIP signalling  Word-p. 861
L.2.2.1B  Re-establishment of the EPS bearer context for SIP signalling  Word-p. 862
L.2.2.1C  P-CSCF restoration procedure [R9]
L.2.2.2  Session management procedures  Word-p. 863
L.2.2.3  Mobility management procedures
L.2.2.4  Cell selection and lack of coverage
L.2.2.5  EPS bearer contexts for media
L.2.2.5.1  General requirements
L.2.2.5.1A  Activation or modification of EPS bearer contexts for media by the UE  Word-p. 864
L.2.2.5.1B  Activation or modification of EPS bearer contexts for media by the network
L.2.2.5.1C  Deactivation of EPS bearer context for media [R11]
L.2.2.5.1D  Default EPS bearer context usage restriction policy [R14]
L.2.2.5.2  Special requirements applying to forked responses  Word-p. 865
L.2.2.5.3  Unsuccessful situations
L.2.2.6  Emergency service
L.2.2.6.1  General [R14]
L.2.2.6.1A  Type of emergency service derived from emergency service category value [R15]  Word-p. 867
L.2.2.6.1B  Type of emergency service derived from extended local emergency number list [R15]  Word-p. 868
L.2.2.6.2  eCall type of emergency service [R14]  Up
L.2.2.6.3  Current location discovery during an emergency call [R14]  Word-p. 869
L.2A  Usage of SDP
L.2A.0  General [R9]
L.2A.1  Impact on SDP offer / answer of activation or modification of EPS bearer context for media by the network
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
L.2A.3  Emergency service [R11]  Word-p. 870
L.3  Application usage of SIP
L.3.1  Procedures at the UE
L.3.1.0  Registration and authentication [R13]
L.3.1.0a  IMS_Registration_handling policy [R15]  Up
L.3.1.1  P-Access-Network-Info header field  Word-p. 871
L.3.1.1A  Cellular-Network-Info header field [R13]
L.3.1.2  Availability for calls
L.3.1.2A  Availability for SMS [R11]  Word-p. 873
L.3.1.3  Authorization header field [R10]
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 [R10]
L.3.1.5  3GPP PS data off [R14]  Word-p. 874
L.3.1.6  Transport mechanisms [R15]  Word-p. 875
L.3.1.7  RLOS [R16]
L.3.1.7.1  General  Up
L.3.1.7.2  Registration
L.3.1.7.3.1  General  Word-p. 876
L.3.1.7.3.2  RLOS session set-up in case of unsuccessful registration
L.3.1.7.3.3  RLOS session set-up in case of successful registration  Word-p. 877
L.3.2  Procedures at the P-CSCF  Word-p. 878
L.3.2.0  Registration and authentication [R12]
L.3.2.1  Determining network to which the originating user is attached
L.3.2.2  Location information handling
L.3.2.3  Prohibited usage of PDN connection for emergency bearer services [R9]
L.3.2.4  Support for paging policy differentiation [R13]  Up
L.3.2.5  Void
L.3.2.6  Resource sharing [R13]  Word-p. 879
L.3.2.6.1  Registration
L.3.2.6.2  UE-originating case
L.3.2.6.3  UE-terminating case  Word-p. 880
L.3.2.6.3.1  The initial INVITE request contains an initial SDP offer
L.3.2.6.3.2  The 18x response or the 2xx responses contains an initial SDP offer
L.3.2.6.4  Abnormal cases  Word-p. 881
L.3.2.6.5  Resource sharing options updated by AS
L.3.2.7  Priority sharing [R13]
L.3.2.7.1  General  Up
L.3.2.7.2  Registration procedure
L.3.2.7.3  Session establishment procedure  Word-p. 882
L.3.2.7.4  Subsequent request procedure
L.3.2.8  RLOS [R16]
L.3.2.8.1  General
L.3.2.8.2  Registration
L.3.2.8.3.1  General  Word-p. 883
L.3.2.8.3.2  General treatment for RLOS session setup - requests from an unregistered user
L.3.2.8.3.3  General treatment for RLOS session setup - requests from a registered user  Word-p. 884
L.3.2.9  Support of ANBR and RAN-assisted codec adaptation [R16]  Up
L.3.3  Procedures at the S-CSCF
L.3.3.1  Notification of AS about registration status
L.3.3.2  RLOS [R16]
L.3.3.2.1  General
L.3.3.2.2  Registration
L.4  3GPP specific encoding for SIP header field extensions  Word-p. 887
L.4.1  Void
L.5  Use of circuit-switched domain

Up   Top   ToC