NG112 reference
Additional Data
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Applications and Data
Additional Emergency Data
Additional data can relate to the call, caller, device, application, vehicle or incident. It must be governed carefully because usefulness, privacy, security and PSAP workflow all matter. Standards-defined structures should be separated from conceptual or proprietary examples.
What it does
Additional emergency data is information beyond the media session and basic location that may help emergency response.
It can enrich PSAP context when delivered in a controlled, interoperable and privacy-aware way.
How it works
- Associates structured data with an emergency session.
- May be carried directly or retrieved through a reference depending on architecture.
- PSAP systems decide what is displayed, stored and acted upon.
Key interfaces and protocols
- IETF RFC 7852
- SIP references
- Application APIs
- PSAP data display
Systems it interacts with
- SIP
- PSAP
- Emergency apps
- eCall MSD
- Security
Common failure modes
- Too much data distracts call takers.
- Sensitive data is over-retained.
- Reference retrieval fails inside emergency network.
- Data source is not trusted.
Implementation considerations
- Define a minimum useful data set.
- Use provenance and timestamps.
- Apply privacy-by-design and retention controls.
Standards
- IETF RFC 7852
- ETSI NG112 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
- RFC 7852: Additional Data Related to an Emergency Call - IETF, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, accessed 2026-08-31
- Directive (EU) 2018/1972 establishing the European Electronic Communications Code - European Union, accessed 2026-08-31
Last verified: 2026-08-31