BS EN 16102-2011 PDF

Full title and description

STB BS EN 16102-2011 — Intelligent transport systems — eCall — Operating requirements for third party support. This European Standard (published as EN 16102:2011 and adopted nationally under designations such as BS EN 16102:2011 and STB BS EN 16102-2011) specifies requirements and procedures for in‑vehicle eCall functionality delivered via Third Party Service Providers (TPSP), and for the transfer of emergency messages (including the Minimum Set of Data) from vehicle to emergency authorities (PSAPs) via TPSPs.

Abstract

EN 16102:2011 defines the general operating requirements, high‑level functional requirements, data handling and service provisions for TPSP‑based eCall services. It covers transmission aspects from the vehicle, TPS in‑vehicle system requirements, TPSP responsibilities, transmission to PSAPs, test and conformance provisions, and marking/packaging requirements; annexes provide a standardised data interface and examples for additional information. The standard references the common European Minimum Set of Data (MSD) (see EN 15722) while leaving the precise MSD format to the MSD standard.

General information

• Status: Confirmed / Active in national adoptions (listed as BS EN 16102:2011 / STB BS EN 16102-2011 in catalogues and national registers).
• Publication date: EN original: December 2011 (EN 16102:2011); published as BS EN 16102:2011 (national adoption) in early 2012 (BS listing Feb 29, 2012).
• Publisher: Comité Européen de Normalisation (CEN); adopted/published nationally by organizations such as BSI (as BS EN 16102:2011) and by national standards bodies (STB adoption indicated in national catalogues).
• ICS / categories: 35.240.60 (IT applications in transport / Intelligent transport systems).
• Edition / version: 2011 (EN 16102:2011; national adoptions use the 2011 designation).
• Number of pages: Approximately 53 pages (typical published EN document length; some national catalogues list between 53–58 pages depending on cover/foreword).

Scope

This standard specifies the operating requirements and intrinsic procedures for providing an in‑vehicle eCall via services of a Third Party Service Provider (TPSP). It covers the transfer of an emergency message from vehicle to TPSP, the onward transfer (where required) from TPSP to the most appropriate Public Safety Answering Point (PSAP), and the actions and interfaces needed to establish voice contact and deliver the Minimum Set of Data to emergency services. Communications protocols and exact MSD content formats are referenced to other standards (for example EN 15722) and are not fully redefined in EN 16102.

Key topics and requirements

• High‑level functional requirements for TPSP‑based eCall services (service objectives, performance expectations, emergency handling workflows).
• Transmission from vehicle aspects — triggering, communication session establishment, voice channel initiation and handover considerations.
• Data requirements — handling and forwarding of the Minimum Set of Data (MSD) and optional additional data elements; recommendations for registering additional data concepts.
• TPS in‑vehicle system requirements — equipment behaviour, indications to vehicle occupants, reliability and availability expectations.
• Service provider (TPSP) responsibilities — receiving eCall, validating and forwarding emergency data to PSAPs, escalation and follow‑up procedures.
• Transmission to PSAPs — selection of appropriate PSAP, data interface formats (annexed standardized interface), and efforts to establish direct voice contact where required.
• Test, conformance and interoperability requirements — conformance testing, marking, labelling and packaging for compliant TPSP/vehicle solutions.
• Normative annex: standardized TPSP–PSAP data interface; informative annexes: transitional arrangements and XML examples for additional information.

Typical use and users

Primary users include vehicle manufacturers and telematics OEMs, Third Party Service Providers (TPSPs) that implement and operate eCall services, emergency services/PSAP integrators, telematics software and hardware suppliers, conformity assessment bodies, and national regulators implementing eCall‑related policy. The standard is used when designing, testing and certifying TPSP eCall solutions and when integrating TPSP services with PSAP infrastructure.

Related standards

EN 15722 — eCall Minimum Set of Data (MSD) (defines the common MSD elements referenced by EN 16102); EN 16072 / EN 16062 series — pan‑European eCall high‑level and operating requirements; CEN technical specifications such as CEN/TS 17182 and other eCall ITS specifications (communications, ITS station interfaces, ASN.1/PER encodings and XML schemas) referenced for interoperability and data registration. These companion documents define the MSD format, high‑level application protocols, and ITS‑station considerations that interoperate with the TPSP model in EN 16102.

Keywords

eCall, TPSP, Third Party Service Provider, eCall operating requirements, Minimum Set of Data (MSD), PSAP, in‑vehicle emergency call, intelligent transport systems, telematics, conformity, data interface.

FAQ

Q: What is this standard?

A: EN 16102:2011 (adopted as national designations such as BS EN 16102:2011 and STB BS EN 16102-2011) is a European Standard that specifies operating requirements for providing in‑vehicle eCall services via Third Party Service Providers.

Q: What does it cover?

A: It covers high‑level functional requirements, data handling (including forwarding the Minimum Set of Data), TPSP and in‑vehicle system requirements, transmission to PSAPs, testing and conformance, and annexed data interface specifications. Communications protocol specifics and MSD format references are handled by companion standards such as EN 15722.

Q: Who typically uses it?

A: Vehicle manufacturers, telematics and eCall service providers (TPSPs), emergency services/PSAP integrators, telematics hardware/software vendors, test laboratories and national standards bodies.

Q: Is it current or superseded?

A: EN 16102:2011 is the 2011 edition and is listed in national catalogues (BS adoption and STB/BDS adoptions) as a confirmed/adopted document. Users should verify with their national standards body for the absolute latest national status or any subsequent amendments or superseding deliverables.

Q: Is it part of a series?

A: Yes — EN 16102 is part of the wider eCall family of ITS/eSafety standards. It should be used alongside EN 15722 (MSD), EN 16072/EN 16062 (pan‑European eCall operating and HLAP requirements) and related CEN/TS documents covering ITS station interfaces and optional data sets.

Q: What are the key keywords?

A: eCall; Third Party Service Provider (TPSP); Minimum Set of Data (MSD); PSAP; intelligent transport systems; telematics; emergency call; operating requirements; conformity.