NG112 reference
Lvf
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Core NG112 Architecture
LVF
Location Validation Function
Location validation is a data-quality control. It does not determine where a device is right now and it does not route the live call by itself. It confirms that an address, floor, room, building identifier or other civic structure is recognizable against authoritative emergency location data before that record is relied on operationally.
What it does
An LVF checks whether civic location data is valid enough to be used for emergency communications.
The LVF improves confidence that civic location records can be used by location servers, routing functions and PSAPs.
How it works
- Compares submitted civic fields against authoritative data.
- Rejects, normalizes or flags records that cannot be matched.
- Feeds provisioning workflows for location databases and routing systems.
Key interfaces and protocols
- Civic address schemas
- GIS/address databases
- Provisioning APIs
- Audit and lifecycle controls
Systems it interacts with
- LIS
- ECRF
- GIS
- Enterprise location management
- PSAP mapping systems
Common failure modes
- Postal address differs from emergency-service address.
- Floor or suite is missing for large buildings.
- Address database updates do not reach emergency systems.
- Validation rules are weaker than dispatch needs.
Implementation considerations
- Validate before deployment, not after an incident.
- Build exception queues for facilities that need manual review.
- Retest after campus moves, renovations and network changes.
Standards
- ETSI TS 103 479
- IETF civic location work
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 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