MMT_111113

Richmedia team

Kyuheon KimContents

•What is the MMT

–Objectives

–MMT history

•Overview of MMT WD

•Result of the 97th Geneva meeting & AhG

meeting (2011.10., Beijing)

What is the MMT

•Ultra-HD content •3D Video content

•Interactive 3D content •User generated content

•Group communications based applications

•

Applications supporting multi-device presentation

Emerging applications and contents

•Application-level adaptivity

•

Transport/network-level adaptivity

Adaptivity

Delivery

•Application-level tools •

Cross-layer design

QoS/QoE-aware delivery

•Progressive download •Streaming

•Content Download •Peer-to-peer (P2P)•Hybrid Delivery

•Multi-channel (multi-pipe) delivery •

Relay

•Network convergence •Service convergence •

Mashed-up services (service aggregation)

Convergence

Transparency to content protection

and rights management

networks. The standard will enable building interoperable solutions for delivery and consumption of media in this context.

§Enable the use of cross-layer design s to improve the Quality of Service/Experience (QoS/QoE). By incorporating QoS/QoE-related information from different layers, the delivery and consumption of media would be optimized.

§Enable building integrated services with multiple components for hybrid delivery over heterogeneous network environments. The specification shall provide the capability of seamless and efficient use of heterogeneous network environments, including broadcast, multicast, storage media and mobile networks.

§Enable bi-directional low delay services and applications, such as online gaming and conversational services.

§Enable efficient signaling, delivery and utilization of multiple content protection and rights management tools.

§Enable efficient content forwarding and relaying.

§Enable efficient one-to-many delivery.

§Provision means for error immunity, including burst errors.§Issue raised by Requirement Group Chairs at Lausanne meeting (Feb. 09)üWhy internet delivery of MPEG contents is so difficult?

üWhy there are lots of non standard ad-hoc solutions?

§Several contributions at Maui meeting (April 09)

üAnalysis on the problems of existing transport mechanism

üNew requirements to support emerging applications/services

§First Workshop at London meeting (July 09)

üTwo sessions (state-of-the arts & future of multimedia delivery)

üSummary of discussions to identify scope and requirements

§Brainstorming session at Xian meeting (Oct. 09)

üImproving requirements

üHighlight on two items§Second Workshop at Kyoto meeting (Jan. 10)

§Release of CfP at Geneva meeting (July 10)

§Evaluation of CfP response at Daegu meeting (Jan. 11)üWorking Draft 1.0

üTechnologies under Consideration

§Evaluation Experiments at Geneva meeting (July. 11)üWorking Draft 2.0

üTechnology under Considerations

üDescription of Evaluation Experiments on MPEG Media Transport

§Evaluation Experiments at Beijing AhG meeting (Oct. 11)üReview on Evaluation Experiments on MPEG Media Transport

MPEG Media Transport Working Draft 2.0

MMT WD

§Title: Updated Working Draft 2.0 of MPEG Media Transport

§Source: AHG on MMT (2011. 10.)

§Contents:

üScope

üDefinitions

üIntroduction

üEncapsulation Functional Area

üDelivery Functional Area

üControl Functional AreaScope

§Scope

üMPEG Media Transport (MMT) addresses transportation of MPEG Media for current and emerging services over IP network

üNote: This scope needs to be improved to reflect the scope illustrated in the Fig.1.

MPEG Media delivery over HTTP is already addressed by MPEG DASH

Figure 1: Functional areas of MMT

§Terms and definitions

üMedia Fragment Unit

ØA generic container format, independent of any specific codec, that will carry the data units independently consumable by a media decoder.

ØNote: A Media Fragment Unit is composed of media fragment data and additional

information such as media characteristics (e.g. loss-tolerance). For instance, Media Fragment Unit can be either a slice or a picture for video.

A generic container format, independent of any specific codec, that will carry üM-Unit

