Problem statement (privacy & compliance)
Connected cars behave like networked IoT devices: embedded SIMs continuously interact with mobile networks, making it technically possible to track vehicles, correlate VINs with IMEI/IMSI identifiers and reconstruct driving histories. At the same time, drivers expect strong privacy protection and strict limitation of surveillance, as highlighted by civil‑society concerns about function creep from lifesaving systems like eCall into broad vehicle tracking. Automotive OEMs therefore face a dual challenge: they must be able to support legitimate investigations and cross‑border requests, while minimizing data exposure, enforcing purpose limitation and ensuring full transparency and auditability.
ETSI TS 103 976 in automotive
ETSI TS 103 976 (V1.5.1, November 2025) specifies the interface between an Authorized Organization (AO), such as a law enforcement agency, and a Request Processing System (RPS) operated by an organization that holds vehicle‑related data, typically a vehicle manufacturer or mobility provider. It builds on the ETSI TS 103 120 messaging framework and mandates JSON encoding over HTTPS with TLS 1.3 and mutual X.509 authentication. The specification defines nine question types: VIN‑to‑CommsID and CommsID‑to‑VIN (IMEI, IMSI, MSISDN, MAC address), VIN‑to‑Location and VIN‑to‑Location‑Push, VIN‑to‑UniquePartNumber and UniquePartNumber‑to‑VIN, VIN‑to‑SubscribedServices, VIN‑to‑ConnectedDevices and VIN‑to‑AllocatedUserAccounts. Results can optionally be returned in ISO 20078 containers, and an informative annex addresses access to DSSAD data for automated driving. The interface is deliberately transactional, covering requests and responses rather than live voice or video streams, and must never compromise vehicle safety or security. The preceding study, ETSI TR 103 854, introduced the reference model and use cases that TS 103 976 now turns into a normative, testable interface, with security, audit and assurance requirements set out in its normative Annex A.

