Q.2 cdma2000® 1x Femtocell Network aspects when connected to the IM CN subsystem
24.2293GPPIP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Release 18Stage 3TS
Q.2.1 Introduction
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].
NOTE: Protocol between the cdma2000® 1x MS and the cdma2000® 1x FAP is out of scope of this document.
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
Q.2.2.1 Activation and P-CSCF discovery
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 [20F] or a DNS Server IPv6 address(es) via RFC 3315 [40].
When using IPv4, the cdma2000® 1x FAP may acquires a P-CSCF address(es) by using the DHCP (see RFC 2132 [20F]), the DHCPv4 options for SIP servers (see RFC 3361 [35A]), and RFC 3263 [27A].
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 [35A]. 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 [40] and RFC 3646 [56C]), the DHCPv6 options for SIP servers (see RFC 3319 [41]), and RFC 3263 [27H].
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 [41]. 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
Not applicable.
Q.2.2.1B Re-establishment of IP-CAN used for SIP signalling
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
Q.2.2.5.1 General requirements
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
Not applicable.
Q.2.2.5.1B Activation or modification of IP-CAN for media by the network
Not applicable.
Q.2.2.5.1C Deactivation of IP-CAN for media
Not applicable
Q.2.2.5.2 Special requirements applying to forked responses
Not applicable.
Q.2.2.5.3 Unsuccessful situations
Not applicable.
Q.2.2.6 Emergency service
Q.2.2.6.1 General
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
Not applicable.
Q.2.2.6.1B Type of emergency service derived from extended local emergency number list
Not applicable.
Q.2.2.6.2 eCall type of emergency service
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
Void.