hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.1 General | As described in the Non-RT RIC Architecture specification [3], the A1-related services produced by the SMO/Non-RT RIC framework enable the following functionalities related to the management of A1 policies and A1 enrichment information: • Creation, modification, deletion, and query of A1 policies. • Discovery of suppor... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.2 A1 policy management services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.2.1 Overview | The A1 Policy management service is an R1 service that enables an rApp (the consumer of that service) to: • discover available A1 policy types and subscribe to notifications on added or removed A1 policy types; • query for details of A1 policy types and details of A1 policy and enforcement status; • create, update, and... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.2.2 A1 Policy management | The following procedures are defined: • Query A1 policy type identifiers: An A1 policy management service Consumer can use this procedure to query for the available A1 policy types. The A1 policy management service Producer will respond with the list of identifiers for all the available A1 policy types. • Subscribe to ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.3 A1 enrichment information related services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.3.1 Overview | A1 enrichment information related services enable rApp to register and deregister of EI types of which data it can produce as the source for the EI job results delivered over the A1 interface. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.3.2 A1 enrichment information | The following procedures are defined: • Register EI type: An rApp uses this procedure to register an EI type that it can produce as the source for the EI job results delivered over the A1 interface to the A1 enrichment information functions. In the registration request, the rApp includes the EI source data type registe... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.4 A1 ML model management services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3.4.1 Overview | The availability of AI/ML model training capabilities over A1 is indicated in the AI/ML model training capability registration as specified in clause 5.6.6. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4 RAN OAM-related Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.1 General | As described in the Non-RT RIC Architecture specification [3], the RAN OAM-related services produced by the SMO/Non-RT RIC framework provide access to OAM functionality that enables the Service Consumer: • To obtain information about alarms. • To change their acknowledgment status. • To obtain performance information r... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.2 Network Information service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.2.1 Overview | The Network Information service provides to the Service Consumer information related to the network, in particular the RAN, that has been aggregated from multiple information sources that the SMO has access to, e.g. configuration, topology, network element state, geolocation, inventory, etc. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.2.2 Queries related to information about cells | The Network Information service supports various information queries that give the rApps access to information aggregated from multiple sources. The following procedure is defined: • Query cells-related information: This service operation allows to query aggregated information related to RAN cells. NOTE: How to query t... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.3 Fault Management (FM) service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.3.1 Overview | The Fault management service allows the Service Consumer to obtain information about alarms. The RAN OAM-related functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.3.2 Querying alarm information | The FM service shall allow the Service Consumer to query alarm information. The following procedure is defined: • Query alarms: This procedure allows the Service Consumer to query the alarm list to obtain the whole list, a subset of the alarms in the list, or an individual alarm. The Service Consumer may specify a set ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.3.3 Changing the alarm acknowledgement state | The FM service shall allow the Service Consumer to change the acknowledgement state of individual alarms (i.e. to acknowledge or unacknowledge them). The following procedure is defined: • Change alarm acknowledgement state: This procedure allows the Service Consumer to change the acknowledgement state of an alarm (i.e.... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.4 Performance Management (PM) service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.4.1 Overview | The performance management service allows the Service Consumer to access performance information that was collected from the network elements by the Service Producer. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 23 The RAN OAM-related functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.4.2 Querying performance information | The PM service shall allow to query performance information using a set of filtering criteria. The following procedure is defined: • Query performance information: This procedure allows to query performance information that has been collected from the network elements. The Service Consumer specifies a set of filtering ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.5 Configuration Management (CM) service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.5.1 Overview | In the following, the term "Service Consumer" refers to the role of an rApp that consumes the Configuration Management (CM) service. The term "Configuration management service Producer" refers to the role of the logical RAN OAM-related functions in the SMO/Non-RT RIC framework producing the CM service. The CM service a... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.5.2 Retrieving configuration schemas | The CM service allows the Service Consumer to retrieve information pertaining to the configuration schemas of one or more managed entities. The following procedure is defined: • Get schemas: A Service Consumer can use this procedure to retrieve configuration schemas for the managed entities. The CM service Producer wil... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.5.3 Reading configuration data | The CM service allows the Service Consumer to read the configuration data, related to one or more managed entities. The following procedure is defined: • Read Configuration: This procedure enables the Service Consumer to obtain configuration data (including the configuration attributes) related to one or more managed e... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.4.5.4 Writing configuration changes | The CM service allows the Service Consumer to write configuration changes, related to one or more managed entities. The following procedure is defined: • Write Configuration: This procedure enables the Service Consumer to request the CM service Producer for writing configuration changes related to one or more managed e... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5 O2-related Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.1 General | As described in the Non-RT RIC Architecture specification [3], the O2-related services produced by the SMO/Non-RT RIC framework provide access to O-Cloud management functionality that enables the Service Consumer: • To obtain information related to O-Cloud infrastructure management such as: - Infrastructure Inventory. ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.2 O2 Infrastructure management service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.2.1 Overview | O2 Infrastructure management service allows the Service Consumer to obtain information related to O-Cloud infrastructure management services. O2 related functions in the SMO/Non-RT RIC framework produce this service as specified in O2IMS [6]. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.2.2 Query O2-IMS Information | O2 Infrastructure management service shall support various information queries that give the rApps access to information related O-Cloud infrastructure management services. The following procedures are defined: • Query O2ims_Infrastructure Inventory related information: This service procedure allows to query informatio... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.3 O2 Deployment management service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.3.1 Overview | O2 deployment management service allows the Service Consumer to obtain information related to O-Cloud deployment management services. O2 related functions in the SMO/Non-RT RIC framework produce this service as specified in O2DMS [7] and O2GAP [8]. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.5.3.2 Query O2-DMS Information | O2 deployment management service shall support various information queries that give the rApps access to information related O-Cloud deployment management services. The following procedures is defined: • Query O2dms_ Deployment Monitoring related information: This service procedure allows to query information related t... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6 AI/ML Workflow Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.1 General | As described in the Non-RT RIC Architecture specification [3], the AI/ML workflow services enable: • Training of an AI/ML model. • Registration of an AI/ML model. • Discovery of an AI/ML model. • Subscription to change of an AI/ML model. • Registration of capability to train an AI/ML model (optional). • Query of AI/ML ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.2 AI/ML model registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.2.1 Overview | AI/ML model Producers consume this service to register, query, update and delete an AI/ML model registration. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.2.2 Registration of AI/ML model | This set of procedures enable AI/ML model Producer to register, and manage the registration of, an AI/ML model. As part of the Register AI/ML model procedure, the AI/ML model Producer provides the producer identifier, model identifier and model-related information. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 27 The followin... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.3 AI/ML model storage service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.3.1 Overview | AI/ML model storage service Consumers consume this service to store and delete an AI/ML model or the location of the AI/ML model. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.3.2 Storage of AI/ML model | This set of procedures enable AI/ML model storage service Consumer to store and delete the AI/ML models and their locations. The following procedures are defined: • Store AI/ML model: An AI/ML model storage service Consumer uses this procedure to store an AI/ML model. On receiving the request, the AI/ML model storage s... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.4 AI/ML model discovery services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.4.1 Overview | AI/ML model Consumers consume this service to discover registered AI/ML Models and their related information. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 28 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.4.2 Discovery of AI/ML model | This procedure enables an AI/ML model Consumer to discover registered AI/ML models and to retrieve information on the registered AI/ML models. The following procedure is defined: • Discover AI/ML model: An AI/ML model Consumer can discover the AI/ML models that are registered based on provided selection criteria. For e... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.5 AI/ML model change subscription service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.5.1 Overview | AI/ML model Consumers consume this service to subscribe to change notifications for registered AI/ML models and to receive notifications about AI/ML model changes. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.5.2 Subscribing to AI/ML model changes | This set of procedures enable AI/ML model Consumer to subscribe to change notifications for registered AI/ML models. The following procedures are defined: • Subscribe AI/ML models changes: An AI/ML model Consumer can use this procedure to subscribe to notifications regarding changes related to registered AI/ML models a... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.6 AI/ML model training capability registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.6.1 Overview | AI/ML model Trainers consume this service to register, query, update and deregister its AI/ML model training capability. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. AI/ML model training service Producer consumes this service to register its AI/ML model training capability. Registe... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.6.2 Registration of AI/ML training capability | This set of procedures enable AI/ML model Trainer to register, and manage the registration of, its training capabilities. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 29 As part of the Register AI/ML model training capability procedure, the AI/ML model Trainer provides the rApp identifier and further information about the tr... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.7 AI/ML Model deployment request service | This procedure enables an AI/ML model deployment Service Consumer to request the deployment of a registered AI/ML model. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. The following procedure is defined: • Request AI/ML model deployment: An AI/ML model deployment Service Consumer req... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.8 AI/ML model training services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.8.1 Overview | AI/ML model training service Consumers consume this service to request AI/ML model training, query AI/ML model training job status, cancel AI/ML model training, and receive notification about AI/ML model training job status change. AI/ML model Trainers or the AI/ML workflow functions in the SMO/Non-RT RIC framework pro... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.8.2 AI/ML model training | This set of procedures enable AI/ML model training service Consumer to request and manage the AI/ML model training of an AI/ML model. The following procedures are defined: • Request AI/ML model training: An AI/ML model training service Consumer uses this procedure to request training of an AI/ML model by providing the ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.9 AI/ML model performance monitoring service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.9.1 Overview | The AI/ML model performance monitoring service is produced by the AI/ML model Consumer rApp. Authorized AI/ML model performance Consumers consume this service to subscribe to, and receive, performance information related to a deployed AI/ML model. During AI/ML model registration, supported AI/ML model performance relat... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.9.2 Monitoring the performance of a deployed AI/ML model | This set of procedures enables the AI/ML model performance monitoring service Consumers to subscribe to, and receive, regular performance information related to a deployed AI/ML model. As part of the Subscribe AI/ML model performance procedure, the AI/ML model performance monitoring service Consumers provide the AI/ML ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.10 AI/ML model inference service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.10.1 Overview | AI/ML model Consumer consumes this service to query the inference capabilities and initiate the inference of an AI/ML model. The AI/ML model Producer or the AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.10.2 Inference of AI/ML model | The below set of procedures enable AI/ML model Consumer to query inference capabilities and request inference of an AI/ML model. The following procedures are defined: • Query AI/ML model inference capabilities: An AI/ML model Consumer uses this procedure to retrieve the inference capability information such as model id... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.11 AI/ML model training capability query services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.11.1 Overview | The AI/ML model training capability query service allows the Service Consumers to query all the available registered AI/ML model training capability. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.6.11.2 Query of AI/ML model training capability | This procedure enables a Service Consumer to query registered AI/ML model training capability. The following procedure is defined: • Query AI/ML model training capability: A Service Consumer uses this procedure to retrieve the registered AI/ML model training capability information based on provided selection criteria. ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 6 R1 Interface Protocol Structure | "R1TP" [5] defines the R1 transport protocol stack. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 32 Annex A (informative): Change history Date Version Information about changes 2024.03.15 11.00 Published final version by updating the data subscription and data request, deprecating Heartbeat service. 2024.11.21 10.00 Publishe... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 1 Scope | The present document defines the integration between HbbTV® (as defined in ETSI TS 102 796 [1]) and broadband content protection technologies - "DRM". This integration has not previously been included in ETSI TS 102 796 [1] and is in the present document to contribute to inter-operability. The DRM systems supporting Hb... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 2 References | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 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... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 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... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 3 Definition of terms, symbols and abbreviations | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 796 [1] and the following apply: HbbTV® Test Suite: set of unit test descriptions from ETSI TR 103 824 [i.6] |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 3.2 Symbols | Void. ETSI ETSI TS 104 227 V1.1.1 (2026-01) 10 |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 796 [1] and the following apply: DASH-IF DASH Industry Forum OEM Original Equipment Manufacturer TA Trusted Application and/or Targeted Advertising TEE Trusted Execution Environment |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 4 Background (informative) | Generally, DRM systems require authentication, encryption and Digital Rights Management (DRM). Authentication is used to ensure the content is being delivered to an approved device. Encryption is used to ensure the content is secure and cannot be accessed or tampered with by unauthorized parties. DRM is used to protect... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5 DRM features (informative) | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.1 Basic features | The most basic use of DRM is to protect individual items of on-demand content. Specifically: • The content is encrypted and identified as such (e.g. in a manifest or in the file format). • Attempting to play content identified as encrypted content triggers a request for a license from a DRM license server. NOTE: Normal... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.2 Common encryption & multi-DRM | Traditionally, distributing digital content to multiple devices and platforms with different DRM technologies required content providers to separately encrypt their content for each DRM technology and device. This process created management complexities and increased costs for content owners. To address these challenge... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.3 AES encryption modes | ISO/IEC 23001-7 [4] defines a number of options for encryption of media data of which the most commonly used are 'cenc' (clause 10.1 of that document) and 'cbcs' (clause 10.4). Historically most DRM systems used 'cenc' except for Apple Fairplay® that used 'cbcs' with an encrypt:skip pattern of 1:9 as defined in clause ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.4.1 DRM Information in ISO BMFF files | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.4.1.1 'pssh' box | The DRM may need a license from which it can generate one or more keys, identified by key IDs, to be used to decrypt the protected content. This license may be carried in one or more 'pssh' boxes, provided by one of the DRM APIs described in the present document or provided by some other means. 'pssh' boxes may be carr... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.4.1.2 Initialization Vector | The initialization vector for use when decrypting a media sample is carried in the InitializationVector field of the Sample Auxiliary Information, which is located using the corresponding byte offset and size stored in the Sample Auxiliary Information Offset ('saio') and Sample Auxiliary Information Size ('saiz') boxes... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.4.1.3 Key ID | Every protected media sample is encrypted using a key, which is identified by a key ID (KID). This is a 128 bit number, recommended to be generated as a UUID to ensure global uniqueness. The key ID is carried in the sample group description 'seig' box in the KID field. This box also indicates whether or not the sample ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.4.2 DRM information in the MPD | In the MPD, protected content has at least one ContentProtection element on each AdaptationSet which contains protected media. Each AdaptationSet has a generic ContentProtection element to advertise that it contains content encrypted according to CENC (ISO/IEC 23001-7 [4]). This element will have the schemeUri attribut... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.5 Clear Key | Clear Key is a mechanism defined in W3C EME [6] that provides some protection for content crossing the network to a media consumption device. As the name implies, the keys to decrypt the content are not protected except by whatever mechanism an HbbTV® application implements so Clear Key is inherently less secure than a... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6 Advanced features | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6.1 Persistent licenses | Typically, a new request for a license is made each time protected content starts to be played. Licenses would not survive beyond the duration of a session of media playback. DRM systems may support a feature often referred to as "persistent licenses" where DRM licenses persist beyond the end of a media playback sessio... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6.2 Key rotation and license rotation | In license rotation, a new license is obtained while playback continues. For DASH, this would occur at a Period boundary. See clause 9.2 of DASH-IF IOP-6 V5.0.0 [i.1]. This is also sometimes referred to as "Periodic re-authorization". In key rotation, the key needed to decrypt content is periodically updated without ne... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6.3 Hardware DRM/trusted execution environment/security levels | DRM systems are designed to secure the access to media content, providing access only to authorized entities. To protect against access by unauthorized entities, DRM systems need to ensure that the processing of DRM content licenses, content keys or the content itself is secured and cannot be easily bypassed or spied u... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6.4 Transitioning between encrypted and unencrypted content | Transitioning between unencrypted and encrypted content or vice-versa is typically needed where adverts have been inserted or replaced as adverts are rarely encrypted. Typically, if content playback started with encrypted content then the media decoding pipeline will also be able to cope with unencrypted content, gener... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6.5 Key per track or key per resolution | Because of the varied types of devices deployed in the field, with different DRM implementations and security levels, content owners or content distributors may wish to protect the highest resolutions or the best features like HDR, Next Generation Audio, or various audio languages with different keys and licenses. Usin... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.7 Authenticating license requests | DRM license servers may require requests for a license to be authenticated using some kind of access token: • Where the EME API (see clause 6.3.3) is used, the application is responsible for sending the request to the license server and can add the access token as required for the license server concerned. • Where the ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.1 Native DASH players | ETSI TS 102 796 [1] has, since version 1.2.1, required support for a DASH player as part of the terminal implementation, generally referred to as the "native" DASH player. This is required to support content according to DVB-DASH, ETSI TS 103 285 [2]. |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.2 MSE DASH players | ETSI TS 102 796 [1] has, since version 1.6.1, required support for the W3C Media Source Extensions (MSE) [6]. These enable DASH players to be provided as part of an HbbTV® application, e.g. as a JavaScript library. Examples of DASH players that are JavaScript libraries include dash.js (https://dashjs.org/, https://gith... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.3 DRM APIs | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.3.1 Introduction | ETSI TS 102 796 [1] includes two APIs for DRM, the older oipfDrmAgent API (see clause 6.2) and the newer Encrypted Media Extensions (see clause 6.3). The oipfDrmAgent API can also be used for broadcast conditional access as well as DRM. Applications should only use one of these for DRM. Using both APIs for DRM during t... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.3.2 oipfDrmAgent | The Open IPTV Forum (OIPF) JavaScript API for content protection is built round the application/oipfDrmAgent embedded object defined in clause 7.6.1 of the OIPF DAE specification [5]. The key features are as follows: • Applications send messages to DRM systems using the method sendDRMMessage( String msgType, String msg... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.3.3 Encrypted Media Extensions | The W3C Encrypted Media Extensions API (EME) [6] are a much more recent API than oipfDRMAgent. Since 2018 the EME API is deployed in almost all web browsers. NOTE: See https://caniuse.com/eme. The API design and architecture are very different to oipfDRMAgent. The architecture features a Content Decryption Module (CDM)... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 6.4 Device capabilities | Applications are able to discover DRM capabilities of terminals as follows: • With the XML capabilities (see clause 10.2.4.7 of ETSI TS 102 796 [1] and clause 9.3.11 of the OIPF DAE specification [5]), support for the DRM feature is required to be indicated by a DRM element and adding a DRM attribute to video_profile a... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 7 Selection of a DRM system and version (informative) | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 7.1 General | The present document does not choose a DRM system or version. This is a commercial choice for stakeholders. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.