Content for TS 24.229 Word version: 18.4.0

1… 3… 4… 4.5… 5… 5.1.1.4… 5.1.2… 5.1.4… 5.2… 5.2.3… 5.2.6… 5.2.7… 5.3… 5.4… 5.4.1.2.2… 5.4.1.3… 5.4.2 5.4.3… 5.4.3.3… 5.4.4… 5.5… 5.7… 5.7.2… 5.8… 5.11… 6… 6.6… 7… 7.2A… 7.2A.6… 7.3… 7.9A… 8… A… A.2… A.2.1.4… A.2.1.4.7… A.2.1.4.8… A.2.1.4.10A… A.2.1.4.12… A.2.2… A.2.2.4… A.2.2.4.7… A.2.2.4.8… A.2.2.4.10A… A.2.2.4.12… A.3… A.3.3… B… C… E… F… H… I… K… L… L.2A… M… N… O… Q… R… S… U… U.2A… V… W…

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

Q.1 Scope p. 933

The present annex defines IP-CAN specific requirements for 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), where the IP-CAN is an IP network as incorporated into the cdma2000® 1x femtocell network subsystem [86E].

Q.2 cdma2000® 1x Femtocell Network aspects when connected to the IM CN subsystem p. 933

Q.2.1 Introduction p. 933

In the cdma2000® 1x femtocell network subsystem, the cdma2000® 1x Mobile Station (MS) accesses the IM CN subsystem by utilising the services provided by the cdma2000® 1x Femtocell Access Point (FAP) [86E].

The cdma2000® 1x FAP 3GPP2 X.P0059-200 [86E] acts as a UE toward the IM CN subsystem.

From the perspective of the FAP, it is assumed that one or more IP-CAN bearer(s) are provided, in the form of connection(s) managed by the layer 2.

Q.2.2 Procedures at the UE p. 933

Q.2.2.1 Activation and P-CSCF discovery p. 933

Unless a static IP address is allocated to the cdma2000® 1x FAP, prior to communication with the IM CN subsystem, the cdma2000® 1x FAP shall perform a Network Attachment procedure depending on the used cdma2000® 1x FAP access type. When using a cdma2000® 1x FAP access, both IPv4 and IPv6 may be used to access the IM CN subsystem. The cdma2000® 1x FAP may request a DNS Server IPv4 address(es) via RFC 2132 or a DNS Server IPv6 address(es) via RFC 3315.

When using IPv4, the cdma2000® 1x FAP may acquires a P-CSCF address(es) by using the DHCP (see RFC 2132), the DHCPv4 options for SIP servers (see RFC 3361), and RFC 3263.

In case the DHCP server provides several P-CSCF addresses or FQDNs to the cdma2000® 1x FAP, the cdma2000® 1x FAP shall select the P-CSCF address or FQDN as indicated in RFC 3361. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the cdma2000® 1x FAP is implementation specific.

When using IPv6, the cdma2000® 1x FAP may acquires a P-CSCF address(es) by using the DHCPv6 (see RFC 3315 and RFC 3646), the DHCPv6 options for SIP servers (see RFC 3319), and RFC 3263.

In case the DHCP server provides several P-CSCF addresses or FQDNs to the cdma2000® 1x FAP, the cdma2000® 1x FAP shall select the P-CSCF address or FQDN as indicated in RFC 3319. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the cdma2000® 1x FAP is implementation specific.

Q.2.2.1A Modification of IP-CAN used for SIP signalling p. 934

Not applicable.

Q.2.2.1B Re-establishment of IP-CAN used for SIP signalling p. 934

Not applicable.

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

Q.2.2.5.1 General requirements p. 934

The cdma2000® 1x FAP uses the bearer used for signalling also for transmission of media.

Q.2.2.5.1A Activation or modification of IP-CAN for media by the UE p. 934

Not applicable.

Q.2.2.5.1B Activation or modification of IP-CAN for media by the network p. 934

Not applicable.

Q.2.2.5.1C Deactivation of IP-CAN for media |R11| p. 934

Not applicable

Q.2.2.5.2 Special requirements applying to forked responses p. 934

Not applicable.

Q.2.2.5.3 Unsuccessful situations p. 934

Not applicable.

Q.2.2.6 Emergency service p. 934

Q.2.2.6.1 General |R14| p. 934

Emergency calls are perceived as regular calls from the perspective of the IM CN subsystem. Entities outside the IM CN subsystem identify and route such calls to PSAP.

Q.2.2.6.1A Type of emergency service derived from emergency service category value |R15| p. 934

Not applicable.

Q.2.2.6.1B Type of emergency service derived from extended local emergency number list |R15| p. 934

Not applicable.

Q.2.2.6.2 eCall type of emergency service |R14| p. 935

The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic".

Q.2.2.6.3 Current location discovery during an emergency call |R14| p. 935

Void.

Q.2A Usage of SDP p. 935

Q.2A.0 General p. 935

Not applicable.

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

Not applicable.

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

Not applicable.

Q.2A.3 Emergency service |R11| p. 935

No additional procedures defined.

Q.3 Application usage of SIP p. 935

Q.3.1 Procedures at the UE p. 935

Q.3.1.0 Void

Q.3.1.0a IMS_Registration_handling policy |R15| p. 935

Not applicable.

Q.3.1.1 P-Access-Network-Info header field p. 935

The cdma2000® 1x FAP shall include the P-Access-Network-Info header field where indicated in subclause 5.1.

Q.3.1.1A Cellular-Network-Info header field |R13| p. 935

Not applicable.

Q.3.1.2 Availability for calls p. 936

Not applicable.

Q.3.1.2A Availability for SMS |R11| p. 936

Void.

Q.3.1.3 Authorization header field |R10| p. 936

Void.

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

Not applicable.

Q.3.1.5 3GPP PS data off |R14| p. 936

Not applicable.

Q.3.1.6 Transport mechanisms |R15| p. 936

No additional requirements are defined.

Q.3.1.7 RLOS |R16| p. 936

Not applicable.

Q.3.2 Procedures at the P-CSCF p. 936

Q.3.2.0 Registration and authentication |R12| p. 936

Void.

Q.3.2.1 Determining network to which the originating user is attached p. 936

If access-type field in the P-Access-Network-Info header field indicated 3GPP2-1X-Femto access the P-CSCF shall assume that an initial request for a dialog or standalone transaction or an unknown method destined for a PSAP is initiated in the same country.