Øone or more Access Units (AU). An M-unit is composed of one or more media fragment units. An M-unit may contain either timed data or non-timed data.

ØNote: An M-unit is composed of Media Fragment Unit data and additional information

such as a timestamp for synchronization. M-Unit is data entity for processing by MMT Encapsulation functions.

üMMT Asset

ØAn MMT Asset is a data entity that is composed of one or more M-units. An MMT Asset is the data unit for which composition information and transport characteristics are defined.

üMMT Package

ØAn MMT Package is composed of one or more MMT Assets along with additional information such as composition information and transport

characteristics.

ØNote: MMT Assets within the MMT Package can be multiplexed or concatenated.

üMMT Payload Format

Ø

A generic payload format for carrying MMT Assets and other information for

their consumption by MMT application protocols or other existing application

transport protocols (e.g. RTP)

ØNote: MMT Payload may contain fragments of MFU with other information such as AL-FEC.

üMMT Transport Packet

ØAn MMT Transport Packet is a data format used by an application transport protocol for MMT.§System Functions Description

üMMT can be divided into three areas, namely: Encapsulation, Delivery and Control

üThe Encapsulation functional area (E) defines the format for the encapsulation of encoded media data either to be stored on storage devices or to be carried

as the payload of delivery protocols and networks.

üThe Delivery functional area (D) provides formats and functionalities that are required for transferring encapsulated media data from one network entity to

another.

üThe Control functional area (C) provides functionalities to control delivery and consumption of the media

Encapsulation Delivery Control

Examples of functionalities -Container Format

-Media Packetization

-Media Fragmentation

-Media Synchronization

-Media Multiplexing

-Content Protection

-Network flow

multiplexing

-Network

Packetization

-QoS

-Session initialization/

control/management

-Server based and/or client-

based trick modes

-Service discovery

Table 1: Examples of functionalities

Introduction(2/2)\n§ Conceptual architecture of MMT\nü MMT Package: Contains multiple MMT Assets with configuration info. ü MMT Asset: component of an MMT Package (A/V, Program Info) ü Composition information: provides the information about the relationship among the MMT Assets. ü Transport characteristics: carry the information about the transmission characteristics of MMT Assets.\n\n§ A service provider aggregates MMT Assets and places the MMT Assets on the spatiotemporal axis to create a multimedia service\n\nFigure 2: Conceptual architecture of MMT\n\n\r\n

Encapsulation Functional Area(1/2)\n§ Media Fragment Unit\nü Indicator of start unit, middle unit and end unit for Media Fragment Unit within group of Media Fragment Units. Sequence number information for indicating Media Fragment Unit position within group of Media Fragment Unit. Priority information to identify the priority value among Media Fragment Units. Dependency information to provide the relationships among Media Fragment Units, Multi-layered information for specific codec.\n\nü\n\nü ü\n\nFigure 3: Conceptual architecture of Encapsulation functional area\n\nü\n\n§ M-unit\nü ü Indicator of start unit, middle unit and end unit for the M-unit. Sequence number provides the information which is associating M-unit order numbers within an MMT Asset. Timing information with M-Unit and fragment information of M-Unit. Position of M-unit contains an Anchor Point (or an access point) of media data such as RAP (random access point).\n\n§ MMT Asset\nü ü ü ü Identification of the MMT Asset. An MMT Package contains list of MMT Assets and their identification. Size information and type information Information indicating whether single or multiple Munits are contained in the MMT Asset. Initialization Parameter Set information providing the information to set up the media codec.\n\nü ü\n\n\r\n

