hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3.2 Symbols | Void. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ELI European Legislative Identifier UCYBEX Universal Cybersecurity Information Exchange Framework 4 Universal Cybersecurity Information Exchange Framework (UCYBEX) |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.0 Cybersecurity information exchange models | The contemporary period of cybersecurity information exchange emerged in the 1990 timeframe and consisted of the exchange of combinations of incident, vulnerability, and threat information via repositories among a complex global community of product and service vendors, end users, and industry and government cyber secu... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.1 UCYBEX Framework - Repository architecture | The present document facilitates the exchange of cybersecurity information using a framework that establishes a design architecture for openness, diversity, extensibility, and interoperability. This global decentralised, autonomous framework architecture enables widespread sharing of cybersecurity resources including o... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2 UCYBEX Framework Resource Record Format and Values | |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.1 Overview | Figure 4.2-1: Mindmap of the UCYBEX Framework Resource Record, V1.0.1 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.2 UCYBEXversion | This required value describes the present UCYBEX Framework Resource Record specification version being used and expressed as three numbers separated by commas and set initially to 1.0.1. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.3 UCYBEXresourcetype | This required value describes the UCYBEX resource type in the following non-case-sensitive enumeration: list Another UCYBEX or compatible Framework Resource list spec Any technical specification for cybersecurity repository Any information repository for cybersecurity purposes enrichment Any cybersecurity enrichment in... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.4 UCYBEXresourcename | This required value describes the name of the resource without any constraints - prefaced by any related identifier associated with the name. For example, "ETSI TS 104 170 V1.0.0 - Rec. ITU-T X.1500 Cyber Security (CYBER); Universal Cybersecurity Information Exchange Framework - Repository". |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.5 UCYBEXresourceaddress | This required value describes the resource address location without any constraints - preferably as a persistent, precise, accessible Uniform Resource Identifier (URI) or a link capable of providing the resource. For example, https://www.etsi.org/deliver/etsi_ts/104170 [TBD]. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 10 |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.6 UCYBEXresourcecontact | This optional value describes the national incorporation jurisdiction using a recognized country identifier and contact information without any constraints for the entity maintaining and accessing the resource preferably including physical and location and useable email address. For example, "France, ETSI Secretariat, ... |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.7 UCYBEXresourceaccess | This optional value without any constraints describes any resource access controls, for example, "paywall" or "members only". The default when leaving blank is publicly available without constraints. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.8 UCYBEXresourcetrust | This optional value without any constraints describes any resource trust mechanisms such as a digital certificate. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.9 UCYBEXnormbindings | This optional value without any constraints describes any asserted normative binding, i.e. an asserted relationship for compliance with one or more obligations in a normative instrument, indicated with an instrument identifier such as a European Legislative Identifier (ELI) [i.3]. |
49a445bf75f8a5998725e61a6cfaf2d8 | 104 170 | 4.2.10 UCYBEXnote | This optional value without any constraints describes any useful attributes of the resource. ETSI ETSI TS 104 170 V1.1.1 (2026-02) 11 Annex A (normative): UCYBEX Framework Resource Record JSON Format V1.0.1 { "$schema": "http://[tbd]", "title": "JSON Schema for UCYBEX Framework Resource Record version 1.0.1", "$id": "h... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 1 Scope | The present document describes considerations for situations in which providers choose to adopt web-based portal solutions to respond to requests from Authorized Organizations. The present document describes portals and explains how existing ETSI TC LI specifications can be used to improve portal design. The present do... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 2 References | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 2.1 Normative references | Normative references are not applicable in the present document. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 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... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3 Definition of terms, symbols and abbreviations | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 976 [i.1] and the following apply: Authorized Organization (AO): any organization legally authorized to make requests and receive results provider: organization responding to a request (the organization that includes the Request Processing System)... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3.2 Symbols | Void. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 6 |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AO Authorized Organization API Application Programming Interface IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity RPS Request Processing System VIN Vehicle Identification Number |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4 Core concepts | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.1 Goal | The goal of the present document is to help people to adopt ETSI TC LI Technical Specifications i.e. full computer-to-computer API (Application Programming Interface). It is acknowledged that initially people might not be able to move to a full computer-to-computer system, and so portals can be a useful stepping stone.... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.2 Definition of a portal | A portal is defined to be a website hosted by, or on behalf of the provider which allows an Authorized Organization to type in requests and then receive results either through the website or delivered over other channels (not specified here). |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.3 Caveat | Adoption of the present document does not imply that a system is compliant with any ETSI TC LI Technical Specification; it is not a substitute for compliance with other ETSI TC LI standards. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.4 Reference design | The approach in Figure 4.4-1 is recommended. The key point is to run one system with two front ends (one for meeting an ETSI Technical Specification, and one for a portal). The goal is to make the front end systems as thin as possible i.e. to put most of the functionality in the main Request Processing System. Figure 4... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.5 Use of portals alongside systems with full APIs | It is clear that the full API is the best long-term solution for high volume uses, but the present document does not advise in favour or against running portals alongside an API solution. Clause 4.5 notes some benefits and drawbacks of doing this, in order to help people make decisions about use of portals. Considerati... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6 Security | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.1 General | The present document does not contain a full analysis of portal security, instead.it identifies some risks and issues to consider. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 8 |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.2 Clear boundaries of responsibility | The Responsible Owner at an AO is the person who takes responsibility for a request that is issued (Was it lawful? Was it correct? Did it go to the right place? Can I justify it?). The Responsible Owner at a Provider is the person who takes responsibility for how the request is handled (Did I check it was correct and a... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.3 Management of users | An important issue for portals is that the provider is responsible for management of the list of accredited users. In general, for a portal solution, the provider would be responsible for managing risks arising when users join or leave the Authorized Organization (AO), or where privileges are revoked. Verification of n... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 4.6.4 Other security points | Standard cyber security risks (e.g. Distributed Denial of Service attack) should be considered. It should be noted that an attack through either front end (see figure 4.4-1) can affect the central Request Processing System i.e. care should be taken around the security of both front ends. If a separate results channel i... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.1 List of parts of ETSI TC LI Technical Specifications | It is recommended that the following parts of an ETSI Technical Specification are used (where appropriate) as part of designing portals: 1) Fundamental model. The ETSI model has a clear boundary between what is AO-managed and what is provider-managed. There are strong reasons to have clear boundaries of responsibility:... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2 Use of ETSI TC LI specifications in a vehicles context | |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.1 Explanation | Clause 5.2 contains illustrations of the points listed in clause 5.1, specifically for a vehicles context. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.2 Fundamental Model | This point relates to ensuring that the boundaries of responsibility are clearly demarcated. The following transitions should be clear to all parties: • The point when the AO submits a request (i.e. an obligation is created on the provider). The AO user should be asked to confirm the submission of a request (with clari... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.3 Definitions | For vehicles, it is recommended to use the standardized definitions for these concepts (and others where appropriate): • VIN. • Location. • Time and date. • IMSI and IMEI. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.4 Identifiers | It is helpful to have a clear system of identifiers for every party (AO or provider). It is useful to have a unique name for each organization to prevent confusion. For example, the AOs involve should work together to ensure that they do not re-use common acronyms. It is out of scope to describe personal details for an... |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.5 Request types | It is recommended that a portal uses any of the request types from ETSI TS 103 976 [i.1], clause 7, that are appropriate. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.6 Results | Wherever one of the ETSI TS 103 976 [i.1] request types has been used, it is recommended to use the accompanying results format. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.7 Workflow | It is recommended to follow the steps in ETSI TS 103 120 [i.2], clause H.2.4. The benefit is that it is clear at all items who is supported to be responding next. |
1096bfb94fa35cd5d7b1ea77a312f2d0 | 104 196 | 5.2.8 Use of ETSI TC LI data structures | No additional comments on this topic are made in the present document. ETSI ETSI TR 104 196 V1.1.1 (2026-02) 11 Annex A: Change history Status of Technical Report ETSI TR 104 196 Considerations for using portals to support requests from Authorized Organizations TC LI approval date Version Remarks January 2026 1.1.1 Fir... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 1 Scope | The present document specifies the general aspects and principles of the R1 interface. It is part of a TS-family covering the R1 interface specifications. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 2 References | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 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... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 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... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3 Definition of terms, symbols and abbreviations | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3.1 Terms | For the purposes of the present document, the following terms apply: AI/ML model: algorithm that applies AI/ML techniques to produce model output data based on model input data AI/ML model training: process to train an AI/ML model by learning the input/output relationship in a data driven manner and obtain a trained AI... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3.2 Symbols | Void. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence API Application Programming Interface CM Configuration Management DME Data Management and Exposure DMS Deployment Management Service EI Enrichment Information FM Fault Management FQDN Fully Qualified Domain Name ID I... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4 General Aspects of R1 Interface and R1 Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.1 Introduction | The following clauses cover the general aspects for R1 interface. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.2 General principles | The general principles for the specification of the R1 interface are as follows: • The R1 interface is an open logical interface within the O-RAN architecture between the rApps and the Non- RT RIC framework. • The R1 interface supports the exchange of control signalling information and the collection and delivery of da... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.3 Specification objectives | The R1 interface specifications shall: • Facilitate inter-connection between rApps and Non-RT RIC framework supplied by different vendors. • Provide a level of abstraction between rApps and SMO/Non-RT RIC framework that can be the consumers and or producers of R1 services. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 4.4 Capabilities | As described in [2] the R1 interface shall support: • Registration and Deregistration of R1 services. • Authentication of rApps. • Authorization of requests to access R1 services. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 10 • Facilitation of service discovery and service notifications for the registered R1 Services. • Re... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5 R1 Services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1 Service management and exposure services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.1 General | As described in the Non-RT RIC Architecture specification [3], the Service management and exposure services provided by the SMO/Non-RT RIC framework enable: • rApp registration. • Registration of services. • Discovery of services. • Authentication and authorization. • Communication support. • Bootstrap (optional). Addi... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.2 Bootstrap service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.2.1 Overview | If the Bootstrap service is provided by the SMO/Non-RT RIC framework, an rApp can use it to discover the endpoints of the Service management and exposure services. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 11 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.2.2 Bootstrap | The endpoint on which the Bootstrap service can be reached shall be version independent. It can be provisioned to the rApp or can be obtained e.g. from a fixed well-known address or FQDN. The following procedure is defined: • Discover bootstrap: This procedure enables determination of the endpoints of the other Service... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.3 Service registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.3.1 Overview | This service allows Service Producers to register information about the R1 services they produce. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.3.2 Registration of services | Register service is a procedure where a Service Producer declares its produced services to the Service management and exposure services Producer. Upon successful registration of a service, the information about the services is stored. Deregister service is a procedure where a Service Producer declares which services ar... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.4 Service discovery service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.4.1 Overview | This service allows Service Consumers to discover R1 services they intend to consume. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 12 |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.4.2 Discovery of services | For service discovery, a set of procedures enables a Service Consumer to retrieve information on available services based on selection criteria. NOTE: Available services either have been registered by service-producing rApps using the Service registration service (in case these are produced by rApps) or have been made ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.5 Void | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6 Authentication and authorization | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6.1 Overview | Authentication and authorization are realized as a combination of procedures and services that allow asserting the identity of Service Producers and Service Consumers and ensure that only authorized consumers can access the R1 services. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6.2 Authentication | Authentication will be performed to authenticate the Service Consumers and Service Producers to allow them to provide or access R1 Services. Service Consumers and Service Producers can initiate secure communication for R1 services after the authentication information is validated. Authentication procedures shall comply... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.6.3 Authorization | Authorization procedures are used to grant Service Consumers access to registered R1 services and to allow Service Producers to produce R1 services. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 13 Authorization can be based on a mechanism to enforce authorization by policies, where exposed R1 services are further subject to ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.7 rApp registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.7.1 Overview | The rApp consumes this service to register with the Service management and exposure services Producer. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.1.7.2 rApp registration management | The rApp consumes this service to register with the Service management and exposure services Producer and may provide the following information such as rApp name, vendor, software version, certificates, role of the rApp (Service Producer and / or Service Consumer), and security credentials. On successful registration, ... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2 Data management and exposure services | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.1 General | As described in the Non-RT RIC Architecture specification [3], the Data management and exposure services enable: • Registration of DME types. • Discovery of DME types. • Request for data. • Subscription to data. • Collection of data from Data Producers and consumption of data by Data Consumers. ETSI ETSI TS 104 228 V11... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.2 Data registration service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.2.1 Overview | Data Producers consume this service to register DME types. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.2.2 Registration of DME types | Register DME type is a procedure where a Data Producer registers its production capabilities related to a DME type. Query DME type registration is a procedure where a Data Producer queries its production capabilities related to a DME type that it has previously registered. Update DME type registration is a procedure wh... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.3 Data discovery service | |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.3.1 Overview | Data Consumers consume this service to discover available DME types. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.2.3.2 Discovery of DME types | This set of procedures enables a Data Consumer to retrieve information on the registered DME types. ETSI ETSI TS 104 228 V11.0.0 (2026-02) 16 Discovery of a DME type does not imply availability of data instances of that DME type. It is just an indication that Data Consumers can request or subscribe to data for that DME... |
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 i... |
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... |
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 f... |
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 initia... |
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 particu... |
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 ... |
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 man... |
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 ... |
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 i... |
e15f2d1f555fa3f2fcad6d758d937051 | 104 228 | 5.3 A1-related Services |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.