From Wikipedia, the free encyclopedia
Jump to: navigation, search

The Transport Protocol Experts Group (TPEG) is a data protocol suite for traffic and travel related information. TPEG can be carried over different transmission media (bearers), such as digital broadcast or cellular networks (wireless Internet). TPEG applications include, among others, information on road conditions, weather, fuel prices, parking or delays of public transport.


TPEG is a set of data protocols for carrying traffic & travel related information, comprising a range of different applications as well as basic building blocks to manage the transmission of the applications themselves, such as the handling of different messages belonging to a given application, grouping applications into data frames, or the updating and cancellation of messages. TPEG can be carried over different transmission media (bearers), such as digital broadcast[1][2][3] or cellular networks (wireless Internet). TPEG aplications include, among others, information on road conditions, weather, fuel prices, parking or delays of public transport.


The Transport Protocol Experts Group was started in 1997 by the European Broadcasting Union (EBU).[4] Work carried on under the auspices of the EBU until 2007, when the group merged with another group working on the Traffic Message Channel (TMC) protocol, hosted by ERTICO - ITS Europe and with the Mobile.Info project, where first prototypes of TPEG technology was tested under realistic driving conditions in various in-car navigation systems by a number of car manufacturers and their suppliers. Today, development work is carried out by the Traveller Information Services Association (TISA), who now also looks after the TMC standards.

In the early days of the Transport Protocol Experts Group, the plan was to develop applications that could extend traffic information services far beyond existing technologies, such as RDS-TMC or proprietary protocols. Further, TPEG should include multi-modal traveller information services, facilitating roaming of travellers between different modes of transportation, e.g. between individual transportation (using a car) and public transportation (bus, subway, trains, ...). It all started with a Road Traffic Message (RTM)[5] application, which was soon complemented by a Public Transport Information (PTI) application, which both shared a common native TPEG Location Referencing method.

TPEG RTM was intended as the "one size fits all" application. However, early implementations soon showed that the RTM structure was too broad to be used in navigation systems as a replacement for TMC. This first generation TPEG applications (TPEG generation 1, or TPEG1) also provided only a binary encoding, having in some cases a separate specification for the mapping to an XML encoding. Consequently, a revision of both the general information modelling style and the design approach was done, moving TPEG towards more clearly defined and separated applications for specific use cases and a top-down data modelling approach. This second generation TPEG applications (TPEG generation 2, or TPEG2) is now specified with an UML model, from which automatically both a binary encoding and XML encoding are derived. A TPEG2 application specification includes both the binary and XML encodings as integral part of the specification.

With the first TPEG2 TEC application, a breakthrough was achieved in a sense that both service providers[6] and device manufacturers accepted TPEG2 as THE successor to TMC[7] and deployments were rolled out in many countries.

Both TPEG1 and TPEG2 are standardized with the International Organization for Standardization as ISO/TS 18234 (TPEG1) and ISO/TS 21219 (TPEG2). TPEG1 is now considered a legacy system and the implementation of new services based on TPEG1 is discouraged.


TPEG defines specifications for providing highly accurate traffic- and traveller information of many kinds. TPEG allows the transfer of data via different bearers e.g. digital broadcast or internet. In fact, today this is mainly used to inform travellers on roads, train tracks or even pedestrians. Information for a convenient journey e.g. on road conditions, weather, fuel prices, parking or delays of public transport are coded in TPEG.TPEG is a protocol with containers which carry specific content, for each service on a specific content so called ‘applications’ are defined in a separate technical specification. TPEG is designed to be modern and flexible, it is even more future proof, easy to adapt towards new trends, needs and conditions. Selecting the right applications and technical implementation profile, allows provision of safety relevant information to all travellers on time, accurately and precisely. Due to this major benefit, TPEG is welcomed by regulators and legal authorities too. TPEG based products are already available in several European and Asian and American markets from different suppliers. Such products range from content creation/management[8] over encoder/decoder equipment,[9][10][11] test equipment[12] and receiver/navigation devices[13][14] to numerous services[15][16][17][18][19][20] that are online world-wide. Further, encryption solutions[21] are available for commercial services.

TPEG design philosophy[edit]

TPEG is developed in a top-down fashion based on modeling use cases in the Unified Modeling Language (UML). Based on the UML modeling, two version are derived:

  • Extensible Markup Language (XML) encoding – This format is human- and machine-readable and it can be easily rendered in navigation devices by parsing the XML structure. It is further backwards compatible in a way that new XML tags can be included in a given application, which would be simply skipped by older device populations that do not recognize these tags. New device populations can however benefit from the new features.
  • Binary encoding – This format is not human-readable, but much more compact than its XML representation. Binary encoding is therefore frequently used when the available bandwidth is small and a compact encoding of services is of the essence.

