1、 ISO 2015 Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) Part 3: UML to binary conversion rules Systmes intelligents de transport Informations sur le trafic et le tourisme via le groupe expert du protocole de transport,
2、 gnration 2 (TPEG2) Partie 3: Rgles de conversion dUML systme binaire TECHNICAL SPECIFICATION ISO/TS 21219-3 Reference number ISO/TS 21219-3:2015(E) First edition 2015-03-01 ISO/TS 21219-3:2015(E)ii ISO 2015 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2015 All rights reserved. Unless otherw
3、ise 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 address be
4、low 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-3:2015(E)Foreword iv Introduction vi 1 Scope . 1 2 Normative refe
5、rences 1 3 Abbreviated terms 1 4 Rules for UML to binary format description conversion 1 4.1 Definition of binary format description 1 4.2 Abstract data types 3 4.3 Binary format specific data types . 7 4.4 TPEG tables 8 4.5 Compound data types . 8 4.5.1 Rule 1: Classes 8 4.5.2 Rule 2: Datastructure
6、s 8 4.5.3 Rule 3: Selector 8 4.5.4 Rule 4: Attributes. 9 4.5.5 Rule 4a: Datatypes 9 4.5.6 Rule 4b: Ordering 9 4.5.7 Rule 4c: Single multiplicity .10 4.5.8 Rule 4d: Multiplicity 0n and Multiplicity 1n 10 4.5.9 Rule 4e: Multiplicity 01.11 4.6 Rule 5: Aggregations and compositions .12 4.7 Rule 6: Speci
7、alisations / Abstract classes .13 Bibliography .14 ISO 2015 All rights reserved iii Contents Page ISO/TS 21219-3: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 S
8、tandards is normally carried out through ISO 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, als
9、o take part in the work. ISO collaborates closely 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.
10、In particular the different approval criteria 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 eleme
11、nts of this document may be the subject of 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
12、 received (see www.iso.org/patents). Any trade 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 I
13、SOs adherence to the WTO principles in the 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),
14、 TPEG Applications Working Group through Category 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 experts group, generation 2 (TPEG2): Part 2: UML modelling rules Technic
15、al Specification Part 3: UML to binary conversion 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
16、Specification Part 18: Traffic flow and prediction 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 Technic
17、al Specification Part 14: Parking information 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-3:2015(E) Part 19: Weather information
18、application Technical Specification Part 20: 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
19、 2015 All rights reserved v ISO/TS 21219-3:2015(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
20、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 users languag
21、e) and by agent systems. Originally a byte-oriented 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 se
22、rvice provider database to an end-users 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 a
23、pplications. 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/WG 4, in conjunction with ISO/TC 204/WG 10, established a project group comprising members of the former EBU B/TPEG and they contin
24、ued the work concurrently. Further parts were 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 r
25、eferencing from one service source to another. 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-PT
26、I, ISO/TS 18234-5), was developed. The so- called 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 t
27、he other applications parts of the ISO/TS 18234-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
28、CEN/ISO development project group, the TPEG 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
29、 not necessarily have binary physical format 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 segm
30、ent and that keeping two physical formats in 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 2121
31、9-series and it comprises many parts that cover 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
32、 could be added in the future. TISA uses an 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-3:2015(E) TPEG2 has a three contain
33、er conceptual structure: Message Management (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 h
34、as many location referencing options as required 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 purpos
35、e: Toolkit parts: TPEG2-INV (Part 1), TPEG2-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
36、 21), TPEG2-OLR (Part 22) Applications: TPEG2-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 implement
37、ations, while not hindering the TPEG2 innovative 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
38、technical/editorial version number: TPEG2-UBCR/1.1/001. ISO 2015 All rights reserved vii Intelligent transport systems - Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) Part 3: UML to binary conversion rules 1 Scope This Technical Specification specifi
39、es the rules for converting TPEG application UML models to the TPEG binary format description. It contains the binary format definition of the abstract data types defined in ISO/TS 21219-2. Rules for converting compound data types are also defined. 2 Normative references The following documents, in
40、whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/TS 18234-2:2013, Intelligent tr
41、ansport systems Traffic and travel information (TTI) via transport experts group, generation 1 (TPEG1) binary data format Part 2: Syntax, semantics and framing structure (TPEG1-SSF) ISO/TS 21219-2, Intelligent transport systems Traffic and travel information (TTI) via transport protocol experts grou
42、p, generation 2 (TPEG2) Part 2: UML modelling rules ISO/TS 21219-5, Intelligent transport systems Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) Part 5: Service framework ISO/IEC/IEEE 60559, Information technology Microprocessor Systems Floating-Point
43、 arithmetic 3 Abbreviated terms The abbreviated terms defined in ISO/TS 21219-2 and the following apply. LSB Least Significant Bit MSB Most Significant Bit 4 Rules for UML to binary format description conversion 4.1 Definition of binary format description The binary format description of TPEG applic
44、ations is included in application specifications as a normative annex. This annex shall be named according to the following scheme: Full application name, TPEG-binary representation The annex shall have four subclauses: Introduction, Application framing and signalling, Application components and App
45、lication datastructures. The content of these subclauses is subject to the specifications in this clause. TECHNICAL SPECIFICATION ISO/TS 21219-3:2015(E) ISO 2015 All rights reserved 1 ISO/TS 21219-3:2015(E) The introduction shall use a similar formulation as in the following: This chapter defines th
46、e application framing and the format of the Full application name message components, datastructures and its attributes for the TPEG binary representation of application abbreviation as described in reference to TPEG framework. For further descriptions of these objects see the related clauses refere
47、nce to clauses in this specification. The Application framing and signalling subclause shall have three parts: Application identification, Version number signalling, and Application framing. The Application identification part shall define the Application Identifier (AID) that is used for the applic
48、ation. The Version number signalling shall define the major and minor version number of the application that are signalled within the SNI application. The Application framing part shall state in what kind of service component the application shall be transmitted. TPEG Service Component (SC) types ar
49、e defined in ISO/TS 21219-5. Currently, the following Service Component types are defined: ServCompFrame Standard SC ServCompFrameProtected SC with data CRC ServCompFrameCountedProtected SC with message count and data CRC ServCompFramePrioritisedProtected SC with group priority and data CRC ServCompFramePrioritisedCountedProtected SC with group priority, message count and data CRC The wording shall be similar to