ATCF/ATGW Support

The following sections describe ATCF/ATGW support available on the SCM (P-CSCF/A-BG).

Feature Description

ATCF (Access Transfer Control Function)/ATGW (Access Transfer Gateway) functionality in P-CSCF service supports Single Radio Voice Call Continuity (SRVCC) functionality. ATCF/ATGW provides proxy role and UA role, as per 3GPP TS 24.237.

SRVCC refers to continuity between Internet Protocol (IP) Multimedia Subsystem (IMS)-over-Packet Switched (PS) access and Circuit Switched (CS) calls that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time.

SRVCC provides the ability to transition a voice call from the VoIP/IMS packet domain to the legacy circuit domain. There are many standards which supports both GSM/UMTS and CDMA 1x circuit domains. For an operator with a legacy cellular network who wishes to deploy IMS/VoIP-based voice services in conjunction with the rollout of an LTE network, SRVCC offers VoIP subscribers with coverage over a much larger area than would typically be available during the rollout of a new network.

Overview

For supporting SRVCC, either Service Centralization and Continuity - Application Server (SCC-AS) or ATCF should anchor the session. When UE is in the home network, IMS sessions are anchored at SCC-AS based on iFC. The SCC-AS will act as third party call-control function to facilitate inter-access mobility. This chapter will not address the SRVCC functionality in SCC-AS.

When UE is roaming, the visiting ATCF in the serving domain can anchor the session to provide service continuity based on the operator policy. The following figure illustrates the high level architecture of SRVCC using ATCF enhancements.


Figure 1. IMS SRVCC Architecture When Using ATCF Enhancements

The ATCF functionality can be co-located with P-CSCF. The ATGW will also be included in the media path if SRVCC enhanced with ATCF is used. The SCM supports ATCF/ATGW as part of P-CSCF node. When SRVCC enhanced with ATCF is used, the ATCF is included in the session control plane for the duration of the call before and after Access Transfer. The ATGW is controlled by the ATCF for media path.

The figure below illustrates session setup when ATCF/ATGW is included in the signaling and bearer paths for the sessions with Packet Switched (PS) domain.


Figure 2. Signaling and Bearer Paths for Sessions with PS Media Using ATCF

Relationships to Other Features

The following features can be used in conjunction with ATCF/ATGW functionality.

IPv6-IPv4 Interworking

IPv6-IPv4 Interworking is supported for ATCF/ATGW. For more information on IPv6-IPv4 Interworking support, refer to IPv6IPv4 Mode in ATCFATGW.

IMPORTANT:

Use of IPv4-IPv6 interworking requires that a valid license key be installed. Contact your Cisco account representative for information on how to obtain a license.

Lawful Intercept (LI)

When Lawful Intercept is enabled for the subscriber to whom Access Transfer is requested by the MSC-Server, new access leg created towards the ATCF and then to SCC-AS will also be marked for Lawful Intercept and packets sent will be tapped. The packets include the newly generated Invite, 200OK, Ack generated by P-CSCF towards SCC-AS, and all other in-dialogue messages sent by the subscriber.

Lawful Intercept during ATCF applies for both event-delivery as well as content-delivery types of Lawful Intercept. There is no extra CLI configuration needed to enable Lawful Intercept for ATCF/ATGW.

IMPORTANT:

For additional information and documentation on the Lawful Intercept feature, contact your Cisco account representative.

Session Recovery

Redundancy works for ATCF/ATGW.

For more information on Session Recovery support, refer to the Session Recovery chapter in the Cisco ASR 5000 System Administration Guide.

IMPORTANT:

Use of Session Recovery requires that a valid license key be installed. Contact your Cisco account representative for information on how to obtain a license.

How it Works

This section will provide details on ATCF/ATGW functionality implementation in P-CSCF service.

Registration

When user does initial registration in the IMS network, P-CSCF will invoke ATCF/ATGW functionality and decides to include itself for access transfer of sessions according to operator policy. The inclusion of ATCF/ATGW functionality will be decided based on the following factors.

  • If UE is roaming, based on the roaming agreement (home operator also supports SRVCC enhanced with ATCF in SCC-AS and HSS). ATCF will have a list of configured home networks which support SRVCC. ATCF functionality will only be invoked for those home networks. Comparison will be done against domain name in request URI.
  • If ATCF is enabled in P-CSCF service.
  • If UE is SRVCC capable. The SC UE shall include the g.3gpp.accesstype media feature tag as described in subclause B.3 of 3GPP TS 24.292 [4] in the Contact header field of the SIP REGISTER request. ATCF will decide based on this tag.
  • Based on Access-Type. Access type is E-UTRAN, UTRAN and GERAN access networks for which ATCF will be included.