Encapsulation Functional Area(2/2)\n§ Configuration Information\nü An MMT Package has functionality and operations to utilize configuration information. Configuration information is consisted of a list of MMT Assets, composition information and transport characteristics. ü Description Information describes MMT Package and MMT Assets. Composition information helps consumption of MMT Assets. Transport Characteristics Information provides hint for delivery of MMT Assets.\nConfiguration Information\n\nOrdering and Addressing of Data Information\n\nPackage Identification Information\n\nAsset List Information\n\nComposition Information\n\nTransport Characteristics\n\nTemporal Relationship\n\nSpatial Relationship\n\nInter-Asset Relationship\n\nRights Management\n\nError Resiliency\n\nCombinable Relationship\n\nMutually Exclusive Relationship\n\nDependency Relationship\n\nAdaptive Relationship\n\nFigure 4: Structure of Configuration Information\n\n\r\n

Delivery Functional Area\n§ Delivery functional area provides the following information\nü ü ü ü ü ü ü Payload identification ü Error control functions Handling of temporal relations ü Flow control functions Timing constraints handling ü QoS related functions Group communications Interfaces with Encapsulation and Control functions Interface with existing application transport protocols (e.g. RTP, RSVP) Interface with existing transport protocols (e.g. UDP, TCP)\n\nFigure 5: Conceptual architecture of Delivery functional area\n\n\r\n

Control Functional Area\n\nFigure 6: Control functions\n\n§ Presentation Session Management\nü Presentation Session Management defines the formats of control messages exchanged between applications for media presentation, session management, and the provisioning of information required for media consumption.\n\n§ Delivery Session Management\nü Delivery Session Management defines the formats of control messages exchanged between delivery end-points. These control messages are used for flow control, delivery session management, delivery session monitoring, error control and hybrid network synchronization control.\n\n\r\n

Result of the 97th Geneva meeting\n§ Working Draft of MPEG Media Transport § Technology under Considerations on MPEG Media Transport § Description of Evaluation Experiments on MPEG Media Transport\nü ü ü ü ü ü ü ü ü ü ü ü ü ü E.3 Layer Design (E3-LD) E.2 Layer Design (E2-LD) E Layer Timing Model (E-TM) E.1 Layer Design (E1-LD) MMT Transport Characteristics (M-TC) E.1 Layer Composition Information (E1-CI) D Layer Timing Model (D-TM) D.1 Layer Design (D1-LD) D.1 Layer AL-FEC (D1-FEC) D.2 Layer Design (D2-LD) D.3 Layer Design (D3-LD) C.1 Layer Design (C1-LD) C.1 DRM/CAS (C1-DRM) C.2 Layer Design (C2-LD)\n\n\r\n

Timeline

11/13/201120

Annex

–3D video content

–Interactive 3D content

–User generated content

–Group communications based applications

–Applications supporting multi-device presentation •Adaptivity

–Application-level adaptivity

–Stateless server

–Stateful server •Content Download

–Movie Download

–Push VoD Service

•Peer-to-peer (P2P)

•Hybrid Delivery

–Broadcast of stream along with auxiliary information over broadband channel

–Purchasing rights objects for a protected broadcast using the broadband channel

–Switching between broadcast and broadband channels

–Broadcast of content aligned with widgets

–Transport/network-level adaptivity

•Delivery

–Progressive download

–Streaming

•Streaming Portal for Timeshift TV / Content on Demand

•Trick play with COD

•Trick play with Live Media Broadcast

•24/7 Streaming Media services

•Live Streaming Events

•Recording a streamed service

•Graceful adaptation to channel burst-errors

•Multimedia Transport over IP for Real-Time Consumption –Relay

–Related content components

–Parallel Consumption of downloaded and streamed Content Items to two ITDs over one Broadband

Connection

–Download of missing parts and additional components after recording

•Multi-channel (multi-pipe) delivery

–Combination of multiple videos delivered over the

Internet

–Multiple audio tracks

–HD/SD, stereo/multi-channel sound

–Picture-in-Picture

–Mosaic

–Additional audio service components

–Additional video service components

–Radio

–Illustrated Radio•QoS/QoE-aware delivery

–Application-level tools

–Cross-layer design

•Bottom-up interfaces

•Top-down interfaces

•Internal functions

•Convergence

–Network convergence

•Media-aware devices

