NG112 reference
Ecall Msd
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
eCall and NG eCall
eCall Minimum Set of Data
MSD gives the PSAP context such as vehicle identity, trigger type, location and direction-related information at a high level. The operational point is not just data transport; it is whether call takers can see, trust and act on the data.
Vehicle sensors
->MSD
->eCall session
->PSAP display
What it does
The Minimum Set of Data is the structured vehicle and incident information sent with an eCall.
MSD is a model for emergency data associated with a vehicle-originated call.
How it works
- The vehicle prepares a standardized emergency data payload.
- The payload accompanies the emergency call path.
- PSAP tools decode and display actionable fields.
Key interfaces and protocols
- Vehicle eCall system
- Emergency call path
- PSAP eCall decoder/display
Systems it interacts with
- eCall
- NG eCall
- Additional data
- PSAP
- Recording
Common failure modes
- Data decode failure
- Location in MSD conflicts with network location.
- Call taker does not recognize trigger context.
- Recording misses associated data.
Implementation considerations
- Train PSAP teams on MSD fields.
- Test vehicle data display and retention.
- Document how conflicting locations are handled.
Standards
- European eCall standards
- ETSI Plugtests references
Related NG112 technologies
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- 6th NG112 and NG eCall Plugtests Report - ETSI, accessed 2026-08-31
- Next Generation 112 and the new Emergency Services Networks Landscape - EENA, accessed 2026-08-31
Last verified: 2026-08-31
Advertisement