Minimum Set of emergency related Data

Description

The Minimum Set of emergency related Data (MSD) is a critical 3GPP concept designed to guarantee that essential information is available to support emergency services (e.g., calling 112, 911). It is defined as the bare minimum data set that a network must be able to retrieve and utilize to establish an emergency session and provide aid, particularly for users who are not authenticated, have no valid subscription, or are roaming outside their home network. The MSD ensures that regulatory requirements for emergency services can be met under virtually all circumstances.

Architecturally, the MSD involves multiple network entities. When a User Equipment (UE) initiates an emergency request, the serving network (Visited Public Land Mobile Network - VPLMN) must attempt to acquire the MSD. This data may be stored in the UE itself, retrieved from the UE's home network (HPLMN) if possible, or derived from the network's own context. Key components involved include the UE, the Radio Access Network (RAN), the Mobility Management Entity (MME) in LTE or the Access and Mobility Management Function (AMF) in 5GC, the Gateway Mobile Location Centre (GMLC), and the Emergency Centre. The MSD typically includes, but is not limited to, the location of the UE (or information to determine it), a callback number, and the identity of the serving cell.

The process works as follows: Upon detecting an emergency service request, the network bypasses normal authentication and subscription checks. It then activates procedures to collect the MSD. The UE may provide some data (e.g., its last known location estimate if it has positioning capabilities). The network uses cell-ID or more advanced methods to determine location. A temporary identifier or a network-assigned callback number is established. This MSD is then made available to the Public Safety Answering Point (PSAP) or emergency center. The role of the MSD is to fulfill the fundamental principle that emergency services must be accessible to anyone, anytime. Its specification across numerous technical documents (from core network protocols to radio performance specs) ensures interoperability and defines fallback mechanisms for when full subscriber data is unavailable.

Purpose & Motivation

The MSD exists to solve a fundamental life-saving problem: ensuring emergency services can receive a call and locate the caller even when the cellular system lacks normal subscriber credentials. Prior to its formalization, networks might reject emergency attempts from non-subscribers or fail to provide crucial location data, potentially with fatal consequences. The MSD was motivated by regulatory and ethical mandates for universal access to emergency services.

It addresses the limitations of traditional cellular operation, which is heavily based on authenticated subscribers with known profiles. In situations like a user without a SIM card, an invalid subscription, or a roaming user whose home network is unreachable, the network still has a legal obligation to connect the emergency call. The MSD provides a standardized fallback framework. Historical context includes the evolution of emergency service requirements from basic voice connectivity (e.g., GSM Phase 1) to enhanced mandates for caller location (E911 in the US, eCall in Europe), which necessitated a robust, standardized data set.

The creation of the MSD ensures technological compliance with these regulations across all 3GPP-based networks. It defines a clear contractual point between network operators and authorities on what minimum information will be supplied. This solves interoperability issues between different network vendors and across borders, ensuring that a phone from any manufacturer, on any compliant network, can provide a baseline level of emergency support. It is a cornerstone for citizen safety in mobile communications.

Key Features

• Ensures emergency call setup without authentication/subscription
• Includes minimum required location information for the caller
• Provides a callback number or identifier for emergency services
• Standardized across core network and access network specifications
• Supports regulatory requirements (e.g., E911, eCall)
• Involves fallback procedures when home network data is unavailable

Evolution Across Releases

Defining Specifications