•Broadcast and point-to-point networks

–Service convergence

•Backward compatible basic service

–Mashed-up services (service aggregation)•Transparency to content protection and rights management

–Preview of high quality versionAnnex A.1. MMT Package

Information(1/2)§Flexible ordering and addressing of data in the MMT

üData in the MMT Package can be arranged in any orders such as consumption order or priority order. The MMT Package provides

information on physical location of data in the MMT Package.

§Package Identification Information

üPackage Identification Information contains machine-readable information such as service provider ID, content ID, genre and episode number of the

MMT Package. It uniquely distinguishes one MMT Package from others.

üPackage Identification Information also contains human-readable information such as title of service, name of actors/actresses, synopsis, etc.

These information help users to choose a MMT Package to consume.

§Asset list Information

üAsset list Information provides a list of MMT Assets in a MMT Package.

Any data in MMT Package payload is MMT Asset and it should be listed

in the Asset list.

Annex A.1. MMT Package

Information(2/2)§Composition Information

üComposition Information specifies how MMT Assets are consumed by signaling Asset relationships. There are three major types of relationships

describing composition of MMT Assets: Temporal Relationship, Spatial

Relationship, and Inter-Asset Relationship.

§Transport Characteristics Information

ü

Transport Characteristics Information provides hints for delivery of MMT

Assets. An MMT Asset shall have one or more Transport Characteristics

Information sets. A MMT Package doesn’t have delivery path for its

internal resources –MMT Assets. An MMT Asset in a MMT Package has a

Transport Characteristics Information set that help to decide delivery path

for each service provider. For example, a Broadcaster or In-home server

can use the same MMT Package. Hence the delivery path to serve same

MMT Asset in the same MMT Package can be differs such as broadcast

RF channel by broadcaster and RTP address by in-home server.§Payload identification

üDifferent types of payloads from the E layers will require different handling by delivery functions. A payload identification scheme provided

by the D functional area facilitates the handling of payloads by various

functions in the delivery functional area.

§Handling of temporal relations

üUnder the network environment envisioned for MMT. MPEG media will be delivered to the destination as MMT delivery packets which possess

temporal relationships with other packets that may be delivered using

different channels and even different networks. Thus the D layer must

provide a function that handle temporal relations for the media units.

Synchronization techniques using timestamps are typically used for this

purpose.

§Timing constraints handling

üFor real time media the delivery of MMT delivery packets is subject to certain timing constraints, e.g. to be delivered by a certain time. To

deliver these types of payload the D layer must provides functions that

can analyse the timing constraints so that the packets can be delivered

within these constraints.§Error control functions

üDepending on network conditions and environments media packets may be damaged or lost during delivery. Thus error control is an essential

function of the delivery layer. Forward Error Correction (FEC) and

retransmission (where applicable) are typical techniques used to provide

this functionality.

§Flow control functions

ü

The delivery layer needs to provide a function to control the flow of

media packets to be delivered to a destination to avoid overwhelming the receiver.

§QoS related functions

üTo maintain certain level of QoS for delivery of media packets the D layer needs to interact with other layers of MMT, as well as with lower layers

(MAC/PHY, cross-layer design).

§Group communications

üOne of the main requirements of MMT which differentiates MMT from existing transport systems is the capability of group communications. To

fulfil this requirement D layer must provide functions for handling group

communications.§Interfaces with Encapsulation and Control functions

üInterfaces must be provided so that D layer can interact with E and C layers to gather so that they can cooperate in delivering media packets.

§Interface with existing application transport protocols (e.g. RTP, RSVP)üThis interface provides means to invoke existing application transport protocols to deliver media packets. In the MMT architecture the MMT

Payload Format defines this interface.

§Interface with existing transport protocols (e.g. UDP, TCP)üThis interface provides means to use existing transport layer protocols, i.e.

UDP and TCP. In the MMT architecture this interface is defined by the

specification of the MMT Transport Packet.