1、 Copyright 2013 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved February 5, 2013 Table of Contents Page Foreword . 2 Intellectual Property 2 Introduction . 2 1 Scope . 3 2 Conformance Notation . 3 3 Normative References . 4 4
2、Glossary of Terms 4 5 Payload Identifier Packet Definition . 5 6 Payload Identifier Specification and Carriage 11 Annex A Payload Identifier Assignments Process (Normative) 14 Annex B Payload identifier Definitions for Existing Interfaces (Normative) 16 Annex C Historical Payload Identifier Definiti
3、ons for Existing Interfaces (Normative) 21 Annex D Mapping the Payload Identifier from an HANC Packet to a KLV Packet According to the Data Encoding Protocol Defined in SMPTE ST 336 (Informative) . 25 Annex E Bibliography (Informative) . 27 Page 1 of 28 pages SMPTE ST 352:2013 Revision of SMPTE ST 3
4、52:2011 SMPTE STANDARD Payload Identification Codes For Serial Digital Interfaces SMPTE ST 352:2013 Page 2 of 28 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the Uni
5、ted States of America, SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices, and Engineering Guidelines, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all with a bona fide inter
6、est in their work. SMPTE cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in Part XIII of its Operations Manual. SMPTE ST 352 was prepared by Technology Committee 32NF. Intellectua
7、l Property At the time of publication no notice had been received by SMPTE claiming patent rights essential to the implementation of this Standard. However, attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. SMPTE shall not be held r
8、esponsible for identifying any or all such patent rights. Introduction This section is entirely informative and does not form an integral part of this document. This standard defines the structure of the 4-byte payload identifier that is used to describe aspects of the payload carried on the SMPTE S
9、erial Digital Interface (SDI). The payload identifier is transmitted as a SMPTE ST 291-1 ancillary data packet. SMPTE ST 352:2013 Page 3 of 28 pages 1 Scope This standard defines the specification of a 4-byte payload identifier that describes aspects of the payload carried on the SMPTE Serial Digita
10、l Interface (SDI) such as: the digital interface standard; picture rate; sampling structure; aspect ratio; colorimetry; bit depth and channel or link assignment. Other application specific aspects of the payload such as audio channel usage, may optionally be described in application specific documen
11、ts that reference SMPTE ST 352. The payload identifier is applicable to all serial digital interfaces and all payloads that produce a directly viewable image on a display device. Furthermore, the viewable image must be a recognizable representation of the source image content. The payload identifier
12、 is mandatory for some reference standards and optional in other reference standards. Refer to the applicable reference standards for further information on mandatory or optional usage of the SMPTE ST 352 payload identifier. The standard defines how the payload identifier is placed into a 10-bit anc
13、illary data packet according to SMPTE ST 291-1. It also specifies the repetition rate of the ancillary data packet, and provides the preferred horizontal and vertical location for the placement of the packet in different digital interfaces. The standard defines values for some of the bit fields of e
14、ach byte of the 4-byte payload identifier, although the values for other bit fields can have custom definitions. The standard also defines the Payload Identification Code assignment process and associated on-line register for Byte 1 Values. See Annex A for details on how to register new values. Anne
15、x B and Annex C define the assigned Payload Identification codes and byte 2, 3 and 4 values for legacy systems. Annex D shows the mapping of the payload identifier from the ancillary data packet structure of SMPTE ST 291-1 to the K-L-V data structure of SMPTE ST 336 as a fixed-length data pack. 2 Co
16、nformance Notation Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: “shall“, “should“, or “may“. Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or
17、added editorially without affecting interoperability. Informative text does not contain any conformance keywords. All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as “Informative“ or individual paragraphs that start with “Note:” The keywor
18、ds “shall“ and “shall not“ indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted. The keywords, “should“ and “should not“ indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning o
19、r excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. SMPTE ST 352:2013 Page 4 of 28 pages The keywords “may“ and “need not“ indicate courses of acti
20、on permissible within the limits of the document. The keyword “Reserved,” indicates a provision that is not defined at this time, shall not be used, and may be defined in the future. The keyword “forbidden” indicates “Reserved” and in addition indicates that the provision will never be defined in th
21、e future. 3 Normative References The following standard contains provisions which, through reference in this text, constitute provisions of this standard. At the time of publications, the editions indicated were valid. All standards are subject to revision and parties to agreements based on this sta
22、ndard are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. SMPTE ST 291-1:2011, Ancillary Data Packet and Space Formatting 4 Glossary of Terms 4.1 Channel In some cases, a digital interface offers sufficient capacity to be able to carry
23、more than one payload. In this case, each payload becomes a channel of the digital interface. 4.2 Interface Transport The data structure defined by an interface for the purpose of synchronizing the transport words at the receiver. This comprises primarily of the EAV and SAV words. The transport data
24、 is usually expressed as a 10 bit word. 4.3 Link In some cases, the picture raster exceeds the capacity available at the digital interface. In these cases, two or more digital interfaces can be used to provide the total capacity required where each digital interface is a single link of the combined
25、interface set. 4.4 Payload The picture, or part of a picture, carried in the active picture area of a digital interface and comprising a matrix of horizontal and vertical pixels. The matrix usually comprises a multiplex of luma and color difference components that can be viewed on a display device a
26、s a recognizable representation of the source image content. The picture can be a part picture or be a combination of small pictures. The picture does not need to use all the bits of the interface although those bits that are not used must be defined. 4.5 Picture Raster The matrix of samples that re
27、presents a digital video picture. 4.6 Picture Rate The Picture Rate value is the frame rate of the originating source image. 4.7 Recommended Throughout this standard the term Recommended is intended to indicate a preferred usage of bit fields. Specific applications may deviate from the recommended u
28、sage. SMPTE ST 352:2013 Page 5 of 28 pages 4.8 Reserved Throughout this standard the term Reserved is intended to indicate that values are undefined, or may be defined in application specific documents. The default value for Reserved is 0. 4.9 Required Throughout this standard the term Required is i
29、ntended to indicate a mandatory usage of bit fields. Specific applications may not deviate from the required usage. 4.10 Sampling Refers to the horizontal arrangement of picture samples, notably the arrangement of multiplexing the various luma, color difference and other data samples. 4.11 Scanning
30、This is the action of reading the data structure of the interface in a predetermined order for transmission. It also refers to the mapping of the picture raster to the interface for transmission. The scanning of the picture raster and the interface transport are often closely related, the notable ex
31、ceptions being the PsF scanning (progressive picture on an interlaced interface). 5 Payload Identifier Packet Definition The payload identifier shall be 4 bytes long and shall be used to identify the payload carried on a digital interface transport. 5.1 General Payload Identifier Format Table 1a sho
32、ws the overall structure of the payload identifier. Within a specific reference standard or document, a single byte 1 value shall identify payload formats having an identical number of active lines (active line count). The values of the remaining 3 bytes are determined by the specific requirements o
33、f the application, and shall be defined such that: bit-fields identified as Required shall be applied without modification bit-fields identified as Recommended should be applied without modification where applicable bit-fields identified as Reserved may be defined on a case-by-case basis in specific
34、 application standards or other documents that reference SMPTE ST 352. It should be noted therefore that some of the definitions in Table 1b and the subsequent definition of specific bit fields that follow are provisions only and that the actual definition may vary on a case by case basis depending
35、on the value given in byte 1. Decoders shall not assume that the definitions in Table 1b and the following sections are the only provisions for bytes 2, 3 and 4. Table 1c shows how each byte is formatted into a complete 10-bit ancillary data packet. The precise definition of all payload identifiers
36、defined prior to 2008 and not contained in a separate reference standard, are documented in Annex B and Annex C of this standard. Precise definitions for bytes 2, 3 and 4 of payload identifiers defined since 2008 shall be provided for each application in the reference standard that specifies the pay
37、load. SMPTE ST 352:2013 Page 6 of 28 pages Table 1a Generalized payload identifier byte definitions for digital transports Bits Byte 1 Byte 2 Byte 3 Byte 4 Bit 7 Version identifier Application specific (line or picture related information) Application specific (sampling or aspect ratio related infor
38、mation) Application specific (channel assignment, bit depth related or other information) Bit 6 Payload and digital interface standards Bit 5 Bit 4 Bit 3 Picture rate Sampling structure identification Bit 2 Bit 1 Bit 0 Table 1b Default payload identifier field definitions Bits Byte 2 Byte 3 Byte 4 B
39、it 7 (Required) Interlaced (0) or progressive (1) transport (Recommended) Image aspect ratio 4:3 (0) or 16:9 (1) (Recommended) Channel assignment Single-link or ch1 of multi-channel (0h), ch2 of multi-channel (1h), ch3 of multi-channel (2h), ch4 of multi-channel (3h), ch5 of multi-channel (4h), ch6
40、of multi-channel (5h), ch7 of multi-channel (6h) ch8 of multi-channel (7h) Bit 6 (Required) Interlaced (0) or progressive (1) picture Reserved Bit 5 Reserved Reserved Bit 4 Reserved Reserved Reserved Bit 3 (Required) Picture rate (Required) Sampling structure identification Reserved Bit 2 Reserved B
41、it 1 (Recommended) Bit depth 8-bit (0h), 10-bit (1h) or 12-bit (2h), Reserved (3h) Bit 0 SMPTE ST 352:2013 Page 7 of 28 pages Table 1c Payload identifier ancillary data packet format b9 (MSB) b8 b7 b6 b5 b4 b3 b2 b1 b0 (LSB) Ancillary data flag (ADF) 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
42、 1 1 1 1 1 Data ID (DID) not b8 EP 0 1 0 0 0 0 0 1 Secondary data ID (SDID) not b8 EP 0 0 0 0 0 0 0 1 Data count (DC) not b8 EP 0 0 0 0 0 1 0 0 Payload (byte 1) not b8 EP Version ID Payload identifier Picture rate and scanning (byte 2) not b8 EP I/P transport I/P picture 0 0 Picture rate Sampling st
43、ructure (byte 3) not b8 EP 4:3/16:9 0 0 0 Sampling structure Special options (byte 4) not b8 EP Channel 0 0 0 Bit depth Checksum not b8 Sum of b0b8 of DID through to payload byte 4. EP = even parity for b0 through b7. Notes: 1. Since the payload bytes use the two LSB.s of the 10-bit packet format, c
44、are needs to be taken when handling the payload identifier in 8-bit systems. 2. Equipment designed in compliance with previous revisions of this standard might not adhere to the bit 8 and bit 9 formatting shown in Table 1c, the payload information is conveyed by b7 through b0 only. 5.2 Byte 1: Paylo
45、ad and Digital Interface Identification This first byte shall identify the combination of payload format and digital interface transport. Within a specific reference standard or document the byte 1 value shall identify payload formats having an identical number of active lines (active line count). W
46、here 2 or more active line counts exist within a single reference standard or document, a separate byte 1 value shall be assigned to each format (e.g. SMPTE ST 292-1). These provisions shall not exclude standards or documents from organizations other than SMPTE using the same byte 1 value as the SMP
47、TE standard for the same interface specification. Some digital interfaces can carry a number of different payload formats at the same transport bit rate. Furthermore, payload formats can now be mapped onto several digital interface transports. Within a specific reference standard or document (e.g. S
48、MPTE ST 372), the byte 1 value shall also identify the digital interface transport mapping structure. Where 2 or more digital interface transport mapping structures exist within a single reference standard or document (e.g. SMPTE ST 425-1 or Recommendation ITU-R BT.1120), a separate byte 1 value sha
49、ll be assigned to combinations of payload format and mapping structure. By identifying the combination of both the payload format and its associated digital interface, it is possible to correctly identify the supported format and mappings purely from inspection of the first byte of the payload identifier. Implementers should be aware that some legacy implementations complying with previous version of this standard may not comply with the full form of the above provision. SMPTE ST 352:2013
