hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
abbbcf930d69260eb2f458d7b29771a1 | 104 152-1 | 5.4.1.3.3 Specific message contents | All message contents are specified in ETSI TS 136 579-1 [1] (3GPP TS 36.579-1) and Annex A, in the subclauses referenced in each step, with the following clarifications. Table 5.4.1.3.3-1: SIP INVITE from SS (MCVideo Server) (Step 1, Table 5.4.1.3.2-1; Step 1, Annex A, Table A.4.1.3.3-1) Derivation Path: Annex A, Table... |
e341f05abb94e155b675f29c6779693c | 104 230 | 1 Scope | The present document specifies the Use cases and Requirements for R1 interface. |
e341f05abb94e155b675f29c6779693c | 104 230 | 2 References | |
e341f05abb94e155b675f29c6779693c | 104 230 | 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... |
e341f05abb94e155b675f29c6779693c | 104 230 | 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... |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.1 Terms | For the purposes of the present document, the following terms apply: DME type: data type managed and exposed by the DME services and identified by a data type identifier O-RAN Non-Real-Time RAN Intelligent Controller (Non-RT RIC): logical function in the SMO framework that enables non-real-time control and optimization... |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.2 Symbols | Void. |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Application Programming Interface AuthN Authentication AuthZ Authorization DME Data Management and Exposure FM Fault Management FWK Framework ID Identifier Non-RT RIC Non-Real Time RAN Intelligent Controller PM Performance Management SME S... |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.4 Conventions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.4.1 General | For the purposes of the present document, the conventions in the following clauses apply. |
e341f05abb94e155b675f29c6779693c | 104 230 | 3.4.2 Requirements | The requirements and solutions for use cases are based on the methodology specified in Recommendation ITU-T M.3020 [7], clause A.1.2. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 12 |
e341f05abb94e155b675f29c6779693c | 104 230 | 4 General | The R1 interface is defined between the rApps and the Non-RT RIC framework, as defined in R1GAP [1]. In the use case sequence flows, solid lines are used for the message interactions which are defined in O-RAN specifications. Dashed lines are used to represent the messages interactions that are not specified in O-RAN s... |
e341f05abb94e155b675f29c6779693c | 104 230 | 5 Requirements | |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.1 General | The general R1 interface requirements are specified in UCR [2]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.2 Security | The security requirements applicable to the R1 interface are specified in SRS [4], clause 5.2.6. |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.3 SME services functional requirements | This clause specifies the SME services functional requirements. The functional requirements are specified in table 5.3-1. Table 5.3-1: SME services functional requirements REQ Description Note REQ-R1-SME-rAppreg-FUN1 The SME services shall support registration of an rApp. REQ-R1-SME-rAppreg-FUN2 The SME services shall ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.4 DME services functional requirements | This cause specifies the DME services functional requirements. The functional requirements are specified in table 5.4-1. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 13 Table 5.4-1: DME services functional requirements REQ Description Note REQ-R1-DME-Regdatatype-FUN1 The DME services shall support registration, query, update... |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.5 RAN OAM-related services functional requirements | This clause specifies the FM, CM and PM services functional requirements. The functional requirements are specified in table 5.5-1. Table 5.5-1: FM, CM and PM services functional requirements REQ Description Note REQ-R1-OAM- FMservice-FUN1 The FM service shall support querying alarm information related to the O-RAN man... |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.6 AI/ML workflow services functional requirements | This clause specifies the AI/ML workflow services functional requirements. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 14 The functional requirements are specified in table 5.6-1. Table 5.6-1: AI/ML workflow services functional requirements REQ Description Note REQ-R1-AIML-Deploymodel-FUN1 The AI/ML workflow services shall ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 5.7 A1-related services functional requirements | This clause specifies the A1 policy management services and A1 enrichment information related services functional requirements. The functional requirements are specified in table 5.7-1. Table 5.7-1: A1 policy management services functional requirements REQ Description Note REQ-R1-A1P-FUN1 The A1 policy management servi... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6 Use cases for Service Management and Exposure | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1 SME use case 1: Registration and Bootstrap | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.1 Overview | This use case provides the description and requirements for registering an rApp with the SMO/Non-RT RIC framework. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.2 Background and goal of the use case | The rApp registration procedure registers the rApp to the SMO/Non-RT RIC framework. It may use the bootstrap service to discover the rApp registration API. To register an rApp, an rApp may pass relevant info that may include the rApp name, vendor, software version, and other information needed by the SMO/Non-RT RIC fra... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality that allows the rApp to retrieve the bootstrap information that enables it to discover the SME services; b) support functionality to authenticate the rApp; c) assign the rApp with an ID. 2) rApp: a) retrieves the bootstrap information that ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.4.1 rApp registration and bootstrap | Table 6.1.4.1-1: rApp registration and bootstrap use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal 1) Find the SME service endpoints (Optional). 2) Register the rApp to the SME services Producer in SMO/Non-RT RIC framework. Actors and Roles - rApp in the role of Service Producer and/or Service... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.1.5 Required data | For registering, an rApp needs to provide the security credentials along with e.g. rApp name, vendor, software version, certificates etc. and the role an rApp is trying to register (Service Producer and/or Service Consumer). The response to the rApp registration includes the status of registration i.e. success or failu... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2 SME Use case 2: Manage Service Registration | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.1 Overview | This use case allows an rApp as Service Producer to register each of its produced services, update the service information of each of its registered services and deregister each of its registered service as specified in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.2 Background and goal of the use case | An rApp as a Service Producer can register each of the new services its produces. Other rApps that are Service Consumers can discover the registered services. After an rApp as a Service Producer has successfully registered the each of the services it produces, it can update and/or deregister each of the registered serv... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality to register a service produced by an rApp; b) support authorization of an rApp to determine whether an rApp can register a service, update a registered service, and deregister a registered service; c) support validation of the new service p... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4.1 Register Service | Table 6.2.4.1-1: Register service use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp successfully registers a service. Actors and Roles - rApp in the role of Service Producer that requests service registration. - SME functions in the role of SME services Producer that handles the servi... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4.2 Update service registration | Table 6.2.4.2-1: Update service registration use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp successfully updates a service registration. Actors and Roles - rApp in the role of Service Producer that requests updating the registered information of a service. - SME functions in the ro... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.4.3 Deregister Service | Table 6.2.4.3-1: Deregister service use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp successfully deregister a service. Actors and Roles - rApp in the role of Service Producer that requests service deregistration. - SME functions in the role of SME services Producer that handles the ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.2.5 Required data | The service profile information includes e.g. the name of the service, service type, communication mechanism, interface endpoint details (such as IP address, port number, URI, protocol), version number, and data format. For registering a service, the rApp needs to provide the rAppId and the service profile. On successf... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3 SME use case 3: Discovery of services | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.1 Overview | This use case allows an rApp as a Service Consumer to discover the available services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.2 Background and goal of the use case | The discovery of services is specified as part of Service management and exposure services in R1GAP [1]. An rApp in the role of Service Consumer will be able to discover the available services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality to discover the available services; b) support authorization of an rApp to determine which services an rApp can discover; ETSI ETSI TS 104 230 V10.0.0 (2026-02) 23 c) retrieve the stored service information and performs filtering of availab... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.4.1 Discover the services | Table 6.3.4.1-1: Discover service use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp discovers the available services. Actors and Roles - rApp in the role of Service Consumer that requests to discover the available services. - SME functions in the role of SME services Producer that han... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.3.5 Required data | For discovering a service, the rApp needs to provide the rAppId and optional selection criteria such as e.g. name of the service, service type, and capabilities. The SME functions respond with information about a set of services which includes e.g. endpoint information and service identifiers. NOTE: Whether an rApp may... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4 SME use case 4: Subscribe service availability | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.1 Overview | This use case allows an rApp as Service Consumer to subscribe to notifications and unsubscribe from notifications regarding changes in service availability, to receive notifications about subscribed events and to update its subscriptions. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.2 Background and goal of the use case | The subscribe service availability, notify service availability changes, unsubscribe service availability and update service availability subscriptions procedures are defined as part of Service management and exposure services in R1GAP [1]. The rApp in the role of Service Consumer can subscribe to notifications and uns... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.3 Entities/resources involved in the use case | 1) SME functions in the role of SME services Producer: a) support functionality to subscribe to and unsubscribe from service availability notifications by an rApp as well as to update its subscriptions; b) support notifying the rApp regarding the changes in the availability of services; c) provide response of success o... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.1 Subscribe to service availability notifications | Table 6.4.4.1-1: Subscribe to service availability notifications Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp subscribes to notifications about changes of the availability of services. Actors and Roles - rApp in the role of Service Consumer that requests subscription to service availabili... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.2 Notify service availability changes | Table 6.4.4.2-1: Notify service availability changes use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp receives notifications about changes in the available services. Actors and Roles - rApp in the role of Service Consumer that receives notifications on service availability changes. -... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.3 Unsubscribe from service availability notifications | Table 6.4.4.3-1: Unsubscribe from service availability notifications Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp unsubscribes from service availability notifications. Actors and Roles - rApp in the role of Service Consumer that requests unsubscribe from service availability notifications... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.4.4 Update subscriptions to service availability notifications | Table 6.4.4.4-1: Update subscriptions to service availability notifications Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp updates its subscriptions to notifications about changes of the availability of services. Actors and Roles - rApp in the role of Service Consumer that requests updating... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.4.5 Required data | To receive notifications regarding changes in service availability, the rApp as Service Consumer subscribes to notifications by providing rAppId and optional service identifier/s. When the SME functions have successfully processed the request, they respond by providing a subscription identifier. The SME functions send ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5 SME use case 5: Query registered services | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.1 Overview | This use case allows an rApp as Service Producer to retrieve the service information of registered services as specified in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.2 Background and goal of the use case | An rApp as a Service registration service Consumer can retrieve the service information of its registered services from the Service registration services Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.3 Entities/resources involved in the use case | 1) SME functions in the role of Service registration service Producer: a) support functionality to query the information of registered services; b) support authorization of an rApp to determine whether an rApp can query the information of registered services; c) retrieve the stored service information and performs filt... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.4.1 Query registered services | Table 6.5.4.1-1: Query registered services use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp is aware of the service information of its registered services. Actors and Roles - rApp in the role of Service registration service Consumer that queries registered services. - SME functions i... |
e341f05abb94e155b675f29c6779693c | 104 230 | 6.5.5 Required data | For querying registered services, the rApp needs to provide the rAppId and optional selection criteria e.g. service name, service type and capabilities. The SME functions respond with service API descriptions that match the selection criteria. 7 Use cases for Data Management and Exposure Services 7.1 DME use case 1: Da... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.1 Overview | This use case defines how an rApp as DME registration and discovery services consumer registers as producer of data for a DME type, queries a DME type registration, updates a DME type registration and deregisters as producer of data for a DME type. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.2 Background and goal of the use case | The Register DME type Query DME type registration, Update DME type registration and Deregister DME type procedures are defined as part of Data management and exposure services in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.3 Entities/resources involved in the use case | 1) Data management and exposure functions: a) support functionality to allow an rApp to register, query, update and deregister as producer of data for a DME type; b) support functionality to allow an rApp to register the constraints for how it can produce and deliver data for the registered DME type; c) support validat... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.1 Register DME type | Table 7.1.4.1-1: DME type registration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp registers as producer of data for a DME type. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registrat... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.2 Deregister DME type | Table 7.1.4.2-1: DME type deregistration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp deregisters as producer of data for a DME type. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data regis... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.3 Update DME type registration | Table 7.1.4.3-1: Update DME type registration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp as producer of data updates a DME type registration it has previously created. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.4.4 Query DME type registration | Table 7.1.4.4-1: Query DME type registration Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp as producer of data query a DME type registration it has previously created. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure fu... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.1.5 Required data | The DME type information includes the data type identifier, metadata describing the DME type, the schemas for the data content, and constraints for how data can be produced, delivered, and accessed. For registering a DME type, the rApp provides the rAppId and DME type information. On successful registration, Data manag... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2 DME use case 2: Discovery of DME types | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.1 Overview | This use case enables an rApp to retrieve information about registered and available DME types and query a DME type identifier and its associated information. It also enables an rApp to subscribe to and unsubscribe from notifications regarding changes in the availability of DME types. ETSI ETSI TS 104 230 V10.0.0 (2026... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.2 Background and goal of the use case | The discover DME type and query DME type information, subscribe DME types changes, unsubscribe DME types changes and notify DME types changes procedure are defined as part of the Data management and exposure services in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.3 Entities/resources involved in the use case | 1) Data management and exposure functions in the role of Data registration and discovery service Producer: a) support functionality allowing rApps to discover the DME types that are available; b) support functionality allowing rApps to retrieve the information about a specific data type identified by a DME type identif... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.1 Discover DME type | Table 7.2.4.1-1: Discover DME types Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves the information on available DME types. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registra... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.2 Query DME type information | Table 7.2.4.2-1: Query DME type information Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves detailed information on a specific DME type. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.3 Subscribe DME types changes | Table 7.2.4.3-1: Subscribe DME types changes Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp subscribes to notifications regarding changes in the availability of DME types. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.4 Notify DME types changes | Table 7.2.4.4-1: Notify DME types changes Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp receives a notification regarding a change in the availability of DME types. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure funct... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.4.5 Unsubscribe DME types changes | Table 7.2.4.5-1: Unsubscribe DME types changes Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp unsubscribes from notifications. Actors and Roles - rApp in the role of Data registration and discovery service Consumer. - Data management and exposure functions in the role of Data registration a... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.2.5 Required data | For the Discover DME types request, the rApp provides the rAppId and optional query information. The Data management and exposure functions respond with information about all available DME types which includes for each DME type, the data type identifier, and related metadata information. If filtering criteria were prov... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3 DME use case 3: Data offer | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.1 Overview | This use case allows a Data Producer rApp as Service Consumer to create and terminate a data offer to trigger the collection of a data instance it wishes to deliver to the Data management and exposure functions as Data management and exposure services Producer for collection. Further, it allows the Data management and ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.2 Background and goal of the use case | A Data Producer rApp as Service Consumer can create a data offer which indicates to the Data management and exposure functions that the rApp intends to deliver a data instance to the Data management and exposure services Producer for collection. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 46 Further, the Data Producer rApp ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.3 Entities/resources involved in the use case | 1) Data management and exposure functions as Data management and exposure services Producer: a) support functionality to create a data offer as requested by a Data Producer rApp; b) support authorization of a Data Producer rApp to determine whether it can create a data offer; c) support to send data offer termination n... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.4.1 Create data offer | Table 7.3.4.1-1: Create data offer use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp creates a data offer to specify a data instance it produces for collection. Actors and Roles - rApp in the role of Data Producer that requests data offer creation. - Data management and exposure ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.4.2 Deliver offered data | Table 7.3.4.2-1: Deliver offered data use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp delivers a data instance it produces for collection, based on a data offer created earlier. Actors and Roles - rApp in the role of Data Producer that produces an offered data instance. - DME f... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.4.3 Terminate data offer by Data Producer | Table 7.3.4.3-1: Terminate data offer by Data Producer use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The Data Producer rApp terminates a data offer to indicate it stops producing a data instance for collection. Actors and Roles - rApp in the role of Data Producer that requests data of... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.4.4 Terminate data offer by DME services Producer | Table 7.3.4.4-1: Terminate data offer by DME services Producer use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The Data management and exposure functions send a data offer termination notification to indicate they do not intend to collect the data instance from the Data Producer any lon... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.3.5 Required data | The Create data offer request contains the rAppId, the registered data type identifier for the data to be produced and additional information related to the data instance to be produced such as scope, target, context, timing etc. Also, the request contains the supported delivery method(s) for the data and information o... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.4.1 Overview | This use case describes how a Data Consumer rApp requests to obtain one-off data for consumption from the DME functions. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.4.2 Background and goal of the use case | The Data request and subscription service and Data delivery service procedures are defined as part of the Data management and exposure services in R1GAP [1]. After performing the Data discovery procedure, an rApp will be able to request data from the Data management and exposure functions, and the Data management and e... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.4.3 Entities/resources involved in the use case | 1) Data management and exposure functions: a) support functionality to receive a data request from an rApp; b) support functionality to authorize the rApps request for data; c) support functionality to provide data to an rApp. 2) rApp: a) support functionality to request data; b) support functionality to retrieve the d... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.4.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.4.4.1 Data Consumer rApp request data | Table 7.4.4.1-1: Use case: A Data Consumer rApp requests data for consumption from the DME functions Use Case Stage Evolution / Specification <<Uses>> Related use Goal An rApp obtains the data they intend to consume from the Data Management and Exposure functions via the request data procedure. Actors and Roles - Data ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.4.5 Required data | For Request data request, the rApp provides to the Data management and exposure functions its rApp identifier (rAppId) and data instance information. Data instance information includes data type identifier, scope i.e. filter on the data, and optional constraints, e.g. time interval (i.e. start time and end time), etc. ... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.5.1 Overview | This use case describes how the Data management and exposure functions request to obtain one-off data for consumption from a Data Producer rApp. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.5.2 Background and goal of the use case | The Data request and subscription service and Data delivery service procedures are defined as part of Data management and exposure services in R1GAP [1]. The Data management and exposure functions request data from a Data Producer rApp, and the Data Producer rApp delivers the requested data. ETSI ETSI TS 104 230 V10.0.... |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.5.3 Entities/resources involved in the use case | 1) Data management and exposure functions: a) support functionality to request data; b) support functionality to retrieve the data. 2) rApp: a) supports functionality to provide data to the DME. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.