Operator will have the liberty to choose these criteria while configuring ATCF; either one of them or a set or neither can qualify.

During registration, ATCF will allocate a routable Session Transfer Number - Single Radio (STN-SR) pointing to the ATCF. This number is configured in CSCF ATCF/ATGW Configuration Mode. This STN-SR ensures that MSC Server selects the correct ATCF during SRVCC procedure. This STN-SR allocated will be forwarded to IMS Core (S-CSCF) though Feature-Caps header. The ATCF will also include a management URI and path header information (same as P-CSCF path) in the Feature-Caps header. The management URI will be used by SCC-AS to provide SRVCC information to ATCF node.

The IMS-Core (S-CSCF) will forward the UE registration information to SCC-AS through third party register request. S-CSCF will include UE Register and 200OK to register in multi-part body of the third party register request.

After third party registration is successful, SCC-AS will send MESSAGE request to provide SRVCC information to ATCF. The SRVCC information will be included in the message body of MESSAGE request. It will contain the following information:

  • Correlation-MSISDN: A Correlation MSISDN (C-MSISDN) is an MSISDN that is used for correlation of sessions at access transfer and to route a call from the IM CN subsystem to the same user in the CS domain. The C-MSISDN is bound to the IMS Private User Identity and is uniquely assigned per IMSI and IMS Private User Identity.
  • ATU-STI (Access Transfer Update - Session Transfer Identifier): This point to the SCC-AS and is allocated to the SCC-AS.
  • ATCF-Path: This is exactly the path header added by ATCF during registration.

Once ATCF/ATGW receives the above information from SCC-AS, Access-Transfer functionality for that subscriber will be enabled.

Furthermore, ATCF needs to validate the identity of SCC-AS. A list of SCC-AS will be configured in ATCF, and incoming message request from SCC-AS will have SCC-AS identity in URI in the P-Asserted-Identity header. This identity will be compared against stored list, and if they don't match MESSAGE request will be responded to with SIP 403 (Forbidden) response with warning header “SCC-AS not authorised”.

Now, ATCF needs to make the decision if it supports CS-PS access transfer. ATCF should look for g.3gpp.cs2ps-srvcc media feature tag and g.3gpp.path in the Contact header field of the SIP REGISTER request to decide if SC UE supports CS-PS access transfer. ATCF should generate SIP 2xx response for register towards UE, which contains a Feature-Caps header field with the g.3gpp.atcf feature capability indicator and with the g.3gpp.cs2ps-srvcc feature capability indicator and dynamic STI-rSR. In this case, ATCF should send MESSAGE request to UE with ATGW information. ATCF should send SIP MESSAGE request to UE after receiving SIP message request from SCC-AS if

  1. The ATCF indicated the support of the CS to PS SRVCC when handling the SIP REGISTER request establishing the registration path;
  2. The SRVCC-related information for the registration path contains the ATU-STI for CS to PS SRVCC; and
  3. The ATCF does not have the UE information for CS to PS SRVCC bound to the registration path.

During Registration, if the ATCF is aware of all MSC servers which can be involved in the SRVCC procedures and which are in the same network as the ATCF, and it supports the MSC server assisted mid-call feature, ATCF should insert the g.3gpp.mid-call feature capability indicator while forwarding requests.

SRVCC Information Bound to the Registration Path

The ATCF shall keep track of existing registrations of the served UEs. Each registration path is identified by the ATCF Path URI.

The ATCF shall bind the following information to the registration path identified by the ATCF Path URI:

  • The S-CSCF Service-Route URI; (already stored)
  • The ATU-STI for PS to CS SRVCC; (stored in subscriber call leg)
  • The C-MSISDN. (stored in subscriber call leg)

If the ATCF supports CS to PS SRVCC, the ATCF shall additionally bind the following information to the registration path identified by the ATCF Path URI:

  • The ATU-STI for CS to PS SRVCC;
  • The contact address of the SC UE;
  • The route set towards the SC UE;
  • The UE information for CS to PS SRVCC;
  • The ATGW information for CS to PS SRVCC

PS Session Establishment

