Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.229  Word version:  17.8.1

Top   Top   Up   Prev   Next
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 (Normative)  IP-Connectivity Access Network specific concepts when using the cdma2000® 1x Femtocell Network to access IM CN subsystem |R9|p. 982

Q.1  Scopep. 982

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 subsystemp. 982

Q.2.1  Introductionp. 982

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.
Up

Q.2.2  Procedures at the UEp. 982

Q.2.2.1  Activation and P-CSCF discoveryp. 982

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.
Up

Q.2.2.1A  Modification of IP-CAN used for SIP signallingp. 983

Not applicable.

Q.2.2.1B  Re-establishment of IP-CAN used for SIP signallingp. 983

Not applicable.

Q.2.2.2Void

Q.2.2.3Void

Q.2.2.4Void

Q.2.2.5  Handling of the IP-CAN for mediap. 983

Q.2.2.5.1  General requirementsp. 983
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 UEp. 983
Not applicable.
Q.2.2.5.1B  Activation or modification of IP-CAN for media by the networkp. 983
Not applicable.
Q.2.2.5.1C  Deactivation of IP-CAN for media |R11|p. 983
Not applicable
Q.2.2.5.2  Special requirements applying to forked responsesp. 983
Not applicable.
Q.2.2.5.3  Unsuccessful situationsp. 983
Not applicable.

Q.2.2.6  Emergency servicep. 983

Q.2.2.6.1  General |R14|p. 983
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. 983
Not applicable.
Q.2.2.6.1B  Type of emergency service derived from extended local emergency number list |R15|p. 983
Not applicable.
Q.2.2.6.2  eCall type of emergency service |R14|p. 984
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. 984
Void.

Q.2A  Usage of SDPp. 984

Q.3  Application usage of SIPp. 984

Q.3.1  Procedures at the UEp. 984

Q.3.2  Procedures at the P-CSCFp. 985

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

Void.

Q.3.2.1  Determining network to which the originating user is attachedp. 985

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.

Q.3.2.2  Location information handlingp. 985

Not applicable

Q.3.2.3Void

Q.3.2.4Void

Q.3.2.5Void

Q.3.2.6  Resource sharing |R13|p. 986

Not applicable.

Q.3.2.7  Priority sharing |R13|p. 986

Not applicable.

Q.3.2.8  RLOS |R16|p. 986

Not applicable.

Q.3.3  Procedures at the S-CSCFp. 986

Q.3.3.1  Notification of AS about registration statusp. 986

Not applicable

Q.3.3.2  RLOS |R16|p. 986

Not applicable.

Q.4  3GPP specific encoding for SIP header field extensionsp. 986

Q.5  Use of circuit-switched domainp. 986

Not applicable

Up   Top   ToC