NG112 reference
Iot
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Applications and Data
IoT Emergency Data
Sensors, alarms and connected devices can provide context, but emergency communications intake must remain controlled, authenticated and operationally usable. IoT data is most credible when it arrives through validated applications, alarm workflows or managed emergency-data interfaces.
What it does
IoT emergency data may support emergency response, but arbitrary devices should not be assumed to access NG112 directly.
IoT may provide contextual emergency data alongside a human emergency communication or authorized alert workflow.
How it works
- Collects device or incident data from managed systems.
- Normalizes and authenticates data before emergency use.
- Presents only actionable information to call takers or responders.
Key interfaces and protocols
- Application APIs
- Additional data references
- Security/authentication
- PSAP integration
Systems it interacts with
- Additional data
- Emergency apps
- Security
- PSAP
- CAD
Common failure modes
- False alarms flood PSAP workflows.
- Untrusted devices inject bad data.
- Data lacks location or caller context.
- Automation bypasses human verification where required.
Implementation considerations
- Avoid direct-to-PSAP assumptions without official support.
- Rate-limit and authenticate device sources.
- Prioritize actionable data over novelty.
Standards
- IETF additional data concepts
- National emergency-services rules
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
Last verified: 2026-08-31