When ATCF functionality is enabled for a Subscriber, P-CSCF will anchor the media for the PS Session establishment. P-CSCF with ATCF/ATGW will allocate NPU flows for media lines for both orig UE and the term UE. During session establishment, ATCF/ATGW will store the remote UE's contact, which will be used when ATCF sends 200OK to session-transfer request from MSC Server. P-CSCF with ATCF/ATGW will act in Proxy Mode for the session.

PS-CS Transfer

When access transfer is requested by MSC-Server to ATCF for performing PS-to-CS access transfer, a new access leg is established by the UE towards the ATCF and then to SCC-AS. The ATCF subdivides the new access leg into a serving leg and a home leg. signaling and bearer resources are allocated in the transferring-in access network and the user's sessions are transferred from the transferring-out access network. The ATCF executes access transfer procedures in co-operation with the SCC-AS. Resources in the transferring-out access network are subsequently released by the SCC-AS.

CS-PS Transfer

Currently, this is not supported and based on tags cs2ps-srvcc REGISTER request will be rejected with 403.

Abnormal Procedures

When the ATCF receives one of the following:

  1. A SIP BYE request on the Source Access Leg containing a Reason header field containing a SIP 503 (Service Unavailable) response code that is terminating an established dialog or an early dialog on the Source Access Leg;
  2. A SIP CANCEL request on the Source Access Leg with the Reason header field containing a SIP 503 (Service Unavailable) response code then, that is terminating an early dialog on the Source Access Leg originated by the SC UE; or
  3. A SIP 503 (Service Unavailable) response on the Source Access Leg, that is terminating an early dialog on the Source Access Leg terminating at the SC UE;

Then, the ATCF shall retain session state information and ATGW resources associated with the session until either it receives a SIP INVITE request due to STN-SR or an operator determined period elapses.

This behavior and timer will be configured through CLI since ATCF and P-CSCF are a single entity.

  • P-CSCF, on receiving ASR for UE for that call, will hold onto that ASR for duration of 8 seconds. (Timer value configurable through CLI.)
  • During these 8 seconds, if access transfer request is received, then this ASR is ignored.
  • If Access transfer request is not received, than ASR is responded to with STR and a BYE is issued towards network without reason header “503 Service not available”. This BYE will be issued on existing call-leg towards S-CSCF.
  • This timer to hold onto ASR will only be cancelled if access transfer is successful. If access transfer invite is rejected because of any reason, then ASR is handled appropriately.

Limitations

ATCF has an assumption that S-CSCF will act as Proxy when it forwards the PS session establishment request to SCC-AS. This is needed when ATCF performs the session transfer and sends Target-Dialog header to SCC-AS to release the PS Call.

Flows

This section presents call procedure flows.

The following topics and procedure flows are included:

Registration

The call flow for UE registration in IMS domain is shown in the following diagram.


Figure 3. Registration

Session Establishment

The call flow for PS session establishment in IMS domain is shown in the following diagram.


Figure 4. Session Establishment

Access Transfer (PS-CS)

The call flow for PS to CS domain session transfer is shown in the following diagram.


Figure 5. Access Transfer (PS-CS)

IPv6IPv4 Mode in ATCF/ATGW

Initially, ATCF will handle IPv6 subscribers for IPv4 core network.

The following are some of the differences between Proxy mode ATCF and IPv6IPv4 mode:

  1. ATCF CLIs need to be configured on both access and core side.
  2. MESSAGE from AS will come to core ATCF demux manager.
  3. Access transfer INVITE from MSC will come to Core ATCF demux manager.
  4. Initial session establishment from IPv6 UE would happen with IPv6 addresses in SDP. Once access transfer happens and UE moves to CS domain, MSC will use IPv4 addresses.
  5. 200OK invite response sent for ATCF INVITE will contain IPv4 addresses allocated from IP pool.
  6. Destination for RTP packets for access side will change from IPv6 IPs to IPv4 IPs.

Figure 6. IPv6IPv4 Mode in ATCF/ATGW

Standards Compliance

ATCF/ATGW support complies with the following standards:

  • 3GPP TS 23.237 V10.8.0 (2011-2012) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 (Release 10)
  • 3GPP TS 24.237 V10.5.0 (2011-2012) 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) Service Continuity; Stage 3 (Release 10)

Configuring ATCF Functionality

IMPORTANT:

Commands used in the configuration samples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Cisco ASR 5x00 Command Line Interface Reference for complete information regarding all commands.

