Extended Emergency Number List Validity

Description

Extended Emergency Number List Validity (EENLV) is a feature defined in 3GPP specifications that manages the UE's (User Equipment's) internal cache of emergency service numbers. The UE typically receives an 'Emergency Number List' from the network via NAS (Non-Access Stratum) signaling, which contains the dialing codes (e.g., 112, 911, 999) valid in its current location or registered PLMN. This list has a finite validity timer. EENLV extends the operational logic for this timer to ensure the UE can still attempt emergency calls using a potentially outdated list if it cannot reach the network to obtain a fresh one.

Architecturally, EENLV is implemented within the UE's NAS layer, specifically in the Mobility Management (MM) and Connection Management (CM) sublayers that handle subscriber registration and session management. The feature interacts with the UE's internal storage (often a USIM application or secure memory) where the last received Emergency Number List and its associated validity timer are kept. The core network indicates the list's validity duration, but with EENLV, the UE applies extended rules for using an expired list.

Operationally, when the UE needs to place an emergency call, it first checks its stored Emergency Number List. If the list's validity timer has expired, standard behavior might prevent the call attempt. With EENLV enabled, the UE is permitted to use the expired list under specific conditions, primarily when it is in a state where it cannot successfully perform a registration or location update to acquire a new list—such as in limited service state (e.g., out of coverage of its home network but within range of any available cell). The UE uses the last known valid list to interpret the dialed digits.

This mechanism is crucial for the UE's fallback logic. It ensures that the human-centric emergency service access is prioritized over strict protocol adherence to timers. The network can control the feature's parameters, but the UE's autonomous decision-making during failure scenarios is enhanced. EENLV does not modify the network-side procedures; it is a UE-centric reliability enhancement for emergency service discovery.

Purpose & Motivation

EENLV was introduced to solve a critical reliability gap in emergency calling. Prior to its introduction, if a UE's stored Emergency Number List expired and the UE could not contact a network to refresh it (e.g., due to being out of coverage, in a radio failure state, or in a non-allowed PLMN), the UE might not recognize a dialed emergency number. This could prevent the emergency call attempt altogether, creating a dangerous scenario where a user in distress cannot even attempt to connect to any available radio access.

The historical context is the increasing reliance on network-provided configuration for services, including emergency numbers which vary by country and region. While this dynamism is beneficial, it introduced a dependency: a UE without recent network contact might have an invalid view of emergency codes. EENLV addresses this by allowing the UE to use its last-known configuration as a best-effort fallback, prioritizing the ability to attempt a call over the certainty of number validity. This aligns with regulatory and safety principles that emergency access should be maximally available.

The feature mitigates the limitations of a strictly timer-driven approach. It acknowledges that in many emergency scenarios, the user's location or network conditions may be impaired. By extending the validity logic, it reduces the risk of a false negative where a UE incorrectly decides an emergency number is invalid. It complements other reliability features like support for emergency calls in limited service state and emergency bearer services.

Key Features

• Extends the usability of an expired Emergency Number List stored on the UE
• Triggers fallback behavior when UE is in limited service state or cannot contact the network
• UE-autonomous operation without requiring network interaction for the decision
• Maintains alignment with regulatory requirements for emergency service accessibility
• Configurable via network-provided parameters but with UE-implemented safety logic
• Integrates with NAS procedures for mobility management and emergency call establishment

Evolution Across Releases

Defining Specifications