ISO 21219-3:2019
Intelligent transport systems — Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) — Part 3: UML to binary conversion rules (TPEG2-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.
This document specifies the rules for converting UML models of TPEG application to the TPEG binary format. It contains the binary format definition of the abstract data types defined in ISO 21219-2. Rules for converting compound data types are also defined.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$240.87 NZD
|
|
| HardCopy |
$277.39 NZD
|
|
| Networkable PDF |
Price varies
|
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Rules for UML to binary format description conversion
5.1 Definition of binary format description
5.2 Abstract data types
5.3 Binary format specific data types
5.4 TPEG tables
5.5 Compound data types
5.5.1 Rule 1: Classes
5.5.2 Rule 2: Datastructures
5.5.3 Rule 3: Selector
5.5.4 Rule 4: Attributes
5.5.5 Rule 4a: Datatypes
5.5.6 Rule 4b: Ordering
5.5.7 Rule 4c: Single multiplicity
5.5.8 Rule 4d: Multiplicity [0..maxOccurs>1], Multiplicity [1..maxOccurs>1] and Multiplicity [minOccurs>1..maxOccurs>1]
5.5.9 Rule 4e: Multiplicity [0..1]
5.5.10 Rule 6 — Specialisations/Abstract classes
Annex A (normative) Usage of the binary component structure to detect and skip unknown content
Bibliography
Keep me up-to-date
Register to receive notifications when updates are made to this standard.
Related Information
Similar Standards
-
23/30382233DC
BS EN 9300-00. Aerospace series. LOTAR -LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data, Part 007. Terms and references
-
AS/NZS 3802:1997
Data elements and interchange formats - Information interchange - Representation of dates and times
-
BS 6451:1984
Specification for netting and fibre rope load restraint systems in surface transport
-
BS 7467:1991
Specification for symbols for computer applications in ship building and marine technology
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Rules for UML to binary format description conversion
5.1 Definition of binary format description
5.2 Abstract data types
5.3 Binary format specific data types
5.4 TPEG tables
5.5 Compound data types
5.5.1 Rule 1: Classes
5.5.2 Rule 2: Datastructures
5.5.3 Rule 3: Selector
5.5.4 Rule 4: Attributes
5.5.5 Rule 4a: Datatypes
5.5.6 Rule 4b: Ordering
5.5.7 Rule 4c: Single multiplicity
5.5.8 Rule 4d: Multiplicity [0..maxOccurs>1], Multiplicity [1..maxOccurs>1] and Multiplicity [minOccurs>1..maxOccurs>1]
5.5.9 Rule 4e: Multiplicity [0..1]
5.5.10 Rule 6 — Specialisations/Abstract classes
Annex A (normative) Usage of the binary component structure to detect and skip unknown content
Bibliography