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…
Q
[N] IP-Connectivity Access Network specific concepts when using the cdma2000® 1x Femtocell Network to access IM CN subsystem
Q.1
Scope
Q.2
cdma2000® 1x Femtocell Network aspects when connected to the IM CN subsystem
Q.2A
Usage of SDP
Q.3
Application usage of SIP
Q.3.1
Procedures at the UE
Q.3.2
Procedures at the P-CSCF
Q.3.3
Procedures at the S-CSCF
Q.4
3GPP specific encoding for SIP header field extensions
Q.5
Use of circuit-switched domain
...
Q
(Normative) IP-Connectivity Access Network specific concepts when using the cdma2000® 1x Femtocell Network to access IM CN subsystem
[R9]
Word-p. 907
Q.1
Scope
Q.2
cdma2000® 1x Femtocell Network aspects when connected to the IM CN subsystem
Q.2.1
Introduction
Q.2.2
Procedures at the UE
Q.2.2.1
Activation and P-CSCF discovery
Q.2.2.1A
Modification of IP-CAN used for SIP signalling
Word-p. 908
Q.2.2.1B
Re-establishment of IP-CAN used for SIP signalling
Q.2.2.2
Void
Q.2.2.3
Void
Q.2.2.4
Void
Q.2.2.5
Handling of the IP-CAN for media
Q.2.2.5.1
General requirements
Q.2.2.5.1A
Activation or modification of IP-CAN for media by the UE
Q.2.2.5.1B
Activation or modification of IP-CAN for media by the network
Q.2.2.5.1C
Deactivation of IP-CAN for media
[R11]
Q.2.2.5.2
Special requirements applying to forked responses
Q.2.2.5.3
Unsuccessful situations
Q.2.2.6
Emergency service
Q.2.2.6.1
General
[R14]
Q.2.2.6.1A
Type of emergency service derived from emergency service category value
[R15]
Q.2.2.6.1B
Type of emergency service derived from extended local emergency number list
[R15]
Q.2.2.6.2
eCall type of emergency service
[R14]
Word-p. 909
Q.2.2.6.3
Current location discovery during an emergency call
[R14]
Q.2A
Usage of SDP
Q.2A.0
General
Q.2A.1
Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network
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
Q.2A.3
Emergency service
[R11]
Q.3
Application usage of SIP
Q.3.1
Procedures at the UE
Q.3.1.0
Void
Q.3.1.0a
IMS_Registration_handling policy
[R15]
Q.3.1.1
P-Access-Network-Info header field
Q.3.1.1A
Cellular-Network-Info header field
[R13]
Q.3.1.2
Availability for calls
Word-p. 910
Q.3.1.2A
Availability for SMS
[R11]
Q.3.1.3
Authorization header field
[R10]
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
[R10]
Q.3.1.5
3GPP PS data off
[R14]
Q.3.1.6
Transport mechanisms
[R15]
Q.3.1.7
RLOS
[R16]
Q.3.2
Procedures at the P-CSCF
Q.3.2.0
Registration and authentication
[R12]
Q.3.2.1
Determining network to which the originating user is attached
Q.3.2.2
Location information handling
Q.3.2.3
Void
Q.3.2.4
Void
Q.3.2.5
Void
Q.3.2.6
Resource sharing
[R13]
Word-p. 911
Q.3.2.7
Priority sharing
[R13]
Q.3.2.8
RLOS
[R16]
Q.3.3
Procedures at the S-CSCF
Q.3.3.1
Notification of AS about registration status
Q.3.3.2
RLOS
[R16]
Q.4
3GPP specific encoding for SIP header field extensions
Q.4.1
Void
Q.5
Use of circuit-switched domain