1、 ISO 2015 Intelligent transport systems - Traffic and travel information via transport protocol experts group, generation 2(TPEG2) Part 6: Message management container (TPEG2-MMC) Systmes intelligents de transport Informations sur le trafic et le tourisme via le groupe expert du protocole de transpo
2、rt, gnration 2 (TPEG2) Partie 6: Conteneur de gestion de message (TPEG2-MMC) TECHNICAL SPECIFICATION ISO/TS 21219-6 First edition 2015-03-01 Reference number ISO/TS 21219-6:2015(E) ISO/TS 21219-6:2015(E)ii ISO 2015 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2015 All rights reserved. Unless
3、 otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the add
4、ress below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/TS 21219-6:2015(E) ISO 2015 All rights reserved iii Contents Page F
5、oreword iv Introduction vi 1 Scope . 1 2 Normative references 1 3 Terms, definitions and abbreviated terms 1 3.1 Terms and definitions . 1 3.2 Abbreviated terms . 2 4 MMC components and capabilities 2 4.1 Overview 2 4.2 Lifecycle and identification of a TPEG message . 6 4.3 MMCTemplate 6 4.4 Message
6、ManagementContainer . 7 4.5 MMCMasterMessage 7 4.6 MMCMessagePart . 8 5 MMC Datatypes . 8 5.1 MultiPartMessageDirectory . 8 6 MMC Tables. 9 6.1 mmc001:PartType . 9 6.2 mmc002:UpdateMode 9 Annex A (normative) Management Container, MMC,TPEG-Binary Representation .10 Annex B (normative) Management Cont
7、ainer, MMC, TPEG-ML Representation 13 Bibliography .18 ISO/TS 21219-6:2015(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through IS
8、O technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates c
9、losely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criter
10、ia needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility that some of the elements of this document may be the subject of
11、patent rights. ISO and TISA shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any tr
12、ade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the
13、Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/TC 204 Intelligent transport systems, in cooperation with the Traveller Information Services Association (TISA), TPEG Applications Working Group through Ca
14、tegory A Liaison status. ISO/TS 21219 consists of the following parts, under the general title Intelligent transport systems Traffic and travel information (TTI) via transport protocol expert group, generation 2 (TPEG2): Part 2: UML modelling rules Technical Specification Part 3: UML to binary conve
15、rsion rules Technical Specification Part 4: UML to XML conversion rules Technical Specification Part 5: Service framework Technical Specification Part 6: Message management container Technical Specification Part 7: Location referencing container Technical Specification Part 18: Traffic flow and pred
16、iction application Technical Specification The following parts are planned: Part 1: Introduction, numbering and versions Technical Specification Part 9: Service and network information Technical Specification Part 10: Conditional access information Technical Specification Part 14: Parking informatio
17、n application Technical Specification Part 15: Traffic event compact application Technical Specification Part 16: Fuel price information application Technical Specificationiv ISO 2015 All rights reserved ISO/TS 21219-6:2015(E) Part 19: Weather information application Technical Specification Part 20:
18、 Extended TMC location referencing Technical Specification Part 21: Geographic location referencing Technical Specification Part 22: OpenLRlocationreferencing Technical Specification Part 23: Roadsandmulti-modalroutesapplication Technical Specification ISO 2015 All rights reserved v ISO/TS 21219-6:2
19、015(E) 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
20、-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 users language) and by agent systems. Originally a byte-o
21、riented data stream format, which may 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-users equi
22、pment. 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, whi
23、ch became ISO/TS 18234-4) described the first application, for Road Traffic Messages. Subsequently in March 1999, CEN TC 278/WG 4, in conjunction with ISO/TC 204/WG 10, established a project group comprising members of the former EBU B/TPEG and they continued the work concurrently. Further parts wer
24、e developed to make the initial set of four parts, enabling the implementation of a consistent service. Part 3 (TPEG-SNI, ISO/TS 18234-3) described the Service and Network Information Application, used by all service implementations to ensure appropriate referencing from one service source to anothe
25、r. Part 1 (TPEG-INV, ISO/TS 18234-1), completed the series, by describing the other parts and their relationship; it also contained the application IDs used within the other parts. Additionally, Part 5, the Public Transport Information Application (TPEG-PTI, ISO/TS 18234-5), was developed. The so- c
26、alled TPEG-LOC location referencing method, which enabled both map-based TPEG-decoders and non map-based ones to deliver either map-based location referencing or human readable text information, was issued as ISO/TS 18234-6 to be used in association with the other applications parts of the ISO/TS 18
27、234-series to provide location referencing. The ISO/TS 18234-series has become known as TPEG Generation 1. TPEG Generation 2 With the inauguration of the Traveller Information Services Association (TISA) in December 2007 derived from former Forums and the CEN/ISO development project group, the TPEG
28、Applications Working Group took over development work for TPEG technology. It was about this time that the (then) new Unified Modelling Language (UML) was seen as having major advantages for the development of new TPEG Applications in communities who would not necessarily have binary physical format
29、 skills required to extend the original TPEG TS work. It was also realized that the XML format for TPEG described within the ISO/TS 24530-series (now superseded) had a greater significance than previously foreseen; especially in the content-generation segment and that keeping two physical formats in
30、 synchronism, in different standards series, would be rather difficult. As a result TISA set about the development of a new TPEG structure that would be UML based this has subsequently become known as TPEG Generation 2. TPEG2 is embodied in the ISO/TS 21219-series and it comprises many parts that co
31、ver introduction, rules, toolkit and application components. TPEG2 is built around UML modelling and has a core of rules that contain the modelling strategy covered in Parts 2, 3, 4 and the conversion to two current physical formats: binary and XML; others could be added in the future. TISA uses an
32、automated tool to convert from the agreed UML model XMI file directly into an MS Word document file, to minimize drafting errors, that forms the Annex for each physical format.vi ISO 2015 All rights reserved ISO/TS 21219-6:2015(E) TPEG2 has a three container conceptual structure: Message Management
33、(Part 6), Application (many Parts) and Location Referencing (Part 7). This structure has flexible capability and can accommodate many differing use cases that have been proposed within the TTI sector and wider for hierarchical message content. TPEG2 also has many location referencing options as requ
34、ired by the service provider community, any of which may be delivered by vectoring data included in the Location Referencing Container. The following classification provides a helpful grouping of the different TPEG2 parts according to their intended purpose: Toolkit parts: TPEG2-INV (Part 1), TPEG2-
35、UML (Part 2), TPEG2-UBCR (Part 3), TPEG2-UXCR (Part 4), TPEG2-SFW (Part 5), TPEG2-MMC (Part 6), TPEG2-LRC (Part 7) Special applications: TPEG2-SNI (Part 9), TPEG2-CAI (Part 10) Location referencing: TPEG2-ULR (Part 11), TPEG2-ETL (Part 20), TPEG2-GLR (Part 21), TPEG2-OLR (Part 22) Applications: TPEG
36、2-PKI (Part 14), TPEG2-TEC (Part 15), TPEG2-FPI (Part 16), TPEG2-TFP (Part 18), TPEG2-WEA (Part 19), TPEG2-RMR (Part 23) TPEG2 has been developed to be broadly (but not totally) backward compatible with TPEG1 to assist in transitions from earlier implementations, while not hindering the TPEG2 innova
37、tive approach and being able to support many new features, such as dealing with applications having both long-term, unchanging content and highly dynamic content, such as Parking Information. This Technical Specification is based on the TISA specification technical/editorial version number: TPEG2-MM
38、C/1.1/001. ISO 2015 All rights reserved vii Intelligent transport systems - Traffic and travel information via transport protocol experts group, generation 2(TPEG2) Part 6: Message management container (TPEG2-MMC) 1 Scope This Technical Specification adds a basic toolkit definition to the ISO 21219
39、series specifying the Message Management Container (MMC), which is used by all TPEG applications to provide information about the handling of messages on the TPEG client side. The MMC holds administrative information allowing a decoder to handle the message appropriately. This information is not aim
40、ed at the end user. The MMC is a toolkit and not a stand-alone application but is included by TPEG applications. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the
41、edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/TS 18234-3, Intelligent transport systems Traffic and travel information via transport protocol experts group, generation 1 (TPEG1) binary data format Part 3: Service
42、and network information (TPEG1- SNI) ISO/TS 21219-2, Intelligent transport Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) Part 2: UML modelling rules ISO/TS 21219-3, Intelligent transport systems Traffic and travel information (TTI) via transport prot
43、ocol experts group, generation 2 (TPEG2) Part 3: UML to binary conversion rules ISO/TS 21219-4, Intelligent transport systems Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) Part 4: UML to XML conversion rules 3 Terms, definitions and abbreviated terms
44、 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1.1 Message unit of information that is controlled under a message ID and contains a MessageManagementContainer, MMCMasterMessage or MMCMessagePart component 3.1.2 Monolithic Message Management
45、 message management that allows versioning of messages by updating complete messages only Note 1 to entry: See 4.1.3. TECHNICAL SPECIFICATION ISO/TS 21219-6:2015(E) ISO 2015 All rights reserved 1 ISO/TS 21219-6:2015(E) 3.1.3 Multipart Message Management message management that allows parts of messag
46、es being transmitted in packets independently Note 1 to entry: See 4.1.4. 3.1.4 Top Level Container any component that is on the same level as the message management container 3.1.5 TPEG Server device or entity on the sending side of the TPEG transmission chain Note 1 to entry: May consist, e.g. of
47、a TPEG encoder, a stream encoder, a network transmission unit. 3.1.6 TPEG Client device or entity on the receiving side of the TPEG transmission chain Note 1 to entry: May consist, e.g. of a broadcast receiver, a TPEG decoder unit. 3.2 Abbreviated terms MMC Message Management Container LRC Location
48、Referencing Container ADC Application Data Container 4 MMC components and capabilities 4.1 Overview 4.1.1 Structure Figure 1 Structure of the Message Management Container2 ISO 2015 All rights reserved ISO/TS 21219-6:2015(E) 4.1.2 Capabilities Any TPEG message typically consists of the following top
49、level containers (see also Figure 2 below): Exactly one Message Management Container (MMC) Optionally one or several Application Data Container(s) (ADC) Optionally one Location Reference Container (LRC) The MMC contains no data dedicated for the user but only administrative information for the TPEG decoder to handle the message appropriately. While the ADC part is defined specifically by the related TPEG application specification, the TPEG
