DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
The ATCF is generally expected to be co-located with an existing functional element in the IMS architecture, such as the P-CSCF, IBCF or MSC server. The most likely option for ATCF co-location is the P-CSCF, since it is already in the path of all UE signalling with IMS. The IBCF is only in the path for a session when the UE is roaming, and the MSC server is only involved in a session during and after SRVCC. Thus the IBCF and MSC server are not co-located with the ATCF. The E-CSCF may reside within the P-CSCF to support IMS Emergency procedures.
ATCF and E-CSCF integrated with P-CSCF : In this case IMS-AGW would act as ATGW (and also since the SBC5xx0 acts as integrated P-CSCF and IMS-AGW, Ribbon ATCF/ATGW solution would also be integrated in same box i.e ATGW interface is NOT exposed externally).
E-CSCF is responsible for routing emergency call requests to the nearest PSAP based on the callers location information, as well as other information, such as the type of emergency service being requested. E-CSCF receives from the P-CSCF request for emergency session establishment, and, if required, contacts the LRF to validate the location information given by the UE and routes the request to the appropriate destination.
Figure 1: SBC as P-CSCF along with co-located ATCF and E-CSCF
At a high level, the functions performed by the ATCF are:
At a high level, the functions performed by the E-CSCF are:
For configuration details, see Configuring SBC as P-CSCF Co-located with ATCF and E-CSCF