® May 6, OVERVIEW OF THE ATSC DATA BROADCAST SERVICE SPECIFICATION Version 1.0 Don Newell, Intel Corporation Regis J. Crinon, Sharp Labs of America Inc.

® May 6, PRESENTATION OVERVIEW MANDATE OF THE ATSC T3S13 WORKING GROUP A/V/D SERVICES DATA SERVICES SIGNALING ANNOUNCEMENT, DISCOVERY, BINDING ADVANTAGES (for broadcast, interactive services) LAYERS AND PROTOCOLS PACKETIZATION, SYNCHRONIZATION, PROTECTION LAYERS DOWNLOAD, IP PROTOCOLS ADVANTAGES TRANSPORT SYTEM TARGET DATA RECEIVER MODEL DATA SERVICE PROFILES BUFFER MODEL DATA SERVICES LEVELS CONCLUSION

® May 6, ATSC T3S13 MANDATE Define how data associated with a television program is carried, scheduled and announced. Define how data not associated with a program is carried, scheduled and announced. Build a foundation for new services (e.g. interactive services). Define transport mechanisms to support a wide variety of data services: ñAsynchronous/Synchronous/Synchronized data ñMultiprotocol data ñFixed bandwidth data ñOpportunistic data.

® May 6, THANK YOU! T3 members for recognizing importance of data services and starting T3S13 T3 members trying to promote our work Active participation of experts from other WGs Companies who have hosted meetings MPEG for endorsement of some new aspects of transmission

® May 6, A/V/D SERVICES

® May 6, DTV = VIDEO + AUDIO + DATA MPEG-2 Transport Streams carrying multiplexed: Service Information (ATSC PSIP + MPEG-2 SI) Audio, video and data elementary streams

® May 6, GENERAL PICTURE * Television Programs * A/V * PSIP/System Info *Associated data such as - HTML-based -New media/graphics Stand-alone Data Services * Subscription Services - Magazines, Music - Targeted info services * Streaming Data (DSM-CC, IP) Opportunistic data services * Business data services * IP router in the sky *Targeted info services MPEGTransportStream Broadcast Multiplex

® May 6, ATSC T3S13 BENEFITS Richer presentation model for advertisers/content producers Media object delivery (HTML, JAVA applets, Rich Graphics) New incremental capabilities based on data Support for widespread existing data protocols Basic data services File download Integration with Web content

® May 6, DATA SERVICES SIGNALING

® May 6, ANNOUNCEMENT : PSIP + DIT DISCOVERY BINDING SDF

® May 6, ANNOUNCEMENT (SCHEDULE) Data Services associated with an A/V event: value of service_type is 0x02 or 0x03 Use either > PSIP EIT(s) for a data services sharing same schedule and same title as A/V event OR > DIT(s) for a data service having a separate schedule or title A/V events data service 1 data service 2 Data Services NOT associated with an A/V event: value of service_type is 0x04 Use DIT(s)

® May 6, ANNOUNCEMENT (SCHEDULE) In the descriptor loop of every A/V/D or D event: A Data Broadcast Descriptor is present. service_profile service_level Fields may be used by data receiver to determine whether it can proceed with acquisition of data service or not A PID Count Descriptor is optionally present: total # of PIDs minimum # of PIDs Fields may be used by data receiver to determine whether it can acquire full or “minimal” data service

® May 6, ANNOUNCEMENT (SCHEDULE) Only one data service per virtual channel Possibly multiple data services in a single MPEG-2 Transport Stream (in this case SDF must be on distinct PIDs)

® May 6, DISCOVERY AND BINDING: SERVICE DESCRIPTION FRAMEWORK SDF: Describes a data service as an aggregation of applications (discovery) Provides information for associating an application with broadcast or remote data components (binding) Is designed based on MPEG-2 DSM-CC mechanisms (Association Tag descriptor, Tap structure).

® May 6, SERVICE DISCOVERY Main element is the Data Service Table identifying the applications making up a data service The transmission of a Data Services Table is mandatory for any ATSC Data Service Data Service Table follows MPEG-2 System section format

