hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 7.2 Content providers, platforms and operators | Application developers, content providers, platforms and operators (and any other organization that is in the position of influencing the features of terminals in a given market) should note that better interoperability can be expected if they decide on a DRM system for which a detailed and open integration specificati... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 7.3 Terminals and terminal implementers | Neither the present document nor ETSI TS 102 796 [1] require implementations to support a specific DRM system in combination with HbbTV® applications. It is expected that future versions of ETSI TS 102 796 [1] will require at least one of the DRM systems in the present document be supported. Terminal implementers shoul... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8 Recommendations for stakeholders (informative) | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.1 Introduction | Most of the recommendations in this clause are forward looking and aspirational. They are based on the hoped evolution of the ecosystem over time following the publication of the present document, and of future versions of ETSI TS 102 796 [1] and related actions. Recommendations for stakeholders based on the current st... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.1 Introduction | This clause contains recommendations for content providers intending to use DRM with HbbTV® for the first time or to make significant changes to already deployed HbbTV® applications using DRM. Obviously, some of the contents of this clause will be well known to some organisations but it is expected that some will find ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.2 Identifying the content protection requirements | Clarity about which requirements apply to which content and the consequences is critical. • Countries such as USA produced content typically has the highest requirements, particularly for UHD. It may be that only devices produced since 2022 - 2023 meet the content protection requirements for UHD. These requirements may... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.3 Risk assessment and mitigation | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.3.1 Risk assessment | Content providers planning a new HbbTV® service or a significant change or enhancement to an existing service should do a risk assessment whether DRM is involved or not. For services involving DRM, some example risk factors that should be considered include the following: • Is the service on-demand (which is lower risk... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.3.2 Mitigation - Communication with implementers | NOTE: This clause is very important for high-risk services, useful for medium-risk services and may be reviewed for low-risk services. Communication with implementers is important. A non-exclusive list of points that should be considered include the following: • Unless the DRM system and supplier for encoding, packagin... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.3.3 Mitigation - Test applications and test streams | NOTE: This clause is very important for high-risk services, useful for medium-risk services and may be reviewed for low-risk services. There is no substitute for a content provider having a test application and test streams that use the exact same supplier, equipment, tools and settings as their real service uses or wi... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.3.4 Mitigation - Enhanced testing by the application/service developer | NOTE: This clause is very important for high-risk services, useful for medium-risk services and may be reviewed for low-risk services. Many application/service developers will test applications and services on a small number of terminals themselves. One way to reduce risk is increasing the number of terminals on which ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.2.3.5 Mitigation - Certification of Terminals | NOTE: This clause is very important for high-risk services, useful for medium-risk services. The cost and overhead are probably excessive for low-risk services. Content providers and platforms may operate a certification scheme for terminals, probably linked to some kind of 'allow list' of certified terminals. Certifyi... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.3 Confirming the Security of the Application Environment | In addition to a DRM (which secures the content distribution) some commercial use cases may also require some 'hardening' of the HbbTV® application environment to help prevent DRM licenses being granted to unauthorised users. HbbTV® specification provides some mechanisms such as clause 11.8 of ETSI TS 102 796 [1] to pr... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 8.4 Recommendations given the 2024 status of the ecosystem | NOTE: This clause contains recommendations for content providers, platforms, operators, national trade associations and terminal implementers based on the status of the ecosystem at the time the present document is prepared and based on version 1.7.1 and earlier of ETSI TS 102 796 [1]. At the time of writing, the state... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9 Requirements for terminals | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1 DRM-system independent requirements | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.1 Media playback | The following media playback scenarios shall be supported with DRM encrypted content for each combination of DRM system, media playback API and license request API supported by a terminal: • Playback of encrypted video with encrypted audio: - Where supported by a DRM system, this shall include both scenarios with the s... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.2 Advanced playback of encrypted content | The following scenarios shall be supported with DRM encrypted content for each combination of DRM system, media playback API and license request API supported by a terminal: • Key changes within a piece of content including: - Decryption stops, the app obtains a new license and re-starts playback and decryption, decodi... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.3 Media profile and bandwidth requirements | Terminals supporting DRM with HbbTV® applications shall support presentation of DRM protected content carried over HTTP/TLS for which the combined channel bandwidth does not exceed the bitrates listed in clause 7.3.1.2 of ETSI TS 102 796 [1]. |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.4 Transition behaviour | The transition behaviour defined in clause 9.6.3 (and annex J) of ETSI TS 102 796 [1] shall apply where either one of the two media elements refers to content protected using DRM delivered via MPEG DASH or a MediaSource object. It is optional where both elements refer to content protected using DRM. If the second media... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.5 Requirements from ETSI TS 102 796 | The requirements in the following clauses from ETSI TS 102 796 [1] are particularly critical: • Clause 9.6.7 in relation to playback failure due to lack of a license that can decrypt DRM protected content. • Clause 10.2.4 in relation to reporting the presence of one or more DRM systems using the capabilities reporting ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.6 API specific requirements | |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.6.1 oipfDrmAgent | On terminals where the oipfDrmAgent API (see clause 6.3.2) is supported in combination with HbbTV® applications, the following requirements are highlighted: • If a license server does not return a license in response to sendDRMMessage being called then onDRMMessageResult shall be called with resultCode=2 and resultMsg ... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.1.6.2 EME | On terminals where the EME API (see clause 6.3.3) is supported in combination with HbbTV® applications, the following requirements are highlighted: • The present document does not require support for use of EME with the native DASH player and DRM (see clause 6.1). NOTE: Support for EME with the native DASH player is re... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 9.2 DRM-system specific requirements | In addition to the DRM-system independent requirements in the previous clause, DRM-system specific requirements shall also apply for each of the DRM systems are supported in combination with HbbTV® applications. These requirements are found in the annex to the present document for each DRM system concerned. ETSI ETSI T... |
1ff77486d6288acbbb2800dc0138e749 | 104 227 | 10 Criteria for adding DRM systems | Further DRM systems may be considered for addition in a future revision of the present document subject to meeting the following requirements: • The DRM system has been integrated with ETSI TS 102 796 [1]. • Unit tests have been defined and their descriptions independently reviewed that cover the integration between th... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 1 Scope | The present document specifies the Type Definitions for R1 Services. It is part of a TS-family covering the R1 interface specifications. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 2 References | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 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... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 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... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 3 Definition of terms, symbols and abbreviations | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 3.1 Terms | For the purposes of the present document, the terms given in R1GAP [2], R1AP [1] and the following apply: DME type: data type managed and exposed by the DME services and identified by a DME type identifier NOTE: The present document defines O-RAN specific DME types and O-RAN re-uses 3GPP data types where applicable. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 3.2 Symbols | Void. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface CP Control Plane DME Data Management and Exposure DN Distinguished Name JSON JavaScript Object Notation Non-RT RIC Non-Real Time Intelligent Controller OAM Operation and maintenance O-CU O-RAN Central Unit... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 4 R1 Application data model | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 4.1 Introduction | The present document together with R1AP [1] defines the realization of the R1 procedures defined in R1GAP [2] and R1UCR [3]. R1AP [1] contains the service description, service operations, resource definition and the API definition (including the Open API document) for the R1 services. The present document contains the ... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 4.2 Version conventions for the present document | The version number of the present document follows the "xx.yy" versioning scheme. There could be implications for the compatibility between implementations that uses DME types defined in different versions of the present document. An incremented "xx" version field of the present document could indicate that a new major... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1 Common definitions | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.1 Introduction | This clause provides common definitions applicable to multiple DME types. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.2 Identifiers and Metadata | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.2.1 DME type identifier | A DME type is identified by an identifier defined as dmeTypeId in R1AP [1], clause B.4.2. The DME type identifier consists of a namespace, name and a version. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.2.2 Data category | A DME type shall be assigned to at least one data category. Assigned data category values can be used as query parameter when searching for available DME types as specified in R1AP [1]. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.3 Versioning of DME types | When updating a DME type, the version in the DME type identifier (see clause 5.1.2.1) is updated according to SemVer [4] to reflect its compatibility with other DME types that have the same namespace and name. ETSI ETSI TS 104 232 V4.1.0 (2026-02) 9 Two DME types with the same namespace and name are incompatible if the... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.4 Schemas for DME types | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.4.1 General | The definition of a DME type is based on two schemas, a data production schema and a data delivery schema. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.4.2 Data production schema | The data production schema defines the structure for how to formulate parameters for the production of data instances of a DME type by a data job or a data offer. A data production schema can be based on data types defined in other specifications. Table 5.1.4.2-1 defines the attributes of the data production schema. Ta... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.4.3 Data delivery schema | The data delivery schema defines the structure of the delivered content resulting from the related data job or data offer. A data delivery schema can be based on data types defined in other specifications The data delivery schema type is defined in R1AP [1]. A DME type can be defined with one or more data delivery sche... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.5 Common data type definitions | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.5.1 Structured Data Types | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.5.1.1 Data type: CollectionWindow | This data type allows selecting the window for data collection and contains the attributes defined in table 5.1.5.1.1-1. ETSI ETSI TS 104 232 V4.1.0 (2026-02) 10 Table 5.1.5.1.1-1: Definition of data type CollectionWindow Attribute Name Data Type P Cardinality Description startTime TimeOfDay M 1 This attribute specifie... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.5.2 Simple data types | Table 5.1.5.2-1: Definition of simple data types Type Name Type Definition Description Applicability GranularityPeriod integer Granularity period simple data type is defined in ETSI 132 401 [12], clause 5.4.1.4. TimeOfDay string String with format as defined in IETF RFC 3339 [11], clause 5.6. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.5.3 Enumerations | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.1.5.3.1 Enumeration: DataCategory | Table 5.1.5.3.1-1: Enumeration DataCategory Enumeration Value Description PERFORMANCE_MANAGEMENT_DATA Category for DME type definitions for performance management data. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2 Definition of individual DME types | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.1 Introduction | This clause defines DME types. A DME type can be registered and discovered using the DME services. Data instances of a DME type can be produced by means of a data job or data offer. The definition of a DME type follows a template that includes but is not limited to: 1) the declaration of a DME type identifier; 2) the a... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2 DME type: RAN OAM PM data | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.1 DME type identifier | The definition of the DME type identifier is provided in clause 5.1.2.2. The DME type for RAN OAM PM data is identified as: DmeTypeId: ORAN:RanOamPmData:1.0.0. ETSI ETSI TS 104 232 V4.1.0 (2026-02) 11 |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.2 Data category | The definition of the data category is provided in clause 5.1.2.1. The DME type for RAN OAM PM data is categorized as: DataCategory: PERFORMANCE_MANAGEMENT_DATA. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.3 Data type definitions | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.3.1 Structured data types | 5.2.2.3.1.1 Data type: DataSelector This data type allows selecting the attributes of the data instance to be produced and contains the attributes defined in table 5.2.2.3.1.1-1. Table 5.2.2.3.1.1-1: Definition of data type DataSelector Attribute Name Data Type P Cardinality Description managementData ManagementData M ... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.3.2 Simple data types | None. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.3.3 Enumerations | None. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.4 Schemas | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.4.1 Data production schema | The data production schema is based on the JSON schema. { "$schema": "https://json-schema.org/draft/2020-12/schema", "description": "dataJobSchema for data subscription/data request", "version": "v1", "type": "object", "properties": { "dataSelector": { "managementData": {"$ref": "#/definitions/ManagementData"} }, "targ... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.2.4.2 Data delivery schemas | 5.2.2.4.2.1 Data delivery schema# 1 This data delivery schema is based on the XML schema and is defined in ETSI TS 128 532 [10], clause 12.3.2.4. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3 DME type: RAN OAM Trace Metrics | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.1 DME type identifier | The definition of the DME type identifier is provided in clause 5.1.2.2. The DME type for RAN OAM TraceMetrics is identified as: DmeTypeId: ORAN:RanOamTraceMetrics:1.0.0. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.2 Data category | The definition of the data category is provided in clause 5.1.2.1. The DME type for RAN OAM TraceMetrics is categorized as: DataCategory: RAN_OAM_TRACE_METRICS _DATA. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.3 Data type definitions | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.3.1 Structured data types | 5.2.3.3.1.1 Data type: DataSelector This data type allows selecting the attributes of the data instance to be produced and contains the attributes defined in table 5.2.3.3.1.1-1. Table 5.2.3.3.1.1-1: Definition of data type DataSelector Attribute Name Data Type P Cardinality Description supportedTraceMetrics String M 1... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.3.2 Simple data types | None. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.3.3 Enumerations | None. |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.4 Schemas | |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.4.1 Data production schema | The data production schema is based on the JSON schema. { "$schema": "https://json-schema.org/draft/2020-12/schema", "description": "dataJobSchema for data subscription/data request", "version": "v1", "type": "object", "properties": { "dataSelector": { "supportedTraceMetrics": { "$ref": "#/definitions/SupportedTraceMet... |
7050f5556c74f7b89a8e29ac1282c72d | 104 232 | 5.2.3.4.2 Data delivery schemas | 5.2.3.4.2.1 Data delivery schema# 1 This data delivery schema for streaming trace is based on the Trace record schema and is defined in ETSI TS 132 423 [17], clause 5.2. ETSI ETSI TS 104 232 V4.1.0 (2026-02) 23 Annex A (informative): Change history Date Version Information about changes 2024.03.14 04.01 Published final... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 1 Scope | The present document specifies the transport protocols for R1 services. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 2 References | |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 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... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 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... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 3 Definition of terms, symbols and abbreviations | |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 3.1 Terms | Void. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 3.2 Symbols | Void. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in O-RAN TS R1GAP [11] and the following apply: HTTP HyperText Transfer Protocol JSON JavaScript Object Notation JWT JSON Web Tokens TCP Transmission Control Protocol TLS Transport Layer Security |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 4 Transport protocols for R1 Services | |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 4.1 General | The R1 interface is defined between the rApps and the Non-RT RIC framework, as defined in R1GAP [11]. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5 REST based protocol stack | |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5.1 General | The layers of the protocol stack for the R1 interface are described in the following chapters: • TCP [2] provides the communication service at the transport layer, • TLS [10] is used as specified in SPS [13], clause 4.2 to provide secure HTTP [17] [18] connections, • HTTP [16] [17] [18] is used as application-level pro... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5.2 Network layer | As network layer at least one of IPv6 [9] or IPv4 [1] shall be supported. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5.3 Transport layer | TCP [2] shall be supported as transport protocol. NOTE: When using TCP as the transport protocol, an HTTP connection is mapped to a TCP connection. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5.4 Security | The specification of security controls on the R1 interface in SRS [12], clause 5.2.6.2 shall be followed. These security controls refer to the detailed specification of the support and use of TLS v1.2 and TLS v1.3 (IETF RFC 8446 [10]), and OAuth2.0 [14] with JSON Web Tokens (JWT) (IETF RFC 7519 [15]) in the O-RAN TS SP... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5.5 Application | As application layer, HTTP/1.1 [17] shall be supported, and HTTP/2 [18] should be supported. The HTTP semantics as defined in IETF RFC 9110 [16] shall be supported. HTTP over TLS (as defined in IETF RFC 9112 for HTTP/1.1 [17] and in IETF RFC 9113 [18] for HTTP/2) shall be supported. HTTP details such as use of standard... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 5.6 Data interchange | As a data interchange format, JSON [8] shall be supported. ETSI ETSI TS 104 233 V4.3.0 (2026-02) 8 |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6 Kafka based protocol stack | |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6.1 General | The Kafka based protocol stack for the R1 interface includes the following layers: • TCP [2] provides the communication service at the transport layer; • TLS [10] is used to provide secure connections at the security layer; • the Kafka Protocol Guide [20] is used at the application layer; • the data interchange layer c... |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6.2 Network layer | As network layer at least one of IPv6 [9] or Ipv4 [1] shall be supported. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6.3 Transport layer | TCP [2] shall be supported as defined in Kafka Protocol Guide [20]. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6.4 Security | The specification of security controls on the R1 interface in SRS [12], clause 5.1.2.1 shall be followed. |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6.5 Application | As application layer, Kafka Protocol Guide [20] version 3.0 or higher shall be supported. The Kafka semantics are defined in the Kafka Documentation [i.1]. R1 service procedures as defined in R1GAP [11] are mapped to the Kafka protocol in R1AP [19]. ETSI ETSI TS 104 233 V4.3.0 (2026-02) 9 |
6189a1f76fc571fd85565ed4db067de7 | 104 233 | 6.6 Data interchange | The Kafka based protocol stack for the R1 interface is agnostic to the data serialization format. ETSI ETSI TS 104 233 V4.3.0 (2026-02) 10 History Version Date Status V4.3.0 February 2026 Publication |
5321880801ac34d054cb1c648f063969 | 104 246 | 1 Scope | The present document defines the policy of the Technical Committee (TC) Terrestrial Trunked Radio and Critical Communications Evolution (TCCE) in the ETSI Coordinated Vulnerability Disclosure (CVD) [i.1]. This policy is based on the ETSI CVD and applies to ETSI deliverables of the TCCE [i.2] only. The present document ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.