NG112 reference
Lis
Structured NG112 reference page.
112 readiness
Policy, location, routing, and response quality connected in one operational model.
Location
LIS
Location Information Server
A LIS may map a device, IP subnet, Wi-Fi access point, switch, switch port, civic address assignment or other access-network clue to emergency location. In enterprises, the LIS is only as good as the data governance behind moves, adds, changes, remote work and facility records.
What it does
A Location Information Server provides location information based on endpoint, network or access context.
The LIS is a source of emergency location that can feed HELD, SIP signaling, routing and PSAP display.
How it works
- Stores or retrieves mappings between access-network context and emergency location.
- Returns location to clients or network elements.
- Supports lifecycle changes as facilities and networks evolve.
Key interfaces and protocols
- HELD
- Provisioning APIs
- Civic address validation
- Network inventory
Systems it interacts with
- HELD clients
- LVF
- Enterprise UC
- Wi-Fi controllers
- Switch inventory
- ECRF where routed by location
Common failure modes
- Network redesign not reflected in location records.
- Shared Wi-Fi maps to a lobby for an entire building.
- Warehouse zones are too large for responders.
- Data owner is unclear during an audit.
Implementation considerations
- Assign owners for every location data source.
- Model campuses, floors, wings and industrial zones explicitly.
- Treat location data as safety-critical configuration.
Standards
- IETF RFC 5985
- IETF RFC 4119
- 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