hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.3.5.6.5 Index configuration | The value of ic_instance_info_in_event_flag shall be equal to 0. The value of ic_grouping_index_in_event_flag shall be equal to 1. The value of ic_multi_element_event_flag shall be equal to 0. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.3.5.7 SDP index | 5.3.5.7.1 General Both initial SDP descriptions and SDP updates, which can be provided by mechanisms such as those, for example, specified in TS 102 591 [11], are stored with SDP indexes specified in this clause. There shall be one movie-level index track containing SDP indexes in any DVB file that contains RTP recepti... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.3.5.8 Proprietary indexes | 5.3.5.8.1 General This provides a framework within which proprietary indexes can be stored. As the index mechanism does not use boxes, this provides the framework to store the uuid. NOTE: A proprietary index may use a specified 4CC, assuming that this has been suitably registered. 5.3.5.8.2 4CC This event shall be sign... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.3.5.9 Error occurrence event | 5.3.5.9.1 General The error occurrence event is used to signal locations in the file where it is know that data is lost. Examples of this include when a transmission signal failed, or where a storage device suffered failure when content was moved or copied. The error shall indicate the first good packet after an error ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.3.5.10 Null index | 5.3.5.10.1 General The null index provides a generic mechanism for a range of operations such as where it is desirable to delete an index, but not desirable to alter the index data, or where it is desirable to insert space for an index. 5.3.5.10.2 4CC This event shall be signalled by the 4CC 'null'. 5.3.5.10.3 Index co... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4 Content protection | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1 Storage of CPCM Protected Content | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.1 Introduction | This clause specifies the use of the mechanism defined in clause 5.2.1.3 to signal CPCM protection of MPEG-2 TS reception hint tracks, and carry the content licence associated with the protection. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2 Usage of the protected scheme information box | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.1 Presence of sub-boxes | The ISO base file format defines some of the sub-boxes of the 'sinf' box as optional. In the scope of the present document, the following boxes shall be present: • the original format box 'frma'; • the scheme type box 'schm'. In the scope of the present document, the following boxes may be present: • the scheme informa... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.2 CPCM scheme type | The scheme type box 'schm' identifies the protection scheme used to protect the track and carries information about the type and version of the scheme. For CPCM, the scheme_type field shall take the value 'cpcm' to signal the storage of CPCM protected content. A scheme_version of 1 is used to signal the CPCM encapsulat... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.3 CPCM scheme information | The ISO base file format defines the scheme information box as a container box for scheme specific information. For CPCM, this box contains the CPCM Content Licence. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.4 CPCM licence box | 5.4.1.2.4.1 Definition The CPCM licence box 'clic' is a sub-box of the scheme box 'schi'. It stores a CPCM content licence in an opaque container. ETSI ETSI TS 102 833 V1.2.1 (2011-03) 56 5.4.1.2.4.2 Syntax class CPCMLicenceBox extends FullBox('clic', version, flags) { if (version == 0) { unsigned int(8) cpcm_licence_d... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.5 CPCM auxiliary data box | 5.4.1.2.5.1 Definition The CPCM auxiliary data box 'caux' is a sub-box of the scheme box 'schi'. It either stores CPCM auxiliary data in an opaque container, or contains the identifier of the metadata item that contains the auxiliary data. It is recommended that auxiliary data larger than 5 kilobytes is stored as a met... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.6 CPCM auxiliary data metadata handler box | The handler type for CPCM auxiliary data held in a metadata box shall be 'cpad'. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.7 CPCM auxiliary data metadata primary item box | The primary item box shall be present in the metadata box with handler type 'cpad'. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.8 CPCM auxiliary data metadata item information box | The Item information box need not be present, may be ignored. ETSI ETSI TS 102 833 V1.2.1 (2011-03) 57 |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.9 CPCM auxiliary data metadata item location box | The metadata box with handler type 'cpad' shall contain an item location box. The item_ID shall be unique within the file. Any item_id(s) listed in 'caux' box(es) shall have an entry in an item location box associated with a handler type of 'cpad'. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.10 Data information box | The data information box shall be present only if the CPCM auxiliary data is stored externally to the file containing the metadata box with handler type 'cpad'. NOTE: Certain brand constraints may prevent the auxiliary data from being stored externally. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.2.11 Location of CPCM auxiliary data metadata | It is recommended that the location of the metadata container box containing the auxiliary data is placed in the file in advance of the content that it protects. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.3 Supporting multiple CPCM content items | If a file contains more than one CPCM protected content item, each new CPCM content item shall correspond to a new protected MPEG-2 TS reception hint track sample entry. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.1.4 Supporting CPCM Revocation Lists | CPCM Revocation Lists shall be stored in the SRM mechanism as detailed in clause 5.4.6. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.2 Key message reception tracks | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.2.1 Introduction (informative) | This clause specifies the reception track format for key messages. The key track is based on a timed metadata track. It stores key messages that are transmitted in parallel to the audiovisual content. It can be used for any IP based broadcast/multicast system, like DVB-H or OMA BCAST. It can be linked either to a RTP r... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.2.2 Key message reception track format | The key message reception track is based on a timed metadata track. It is used to store key messages that are transmitted in parallel to the audiovisual content. A track reference of type 'cdsc' shall be used to connect each key message reception track to the associated media track, either an RTP reception hint track o... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.2.3 Sample description format | 5.4.2.3.1 Description The entry format in the sample description for the key messages reception tracks is 'keym'. The KeyMessageReceptionSampleEntry is derived from the MetadataSampleEntry. The format of the key sample is signalled by key_sample_type and key_sample_version. Additional boxes may be available at the end ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.2.4 Sample format | 5.4.2.4.1 Description Each sample in the key message reception track represents one key message without additional headers. For instance, if the key messages are directly encapsulated in UDP packets without additional headers, the sample contains the plain UDP packet payload. Sample times of the key messages are usuall... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.3 Key stream storage of protected DVB-H IPDC services | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.3.1 Introduction (informative) | The IP layer of DVB-H is using RTP streams for transmission of the audiovisual content. DVB-H Service Purchase and Protection [9] specifies protection of DVB-H services and encryption of the packetized audiovisual content. Two alternatives are available for the key management: the Open Security Framework (OSF) and 18Cr... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.3.2 18Crypt (18C) | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.3.2.1 Description | A key message reception track as specified in clause 5.4.2 is used to store the Key Stream Messages (KSM). As specified in TS 102 474 [9], each KSM is sent as one UDP packet. The key messages are received on a dedicated UDP port. Signalling information related to the 18C protection scheme is part of the SDP information... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.3.3 Open Security Framework (OSF) | 5.4.3.3.1 Description A key message reception track as specified in clause 5.4.2 is used to store the Entitlement Control Messages (ECM). The ECMs are received on a dedicated UDP port. As specified in TS 102 474 [9], one UDP packet contains one or more ECMs without any additional header. Signalling information related ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.4 Key tracks and ISMACryp elementary stream media tracks | Key tracks as specified in clause 5.4.2 may also be used in combination with audiovisual elementary stream tracks that are encrypted using ISMACryp [23]. NOTE: ISMACryp is designed in a way that allows depacketization of audiovisual data from RTP payloads to elementary stream access units without decryption. Thus, the ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.5 Proprietary protection schemes | The ISO base file format offers a generic solution to signal that a media track is protected and to store protection scheme related information in the sample description (see clause 8.12 of ISO/IEC 14496-12 [30]). In the case of proprietary protected media tracks, this mechanism shall be used. In the case of proprietar... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.6 System Renewability Messages | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.6.1 Introduction (informative) | System Renewability Messages (SRMs) are a generic way of conveying messages that may be required by systems outside the scope of this file format. These systems may form part of the consumption chain of the content contained in the file, and the passage of the content through these systems may require the presence of t... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.6.2 System Renewability Message container box | 5.4.6.2.1 Description The System Renewability Messages container box 'srmc' may be used to store a list of System Renewability Messages (SRM). If present in the file, the SRM container box shall occur at the top level of the file hierarchy. 5.4.6.2.2 Syntax aligned(8) class SRMContainerBox extends FullBox('srmc', 0, fl... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.6.3 System Renewability Message box | 5.4.6.3.1 Description The System Renewability Message box 'srmb' may be used to store a System Renewability Message (SRM). The format of the SRM and the usage of the SRM are defined by the relevant KMS. ETSI ETSI TS 102 833 V1.2.1 (2011-03) 62 5.4.6.3.2 Syntax aligned(8) class SRMBox extends FullBox('srmb', 0, flags) {... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7 Storage of Key Management Messages | |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7.1 Overview | Key Management Messages (KMM) or Rights Objects (RO) (defined in TS 102 474 [9]), in OSF also known as Entitlement Messages (EMM), contain content/service access rights and enable authorized users to access the Key Stream Messages. They are either infrequently sent in-band or are acquired out-of-band using an interacti... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7.2 Handler box | The handler type for key management messages shall be 'skmm'. There shall be only one metadata box with handler type 'skmm' present in a file. NOTE: This box may contain multiple key messages, and messages for more than one system. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7.3 Primary item box | The primary item box shall be present in the metadata box with handler type 'skmm'. If more than one item exists in the metadata, then the choice of primary item is made by the creator of the file. NOTE: Typically the protection mechanism will identify which is the "primary" item, e.g. which one should be presented to ... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7.4 Item information box | The item information box shall be present in the metadata box with handler type 'skmm', and shall contain one item information entry for each key management message present (and therefore for each item_ID given in the item location box). The item information entry shall have a version of 1, and shall contain at least o... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7.5 Item location box | The metadata box with handler type 'skmm' shall contain an item location box. For each metadata item present, there shall be an entry in the item location box that maps the Key Management Message to an item_ID. Each item_ID shall be unique within the file. NOTE: This means that a given item_ID cannot refer to both a ke... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 5.4.7.6 Data information box | The data information box shall be present only if the Key Management Messages are stored externally to the file containing the metadata box with handler type 'skmm'. ETSI ETSI TS 102 833 V1.2.1 (2011-03) 64 |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 6 Proprietary extensions | It is reasonable to expect that some implementations of the file format will wish to provide proprietary extensions. This clause provides definitions that minimize interoperability problems. Where appropriate, extension mechanisms have already been defined in the clauses above. |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 6.1 General issues | Any extensions shall follow the guidelines in annex C of the ISO base file format [30]. It is recommended that proprietary extensions do not contain standard defined and published boxes. NOTE: Encapsulating standard boxes within a proprietary box may "hide" them from a player, and as such reduce the interoperability (o... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 6.2 Use of UUID | It is strongly recommended that any proprietary extensions use the 4CC 'uuid', as defined in clause 4.2 of ISO/IEC 14496-12 [30]. This mechanism utilizes a 16-byte UUID as defined in ISO/IEC 9834-8 [26] to identify the box type, and this shall be allocated by the body responsible for the proprietary extension. NOTE: Th... |
bb2be2ae3e413728560baab104665eb4 | 102 833 | 6.3 Use of 4CC | No 4CC shall be present in the file that has not been registered with the MPEG-4 Registration Authority, as explained in annex D of ISO/IEC 14496-12 [30]. NOTE: This means that proprietary extensions within a DVB File that do not make use of the 'uuid' mechanism have to be registered. This is to ensure that there are n... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 1 Scope | The present document specifies the Usage State Information (USI) for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. Additionally, the present document specifies USI-related Auxiliary Data that will be carried along with the USI by mechanisms to be specified further by CPCM. N... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 825-1: "Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 1: CPCM Abbreviations, Definitions and Terms". [2] ETSI TS 102 825-4: "Digital Video Broadcasting (DVB); Content... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 101 154: "Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 3 Definitions and abbreviations | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 825-1 [1] apply. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 102 825-1 [1] apply. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4 Usage State Information General Requirements | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.1 Definition and application | The DVB CPCM Usage States Information (USI) is CPCM Content metadata that signals the Authorized Usage for that particular Content Item. Authorized Usage is the permitted usage of CPCM Content, consisting of the set of Usage Rules applied to that Content. Content is data that is to be protected by the CPCM System. This... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.2 CPCM Content Licence | The USI is contained within a higher level DVB CPCM metadata structure called the CPCM Content Licence. The CPCM Content Licence is generated upon Acquisition. The CPCM Content Licence shall include the following fields as defined in TS 102 825-4 [2] some of which may not be systematically populated: • Content Licence ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.3 Secure Binding to Content | The USI of a given Content Item shall be securely bound to its Content Item, i.e. they shall be inextricably linked and no other USI shall be able to be substituted for it except as specifically permitted by compliant behaviour. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.4 Content Entering DVB CPCM System | When Content first enters the DVB CPCM system, at a particular Acquisition Point, the Authorized Usage of that Content shall be determined and then preserved by securely binding it as USI metadata to the Content. The DVB CPCM System shall only Acquire content for which there is an approved Usage Rule mapping, i.e. from... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.5 Content within DVB CPCM System | In the case of a transfer of Content from one DVB CPCM Instance to another DVB CPCM Instance, all of the USI shall be securely conveyed and shall remain securely bound to the Content. Certain USI fields may change through a secure process, for example: • transition from Copy Once to Copy No More; • transition from Zero... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.6 Propagation Controls | The DVB CPCM USI includes a variety of propagation USI that enable Copying, Movement and Viewing of Content within defined groups of DVB CPCM compliant devices. Copying and Movement are controlled together and use the same USI fields. Viewing, or Consumption, can be controlled independently and therefore uses separate ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 4.9 Extensions | The CPCM baseline functionality may be extended where necessary for particular proprietary functionality, or for future additional extended CPCM functionality. This shall be done as described in the CPCM Extension section of TS 102 825-2 [5]. The CPCM System includes the facility for data for extended CPCM functionalit... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 5 Overview of USI Fields | Table 2: Usage State Information Overview USI field name Meaning (short version) Copy and Movement Control - see clause 6.1 Copy Control Information (CCI) The Copy Control Information field that has four states: CCNA, C1, CNM, or CN. CCNA "Copy Control Not Asserted" state of CCI. C1 "Copy Once" state of CCI. CNM "Copy ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6 Detailed Description of USI Fields | The syntax given in this clause and in the following clause is mandatory. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1 Copy and Movement Control | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1.1 Copy Control Information (CCI) | The Copy Control Information field can take on four states: • CCNA; • C1; • CNM; or • CN. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1.2 Copy Control Not Asserted (CCNA) | "Copy Control Not Asserted" is a Copy Control Information state that means that the Authorized Usage shall not include numerical restrictions to Copying. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1.3 Copy Once (C1) | "Copy Once" is a Copy Control Information state that means that the Authorized Usage shall permit exactly one Copy. The resulting Copy is marked "Copy No More". "Copy Once" can only apply to "live" Content (i.e. contemporaneous to the Content's Acquisition), since any stored Copy must be remarked "Copy No More". NOTE: ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1.4 Copy No More (CNM) | "Copy No More" is a Copy Control Information state that means that the Authorized Usage shall not permit Copying. This Copy Control Information state is given to Copies of "Copy Once" Content during the Copying process. NOTE: Content that is marked "Copy No More" is Movable. Moving is the process of making a Copy where... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1.5 Copy Never (CN) Zero Retention Not Asserted | "Copy Never" is a Copy Control Information state that means that the Authorized Usage shall not permit Copying. Further storage or buffering of "Copy Never" content is allowed to facilitate a fixed time period pause and trick mode function, e.g. because such capability is not otherwise available to the user via an upst... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.1.6 Copy Never (CN) Zero Retention Asserted | If zero_retention is asserted, then Content with a CCI state of "Copy Never" shall not be stored or retained for the purpose of enabling pause or trick modes. zero_retention is provided to indicate that no further storage or buffering of "Copy Never" content is allowed to facilitate a fixed time period pause and trick ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2 Consumption Control | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.1 Viewable (V) | If V is asserted, viewing, i.e. Consumption or Export, is enabled, subject further to the View Window and the View Period. If V is not asserted then Consumption and Export are not enabled. NOTE: Content may Acquired into CPCM with V not asserted; this allows the Content to be managed by CPCM prior to authorization to C... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.2 View Window | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.2.1 View Window Activated (VWA) | If VWA is asserted, viewing, i.e. Consumption or Export, is temporally limited by the View Window field, i.e. Consumption is: a) enabled when the View Window is enabled, or open, subject further to the V field and the View Period; and b) disabled when the View Window is not enabled, or closed. If VWA is not asserted, C... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.2.2 View Window Start | The view_window_start field defines the start time upon which the View Window is enabled, or opened. It is defined as absolute start time. The format of this field is defined in CPCM Systems Specification (TS 102 825-4 [2]). ETSI ETSI TS 102 825-3 V1.2.1 (2011-03) 15 |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.2.3 View Window End | The view_window_end field defines the end time after which the View Window is disabled, or closed. It is defined as absolute expiry time. The format of this field is defined in CPCM Systems Specification (TS 102 825-4 [2]). |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.3 View Period | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.3.1 View Period Activated (VPA) | If VPA is asserted, viewing, i.e. Consumption or Export, is enabled for a limited period of time after first playback of the Content, the View Period, as specified by the view_period_from_first_playback field, subject further to the V field and the View Window. If VPA is asserted and the view_period_from_first_playback... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.3.2 View Period From First Playback | The view_period_from_first_playback field defines when Consumption or Export is enabled and when it expires in terms of a period of time relative to first Consumption or Export of a stored Copy (or first Consumption or Export of live Input Content that is stored for additional future Consumption). The right to Consume ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.4 Simultaneous View Count | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.4.1 Simultaneous View Count Activated (SVCA) | If SVCA is asserted, then viewing, i.e. simultaneous Consumption and Export, is numerically limited. If SVCA is not asserted, then viewing, i.e. simultaneous Consumption and Export, is not numerically limited. NOTE: See the simultaneous_view_count below for another means to "not assert" SVCA. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.2.4.2 Simultaneous View Count | The simultaneous_view_count field indicates the number of concurrent Consumption Points and Export Points that can be used for the Live/Direct Consumption and Export of a Content Item. The eight-bit simultaneous_view_count field is defined in Table 3. Table 3: Simultaneous View Count Description Value Meaning 0 Conditi... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3 Propagation Control | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.1 Movement and Copying Propagation Information | The Movement and Copying Propagation Information can take on four states: MLAD, MGAD, MAD or MCPCM. See clause 4.6 for a description of propagation controls. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.1.1 Movement and Copying Within Localized AD Enabled (MLAD) | If asserted, Copying and/or Movement to another Storage Entity (or via a CPCM Device) is allowed within the same Localized AD, subject to the states of the CCI field. NOTE: This is the minimum extent of Propagation that can be signalled by the Movement and Copying Propagation Information. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.1.2 Movement and Copying Within GAD Enabled (MGAD) | If asserted, Copying and/or Movement to another Storage Entity (or via a CPCM Device) is allowed within the same Geographically-constrained AD (GAD), subject to the states of the CCI field. The GAD is the AD constrained to the Geographic Area specified in an Auxiliary Data field described in clause 7.2. NOTE 1: The MGA... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.1.3 Movement and Copying Within AD Enabled (MAD) | If asserted, Copying and/or Movement to another Storage Entity (or via a CPCM Device) is allowed within the same Authorized Domain, subject to the states of the CCI field. If MLAD or MGAD is asserted, then the same Authorized Usage that is allowed by MAD shall be allowed upon fulfilment of conditions specified in the R... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.1.4 Movement and Copying Within CPCM Enabled (MCPCM) | If asserted, Copying and/or Movement to any CPCM-compliant Storage Entity (or via any CPCM Device) is allowed, subject to the states of the CCI field. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.2 Viewing Propagation Information | The Viewing Propagation Information can take on four states: VLAD, VGAD, VAD or VCPCM. See clause 4.5 for a description of propagation controls. NOTE: It may not make sense to assert more restrictive propagation control on Viewing (Consumption) than on Movement and Copying since the equivalent functionality could be ob... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.2.1 Viewing Within Localized AD Enabled (VLAD) | If asserted, viewing, i.e. Consumption, is allowed using a Consumption Point (or via a CPCM Device) in the same Localized AD, subject to the states the V, VWA, View Window, SVCA and simultaneous_view_count fields. NOTE: This is the minimum extent of Propagation that can be signalled by the Viewing Propagation Informati... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.2.2 Viewing Within GAD Enabled (VGAD) | If asserted, viewing, i.e. Consumption, is allowed using a Consumption Point (or via a CPCM Device) in the same Geographically-constrained AD, subject to the states of the V, VWA, View Window, SVCA and simultaneous_view_count fields. The GAD is the AD constrained to the Geographic Area specified in a Content Licence Au... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.2.3 Viewing Within AD Enabled (VAD) | If asserted, viewing, i.e. Consumption, is allowed using a Consumption Point (or via a CPCM Device) in the same Authorized Domain as the Content Source, subject to the states of the V, VWA, View Window, SVCA and simultaneous_view_count fields. If VLAD or VGAD is asserted, then the same Authorized Usage that is allowed ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.2.4 Viewing Within CPCM Enabled (VCPCM) | If asserted, viewing, i.e. Consumption, is allowed using any CPCM-compliant Consumption Point, subject to the states of the V, VWA, View Window, SVCA and simultaneous_view_count fields. |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.3 Transition from "LAD or GAD Usage" to "AD Usage" | |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.3.1 Remote Access Rule | The Remote Access Rule defines the conditions under which Copying, Movement and/or Consumption shall transition from being allowed only within the Localized AD or Geographically-constrained AD to being allowed within the entire AD, i.e. "Remote Access" within an AD. It therefore has meaning with respect to Copying and ... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.3.2 Remote Access Date flag (moving window) | If remote_access_date_moving_window_flag is asserted then Remote Access is allowed for a specific part of the Content Item, in accordance with other USI fields, starting when the absolute date specified in the remote_access_date Field augmented with the time duration elapsed between the beginning of the Content and the... |
92646f4b2a91a814e0eb35e493c92b0c | 102 825-3 | 6.3.3.3 Remote Access Record Flag | If the remote_access_record flag is asserted then Remote Access is allowed, in accordance with other USI fields, upon the end of recording of the particular Content Item. The format of this field is defined in CPCM Systems Specification (TS 102 825-4 [2]). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.