Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

E-CSCF

Emergency – Call Session Control Function

Services →

E-CSCF is the IMS core network function that handles emergency call session establishment and routing by determining the correct PSAP based on the user's location and service requirements.

Introduced
Rel-7
Where
Services › IMS
Specifications
8 specs
Also in
Core Network
E-CSCF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Emergency – Call Session Control Function (E-CSCF) is a critical component within the IP Multimedia Subsystem (IMS) architecture, specifically designed to manage emergency sessions. It operates as a specialized SIP proxy server. When an emergency session initiation request (e.g., an INVITE message with an emergency service URN) is received by the IMS, typically via a Proxy-CSCF (P-CSCF), it is forwarded to the E-CSCF. The E-CSCF's primary role is to ascertain the caller's location, either from information embedded in the SIP signaling (e.g., PANI, CAI, or civic address) or by querying other network entities like a Location Retrieval Function (LRF).

Using the obtained location information, the E-CSCF interacts with a Location-to-Service Translation (LoST) server or a similar functional entity. This interaction translates the geographic coordinates or civic address into a uniform resource identifier (URI) for the appropriate Public Safety Answering Point (PSAP). The PSAP is the contact point for emergency services like police, fire, or ambulance. The E-CSCF then routes the emergency session request (SIP INVITE) to this PSAP URI, ensuring the call reaches the correct local emergency authority.

Furthermore, the E-CSCF plays a vital role in scenarios where normal IMS registration or subscription checks might fail. For emergency sessions, the E-CSCF may bypass certain authentication and authorization procedures to ensure the call is established even for unregistered users or users without a valid subscription, adhering to regulatory requirements for universal access to emergency services. It also coordinates with the LRF for possible subsequent location requests from the PSAP, facilitating emergency call back and accurate dispatch of first responders.

Purpose & Motivation

The E-CSCF was introduced to address the critical need for reliable, location-aware emergency call handling in IP-based networks, specifically within the 3GPP IMS framework. Traditional circuit-switched mobile networks had established mechanisms for emergency calls, but the migration to all-IP core networks like IMS presented new challenges. In an IP environment, routing is not inherently tied to a physical network location, making it difficult to determine which local emergency service center should receive a call.

Its creation was motivated by regulatory and safety requirements mandating that emergency calls be routed to the correct local PSAP based on the caller's current location, regardless of their home network or registration status. The E-CSCF solves the problem of translating a user's device location (which could be dynamic in a mobile network) into a routable address for the appropriate emergency service endpoint. It ensures that the advanced session control capabilities of IMS are leveraged for emergency services, providing a standardized, robust, and future-proof architecture for emergency communications in LTE, 5G, and subsequent generations of mobile networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define E-CSCF. Each summary describes the whole specification, not only this term.

TS 23.271Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.271: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.271 →
TS 24.229Rel-18 → Rel-19

Rel-19 adds Rich Call Data support to TS 24.229, including the DC-Info header, rcd-np Call-Info parameter, and RCD info retrieval and verification across originating, terminating, IBCF and AS behaviour. It also adds MPS for Messaging, eCall alignment with EN 17184:2024 (test eCall and updated-MSD transfer), and satellite identifiers in P-Access-Network-Info.

Full comparison in TS 24.229 →

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • E-CSCF split from CSCF
    “The CSCF can act as Proxy CSCF (P‑CSCF), Serving CSCF (S‑CSCF), Emergency CSCF (E‑CSCF), or Interrogating CSCF (I‑CSCF).” TS 23.002
  • E-CSCF used together with BGCF
    “The E‑CSCF is the IMS network entity, which is responsible to route the request to an emergency centre/PSAP via or BGCF, IBCF or IP multimedia network based on location information” TS 23.167

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 12 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-7 introduced

The E-CSCF is defined for the first time in Rel-7: a new CSCF role that routes emergency requests to a PSAP, retrieves location from the LRF, and has its own SIP procedures in TS 24.229.

  • “This specification introduces an additional CSCF role to those defined in the IMS architecture TS 23.002 [12], called Emergency CSCF (E‑CSCF)” TS 23.167 v7.13.0
  • “The E‑CSCF is the IMS network entity, which is responsible to route the request to an emergency centre/PSAP or BGCF” TS 23.167 v7.13.0
  • “If the E-CSCF fails to select a PSAP based on the received location information contained in an INVITE request” TS 24.229 v7.34.0
Rel-8 specification text

The E-CSCF gained a requirement to derive a non-dialable callback number for UEs without credentials where regulation requires it, and its emergency routing and forwarding text was revised.

  • “Where required by local regulation, the E-CSCF shall derive a non-dialable callback number to include as the UE's identity in the session establishment request” TS 23.167 v8.6.0
  • “The E‑CSCF shall inform the UE that the session has been marked as an emergency session” TS 23.167 v8.6.0
  • “The E‑CSCF forwards the SIP request containing the UE's location information to the PSAP/Emergency Centre via PS domain or via BGCF/MGCF” TS 23.167 v8.6.0
Rel-9 specification text

E-CSCF behaviour was extended: it can query an external server for location when PSAP selection fails, handles privacy requests, rejects non-emergency requests with 403, and gets a new I4 reference point to the EATF.

Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.

  • “the E-CSCF fails to select the PSAP, the E-CSCF can interrogate an external server in order to retrieve location information.” TS 24.229 v9.31.0
  • “the E-CSCF shall reject the request by sending a 403 (Forbidden) response.” TS 24.229 v9.31.0
  • “I4 is a reference point between an E-CSCF and an EATF. See TS 23.237 [32].” TS 23.167 v9.14.0
