Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD ISO TS 21219 โ Intelligent Transport Systems โ Traffic and Travel Information (TTI) via TPEG2 Standard Series
PD (Published Document) identically adopting ISO/TS 21219 โ TPEG2 family for traffic and travel information
๐ก PD ISO TS 21219 is the British Standards Institution’s Published Document that identically adopts the ISO/TS 21219 Technical Specification family. It belongs to the field of Intelligent Transport Systems (ITS) and defines TPEG2 โ the second generation of the Transport Protocol Experts Group format โ used to deliver Traffic and Travel Information (TTI) such as road conditions, incidents, weather, parking, fuel prices and public-transport data. TPEG2 re-engineered the earlier character-based TPEG1 into a compact, binary, application-oriented model in which the content of each information type is fully decoupled from the underlying bearer, whether that bearer is broadcast (e.g. DAB), cellular or IP-based internet delivery.
๐ก Note: most parts of this series are scanned versions; this article is written on the basis of public-domain knowledge. The readable parts (such as -1, -10 and -14) supplied genuine scope and title information, and the content below combines that visible material with public-domain knowledge of the domain.
1. Scope and Position in the Standards Landscape ๐
PD ISO TS 21219 addresses the content representation and transport of TTI, not the physical or link layer of any bearer. Compared with TPEG1, the central change in TPEG2 is a layered model that separates applications from bearers. The family consists of an introductory/guidance part and a set of application parts. The guidance part defines numbering, versions, application identification and the relationship to bearers; each application part defines the data elements, syntax and semantics of one information type (e.g. road traffic, parking, conditional access).
The visible parts of the series include at least: Part 1 (TPEG2-INV: introduction, numbering and versions), Part 2, Part 3, Part 4, Part 5, Part 6, Part 9, Part 10 (TPEG2-CAI: conditional access information), Part 14 (TPEG2-PKI: parking information application), and further Parts 15, 16, 18, 19, 23, 24 and 25 โ sixteen parts in total, forming a complete application set.
โ ๏ธ TPEG2 only standardises the encoding and semantics of information; it does not define the bearer networks themselves (RDS-TMC, DAB, IP and so on). A deployment must also follow the relevant bearer specification, otherwise a terminal cannot correctly receive and parse the data.
2. Composition of the Series and Key Parts ๐ง
| Part | Shorthand | Main content |
|---|---|---|
| PD ISO/TS 21219-1 | TPEG2-INV | Guidance: application identification, numbering and version management โ the entry point for all other parts |
| PD ISO/TS 21219-2 | โ | Generic container and message framework defining the basic TPEG message structure |
| PD ISO/TS 21219-3 | โ | Generic language support and text-encoding foundation |
| PD ISO/TS 21219-4 | โ | Generic framework for location referencing |
| PD ISO/TS 21219-5 | โ | Service and network information (SNI) basis |
| PD ISO/TS 21219-6 | โ | Service description related content |
| PD ISO/TS 21219-9 | โ | Specific application: road traffic and event content |
| PD ISO/TS 21219-10 | TPEG2-CAI | Conditional access information: encryption and authorization for paid or restricted services |
| PD ISO/TS 21219-14 | TPEG2-PKI | Parking information application: location, availability, tariffs and so on |
| PD ISO/TS 21219-15/16/18/19 | โ | Weather, fuel price, public transport, environment and other extended applications |
| PD ISO/TS 21219-23/24/25 | โ | Subsequent extended application parts |
3. Key Technical Requirements ๐ฅ
From the readable parts, several design pillars stand out. First, application/bearer separation: each application part only cares about which data elements make up a parking message, while a separate bearer-mapping layer decides how to place it into a DAB frame or an IP packet. Second, compact binary encoding: TPEG2 uses self-describing TPEG messages containing an application identification, a version number and a payload, so a terminal can decide by application ID whether to parse. Third, standardised location referencing: because the value of traffic information depends heavily on “where”, the family includes a location-referencing framework (e.g. Part 4 with its location applications) that describes links, areas and points of interest with a unified geographic encoding.
Part 10 (TPEG2-CAI, conditional access information) defines the scrambling and authorisation mechanism for restricted services, allowing operators to charge for, or regionally authorise, premium traffic information such as precise congestion data or parking reservation. Part 14 (TPEG2-PKI, parking information application) targets the high-frequency urban-parking scenario, defining data elements for parking-supply, opening hours, tariff bands and accessibility.
๐จ Conditional access (CAI) involves encryption and key distribution. Any implementation of paid services must satisfy the applicable national regulations on encryption and consumer protection; compliance with TPEG2 encoding alone does not excuse a service from those obligations.
4. Engineering Practice ๐ ๏ธ
- ๐ Information service providers map their own traffic, parking and incident data onto the data elements of each application part to form TPEG2 messages, then encapsulate them through a bearer-mapping layer.
- ๐ง Vehicle and mobile terminals selectively parse by application identification and, using location referencing, overlay the information on a digital map to give drivers diversion and parking advice.
- ๐ Cross-platform interoperability because the application layer is decoupled from the bearer, the same TPEG2 content can be distributed simultaneously over DAB broadcast and mobile internet, lowering multi-channel operating costs.
- ๐ Compliance and versions before deployment verify the part versions in use; terminals must handle version negotiation so that new application messages are not mis-parsed by older terminals.
5. Frequently Asked Questions โ
โ Q: What is the relationship between PD ISO TS 21219 and ISO/TS 21219?
A: PD (Published Document) is BSI’s published-document form. PD ISO TS 21219 is the UK national version in which BSI identically adopts the ISO/TS 21219 technical specification; the technical content is identical to ISO/TS 21219.
A: PD (Published Document) is BSI’s published-document form. PD ISO TS 21219 is the UK national version in which BSI identically adopts the ISO/TS 21219 technical specification; the technical content is identical to ISO/TS 21219.
โ Q: What is the main difference between TPEG2 and earlier TPEG1?
A: TPEG2 decouples “application” from “bearer”, adopts a more compact, extensible binary message structure, and introduces a unified application numbering and versioning mechanism, making it easy to add new application parts without breaking compatibility of existing terminals.
A: TPEG2 decouples “application” from “bearer”, adopts a more compact, extensible binary message structure, and introduces a unified application numbering and versioning mechanism, making it easy to add new application parts without breaking compatibility of existing terminals.
โ Q: What can the parking information application (PKI) express?
A: From the visible Part -14, PKI addresses the location, available spaces, tariffs, opening periods and management mode of parking facilities, supporting integration with navigation and parking-guidance systems.
A: From the visible Part -14, PKI addresses the location, available spaces, tariffs, opening periods and management mode of parking facilities, supporting integration with navigation and parking-guidance systems.
๐ Q: Is conditional access information (CAI) mandatory?
A: No. CAI is used only where a paid or restricted premium information service must be protected; freely broadcast traffic information does not require CAI but still must follow the encoding rules of the relevant application part.
A: No. CAI is used only where a paid or restricted premium information service must be protected; freely broadcast traffic information does not require CAI but still must follow the encoding rules of the relevant application part.