112NG112.netNext generation emergency communications

NG112 reference

Esinet

Structured NG112 reference page.

112 readiness

Policy, location, routing, and response quality connected in one operational model.

Core NG112 Architecture

ESInet

Emergency Services IP Network

An ESInet is not the public internet. It is an engineered IP service environment with controlled interconnects, security boundaries, routing functions, monitoring, redundancy and operational governance. European implementations can be national, regional, federated or transitional, so the term should describe the function and assurance model rather than imply one identical deployment pattern.

ESInet is not simply the internet; it is a controlled emergency-services IP network with operational policy, security and availability requirements.
Originating network
->
NG112 interconnect
->
ESInet service functions
->
Selected PSAP

What it does

An Emergency Services IP Network is the managed emergency-services network that carries IP emergency sessions and related data between originating networks, routing functions and PSAPs.

The ESInet provides the trusted transport and service layer where emergency sessions can reach routing, validation, security and PSAP functions.

How it works

  • Carries SIP emergency sessions and associated data across a controlled emergency-services IP environment.
  • Hosts or reaches routing, validation, security and operational monitoring functions.
  • Supports redundancy and alternate routing so a single site or path failure does not strand emergency calls.

Key interfaces and protocols

  • SIP/SIP over TLS
  • IP routing and QoS
  • DNS/service discovery where used
  • Operational monitoring interfaces

Systems it interacts with

  • BCF
  • ESRP
  • ECRF
  • LVF
  • PSAP
  • Originating networks

Common failure modes

  • Loss of interconnect capacity
  • DNS or certificate failures
  • Misrouted traffic after policy change
  • Single-region dependency hidden inside a national architecture

Implementation considerations

  • Define national versus regional ownership clearly.
  • Test failover across real PSAP paths, not only lab proxies.
  • Document which functions are inside the ESInet and which remain in originating networks.

Standards

  • ETSI TS 103 479
  • ETSI TS 103 480
  • IETF emergency calling RFCs

Related NG112 technologies

Related country deployments

No country deployments are listed here until independently verified against official or high-confidence sources.

Related articles

Sources

Last verified: 2026-08-31

Advertisement