|This article needs additional citations for verification. (January 2015)|
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.
The Transport Protocol Experts Group was started in 1997 by the European Broadcasting Union (EBU). 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) 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 and device manufacturers accepted TPEG2 as THE successor to TMC 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.