MPEG Media Transport (MMT) has been designed to support the second half of the MPEG-H title “Media Delivery in Heterogeneous Environments” and is based on the following assumptions

• IP-based delivery: packet oriented, with relatively large jitter, and use of internet protocols and functionalities (e.g. NTP)
• Two-planes: data plane for media delivery and control plane for signaling, and presentation and delivery management
• Layered architecture with support to communication across layers

Figure 1 depicts the MMT protocol stack.

Figure 1 – MMT protocol stack

MMT specifies technologies for three functional areas:

1. Encapsulation. Media components are processed into an MMT-specified format called Media Processing Unit (MPU) that defines the content logical structure and the physical encapsulation format based on ISO BMFF. Media component are decomposed into Assets, and individual Assets are encapsulated into a MPU file defined by MMT based on ISO BMFF. Spatial and temporal relationships among multimedia components are represented by HTML5 and Composition Information (CI) as shown in Figure2. This MPU file produced by an encapsulation function is used either to store coded media data on a storage device for delivery preparation.
2. Delivery defining:
   1.  The protocol supporting streaming delivery of packetised content through heterogeneous network environments
   2. The payload format for packetised encapsulated media
3. Signalling defining the message formats to manage MMT package consumption and delivery:
   1. Consumption management messages signal the MMT package’s structure
   2. Delivery management messages signal the payload format’s structure and the protocol configuration.

This is represented in Figure 2 below

Figure 2 – MMT specification areas (green blocks)

MMT content has an onion-shell structure composed of (from the center)

1. Media Fragment Unit (MFU) composed of Access Units (AU) which can be decoded independently;
2. Media Processing Unit (MPU) is the minimum storage and consumption unit of MMT content. It contains one/more than one MFUs and can be independently decoded. Its structure is based on ISO BMFF;
3. MMT Asset is a logical unit for multimedia component elementary streams (e.g. audio, video and data). It contains one/more than one MPU files and has its own ID so that all MPU files of an Asset can be recognised through this ID.
4. MMT Package is a logical unit of content, e.g. a broadcasting program and can be realised by one or more than one MMT Asset. Since an MMT package is represented by spatial and temporal relationship among Assets, and can be delivered by various networks, the MMT Package contains also these relationships and delivery network information.

The MMT content hierarchy is represented in Figure 3 below.

Figure 3 – MMT content hierarchy

MMT Composition Information provides information on how to presentan MMT Package in terms of both spatial and temporal relationships among MMT Assets in a MMT Package, and thus specifies how to describe and consume a MMT Package in terms of Assets relationships. The information about a MMT Package and the composition of MMT Assets in the MMT Package are described in MMT-CI. As an initial presentation of an MMT Package, the spatial relationship among Assets in the Package is described by HTML5. Assets in the MMT Package may also be delivered earlier or later in accordance with timing of events, and presented in certain regions. This temporal relationship is described by MMT-CI, which is based on XML.

Figure 4 depicts how an MMT file (top left) is chopped in MMT packets and vice versa.

Figure 4 – MMT File packetisation and back