ISO 21219-6:2019

Overview

ISO 21219-6:2019 defines the Message Management Container (MMC) for TPEG2 (Traffic and Travel Information via Transport Protocol Experts Group, generation 2). As a toolkit (not a standalone application), the MMC is included in every TPEG message to carry administrative information that helps a TPEG client (decoder) manage, version and process messages correctly. The MMC is always the first (ordered) container in a TPEG message and contains no end‑user content - it is intended purely for message handling on the client side.

Keywords: ISO 21219-6:2019, TPEG2, Message Management Container, MMC, intelligent transport systems, traffic and travel information, TTI.

Key topics and technical requirements

• MMC role and structure
  • Specifies MMC components such as MMCTemplate, MessageManagementContainer, MMCMasterMessage and MMCMessagePart.
  • MMC must be the first top-level container in a TPEG message; other containers (ADC, LRC) follow.
• Message management mechanisms
  • Monolithic Message Management: whole-message updates and versioning; replacement of complete messages.
  • Multipart Message Management: parts of a message transmitted and combined independently; includes multi-part lifecycle and directory datatypes.
  • The two mechanisms are mutually exclusive for a given messageID - receipt of one replaces the other in client repositories.
• Lifecycle and identification
  • Defines how a TPEG message is identified, versioned and managed across transmit/receive lifecycles.
• Datatypes and tables
  • Includes datatypes such as MultiPartMessageDirectory and tables like mmc001: PartType and mmc002: UpdateMode.
• Physical format representations
  • Normative annexes provide the MMC in both TPEG-Binary and TPEG-ML (XML) representations.

Practical applications - who uses this standard

• ITS implementers and service providers building or operating TPEG2-based traffic and travel information services.
• TPEG encoder and broadcaster vendors who package TTI services for distribution.
• Device and decoder manufacturers (in-car systems, infotainment, set‑top receivers) implementing client-side message handling logic.
• Software developers and integrators building middleware that assembles, versions or reconstitutes multipart TPEG messages.
• Standards bodies and consultants aligning TPEG applications, ADCs and LRCs with TPEG2 toolkit requirements.

Related standards

• ISO 21219 series (TPEG2 toolkit and applications), e.g. TPEG2-INV, TPEG2-UML, TPEG2-SFW, and TPEG2-LRC (ISO/TS 21219-7).
• Historical context: TPEG Generation 2 is the successor to TPEG Generation 1 (ISO/TS 18234 series).

ISO 21219-6:2019 is essential for reliable TPEG2 message handling, ensuring decoders can correctly version, replace and assemble messages across broadcast and packet delivery systems.