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

Glossary term · Services

MSD

Minimum Set of emergency related Data

MSD has more than one meaning in 3GPP. Also: Maximum Sensitivity Degradation.

Services →

MSD is the standardized, minimal set of data a network must obtain and provide for emergency services to ensure basic call setup and location information, even when normal authentication fails.

Introduced
Rel-7
Where
Radio Access Network › NG-RAN (5G)
Specifications
55 specs
Also in
User Equipment, Services, Core Network
MSD Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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

Full comparison in TR 21.905 →
TS 23.167Rel-17 → Rel-18

Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.

Full comparison in TS 23.167 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 1 change
  • CR on MSD for EN-DC including Band 66 and n78 to TR 37.872 TS 37.872CR0001
Rel-18 1 change
  • Clarification to lower MSD capability TS 38.306CR1240
Rel-19 6 changes
  • Support of MSD transfer for a PSAP Callback for eCall over IMS TS 23.167CR0376
  • Alignment of abnormal MSD transfer for eCall with CEN TS 24.229CR6670
  • Correcting the reference for eCall MSD definition TS 24.229CR6679
  • Correcting Updated MSD Transfer for PSAP Callback for an eCall TS 24.229CR6685
  • Clarifications to eCall setup, in-band MSD transmission and retry TS 24.229CR6727
  • (NR_CADC_SUL_R19-Core) CR to 38.719-03-01 to correct UL transmission bandwidth symbol LCRB in MSD tables TS 38.719CR0001
Rel-20 1 change
  • Clarification on parameters for EmergencyCallData.eCall.MSD Info Package in Recv-Info header field TS 24.229CR6791

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 22.967 vj00 eCall Emergency Data Transmission Rel-19 read
TS 23.167 vk10 IMS Emergency Services Rel-20 read
TS 23.216 vj00 SRVCC Architecture Enhancements Rel-19 read
TS 23.237 vj00 IMS Service Continuity (ISC) Stage 2 Rel-19 read
TS 24.008 vk10 NAS Call, Mobility and Session Procedures Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 26.267 vj00 eCall In-band Modem Specification Rel-19 read
TS 26.268 vj00 eCall In-band Modem ANSI-C Code Rel-19 read
TS 26.269 vj00 eCall In-band Modem Conformance Testing Rel-19 read
TR 26.967 vj00 eCall via CTM Suitability Analysis Rel-19 read
TR 26.969 vj00 eCall In-band Modem Performance Characterization Rel-19 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 36.101 vk10 E-UTRA UE RF Requirements Rel-20 read
TS 36.833 3GPP TR 36.833 Rel-7 read
TS 36.853 3GPP TR 36.853 Rel-7 read
TS 37.716 3GPP TR 37.716 Rel-7 read
TS 37.717 3GPP TR 37.717 Rel-7 read
TS 37.718 3GPP TR 37.718 Rel-7 read
TS 37.719 vj00 Rel-19 Dual Connectivity Band Combinations Rel-19 read
TS 37.825 vg00 High Power UE (PC2) for EN-DC TDD-TDD Rel-16 read
TS 37.863 3GPP TR 37.863 Rel-7 read
TS 37.864 3GPP TR 37.864 Rel-7 read
TS 37.865 3GPP TR 37.865 Rel-7 read
TS 37.866 3GPP TR 37.866 Rel-7 read
TS 37.872 vf10 Technical Report on SUL & LTE-NR DC with SUL Rel-15 read
TR 37.878 vi00 Technical Report on Rel-18 NR V2X Band Combinations Rel-18 read
TS 37.898 vj00 Rel-19 HPUE for EN-DC Band Combinations Rel-19 read
TS 38.101 vj40 UE Radio Transmission and Reception; Satellite Access Rel-19 read
TS 38.306 vj40 NR UE Radio Access Capability Parameters Rel-19 read
TS 38.521 vj10 UE Conformance Spec for NR Satellite Access Rel-19 read
TS 38.716 3GPP TR 38.716 Rel-7 read
TS 38.717 3GPP TR 38.717 Rel-7 read
TS 38.718 3GPP TR 38.718 Rel-7 read
TS 38.719 vj10 NR Inter-band CA/DC Configurations Rel-19 read
TS 38.741 vj20 NR NTN L-/S-Band Requirements Rel-19 read
TS 38.746 vj00 High Power UE for NR Inter-band CA/DC Rel-19 read
TS 38.750 vj00 High Power UE for NR Inter-band CA/DC Rel-19 read
TS 38.755 vj10 NR FR1 DL Fragmented Carriers Study Rel-19 read
TS 38.792 vj00 UE RF Requirements for PC1.5 Inter-band UL CA/DC Rel-19 read
TS 38.793 vj00 Simultaneous Rx/Tx Band Combinations TR Rel-19 read
TS 38.796 vj00 Rel-19 High Power UE for NR FR1 Rel-19 read
TR 38.839 vh00 Simultaneous Rx/Tx band combinations Rel-17 read
TR 38.841 vh00 High power UE for NR inter-band CA Rel-17 read
TR 38.842 vh00 High Power UE for NR CA with Multiple Bands Rel-17 read
TR 38.846 vi10 Technical Report Rel-18 read
TR 38.850 vi10 Technical Report for Rel-18 High Power UE Rel-18 read
TS 38.863 vk00 NR NTN RF Coexistence Requirements Rel-20 read
TS 38.870 vj50 Enhanced OTA Test Methods for NR TRP and TRS Rel-19 read
TR 38.872 vi40 Technical Report on Sub-1GHz NR Band Combinations Rel-18 read
TR 38.880 vi00 Technical Report for 3Tx inter-band UL CA and EN-DC Rel-18 read
TR 38.881 vi00 Technical Report on Lower MSD for Inter-band CA/EN-DC/DC Rel-18 read
TR 38.894 vi00 Technical Report Rel-18 read
TR 38.896 vi00 Technical Report for High Power UE (Power Class 2) for NR FR1 FDD Rel-18 read
TR 38.899 vi00 Technical Report for High Power UE Rel-18 read