To configure support of ATCF functionality:

  1. Create an ATCF policy by applying the example configuration in the Creating an ATCF Policy section.
  2. Enable ATCF functionality in a P-CSCF service by applying the example configuration in the Enabling ATCF Functionality in P-CSCF Service section.
  3. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Creating an ATCF Policy

Use the following example to create an ATCF policy:

config
   context <context_name>
      atcf
policy name <policy_name>
         criteria { access-type { 3gpp-e-utran-fdd | 3gpp-e-utran-tdd | 3gpp-geran | 3gpp-utranfdd | 3gpp-utran-tdd | any | cellular | docsis | dsl | ethernet | wlan } | all | any | icscapability | roaming }
         ps-cs-alerting
         end

Notes:

  • <policy_name> must be an alphanumeric string of 1 through 79 characters.
  • criteria enables criteria to invoke ATCF functionality.
  • ps-cs-alerting determines if ATCF shall support access transfer of call in alerting state from PS-CS.
  • Multiple policies can be configured, and then one can be associated inside the ATCF service. By default, “default” policy will be applicable

Enabling ATCF Functionality in P-CSCF Service

Use the following example to assign an existing ATCF policy to the specified P-CSCF service:

config
   context <context_name>
      cscf
service <service_name>
         proxy-cscf
            atcf-atgw
               call-linger-timer <seconds>
               mgmt-uri <mgmt_uri>
               policy
name <name>
               stn-sr <stn-sr>
               trusted
scc-as <scc-as>
               end

Notes:

  • call-linger-timer determines timeout value of session for abnormal procedure parameters in ATCF service. <seconds> must be 1 to 32 seconds.
  • mgmt-uri supports PSI-based routing mode in I-CSCF. <mgmt_uri> must be an alphanumeric string of 1 through 127 characters. Example format of management uri sip:atcf.xyz.net for hostname with domain or sip:xyz@abc.com for uri.
  • policy name must be an existing ATCF policy.
  • stn-sr specifies a Session Transfer Number for Single Radio (STN-SR) for the ATCF. The same STN-SR number will be used for all subscribers. <stn-sr> must be a string of up to 15 digits.
  • trusted scc-as specifies a trusted SCC-AS address in ATCF service. <scc-as> must be an alphanumeric string of 1 through 79 characters.

Verifying ATCF/ATGW Configuration

Use the following command to verify if ACTF functionality is enabled.

show cscf service all

Monitoring and Troubleshooting ATCF/ATGW

ATCF/ATGW Show Command(s) and/or Outputs

This section provides information regarding show commands and/or their outputs in support of ATCF/ATGW.

The show commands in this section are available in support of ATCF/ATGW.

show cscf service

The following command shows statistics related to ATCF access transfers.

show cscf service statistics
name p-cscf_name atcf

clear cscf service

The following command clears all statistics related to ATCF access transfers.

clear cscf service
statistics name p-cscf_name atcf

show cscf service statistics name <p-cscf_name> atcf

The following fields have been added to this command to display all the ATCF/P-CSCF access transfer statistics related to calls:

  • ATCF call statistics
    • Access Transfer Attempts
    • Access Transfer Success
    • Access Transfer Failures
    • 404 Error responses
    • 500 Internal Error
    • 488 Responses
    • 4xx Responses
    • 5xx Responses
    • 6xx Responses

show cscf service statistics name <p-cscf_name>

The following fields have been added to this command for ATCF support:

  • ATCF call statistics
    • Access Transfer Attempts
    • Access Transfer Success
    • Access Transfer Failures

show subscribers cscf-only full

The following fields have been added to this command for ATCF support:

  • SRVCC Enabled
  • ICS capable

ATCF/ATGW Bulk Statistics

The following statistics are included in the CSCF Schema in support of ATCF:

  • at-att-rx
  • at-att-tx
  • at-succ-rx
  • at-succ-tx
  • at-fail-rx
  • at-fail-tx
  • at-fail-404-rx
  • at-fail-404-tx
  • at-fail-488-rx
  • at-fail-488-tx
  • at-fail-500-rx
  • at-fail-500-tx
  • at-fail-4xx-rx
  • at-fail-4xx-tx
  • at-fail-5xx-rx
  • at-fail-5xx-tx
  • at-fail-6xx-rx
  • at-fail-6xx-tx

For descriptions of these variables, see “CSCF Schema Statistics” in the Statistics and Counters Reference.