Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD CEN ISO TS 18234 — Intelligent Transport Systems Traffic and Travel Information TPEG1 Binary Data Format Standard Series
Intelligent Transport Systems — Traffic and Travel Information via TPEG1 Binary Data Format (2013 Series, UK implementation of CEN ISO/TS 18234)
🚗 PD CEN ISO/TS 18234 is the series of British Standards Institution (BSI) Published Documents implementing CEN ISO/TS 18234. The series specifies how traffic and travel information (TTI) is carried using the generation-1 binary data format of the Transport Protocol Experts Group (TPEG1). TPEG was developed jointly by CEN/TC 278 (Intelligent transport systems) and ISO/TC 204; UK participation was entrusted to Technical Committee EPL/278, with ICS classifications 03.220.01 and 35.240.60. The seven parts cover introduction, numbering and versions, data applications, location referencing and conditional access — a landmark data format for in-car navigation, roadside broadcasting and mobile mobility applications.
💡 Why TPEG1 emerged: early traffic information relied on RDS-TMC (FM subcarrier traffic coding), which had limited bandwidth and low carrying capacity. TPEG1 uses an application-oriented binary data format design that carries richer traffic events, congestion forecasts and location information, and can be distributed over DAB (digital audio broadcasting), the Internet and other channels.
1. Background and Design Goals 📌
Traffic and travel information needs a language-neutral, application-neutral and extensible data encoding so that it can be delivered consistently across countries, distribution networks and terminal devices. The TPEG1 format in CEN ISO/TS 18234 is built on a layered design of “application messages + common containers”: each application (road traffic events, weather, public transport information, etc.) defines its own message structure, while common parts such as location referencing and timing are carried by shared container specifications, ensuring flexibility and interoperability.
The “PD” in the filenames denotes a Published Document — BSI’s UK implementation of a CEN Technical Specification (CEN/TS). A CEN/TS is initially valid for three years, after which CEN members evaluate whether it should be converted into a European Standard (EN). Part 1 is the “top-level” document of the series, defining the overall TPEG1 structure, message numbering rules and version management — the entry point for understanding the remaining parts.
⚠️ Four of the seven parts in this series are scanned versions without a full searchable text, including Parts 2, 3, 7 and 9. Descriptions of these parts in this article are compiled from public domain knowledge; always refer to the official BSI published edition for authoritative clauses.
2. Series Composition 🧩
| Part | Edition | Subject | Notes |
|---|---|---|---|
| PD CEN ISO/TS 18234-1 | 2013 | Introduction, numbering and versions (TPEG1-INV) | Readable version |
| PD CEN ISO/TS 18234-2 | 2013 | Data / application layer general framework | Scanned version |
| PD CEN ISO/TS 18234-3 | 2013 | Service and network layer (SNP) definitions | Scanned version |
| PD CEN ISO/TS 18234-7 | 2013 | General location referencing mechanisms | Scanned version |
| PD CEN ISO/TS 18234-9 | 2013 | Traffic event application messages | Scanned version |
| PD CEN ISO/TS 18234-10 | 2013 | Conditional access information (TPEG1-CAI) | Readable version |
| PD CEN ISO/TS 18234-11 | 2013 | Location referencing container (TPEG1-LRC) | Readable version |
3. Key Technical Requirements 🔧
3.1 Introduction, Numbering and Versions — Part 1
Part 1 defines the overall framework of the TPEG1 binary data format: message application numbering rules, version management, message container structures and cross-reference methods for the other parts. It provides the consistency foundation of the series: any TPEG1 receiver must first parse the message identifiers and version fields defined in Part 1 before it can correctly interpret the subsequent content.
3.2 Conditional Access Information — Part 10
Part 10 specifies the message format for conditional access information (TPEG1-CAI), used for access control and authorization of protected traffic information content. It defines the encoding of permission descriptions, key management information and access-control messages, enabling operators to implement subscription, encryption and authorized distribution of premium traffic information services, supporting the commercial model.
3.3 Location Referencing Container — Part 11
Part 11 defines the location referencing container (TPEG1-LRC). Location referencing is the “address language” of traffic information: it maps events, congestion and waypoints precisely onto map elements. TPEG1-LRC offers an extensible, interoperable encoding of location references supporting coordinates, road segments, nodes and names — the key to making “information that is described also findable on the map”.
✅ Application note: combining TPEG1-LRC with the Part 7 location referencing mechanisms lets the same traffic event be located consistently and accurately by map engines from different vendors; conditional access (CAI) provides a standardized protection channel for premium services. Together they are the two pillars of commercial TPEG deployment.
4. Engineering Practice and Use Cases 🏭
- 📻 Digital broadcast distribution: TPEG1 byte streams are broadcast to in-car terminals over DAB/DAB+, supporting live traffic conditions, incident alerts and parking information over wide coverage with no data charges.
- 📱 Mobile mobility applications: TPEG1 data is pushed to smartphone navigation apps over the Internet and overlaid onto maps as congestion and incident layers using the location referencing container.
- 🚌 Public transport information: bus arrivals and train delays are encoded using TPEG1 applications and parsed uniformly by passenger information systems.
- 🔌 Integration essentials: receivers must implement Part 1 numbering and version parsing first; maintain backward compatibility when upgrading versions; implement authorization and decryption flows per Part 10 for paid services; and always validate map matching per Part 11 for location display.
5. FAQ ❓
❓ Q: What is the difference between TPEG1 and RDS-TMC?
A: RDS-TMC uses FM subcarriers with compact event-code plus location-code encoding and limited bandwidth; TPEG1 is an application-oriented binary data format that is richer and more flexible, can be distributed over DAB and the Internet, and supports conditional access and multimedia extensions — becoming the next-generation traffic information format.
A: RDS-TMC uses FM subcarriers with compact event-code plus location-code encoding and limited bandwidth; TPEG1 is an application-oriented binary data format that is richer and more flexible, can be distributed over DAB and the Internet, and supports conditional access and multimedia extensions — becoming the next-generation traffic information format.
🔍 Q: What problem does the location referencing container (LRC) solve?
A: The same place may be represented by different road-segment codes in different map vendors’ databases. LRC provides a unified, mappable location-reference encoding so that a single source encoding can be located consistently by multiple map engines — avoiding the awkward situation of “the event is described but the map cannot find it”.
A: The same place may be represented by different road-segment codes in different map vendors’ databases. LRC provides a unified, mappable location-reference encoding so that a single source encoding can be located consistently by multiple map engines — avoiding the awkward situation of “the event is described but the map cannot find it”.
❓ Q: Does conditional access (CAI) mean the information is necessarily paid?
A: Not necessarily. CAI is an access-control mechanism; it can protect paid subscription content, but also support statistics, regional authorization or compliance management. Whether to charge is a business decision; CAI solves the technical question of “how to securely control who can see it”.
A: Not necessarily. CAI is an access-control mechanism; it can protect paid subscription content, but also support statistics, regional authorization or compliance management. Whether to charge is a business decision; CAI solves the technical question of “how to securely control who can see it”.
📊 Q: How do I verify a system supports TPEG1?
A: Check that the receiver implements Part 1 numbering and version parsing, the target application messages (e.g. traffic events), and the required location referencing and (optional) conditional access containers; also confirm that the distribution channel (DAB/Internet) matches the service and network layer (SNP) encapsulation.
A: Check that the receiver implements Part 1 numbering and version parsing, the target application messages (e.g. traffic events), and the required location referencing and (optional) conditional access containers; also confirm that the distribution channel (DAB/Internet) matches the service and network layer (SNP) encapsulation.