NG112 reference
Ecrf
Structured NG112 reference page.

112 readiness
Policy, location, routing, and response quality connected in one operational model.
Core NG112 Architecture
ECRF
Emergency Call Routing Function
An ECRF is about location-based service routing, not simply telephone-number lookup. It depends on authoritative service boundaries, geospatial data quality and policy about ambiguous or missing location. In some architectures the protocol expression resembles LoST; in others, the same conceptual function may be implemented behind national interfaces.
What it does
An ECRF maps a caller location and requested emergency service to routing information for the appropriate emergency destination.
The ECRF helps the routing layer determine which PSAP or emergency service URI should receive a session.
How it works
- Receives location and service context from a routing element.
- Matches the location to emergency service boundaries.
- Returns routing information or a route decision used by the ESRP.
Key interfaces and protocols
- LoST concepts
- GIS/service boundary data
- SIP routing policy
- Administrative provisioning
Systems it interacts with
- ESRP
- GIS
- LVF
- PSAP boundary data
- National routing databases
Common failure modes
- Out-of-date service boundaries
- Postal address accepted but not routable
- Border-area ambiguity
- Conflicting civic and geodetic location
Implementation considerations
- Treat GIS data as operational infrastructure.
- Version service boundaries and test edge cases.
- Document how emergency service subtypes are routed.
Standards
- IETF RFC 5222
- IETF RFC 5031
- ETSI TS 103 479
Related NG112 technologies
Relationship graph
Routing chain: ESRP <-> ECRF <-> LoST <-> PSAP Technology <-> ESInet
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- 112: the European emergency number - European Commission, accessed 2026-08-31
- Directive (EU) 2018/1972 establishing the European Electronic Communications Code - European Union, accessed 2026-08-31
- Emergency communications - BEREC, accessed 2026-08-31
- Next Generation 112 and the new Emergency Services Networks Landscape - EENA, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, 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
Last verified: 2026-08-31