ESQK

Emergency Service Query Key

Services →
Introduced in Rel-7

ESQK is a temporary identifier used in the IMS to correlate an emergency call with location and subscriber data for routing to the correct PSAP and providing accurate caller information.

Category
Services
Introduced
Rel-7
Where
Services
Specifications
1 specs
ESQK Description Purpose Related Classification Detected Changes Specifications

Description

The Emergency Service Query Key (ESQK) is a critical element within the 3GPP IMS emergency services architecture, defined primarily in TS 23.167. It functions as a temporary, unique key assigned by the network for the duration of an emergency session. When a user initiates an emergency call via an IMS network, the call is routed to an Emergency Call Session Control Function (E-CSCF). The E-CSCF, in conjunction with a Location Retrieval Function (LRF), is responsible for obtaining the caller's location. The ESQK is generated and associated with this specific emergency session and its corresponding location data.

The ESQK is then inserted into the Session Initiation Protocol (SIP) signaling of the emergency call, typically in the Request-URI or a dedicated header. When the call is routed to the Public Safety Answering Point (PSAP), the PSAP system uses the received ESQK as a query key. The PSAP sends this ESQK in a query to a designated emergency services network entity, such as an Emergency Services Message Entity (ESME) or via the LoST (Location-to-Service Translation) protocol framework, to retrieve the associated location information and other call data from the network's database where the E-CSCF/LRF stored it.

This mechanism decouples the real-time voice call path from the location data retrieval path, which is essential for efficiency and reliability. The PSAP does not need to parse complex location objects within the SIP signaling itself; it simply uses the lightweight ESQK to fetch the data. This architecture supports both initial location retrieval and subsequent location updates, as the network can push updated location information to the same database record keyed by the ESQK. The ESQK is temporary and valid only for the life of the emergency session, after which it can be recycled, ensuring privacy and efficient resource usage.

Key components involved with the ESQK include the User Equipment (UE), the Proxy-CSCF (P-CSCF) that detects the emergency request, the E-CSCF that manages the emergency session, the LRF that obtains and formats location information, and the PSAP infrastructure. The ESQK enables a standardized, interoperable interface between the mobile operator's IMS core and disparate PSAP systems, which may be operated by different authorities. Its role is foundational for Next Generation emergency services (NG-eCall, IMS emergency calls) where accurate, network-derived location is paramount.

Purpose & Motivation

The ESQK was introduced to solve critical problems in routing emergency calls and delivering location information within IP-based networks, specifically IMS. Traditional circuit-switched emergency calls often embedded location data directly in the call signaling or relied on the cell ID available to the PSAP, which could be inaccurate or insufficient for rapid response, especially for mobile users. As networks evolved to all-IP architectures, a new, standardized method was needed to correlate a voice call with dynamically obtained, precise location data.

The primary motivation was to separate the delivery of the emergency voice media from the delivery of associated data (like GPS coordinates or civic address). This separation allows each system—the voice routing network and the location database system—to operate optimally. It also accommodates the fact that PSAPs may need to query for location after the call is answered and may require updated locations if the caller is moving. The ESQK provides a simple, universal 'key' that bridges these two worlds, enabling PSAPs from various vendors and regions to interoperate with 3GPP-compliant networks without needing deep integration into the operator's internal location systems.

Furthermore, it addresses privacy and security concerns by using a temporary, non-personal identifier. The ESQK does not reveal the caller's phone number (MSISDN) or permanent subscriber identifier to the PSAP until explicitly retrieved, if allowed by policy. This architecture, centered on the ESQK, was a foundational step towards reliable, location-enabled emergency services in LTE and 5G, supporting regulatory requirements like E911 in the US and eCall in Europe.

Classification

Part ofESRK
Specific typesESRK
Related approachesE-CSCFPSAP

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (22 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-7, normative work from Rel-15.

Rel-15 15 changes

In Release 15, the ESQK function was not newly introduced; the provided grounding context defines it as an existing 10-digit key used by the LRF for location look-up, while the listed CR titles for this release focus on expanding emergency service support for 5GS, NG-RAN, and untrusted non-3GPP access, alongside enhancements to domain selection and local emergency number handling.

  • Support of IMS Emergency Calls for NG-RAN access to 5GS TS 23.167CR0319
  • More Flexible Domain selection for Emergency Calls using the PS Domain TS 23.167CR0341
  • Emergency services over 5GC via untrusted non-3GPP access TS 23.167CR0320
  • Handling of emergency sessions over untrusted N3GPP access in 5GS TS 23.167CR0321
  • Delivery of local emergency numbers in NAS TS 23.167CR0324
  • Addition of Emergency Services Support using Fallback to Domain Selection Rules TS 23.167CR0325

+ 9 more changes

Rel-16 3 changes

In Release 16, the ESQK function was enhanced to support IMS emergency sessions for roaming users in 5GS deployments that lack IMS-level roaming interfaces, ensuring location retrieval and callback identification could still function. This was part of enabling emergency calls using trusted non-3GPP access to the 5G Core network. The release also included corrections for the procedures of IMS Emergency Registration and Session Establishment to ensure robust ESQK handling.

  • Enabling emergency call using trusted non-3GPP access to 5GC TS 23.167CR0344
  • Support of IMS emergency sessions for roaming users in 5GS deployments without IMS-level roaming interfaces TS 23.167CR0350
  • Correction for IMS Emergency Registration and Session Establishment TS 23.167CR0355
Rel-17 4 changes

In Release 17, the ESQK function was enhanced to support new access scenarios, including IMS Emergency Calls over NR Satellite Access and for emergency sessions within a Stand-alone Non-Public Network (SNPN). These additions ensure the ESQK, as the key for the LRF to look up location and callback information, remains functional for emergency calls established over these new types of network access.

  • Support for Caller Identity Attestation and Assertion of Emergency sessions TS 23.167CR0359
  • Support of IMS Emergency Calls over NR Satellite Access TS 23.167CR0361
  • KI#3: Support for IMS emergency over SNPN TS 23.167CR0360
  • Usage of alternate P-CSCF for emergency registration TS 23.167CR0365

Explore further

Broader topics and technologies where ESQK plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.167 vj11 IMS Emergency Sessions Rel-19