Study guide
4.3 Location Validation Function (LVF) & Legacy Gateways
NENA Emergency Number Professional ENP
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the NENA ENP Exam
2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture
1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1
3 Chapter 2: Modern Location Technologies & MLTS
2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act
4 Chapter 3: NG911 i3 Core Network & Security
3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow
5 Chapter 4: NG911 Location Services & Call Routing
4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements
6 Chapter 5: Public Safety Radio, Broadband & FirstNet
5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services
7 Chapter 6: Call Processing, Accessibility & Protocol Systems
6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment
8 Chapter 7: Computer Aided Dispatch & Information Systems
7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents
9 Chapter 8: GIS for Next Generation 9-1-1
8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management
10 Chapter 9: Cybersecurity & CJIS Compliance
9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning
11 Chapter 10: Telecommunications Policy, Funding & Civil Rights
10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws
12 Chapter 11: PSAP Governance, Strategy & Facility Design
11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning
13 Chapter 12: Power Redundancy, COOP & Disaster Recovery
12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases
14 Chapter 13: Emergency Incident Management & NIMS/ICS
13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS
15 Chapter 14: Procurement, Contracts & Financial Management
14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management
16 Chapter 15: Staffing Models, Scheduling & Wellness
15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD
17 Chapter 16: Training, CTO Coaching & Quality Assurance
16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service
18 Chapter 17: Employee Relations, Labor Standards & Legal Protections
17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act
19 Chapter 18: Records Governance, Liability & Public Relations
18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach
20 Chapter 19: Recruiting, Hiring, Compensation & Retention
19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning
4.3 Location Validation Function (LVF) & Legacy Gateways
Key Takeaways Explain This Topic AI
The Location Validation Function (LVF) uses the LoST protocol to validate civic addresses against authoritative GIS layers prior to call origination, completely replacing legacy MSAG databases.
While the ECRF and LVF share identical GIS data layers and LoST interfaces, the LVF executes during service provisioning, whereas the ECRF routes live emergency calls in real time.
The Legacy Network Gateway (LNG) interfaces legacy TDM Central Offices and mobile MSCs with the ESInet, converting CAMA/SS7 signaling and legacy ALI dips into SIP INVITEs with Location by Value.
The Legacy PSAP Gateway (LPG) allows non-IP PSAPs to connect to the ESInet by converting SIP signaling into CAMA/ISDN PRI trunks and emulating a local ALI database for legacy console dips.
The Legacy Selective Router Gateway (LSRG) facilitates bi-directional inter-tandem routing between the ESInet and legacy E9-1-1 selective routers, supporting inter-agency transfers during migration.
Last updated: September 2026
4.3 Location Validation Function (LVF) & Legacy Gateways
Quick Answer: The Location Validation Function (LVF) is a core Next Generation Core Services (NGCS) functional entity that validates civic addresses prior to call origination (during service provisioning) using the identical LoST protocol (RFC 5222) and authoritative GIS layers as the ECRF, completely replacing the legacy Master Street Address Guide (MSAG). During the phased migration from legacy E9-1-1 to full NG911, three transitional gateways maintain backward compatibility: the Legacy Network Gateway (LNG) interfaces legacy originating TDM/wireless networks to the ESInet; the Legacy PSAP Gateway (LPG) converts ESInet SIP sessions into CAMA/PRI signaling and emulates an ALI database for legacy call-taking consoles; and the Legacy Selective Router Gateway (LSRG) enables bi-directional inter-tandem trunking and call transfers between the ESInet and legacy E9-1-1 selective routers.
The Location Validation Function (LVF) Architectural Role
In legacy 9-1-1, telecommunications carriers validated customer service addresses against a static, tabular Master Street Address Guide (MSAG) maintained by the incumbent local exchange carrier (ILEC). If a subscriber's address contained a slight spelling discrepancy, directional error, or fell outside a provisioned street range, service provisioning halted. MSAG updates required cumbersome 24- to 72-hour batch file exchanges across multiple carrier boundaries.
In Next Generation 9-1-1, the Location Validation Function (LVF) completely replaces the legacy MSAG. The LVF is a specialized validation service hosted on the ESInet that allows Originating Service Providers (OSPs)—including wireline telcos, broadband ISPs, and interconnected VoIP providers—to verify that a customer's civic address is valid and spatially routable prior to service activation .
Core Differences: LVF vs. ECRF
Although the LVF and the Emergency Call Routing Function (ECRF) utilize the exact same LoST protocol (RFC 5222) and query the exact same GIS spatial database , their operational timing and objectives are fundamentally distinct:
Operational Dimension Location Validation Function (LVF) Emergency Call Routing Function (ECRF)
Operational Timing Pre-call validation ; executed days, weeks, or months before an emergency call is dialed Real-time call processing ; executed during active emergency call setup (< 100 ms)
Querying Client Originating Service Provider (OSP) billing and provisioning systems, enterprise MLTS admins Emergency Service Routing Proxies (ESRP), Border Control Functions (BCF), or IP endpoints
Target Input Data Structured civic addresses (RFC 5139 CAtypes) Civic addresses OR geodetic coordinates (lat/long) in a PIDF-LO payload
Operational Outcome Returns validation status ( Valid , Invalid , or Ambiguous ) and matched civic elements Returns the routable SIP URI of the destination PSAP and a <serviceBoundary> polygon
System Failure Impact Service provisioning order is delayed pending address remediation with local GIS Call routing failure forces ESRP into default routing to prevent dropped emergency calls PRE-CALL SERVICE PROVISIONING (LVF):
[ Customer Orders VoIP Service ] ──► [ Carrier Provisioning ] ── LoST Query ──► [ LVF Engine ] ◄── [ GIS Layers ]
- │
- [ Status: Valid / Invalid / Ambiguous ] ◄─────┘
REAL-TIME EMERGENCY CALL PROCESSING (ECRF):
[ Citizen Dials 9-1-1 ] ──► [ SIP INVITE ] ──► [ ESRP Ingress ] ── LoST Query ──► [ ECRF Engine ] ◄── [ GIS Layers ]
- │
- [ Destination PSAP SIP URI Returned ] ◄───────┘
- The Spatial Interface (SI) & GIS Data Synchronization
How do the LVF and ECRF maintain absolute data integrity? Under NENA-STA-010, local municipal and county GIS authorities do not manually edit the ECRF/LVF directly. Instead, they publish spatial updates through the Spatial Interface (SI) .
Required GIS Layers Provisioned via the Spatial Interface (NENA-STA-006):
Site/Structure Address Points (SSAPs): Highly accurate spatial point locations representing individual building footprints, primary access points, and sub-units.
Road Centerlines: Vector line layers containing street names, address number ranges (left/right parity), and administrative boundary tags.
PSAP Boundary Polygons: Polygons delineating the primary geographic jurisdiction of every answering center.
Emergency Service Boundaries (ESBs): Independent polygon layers defining response districts for law enforcement, fire/rescue, and emergency medical services (EMS).
Provisioning Boundary: Polygons defining the area for which each GIS data provider is authoritative, so the Spatial Interface accepts a provider's features only inside its boundary.
NENA Quality Guidance: NENA's GIS-MSAG-ALI synchronization guidance (NENA 71-501) recommends reaching at least a 98% match rate before relying on GIS data for ECRF and LVF services, and many state programs set stricter targets. Because the LVF and ECRF are provisioned from the same GIS layers, an address that validates should route correctly, but boundary errors can still misroute calls, so discrepancy reporting remains essential.
Transitional Migration Architecture in NG911
The migration from legacy E9-1-1 to Next Generation 9-1-1 is a complex, multi-year evolutionary process. Public safety agencies cannot execute a simultaneous nationwide "flash cut." Consequently, NENA i3 specifications define three specialized transitional gateways to bridge legacy TDM networks with the IP-based ESInet: +---------------------------------------------------------------------------------------------------+
- | TRANSITIONAL GATEWAY ARCHITECTURE |
- | |
- | [ Legacy Carrier Network ] [ Legacy PSAP CPE ] |
- | (Wireline CO / Mobile MSC) (Non-IP Call Consoles) |
- | │ ▲ |
- | │ CAMA MF / SS7 ISUP Trunks │ CAMA / PRI |
- | ▼ │ (Serial ALI) |
- | +---------------+ SIP INVITE (LbyV) +-------------------+ │ |
- | | Legacy Network| --------------------------> | | +---------------+ |
- | | Gateway (LNG) | | EMERGENCY | ──> | Legacy PSAP | ──────┘ |
- | +---------------+ | SERVICES IP | | Gateway (LPG) | |
- | │ Queries | NETWORK | +---------------+ |
- | ▼ (Legacy ALI) | (ESInet) | |
- | [ Legacy ALI ] | | |
- | +-------------------+ |
- | ▲ |
- | Bi-directional │ SIP / CAMA Trunking |
- | ▼ |
- | +-------------------+ |
- | | Legacy Selective | |
- | | Router Gateway | |
- | | (LSRG) | |
- | +-------------------+ |
- | │ |
- | ▼ CAMA / SS7 Inter-Tandem Trunks |
- | [ Legacy Selective ] |
- | [ Router Switch ] |
- +---------------------------------------------------------------------------------------------------+
- 1. Legacy Network Gateway (LNG)
The Legacy Network Gateway (LNG) is deployed at the ingress perimeter of the ESInet facing legacy Originating Service Providers. It acts as the bridge connecting legacy Central Offices (COs) and wireless Mobile Switching Centers (MSCs) to the modern NGCS core.
Core Engineering Functions of the LNG:
Signaling Ingress Conversion: Receives legacy TDM trunk signaling—including Centralized Automatic Message Accounting (CAMA) multi-frequency (MF) tones and SS7 ISDN User Part (ISUP) call setup messages.
Location Discovery & Extraction: In legacy networks, location is not delivered in the voice path. The LNG extracts the caller's 10-digit telephone number (ANI) or wireless pseudo-ANI (pANI / ESRK / ESRD) and initiates an out-of-band location lookup to the legacy ALI database (or the wireless MPC/GMLC) using standardized interfaces such as E2.
PIDF-LO Construction: The LNG converts the tabular ALI record or geodetic coordinate into an RFC 4119 / RFC 5139 compliant PIDF-LO XML document.
SIP Session Generation: The LNG constructs an RFC 3261 SIP INVITE addressed to urn:service:sos , embeds the newly created PIDF-LO as Location by Value (LbyV) in a multipart MIME body, and transmits the call across the Border Control Function (BCF) into the ESInet.
2. Legacy PSAP Gateway (LPG)
The Legacy PSAP Gateway (LPG) is deployed at the egress perimeter of the ESInet facing an answering center that has not yet upgraded its Call Handling Equipment (CHE) to native NENA i3 SIP capabilities.
Core Engineering Functions of the LPG:
SIP-to-TDM Signaling Conversion: Receives native SIP INVITE requests from the ESInet (via the BCF) and converts them into legacy analog CAMA MF trunk signaling or ISDN Primary Rate Interface (PRI) signaling compatible with legacy PSAP PBX hardware.
Voice Media Decoding: Decodes IP-based RTP media streams (G.711 mu-law) and outputs standard 64 kbps DS0 analog/TDM voice channels.
Emulated ALI Database: Because legacy call-taking consoles cannot parse SIP signaling or XML PIDF-LO documents, the LPG operates as an emulated local ALI database :
When an incoming call arrives, the LPG extracts the PIDF-LO from the SIP INVITE and populates an internal temporary cache indexed by the caller's ANI.
When the legacy call-taker console answers the trunk, it automatically initiates an out-of-band ALI dip over an RS-232 serial connection or point-to-point IP link.
The LPG intercepts the serial dip, formats the cached PIDF-LO data into a NENA-format tabular ALI record the legacy console already understands, and returns it to the console screen.
3. Legacy Selective Router Gateway (LSRG)
The Legacy Selective Router Gateway (LSRG) provides bi-directional inter-tandem trunking between an ESInet and an incumbent legacy E9-1-1 Selective Router (SR). The LSRG is indispensable during phased regional cutovers, allowing calls to be transferred seamlessly between modernized NG911 PSAPs and legacy PSAPs.
Two Primary Operational Use Cases of the LSRG:
Use Case A: ESInet to Legacy Selective Router (NG911 PSAP -> Legacy PSAP Transfer)
An NG911 PSAP receives a call that belongs to an adjacent rural jurisdiction whose PSAP still operates on a legacy selective router:
The NG911 telecommunicator initiates a transfer in CAD/CHE.
The ESInet ESRP routes the SIP INVITE to the LSRG.
The LSRG converts the SIP session into dedicated CAMA or SS7 inter-tandem trunks connecting to the legacy Selective Router.
The LSRG maps the call to a pseudo-ANI or legacy Emergency Service Number (ESN) recognized by the selective router, ensuring the selective router directs the call to the appropriate legacy PSAP.
Use Case B: Legacy Selective Router to ESInet (Legacy PSAP -> NG911 PSAP Transfer)
A legacy Central Office or legacy selective router receives a call that must be routed to a modernized PSAP operating on the ESInet:
The legacy selective router forwards the call across inter-tandem trunks to the LSRG.
The LSRG extracts the calling digits, performs a location dip to acquire tabular ALI data, and converts the information into a PIDF-LO.
The LSRG issues an RFC 3261 SIP INVITE with urn:service:sos and embedded PIDF-LO into the ESInet, where the ESRP and ECRF take over routing.
Summary of Transitional Gateway Functions
Gateway Element Network Position Input Signaling / Protocol Output Signaling / Protocol Primary Public Safety Mission
Legacy Network Gateway (LNG) ESInet Ingress CAMA MF / SS7 ISUP + Legacy ALI dip SIP INVITE (RFC 3261) + PIDF-LO (LbyV) Enables legacy wireline COs and wireless MSCs to deliver 9-1-1 calls into an ESInet
Legacy PSAP Gateway (LPG) ESInet Egress SIP INVITE + PIDF-LO XML CAMA MF / ISDN PRI + Emulated Serial ALI Enables older non-IP PSAP consoles to receive ESInet calls and display tabular ALI
Legacy Selective Router Gateway (LSRG) ESInet Boundary Bi-directional: SIP / CAMA / SS7 Bi-directional: CAMA / SS7 / SIP Enables inter-tandem trunking and two-way call transfers between ESInets and legacy Selective Routers