hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.2.3 Talking-and-listening test | In a TALT, the test subject interface via a telephone handset with a live simulation of speech signals impaired by echo artefacts and double talk impairments. All impairments need be introduced in real-time because the source speech signal is generated by the test subject himself. Therefore, the test subject can listen... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.2.4 Third-Party listening tests | In a TPLT as described in Recommendation ITU-T P.831 [3], the test subjects listen to and consequently judge impaired speech signals that are part of a conversation between the two recorded parties. The impaired speech signals are generated offline, typically using artificial head recordings. The speech signals either ... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.2.5 Summary | As already indicated in Recommendation ITU-T P.805 [5], each of the aforementioned listening/conversational tests have to deal with a trade-off between realistic conversations, number of test conditions, reproducibility and effort. A comparison of the specific advantages and disadvantages of the corresponding subjectiv... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.3 Selection of Speech Material | This clause describes the source speech material, which shall be used for the generation of degraded listening test conditions. All sequences described in the following shall be suitable for the playback via mouth simulator of HATS, i.e. available in fullband (20 Hz - 20 kHz audio bandwidth). If not specified otherwise... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4 Generation of test conditions | |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.1 Introduction | Figure 5 provides a modified version of the general communication scenario shown in Figure 1 and Figure 3, which describes the recording of binaural stimuli for the TPLT. For this purpose, user B at the reference-side is replaced by a HATS, which acts first as a talker, then in a second step as a listener. Figure 5: Co... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.2 Requirements on Test Equipment | For the playback and recording of speech signals, accesses to acoustic interfaces and different types of electrical POI are required. For this purpose, high quality measurement equipment shall be used for all recordings described in the following clauses. Depending on the use case, terminal type and bandwidth according... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.3 Recordings on Reference-side | |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.3.1 Sending Direction | In order to transmit the speech signals originated from the reference-side with a realistic absolute level range, the following insertion methods in sending direction are possible: 1) Playback over the artificial mouth, acoustic insertion into a reference device (e.g. a known phone providing high quality). This device ... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.3.2 Sidetone | In order to simulate the binaural self-hearing of talking perceived by the talker/listener at the reference-side (sidetone) for the listening test stimuli, the following recording or simulation methods are possible: 1) Recording with active reference device mounted to HATS. In this case, the sidetone has to be recorded... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.4 Recording of degraded signals | Listening test speech samples simulated with the subjective test procedure of the present document should reflect impairments, which may occur in real-life communication situations as well. However, the number of conditions may grow rapidly, when trying to combine multiple source files, terminals and/or other degradati... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.4.5 Calibration of test signals | For the generation of stimuli, the sending signals from device-side are captured electrically at the POI. In order to provide correct level and suitable frequency shaping, the acoustic capture on the reference-side can be realized similar as in clause 5.4.3.1: 1) Electric insertion into a reference device (e.g. a known... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.5 Reference conditions | As common practise for other standardized speech quality tests, reference conditions shall be used in TPLT complying with the present document. Reference conditions are a well-established method to conduct meaningful comparisons of auditory test results from different laboratories or from the same laboratory at differe... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.6 Headphone playback for presentation | Headphones used for presentation of the test material to the listening panel shall be calibrated and equalized using a HATS conforming to Recommendation ITU-T P.58 [14] equipped with an artificial ear type 3.3 according to Recommendation ITU-T P.57 [13]. The HATS is diffuse field equalized. The resulting frequency resp... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.7 Listening Test Design | |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.7.1 Listening Test Instructions | Since the task in a TPLT is more challenging for naïve test subjects than traditional speech quality tests, the test has to be prepared with care. A clear, simple and direct introduction shall be presented to the subjects in advance of the test. This includes a written and/or oral description in the mother tongue of th... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.7.2 Choice of Listening Test Subjects | In general, the choice of test subjects should follow the guidelines of Recommendation ITU-T P.800 [2] and the Handbook of subjective testing [4] as close as possible. The subject pool should be representative of the telecommunication user pool. Groups should be heterogeneous and balanced concerning gender, age and (if... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.7.3 Test Procedure | In accordance to [4], a training phase of at least five samples shall be presented in advance of the real test. These samples shall be of same type as the actual test conditions and may originate from the test corpus itself. However, it shall be ensured that the training samples are not presented in the first session o... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.7.4 Test Sample Presentation | The samples of test and reference conditions shall be structured into sessions. In each session, one randomly selected sample per condition is included (balanced blocks design, see [4]). All listening test samples within a single session shall be presented in a (pseudo-)random order to the subjects. |
af00e45b7208320af4d15dc870bb407d | 103 801 | 5.8 Requirements on the listening laboratory | Listening laboratory facilities shall comply with the requirements and follow the guidelines provided in Recommendation ITU-T P.800 [2] and the ITU-T handbook on practical procedures for subjective testing [4]. |
af00e45b7208320af4d15dc870bb407d | 103 801 | 6 Assessment of Echo Artefacts | For echo-only listening tests, the common requirements of clause 5 shall be met. In addition, the following items shall be considered: • During the recording of test conditions, no talker shall be active at the sending side of the DUT, i.e. no uplink signal shall be transmitted by the DUT (except the echo signal). See ... |
af00e45b7208320af4d15dc870bb407d | 103 801 | 7 Assessment of Double Talk Impairments | For double talk listening tests, the common requirements of clause 5 shall be met. In addition, the following items shall be considered: • During the recording of test conditions, a talker shall always be active at the sending side of the DUT, i.e. no echo-only recordings as per clause 6 shall be evaluated in a double ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 1 Scope | The scope of the present document is to define a Content Protection Information Exchange (CPIX) Format. A CPIX document contains keys and DRM information used for encrypting and protecting content and can be used for exchanging this information among entities needing it in many possibly different workflows for preparin... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 2 References | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 3 Definition of terms, symbols and abbreviations | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 3.1 Terms | For the purposes of the present document, the following terms apply: content: one or more audio-visual elementary streams and the associated MPD if in DASH format content key: cryptographic key used for encrypting part of the content content key context: portion of a media stream which is encrypted with a specific cont... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 3.2 Symbols | Void. |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard BMFF Base Media File Format CBC Cypher Block Chaining CDN Content Delivery Network CMS Content Management System CPIX Content Protection Information eXchange DASH Dynamic Adaptive Streaming over HTTP DRM Digita... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4 Use Cases and Requirements | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.1 Introduction | Content Keys and DRM Signaling, as known as content protection information, need to be created and exchanged between some system entities when preparing Content. The flows of information are of very different nature depending on where Content Keys are created and also depending on the type of Content that can be either... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.2 Overview of the End-to-End Architecture | This clause gives a general overview of the context in which content protection information needs to be exchanged between entities in the backend. It completes clause 4 of [1] by putting more emphasis on the backend aspects. This clause takes DASH content as an example for providing more specific and clear understandin... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.3 Use Cases for the Preparation of Content | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.3.1 Introduction | This clause describes some workflows for content preparation where content protection information is exchanged between or carried through some entities. As for the previous clause, this clause takes DASH content as an example for providing more specific and clear understanding, but this can be generalized to other stre... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.3.2 On-Demand Content | The flow for preparing On-Demand Content requires that a media asset is available non-encrypted, ideally in the maximum resolution so that an adaptive streaming presentation can be prepared. One possible flow is that a Content Management System (CMS) creates a workflow ensuring that DASH Content is prepared. The CMS ma... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.3.3 Live Content | Metadata is regularly imported with new or updated information. Metadata can include different type of information on the EPG events such as the duration of the event, the list of actors, the output controls usage rules, a purchase window, etc. Content is continuously received, transcoded in the desired format and encr... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.3.4 Catch-up | Live Content has already been encoded and encrypted (if required) for Live unicast. All DRM systems have access to the keys. Additional metadata may be required for ensuring that events are effectively available in catch-up. These are made available to the Portal and some Live events are identified as being able to be ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4 Exchange over an Interface | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.1 Introduction | This clause gives details on how content protection information is exchanged or transferred over an interface between two or more entities. |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.2 Content Key Delivery to One Entity | In the simplest use case shown in Figure 4, content protection information is made of a Content Key. One entity sends a Content Key to the other entity. Figure 4: Content Key delivery to one entity The primary data model carried by content protection information document is made of one to many Content Keys with their a... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.3 Secure Content Key Delivery to Several Entities | This use case shown in Figure 5 is an extension of the use case of clause 4.4.2 and is compatible with the use cases presented in the following clauses. Figure 5: Secure Content Key Delivery to Several Entities The entities exchanging Content Keys may want to rely upon a trust relationship that ensures authentication a... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.4 Content Key Delivery with Usage Rules | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.4.1 Introduction | These use cases are extension of the use case of clause 4.4.2 and present different rules that can be applied on a Content Key when delivered to an entity as shown in Figure 6. Each usage rule defines a set of filters that are used to define a Content Key Context. If a rule match is found, the Content Key referenced by... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.4.2 Label Filter | This use case adds information to Content Keys that specifies how they are to be mapped to labelled Content Key Contexts, where the labelling system has been pre-agreed between the producer and consumer of the CPIX document. For example, labels might be the IDs of DASH adaptation sets or, for more compatibility with fo... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.4.3 Key Period Filter | This use case adds information to Content Keys that specifies how they are to be mapped to key periods, as known as cryptoperiods for Content Key rotation. The mapping is accomplished by defining key periods and mapping Content Keys to any number of key periods. The recipient will use the added information to map Conte... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.4.4 Policy-based Filters | This use case associates policy-based information with Content Keys, constraining how they define Content Key Contexts. Policy based filters are, for example, video or audio stream attributes and bitrate ranges. The recipient will use the added information to map Content Keys to Content Key Contexts according to the de... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.5 Content Key Delivery with DRM Signaling | This use case is an extension of the use case of clause 4.4.2 and is compatible with the use case of clause 4.4.4. This use case adds DRM Signaling information to each Content Key. The recipient may embed this signaling into the data streams it generates. See Figure 7. Figure 7: Content Key Delivery with DRM Signaling ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.6 Incremental Update and Extension of the document | This use case, shown in Figure 8, illustrates the usage of the content protection information document in a realistic workflow comprising multiple cooperating components that require a standardized data format for content protection information exchange. Figure 8: Incremental update and extension of the document Each c... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.7 Multiple Content Keys Delivery for Multiples Assets | This use case, shown in Figure 9, is for the bulk transfer of Content Keys in one document. Each Content Key is associated to a different media asset, hence within the document, several media assets can be referenced. Limiting the number of documents to exchange allows for simpler transfer between entities of Content K... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.8 Content Key Hierarchy Delivery for Content Packaging | Some DRM systems enable the use of hierarchy of keys, where the set of keys delivered to clients (root keys) within licenses differs from the set of keys used to encrypt Content (leaf keys). Doing so enables DRM systems to separate content encryption and commercial offer management. Packaging content that uses a key hi... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.4.9 Root Key Delivery for License Server Operation | Some DRM systems enable the use of hierarchical keys, where the set of keys delivered to clients (root keys) differs from the set of keys used to encrypt Content (leaf keys). When, for example, key creation is not a function of the license server, creating licenses in scenarios that use hierarchical keys requires the l... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.5 Workflow Examples | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.5.1 Encryptor Producer and Encryptor Consumer | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.5.1.1 Introduction | There are many workflows that are possible, depending on which entities provide information in the CPIX document, and which entities consume that information. Two simple single-producer, single-consumer examples are illustrated below in Figure 10 and Figure 11. Content Key handling component Content Key handling compon... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.5.1.2 Encryptor Producer | This clause shows a possible workflow for securing the exchange of the key information between entities when the Encryptor generates the Content Keys. In this example, the Encryptor is the entity which is taking responsibility for generating the Content Keys, protecting them and pushing them to the DRM Systems: • The f... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.5.1.3 Encryptor Consumer | This clause shows a possible workflow for securing the exchange of the key information between entities when the DRM System generates the Content Keys. In this model, the Encryptor can pull documents directly from a DRM System. In this case, the DRM System is generating Content Keys and is encrypting them for a secure ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 4.5.2 Multiple Producers | This clause illustrates that it is possible to have more complex workflows than those previously illustrated. In one such example, shown in Figure 14, for DASH content, a media packager might define the types of streams in the presentation, an Encryptor might generate the Content Keys, a DRM System might generate other... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5 XSD Schema Definition | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.1 Introduction | This clause describes the Content Protection Information eXchange (CPIX) format to provide a framework to securely exchange Content Key(s) and DRM Signaling between different system entities (see clause 4). This is an XML file that is described by the XSD. This clause describes in details elements part of the schema. |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.2 Requirements | It shall be possible to exchange Content Key(s) and DRM Signaling between entities involved in Content preparation workflows, an example of such interface where the exchange shall be possible is between a DRM system and the encryption engine. It shall be possible that the manifest generator receives DRM Signaling for s... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.3 Structure Overview | The structure is articulated around Content Keys and the accompanying material. The document contains all the information required for allowing any entitled entity to get access to or add in the Content Keys and either consume or add material, such as time constraint, DRM information to the CPIX document. The same XML ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4 Hierarchical Data Model | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.1 Introduction | In all tables of this clause, the following convention is used: • Elements are in bold and the number of allowed instances is defined by <minOccurs>…<maxOccurs> (where N for <maxOccurs> means unbounded). Elements shall be in the order specified in this clause. • Attributes are non-bold preceded with an @ and the use of... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.2 CPIX Element | The root element that carries the Content Protection Information for a set of media assets. @id (O, xs:ID) An identifier for the CPIX document. It is recommended to use an identifier that is unique within the scope in which this file is published. @contentId (O, xs:string) An identifier for the asset or content that is... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.3 DeliveryDataList Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. ETSI ETSI TS 103 799 V1.2.1 (2026-04) 24 @updateVersion (O, xs:integer) Matches the @updateVersion attribute of the UpdateHistoryItem element providing details o... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.4 DeliveryData Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @updateVersion (O, xs:integer) Matches the @updateVersion attribute of the UpdateHistoryItem element providing details on when this element was added or updated.... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.5 DocumentKey Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. ETSI ETSI TS 103 799 V1.2.1 (2026-04) 26 @encryptsKey (O, cpix:UUID) Matches the @kid attribute(s) of the referenced ContentKey elements. These referenced Conten... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.6 ContentKeyList Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @updateVersion (O, xs:integer) Matches the @updateVersion attribute of the UpdateHistoryItem element providing details on when this element was added or updated.... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.7 ContentKey Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @contentId (O, xs:string) An identifier for the asset or content that is protected by this key. It is mutually exclusive with the attribute @contentId defined in... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.8 HDCPData Element | @HLSHDCPLevel (O, xs:string) This attribute specifies the value of the HDCP-LEVEL attribute of the EXT-X-STREAM-INF tag in the multiVariant playlist. Its format is as specified in clause 4.4.6.2 of [8]. This attribute has meaning only when an HLS playlist is created for the media content. HDCPOutputProtectionData (0...... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.9 DRMSystemList Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @updateVersion (O, xs:integer) Matches the @updateVersion attribute of the UpdateHistoryItem element providing details on when this element was added or updated.... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.10 DRMSystem Element | The DRMSystem element contains all information on a DRM system that can be used for retrieving licenses for getting access to content. The present document defines elements for DRM system signaling in DASH, ISO BMFF, Smooth Streaming and HLS formats. Implementations may extend CPIX documents with additional elements to... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.11 ContentProtectionData Element | The ContentProtectionData shall be base64 encoded text. It has an optional attribute allowing to define the robustness level that is expected for this DRM. @robustness (O, xs:string) The value of this attribute is DRM specific. It announces what robustness level is expected from the DRM system for the representations t... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.12 HLSSignalingData Element | The HLSSignalingData shall be base64 encoded text. It has an optional attribute allowing to define where this data is to be placed, either in the multiVariant playlist or in the media playlist. It allows having different proprietary signaling in these locations. In a DRMSystem element, every HLSSignalingData shall have... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.13 ContentKeyPeriodList Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @updateVersion (O, xs:integer) Matches the @updateVersion attribute of the UpdateHistoryItem element providing details on when this element was added or updated.... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.14 ContentKeyPeriod Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @index (O, xs:integer) Numerical index for the key period. It shall increase. When reaching MAX_UINT32, the value rolls over. @label (O, xs:string) String identi... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.15 ContentKeyUsageRuleList Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @updateVersion (O, xs:integer) Matches the @updateVersion attribute of the UpdateHistoryItem element providing details on when this element was added or updated.... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.16 ContentKeyUsageRule Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @kid (M, cpix:UUIDType) Matches the @kid attribute of the ContentKey this element references. In hierarchical key scenarios, this shall reference a leaf key, not... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17 Usage Rules Filters | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17.1 Introduction | There can be several filters defined within a single ContentKeyUsageRule. In this case, all rules apply identically, the entity generating the ContentKeyUsageRule element or adding a new rule is responsible for ensuring that they do not contradict each other. A set of rules that would match multiple Content Keys to a s... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17.2 KeyPeriodFilter Element | @periodId (M, xs:IDREF) This references a ContentKeyPeriod element by @id. The filter will only match samples that belong to the referenced key period. Figure 32 shows a graphical view of the element. Figure 32: KeyPeriodFilter element |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17.3 LabelFilter Element | @label (M, xs:string) The filter will only match samples that carry a matching label. The exact meaning of labels is implementation- defined and shall be agreed upon in advance by the producer and consumer of the CPIX document. Figure 33 shows a graphical view of the element. Figure 33: LabelFilter element The @label a... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17.4 VideoFilter Element | If present, even without any attributes, the filter will only match video samples. @minPixels (OD, xs:integer) The filter will only match video samples that contain at least this number of pixels (encoded width x height before considering pixel/sample aspect ratio). The default value is 0 (zero). @maxPixels (OD, xs:int... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17.5 AudioFilter Element | If present, even without any attributes, the filter will only match audio samples. @minChannels (OD, xs:integer) The filter will only match audio samples that contain at least this number of channels. The default value is 0 (zero). @maxChannels (OD, xs:integer) The filter will not match audio samples that contain more ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.17.6 BitrateFilter Element | @minBitrate (OD, xs:integer) The filter will only match samples from streams with a nominal bitrate in b/s of at least this value. The default value is 0 (zero). @maxBitrate (OD, xs:integer) The filter will not match samples from streams with a nominal bitrate in b/s that exceeds this value. The default value is MAX_UI... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.18 UpdateHistoryItemList Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. UpdateHistoryItem (1...N, cpix:UpdateHistoryItem) It contains metadata about an update made to the CPIX document. There should be one entry for each instance in ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 5.4.19 UpdateHistoryItem Element | @id (O, xs:ID) An identifier for the element. It is recommended to use an identifier that is unique within the scope in which this CPIX document is published. @updateVersion (O, xs:integer) The is the ID referenced by other elements in the document. It is strongly recommended to use an identifier that is unique within ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6 Key Management | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.1 Key Encryption and Authentication in the CPIX Document | |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.1.1 Introduction | The CPIX document allows exchanging Content Keys in the clear but this is not a recommended method as it relies on the security of the communication mechanism used to deliver the CPIX document to the recipients, which may not be sufficient to adequately protect the Content Keys. Content Keys can be delivered encrypted ... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.1.2 Encryption | The document contains the following keys for encrypting Content Keys: Content Keys Each ContentKey element contains one Content Key that is used for encrypting an asset or crypto period of an asset or that acts as a dependency for the use of other Content Keys (when a key hierarchy is used). Typically, for Common Encry... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.1.3 Authenticated Encryption | The document contains the following key for authenticating keys: MAC Key For every CPIX document, a MAC Key may be created. It is used to calculate the MAC of every encrypted Content Key. The DeliveryData element identifies the MAC algorithm and provides the MAC Key, encrypted with the Delivery Key, for each recipient.... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.1.4 Digital Signature | Every element in the document that has an @id attribute can be signed according to [6]. Furthermore, the document (including any other signatures) can be signed as a whole. Upon loading a CPIX document, implementations should verify that signatures are present on entities that are expected to be signed and verify all d... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.1.5 Mandatory Algorithms | Table 1 gives the identification of the algorithms that shall be used for encryption, signature, MAC creation. Table 1: List of algorithms for the different security usages Usage Algorithm Content Key wrapping AES256-CBC, PKCS #7 padding Encrypted key MAC HMAC-SHA512 Document Key wrapping RSA-OAEP-MGF1-SHA1 Digital sig... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.2 Key Rotation Support | A CPIX document can contain content protection information for multiple crypto-periods, or period of time for content encrypted using key rotation. When content is protected with key rotation, a CPIX document shall contain one or more ContentKey elements and one or more ContentKeyPeriod elements, one of each per crypto... |
1833bbc28f0dd4ce15d0b718dc1156c1 | 103 799 | 6.3 Content Keys with Several Protection Encryption Schemes | In [7], several protection schemes that are not interoperable are defined. This means that several encrypted versions for the same content in the clear are created if the targeted devices support one or another protection scheme. While it may not be recommended, it is possible to use the same Content Keys when encrypti... |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 1 Scope | The present document provides the Test Purposes (TP) for Development of AML Test Descriptions for handsets as defined in the ETSI AML specification ETSI TS 103 625 [1] listed in clause 2.1 of the present document. |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 2 References | |
f9b949e5dfbfa3cca3d689fdbba35d42 | 103 825 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.