IVS

In-Vehicle System

IoT
Introduced in Rel-7
The In-Vehicle System is the terminal and associated sub-systems installed in a vehicle to support the eCall emergency service. It enables automatic or manual initiation of an emergency call, transmitting critical data like vehicle location to a Public Safety Answering Point (PSAP). This system is fundamental for road safety and mandated in many regions.

Description

The In-Vehicle System (IVS) is a comprehensive vehicular terminal defined by 3GPP to support the Pan-European eCall in-vehicle emergency service and its derivatives. It is the physical and logical entity embedded within a vehicle, responsible for detecting a severe accident (via sensors like airbag deployment or crash sensors) or allowing manual trigger by occupants. Upon activation, the IVS establishes a circuit-switched voice call to the nearest Public Safety Answering Point (PSAP) via the cellular network. Crucially, it also transmits a Minimum Set of Data (MSD), a standardized data packet containing vital information such as the vehicle's precise location (from GNSS), vehicle identification number (VIN), type of fuel, number of passengers, and the time of the incident. This MSD is sent either in-band as a modem signal during the call setup phase (using in-band modem tones) or out-of-band using SMS or packet data, depending on the network capabilities and regional implementation.

Architecturally, the IVS integrates several key components: a cellular modem (supporting 2G, 3G, or 4G for the initial eCall), a Global Navigation Satellite System (GNSS) receiver for positioning, an accelerometer or crash sensor interface, a microphone and speaker for voice communication, and a control unit that manages the entire emergency call procedure. The system must be resilient, often featuring a backup battery to ensure operation even if the vehicle's main power is cut. Its operation is highly automated; upon a severe crash detection, it initiates the call sequence without requiring human intervention, though it typically includes a manual override or cancel button for occupants.

Within the broader eCall ecosystem, the IVS interfaces with the cellular Mobile Network (e.g., GSM/UMTS/LTE), which routes the emergency call and data to the appropriate PSAP. The IVS's role is strictly defined as the vehicle-side endpoint. The standardization of the IVS and the MSD format ensures interoperability across different vehicle manufacturers, cellular networks, and PSAP systems throughout Europe and other adopting regions, creating a seamless, automated emergency response mechanism that significantly reduces the time for help to arrive at an accident scene.

Purpose & Motivation

The IVS was created to address the critical problem of delayed emergency response times following road traffic accidents, which are a leading cause of death and serious injury globally. Prior to eCall and the standardized IVS, emergency calls relied solely on occupants being conscious and able to communicate their location, which is often impossible in severe crashes. This led to significant delays in locating the accident site and dispatching appropriate emergency services. The primary motivation was to automate the emergency notification process, ensuring that help is summoned immediately and with precise location data, thereby saving lives and reducing the severity of injuries.

The development of the IVS was driven by a European Union initiative, culminating in a mandate for all new vehicle types in the EU to be equipped with the technology. 3GPP standardized the IVS to leverage existing, ubiquitous cellular networks as the communication bearer, avoiding the need for a separate, dedicated emergency radio network. This approach provided wide-area coverage and reliability. The IVS solves the limitations of previous ad-hoc or proprietary vehicle emergency systems by creating a single, pan-European standard. This ensures that any eCall-equipped vehicle can connect to any PSAP in any member state, overcoming interoperability barriers that would exist with multiple, incompatible manufacturer-specific systems.

Key Features

  • Automatic crash detection and trigger via integrated vehicle sensors
  • Manual emergency call initiation via a dedicated button
  • Transmission of the standardized Minimum Set of Data (MSD)
  • Integration of GNSS for accurate vehicle location reporting
  • Resilient design with backup power supply
  • Support for in-band modem and out-of-band (SMS/data) MSD transmission

Evolution Across Releases

Rel-7 Initial

Introduced the foundational architecture for the In-Vehicle System as part of the initial Pan-European eCall standardization. Defined the core capabilities: automatic/manual trigger, establishment of a circuit-switched voice call to a PSAP, and the transmission of the Minimum Set of Data (MSD) using an in-band modem over the voice channel. Specified the basic MSD content and the call control procedures.

Enhanced eCall to support Next Generation (NG) eCall over IP-based networks (LTE). Introduced support for packet-switched data transport for the MSD, moving beyond reliance on circuit-switched voice and in-band modem. This allowed for faster, more reliable data transmission and paved the way for future enriched data capabilities.

Further evolved NG eCall, including support for the IP Multimedia Subsystem (IMS) and Session Initiation Protocol (SIP) for call establishment. Introduced the concept of "eCall only mode" for devices without a UICC, ensuring basic emergency service availability. Worked on alignment with broader MCPTT (Mission Critical Push-To-Talk) services.

Continued enhancements for NG eCall operation in 5GS (5G System). Focused on ensuring reliable eCall service delivery over 5G networks, including support for Voice over New Radio (VoNR) and emergency service fallback procedures. Addressed service continuity and regulatory requirements in the 5G context.

Ongoing maintenance, testing, and refinement of eCall and NG eCall specifications. Work includes updates for security, testing procedures (e.g., conformance testing for IVS in TS 26.267 series), and ensuring interoperability with evolving network architectures like 5G-Advanced and V2X (Vehicle-to-Everything) ecosystems.

Defining Specifications

SpecificationTitle
TS 22.101 3GPP TS 22.101
TS 22.967 3GPP TS 22.967
TS 26.267 3GPP TS 26.267
TS 26.268 3GPP TS 26.268
TS 26.269 3GPP TS 26.269
TS 26.967 3GPP TS 26.967
TS 26.969 3GPP TS 26.969