NG112 reference
Policy Routing
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Location-Based Routing
Policy Routing
Location is central, but policy decides what to do with unavailable PSAPs, ambiguous boundaries, media-specific capability, language support, incident load and test traffic. The safest designs make those choices explicit and auditable.
What it does
Policy routing applies operational rules to emergency session routing beyond the simple fact of where the caller is located.
Policy routing turns routing data into operational behavior under normal, degraded and exceptional conditions.
How it works
- Evaluates service type, location, PSAP availability and national rules.
- Selects primary and alternate routing targets.
- Logs the decision path for troubleshooting and audit.
Key interfaces and protocols
- ESRP policy data
- ECRF results
- PSAP status inputs
- Operational procedures
Systems it interacts with
- ESRP
- ECRF
- PSAP
- Resilience planning
- Testing
Common failure modes
- Undocumented fallback sends calls to a generic queue.
- Policy and GIS boundaries diverge.
- Media-capability routing is not tested.
- Test calls follow a different route than real incidents.
Implementation considerations
- Put fallback rules in writing.
- Retest policy after boundary or PSAP changes.
- Use controlled test numbers and scenarios where available.
Standards
- ETSI TS 103 479
- ETSI TS 103 480
Related NG112 technologies
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- ETSI TS 103 480 deliverable directory - ETSI, accessed 2026-08-31
- 5th NG112 Plugtests Report - ETSI, accessed 2026-08-31
- 6th NG112 and NG eCall Plugtests Report - ETSI, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, accessed 2026-08-31
Last verified: 2026-08-31