TPEG core principles[edit]

The following principles are considered as core in the development of the TPEG protocol, structure and semantics (see[22] and [23]).

TPEG ...

  • is designed for unidirectional (broadcast) and bi-directional communication channels (e.g. IP)
  • binary versions are Byte-oriented
  • provides a protocol structure with asynchronous framing and a hierarchical data frame structure
  • includes CRC error detection capabilities on different protocol levels
  • assumes that the underlying communication layers provide error correction
  • uses a transparent data channel
  • facilitates transmission of service provider names, service names, network information, etc.
  • permits the use of encryption[21] mechanisms, e.g. for restricting access to commercial services

TPEG additional capabilities

TPEG ...

  • supports dynamic ("on-the-fly") location referencing methods and therefore does not need a preloaded location database (e.g. TMC Location Tables)
  • offers rich content encoding
  • is language independent
  • facilitates client device filtering of service content
  • is designed to support “thick” and “thin” client devices
  • provides adaptation layers for different communication bearers

TPEG2 Applications[edit]

ISO Part No. ISO Reference Title Acronym Description
21219-1 Introduction, numbering and versions INV This Technical Specification provides an introduction and index to the complete set of TPEG Generation 2 toolkit components and applications. It allows the indexing of new applications as they are added to the TPEG applications family, by defining their Application Identification (AID).
21219-2 [1] UML modelling rules UMR Rules to define the semantics of a TPEG application by a suitable model, independent from its physical data format and transmission issues. These rules ease TPEG implementation process.
21219-3 [2] UML to binary conversion rules UBCR TPEG applications are modelled in UML to provide an application description that is independent of a physical format representation. By separating semantics from application description, applications can easily be developed at a functional level. Different physical format representations can be generated following a well defined set of rules on how to convert UML classes to different physical formats.
21219-4 [3] UML to XML conversion rules UXCR Rules for converting TPEG application UML models to the tpegML format description.
21219-5 [4] Service framework SFW TPEG2 can provide a multiplex of TPEG Services and applications. Both the binary and XML formats are specified to compose a multiplex of TPEG services, each potentially having multiple TPEG applications.
21219-6 [5] Message management container MMC The Message Management Container is used by all TPEG applications to provide information about the handling of messages on the TPEG client side
21219-7 Location referencing container LRC The TPEG2-Location Referencing Container is used to signal which specific location referencing method is in use for a particular TPEG Message. It is able to handle Location Referencing methods that are external to the present ISO series and the internal location referencing methods defined as parts of this series.
21219-9 Service and network information SNI The TPEG-SNI application is designed to allow the efficient and language independent delivery of information about the availability of the same service on another bearer channel or similar service data from another service provider, directly from service provider to end-users. In all TPEG streams it is mandatory to deliver to so-called GST. Additionally it is possible to signal linkage of content between different bearers and services.
21219-10 Conditional access information CAI Function applied on service frame or service component level. Thanks to it, some service components may be encrypted using the same “encryption key”, while other remain unencrypted or use different “encryption keys”.
21219-11 Universal location referencing ULR TPEG Applications and toolkits are developed using UML models via two alternative representations: Byte-binary for usage in on-air interface and TPEG-ML for application on the sender infrastructure. These models provide representation of the applications that is independent of any physical format.
21219-14 [6] Parking information application PKI Designed to deliver parking informaiont (textually, voiced or graphically) to a variety of receivers via digital broadcasting and Internet technologies.
21219-15 [7] Traffic event compact application TEC Compact application for traffic event / incident information. TPEG2-TEC is optimized to support dynamic route guidance navigation devices. This application is currently in the phase of being rolled out by more and more providers to replace TMC
21219-16 [8] Fuel price information application FPI This application has been designed to support information of fuel stations, their location, fuel types offered, and fuel pricing and availability information.
21219-18 [9] Traffic flow and prediction application TFP Compact application providing precise travel speed / travel time and forecast information. Many premium dynamic navigation devices use this application as a basis to use current and expected traffic to be displayed to the user and for dynamic route calculation
21219-19 Weather information application WEA Weather forecast for travellers, over multiple time periods and geographical areas.
21219-20 Extended TMC location referencing ETL This application establishes additional fields for coding closed exit and entries. This is primarily aimed at devices which can only decode TEC with TMC-Location-Container.

