Introduction

E-CSCF is a network element in IMS, which is responsible for routing an emergency call to a
PSAP. As the current E-CSCF standards are still evolving, a list of technical requirements
have been put together from various sources (3GPP, NENA, Customer specific requirements)
in Appendix A. This design document will cater to the requirements listed here.

1 Detailed Feature/Component Description

1.1 Overview
E-CSCF will receive new requests from the P-CSCF and route them to a PSAP or a BGCF
when PSAP is in the CS Domain. To identify the next hop PSAP, E-CSCF interacts with the
LRF. LRF provides the necessary routing information so that E-CSCF can route the request
to the appropriate PSAP.

Le (e.g. E2)
LRF from PSAP

Ml to PSAP or ECS
via IP mutimedia
Mm Network
Gm Mw
UE P-CSCF E-CSCF Mi/Mg

to PSAP
Mw
(via PSTN
via BGCF/
MGCF)

Mm/Mw
S-CSCF from PSAP
1.2 Configurable
1.2.1 E-CSCF service
E-CSCF will be configured as a new role under the cscf-service. This will allow operators to
configure a standalone E-CSCF service.

Mode: config-cscf-service
Description: This command is used to enable emergency cscf service.
CLI:
[ctx]st16(config-cscf-service)# emergency-cscf

1.2.2 Privacy
Operator can configure privacy support for E-CSCF service. Based on this configuration,
several privacy procedures will be applied at E-CSCF.

Mode: config-cscf-service-emergency-cscf
Description: This command is used to enable privacy for emergency cscf service.
CLI:
[ctx]st16(config-cscf-service-emergency-cscf)# privacy

1.3 Procedures at E-CSCF

This section describes the SIP procedures that will be applied as part of the E-CSCF service
at the sessmgr. The following general points need to be noted for E-CSCF:

 E-CSCF is a subscriber un-aware and hence, it will not store any subscriber specific
data.
 When an out-of-dialog request is received at E-CSCF, operator is expected to setup a
cscf-route CLI so that the initial request will be routed to an external LRF component.
 When the external LRF component sends a redirect response, it will provide the next-
hop PSAP address in the Contact header of the redirect response.
 E-CSCF will forward the INVITE request to the PSAP address received after
applying the appropriate SIP procedures.
Out-Of-Dialog SIP-
Message received

Yes

Reject the request

Is it an INVITE
No with “405 Method
?
Not Allowed”

Yes

Is Emergency Reject the request

Proxy-
Yes Privacy CLI No with “420 Bad
Require:Privac
Enabled? Extension”
y?

No Yes

If Privacy tag Reject the request

Privacy:critical? Yes other than Yes with “500 Internal
header/critical Error”
received?

No
No

ECSCF will be set Is Emergency Reject the request

to Proxy Mode for Privacy CLI No with “500 Internal
this request. Enabled ? Error”

Yes

ECSCF wlil be set

to B2BUA Mode
for this request.

1. Store the access-network-charging-info

param from the P-Charging-Vector
2. Store the request-uri if it is a tel:911 or
tel:112.

Forward the request to the LRF:

- Preferably a matching cscf-route should be

configured with LRF as peer-server.
- If no route is configured, request will be
forwarded using request-uri.
Figure-1: Procedures at E-CSCF when an Out-Of-Dialog SIP Message is received
3xx response received
from LRF

Is ECSCF in
Proxy-Mode ?
Yes A new redirected INVITE will be created by making a
Copy any PAI copy of the original INVITE, except for new call-id/tag..
headers received Following processing is done on this INVITE message:
No
in 3xx into call-cb.
1. Remove all SIP message bodies with content-type:
application/pidf+xml.

A redirected INVITE 2. Update the Content-Type header if required

with the same Call-
id/From tag as 3. Remove Geo-location header.
original INVITE will
be created.

1. Remove Privacy: Header

Copy the PAI
2. If there is no tag other the Privacy: Critical,
headers stored in
remove all the Privacy headers.
the call-cb into the
redirected INVITE

Update the Redirected INVITE’s

Request-URI with the first Contact URI
received in the 3xx

If P-Charging-Vector was present in the

original INVITE, add a type-2 orig-ioi param in
the redirected-INVITE:

This will be set to either

- default-aor-domain (if available) or
- hostname (if available) or
- bind-ip-adress

Forward the INVITE request based on either

the cscf-route configured or request-URI.
Figure-2: Procedures at E-CSCF when a 3xx response is received from LRF
In-Dialog SIP Message

Is request
message?

No Yes
Forward the Forward the
If 1xx or 2xx If not ACK or
message to the No No message to the
response? CANCEL ?
destination. destination.

Yes Yes

1. Remove any PPI headers Update the access-network-

present. charging-info param in the P-
2. Add PAI with the stored Charging-Vector wth the one that
request-uri of the orginal is stored
INVITE request.

Forward the message to the

destination.

Figure-3: Procedures at E-CSCF for in-dialog messages after INVITE is forwarded to PSAP.

1.4 E-CSCF Call-Flow

1.4.1 User initiated Emergency Call
 UA/P-CSCF E-CSCF LRF BGCF/MGCF PSAP

INVITE
INVITE

3XX

ACK

INVITE (New Request-URI, PAI)

200 OK
200 OK
Session setup with PSAP
ACK
ACK

SESSION ESTABLISHED

BYE
BYE

Session teardown with PSAP

200 OK
200 OK

SESSION TERMINATED

Figure-4: End-End Emergency Call Session Establishment and TearDown

1.4.2 PSAP CallBack

In case the emergency call drops in-between and if the PSAP want to callback the user, the
procedure below is followed:
 PSAP calls the Emergency-User using the MDN received.
 MGCF will route the call to the User’s S-CSCF.
 S-CSCF will route the call to the User’s P-CSCF using the Path Header.
 User’s P-CSCF will in turn forward the call to the User’s phone.
1.5 Mapping of 3xx header fields to INVITE

This section describes the mapping of the header fields received in 3xx message (from the
LRF) to the new redirected INVITE message (sent to BGCF).

3xx Response Fields INVITE Fields

Contact Header Request-URI
List of PAI List of PAI

1.6 Detailed Design

1.6.1 Data Structure Changes
This section describes the data structure changes for E-CSCF.

1.6.1.1 cscf_ProxyRoleType_t

typedef enum cscf_ProxyRoleType {

…
CSCF_PROXY_ROLE_ECSCF = 5,
…
} cscf_ProxyRoleType_t;

A new role, ECSCF is added to the list of ProxyRole types.

1.6.1.2 UMM_TYPE_EmergencyNum
typedef enum

{
UMM_EMERGENCYNUM_INVALID = 0,
UMM_EMERGENCYNUM_911,
UMM_EMERGENCYNUM_112
} UMM_TYPE_EmergencyNum;

A new enum indicating the standard emergency numbers is defined.

1.6.1.3 SIPAPP_CALL_CB

typedef struct sipapp_call_cb

{
…
UMM_DLL_t paiList; /* List Of UMM_PARAM_PAssertedIdentity_t */
UMM_TYPE_EmergencyNum emergencynum_type; /* Emergency-Number Type */
} SIPAPP_CALL_CB;

When E-CSCF receives an initial INVITE request, and if the request-uri was a tel:911 or
tel:112, then SIPAPP stores this as an emergency enum in the SIPAPP_CALL_CB.
When E-CSCF receives a 3xx response with a list of PAI headers from LRF, SIPAPP will
store the list of PAI headers in the SIPAPP_CALL_CB.