® May 6, DATA SERVICE TABLE dataServiceTable(){ for (applications count) { compatibility descriptor application identifier for (tapsCount){ protocol_ encapsulation Tap() } // end tapsCount application parameters descriptors application private information } // end applications count service private information } MPEG-2 packetization, synchronization, protection layers + protocol “pointer” to data element

® May 6, BINDING TO A COMMUNICATION CHANNEL ApplicationCode() { open( TapId ) } TapId use associationTag selectorLength for(j=0;j<selectorLength; j++){ selectorByte } } } associationTag in associationTag descriptor in PMT OR in Network Resource Descriptor APP TAP IN DST

® May 6, SERVICE BINDING Main elements are the Network Resources Table and the Association Tag descriptor(s) in the PMT The Network Resources Table announces any external communication channels used by a data service. The transmission of a Network Resources Table is optional for any ATSC Data Service Network Resources Table follows MPEG-2 section format

® May 6, NETWORK RESOURCES TABLE networkResourceTable(){ compatibility descriptor dsmccResourceDescriptor private information } The internet address of a server in an interactive service OR a remote data elementary stream in another MPEG-2 Transport Stream includes an association tag

® May 6, SERVICE BINDING Multiple Taps of one or several applications can reference the same Network Resource !!! DST NRTPMT AT1 AT2 App1 Tap1 Tap2 Tap3 App2 Tap1 Tap2

® May 6, SDF: GENERAL PICTURE Tap 1 (AT1) Tap 2 (AT4) Data Service Table Network Resources TableProgram Map Table APPLICATION LAYER COMMUNICATION LAYER Application 1 PID 4 ATdescriptor AT 4 Connection 1 (AT1) Connection 2 (AT2) Connection 3 (AT3) WEB SERVER BROADCAST DATA INTERACTIVE DATA PIDx PIDy PID4 Matching AT Tap2 Tap1

® May 6, SDF ADVANTAGES promotes responsible usage of bandwidth flexibility to determine how frequently it is transmitted (impact on accessibility) designed for broadcast and interactive services based on basic MPEG section parsing. direct access to association tags so they can be managed easily in emission station uses new resource descriptors for broadcast and interactive services (amendment 2 to DSM-CC)

® May 6, LAYERS AND PROTOCOLS

® May 6, PACKETIZATION, SYNCHRONIZATION, PROTECTION LAYERS MPEG-2 Transport Stream Non-flow controlled LLC/SNAP PES packets Data Piping SDF addressable sections MPEG-2 sections DSM-CC sections PSIP checksum CRC32 checksum CRC32 MPEG-2 PTS data carousel DSM-CC download MPEG-2 PTS AIPV LLC/ SNAP

® May 6, PES Packets Carry A/V data Carry A/V data Carry data synchronized with A/V Carry data synchronized with A/V Carries data synchronized with other PES streams Carries data synchronized with other PES streams Carries synchronous data Carries synchronous data MPEG-2 T.S. PES packets MPEG-2 PTS AIPV LLC/ SNAP

® May 6, PES PACKETS Synchronous data streaming harmonized with Synchronous data streaming harmonized with SCTE DVS132 SCTE DVS132 Synchronized data streaming harmonized with DVB Synchronized data streaming harmonized with DVB Each type has a defined header Each type has a defined header Headers are not the same for Synchronous and Headers are not the same for Synchronous and Synchronized data elementary streams Synchronized data elementary streams

® May 6, EXAMPLE OF SYNCHRONOUS DATA SERVICES Video Games based on 2D/3D graphics and image rendering Infomercial based on animated computer graphics

® May 6, DSM-CC SECTIONS carousel scenario = periodic re-transmission of carousel scenario = periodic re-transmission of data module (for increased accessibility) data module (for increased accessibility) non-flow controlled scenario = one time download non-flow controlled scenario = one time download of a data module of a data module Download protocol follows amendment 1 to DSM-CC Download protocol follows amendment 1 to DSM-CC for directory message numbering for directory message numbering The synchronized download protocol offers capability The synchronized download protocol offers capability to transmit non-streaming, error-protected, to transmit non-streaming, error-protected, synchronized data synchronized data MPEG-2 T.S. Non-flow controlled DSM-CC sections checksum CRC32 MPEG-2 PTS data carousel DSM-CC download

