1. No category

S33: Specialist Group on
Management & Protocols
Youngkwon Lim,
S33 Chairman
[email protected]
Samsung Electronics
S31
SG on System Requirements
& Program Management
Layers: System and Process
S34
Applications and Presentation
Management
S33
Protocols
S32
Physical
2
In the past (I) - ATSC 1.0
Program Multiplexing
Clock Reference Locking
MPEG-2
Transport
Stream
A/V Synchronization
Program and System Information Protocol
In the past (II) - ATSC 2.0
Interactivity
Personalization
Measurements
Adding
use of Internet
Non
Realtime
(NRT)
Delivery
via other
interfaces
Adding
use of local storage &
others
Advanced
Codecs
Support
Adding
use of new codecs
In the past (III) - ATSC MDTV
captured from http://www.atsc.org/cms/pdf/bootcamp/ATSC_MDTV_Bootcamp%20_10_13_11-Jay_Adrick.pdf
Scope of S33 & AHGs
The Specialist Group on Management and Protocols (called
TG3/S33) will solicit, examine and assess technical proposals and
develop Standards and Recommended Practices related to
technologies for the management and delivery of ATSC 3.0
services and associated metadata, over terrestrial broadcast
channels and, if appropriate, broadband/bi-directional
networks, to fulfill the relevant ATSC 3.0 System Requirements.
6
S33 – Management and Protocols
S33: Management & Protocols
(Youngkwon Lim)
S33-1: Service Delivery &
Synchronization
Delivery
Signaling
Error
Recovery
Emergency
Alerts
Personalization
Content
Advisory
Usage
Reporting
Synch.
(Rich Chernock & Charles Lo)
S33-2: Service Announcement
& Personalization
Announcement
(Sachin Despande)
S33-3: Interactive Service &
Companion-Screen
(Madeleine Noland)
2nd screen
Interactivity
redistribution
support
App Signaling
Toward IP-friendly standard
MMT
MMT
ISOBMFF
IP
ROUTE
Watermark
OMA
BCAST
ESG
UTC
Key features of
ATSC 3.0 Management & Protocols
IP-based protocols
(no use of MPEG-2 TS)
ISOBMFF as the
streaming media
format
UTC as the clock
reference
Roles of each layers
Presentation Layer (HTML5)
ISO Base Media File Format
Delivery Encapsulation of ISOBMFF
Application Layer Protocol
TCP/UDP and IP
Physical Layer
This layer is in charge of basic lip sync.
(e.g. synchronization of audio and video)
This layer is in charge of converting ISOBMFF into a
streamable format
This layer is in charge of delivering media data ensuring
buffer model and forward error correction
Protocol Stack
Media Processing Unit
(MPU)
MPEG DASH
NRT
NRT
MPEG Media Transport Protocol (MPU mode)
ROUTE
HTTP
UDP
UDP
TCP
IP
IP
IP
Data Link Layer
Data Link Layer
Physical Layer (e.g. ATSC 3.0)
Physical Layer
Broadcast
Broadband
S33-2
Service Announcement &
Personalization
Service Announcement (SA)
• Service Announcement Data Model is based on OMA
BCAST 1.0.1 with some elements taken from OMA
BCAST 1.1 and some extensions for ATSC 3.0
• Extensions specific to ATSC 3.0
– Speech Phonetic Information extensions for service
description
– Service Level extensions for icon and channel numbers
– Content Level extensions regarding component description
and device capabilities descriptions
Fragments of Service Announcement
• Service Fragment
• Schedule Fragment
• Content Fragment
Encapsulation of Service Announcement
for Delivery
• Service Guide Delivery Unit structure as specified in the
OMA BCAST 1.0.1 Service Guide with some additional constraints
– Delivering SA as Service Guide XML fragments
– Service_Guide_Delivery_Unit
• Unit_Header
– fragmentTransportID[i]
– fragmentVersion[i]
• Unit_Payload
– XMLFragment
Content Advisory & Personalization
• Content Advisory ratings is indicated for each rating region.
For each rating region, rating value is provided for one or more rating
dimensions.
• Personalization work will define data model of personalization and the
delivery of personalization data
– Input on personalization conceptual model from TG3/S34-3
– Personalization will include accessibility & rendering preferences and targeting
and demographics related personalization
Service Usage Reporting
• Service Usage reporting mechanism defines a client which manages
the functions of service consumption data collection, storage and
transmission to the servers.
• Based on ATSC A/105 usage reporting with extensions for ATSC 3.0
• Extensions for ATSC 3.0 include:
–
–
–
–
Indication of service usage report per component
Indication of delivery path
Indication of which device the content is being consumed on
Use of JavaScript Object Notation (JSON) for delivery of Consumption Data
Messages
Summary
HTML 5
IP
ATSC 3.0
Physical Layer
Ethernet
Wi-Fi
4G LTE
ATSC 3.0 will add another IP pipe to the device
More to come in the afternoon
S33-1 AHG on Service Delivery and Synchronization
Charles Lo, Qualcomm
33-3 AHG on Interactive Service and Companion-Screen
Madeleine Noland, Zenith
19
ATSC 3.0
Because Quantity
Matters.
Thanks to our Sponsors