Overview
ISO/TS 18234-4:2006 defines the TPEG Road Traffic Message (TPEG‑RTM) application for delivering Road Traffic Messages (RTM) within a TPEG (Transport Protocol Expert Group) service. TPEG‑RTM specifies a byte‑oriented stream format that enables efficient, language‑independent transfer of road event and status information from service providers to end‑users. The specification is focused on concise event descriptions, message management, and interoperable location referencing for use in navigation systems, broadcast services and telematics.
Key topics and technical requirements
- Message structure: TPEG‑RTM uses three main containers:
- Message Management Container (header, date/time, expiry, severity, reliability)
- Application Event Container (detailed event descriptions and qualifiers)
- TPEG‑Location Container (location referencing; specified in ISO/TS 18234‑6)
- Application Identification: AID = 0001 is assigned to the TPEG‑RTM application.
- Byte‑oriented stream: Designed for transport over many digital bearers with appropriate adaptation layers.
- Language independence: Word‑oriented dictionaries (derived from DATEX / ENV 13106) support multilingual rendering at the receiver.
- Event taxonomy: Hierarchical event classes, qualifiers (e.g., vehicle types, carriageway positions), severity and reliability coding.
- Timing and formats: Uses ISO 8601 for date/time elements (normative reference).
- Interoperability: Designed to interwork with other TPEG parts (Part 1, Part 2 SSF, Part 3 SNI, Part 6 Location).
- Backward compatibility: Includes mappings to RDS‑TMC concepts where reasonable, though explicit full backward compatibility is not guaranteed.
Applications and who uses it
- Traffic service providers and broadcasters: encode and push RTM content to distribution networks.
- Automotive OEMs and infotainment systems: integrate TPEG‑RTM decoders for in‑vehicle guidance and alerts.
- Navigation and map vendors: consume structured events for dynamic routing and map overlays.
- Telematics and fleet management: automate incident awareness and routing decisions.
- ITS integrators and mobile app developers: build multilingual, efficient traffic information services for end users.
Practical use cases include real‑time incident alerts, road status updates (including abnormal link operation like ferries or lifting bridges), diversion advice, and severity‑aware notifications.
Related standards
- ISO/TS 18234‑1 - Introduction, numbering and versions
- ISO/TS 18234‑2 - Syntax, Semantics and Framing Structure (TPEG‑SSF)
- ISO/TS 18234‑3 - Service and Network Information (SNI) application
- ISO/TS 18234‑6 - Location Referencing application (TPEG‑Loc)
- ISO 8601 - Date and time representation
- DATEX (ENV 13106) - Source of many word dictionaries used by TPEG‑RTM
ISO/TS 18234‑4 is essential for anyone implementing standardized, interoperable road traffic messaging using the TPEG framework. Keywords: ISO/TS 18234-4:2006, TPEG-RTM, Road Traffic Message, Traffic and Travel Information, TTI, location referencing, TPEG.
Open preview (PDF)Traffic and Travel Information (TTI) — TTI via Transport Protocol Expert Group (TPEG) data-streams — Part 4: Road Traffic Message (RTM) application