Study guide
3.1 NG911 Architecture: The ESInet & Core Services
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
3.1 NG911 Architecture: The ESInet & Core Services
Key Takeaways Explain This Topic AI
The Emergency Services IP Network (ESInet) is an engineered, private, multi-tenant IP transport infrastructure governed by NENA-STA-010 that securely interconnects originating service providers, core services, and PSAPs.
Next Generation Core Services (NGCS) comprise specialized software functional entities including the Emergency Service Routing Proxy (ESRP), Policy Routing Function (PRF), Emergency Call Routing Function (ECRF), Location Validation Function (LVF), and Location Information Server (LIS).
Strict Quality of Service (QoS) using Differentiated Services (DiffServ) prioritizes traffic: Expedited Forwarding (EF / DSCP 46) for emergency voice RTP, Assured Forwarding 31 (AF31 / DSCP 26) or CS3 (DSCP 24) for SIP signaling, and AF41 (DSCP 34) for real-time video.
Common voice-quality engineering targets for ESInet designs (drawn from ITU-T G.114 guidance and carrier SLAs rather than a NENA-mandated number) keep one-way mouth-to-ear delay under about 150 ms, jitter low enough for de-jitter buffers, packet loss well under 1%, and perceived quality near toll grade (MOS about 4.0).
Mission-critical public safety SLAs mandate 99.999% availability (maximum 5.26 minutes of unplanned downtime annually), dual-carrier transport with true physical route diversity, and a Mean Time to Repair (MTTR) under 4 hours.
Last updated: September 2026
3.1 NG911 Architecture: The ESInet & Core Services
Quick Answer: An Emergency Services IP Network (ESInet) is an engineered, private, managed IP transport backbone governed by NENA-STA-010. It carries emergency voice, video, text, and rich data among Originating Service Providers (OSPs), Next Generation Core Services (NGCS), and Public Safety Answering Points (PSAPs). Unlike the best-effort public Internet, an ESInet enforces strict Quality of Service (QoS) using DiffServ Expedited Forwarding (EF / DSCP 46) for audio media and Assured Forwarding (AF31 / DSCP 26) for SIP signaling. It guarantees 99.999% ("five nines") availability through physically diverse, dual-carrier transport architectures.
The Shift to Managed IP Transport
In legacy Enhanced 9-1-1 (E9-1-1) architectures, emergency calls traversed dedicated analog or time-division multiplexed (TDM) copper trunk lines, such as Centralized Automatic Message Accounting (CAMA) and Signalling System No. 7 (SS7) trunks, terminating at legacy selective routers. This architecture restricted communications to narrowband voice plus the caller's number (ANI), with location retrieved separately from the ALI database.
As described in NENA-STA-010 (NENA i3 Standard for Next Generation 9-1-1) and the design guidance in NENA-INF-016 (Emergency Services IP Network Design Information Document) , the Emergency Services IP Network (ESInet) fundamentally transforms public safety communications. The ESInet is an engineered, private, managed Multi-Protocol Label Switching (MPLS) or Carrier Ethernet IP network. Rather than serving as an isolated application, the ESInet acts as the shared, secure IP transport fabric upon which all Next Generation Core Services (NGCS) operate—including the Location Information Server (LIS), Emergency Call Routing Function (ECRF), Location Validation Function (LVF), and Emergency Service Routing Proxy (ESRP). +-------------------------------------------------------------------------+
- | EMERGENCY SERVICES IP NETWORK (ESInet) |
- | |
- | +-------------+ +--------------+ +---------------------+ |
- | | NGCS Core | <--> | Policy-Based | <--> | Location Services | |
- | | (ESRP/BCF) | | Routing (PRF)| | (ECRF / LVF / LIS) | |
- | +-------------+ +--------------+ +---------------------+ |
- | ^ ^ |
- +----------|----------------------------------------------|---------------+
- | (Secure Private Ingress) | (Private Interconnect)
- +----------v--------------+ +----------v--------------+
- | Originating Providers | | Primary & Backup PSAPs |
- | (Wireline, Wireless, IP)| | (Call-Handling / CAD) |
- +-------------------------+ +-------------------------+
Key characteristics of the ESInet include:
Inter-Agency Interoperability: Enables seamless interconnection between municipal, county, regional, state, and federal emergency entities.
Multi-Media Delivery: Concurrently transports high-definition audio, real-time interactive video, Real-Time Text (RTT), Computer Aided Dispatch (CAD) incident data, and rich Geographic Information Systems (GIS) spatial datasets.
Scalable Multicast and Unicast: Supports point-to-point emergency routing as well as broadcast incident dissemination to mutual-aid dispatch centers.
Next Generation Core Services (NGCS) Functional Architecture
Next Generation Core Services (NGCS) are the standardized software applications and functional elements hosted on the ESInet that process, validate, route, and log emergency sessions:
Emergency Service Routing Proxy (ESRP): The NG911 next-hop routing engine. The ESRP is an RFC 3261 SIP proxy server that evaluates incoming emergency calls, queries location and policy engines, and forwards calls to the appropriate destination (another ESRP or a PSAP).
Policy Routing Function (PRF): The software decision logic integrated with or queried by an ESRP. The PRF evaluates dynamic operational policies—such as time of day, console availability, queue depth, or emergency rollover conditions—to determine the final routing destination.
Emergency Call Routing Function (ECRF): An interactive spatial database service that accepts a caller's geographic coordinates (or validated civic address) and a Service URN ( urn:service:sos ), performing spatial point-in-polygon queries against authoritative GIS boundary layers to return the routable SIP URI of the serving PSAP.
Location Validation Function (LVF): A pre-call validation service that checks civic addresses against authoritative GIS road centerlines and address point layers before emergency calls are placed, ensuring that civic locations resolve deterministically during live emergencies.
Location Information Server (LIS): A functional entity located in the originating access network that stores subscriber geodetic or civic location and provides it to endpoints or core services via Presence Information Data Format Location Objects (PIDF-LO).
Forest Guide: A hierarchical routing infrastructure connecting regional and state ECRFs, enabling emergency calls to be routed to the correct destination even when the caller's location falls completely outside the local or regional ESInet boundary.
Discrepancy Reporting (DR): A standardized i3 function used to log, report, and track operational, GIS, or protocol discrepancies (e.g., location lookup failures or malformed SIP headers) between interconnecting NG911 entities.
Private Managed IP Transport vs. The Public Internet
NENA's ESInet design guidance strongly favors managed, private IP transport with engineered service levels over the unmanaged public Internet as the primary path for emergency call delivery. While consumer Over-The-Top (OTT) VoIP services operate over best-effort Internet connections, emergency services demand deterministic reliability.
- Architectural Attribute Private Managed ESInet Public Internet
- Packet Delivery Model Deterministic with bandwidth guarantees Best-effort (uncontrolled queuing)
Quality of Service (QoS) Strict hardware-enforced DiffServ / MPLS EXP Ignored or stripped across transit Autonomous Systems (AS)
Latency & Jitter Contractually bounded through carrier SLAs High variance, bufferbloat, unpredictable spikes
Availability SLAs 99.999% uptime with 2-to-4 hour Mean Time to Repair (MTTR) No availability or restoration guarantees
Security & Exposure Closed perimeter, private addressing, mTLS, BCF protection Exposed to global DDoS, scanning, BGP hijacking, spoofing
Operational Warning: Public Internet connections may only be used as a secondary, encrypted overlay (via IPsec VPN tunnels) during catastrophic failover scenarios or for non-mission-critical out-of-band administrative updates. Routing primary live emergency voice or video across the open Internet without managed service levels conflicts with NENA ESInet design guidance and adds avoidable reliability and security risk.
Layer 2 and Layer 3 Transport Options
Public safety agencies construct ESInets using several underlying Layer 2 and Layer 3 wide area network (WAN) transport technologies:
1. Multi-Protocol Label Switching (MPLS) Layer 3 VPNs
MPLS is the industry standard for regional and statewide ESInet deployments. MPLS allows network carriers to encapsulate IP packets with 32-bit labels, establishing Virtual Private Routed Networks (VPRNs). Key public safety advantages include:
Traffic Engineering (MPLS-TE): Pre-allocates deterministic paths through the provider core, preventing traffic congestion.
Fast Reroute (FRR): Provides sub-50-millisecond circuit failover if a primary fiber link is severed, ensuring live 9-1-1 audio does not drop.
Class of Service (CoS) Mapping: Maps IP Differentiated Services Code Point (DSCP) values directly to 3-bit MPLS Experimental (EXP) bits across the core.
2. Carrier Ethernet (E-Line, E-LAN, E-Tree)
Governed by the Metro Ethernet Forum (MEF), Carrier Ethernet delivers standardized Layer 2 Ethernet services across metro and regional scales:
Ethernet Private Line (E-Line / EVPL): Point-to-point dedicated bandwidth connecting a PSAP directly to an ESInet core data center.
Ethernet Private LAN (E-LAN): Multipoint-to-multipoint service connecting multiple PSAPs in a shared regional consortium.
Advantage: Lower protocol encapsulation overhead and native Layer 2 framing, though requiring upstream Layer 3 routing management.
3. Dark Fiber with Dense Wavelength Division Multiplexing (DWDM)
Municipalities or regional consortia that own or lease unlit optical fiber ("dark fiber") can deploy dedicated optical transceivers using Coarse or Dense Wavelength Division Multiplexing (CWDM/DWDM). By assigning dedicated optical wavelengths (lambdas) exclusively to public safety traffic, agencies achieve near-zero latency, multi-gigabit throughput, and complete physical layer isolation from commercial traffic.
4. IPsec VPN Tunnels (Overlay Transport)
When connecting remote secondary answering points or mobile incident command vehicles where dedicated fiber or MPLS circuits are economically or physically unfeasible, encrypted IPsec (Internet Protocol Security) tunnels serve as an overlay. However, IPsec incurs packet encapsulation overhead (typically 50-70 bytes per packet) and remains subject to the latency and packet loss fluctuations of the underlying broadband connection.
Quality of Service (QoS) & DiffServ DSCP Engineering
Because IP networks are packet-switched, multiple data flows compete for interface queue space. Without prioritization, large GIS shapefile transfers or CAD database synchronizations could monopolize buffer queues, causing emergency voice packets to be delayed or dropped.
NG911 networks enforce Differentiated Services (DiffServ - IETF RFC 2474 / RFC 2475) . Network routers classify, mark, and police packets at the ingress edge using the 6-bit Differentiated Services Code Point (DSCP) field within the IPv4 Type of Service (ToS) byte or IPv6 Traffic Class octet. IPv4 Header: [ Version (4b) | IHL (4b) | Type of Service / DSCP (6b) + ECN (2b) | Total Length (16b) ]
- \-----------------------/
- DSCP Bits 0-5 (0 to 63)
Typical ESInet QoS designs follow IETF DiffServ guidance (such as RFC 4594) to assign queuing priorities across traffic classes. The delay, jitter, and loss columns below are common engineering targets, not NENA-mandated values:
Traffic Class DSCP Name DSCP Value (Dec / Bin) Per-Hop Behavior (PHB) Target Packet Delay Target Jitter Target Loss
Emergency Voice RTP Expedited Forwarding (EF) 46 / 101110 Strict Priority Queuing (SPQ); preempts all other traffic < 50 ms < 10 ms < 0.1%
Emergency Video RTP Assured Forwarding (AF41) 34 / 100010 Low-latency weighted fair queuing (CBWFQ); rate policed < 80 ms < 15 ms < 0.5%
SIP Signaling / Call Control Assured Forwarding (AF31) or CS3 26 / 011010 (or 24 / 011000 ) High-priority guaranteed bandwidth; avoids tail-drop < 100 ms < 20 ms < 0.1%
Interactive CAD / GIS Data Assured Forwarding (AF21) 18 / 010010 Guaranteed transactional bandwidth; medium drop precedence < 200 ms < 50 ms < 1.0%
Administrative / Web Best Effort (BE) 0 / 000000 Default FIFO queuing; dropped first during congestion N/A N/A Variable
Expedited Forwarding (EF - DSCP 46)
EF provides a low-loss, low-latency, low-jitter end-to-end service. In hardware routers, EF traffic is placed into a Strict Priority Queue (SPQ) . As long as packets reside in the EF queue, the router services them before any other queue. To prevent a malicious or malfunctioning voice endpoint from starving other critical services, the ingress BCF applies policing and shaping to strictly limit EF traffic to its negotiated bandwidth ceiling.
Assured Forwarding (AF) and Call Signaling
SIP signaling packets (INVITE, 100 Trying, 180 Ringing, 200 OK) must not be dropped. Dropping an INVITE or ACK causes SIP retransmission timers to trigger (Timer A starts at 500 ms and doubles), introducing unacceptable call-setup delays. SIP signaling is marked with AF31 (DSCP 26) or Class Selector 3 (CS3 / DSCP 24) , guaranteeing bandwidth even when network links reach 100% saturation.
Network Performance Thresholds for Public Safety
To keep emergency voice intelligible, ESInet designers typically work to the following engineering targets, drawn from ITU-T Recommendation G.114 and carrier service-level agreements:
One-Way Latency (Delay): Keep mouth-to-ear delay under about 150 milliseconds (the ITU-T G.114 planning guideline), with network transit budgeted well below that. Delays exceeding 200 ms cause callers and call-takers to talk over one another.
Jitter (Delay Variation): Keep jitter low (designs commonly target under about 30 milliseconds ). Excessive jitter exceeds the capacity of the receiving device's de-jitter buffer, leading to buffer underruns and dropped audio frames.
Packet Loss: Keep loss well below 1% on voice streams. While VoIP concealment algorithms can reconstruct single lost packets, burst packet loss produces garbled speech and dropped syllables.
Mean Opinion Score (MOS): Aim for perceptual voice quality around a MOS of 4.0 (on a 1.0 to 5.0 scale), representing toll-quality audio.
- Bandwidth Sizing, Physical Diversity, and High Availability
- Bandwidth Engineering Calculations
Bandwidth dimensioning must accommodate peak concurrent busy-hour call volumes, multi-party conferencing, high-definition video, and CAD/GIS data spikes:
A standard uncompressed G.711 voice call generates 64 kbps of raw payload. When encapsulated with IP (20 bytes), UDP (8 bytes), RTP (12 bytes), and Layer 2 framing (18 bytes Ethernet) at a 20 ms packetization rate (50 packets per second), the actual consumed bandwidth is 87.2 kbps per concurrent call .
A two-way interactive video stream (H.264 at 720p/30fps) consumes 1.5 to 2.5 Mbps .
High-resolution GIS map layers, aerial orthophotography, and building floor plans pushed to CAD consoles require burst allocations of 10 to 50 Mbps .
Physical Route Diversity vs. Carrier Redundancy
A frequent operational pitfall in emergency communications procurement is confusing carrier diversity with physical route diversity . FLAWED ARCHITECTURE (Common Point of Failure):
- +-------------+ Carrier A (Contract 1) +-------------------+
- | ESInet / | ===========================> | Shared Underground| ===> [ PSAP ]
- | Data Center | Carrier B (Contract 2) | Conduit / Bridge |
- +-------------+ ===========================> +-------------------+
- ^
- [Severed by Backhoe!]
TRUE PHYSICALLY DIVERSE ARCHITECTURE (Zero Common Failure):
- +-------------+ ===== Carrier A (North Path / Aerial) =====> [ Demarc A ]
- | ESInet / | |
- | Data Center | ===== Carrier B (South Path / Buried Trench) => [ Demarc B ]
- +-------------+ |
- [ Dual-Homed CPE Routers ]
True high availability requires:
Diverse Rights-of-Way: Carrier circuits must travel along completely separate geographic paths (e.g., North entrance via buried trench along Highway 10; South entrance via aerial utility poles along 5th Street).
Entrance Facility Diversity: The PSAP facility must feature two physically separated building entry points (demarcation rooms) located on opposite exterior walls.
Dual-Homing & Hardware Redundancy: Edge routers must operate in active/standby or active/active pairs running Virtual Router Redundancy Protocol (VRRP) or Hot Standby Router Protocol (HSRP), peering over Border Gateway Protocol (BGP) with independent Autonomous System Numbers (ASNs).
Service Level Agreements (SLAs) & Operational Metrics
Public safety contracts with telecommunications carriers must mandate stringent, enforceable Service Level Agreements:
99.999% Availability ("Five Nines"): Total unplanned circuit unavailability across the core ESInet cannot exceed 5.26 minutes per calendar year . Unplanned Downtime = 365 days × 24 hours × 60 minutes × ( 1 − 0.99999 ) = 5.256 minutes/year \text{Unplanned Downtime} = 365 \text{ days} \times 24 \text{ hours} \times 60 \text{ minutes} \times (1 - 0.99999) = 5.256 \text{ minutes/year} Unplanned Downtime = 365 days × 24 hours × 60 minutes × ( 1 − 0.99999 ) = 5.256 minutes/year
Mean Time to Repair (MTTR): In the event of a catastrophic circuit failure, the carrier must contractually guarantee an MTTR of <= 2 to 4 hours , backed by 24/7/365 dedicated public safety dispatch technicians.
Continuous Performance Verification: The carrier must provide continuous, real-time proactive monitoring (via Synthetic Network Probes and SNMP/NetFlow monitoring) with automated alerting to the PSAP IT Director and state 9-1-1 authority upon any threshold breach.