Rel-10 specification text

E-CSCF behaviour was extended: it can receive emergency requests from an IBCF or S-CSCF, exchanges type 2 IOI, inserts location by reference from 3xx responses, and uses reference points Mx and Mw.

  • “In scenarios where the E-CSCF receives emergency requests from an S-CSCF, a type 2 IOI is exchanged.” TS 24.229 v10.29.0
  • “the E-CSCF shall insert a Geolocation header field containing this PIDF location object by reference” TS 24.229 v10.29.0
  • “The E‑CSCF uses Mw, Mg, Mi, Ml, Mm, Mx and I4 reference points to connect to other IMS entities and other IP Networks.” TS 23.167 v10.11.0
Rel-11 specification text

E-CSCF behaviour was extended: it now provides the UA role for dialog event notification and LRF location by value, strips P-Asserted-Identity on responses, and inserts a Geolocation header for location by reference.

  • “when acting as a notifier for the dialog event package the E-CSCF shall provide the UA role” TS 24.229 v11.31.0
  • “the E-CSCF shall insert a Geolocation header field containing this PIDF location object by reference” TS 24.229 v11.31.0
  • “The E-CSCF retrieves location information from LRF as described in clause 6.2.2.” TS 23.167 v11.11.0
Rel-12 specification text

E-CSCF handling of P-Charging-Vector in SUBSCRIBE from the LRF was corrected: the 200 OK now includes an icid-value, and orig-ioi is set in requests the E-CSCF sends.

  • “the "icid-value" header field parameter is set to the received value of the "icid-value" header field parameter in the request.” TS 24.229 v12.27.0
  • “Correcting E-CSCF P-Charging-Vector handling for SUBSCRIBE from LRF” TS 24.229 v12.27.0
  • “The E-CSCF shall set the type 3 "orig-ioi" header field parameter to a value that identifies the sending network of the request.” TS 24.229 v12.27.0
Rel-13 specification text

E-CSCF behaviour in 24.229 changed: it now handles P-Charging-Vector (ICID/IOI) separately from P-Charging-Function-Addresses, with IOI clarified between P-CSCF and E-CSCF.

  • “Apply general principle of ICID and IOI to E-CSCF” TS 24.229 v13.23.0
  • “Clarification of IOI between a P-CSCF and an E-CSCF on request from a user with/without emergency registration” TS 24.229 v13.23.0
  • “the E-CSCF may insert previously saved values into a P-Charging-Function-Addresses header field before forwarding the message.” TS 24.229 v13.23.0
Rel-14 specification text

E-CSCF procedures were extended in Rel-14: logging of logme requests, Response-Source and fe-addr insertion, forwarding to PSAPs in other networks via IBCF, and handling of SUBSCRIBE for emergency call location.

  • “Based on local policy the E-CSCF shall add an "fe-addr" element of the "fe-identifier" header field parameter to the P-Charging-Vector header field” TS 24.229 v14.21.0
  • “The E-CSCF may forward an emergency request to a PSAP in the IM CN subsystem, a PSAP attached to another network, or a PSAP in the PSTN.” TS 24.229 v14.21.0
  • “For an NG-eCall and if an LRF/RDF is not deployed, the E-CSCF may use an indication of an automatic eCall or a manual eCall” TS 23.167 v14.6.0
Rel-15 specification text

E-CSCF emergency routing text now covers 5GS (NG-RAN) and untrusted non-3GPP access to 5GC, and its non-emergency-bearer session handling now also refers to emergency PDU sessions.

  • “5GS (NG-RAN), fixed broadband access, WLAN access to EPC or untrusted non-3GPP access to 5GC for the emergency service.” TS 23.167 v15.7.0
  • “Such a session will not use an emergency PDN connection or emergency PDU session” TS 23.167 v15.7.0
Rel-16 specification text

The E-CSCF's Geolocation-by-reference insertion from a 3xx response now requires the PIDF location object to conform to RFC 5491 as well as RFC 4119.

  • “identifying a PIDF location object as defined in RFC 4119 [90] and RFC 5491 [267], then the E-CSCF shall insert a Geolocation header field” TS 24.229 v16.17.0
Rel-17 specification text

In Rel-17 the P-CSCF may retrieve additional subscriber identifiers for anonymous emergency sessions and forward them to the E-CSCF, and may assert Resource-Priority before forwarding the request to the E-CSCF.

  • “P‑CSCF may retrieve additional subscriber related identifier(s) from IP-CAN and forward those identifiers to E-CSCF.” TS 23.167 v17.2.0
  • “Prior to forwarding the request to an appropriate E-CSCF, the P-CSCF may assert Resource-Priority information for an emergency session” TS 23.167 v17.2.0
Rel-18 1 CR

The P-CSCF now passes the relay's NCGI and UE identity to the E-CSCF for emergency calls from 5G ProSe Remote UEs, and the E-CSCF performs location validation for the L3 remote UE.

  • “the P-CSCF provides to the E-CSCF the NCGI and the UE Identity of 5G ProSe UE-to-Network Relay received from the PCF” TS 23.167 v18.2.0
  • Location validation for the L3 remote UE by the E-CSCF TS 23.167CR0373

Defining Specifications

3GPP specifications that define or reference E-CSCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.409 vj00 IMS Performance Management Measurements Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read