A Candidate Standard is a document that has received significant review within a specialist group. Advancement of a document to Candidate Standard is an explicit call to those outside of the related specialist group for implementation and technical feedback. This is the phase at which the specialist group is responsible for formally acquiring that experience or at least defining the expectations of implementation.
Approved 28 February 2017. Updated 12 April 2017. The CS period ends 31 July 2017.
This document describes the ATSC 3.0 digital television system. ATSC 3.0 is a suite of voluntary technical Standards and Recommended Practices for a digital terrestrial television broadcast system. ATSC 3.0 is fundamentally different from predecessor ATSC systems and is therefore largely incompatible with them. This divergence from earlier design is intended to allow substantial improvements […]Read More Download PDF File
Approved 30 September 2016. The CS period ends 31 July 2017.
This document specifies the protocol on the Single Frequency Network (SFN) interface from studio side infrastructure to SFN of transmitters. The document also defines possible interfaces among the studio infrastructure, for example the interconnection of the ATSC Link Layer Protocol (ALP) and a Broadcast Gateway. This document specifies certain constraints on the scheduling of content […]Read More Download PDF File
Approved 5 January 2016. Updated 22 March 2017. This document is currently at ballot as a Proposed Standard.
This document specifies the technical mechanisms and procedures pertaining to service signaling and IP-based delivery of a variety of ATSC 3.0 services and contents to ATSC 3.0-capable receivers over broadcast, broadband and hybrid broadcast/broadband networks. The service signaling functionality defines the data formats and information components necessary to discover and acquire user services. The IP-based […]Read More Download PDF File Download Zip File
Approved 19 January 2017. Updated 16 April 2017. The CS period ends 19 July 2017.
This document specifies mechanisms for signaling the properties of applications, including their lifecycle states, and also mechanisms for delivering activation notifications synchronized with a time base, so that the actions of applications can be synchronized accordingly. The accompanying schemas can be downloaded as a ZIP file (see below). A redline is available showing changes made relative […]Read More Download PDF File Download Zip File
Approved 2 March 2017. This document is currently at ballot as a Proposed Standard.
Approved 29 December 2016. Updated 18 April 2017. The CS period ends 29 June 2017.
This specification defines the details of an environment that is required for broadcaster’s applications to run. The broadcaster’s application is an HTML5 application running in a User Agent, which utilizes the User Agent APIs specified in this document. A redline is available that shows changes relative to the previously published version.Read More Download PDF File
Approved 28 October 2016. Updated 27 March 2017. This document is currently at ballot as a Proposed Standard.