SMPTE RP 205-2014 Application of Unique Material Identifiers in Production and Broadcast Environments.pdf

1、 Copyright 2014 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved August 15, 2014 Table of Contents Page Foreword . 3 Intellectual Property 3 Introduction 3 1 Scope . 5 2 Conformance Notation . 5 3 Normative References . 5 4 UMI

2、D Application Principles . 6 4.1 Introduction 6 4.2 Principle 1 Definition . 6 4.3 Principle 2 UMID Creation 7 4.4 Principle 3 UMID Integrity . 7 4.5 Principle 4 UMID Identification 8 4.6 Principle 5 UMID Inheritance 8 4.7 Principle 6 Extended UMID . 8 4.8 Principle 7 Source Pack 9 5 UMID-Aware Appl

3、ication Considerations . 9 5.1 Introduction 9 5.2 UMID Managed Domain. 9 5.2.1 What is the UMID Managed Domain? 9 5.2.2 Material Manager Requirements. 10 5.3 UMID Material Number as a Dumb Number 11 5.4 UMID as a Wrapper for the Globally Unique Value . 12 5.5 UMID for Abstract Original Material . 12

4、 5.6 Identical Materials via UMID 13 5.7 UMID for Growing Material. 14 Annex A UMID Basics (Informative) 16 A.1 Introduction 16 A.2 UMID Format 16 Annex B To Maintain the UMID Managed Domain (Informative). 18 B.1 Introduction 18 Page 1 of 44 pages SMPTE RP 205:2014 Revision of SMPTE RP 205:2009 SMPT

5、E RECOMMENDED PRACTICE Application of Unique Material Identifiers in Production and Broadcast Environments SMPTE RP 205:2014 Page 2 of 44 pages B.2 Behaviors of Material Manager . 18 B.2.1 New material creation in the domain . 18 B.2.2 Existing material deletion in the domain . 18 B.2.3 Existing mat

6、erial copy or move within the domain 18 B.2.4 New material import into the domain 19 B.2.5 Existing material export from the domain 20 B.2.6 Existing material modification at its essence in the domain 20 B.2.7 Existing material modification at its metadata in the domain 20 B.2.8 Existing material ba

7、ckup and restore 21 B.2.9 Material managed by multiple material managers 21 Annex C UMID Application Examples (Informative) . 23 C.1 Introduction 23 C.2 UMID Application Basics . 23 C.2.1 Two distinct functions of UMID 23 C.2.2 Exclusive UMID functions 24 C.2.3 Overview of UMID treatments in a media

8、 production workflow chain . 24 C.3 Simultaneous Multiple Material Creations for Offline/Online Edits 26 C.4 UMID based Material Search 28 C.5 Cooperation of Multiple MAMS (Media Asset Management System) . 29 C.6 Common Material Identifier in a Best-of-Breed Media Production System . 30 C.7 Globally

9、 Distributed Material Management . 31 C.8 Additional Metadata Search for a Material at Hand. 32 C.9 Loose Coupling between Application and Media Layers 32 C.10 UMID Applications in Traditional VTR/SDI Environment . 34 C.10.1 Introduction 34 C.10.2 What is material in tradition VTR/SDI environment? .

10、 34 C.10.3 Two functions of UMID in traditional VTR/SDI environment 35 C.10.4 Extended UMID and Source Pack . 37 C.10.5 Source Pack applications 37 C.10.6 Limitation of UMID applications for traditional VTR/SDI environment . 39 Annex D Frequently Asked Questions (Informative) 41 Annex E Bibliography

11、 (Informative) 44 SMPTE RP 205:2014 Page 3 of 44 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America, SMPTE has members in over 80 countries on

12、 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 interest in their work. SMPTE cooperates closely with other standards

13、-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in its Standards Operations Manual. SMPTE RP 205 was prepared by Technology Committee 30MR on Metadata and Registers. Intellectual Property SMPTE draws attention to the f

