Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) - Part 9: Service and network information (TPEG2-SNI)
Introduction: History TPEG technology was originally proposed by the European Broadcasting Union (EBU) Broadcast Management Committee, who established the B/TPEG project group in the autumn of 1997 with a brief to develop, as soon as possible, a new protocol for broadcasting traffic and travel-related information in the multimedia environment. TPEG technology, its applications and service features were designed to enable travel-related messages to be coded, decoded, filtered and understood by humans (visually and/or audibly in the user’s language) and by agent systems. Originally, a byte-oriented data stream format, which can be carried on almost any digital bearer with an appropriate adaptation layer, was developed. Hierarchically structured TPEG messages from service providers to end-users were designed to transfer information from the service provider database to an end-user’s equipment. One year later in December 1998, the B/TPEG group produced its first EBU specifications. Two documents were released. Part 2 (TPEG-SSF, which became ISO/TS 18234-2) described the Syntax, Semantics and Framing structure, which was used for all TPEG applications. Meanwhile, Part 4 (TPEG- RTM, which became ISO/TS 18234-4) described the first application, for Road Traffic Messages. Subsequently in March 1999, CEN TC 278, in conjunction with ISO/TC 204, established a group comprising members of the former EBU B/TPEG and this working group continued development work. Further parts were developed to make the i
Scope: This part of ISO/TS 21219 establishes the method of delivering service and network information within a TPEG service. 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. NOTE A number of tables of information are described, which provide comprehensive options for describing services, their timing, content, geographical coverage, etc. 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.