hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.4 Data request service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.4.1 Overview | For data consumption, Data Consumers consume this service to request data instances, and the Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. For data collection, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service to request data instances, and Data Producers produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.4.2 Requesting data | This set of procedures allows a Data request service Consumer to specify a data instance (for a registered DME type) to be delivered to it. The data instance is defined by information specified in clause 5.2.1. Data request is a one-time request and is performed via Request data procedure. A data request can be stopped using the Cancel data request procedure. Data request service Consumer can query the status of the production of the data. The following procedures are defined: • Request data: The Service Consumer provides, to the Data request service Producer, information on the data it requests based on the DME type information. • Cancel data request: The Service Consumer cancels a data request. • Query data request status: The Service Consumer queries the status of production of the data. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.5 Data subscription service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.5.1 Overview | For data consumption, Data Consumers consume this service to subscribe to data instances, and the Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 17 For data collection, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service to subscribe to data instances, and Data Producers produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.5.2 Subscribing to data | This set of procedures allows a Data subscription service Consumer to specify a data instance (for a registered DME type) to be delivered to it, and to choose the delivery service to use (e.g. push or pull). The data instance is defined by information specified in clause 5.2.1. Subscribe data is a procedure that initiates the delivery of a data instance in potentially multiple chunks of data. A data subscription can be stopped using the Unsubscribe data procedure. A data subscription can be updated using Update data subscription procedure and a data subscription can be queried using Query data subscription. The following procedures are defined: • Subscribe data: The Service Consumer provides, to the Data subscription service Producer, information on the data it wants to subscribe to be based on the DME type information retrieved using the Discover DME types procedure. • Notify data availability: The Service Consumer is provided information on the availability and retrieval scheme of the subscribed data instance. As a precondition, the Service Consumer should have used the Subscribe data procedure to create a subscription. • Update data subscription: The Service Consumer updates a data subscription. • Query data subscription: The Service Consumer queries a data subscription. • Unsubscribe data: The Service Consumer cancels a data subscription. • Query data subscription status: The Service Consumer uses this procedure to query the status of data subscription by providing the data job identifier. • Notify change of data subscription status: The Service Consumer is provided information on the changes in the status of the data subscription. Data production is handled as part of data subscription and whenever there are changes in the data production it will be notified as part of the data subscription status change. The procedures for delivery of data instances are described in clause 5.2.6. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.6 Data delivery services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.6.1 Overview | Data delivery is handled through a set of services as defined below which deliver data as requested using the Request data procedure (see clause 5.2.4.2) or the Subscribe data procedure (see clause 5.2.5.2) or indicated using the Create data offer procedure (see clause 5.2.6). Data delivery messages relate to a particular data request, data subscription or data offer. The data can be delivered in different ways, e.g.: from a REST endpoint, via a message bus or from an object store location. The means where and how the data can be retrieved can be made known to the recipient of the data by different means as part of the Request data, Subscribe data, Notify data availability, or Create data offer procedure. NOTE: Additional procedures for data delivery can be added in later releases. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.6.2 Pull data service | The pull data service allows the Service Consumer to obtain data via a pull mechanism from the Service Producer. Retrieval of data can occur once or multiple times (polling). For data consumption, Data Consumers consume this service and the Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 18 For data collection, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service and Data Producers produce this service. The following procedure is defined: • Retrieve data: The Service Consumer retrieves, from the Service Producer, data instances about whose existence the Service Consumer has been informed as part of the Request data, Notify data availability, or Create data offer procedure, using a pull communication mechanism. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.6.3 Push data service | The push data service allows the Service Consumer to push data to the Service Producer. For data consumption, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service and Data Consumers produce this service. For data collection, Data Producers consume this service and the Data management and exposure functions in the SMO/Non-RT RIC framework produces this service. The following procedure is defined: • Push data: The Service Consumer provides, to the Service Producer a data instance using a push communication mechanism as arranged as part of the Request data, Subscribe data, or Create data offer procedure. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.6.4 Point to multipoint data streaming service | This service allows each Data Producer to deliver data to multiple Data Consumers using a message bus. It can be used as a delivery mechanism for data subscription or data offer. For data subscription, the Data management and exposure functions in the SMO/Non-RT RIC framework inform the Data Producer which data stream to use to send data. Further, they inform the Data Consumer which data stream to use to fetch data. For data offer, the Data management and exposure functions in the SMO/Non-RT RIC framework inform the Data Producer which data stream to use to send data. The following procedures are defined: • Send data to data stream: The Data Producer sends data to a stream that is distributed by the message bus. • Fetch data from data stream: The Data Consumer fetches data from a stream that is distributed by the message bus. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.7 Data offer service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.7.1 Overview | Data Producers consume this service to request producing data to the Data offer service Producer for immediate collection and storage. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.7.2 Managing a data offer | This service allows a Data Producer to declare to the Data offer service Producer that it intends to produce data instances for immediate collection and storage by the latter. Prior to creating a data offer, the Data Producer has registered the related DME type. The Data Producer provides information on the data that it intends to provide based on the DME type information it has provided during data registration (see clause 5.2.2.2) and specifies additional characteristics of the data instance it intends to provide, similar to the information passed in the data request or data subscription (see clauses 5.2.4.2 and 5.2.5.2). ETSI ETSI TS 104 228 V11.0.0 (2026-02) 19 The Data Producer can further indicate that it no longer intends to produce data for a data offer by deleting the offer. The Data offer service Producer can indicate to the Data Producer that it does no longer wishes to receive data related to the offer by sending a data offer termination notification to the Data Producer, subsequently stopping collecting data related to the offer and terminating the offer. The following procedures are defined: • Create data offer: A Data Producer provides, to the Data offer service Producer, information on the data it intends to deliver based on the DME type information passed during the Register DME type procedure. In case the push data service is intended to be used for data delivery, the Data offer service Producer provides to the Service Consumer information regarding the endpoint on which to receive the pushed data. In case the pull data service is intended to be used for data delivery, the Data offer service Producer provides to the Service Consumer information regarding the endpoint on which to receive the data availability notifications. • Terminate data offer: A Data Producer terminates a data offer it has created. • Notify data offer termination: The Data offer service Producer provides, to the Data Producer, a notification that it intends to stop collecting data from the data offer and terminating the offer. Following the reception of such notification, the Data Producer shall not deliver further data related to the data offer. The procedures for the delivery of data instances are described in clause 5.2.6. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3 A1-related Services | |
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 supported A1 policy types. • Querying the status of A1 policies. • Subscribe to event notifications related to A1 policies. • Registration and deregistration of EI types. |
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 delete an A1 policy; • subscribe to A1 policy enforcement status changes. The term "A1 policy management service Producer" refers to the A1-related functions in the SMO/Non-RT RIC framework acting as Service Producer of the A1 policy management service. The term "A1 policy management service Consumer" refers to an rApp acting as Service Consumer of the A1 policy management service. NOTE 1: Another name for this service that does not depend on southbound interface naming is not defined in the present document. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 20 NOTE 2: The terms A1 policy type, A1 policy type identifier, A1 policy and A1 policy identifier refer to definitions made for the A1-P service over the A1 interface, see A1AP [1], and are used unchanged in the procedures of the A1 policy management service over the R1 interface. |
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 policy type availability changes: An A1 policy management service Consumer can use this procedure to subscribe to notifications on policy type availability changes, i.e. when an A1 policy type becomes available or when an A1 policy type becomes unavailable. • Query A1 policy type: An A1 policy management service Consumer can use this procedure to query the details of an A1 policy type by providing the A1 policy type identifier. The A1 policy management service Producer will respond with information about the A1 policy type. • Query A1 policy identifiers: An A1 policy management service Consumer can use this procedure to query for the A1 policies, or a subset of the A1 policies by providing query parameters such as A1 policy type identifier or Near-RT RIC identifier. The A1 policy management service Producer will return the list of A1 policy identifiers that matches with the query criteria. • Query A1 policy: An A1 policy management service Consumer can use this procedure to query for the details of an A1 policy by providing the A1 policy identifier. The A1 policy management service Producer will respond with information about the A1 policy. • Create A1 policy: An A1 policy management service Consumer can use this procedure to create an A1 policy by providing the below parameters: - Information about the A1 policy. - A1 policy type identifier. - Near-RT RIC identifier. On receiving the request, the A1 policy management service Producer determines whether the A1 policy type is supported by the Near-RT RIC, assigns an A1 policy identifier for the new A1 policy, and informs the A1 policy management service Consumer on the outcome of the A1 policy creation. • Update A1 Policy: An A1 policy management service Consumer can use this procedure to update an A1 policy by providing the below parameters: - Information about the A1 policy. - A1 policy identifier. On receiving the request, the A1 policy management service Producer determines whether the A1 policy is available in the Near-RT RIC and informs the A1 policy management service Consumer on the outcome of the A1 policy update. • Query A1 policy status: An A1 policy management service Consumer can use this procedure to query the enforcement status of a single A1 policy by providing the A1 policy identifier. The A1 policy management service Producer will respond with the enforcement status of the A1 policy. • Subscribe A1 policy status: An A1 policy management service Consumer can use this procedure to subscribe to status changes of A1 policies by providing either a list of A1 policies or a list of Near-RT RIC identifiers or a list of policy type identifiers. i.e. when A1 policies status becomes enforced or not enforced. • Query A1 policy status subscription: An A1 policy management service Consumer can use this procedure to query an A1 policy status subscription. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 21 • Update A1 policy status subscription: An A1 policy management service Consumer can use this procedure to update an A1 policy status subscription. • Unsubscribe A1 policy status: An A1 policy management service Consumer can use this procedure to unsubscribe from status changes of A1 policies. • Notify A1 policy status changes: An A1 policy management service Consumer is provided information on the status change of an A1 policy (i.e. when status changes from enforced or not enforced). • Delete A1 policy: An A1 policy management service Consumer can use this procedure to delete an existing A1 policy. The A1 policy management service Producer will respond with the outcome of the A1 policy deletion. NOTE: In the responses of the above procedures, the A1 policy management service Producer can either use stored information that has already been received via the A1 interface (e.g. information on available A1 policy types), or information directly resulting from an A1 procedure performed due to the R1 procedure (e.g. creation of an A1 policy). |
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 registered in the DME functions. On receiving the request, the A1 enrichment information functions can subscribe EI source data from DME functions using the EI source data type. In the response, the A1 enrichment information functions inform the rApp on the EI type capabilities that it is registered to provide. • Deregister EI type: An rApp can use this procedure to deregister EI types that it has previously registered, but that it is no longer able to produce. |
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 related to the network. • To obtain the current configuration of the network. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 22 • To provision changes of the configuration of the network. • To obtain additional information related to the network. |
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 the information, and how this relates to the Data management and exposure services, is not defined in the present document. |
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 of filtering criteria to control what is returned as result. |
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. to acknowledge or unacknowledge it). |
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 criteria to determine the set of information returned. NOTE: How to query the information, and how this relates to the Data management and exposure services, is not defined in the present document. |
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 allows the Service Consumer to access configuration information pertaining to the managed entities, as obtained by the CM service Producer. The CM service further allows the Service Consumer to request configuration changes related to the managed entities. NOTE: As a preliminary definition in the context of R1, the term "managed entities" represents (i) the RAN nodes and RAN functions managed by the SMO via O1 or M-plane interfaces, and (ii) the group of these known as RAN-specific network slice subnets. The exact definition of the term "managed entity" is not defined in the present document. The following capabilities are provided by the CM service Producer over the R1 interface: • Retrieving configuration schemas. • Reading configuration data. • Writing configuration changes. |
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 will respond with the requested schemas. The schemas provide information about which configuration attributes are supported by the managed entities. |
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 entities from the CM service Producer, subject to optional filtering criteria. The CM service Producer responds to the Service Consumer by providing the requested configuration data or indicates a failure with an appropriate cause. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 24 |
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 entities. The CM service Producer responds to the Service Consumer with the status of the write operation for the configuration changes requested by the Service Consumer or indicates a failure with an appropriate cause. |
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. - Infrastructure Monitoring. - Infrastructure Provisioning. - Infrastructure Lifecycle Management. - Infrastructure Software Management. • To obtain information related to O-Cloud deployment management such as: - Deployment Inventory. - Deployment Monitoring. - Deployment Lifecycle Management. • To provision changes of the configuration of the O-Cloud. • To obtain additional information related to the O-Cloud. NOTE: Details about O-Cloud deployment management services, provision of configuration changes, additional information related to the O-Cloud is not defined in the present document. |
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 information related to infrastructure resource inventory and event notification service of O-Cloud. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 25 • Query O2ims_InfrastructureMonitoring related information: This service procedure allows to query information related to telemetry reporting. • Query O2ims_InfrastructureProvisioning information: This service procedure allows to query information related to O-Cloud provisioning services. • Query O2ims_InfrastructureLifecycleManagement information: This service procedure allows to query information related to support of procedures for the automation of O-Clouds lifecycle events. |
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 to telemetry reporting. |
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 model training capability (optional). • Storage of an AI/ML model. • Monitoring the performance of a deployed AI/ML model. • Retrieving the model location details of an AI/ML model. • Requesting the deployment of an AI/ML model. • Querying AI/ML model inference capabilities. • Requesting inference of an AI/ML model. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 26 The AI/ML workflow services include AI/ML model management and exposure services, which are produced by the AI/ML workflow functions. An AI/ML model is identified by a model identifier, which includes model name, model version and artifact version. Model identifier and model-related information can be registered, discovered and de-registered. The model identifier can be used by an rApp in the AI/ML workflow procedures. The cloud native application developer assigns the model name and the model version as part of an rApp package for model onboarding, see clause 6 in OAM architecture [10]. The model name and model version are not changed after onboarding or after rApp deployment with the AI/ML model, or after training by an AI/ML model training service Producer. If the AI/ML model needs to be upgraded, the cloud native application developer updates the model version, and the upgraded model is onboarded as part of a new rApp package. The onboarded AI/ML model comes pre-trained, or is specialized during onboarding, and this is reflected in the initial value of the artifact version of the AI/ML model. After the registered AI/ML model has been trained by an AI/ML model training service Producer, the artifact version is updated. AI/ML model Producer refers to an rApp that can register an AI/ML model and provides model-related information. When an AI/ML Model has been registered, it can be trained by authorized AI/ML Model Trainers and is available for discovery and deployment, by authorized AI/ML Model Consumers. NOTE 1: The AI/ML model Producer acting in the run-time process is related to the rApp provided for onboarding, with an AI/ML model in the rApp package, by the cloud native application developer acting in the design-time process. AI/ML model Trainer refers to an rApp that can train an AI/ML model, store a new AI/ML model artifact version, and provides training-related information. model training can be initiated via the AI/ML Model training service. Model storage and deletion can be initiated via the AI/ML model storage service. AI/ML model Consumer refers to an rApp that can discover and request deployment or inference of AI/ML model artifact versions of an AI/ML model. AI/ML model discovery allows an AI/ML model Consumer to discover AI/ML model identifiers and AI/ML model metadata based on registered AI/ML models and provided selection criteria. AI/ML model change notifications allows AI/ML model Consumer to be notified about changes of the subscribed AI/ML models. NOTE 2: Deployment of an rApp with an AI/ML model, e.g. after AI/ML model discovery, is not specified in the present document. AI/ML model performance monitoring allows authorized AI/ML model performance monitoring service consumers to monitor the performance of deployed AI/ML models and receive periodical or event based performance related information. AI/ML inference service allows authorized AI/ML model Consumers to request the inference of an AI/ML model. AI/ML inference service Producer provides model performance information via the AI/ML model performance monitoring service. |
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 following procedures are defined: • Register AI/ML model: An AI/ML model Producer uses this procedure to register an AI/ML model. On receiving the request, the AI/ML model management and exposure service Producer determines whether the AI/ML model Producer is authorized to register the AI/ML model. In the response, the AI/ML model management and exposure service Producer informs the AI/ML model Producer of the AI/ML model registration details. • Query AI/ML model registration: An AI/ML model Producer can use this procedure to retrieve information about model registrations it has previously made. • Update AI/ML model registration: An AI/ML model Producer can use this procedure to update an AI/ML model registration it has previously made. • Deregister AI/ML model: An AI/ML model Producer can use this procedure to deregister an AI/ML model it has previously registered. |
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 service Producer determines whether the AI/ML model storage service Consumer is authorized to store the AI/ML model. In the response, the AI/ML model storage service Producer informs the AI/ML model storage service Consumer if the AI/ML model is stored and about the location of the stored AI/ML model if stored. • Store location of AI/ML model: An AI/ML model storage service Consumer uses this procedure to store the location of an AI/ML model. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to store location of the AI/ML model. In the response, the AI/ML model storage service Producer informs the AI/ML model storage service Consumer if the location of the AI/ML model is stored. • Delete AI/ML model: An AI/ML model storage service Consumer can use this procedure to delete an AI/ML model previously stored. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to delete the AI/ML model. the AI/ML model storage service Producer informs the AI/ML model storage service Consumer that the AI/ML model is deleted. • Delete location of AI/ML model: An AI/ML model storage service Consumer can use this procedure to delete the AI/ML model location previously stored. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to delete the AI/ML model file location. In the response, the AI/ML model storage service Producer informs the AI/ML model storage service Consumer that the location of the AI/ML model is deleted. |
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 each registered AI/ML model, model identifiers and model metadata are provided as a response. The AI/ML model Consumer can only discover AI/ML models that it is authorized to access. |
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 and thereby receive notifications when AI/ML models have been registered or deregistered, when information has been updated, and when new model versions and/or artifact versions have been stored or deleted. The subscription is created for the Model Consumer based on the AI/ML models that it is authorized to access, i.e. the AI/ML model Consumer can only subscribe to get notified about model changes of AI/ML models that it is authorized to access. • Unsubscribe AI/ML models changes: An AI/ML model Consumer can unsubscribe from notifications regarding changes related to registered AI/ML models. • Notify AI/ML models changes: The AI/ML model management and exposure service Producer uses this procedure to notify a subscribed AI/ML model Consumer about changes related to registered AI/ML models. |
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. Register AI/ML model training capability is a procedure where an AI/ML model Trainer registers its capability to train AI/ML models to the AI/ML model management and exposure service Producer. Deregister AI/ML model training capability is a procedure where an AI/ML model Trainer declares the training capability is no longer available. |
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 training capability, it may provide information on, including but not limited to, the following: • Information on the training platform that can be provided, e.g. framework and library. • Information on available training resources. The following procedures are defined: • Register AI/ML model training capability: An AI/ML model Trainer uses this procedure to register the capability to train AI/ML models. On receiving the request, the AI/ML model management and exposure service Producer determines whether the AI/ML model Trainer is authorized to register the AI/ML model training capability. In the response, the AI/ML model management and exposure service Producer informs the AI/ML model Trainer if the AI/ML model training capability is registered. • Query AI/ML model training capability: An AI/ML model Trainer uses this procedure to query an AI/ML model training capability registration it has previously made. • Update AI/ML model training capability: An AI/ML model Trainer uses this procedure to update an AI/ML model training capability registration it has previously made. • Deregister AI/ML model training capability: An AI/ML model Trainer can use this procedure to deregister an AI/ML model training capability that it has previously registered. |
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 requests the deployment of a registered AI/ML model. The model identifier and target deployment location of the registered AI/ML model is provided in the request. The AI/ML model deployment Service Consumer can only request the deployment of registered AI/ML models that it is authorized to access. The AI/ML model deployment Service Consumer is notified of the outcome of the model deployment request. |
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 produce this service. |
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 information for training. The AI/ML training service Producer determines whether the AI/ML model training Consumer is authorized to request training of the AI/ML model. The AI/ML training service Producer creates the AI/ML model training job and responds to the AI/ML model training service Consumer with the training job identifier. • Query AI/ML model training job status: An AI/ML model training service Consumer uses this procedure to query AI/ML model training job status by providing the training job identifier that it has previously received. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 30 • Cancel AI/ML model training: An AI/ML model training service Consumer uses this procedure to request to cancel the training of an AI/ML model by providing the training job identifier that it has previously received. • Notify AI/ML model training job status change: An AI/ML training service Producer uses this procedure to notify an AI/ML model training service Consumer about a status change of an AI/ML model training job. |
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 related information is provided as part of the registration information. |
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 model identifier, information for the AI/ML model performance monitoring, and optionally a notification URI to receive regular performance related information of the specified deployed AI/ML model. The following procedures are defined: • Subscribe AI/ML model performance: AI/ML performance monitoring service Consumers can use this procedure to subscribe to specific or all performance related information of a deployed AI/ML model. Supported AI/ML model performance related information is provided as part of the AI/ML model registration information. In the request, AI/ML model performance monitoring service Consumers can specify whether to be periodically notified or only notified in the occurrence of a specific event (e.g. if the performance of a deployed AI/ML model drops below a certain threshold). On receiving the subscription request, the AI/ML model performance monitoring service Producer creates the subscription and informs the AI/ML model performance monitoring service Consumer of the subscription ID. • Notify AI/ML model performance: An AI/ML model performance monitoring service Producer can use this procedure to notify the AI/ML model performance monitoring service Consumers about performance information related to a deployed AI/ML model. |
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 identifier, input data and output data. On receiving the request, the AI/ML inference service Producer determines whether the AI/ML model Consumer is authorized to retrieve the inference capability information. In the response, the AI/ML inference service Producer informs the AI/ML model Consumer regarding the AI/ML model inference capability information. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 31 • Request AI/ML model inference: An AI/ML model Consumer uses this procedure to request inference for an AI/ML model by providing the model identifier and input data. On receiving the request, the AI/ML inference service Producer determines whether the AI/ML model Consumer is authorized to request the inference of the AI/ML model. In the response, the AI/ML inference service Producer informs the AI/ML model Consumer of the model inference job identifier. • Cancel AI/ML model inference: An AI/ML model Consumer uses this procedure to request to cancel the inference by providing the inference job identifier that it has previously received. |
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. The Service Consumer can only query the AI/ML model training capability information of the AI/ML models that it is authorized to access. In the response, the Service Producer informs the Service Consumer AI/ML model Trainer rAppIds and the registered AI/ML model training capability information. |
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 Published as final version by adding the A1 ML model management services, procedure to query of AI/Ml model training capabilities , procedure to retrieve the status of the data request and data subscription and updated the existing procedures for service registration and authorization service. 2024.07.11 09.00 Published final version by adding production capability related to DME type, added AI/ML model inference service, updated query procedure for subscription data and updated subscription procedures for SME. 2024.03.18 08.00 Published final version by adding AI/ML performance monitoring procedures and aligning the terms Producer and Consumer. 2023.11.20 07.00 Published final version by adding the AI/ML related service procedures and updated the data types to DME types and added the data streaming service in DME service. 2023.07.27 06.00 Published as Final version 06.00. 2023.03.24 05.00 Published as Final version 05.00. 2022.11.18 04.00 Published as Final version 04.00. 2022.07.27 03.00 Published as Final version 03.00. 2022.03.31 02.00 Published as Final version 02.00. 2021.11.23 01.00 Published as Final version 01.00. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 33 History Version Date Status V11.0.0 February 2026 Publication |
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 HbbTV® and cited in the present document are the most widespread at the moment. Further DRM systems may be considered for addition in a future revision of the present document subject to meeting the requirements listed in clause 10 of the present document. The present document does not mandate a DRM system or version, this is a commercial choice for stakeholders. |
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 are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 796: "Hybrid Broadcast Broadband TV". [2] ETSI TS 103 285: "Digital Video Broadcasting (DVB); MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks". [3] ISO/IEC 23000-19: "Information technology — Multimedia application format (MPEG-A) Part 19: Common media application format (CMAF) for segmented media". . [4] ISO/IEC 23001-7:2023: "Information technology - MPEG systems technologies - Part 7: Common encryption in ISO base media file format files". [5] Open IPTV Forum: "Release 2 specification, volume 5 (V2.3) Declarative Application Environment". [6] W3C® Recommendation 21 August 2025: "Encrypted Media Extensions". |
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] DASH-IF IOP-6 V5.0.0 (2022-01): "DASH-IF Interoperability Points; Part 6: Content Protection". [i.2] Google®: "Getting Started with Widevine™ DRM". [i.3] Google®: "Widevine™ DRM Architecture Overview". ETSI ETSI TS 104 227 V1.1.1 (2026-01) 9 [i.4] Google®: "Getting Started Widevine™ DRM on Devices". [i.5] Github: "Widevine™ Pssh Data proto format", 2016. [i.6] ETSI TR 103 824 (V1.1.1): "Unit Test Descriptions for Hybrid Broadcast Broadband TV". . [i.7] HbbTV® Association: "Reference Video Application". [i.8] Microsoft®: "DASH Content Protection using Microsoft PlayReady™", Version 1.3, February 15, 2018. NOTE: PlayReady™ is one example of a DRM system. The present document includes another example Widevine™ and defines objective criteria for adding more examples. [i.9] Microsoft®: "PlayReady™ Test and Documentation Server: Query String Syntax Documentation". [i.10] Microsoft®: "HbbTV Content Protection Using Microsoft PlayReady™". NOTE: This document is only available to PlayReady™ licensees. [i.11] Smart TV Alliance: "Widevine™ API Mapping", Version 1.0, 7th January 2013. NOTE: Widevine™ is one example of a DRM system. The present document includes another example PlayReady™ and defines objective criteria for adding more examples. [i.12] LG: "DRM Messages". [i.13] Microsoft®: "Content Packaging and Delivery". [i.14] Microsoft®: "PlayReady Header Specification". [i.15] Microsoft®: "License Persistence". [i.16] Microsoft®: "Security Level". [i.17] Microsoft®: "PlayReady Integration to HbbTV", Version 0.95, February 2012. [i.18] Recommendation ITU-T X.667: "Information technology - Procedures for the operation of object identifier registration authorities: Generation of universally unique identifiers and their use in object identifiers". [i.19] WHATWG: "HTML Living Standard". |
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 the content from illegal copying and distribution, with restrictions defined in dedicated service levels and output protection levels of the DRM systems. It also enables content providers to control who can access the content in a defined resolution, and the length of time it can be accessed. Content licensors, especially the Hollywood studios, have been defining increasingly stringent content protection requirements and obligations, e.g. for HD 1080p, UHD 2160p/HDR format content or early release window content, which they then require to be implemented by service providers/licensees. This may include the obligation to use approved high-level DRM systems that are already integrated with a hardware based Trusted Execution Environment (TEE), such as Microsoft PlayReady™'s SL3000 hardware-based security. End user devices using Microsoft PlayReady™ DRM and requesting UltraHD resolution licensed content are often required to ensure a SL3000 and HDCP 2.2 on digital outputs. As content protection technologies are not standing still, further advanced profiles of modern DRM can be expected in the future. While the terminals used to play HbbTV® applications are generally equipped with current versions of DRM systems (as they are generally required by the non-HbbTV® applications also supported on the terminals), many terminals have historically not fully integrated the HbbTV® implementation and the DRM system, which prevented end users using HbbTV® applications to access high value content. |
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: Normally this request would be handled by an application however in some cases a native DASH player may make a request without involving an application as explained in clause 5.4. • The DRM license server delivers a license to the DRM implementation in the media consumption device. Normally this license will pass through an application however in some cases a native DASH player may process this response without involving an application. • The DRM license contains at a minimum the content encryption key, and generally includes the terms of use or required protection for the content and a license validity duration. • The DRM implementation validates the license and extracts the key to decrypt the content. • The media decoding pipeline in the media consumption device is configured to include a decryption element that in turn is configured using the key. ETSI ETSI TS 104 227 V1.1.1 (2026-01) 11 • The content is played. Some variations on the theme above include the following: • The license may be pre-provisioned before attempting to play the content. • Only the video is encrypted and not the audio. Protecting live content is more complex than protecting on-demand content and often involves advanced features like key rotation addressed in clause 5.6.2 below. |
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 challenges, common encryption was developed. Common encryption allows content owners to encrypt their content once, using a single encryption key, which can be used across multiple devices and platforms with different DRM technologies. This approach simplifies content distribution management, reduces costs, and ensures a consistent user experience across different platforms. License acquisition and processing remains specific to each different DRM system and is not a matter for a Technical Specification, therefore not included in the present document Multi-DRM builds on top of common encryption by adding specific signalling for each supported DRM in a standardized format to the content encrypted with the common encryption key. This allows content to be accessed and decrypted using the appropriate matching DRM implementation on the device. This approach helps content owners to cater to different user preferences and device capabilities, while still providing a consistent user experience. Additionally, multi-DRM helps content providers to comply with industry standards and regulations for content protection, which is crucial in preventing piracy and unauthorized distribution of digital content. Common encryption is defined by MPEG in ISO/IEC 23001-7 [4]. More information about using MPEG common encryption can be found in clause 8 of ETSI TS 103 285 [2] and DASH-IF [i.1]. |
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 10.4.2 of that document. More recently, DRM systems have started supporting Apple®-compatible 'cbcs' as well as 'cenc' however, at the time of writing, there is still a large installed base of devices only supporting 'cenc'. Supporting 'cbcs' in addition to 'cenc' is a trend in the industry as it enables unifying support across all devices with a common media format, such as Apple® and others. ETSI TS 102 796 [1] from (V1.6.1) onwards defines an extension to the XML capabilities mechanism that enables applications to discover support for cbcs 1:9. The working draft of EME [6] has, since December 2019, defined an encryptionScheme of 'cbcs-1-9' for use in MediaKeySystemMediaCapability to discover support for cbcs 1:9. NOTE: The reference video application [i.7] includes tests for cbcs 1:9 as well as 'cenc'. Clause A.1.2 includes data on the extent of support for cbcs 1:9 in a sample of current and previous terminals. ETSI ETSI TS 104 227 V1.1.1 (2026-01) 12 5.4 Carriage of DRM information in ISO BMFF files and DASH manifests |
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 carried in the following locations: • Within a ContentProtection element in the MPD, as described in clause 5.4.2. This is the preferred location for the 'pssh' box as it allows players to perform advance license acquisition, which is beneficial for the license servers as well to reduce peak loads. • In the 'moov' box in the initialization segment. The same 'pssh' box is carried in this location for all Representations in the AdaptationSet. If a 'pssh' box for a DRM system is present within a ContentProtection element in the MPD, all 'pssh' boxes for that DRM system in the 'moov' box are ignored. • In the 'moof' box in the media segment. The same 'pssh' box is carried in this location co-timed for all Representations in the AdaptationSet. This location is used when key rotation is employed, usually in association with a 'pssh' box in a ContentProtection element in the MPD. If the 'pssh' box is carried in the media segments, it is present in every media segment in every Representation to ensure that the player is able to start playing the content from any location. The DRM may require information from the 'pssh' boxes in both the initialization segment (or MPD, as appropriate) and the media segment in order to obtain license and keys. Once a player has selected a DRM to use to decrypt the protected content, it can filter all of the 'pssh' boxes based on the UUID for that DRM, matching this against the value in the SystemID field in the 'pssh' box. There may be one or more 'pssh' boxes in each location. After applying the above filtering, the player needs to pass the remaining 'pssh' box(es) to the DRM to enable it to acquire the license and generate the required keys. |
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. The Sample Auxiliary Information, which includes the initialization vector and NAL subsample byte ranges, may be stored in a Sample Encryption ('senc') box. If the Sample Auxiliary Information is not present for a sample, there may be a default value in the 'tenc' box, for when pattern-based encryption is in effect, in the default_constant_IV field. NOTE: Clause 10.4.1 of ISO/IEC 23001-7 [4] requires that constant IVs be used with cbcs encryption and excludes the use of sample IVs. |
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 is encrypted (in the isProtected field). If the sample is not a member of a group or no 'seig' box is present for the group, the default key ID carried in the 'tenc' box in the default_KID field is used. This value may also be found in the MPD as described in clause 5.4.2. ETSI ETSI TS 104 227 V1.1.1 (2026-01) 13 |
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 attribute set to "urn:mpeg:dash:mp4protection:2011" and the value attribute set to "cenc" or "cbcs", which is the same string as in the scheme_type field in the scheme type box 'schm' which is in the protection scheme information box 'sinf' box. The value attribute allows the player to determine the encryption mode without having to read any of the media segments. For each DRM that could be used to obtain a key to decrypt the content, each AdaptationSet also has a ContentProtection element which may contain some of the elements and attributes defined by CENC (ISO/IEC 23001-7 [4]) and/or elements as defined by the DRM provider. Such a ContentProtection element has the schemeUri attribute containing a UUID URN identifying the DRM. NOTE 1: UUID strings are not case sensitive and may be expressed in upper or lower case. Refer to Recommendation ITU-T X.667 [i.18] for more information about how to format and construct a UUID in a URN. A player can use the DRM-specific ContentProtection elements to determine whether there is a match with any embedded DRMs that it supports. Alternatively, it may have a priori knowledge that it contains a suitable DRM. The elements and attributes defined by CENC (ISO/IEC 23001-7 [4]) are: • The attribute default_KID which may be added to the generic ContentProtection element. It is a copy of the value from the 'tenc' box. It contains a single key ID. • The element pssh which may be added as a child of the DRM-specific ContentProtection element and contains a binary copy of the 'pssh' box that would allow a license/key server to generate the license bound to the requesting device and associated with the default key ID and content. This is normally the same as (and takes precedence over) any 'pssh' box that might be present in an initialization segment. NOTE 2: The DASH-IF content protection and security specification [i.1] defines a dashif:laurl that can be used to add a license request URL to a DASH MPD in a DRM-system independent way. This is not believed to be used in the context of native DASH players in ETSI TS 102 796 [1] although it may be used included in JavaScript DASH players. • Clause 5.8.4.1.2 of DASH [i.1] defines an optional @robustness attribute that may be present in a content protection element to indicate the minimum robustness value required for playing back the associated Representations. |
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 commercial DRM. Clear Key is understood not to meet the requirements of global content providers however it may be suitable for a broadcaster making their own content available. When using Clear Key, the manifest only needs to include the cenc and clearkey drm elements. The init segment should signal just a generic cenc pssh (guid=1077efec-c0b2-4d02-ace3-3c1e52e2fb4b) box or no pssh boxes at all in the init segment. e.g. <ContentProtection cenc:default_KID="44332211-1234-1234-1234-112233441236" schemeIdUri="urn:mpeg:dash:mp4protection:2011" value="cenc"/> <ContentProtection schemeIdUri="urn:uuid:e2719d58-a985-b3c9-781a-b030af78d30e" value="ClearKey1.0"> ETSI ETSI TS 104 227 V1.1.1 (2026-01) 14 Combining Clear Key and regular commercial DRM in common encryption would be a serious concern for several organisations and is not recommended security practice. It would weaken the security of the other (commercial) DRM systems. Organisations considering doing this should explicitly confirm with their content and technology suppliers before doing so. NOTE 1: It has been suggested that, for at least one commercial DRM, it would be incompatible with the agreements governing its use. NOTE 2: This is explicitly prohibited by clause 8 of DASH-IF IOP-6 V5.0.0 [i.1]. |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 5.6 Advanced features |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.