NG112 reference
Location
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Location
Emergency Location Chain
A good NG112 implementation does not treat location as one magic field. Devices, networks, enterprise systems and mobile platforms may produce location. PIDF-LO may represent it. SIP may convey it. LVF may validate civic data. ECRF or equivalent routing functions may use it. PSAP tools must display it clearly enough for action.
What it does
Emergency location is a chain of separate functions: determining location, representing it, conveying it, validating it and using it for routing and display.
Location is the evidence that helps route the emergency session and guide responders.
How it works
- Combines civic, geodetic, network and handset-derived inputs depending on access type.
- Marks uncertainty, confidence or source limitations where available.
- Feeds routing and PSAP display while preserving privacy controls.
Key interfaces and protocols
- PIDF-LO
- HELD
- SIP Geolocation
- AML delivery paths
- GIS and civic validation
Systems it interacts with
- LIS
- LVF
- ECRF
- PSAP GIS
- Mobile networks
- Enterprise systems
Common failure modes
- Stale enterprise location
- Indoor location too vague
- Conflicting civic and GPS data
- Missing location forces fallback route
Implementation considerations
- Separate source, representation and routing in documentation.
- Define how stale or low-confidence location is handled.
- Test office, factory, warehouse, campus and roaming cases.
Standards
- IETF RFC 4119
- IETF RFC 5985
- IETF RFC 6442
- ETSI TS 103 479
Related NG112 technologies
Relationship graph
Location chain: Emergency Location Chain <-> LIS <-> HELD <-> PIDF-LO <-> SIP Geolocation <-> Location-Based Routing
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- RFC 4119: A Presence-based GEOPRIV Location Object Format - IETF, accessed 2026-08-31
- RFC 5985: HTTP-Enabled Location Delivery - IETF, accessed 2026-08-31
- RFC 6442: Location Conveyance for SIP - IETF, accessed 2026-08-31
- RFC 5222: LoST: A Location-to-Service Translation Protocol - IETF, accessed 2026-08-31
- RFC 5031: A Uniform Resource Name for Emergency and Other Well-Known Services - IETF, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, accessed 2026-08-31
Last verified: 2026-08-31