Furthermore, the possibility is added to “Extend” a TMC location to include the Internal road segments of the secundary location, and to exclude optionally the internal road segments of the primary location.

21219-21 Geographic location referencing GLR Method for signaling geographic location references (points, poly-lines, and geographical areas), which can be transported inside a TPEG-Location Referencing Container (TPEG-LRC) for those TPEG applications wishing to relay primarily geographical locations (e.g. Weather).
21219-22 OpenLR location referencing OLR Designed to transfer traffic information (e.g. current traffic situation at a certain point, special alerts) from a centre to in-vehicle systems, built-in or used as an add-on (PND, Smart Phone).
21219-23 Road and multimodal routes application RMR This application enables the provision of precise information and guidance from a central knowledge base to a traveller’s mobile device. It encompasses road routes as well as multi-modal routes and parking.

See also[edit]

External links[edit]


  1. ^ "Traffic and Travel". World DAB Forum. Retrieved December 8, 2015. 
  2. ^ Delaney, Ian (26 March 2015). "All we hear is Radio Garmin: HERE is tuned into DAB". HERE 360. HERE. Retrieved 7 December 2015. 
  3. ^ Stauch, Oliver (October 28, 2013). "DAB+: Stauinfos per TPEG". Connect. WEKA MEDIA PUBLISHING GmbH. Retrieved December 8, 2015. 
  4. ^ "TPEG - Transport Protocol Experts Group". EBU Tech. European Broadcasting Union. 2002. Retrieved December 7, 2015. 
  5. ^ "RTM (Road Traffic Message)". Munhwa Broadcasting Corporation. Retrieved December 8, 2015. 
  6. ^ "ARD-Hörfunk optimiert Verkehrsservice". January 6, 2005. Retrieved December 8, 2015 – via ARD. 
  7. ^ Mikolaschek, Peter. "Traffic and Travel Information from the point of view of the ADAC". World DAB Eureka. Retrieved December 8, 2015. 
  8. ^ "TPEG". GEWI. Retrieved December 8, 2015. 
  9. ^ "TPEG Encoder/Converter". Institut für Rundfunktechnik (IRT). Retrieved December 8, 2015. 
  10. ^ "TPEG End-to-End Solution". SM CNS. Retrieved December 8, 2015. 
  11. ^ "TPEG Decoder Software" (PDF). Fraunhofer Institute for Integrated Circuits (IIS). Retrieved December 8, 2015. 
  12. ^ "Traffic Telematics". Bayerische Medien Technik GmbH. Retrieved December 8, 2015. 
  13. ^ "BMW the first with new jam-busting technology: Real Time Traffic Information (RTTI)". BMW Group. October 10, 2011. Retrieved December 8, 2015. 
  14. ^ "Audi launches TPEG over IP traffic info powered by INRIX XD Traffic". Telematics News. January 24, 2011. Retrieved December 8, 2015. 
  15. ^ "INRIX TPEG Connect™ Optimizes Delivery and Reduces Costs of Providing Dynamic Traffic Info to Connected Vehicles and Devices". INRIX. July 28, 2010. Retrieved December 8, 2015. 
  16. ^ "V-Traffic Premium DAB". Mediamobile. Retrieved December 8, 2015. 
  17. ^ "Mediamobile Delivers First Digital Radio Traffic Service in Germany". TDF Group. May 15, 2013. Retrieved December 8, 2015. 
  18. ^ "Traffic Information Platform (TRIP)". Quantum Inventions. Retrieved December 8, 2015. 
  19. ^ "TomTom HD Traffic now available as TPEG service for automotive navigation solutions". TomTom. Retrieved December 8, 2015. 
  20. ^ INRIX (July 6, 2012). "Real-Time Traffic Info Gets More Real". WIRED. Retrieved December 8, 2015. 
  21. ^ a b "HECA - Hich Efficiency Conditional Access for Digital Broadcast Services" (PDF). Fraunhofer Institute for Integrated Circuits (IIS). Retrieved December 8, 2015. 
  22. ^ TISA (October 15, 2013). "Intelligent transport systems -- Traffic and travel information via transport protocol experts group, generation 1 (TPEG1) binary data format -- Part 2: Syntax, semantics and framing structure (TPEG1-SSF)". ISO. Retrieved December 12, 2015. 
  23. ^ TISA (March 1, 2015). "Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) -- Part 5: Service framework (TPEG2-SFW)". ISO. Retrieved December 12, 2015.