14、act that it is claimed that compliance with this Standard may involve the use of one or more patents or other intellectual property rights (collectively, “IPR“). The Society takes no position concerning the evidence, validity, or scope of this IPR. Each holder of claimed IPR has assured the Society

15、that it is willing to License all IPR it owns, and any third party IPR it has the right to sublicense, that is essential to the implementation of this Standard to those (Members and non-Members alike) desiring to implement this Standard under reasonable terms and conditions, demonstrably free of dis

16、crimination. Each holder of claimed IPR has filed a statement to such effect with SMPTE. Information may be obtained from the Director, Standards using the UMID as a common unique material identifier across a heterogeneous system, comprised of numerous media products from different vendors. However,

17、 in order to realize this, a universal rule set for UMID applications that provides a means by which the integrity of a UMID attached to a given material asset can be trusted, regardless of the products used to create the UMID and/or attach the UMID to the material asset, is required. Unfortunately,

18、 SMPTE ST 330 does not specify nor provide the set of rules required to facilitate the trust framework to guarantee the integrity of a UMID. Therefore additional regulations and rules must be defined to create this trust framework. In this Recommended Practice, the UMID Application Principles are sp

19、ecified as a set of rules applicable to all UMID applications, which establishes a trust framework for UMID usage. If a media product strictly adheres to the UMID Application Principles, the integrity of the UMIDs attached to material obtained from that product can be trusted, such applications and

20、products are known as “UMID-aware”. Since the means by which the UMID Application Principles are applied depend on the type of product and the type of recording medium used, the Principles are specified in terms of “What to Achieve” versus “How to Achieve Them”, and how they are achieved is left up

21、to the implementer of the product. Please refer to Annex B for a typical implementation example of the UMID Application Principles using a UMID as a globally unique material identifier. Furthermore, since SMPTE ST 330 allows UMIDs to be used for purposes other than globally unique material identity,

22、 rules for these additional purposes have been defined within the UMID Application Principles. In summary, the purpose of this Recommended Practice is to establish a common trust framework by which applications can utilize UMIDs in a consistent, unambiguous, and well-understood manner that allows fo

23、r the maintenance of the logical relationships between material assets, their metadata, and their instances. SMPTE RP 205:2014 Page 5 of 44 pages 1 Scope This Recommended Practice defines the UMID Application Principles that must constitute the basis of any UMID application, and recommends several p

24、oints on UMID use that must be carefully considered for each application. It also provides informative text on the UMID basics, how to implement the UMID Application Principles for a UMID as a globally unique material identifier, various UMID application examples, and frequently asked questions on t

25、he UMID applications. 2 Conformance 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 ca

26、n be removed, changed, or 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 sta

27、rt with “Note:” The keywords “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 suit

28、able, without mentioning or 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. The keywords “may“ and “need not“ indicate courses of action permissi

29、ble 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 the future. A

30、conformant implementation according to this document is one that includes all mandatory provisions (“shall“) and, if implemented, all recommended provisions (“should“) as described. A conformant implementation need not implement optional provisions (“may“) and need not implement them as described. U

31、nless otherwise specified, the order of precedence of the types of normative information in this document shall be as follows: Normative prose shall be the authoritative definition; Tables shall be next; followed by formal languages; then figures; and then any other language forms. 3 Normative Refer

32、ences Note: All references in this document to other SMPTE documents use the current numbering style (e.g. SMPTE ST 298:2009) although, during a transitional phase, the document as published (printed or PDF) may bear an older designation (such as SMPTE 298-2009). Documents with the same root number

33、(e.g. 298) and publication year (e.g. 2009) are functionally identical. The following standards contain provisions which, through reference in this text, constitute provisions of this recommended practice. At the time of publication, the editions indicated were valid. All standards are subject to re

34、vision, and parties to agreements based on this recommended practice are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below. SMPTE ST 298:2009, Universal Labels for Unique Identification of Digital Data SMPTE ST 330:2011, Unique Material Id

