Emergency Service Routing Key

Description

The Emergency Service Routing Key (ESRK) is a critical identifier defined in 3GPP TS 23.167 for supporting legacy North American E911 Phase I and Phase II requirements within 3GPP networks. It is a 10-digit number, resembling a telephone number, that is dynamically assigned by the network's Mobile Switching Center (MSC) or its successor in the IP Multimedia Subsystem (IMS), such as an Emergency CSCF (E-CSCF) in conjunction with a Gateway Mobile Location Center (GMLC). When a mobile user initiates an emergency call (e.g., dials 911), the serving network node (MSC for circuit-switched, E-CSCF for IMS) requests an ESRK from a location server or generates it based on the cell of origin.

The primary function of the ESRK is call routing. The network uses the ESRK to route the emergency call through the telephone network to a selective router, which then directs the call to the specific PSAP responsible for the geographic area associated with that ESRK. The mapping between ESRKs and PSAPs is maintained in a national or regional Emergency Services Routing Database (ESRD). Essentially, the ESRK encodes coarse location information—typically the cell site and sector identifier—allowing the call to reach a PSAP in the correct jurisdiction even before any precise GPS or network-derived location is obtained.

Once the call is established at the PSAP, the ESRK serves a second vital function: it is the key for retrieving the caller's more precise location and callback number. The PSAP equipment automatically queries an Automatic Location Identification (ALI) database using the ESRK. This ALI database has been populated by the wireless carrier's GMLC or location server with the precise coordinates (for Phase II) and the mobile directory number (MDN) associated with that specific ESRK assignment. This two-step process—routing via ESRK, then data retrieval via ESRK—ensures the call gets to the right dispatcher quickly, and the dispatcher then receives the detailed information needed for response.

In an IMS-based emergency call scenario, the ESRK may be used in conjunction with or as an alternative to the ESQK, depending on the interface requirements of the legacy PSAP network. The network must ensure the ESRK is unique for the duration of the emergency call and is released for reuse after a timeout period. Its role is foundational for interoperability between modern 3GPP networks and the installed base of E911 infrastructure in North America.

Purpose & Motivation

The ESRK was developed to solve the fundamental challenge of routing wireless emergency calls to the correct PSAP, a problem that did not exist with traditional landline phones where the phone number is tied to a fixed address. In the early days of cellular networks, a 911 call from a mobile phone could only be routed to a default PSAP, often a state police barracks, requiring manual transfer and causing critical delays. The E911 Phase I mandate required wireless carriers to provide a callback number and the location of the cell site handling the call.

The ESRK mechanism was created to meet this mandate. It provides a dynamic, location-dependent 'pseudo-number' that the telephone switching network can use for routing, just as it routes regular calls based on area code and exchange. This allowed the existing wireline E911 selective routing infrastructure to be reused for wireless calls without major overhaul. The ESRK system addressed the limitation of not having a fixed subscriber location by tying the routing key to the network element (cell site) currently serving the caller.

As E911 evolved to Phase II, requiring more precise location (within 50-300 meters), the ESRK's role expanded. It became the essential link that correlated the initial routed call with the subsequently delivered high-accuracy location data. Its continued specification in 3GPP standards, even for IMS-based networks, ensures backward compatibility and supports a gradual migration path for emergency services. It solves the critical problem of ensuring life-saving calls reach the correct local responders in the shortest possible time, leveraging both new location technologies and legacy routing databases.