NG112 reference
Location Based Routing
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Location-Based Routing
Location-Based Routing
Location-based routing is the heart of next-generation emergency communications. It must handle civic and geodetic location, ambiguous boundaries, missing or stale data, service-specific routing, fallback and operational overrides. It is not a simple mapping from telephone number to PSAP.
What it does
Location-based routing selects the emergency destination using where the caller is and what emergency service is requested.
It helps send the session to the PSAP or emergency service responsible for the caller location.
How it works
- Receives location and emergency service context.
- Matches that location to authoritative service boundaries.
- Applies policy for ambiguity, outages, media support or missing information.
Key interfaces and protocols
- ECRF/LoST concepts
- ESRP
- GIS boundaries
- SIP routing
Systems it interacts with
- Location
- ECRF
- ESRP
- PSAP
- GIS
- Policy routing
Common failure modes
- Stale location sends caller to wrong PSAP.
- Boundary edge cases route unpredictably.
- No fallback route for missing location.
- Voice route and data route disagree.
Implementation considerations
- Test with known points near jurisdiction boundaries.
- Maintain authoritative GIS change control.
- Record why each route was selected during validation.
Standards
- IETF RFC 5222
- ETSI TS 103 479
- ETSI TS 103 480
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
- ETSI TS 103 480 deliverable directory - ETSI, accessed 2026-08-31
Last verified: 2026-08-31