112NG112.netNext generation emergency communications

NG112 reference

Ecall

Structured NG112 reference page.

112 readiness

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

eCall and NG eCall

eCall

eCall is not NG112. It is a vehicle emergency service using 112 access. It matters to NG112 because vehicle-originated data and future NG eCall evolution intersect with PSAP readiness, mobile networks and emergency data handling.

eCall is not NG112, even though both are part of the European emergency communications ecosystem.
Vehicle incident/manual trigger
->
112 eCall
->
Minimum Set of Data
->
PSAP

What it does

eCall is vehicle-originated emergency calling to 112, carrying voice and a Minimum Set of Data from the vehicle.

eCall is an adjacent 112 service that PSAPs and networks must account for in modernization plans.

How it works

  • The in-vehicle system initiates an emergency call manually or automatically.
  • A data payload supplies vehicle and incident context.
  • The PSAP handles the voice call and associated vehicle data.

Key interfaces and protocols

  • In-vehicle system
  • Mobile emergency access
  • MSD
  • PSAP eCall handling

Systems it interacts with

  • eCall MSD
  • NG eCall
  • Mobile location
  • PSAP
  • Recording

Common failure modes

  • Vehicle data is not displayed to call taker.
  • Voice works but data path fails.
  • 2G/3G retirement affects legacy assumptions.
  • PSAP workflow treats eCall like ordinary voice only.

Implementation considerations

  • Separate eCall readiness from NG112 readiness.
  • Plan PSAP training and data display.
  • Track mobile network sunset dependencies.

Standards

  • European eCall framework
  • ETSI NG eCall Plugtests references

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