® May 6, EXAMPLES OF ASYNCHRONOUS DATA SERVICES SONICS 102 PACERS 90 FINAL... Stock tickers sports statistics weather reports music downloads,...

® May 6, EXAMPLES OF NON-STREAMING SYNCHRONIZED SERVICES Just-in-Time transmission of data synchronized with video and/or audio born in 1962 Pop-up videos Hot-spots, URL links in commercials and documentaries Evening games Triggers

® May 6, ADDRESSABLE SECTIONS MPEG-2 TS LLC/SNAP addressable sections checksum IP For tunneling of Internet Protocol Include a 6-byte MAC address Default mapping is 28-bit IP multicast address to 23-bit Ethernet MAC multicast address Agree with Amendment 1 to DSM-CC checksum protection only for backward compatibility with MPEG section parsers Note: We need protocols to manage ATSC IP Network (urgent) !!!

® May 6, EXAMPLES OF ADDRESSABLE SECTION -BASED SERVICES Personalized services: Download of software at night Subscription to newspaper service Scalable services: platform-dependent downloads

® May 6, TRANSPORT SYSTEM TARGET DATA RECEIVER MODEL

® May 6, DATA SERVICE PROFILES Purpose is: To represent maximum bandwidth allocated to a data service. Multiple services can be bundled together into the same profile A data service may use less than the transmission bandwidth allowed by the profile

® May 6, DATA SERVICE PROFILES G1 G2 G3 A1 Guaranteed bandwidth up to 384 kpbs Guaranteed bandwidth up to 3.84 Mbps Guaranteed bandwidth up to Mbps Opportunistic up to Mbps ( NTSC VBI-based Data Services: 180 kbits/sec max )

® May 6, OPPORTUNISTIC DATA SERVICES Opportunistic data service = A data service for which no transmission bandwidth has been provisioned in the emission station. Data packets are inserted into the multiplex upon request from multiplexer (see IS DIWG) Opportunistic data services make use of instantaneous bandwidth available in a transport stream. Profile to be used in connection with VBR video encoders.

® May 6, T-STD BUFFER MODEL The T-STD buffer model embodies the timely and controlled delivery of data. Its purpose: To provide multiplexers with tool to implement synchronization of data with video or audio in a reliable manner. To define bounds on size of data to be acquired by data receivers To define bounds on throughput required in data receivers.

® May 6, T-STD BUFFER MODEL FOR ASYNCHRONOUS SERVICES Transport buffer TBn Smoothing buffer SBn Data transfer rate specified by RXn Leak rate specified by sb_leak_rate 512 Bytes Size determined by sb_size

® May 6, T-STD FOR SYNCHRONIZED SERVICES Transport buffer TBn Smoothing buffer SBn Data Elementary buffer DEBn Data transfer rate specified by RXn Leak rate specified by sb_leak_rate 512 Bytes Size determined by sb_size Size determined by SDEBn Data Access Unit (DAU) taken out at time specified by MPEG-2 PTS associated with DAU, assuming instantaneous decoding

® May 6, DATA SERVICE LEVELS DEBSn = bytes DEBSn = bytes DEBSn = bytes DEBSn = bytes

® May 6, DATA SERVICE LEVELS Purpose to provide reference points for memory and throughput requirements in data receivers DEBn buffer is split uniformly among all data elementary streams so applications of a same service can be run concurrently in a data receiver Nominal Data Access Unit (DAU) size is bytes = 19.2 Mbits/sec * 1001 / (8 * 60 * 1000) DAUs must at least msec apart (172.8 Mbits/sec throughput for level 1 services )

® May 6, CONCLUSION ATSC Data Broadcast Service specification is the result of more than 2 years of successful collaboration between CE, PC and head-end equipment manufacturers. It has been recorded as DVS 161 by SCTE The specification opens up new business opportunities (opportunistic data, data service devices, IEEE 1394, personalization,...) The specification will help accelerate deployment of DTV services.