35、entifier (UMID) SMPTE RP 205:2014 Page 6 of 44 pages 4 UMID Application Principles 4.1 Introduction This section defines a set of UMID Application Principles. Except for this and Section 4.2, each subsection starts with the statement of the principle, followed by implications that will help the read

36、er to obtain a better understanding of the statement. 4.2 Principle 1 Definitions For the purpose of describing the UMID Application Principles, the capitalized terms used in the statements below shall have the respective meanings defined as follows: Basic UMID shall mean the UMID of 32-byte long co

37、mposed of its12-byte UL, the 1-byte length field, 3-byte Instance Number Field and 16-byte Material Number Field, specified in SMPTE ST 330. While this term may represent either on its own or the first 32-byte of Extended UMID, the phrase “the Basic part of Extended UMID” may be used to refer to the

38、 latter case for its further clarification if needed. Extended UMID shall mean the UMID of 64-byte long composed of its 32-byte Basic UMID followed by 32-byte Source Pack, used to identify a finer granularity than is identified by its Basic part, specified in SMPTE ST 330. Instance shall mean a spec

39、ific item of stored material(s) that shares the same Material Number regardless of its Instance Number value. Instance Number shall mean the value in the Instance Number Field of the UMID. The Instance Number shall take a value of zero for the original Material and a non-zero value for any copy or d

40、erivation of the original Material. Note: SMPTE ST 330 defines several methods by which the Instance Number value is created. The uniqueness of an Instance Number value is guaranteed only within a predefined closed domain where the uniqueness of an Instance Number is appropriately controlled by usin

41、g such as local registration. In open domains, the assignment of a new non-zero Instance Number value cannot guarantee a unique value; i.e., there is a small, but finite, probability that duplicate values can occur. Instance Number Field shall mean the 24 bits field using bytes 14th-16th of the UMID

42、 as specified in SMPTE ST 330. Instance Number Generation Method Field shall mean the field of the 4 least significant bits (LSBs) of byte 12th of the UMID UL used to identify the method to create the Instance Number field value as specified in SMPTE ST 330. Note that the special value of 15 (Fh) is

43、 reserved for this field in order for the UMID with it to be used to signal a live-stream source that has never been fully recorded (and hence has never been instantiated as a persistent and deterministic form of material) rather than to be used as a unique material identifier. Material shall mean a

44、 persistent and deterministic form of unique set of audio and/or visual essence playable on a single timeline, which may be a single item or a set of synchronized items, which shall be continuous along the timeline. Material, often preceded with the term “original”, shall be globally uniquely identi

45、fied by a UMID with a newly created Material Number together with zero Instance Number, whose global uniqueness is algorithmically guaranteed according to SMPTE ST 330. The essence in the Material may either be a playable bit stream, or an abstract source from which a playable bit stream may be crea

46、ted. Material Number shall mean a non-zero value for the Material Number Field in the UMID. Material Number Field shall mean the field of bytes 17th-32nd of UMID as specified in SMPTE ST 330. Material Unit shall mean the quantum of material composed as its cyclic sampling structure. SMPTE RP 205:201

47、4 Page 7 of 44 pages Source Pack shall mean the last 32 bytes of the Extended UMID, which contains the information of “when”, “where” and “who” has created the material, as specified in SMPTE ST 330. UL shall mean the SMPTE Universal Label specified in SMPTE ST 298, which is truncated to 12 bytes le

48、ngth when used in the UMID format. When the UMID UL is extracted for external use, it shall be padded to 16 bytes by appending 4 bytes of zero value and shall change the value of the label size in byte 2nd from 0Ah to 0Eh. UMID shall mean the Unique Material IDentifier whose format and value creatio

49、n methods are specified in SMPTE ST 330. The UMID may take the form of either 32-byte Basic UMID or 64-byte Extended UMID, where the Extended UMID is still a UMID, but the one extended with additional 32 bytes of geo-location and other information to form the Source Pack. UMID Managed Domain shall be an authoritative source in which the uniqueness and meaning of a UMIDs Material Number and Instance Number shall be managed and guaranteed. A UMID Managed Domain may range from a single registry, withi