|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
A/331:2024-04
|
|
Title:
|
Advanced Television Systems Committee, ATSC Standard A/331:2024-04, Signaling, Delivery, Synchronization, and Error Protection
|
|
|
2.
|
Status of approval:
|
|
|
Approved by ATSC
|
|
3.
|
Justification for the specific reference:
|
|
|
This is an normative reference in J.152
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
none
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
none
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Approved on 3 April 2024
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] ATSC: “ATSC Standard: Program and System Information Protocol for Terrestrial Broadcast/
and Cable,” Doc. A/65:2013, Advanced Television Systems Committee, Washington, DC, 7/
August 2013./
[2] ATSC: “ATSC Mobile DTV Standard, Part 4: Announcement,” Doc. A/153 Part 4:2009,/
Advanced Television Systems Committee, Washington, DC, October 2009./
[3] ATSC: “ATSC Standard: System Discovery and Signaling,” Doc. A/321:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[4] ATSC: “ATSC Standard: Physical Layer Protocol,” Doc. A/322:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[5] ATSC: “ATSC Standard: Service Announcement,” Doc. A/332:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[6] ATSC: “ATSC Standard: Service Usage Reporting,” Doc. A/333:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[7] ATSC: “ATSC Standard: Application Event Delivery,” Doc. A/337:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[8] ATSC: “ATSC Standard: AC-4 System,” Doc. A/342-2:2023-03, Advanced Television/
Systems Committee, Washington, DC, 28 March 2023./
[9] ATSC: “ATSC Standard: MPEG-H System,” Doc. A/342-3:2023-03 Advanced Television/
Systems Committee, Washington, DC, 28 March 2023./
[10] ATSC: “ATSC Standard: ATSC 3.0 Security and Service Protection,” Doc. A/360:2023-08,/
Advanced Television Systems Committee, Washington, DC, 15 August 2023./
[11] CTA: “U.S. and Canadian Region Rating Tables (RRT) and Content Advisory Descriptors/
for Transport of Content Advisory Information Using ATSC Program and System/
Information Protocol (PSIP),” Doc. CTA-766-D (ANSI), Consumer Technology/
Association, Arlington, VA, December 11, 2013./
[12] DASH IF: “Guidelines for Implementation: DASH-IF Interoperability Points for ATSC 3.0,/
Version 1.1,” DASH Interoperability Forum, June 12, 2018./
https://dashif.org/guidelines//
[13] ETSI: “Digital Audio Compression (AC-4) Standard, Part 2: Immersive and personalized/
audio,” Doc. ETSI TS 103 190-2 V1.1.1 (2015-09), European Telecommunications/
Standards Institute, September 2015./
[14] ETSI: “Universal Mobile Telecommunications Systems (UMTS); LTE; Multimedia/
Broadcast/Multicast Service (MBMS); Protocols and codecs (3GPP TS 26.346 version/
13.3.0 Release 13),” Doc. ETSI TS 126 346 v13.3.0 (2016-01), European/
Telecommunications Standards Institute, January 2016./
http://www.etsi.org/deliver/etsi_ts/126300_126399/126346/13.03.00_60/ts_126346v13030/
0p.pdf/
[15] IEEE: “Use of the International Systems of Units (SI): The Modern Metric System,” Doc. SI/
10-2010, Institute of Electrical and Electronics Engineers, New York, N.Y./
[16] IETF: RFC 1952, “GZIP file format specification version 4.3,” Internet Engineering Task/
Force, Reston, VA, May, 1996./
http://tools.ietf.org/html/rfc1952/
[17] IETF: RFC 2387, “The MIME Multipart/Related Content-type”, Internet Engineering Task/
Force, Reston, VA, August 1998./
http://tools.ietf.org/html/rfc2387/
[18] IETF: RFC 2557, “MIME Encapsulation of Aggregate Documents, such as HTML/
(MHTML)”, Internet Engineering Task Force, Reston, VA, March 1999./
http://tools.ietf.org/html/rfc2557/
[19] IETF: RFC 3986, “Uniform Resource Identifier (URI): Generic Syntax,” Internet/
Engineering Task Force, Reston, VA, January, 2005./
http://tools.ietf.org/html/rfc3986/
[20] IETF: RFC 4122 “A Universally Unique IDentifier (UUID) URN Namespace,” Internet/
Engineering Task Force, Reston, VA, July, 2005./
http://tools.ietf.org/html/rfc4122/
[21] IETF: RFC 4566, “SDP: Session Description Protocol,” Internet Engineering Task Force,/
Reston, VA, July 2006./
http://tools.ietf.org/html/rfc4566/
[22] IETF: RFC 5052, “Forward Error Correction (FEC) Building Block,” Internet Engineering/
Task Force, Reston, VA, August 2007./
http://tools.ietf.org/html/rfc5052/
[23] IETF: RFC 5234, “Augmented BNF for Syntax Specifications: ABNF,” Internet Engineering/
Task Force, Reston, VA, July 2006./
http://tools.ietf.org/html/rfc5234./
[24] IETF: RFC 5751, “Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2/
Message Specification,” Internet Engineering Task Force, Fremont, CA, January 2010./
https://tools.ietf.org/html/rfc5751/
[25] IETF: RFC 5905, “Network Time Protocol Version 4: Protocol and Algorithms/
Specification,” Internet Engineering Task Force, Reston, VA, June, 2010./
http://tools.ietf.org/html/rfc5905/
[26] IETF: RFC 5445, “Basic Forward Error Correction (FEC) Schemes,” Internet Engineering/
Task Force, Reston, VA, March, 2009./
http://tools.ietf.org/html/rfc5445/
[27] IETF: RFC 5651, “Layered Coding Transport (LCT) Building Block,” Internet Engineering/
Task Force, Reston, VA, October, 2009./
http://tools.ietf.org/html/rfc5651/
[28] IETF: RFC 5775, “Asynchronous Layered Coding (ALC) Protocol Instantiation,” Internet/
Engineering Task Force, Reston, VA, April, 2010./
http://tools.ietf.org/html/rfc5775/
[29] IETF: RFC 6330, “RaptorQ Forward Error Correction Scheme for Object Delivery,” Internet/
Engineering Task Force, Reston, VA, August, 2011./
http://tools.ietf.org/html/rfc6330/
[30] IETF: RFC 6381, “The ‘Codecs’ and ‘Profiles’ Parameters for ‘Bucket’ Media Types,”/
Internet Engineering Task Force, Reston, VA, August 2011./
https://tools.ietf.org/html/rfc6381/
[31] IETF: RFC 6726, “FLUTE – File Delivery over Unidirectional Transport,” Internet/
Engineering Task Force, Reston, VA, November, 2012./
http://tools.ietf.org/html/rfc6726/
ATSC A/331:2023-10 Signaling, Deli/
[32] IETF: RFC 7231, “Hypertext Transfer Protocol — HTTP/1.1,” Internet Engineering Task/
Force, Reston, VA, June 2014./
http://tools.ietf.org/html/rfc7231/
[33] IETF: BCP 47, “Tags for Identifying Languages,” Internet Engineering Task Force, Reston,/
VA, September 2009./
https://tools.ietf.org/html/bcp47/
[34] ISO/IEC: “Information Technology – Generic coding of moving pictures and associated/
audio – Part 1: Systems,” Doc. ISO/IEC 13818-1:2015, International Organization for/
Standardization/International Electrotechnical Commission, Geneva, Switzerland./
[35] ISO/IEC: “Information technology – Coding of audio-visual objects – Part 12: ISO base/
media file format,” Doc. ISO/IEC 14496-12:2015, International Organization for/
Standardization/International Electrotechnical Commission, Geneva, Switzerland./
[36] ISO/IEC: “Information technology – Coding of audio-visual objects – Part 15: Carriage of/
network abstraction layer (NAL) unit structured video in ISO base media file format,” Doc./
ISO/IEC 14496-15:2014 with Cor. 1:2015, International Organization for Standardization//
International Electrotechnical Commission, Geneva, Switzerland./
[37] ISO/IEC: “Information technology – MPEG systems technologies – Part 8: Codingindependent code points,” Doc. ISO/IEC 23001-8:2013, International Organization for/
Standardization/International Electrotechnical Commission, Geneva, Switzerland./
[38] ISO/IEC: “Information technology – High efficiency coding and media delivery in/
heterogeneous environments – Part 1: MPEG media transport (MMT),” Doc. ISO/IEC/
23008-1:2017(E), International Organization for Standardization/ International/
Electrotechnical Commission, Geneva, Switzerland./
[39] ISO/IEC: “Information technology – High efficiency coding and media delivery in/
heterogeneous environments – Part 2: High Efficiency Video Coding,” Doc. ISO/IEC/
23008-2:2015, International Organization for Standardization/ International Electrotechnical/
Commission, Geneva, Switzerland./
[40] ISO/IEC: “Information technology – High efficiency coding and media delivery in/
heterogeneous environments – Part 3: 3D audio,” Doc. 23008-3:2015, with Amendment/
2:2016 and Amendment 3:2017. International Organization for Standardization/International/
Electrotechnical Commission, Geneva, Switzerland./
[41] ITU: “Parameter values for the HDTV standards for production and international programme/
exchange,” ITU-R Recommendation BT.709-5 (2002), International Telecommunications/
Union, Geneva, Switzerland./
[42] SMPTE: “Advertising Digital Identifier (Ad-ID®) Representations,” RP 2092-1:2015,/
Society of Motion Picture and Television Engineers, White Plains, NY./
[43] SMPTE: “Digital Object Identifier (DOI) Name and Entertainment ID Registry (EIDR)/
Identifier Representations,” RP 2079:2013, Society of Motion Picture and Television/
Engineers, White Plains, NY./
[44] W3C: “XML Schema Part 2: Datatypes Second Edition,” W3C Recommendation,/
Worldwide Web Consortium, 28 October 2004./
https://www.w3.org/TR/xmlschema-2//
[45] ISO/IEC 23001-7:2016, “Information technology – MPEG systems technologies – Part 7:/
Common encryption in ISO base media file format files.”/
[46] DASH-IF: “Identifiers / Content Protection”, DASH Industry Forum./
https://dashif.org/identifiers/content_protection//
[47] DASH-IF: IOP V5, Part 6 “Content Protection” DASH Industry Forum./
https://dashif.org/guidelines/iop-v5#part-6-content-protection-and-security/
[48] IETF: RFC 4648, “The Base16, Base32, and Base64 Data Encodings,” Internet Engineering/
Task Force, Reston, VA, October 2006./
https://www.rfc-editor.org/info/rfc4648
|
|
9.
|
Qualification of
ATSC:
|
|
|
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
