DCI Specs - Digital Cinema Initiatives

More documents

Recommendations

Info

9.4.5. Intra-Theater Communications) shall be issued to each remote SPB atleast every 30 seconds whenever TLS sessions are open. Receipt of aQuerySPB response indicating a "security alert" condition shall be indicative of afaulty SPB, and shall prevent or terminate playback per the DRM requirements ofSection 9.6.1. Digital Rights Management. Once a show has started, failure of aTLS link shall not cause termination of a show (i.e., QuerySPB commands willnot successfully execute, but the show should continue to play if possible).16. Support suite playback enablement (authentication followed by keying) such thatno more than one of each type of SE is enabled (i.e., one LD Block, one ImageMD, one Audio MD), except for content owner-approved special auditoriumsituations employing the use of multiple Link Encryption operations. SMs shallsupport the authentication and keying of multiple Link Encryption operation perthe requirements of Section 9.4.4.1 Multiple Link Encryption Operation.17. The SM shall be “playout aware”, meaning it shall have real-time knowledge ofthe occurrence of playout start and end periods. Secure Processing Blockbehavior and suite implementations shall permit the SM to prevent or terminateplayback upon the occurrence of a suite SPB substitution or addition since theprevious suite authentication and/or ITM status query. The SMs shall respond tosuch a change by immediately purging all content and link encryption keys,terminating and re-establishing: a) TLS sessions (and re-authenticating thesuite), and b) suite playability conditions (KDM prerequisites, SPB queries andkey loads). Perform the security equipment integrity checks and suite re-keyingper item 11 above prior to the next playback.18. Perform and log all the above functions under the operational (not security)control of the particular SMS designated by the exhibition operator per Section9.4.2.5 Screen Management System (SMS).9.4.3.6. Functional Requirements for Secure Processing Block SystemsEach type 1 Secure Processing Block (SPB) can be considered an SPB system, since itoperates as a collection of SEs. Similarly, the projector also has its associated type 2SPB, which does not contain SEs, but fulfills security functions as described below.(Secure Processing Block types are defined in Section 9.4.2.2 The Secure ProcessingBlock (SPB).) In order to facilitate a composition playback, SPBs constituting the suitemust work in a coordinated fashion under control of the suite’s SM, contained within theImage Media Block (IMB).Functional requirements of the SM are defined in Section 9.4.3.5 Functions of theSecurity Manager (SM). This section defines the functions and operational requirementsfor the following SPB systems:DCI Digital Cinema System Specification v.1.2 Page 112
• Projector Secure Processing Block (SPB)• Link Decryptor Block (LDB) Secure Processing Block (SPB)• Image Media Block (IMB) Secure Processing Block (SPB)In addition to the specific requirements given for SPB systems in this section, all SPBsystems shall meet the behavior requirements of Section 9.6.1 Digital RightsManagement.9.4.3.6.1. Normative Requirements: Projector Secure Processing BlockFrom a security perspective, a projection system consists of the projector SecureProcessing Blocks (SPB) type 2 and its companion SPB, which will be either the LinkDecryptor Block (LDB) or Image Media Block (IMB).The following are the normative requirements for the projector Secure ProcessingBlock (SPB):1. The projector’s companion SPB (Link Decryptor Block or Image Media Block)shall be physically inside of, or otherwise mechanically connected to, theprojector Secure Processing Block (SPB).2. The projector and Link Decryptor Block (LDB) Secure Processing Blocks(SPBs) shall be authenticated to the SM. However, authentication does notensure that the two SPBs are mechanically connected to each other orensure that an IMB/projector system is mechanically connected. Therefore,an electronic marriage shall take place upon installation of an IMB or LDBprojector pair. This physical/electrical connection shall be battery-backed andmonitored 24/7 by the companion SPB and, if broken, shall require a reinstallation(re-marriage) process.Breaking the marriage shall not zero the projector SPB long term identitykeys (RSA private), see item 7 below.3. Projector maintenance may involve a marriage (or re-marriage) event, oraccess to the projector SPB or both. To support projector maintenance, theprojector SPB may be serviceable, but access is security-sensitive becauseof the possibility of tampering during service access.Once a projector is installed, projector SPB access door “open”, access door“close”, “marriage” and “marriage break” events shall be logged, and the“AuthID” token (see Section 9.4.6.3.8 Log Record Information) shall indicatethe responsible exhibition party that executed (or supervised) the event(s).Once a projector is installed, all relevant projector SPB events of Section9.4.6.3 Logging Subsystem shall be logged 24/7 under both powered and unpoweredconditions.Playback shall not be permitted and shall terminate if the projectorcompanionSPB marriage is broken, or a projector SPB access door is openTo avoid the complexity of retaining its own log records (and the associatedneed for a clock and battery-backed persistence), the projector SPB may relyupon its companion type 1 SPB by sending projector SPB log event dataacross the marriage electrical interface to the companion SPB. It isencouraged but not mandatory that projector SPB logs be recorded while aprojector is not installed (i.e., not connected to its companion SPB).DCI Digital Cinema System Specification v.1.2 Page 113
Page 1 and 2:
Digital Cinema Initiatives, LLCDigi
Page 3 and 4:
Table of Contents1. OVERVIEW 151.1.
Page 5 and 6:
5.2.2. Packaging Fundamental Requir
Page 8 and 9:
7.5.5.1. Introduction..............
Page 10 and 11:
9.4.2.5. Screen Management System (
Page 12 and 13:
Table of FiguresFigure 1: System Ov
Page 14 and 15:
THIS PAGE LEFT BLANK INTENTIONALLYD
Page 16 and 17:
equirements for encrypting the esse
Page 18 and 19:
• This document specifies a basel
Page 20 and 21:
DCI Digital Cinema System Specifica
Page 22 and 23:
2.1.1. Major System Concepts2.1.1.1
Page 24 and 25:
2.1.1.8. ReelsFeature films have be
Page 26 and 27:
Metadata within the DCDM provides a
Page 28 and 29:
3.2.1.6. Transfer FunctionThe CIE X
Page 30 and 31:
The information, as shown in Table
Page 32 and 33:
AES Pair#/Ch# Channel # Label / Nam
Page 34 and 35:
3.3.4. File Format3.3.4.1. GeneralT
Page 36 and 37:
3.4.3. Timed Text Concepts and Requ
Page 38 and 39:
Page 40 and 41:
• All decoders shall decode each
Page 42 and 43:
Page 44 and 45:
5.2.2.3. InteroperableThe Packaging
Page 46 and 47:
Figure 6: Example Show PlaylistThe
Page 48 and 49:
Length (Value Length), followed by
Page 50 and 51:
which it was stopped or paused. It
Page 52 and 53:
5.3.4.2. Frame BoundariesThe Audio
Page 54 and 55:
• Rating• Aspect Ratio• Image
Page 56 and 57:
• Annotation Text parameter (opti
Page 58 and 59:
Page 60 and 61:
7.2.3.1. ReliabilityA key part of t
Page 62 and 63: • Country• Rating• Aspect Rat
Page 64 and 65: facility, while the system is in op
Page 66 and 67: Exhibitor and the Distributor, data
Page 68 and 69: 7.5.2.2. Ingest InterfacesExcept fo
Page 70 and 71: (channels) * hours * 60 min/hour *
Page 72 and 73: 7.5.4.2.4. UnpackagingAny packaged
Page 74 and 75: 7.5.6. Audio System7.5.6.1. Introdu
Page 76 and 77: made up of Theater System devices a
Page 78 and 79: DCI Digital Cinema System Specifica
Page 80 and 81: 8.2.2.3. Alternative ContentThe pro
Page 82 and 83: With the projector turned off or wi
Page 84 and 85: Image ParametersNominal(Projected I
Page 86 and 87: Input Code Values Output Chromatici
Page 88 and 89: 8.4. Projector Interfaces8.4.1. Int
Page 90 and 91: • Lens Shift Up / Down• Lamp Mo
Page 92 and 93: • Essence Encryption and Cryptogr
Page 94 and 95: content keys and Trusted Device Lis
Page 96 and 97: Figure 14: Digital Cinema Security
Page 98 and 99: Figure 15 presents the two fundamen
Page 100 and 101: DCI Digital Cinema System Specifica
Page 102 and 103: 9.4.2.3. Media Blocks (MBs)The term
Page 104 and 105: which TLS-based authentication alon
Page 106 and 107: working with the security infrastru
Page 108 and 109: Figure 18: Show Playback Overview9.
Page 110 and 111: a. Playout shall be fully supported
Page 114 and 115: 4. Projector SPB designs shall not
Page 116 and 117: the event, and zero all Critical Se
Page 118 and 119: window) shall be UTC.Security Manag
Page 120 and 121: . The SM shall independently authen
Page 122 and 123: 6. No broadcast RRP commands shall
Page 124 and 125: Functions of the Security Manager (
Page 126 and 127: Note: DCI reserves the right, at so
Page 128 and 129: • Is required to survive camcorde
Page 130 and 131: • Log Data - Security event infor
Page 132 and 133: using the GetEventList and GetEvent
Page 134 and 135: failure) per Section 9.6.1.3 Digita
Page 136 and 137: • Secure Silicon -Sensitive data
Page 138 and 139: secure silicon chip, input/output s
Page 140 and 141: FIPS 140-2 level 3 devices provide
Page 142 and 143: to the appropriate Section 9.4.5.2.
Page 144 and 145: those under the control of the Secu
Page 146 and 147: Security Managers (SMs) other than
Page 148 and 149: The above RSA asymmetric protection
Page 150 and 151: THIS PAGE LEFT BLANK INTENTIONALLYD
Page 152 and 153: CPRL Acronym for Component Position
Page 154 and 155: LTCMain TitlesMBMDMEMetadataMTBFMXF
Page 156: TDLTimed TextTLMTLSTMSTrack FileUDP
show all

DCI Specs - Digital Cinema Initiatives

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?