hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 functions in the role of Data management and exposure services Producer that handles the data offer creation. Assumptions n/a Preconditions The rApp is deployed and is authorized to access the Data management and exposure functions. Begins when The rApp determines the need to create a data offer. Step 1 (M) The rApp requests the Data management and exposure functions to create a data offer by providing the rAppId, registered data type identifier, further information about the data instance, and intended delivery method(s). Step 2 (M) The Data management and exposure functions check whether the rApp is authorized to create a data offer. Step 3 (M) The Data management and exposure functions validate the information provided with the request. Step 4 (M) The Data management and exposure functions create the data offer and prepare an endpoint for the delivery of notifications or push data. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 47 Use Case Stage Evolution / Specification <<Uses>> Related use case Step 5 (M) The Data management and exposure functions respond to the rApp with a success result along with the data offer identifier and endpoint for the delivery of notifications or push data. Ends when The rApp was able to create a data offer. Exceptions n/a Post Conditions The Data management and exposure functions are ready to collect the data instance related to the data offer and the rApp is ready to produce it. Further, the rApp and the Data management and exposure services Producer will be able to terminate the data offer. Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as dme endbox endbox rapp -> dme: <<R1>> Create data offer request \n(rAppId, dataTypeId, dataInstanceInfo, deliveryMethods, notifyEndpointInfo) activate dme dme --> dme: AuthZ note right Check authorization in collaboration with SME functions end note dme --> dme: Validate request dme --> dme: Create data offer\nand prepare\ndelivery endpoint dme -> rapp: <<R1>> Create data offer response (dataOfferId, deliveryEndpointInfo) deactivate dme @enduml Figure 7.3.4.1-1: Create data offer use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 48 |
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 functions in the role of Data management and exposure services Producer that collect the offered data instance. Assumptions n/a Preconditions A data offer has been created. Begins when The rApp starts delivering the produced data related to the data offer. Alternative procedure Each time a set of data becomes available for delivery, Steps 1-3 are executed if pull is used as the data delivery method. Step 1 (M) The Data Producer rApp sends to the Data management and exposure functions a Notify data availability message, including details how to pull the requested data and the data offer identifier. Step 2 (M) The Data management and exposure functions send a pull data request message, using the pull delivery details obtained in step 1. Step 3 (M) The Data Producer rApp responds with a pull data response, including the data to be collected. Alternative procedure Each time a set of data becomes available for delivery, Step 4 is executed if push is used as the data delivery method. Step 4 (M) The Data Producer rApp sends to the Data management and exposure functions a push data message, including the data to be collected and the subscription identifier. Step 5 (M) The Data management and exposure functions store the delivered data. Ends when The rApp has delivered to the Data management and exposure functions for collection the produced data related to the data offer. Exceptions n/a Post Conditions n/a Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant "rApp" as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\nexposure functions" as dme end box loop when data becomes available alt pull data delivery method rApp -> dme : <<R1>> Notify data availability (pull delivery details, data offer ID) dme -> rApp : <<R1>> Pull data request (pull delivery details) rApp -> dme : <<R1>> Pull data response (with data payload) else push data delivery method rApp -> dme : <<R1>> Push data message (data payload, data offer ID) end dme --> dme: Store data end @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 49 Figure 7.3.4.2-1: Deliver offered data use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 50 |
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 offer termination. - Data management and exposure functions in the role of Data management and exposure services Producer that handles the data offer termination. Assumptions n/a Preconditions - The rApp is authorized to access the Data management and exposure functions. - The rApp has created a data offer. Begins when The rApp determines the need to terminate a data offer it has created previously. Step 1 (M) The rApp requests the Data management and exposure functions to terminate a data offer by providing the rAppId and the data offer identifier. Step 2 (M) The Data management and exposure functions check whether the rApp is authorized to terminate the data offer. Step 3 (M) The Data management and exposure functions validate the information provided with the request. Step 4 (M) The Data management and exposure functions stop collecting the data instance and terminate the data offer. Step 5 (M) The Data management and exposure functions respond to the rApp with a success result along with the data offer identifier. Ends when The rApp was able to terminate the data offer. Exceptions n/a Post Conditions The data instance associated with the data offer is no longer collected. Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC"" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as dme endbox endbox rapp -> dme: <<R1>> Terminate data offer request (rAppId, dataOfferId) activate dme dme -->dme: AuthZ note right Check authorization in collaboration with SME functions end note dme --> dme: Validate request dme --> dme: Stop collecting data\nand terminate data offer dme -> rapp: <<R1>> Terminate data offer response (dataOfferId) deactivate dme @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 51 Figure 7.3.4.3-1: Terminate data offer by Data Producer use case flow diagram |
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 longer. Actors and Roles - rApp in the role of Data Producer that receives a data offer termination notification. - Data management and exposure functions in the role of Data management and exposure services Producer that sends the data offer termination notification. Assumptions n/a Preconditions The rApp has created a data offer. Begins when The Data management and exposure functions determine a need to terminate a data offer. Step 1 (M) The Data management and exposure functions send to the rApp a data offer termination notification providing the data offer ID. Step 2 (M) After a delay to allow the Data Producer to react to the notification, the Data management and exposure functions stop collecting data for the affected data offer and terminate the offer. Step 3 (M) The rApp stops delivering to the Data management and exposure functions data related to the affected data offer. Ends when The Data management and exposure functions were able to terminate the data offer. Exceptions n/a Post Conditions The data instance associated with the data offer is no longer collected. Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber ETSI ETSI TS 104 230 V10.0.0 (2026-02) 52 box "Non-RT RIC" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as dme endbox endbox dme -> rapp: <<R1>> Terminate data offer notification (dataOfferId) dme --> dme: Stop collecting data and\nterminate data offer rapp --> rapp: Stop delivering data @enduml Figure 7.3.4.4-1: Terminate data offer by DME services Producer use case flow diagram |
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 on the endpoint where to send data offer termination notifications. The Create data offer response contains the data offer identifier. In case of the pull delivery method, the response further contains information about the endpoint where to send data availability notifications. In case of the push delivery method, the response further contains information about the endpoint where to push the data. The Notify data availability message contains pull delivery details (e.g. a URI) and the data offer identifier. In the Pull data request, the Data management and exposure functions use the pull delivery details provided in the notify data availability message to locate the data. The Pull data response contains a set of data for collection. The Push data message contains a set of data for collection and the data offer identifier. The Terminate data offer request contains the rAppId and the data offer ID. The Terminate data offer response contains the data offer ID. The Data offer termination notification contains the data offer ID. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 53 7.4 DME use case 4: Data request-Data Consumer rApp requests data for consumption from the DME functions |
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 exposure functions deliver the requested data. |
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 data. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 54 |
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 Consumer rApp in the role of Data management and exposure services Consumer. - Data management and exposure functions in the role of Data management and exposure services Producer that provides data. Assumptions n/a Preconditions - rApp is deployed, authenticated, and authorized for usage of the Data management and exposure services. - Data management and exposure functions produce the Data management and exposure services. Begins when An rApp, as a Data Consumer, initiates the request data procedure. Step 1 (M) The Data Consumer rApp sends to the Data management and exposure functions a request data request to obtain data for consumption, providing its rAppId and data instance information. Step 2 (M) The Data management and exposure functions check the Data Consumer rApps authorization. Step 3 (M) The Data management and exposure functions validate the Data Consumer's data request. Step 4 (M) The Data management and exposure functions send to the Data Consumer rApp the data request response and include pull delivery details for the requested data instance. Step 5 (M) The Data Consumer rApp sends to the Data management and exposure functions a pull data request message, using the pull delivery details received in step 4. Step 6 (M) The Data management and exposure functions respond with a pull data response, including in the payload the data to be consumed. Ends when The requested data have been delivered to the Data Consumer rApp for consumption. Exceptions n/a Post Conditions The Data Consumer rApp has consumed the requested data. Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rApp" as rApp end box box "Non-RT RIC"" #whitesmoke box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and \n exposure functions" as dme end box dme <- rApp : <<R1>> Request data request (rAppId, Data instance information) dme --> dme :AuthZ note right Check authorization in collaboration with SME functions end note dme --> dme: Validate rApp <- dme : <<R1>> Request data response (pull delivery details) dme <- rApp : <<R1>> Pull data request(pull delivery details) rApp <- dme : <<R1>> Pull data response (with data payload) @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 55 Figure 7.4.4.1-1: A Data Consumer rApp requests data for consumption from the DME functions use case flow diagram |
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. For Request data response, the Data management and exposure functions provide pull delivery details. The pull delivery details are used to locate the requested data instance, e.g. using a URI. NOTE: A request identifier, assigned by the Service Producer, can be a part of pull delivery details if necessary, during the protocol design stage. For Pull data request, the rApp provides pull delivery details. For Pull data response, the Data management and exposure functions provide the requested data. 7.5 DME use case 5: Data request - DME functions request data for collection from a Data Producer rApp |
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.0 (2026-02) 56 |
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. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.5.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.5.4.1 DME functions request data for collection from a Data Producer rApp | Table 7.5.4.1-1: Use case: DME functions request data for collection from a Data Producer rApp Use Case Stage Evolution / Specification <<Uses>> Related use Goal The DME functions obtain the data they intend to collect from the Data Producer rApp via request data procedure. Actors and Roles - rApp in the role of Data Producer. - Data management and exposure functions in the role of Data management and exposure services Consumer. Assumptions n/a Preconditions - rApp is deployed and authenticated. - Data management and exposure functions have the data type identifier of the needed data. Begins when The Data management and exposure functions initiate the request data procedure to collect data from the Data Producer rApp. Step 1 (M) The Data management and exposure functions send the Data Producer rApp a request data request to obtain data for collection, providing data instance information. Step 2 (M) The Data Producer rApp validates the Data management and exposure functions data request. Step 3 (M) The Data Producer rApp replies with a request data response message, including details how to pull the requested data. Step 4 (M) The Data management and exposure functions send to the Data Producer rApp a pull data request message, using the pull delivery details received in step 3. Step 5 (M) The Data Producer rApp responds with a pull data response, including in the payload the data to be collected. Ends when The requested data have been delivered to the Data management and exposure functions for collection. Exceptions n/a Post Conditions The Data management and exposure functions have collected the requested data. Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rApp" as rApp end box box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as dme end box ETSI ETSI TS 104 230 V10.0.0 (2026-02) 57 dme -> rApp : <<R1>> Request data request (Data instance information) rApp --> rApp: validate rApp -> dme : <<R1>> Request data response (pull delivery details) dme -> rApp : <<R1>> Pull data request (pull delivery details) rApp -> dme : <<R1>> Pull data response (with data payload) @enduml Figure 7.5.4.1-1: DME functions request data for collection from a Data Producer rApp use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.5.5 Required data | For the Request data request, the Data management and exposure functions provide 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. For Request data response, the Data Producer rApp provides pull delivery details. The pull delivery details are used to locate the requested data instance, e.g. using a URI. NOTE: A request identifier, assigned by the service producer, can be a part of pull delivery details if necessary, during the protocol design stage. For Pull data request, the Data management and exposure functions use the pull delivery details provided in the Request data response to locate the data. For Pull data response, the rApp provides the requested data. 7.6 DME use case 6: The DME functions subscribe data for collection from a Data Producer rApp |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.1 Overview | This use case describes how the DME functions subscribe data for collection from a Data Producer rApp, update the data subscription, query the data subscription, obtain the data, query the status of the data subscription, and terminate the data subscription. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 58 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.2 Background and goal of the use case | The Data 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 subscribe data from a Data Producer rApp for collection, update the data subscription, query the data subscription, and its status, and terminate the data subscription. The Data Producer rApp delivers the requested data. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.3 Entities/resources involved in the use case | 1) Data management and exposure functions: a) support functionality to request subscription to data, update the data subscription, query the data subscription, query the subscription status, and termination of the subscription; b) support functionality to obtain the data for collection. 2) Data Producer rApp: a) supports functionality to subscribe to data; b) supports functionality to update a data subscription; c) supports functionality to query a data subscription; d) supports functionality to terminate a data subscription; e) supports functionality to provide data to the DME functions; f) supports functionality to provide the status of data subscriptions. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 59 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.4.1 DME functions subscribe data for collection from a Data producer rApp | Table 7.6.4.1-1: Use case: The DME functions subscribe data for collection from a Data Producer rApp Use Case Stage Evolution / Specification <<Uses>> Related use Goal The Data management and exposure functions obtain data they intend to collect from a Data Producer rApp via the subscribe data procedure. Actors and Roles - rApp in the role of Data Producer. - Data management and exposure functions: entity in the role of Data subscription service Consumer and Pull data service Consumer and/or Push data service Producer and/or owner of the point to multipoint data stream configuration. Assumptions If point to multipoint data stream is used as delivery method, data stream endpoint is configured as part of preconditions, or the configuration may also take place as part of the subscription. Preconditions - rApp is deployed and authenticated. - Data management and exposure functions have the data type identifier of the needed data. - For point to multipoint data stream delivery method, the data stream endpoint has been configured. Begins when The Data management and exposure functions initiate the Subscribe data procedure to collect a data instance. Step 1 (M) The Data management and exposure functions send to the Data Producer rApp a subscribe data request to subscribe the data to be collected providing Data instance information. Alternative procedure If point to multipoint data stream is used as delivery method, the Data management and exposure functions provide a data stream endpoint. Step 2 (M) The Data management and exposure functions send to the Data Producer rApp a subscribe data request to subscribe the data to be collected providing Data instance information and data stream endpoint. Step 3 (M) The Data Producer rApp validates the request. Step 4 (M) The Data Producer rApp creates the subscription. Step 5 (M) The Data Producer rApp replies with a subscribe data response message, including the subscription identifier. Alternative procedure Each time a set of data becomes available for delivery, steps 5-7 are executed if pull data is used as the data delivery method. Step 6 (M) The Data Producer rApp sends to the Data management and exposure functions a Notify data availability message, including details how to pull the requested data and the subscription identifier. Step 7 (M) The Data management and exposure functions send a pull data request message, using the pull delivery details obtained in step 5. Step 8 (M) The Data Producer rApp responds with a pull data response, including the data to be collected. Alternative procedure Each time a set of data becomes available for delivery, step 8 is executed if push data is used as the data delivery method. Step 9 (M) The Data Producer rApp sends to the Data management and exposure functions a push data message, including the subscription identifier and the data to be collected. Alternative procedure Each time a set of data becomes available for delivery, step 10 is executed if point to multipoint data stream is used as the delivery method. Step 10 (M) The Data Producer rApp send the data-to-data stream endpoint. Ends when The subscribed data instance has been delivered for collection to the Data management and exposure functions. Exceptions n/a Post Conditions The Data management and exposure functions have collected the needed data. Traceability REQ-R1-DME-Data subscription-FUN1, REQ-R1-DME-Data delivery-FUN1. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 60 @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rApp" as rApp end box box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as dme end box alt Pull or push data delivery method dme -> rApp : <<R1>> subscribe data request (data instance information) else Point to multipoint data stream delivery method dme -> rApp : <<R1>> subscribe data request (data instance information,\n data stream endpoint) end activate dme rApp --> rApp : Validate request rApp --> rApp : Create subscription rApp -> dme : <<R1>> subscribe data response (subscription ID) deactivate dme loop when data becomes available alt Pull data delivery method rApp -> dme : <<R1>> Notify data availability (pull delivery details, subscription ID) dme -> rApp : <<R1>> Pull data request rApp -> dme : <<R1>> Pull data response (with data payload) else Push data delivery method rApp -> dme : <<R1>> Push data message (subscription ID, data payload) else Point to multipoint data stream delivery method rApp -> dme: <<R1>> rApp sends data payload to data stream endpoint end end @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 61 Figure 7.6.4.1-1: DME functions subscribe data for collection from a Data Producer rApp use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 62 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.4.2 DME functions terminate the data subscription | Table 7.6.4.2-1: Use case: The DME functions terminate the data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal Data management and exposure functions terminate the data subscription. Actors and Roles - rApp in the role of Data Producer. - Data management and exposure functions in the role of Data subscription service Consumer. Assumptions n/a Preconditions The DME functions have subscribed data. Begins when The DME functions determine to terminate the data subscription. Step 1 (M) The DME functions send the Unsubscribe data request with subscription ID as parameter. Step 2 (M) The rApp validates the request. Step 3 (M) The rApp removes the data subscription. Step 4 (M) The rApp responds to the request. Ends when The DME functions have terminated the data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN2. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME end box rApp <- DME: <<R1>> Unsubscribe data request\n (subscription ID) activate rApp rApp --> rApp : validate request rApp --> rApp : remove subscription rApp -> DME: <<R1>> Unsubscribe data response deactivate rApp @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 63 Figure 7.6.4.2-1: The DME functions terminate the data subscription |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.4.3 DME functions update a data subscription | Table 7.6.4.3-1: Use case: The DME functions update a data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal Data management and exposure functions update a data subscription. Actors and Roles - rApp in the role of Data Producer. - Data management and exposure functions in the role of Data subscription service Consumer. Assumptions n/a Preconditions The DME functions have subscribed to data instance. Begins when The DME functions determine to update a data subscription. Step 1 (M) The DME functions send the Update data subscription request with subscription ID and data subscription update information as parameter. Step 2 (M) The rApp validates the request. Step 3 (M) The rApp updates data subscription. Step 4 (M) The rApp responds to the request. Ends when The DME functions have updated the data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN3. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME end box rApp <- DME: <<R1>> Update data subscription request\n (subscription ID,\n data subscription update information) activate rApp rApp --> rApp : validate request ETSI ETSI TS 104 230 V10.0.0 (2026-02) 64 rApp --> rApp : update data subscription rApp -> DME: <<R1>> Update data subscription response deactivate rApp @enduml Figure 7.6.4.3-1: The DME functions update the data subscription |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.4.4 DME functions query a data subscription | Table 7.6.4.4-1: Use case: The DME functions query a data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal Data management and exposure functions query a data subscription. Actors and Roles - rApp in the role of Data Producer. - Data management and exposure functions in the role of Data subscription service Consumer. Assumptions n/a Preconditions The DME functions have subscribed to data instance. Begins when The DME functions determine to query a data subscription. Step 1 (M) The DME functions send the Query data subscription request with subscription ID as parameter. Step 2 (M) The rApp validates the request. Step 3 (M) The rApp responds to the request with data subscription information. Ends when The DME functions have queried the data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN4. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME ETSI ETSI TS 104 230 V10.0.0 (2026-02) 65 end box rApp <- DME: <<R1>> Query data subscription request\n (subscription ID) activate rApp rApp --> rApp : validate request rApp -> DME: <<R1>> Query data subscription response\n (data subscription information) deactivate rApp @enduml Figure 7.6.4.4-1: The DME functions query the data subscription |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.4.5 DME functions query status of data subscription | Table 7.6.4.5-1: Use case: The DME functions query status of data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal Data management and exposure functions query status of a created data subscription. Actors and Roles - rApp in the role of Data Producer. - Data management and exposure functions in the role of Data subscription service Consumer. Assumptions n/a Preconditions The DME functions have subscribed to data instance. Begins when The DME functions determine the need to query the status a data subscription. Step 1 (M) The DME functions send the Query data subscription status request with subscription ID as parameter. Step 2 (M) The rApp validates the request. Step 3 (M) The rApp responds to the request with the status of the data subscription. Ends when The DME functions have queried the status of data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN1. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue ETSI ETSI TS 104 230 V10.0.0 (2026-02) 66 participant "Data management and\n exposure functions" as DME end box rApp <- DME: <<R1>> Query data subscription status request\n (subscription ID) activate rApp rApp --> rApp : validate request rApp -> DME: <<R1>> Query data subscription status response\n (data subscription information) deactivate rApp @enduml Figure 7.6.4.5-1: The DME functions query the status of data subscription |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.6.5 Required data | In the subscribe data request, the Data management and exposure functions provide data instance information. Data instance information includes the data type identifier, scope (i.e. filter on the data), periodicity of collection and additional optional constraints periodicity of reporting, etc. If point to multipoint data stream is used as delivery method, the Data management and exposure functions provide the data stream endpoint to Data Producer to send data. In the subscribe data response, the Data Producer rApp provides the subscription identifier. The subscription identifier is a unique identifier assigned by service Producer to identify a specific subscription. In the update data subscription request, the Data management and exposure functions provide the subscription identifier and data subscription update information. In the query data subscription request, the Data management and exposure functions provide the subscription identifier. In the query data subscription response, the Data Producer rApp provides the data subscription information. In the unsubscribe data request, the Data management and exposure functions provide the subscription identifier. In the notify data availability message, the Data Producer rApp provides pull delivery details (e.g. a URI) and the subscription identifier. In the pull data request, the Data management and exposure functions use the pull delivery details provided in the notify data availability message to locate the data. In the pull data response, the Data Producer rApp provides a set of data for collection. In the query data subscription status request, the Data management and exposure functions provide the subscription identifier. In the query data subscription status response, the Data Producer rApp provides the data subscription status information. In the push data message, the Data Producer rApp provides the subscription identifier and a set of data for collection. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 67 When point to multipoint data stream is used, Data Producer rApp sends the data to the data stream endpoint. 7.7 DME use case 7: A Data Consumer rApp subscribes data for consumption using the Data request and subscription service |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.1 Overview | This use case describes how a Data Consumer rApp subscribes data it needs to consume, update the data subscription, query the data subscription obtains the data, and terminates the data subscription. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.2 Background and goal of the use case | The Data subscription service and Data delivery service procedures are defined as part of Data management and exposure services in R1GAP [1]. A Data Consumer rApp will be able to subscribe data based on the DME type information it is aware of e.g. from discovery or configuration, update the data subscription, query the data subscription, and terminate the data subscription using Data management and exposure procedures. Data management and exposure functions deliver the subscribed data using Data delivery services. |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.3 Entities/resources involved in the use case | 1) Data management and exposure functions: a) support services that allow an rApp to subscribe data, update the data subscription, query the data subscription and terminate the data subscription; b) deliver the subscribed data to an rApp that has subscribed. 2) rApp: a) supports functionality to initiate a data subscription; b) supports functionality to initiate an update of a data subscription; c) supports functionality to initiate a query of a data subscription; d) supports functionality to initiate the termination of a data subscription; e) supports functionality to obtain the subscribed data. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 68 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.4.1 Subscribe data and delivery of subscribed data | Table 7.7.4.1-1: Subscribing data and delivery of subscribed data Use Case Stage Evolution / Specification <<Uses>> Related use Goal rApp subscribes the data it needs to consume, and the subscribed data is delivered. Actors and Roles - rApp in the role of Data management and exposure services Consumer. - Data management and exposure functions in the role of Data management and exposure services Producer. Assumptions If point to multipoint data stream is used as delivery method, data stream endpoint configured as part of preconditions, or the configuration may also take place as part of the subscription. Preconditions 1) The rApp is authorized to access the Data management and exposure services. 2) The rApp has obtained the DME type information e.g. by discovery or configuration. 3) For point to multipoint data stream delivery method, data stream endpoint has been configured by Data management and exposure functions. Begins when The rApp determines the need to subscribe data it needs to consume. Step 1 (M) The rApp subscribes data that it needs to consume with rAppId and Data instance information as parameters. Step 2 (M) The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to subscribe data. Step 3 (M) The Data management and exposure functions validate the request. Step 4 (M) The Data management and exposure functions create the subscription. Step 5 (M) The Data management and exposure functions respond to the request with subscription ID as a parameter. Alternative procedure If point to multipoint data stream is used as a delivery method, the Data management and exposure functions provide the data stream endpoint. Step 6 (M) The Data management and exposure functions respond to the request with subscription ID as a parameter and data stream endpoint. Alternative procedure Each time a set of subscribed data becomes available for delivery, steps 7-9 are executed if "pull data" is used as the data delivery method. Step 7 (M) The Data management and exposure functions notify the availability of data with subscription ID and pull delivery details as parameters. Step 8 (M) The rApp send a pull data request based on the pull delivery details received in the previous step. Step 9 (M) The Data management and exposure functions respond to the pull data request with data payload as a parameter. Alternative procedure Each time a set of subscribed data becomes available for delivery, step 10 is executed if the "push data" is used as the data delivery method. Step 10 (M) The Data management and exposure functions send a push data message with subscription ID and data payload as parameters. Alternative procedure Each time a set of data becomes available for delivery, step 11 is executed if point to multipoint data stream is used as the data delivery method. Step 11 (M) rApp fetches the data from the data stream endpoint. Ends when The rApp has terminated the subscription. Exceptions n/a Post Conditions The rApp has the data it determined it needed. Traceability REQ-R1-DME-Data subscription-FUN1, REQ-R1-DME-Data delivery-FUN1. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box ETSI ETSI TS 104 230 V10.0.0 (2026-02) 69 box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME end box rApp -> DME : <<R1>> Subscribe data request (rAppId, Data instance information) DME --> DME : AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME : Validate request DME --> DME : Create subscription Alt Pull or push delivery method rApp <- DME : <<R1>> Subscribe data response(subscription ID) else Point to multipoint data stream delivery method rApp <- DME : <<R1>> Subscribe data response(subscription ID, data stream endpoint) end loop when data becomes available alt Pull data delivery method rApp <- DME : <<R1>> Notify data availability (pull delivery details, subscription ID ) rApp -> DME : <<R1>> Pull data request rApp <- DME : <<R1>> Pull data response (data payload) else Push data delivery method DME -> rApp : <<R1>> Push data message (subscription ID, data payload) else Point to multipoint data stream delivery method rApp -> DME: <<R1>> rApp fetches data payload from data stream endpoint end end @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 70 Figure 7.7.4.1-1: Subscribe data and delivery of subscribed data use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 71 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.4.2 Terminate data subscription | Table 7.7.4.2-1: Terminate data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal rApp terminates the data subscription. Actors and Roles - rApp in the role of Data management and exposure services Consumer. - Data management and exposure functions in the role of Data management and exposure services Producer. Assumptions n/a Preconditions The rApp has created a data subscription. Begins when The rApp determines to terminate the data subscription. Step 1 (M) The rApp sends the Unsubscribe data request with rAppId and subscription ID as parameters. Step 2 (M) The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to terminate subscriptions. Step 3 (M) The Data management and exposure functions validate the request. Step 4 (M) The Data management and exposure functions remove the subscription. Step 5 (M) The Data management and exposure functions respond to the request. Ends when rApp has terminated the data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN2. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME end box rApp -> DME: <<R1>> Unsubscribe data request\n (rAppId, subscription ID) activate DME DME --> DME : AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME : Validate request DME --> DME : Remove subscription rApp <- DME: <<R1>> Unsubscribe data response deactivate DME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 72 Figure 7.7.4.2-1: Terminate data subscription use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.4.3 Update a data subscription | Table 7.7.4.3-1: Update a data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal rApp update a data subscription. Actors and Roles - rApp in the role of Data management and exposure services Consumer. - Data management and exposure functions in the role of Data management and exposure services Producer. Assumptions n/a Preconditions The rApp has subscribed to data instance. Begins when The rApp determines to update a data subscription. Step 1 (M) The rApp sends the Update data subscription request with rAppId, subscription ID and data subscription update information as parameters. Step 2 (M) The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to update a data subscription. Step 3 (M) The Data management and exposure functions validate the request. Step 4 (M) The Data management and exposure functions updates the data subscription. Step 5 (M) The Data management and exposure functions respond to the request. Ends when rApp has updated the data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN3. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue ETSI ETSI TS 104 230 V10.0.0 (2026-02) 73 participant "Data management and\n exposure functions" as DME end box rApp -> DME: <<R1>> Update data subscription request\n (rAppId, subscription ID\n, data subscription update information) activate DME DME --> DME : AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME : Validate request DME --> DME : Update data subscription rApp <- DME: <<R1>> Update data subscription response deactivate DME @enduml Figure 7.7.4.3-1: Update a data subscription use case flow diagram ETSI ETSI TS 104 230 V10.0.0 (2026-02) 74 |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.4.4 Query a data subscription | Table 7.7.4.4-1: Query a data subscription Use Case Stage Evolution / Specification <<Uses>> Related use Goal rApp query a data subscription. Actors and Roles - rApp in the role of Data management and exposure services Consumer. - Data management and exposure functions in the role of Data management and exposure services Producer. Assumptions n/a Preconditions The rApp has subscribed to data instance. Begins when The rApp determines to query a data subscription. Step 1 (M) The rApp sends the Query data subscription request with rAppId, subscription ID as parameters. Step 2 (M) The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to query a data subscription. Step 3 (M) The Data management and exposure functions validate the request. Step 4 (M) The Data management and exposure functions respond to the request with the data subscription information. Ends when rApp has queried the data subscription. Exceptions n/a Post Conditions n/a Traceability REQ-R1-DME-Data subscription-FUN4. @startuml !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp end box box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "Data management and\n exposure functions" as DME end box rApp -> DME: <<R1>> Query data subscription request(rAppId, subscription ID) activate DME DME --> DME : AuthZ note right Check authorization in collaboration with SME functions end note DME --> DME : Validate request rApp <- DME: <<R1>> Query data subscription response\n (data subscription information) deactivate DME @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 75 Figure 7.7.4.4-1: Query a data subscription use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 7.7.5 Required data | The rApp defines the data it needs to consume in data instance information parameter. Data instance information includes data type identifier, scope (i.e. filter on the data), periodicity of collection and additional optional constraints e.g. periodicity of reporting, etc. A subscription ID is a unique identifier per subscription assigned by the Data management and exposure functions. If point to multipoint data stream is used as delivery method, the Data management and exposure functions provide the data stream endpoint. The rApp requests the Data management and exposure functions with rAppId and subscription identifier as parameters to terminate the data subscription. In the update data subscription request, the rApp provides the rAppId, subscription ID and data subscription update information. In the query data subscription request, the rApp provides the rAppId and subscription identifier. In the query data subscription response, the Data management and exposure functions provide the data subscription information. In the notify data availability message, the Data management and exposure functions provide pull delivery details (e.g. a URI) and the subscription identifier. In the pull data request, the rApp uses the pull delivery details provided in the notify data availability message to locate the data. In the pull data response, the Data management and exposure functions provide a set of data for consumption. In the push data message, the Data management and exposure functions provide the subscription identifier and a set of data for consumption. When point to multipoint data stream is used, rApp fetches the data from data stream endpoint. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8 Use cases for RAN OAM-Related Services | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1 RAN OAM-Related use case 1: Alarm query | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1.1 Overview | This use case allows an rApp acting as Service Consumer to query alarm information. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 76 |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1.2 Background and goal of the use case | An rApp acting as Service Consumer can query from the Fault management service Producer information about an individual alarm, a set of alarms matching provided filtering criteria or all active alarms available in the alarm list. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1.3 Entities/resources involved in the use case | 1) RAN OAM-related functions as Fault management service Producer: a) receive the request to query alarm information; b) provide the response of success or failure result to the Query alarm information request. 2) rApp: a) supports functionality to initiate the procedure to query alarm information. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1.4.1 Query alarm information | Table 8.1.4.1-1: Query alarm information use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp obtains alarm information from the Fault management service Producer. Actors and Roles - rApp in the role of Service Consumer that queries alarm information. - RAN AOM-related functions in the role of Fault management service Producer that provides alarm information in response to the alarm queries. Assumptions n/a Preconditions The rApp is deployed and authorized to query alarm information. Begins when The rApp determines the need to query alarm information. Step 1 (M) The rApp queries alarm information from the RAN OAM-related functions by providing the rAppId and optional query information that determines the requested result set. Step 2 (M) The RAN OAM-related functions check whether the rApp is authorized to query alarm information. Step 3 (M) The RAN OAM-related functions validate the query information if it has been provided with the request. Step 4 (M) The Ran OAM-related functions respond to the rApp with a success result along with the requested alarm information. Ends when The rApp was able to query alarm information. Exceptions n/a Post Conditions n/a Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "RAN OAM-related functions" as fmsp endbox endbox ETSI ETSI TS 104 230 V10.0.0 (2026-02) 77 rapp -> fmsp: <<R1>> Query alarm information request (rAppId, queryInfo) fmsp --> fmsp: AuthZ note right Check authorization in collaboration with SME functions end note fmsp --> fmsp: Validate request fmsp -> rapp: <<R1>> Query alarm information response (alarmInfo) @enduml Figure 8.1.4.1-1: Query alarm information use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.1.5 Required data | The Query alarm information request contains the rAppId and optional query information. The query information determines the requested alarm information, for instance a single alarm with a particular alarm ID, all alarms in the alarm list or a subset of these alarms that match a set of filtering parameters. The Query alarm information response contains the requested alarm information scoped by the query information provided in the request. 8.2 RAN OAM-Related use case 2: Alarm acknowledgement / unacknowledgement |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.2.1 Overview | This use case allows an rApp acting as Service Consumer to acknowledge and unacknowledge an alarm with the Fault management service Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.2.2 Background and goal of the use case | An rApp acting as Service Consumer can acknowledge and unacknowledge an individual alarm managed by the Fault management service Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.2.3 Entities/resources involved in the use case | 1) RAN OAM-related functions in the role of Fault management service Producer: a) receive the request to change the acknowledgement state of an alarm; b) store the alarm acknowledgement state information; c) provide the response of success or failure result to the Change alarm acknowledgement state request. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 78 2) rApp: a) supports functionality to initiate the procedure to change the acknowledgement state of an alarm. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.2.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.2.4.1 Change alarm acknowledgement state | Table 8.2.4.1-1: Change alarm acknowledgement state use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp requests the Service Producer to acknowledge an alarm. Actors and Roles - rApp in the role of Service Consumer that requests to acknowledge an alarm. - RAN OAM-related functions in the role of Fault management service Producer that handles the request to acknowledge an alarm. Assumptions The rApp is aware of the alarm ID of the alarm to be acknowledged or unacknowledged. Preconditions The rApp is deployed and is authorized to consume the Fault management service. Begins when The rApp determines the need to acknowledge an alarm. Step 1 (M) The rApp requests the RAN OAM-related functions to change the acknowledgement state of an alarm by providing the rAppId, the alarm ID and the new acknowledgement state (i.e. acknowledged, or unacknowledged). Step 2 (M) The RAN OAM-related functions check whether the rApp is authorized to change the acknowledgement state of alarms. Step 3 (M) The RAN OAM-related functions validate the alarm ID that has been provided with the request. Step 4 (M) The RAN OAM-related functions persist the new state of the alarm identified by the alarm ID to represent the alarm acknowledgement state change. Step 5 (M) The RAN OAM-related functions respond to the rApp with a success result. Ends when The rApp was able to acknowledge an alarm. Exceptions n/a Post Conditions The state of the alarm identified by the alarm ID has been changed according to the request. Traceability n/a @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "RAN OAM-related functions" as fmsp endbox endbox rapp -> fmsp: <<R1>> Change alarm acknowledgement state request\n(rAppId,alarmId, newAlarmState) fmsp --> fmsp: AuthZ note right Check authorization in collaboration with SME functions end note fmsp --> fmsp: Validate request fmsp --> fmsp: Persist new alarm state fmsp -> rapp: <<R1>> Change alarm acknowledgement state response @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 79 Figure 8.2.4.1-1: Change alarm acknowledgement state use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.2.5 Required data | The Change alarm acknowledgement state request contains the rAppId, the alarm ID of the alarm to be acknowledged or unacknowledged and the requested new acknowledgement state of the alarm. NOTE: If and how the RAN OAM-related functions ensure that the alarm IDs from multiple network elements do not collide is not defined in the present document. 8.3 RAN OAM-Related use case 3: Performance information query |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.3.1 Overview | This use-case allows an rApp acting as a Service Consumer to query the performance information pertaining to the managed entities. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.3.2 Background and goal of the use-case | An rApp acting as a Service Consumer can query the performance information pertaining to one or more managed entities from the Performance management Service Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.3.3 Entities/resources involved in the use-case | 1) RAN OAM-related functions as Performance Management Service Producer: a) receive the request to query the performance information related to one or more managed entities. b) provide the response of success or failure result to the performance information query request. 2) rApp: a) supports functionality to initiate the procedure to query the performance information. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 80 |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.3.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.3.4.1 Query performance information | Table 8.3.4.1-1: Query performance information use-case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp obtains performance information from the Performance management service Producer. Actors and Roles - rApp in the role of Service Consumer that queries performance information pertaining to one or more managed entities. - RAN OAM-related functions in the role of Performance Management service Producer that provide the requested performance information. Assumptions n/a Preconditions The rApp is deployed and authorized to query performance information. Begins when The rApp determines the need to query performance information. Step 1 (M) The rApp queries performance information from the RAN OAM-related functions by providing the rAppId, optional query criteria and information about the managed entities, along with the desired performance information, that determines the requested result set. Step 2 (M) The RAN OAM-related functions check whether the rApp is authorized to query the performance information. Step 3 (M) The RAN OAM-related functions validate the performance information criteria if they were provided with the request. Step 4 (M) The RAN OAM-related functions respond to the rApp with a success result along with the desired performance management information. Ends when The rApp was able to receive the performance information response. Exceptions n/a Post Conditions n/a Traceability REQ-R1-OAm-PMservice-FUN1. @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "RAN OAM-related functions" as fmsp endbox endbox rapp -> fmsp: <<R1>> Query performance information request(rAppId, queryCriteria) fmsp --> fmsp: AuthZ note right Check authorization in collaboration with SME functions end note fmsp --> fmsp: Validate request fmsp -> rapp: <<R1>>Query Performance information response(performanceInformation) @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 81 Figure 8.3.4.1-1: Query performance information use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.3.5 Required data | The request for querying performance information contains the rAppId, and query criteria (including information about the related managed entities and about the requested performance information). The performance information query response is scoped by the information provided in the request. NOTE: The querying of performance information, and how this relates to the Data management and exposure services, is not defined in the present document. 8.4 RAN OAM-Related use case 4: Retrieve configuration schemas |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.4.1 Overview | This use-case allows an rApp acting as a CM service Consumer to retrieve information pertaining to the configuration schemas of one or more managed entities. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.4.2 Background and goal of the use-case | An rApp acting as a CM service Consumer can retrieve information pertaining to one or more managed entities from the Configuration management service Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.4.3 Entities/resources involved in the use-case | 1) RAN OAM-related functions as Configuration management service Producer: a) receive the Get schemas request to retrieve configuration schema information related to one or more managed entities; b) provide the response of success or failure result to the Get schema request. 2) rApp: a) supports functionality to initiate Get schemas procedure to retrieve the configuration schema information. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 82 |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.4.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.4.4.1 Retrieve configuration schema information | Table 8.4.4.1-1: Retrieve configuration schema information use-case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp obtains configuration schema information from the Configuration management service Producer. Actors and Roles - rApp in the role of CM service Consumer that request the configuration schema information pertaining to one or more managed entities. - RAN OAM-related functions in the role of Configuration management service Producer that provide the requested configuration schema information. Assumptions n/a Preconditions The rApp is deployed and authorized to request the configuration schema information. Begins when The rApp determines the need to request the configuration schema information. Step 1 (M) The rApp requests "Get schemas" to obtain the configuration schema information from the RAN OAM-related functions by providing the rAppId, optional query criteria and information about the managed entities, along with the desired configuration schema information, that determines the requested result set. Step 2 (M) The RAN OAM-related functions check whether the rApp is authorized to request Get Schemas to retrieve configuration schema information. Step 3 (M) The RAN OAM-related functions validate the information provided with Get Schema request, if they were provided with the request. Step 4 (M) The RAN OAM-related functions respond to the rApp with a success result along with the desired configuration schema information. Ends when The rApp was able to receive the configuration schema information. Exceptions n/a Post Conditions n/a Traceability REQ-R1-OAM-CmService-FUN1. @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "RAN OAM-related functions" as cmsp endbox endbox rapp -> cmsp: <<R1>> Get schemas request(rAppId, queryCriteria) cmsp --> cmsp: AuthZ note right Check authorization in Collaboration with SME functions end note cmsp --> cmsp: Validate request cmsp -> rapp: <<R1>>Get schemas response (configurationSchema) @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 83 Figure 8.4.4.1-1: Retrieve configuration schema information use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.4.5 Required data | The Get schemas request for retrieval of configuration schemas information contains the rAppId, and query criteria (including information about the related managed entities and about the requested configuration schemas information). The Get schemas response is scoped by the information provided in the request. NOTE: It is up to the design of the authorization mechanism whether the rAppId will be passed as a separate piece of information or will be embedded in or implied by the authorization information. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5 RAN OAM-Related use case 5: Read configuration data | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5.1 Overview | This use-case allows an rApp acting as a CM service Consumer to retrieve information pertaining to the configuration data of one or more managed entities. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5.2 Background and goal of the use-case | An rApp acting as a CM service Consumer can retrieve configuration data pertaining to one or more managed entities from the Configuration management service Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5.3 Entities/resources involved in the use-case | 1) RAN OAM-related functions as Configuration management service Producer: a) receives the request to read configuration data related to one or more managed entities; b) provides the response of success or failure result to the read configuration data request. 2) rApp: a) supports functionality to initiate procedure to read configuration data. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 84 |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5.4.1 Read configuration data | Table 8.5.4.1-1: Read configuration data use-case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp obtains configuration data from the Configuration management service Producer. Actors and Roles - rApp in the role of Service Consumer that request the configuration data pertaining to one or more managed entities. - RAN OAM-related functions in the role of Configuration Management service Producer that provide the requested configuration data information. Assumptions rApp can optionally query configuration schema before requesting to read configuration data. Preconditions The rApp is deployed and authorized to request the configuration data. Begins when The rApp determines the need to request the configuration data. Step 1 (M) The rApp requests "Read configuration" to obtain the configuration data from the RAN OAM-related functions by providing the rAppId, optional query criteria and information about the managed entities, along with information about the desired configuration data, that determines the requested result set. Step 2 (M) The RAN OAM-related functions check whether the rApp is authorized to Read configuration data. Step 3 (M) The RAN OAM-related functions validate information provided with the Read configuration request. Step 4 (M) The RAN OAM-related functions respond to the rApp with a success result along with the desired configuration data. Ends when The rApp was able to receive the configuration data. Exceptions n/a Post Conditions n/a Traceability REQ-R1-OAM-CmService-FUN2. @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rapp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "RAN OAM-related functions" as cmsp endbox endbox rapp -> cmsp: <<R1>> Read configuration request(rAppId, queryCriteria) cmsp --> cmsp: AuthZ note right Check authorization in Collaboration with SME functions end note cmsp --> cmsp: Validate request cmsp -> rapp: <<R1>> Read configuration response (configurationData) @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 85 Figure 8.5.4.1-1: Read configuration data use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.5.5 Required data | The read configuration request for reading configuration data contains the rAppId, and query criteria (including information about the related managed entities and about the requested configuration data information). The read configuration response is scoped by the information provided in the request. NOTE: It is up to the design of the authorization mechanism whether the rAppId will be passed as a separate piece of information or will be embedded in or implied by the authorization information. 8.6 RAN OAM-Related use case 6: Writing configuration changes |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.6.1 Overview | This use-case allows an rApp acting as a CM service Consumer to write information pertaining to the configuration changes of one or more managed entities. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.6.2 Background and goal of the use-case | An rApp acting as a CM service Consumer can write information pertaining to the configuration changes for one or more managed entities through the CM service Producer. |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.6.3 Entities/resources involved in the use-case | 1) RAN OAM-related functions as CM service Producer: a) receives the Write configuration changes request to write configuration change information related to one or more managed entities; b) provides the response of success or failure result to the Service Consumer that initiated the Write configuration request. 2) rApp: a) supports functionality to initiate Write configuration changes request to write the configuration change information. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 86 |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.6.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.6.4.1 Write configuration changes | Table 8.6.4.1-1: Write Configuration changes use case Use Case Stage Evolution / Specification <<Uses>> Related use case Goal The rApp writes configuration change information to the CM service Producer. Actors and Roles - rApp in the role of CM service Consumer that requests writing the configuration change information pertaining to one or more managed entities. - RAN OAM-related functions in the role of CM service Producer that initiate provisioning the requested configuration changes. Assumptions rApp optionally query configuration schema before preparing the write configuration change information. Preconditions The rApp is deployed and authorized to write the configuration change information. Optionally the rApp is subscribed to receive information related to write configuration change status from RAN OAM-related function through Notification or polling. Begins when The rApp determines the need to write the configuration change information. Step 1 (M) The rApp sends a Write configuration changes request to write the configuration change information to the RAN OAM-related functions by providing the rAppId, along with the desired configuration changes information for one or more managed entities. Step 2 (M) The RAN OAM-related functions check whether the rApp is authorized to initiate the Write configuration changes request. Step 3 (M) The RAN OAM-related functions validate the information provided in the Write configuration changes request. Step 4 (M) The RAN OAM-related functions create a Write configuration job from the information provided in the Write configuration changes request. Step 5 (M) RAN OAM-related functions respond to the rApp with information about the job created such as job identifier. The rApp can use this information for querying or receiving notification about the status / result of the requested configuration change. Ends when The rApp was able to receive the Write configuration response. Exceptions n/a Post Conditions n/a Traceability REQ-R1-OAM-CmService-FUN3. @startuml !pragma teoz true skinparam ParticipantPadding 70 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid Autonumber box "Non-RT RIC" #whitesmoke box #ivory participant "rApp" as rapp endbox box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "RAN OAM-related functions" as cmsp endbox endbox rapp -> cmsp: <<R1>> Write configuration changes request\n(rAppId, configuration changes information) cmsp --> cmsp: AuthZ note right Check authorization in Collaboration with SME functions end note cmsp --> cmsp: Validate request cmsp --> cmsp: Create job ETSI ETSI TS 104 230 V10.0.0 (2026-02) 87 cmsp -> rapp: <<R1>> Write configuration changes response\n (Job information) @enduml Figure 8.6.4.1-1: Write configuration changes use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 8.6.5 Required data | The request for writing configuration changes information contains the rAppId and write configuration information for one or more managed entities (e.g. list of attributes and desired values). The RAN OAM-related functions respond to the rApp with configuration job information created, e.g. job identifier. The rApp can use this job information for querying or receiving notifications about the status / result of the requested configuration change which includes e.g.: • a success result if all the requested configuration changes were written in the related managed entities; or • a partial success result if some but not all requested configuration changes were written in the related mentioned managed entities, optionally with further information about the reason of the errors; or • a failure result if one of the requested configuration changes were written in the related managed entities, optionally with further information about the reason of the errors. |
e341f05abb94e155b675f29c6779693c | 104 230 | 9 Use cases for O2-Related Services | NOTE: Use cases for O2-Related services are not defined in the present document. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 88 |
e341f05abb94e155b675f29c6779693c | 104 230 | 10 Use cases for A1-Related Services | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.1 Void | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.2 Void | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3 A1-Related use case 1: Query A1 policy type identifiers | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3.1 Overview | This use case provides the description and requirements for querying the A1 policy type identifiers. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3.2 Background and goal of the use case | Query A1 policy type identifiers procedure is defined as part of A1 policy management service in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3.3 Entities/resources involved in the use case | 1) A1 Policy functions: a) support functionality to allow rApps to query the A1 policy type identifiers. 2) rApp: a) initiates the Query A1 policy type identifiers procedure. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3.4.1 Query A1 policy type identifiers | Table 10.3.4.1-1: Query A1 policy type identifiers Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves the list of identifiers for all the available A1 policy types. Actors and Roles - rApp in the role of A1 policy management service Consumer. - A1 policy functions in the role of A1 policy management service Producer. Assumptions rApp is authorized to consume the A1 policy management service. Preconditions n/a Begins when The rApp determines the need to query the identifiers for all the available A1 policy types. Step 1 (M) The rApp queries the available A1 policy type identifiers, providing the rAppId and optional selection criteria (Near-RT RIC identifier and/or typename (see 3 in A1AP [5], clause 6.2.3.1)). Step 2 (M) The A1 policy management functions validate if the rApp is authorized to query A1 policy type identifiers. Step 3 (M) The A1 policy management functions respond with the list of identifiers for all the available A1 policy types that matches with the query criteria. Further, the response includes for each A1 policy type identifier a list of Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. Ends when The rApp has the identifiers of all the available A1 policy types. Exceptions n/a Post Conditions The rApp has the identifiers of all the available A1 policy types. Traceability REQ-R1-A1P-FUN3. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 89 @startuml 'https://plantuml.com/sequence-diagram' !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "A1 policy functions " as A1P endbox rApp -> A1P : <<R1>> Query A1 policy type identifiers request (rAppId) activate A1P A1P --> A1P : AuthZ note right Check authorization in collaboration with SME functions end note A1P -> rApp : <<R1>> Query A1 policy type identifiers response (list of A1 policy type identifiers) Deactivate A1P @enduml Figure 10.3.4.1-1: Query A1 policy type identifiers use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.3.5 Required data | For querying the A1 policy type identifiers, the rApp sends a query request to the A1 policy functions and optionally provides a Near-RT RIC identifier and/or a typename (see in A1AP [5], clause 6.2.3.1.3) as a selection criterion. If the rApp queries with no selection criteria, the A1 policy functions respond with a list of A1 policy type identifiers. Further, the response includes for each A1 policy type identifier a list of Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. If the rApp queries with selection criteria, the A1 policy functions respond with a list of A1 policy type identifiers which match with the query criteria. Further, the response includes for each A1 policy type identifier a list of Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4 A1-Related use case 2: Query an A1 policy type | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4.1 Overview | This use case provides the description and requirements for querying the information of an A1 policy type. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4.2 Background and goal of the use case | Query A1 policy type procedure is defined as part of A1 policy management service in R1GAP [1]. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 90 |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4.3 Entities/resources involved in the use case | 1) A1 Policy functions: a) support functionality to allow rApps to query the information of an A1 policy type. 2) rApp: a) initiates the Query A1 policy type procedure. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4.4.1 Query A1 policy type | Table 10.4.4.1-1: Query A1 policy type Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves information about A1 policy type. Actors and Roles - rApp in the role of A1 policy management service Consumer. - A1 policy functions in the role of A1 policy management service Producer. Assumptions rApp is authorized to consume the A1 policy management service. Preconditions rApp is aware of the A1 policy type identifier. Begins when The rApp determines the need to query the information of an A1 policy type. Step 1 (M) The rApp queries the information of an A1 policy type with the A1 policy functions by providing rAppId and an A1 policy type identifier. Step 2 (M) The A1 policy functions validate if the rApp is authorized to access the information of an A1 policy type. Step 3 (M) The A1 policy functions retrieve the policy type information. Step 4 (M) The A1 policy functions respond with the requested A1 policy type information. Ends when The rApp have received the information about the requested A1 policy type. Exceptions n/a Post Conditions The rApp have the information about the requested A1 policy type. Traceability REQ-R1-A1P-FUN1. @startuml 'https://plantuml.com/sequence-diagram' !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "A1 policy functions " as A1P endbox rApp -> A1P : <<R1>> Query A1 policy type request (rAppId, A1 policy type identifier) activate A1P A1P --> A1P : AuthZ note right Check authorization in collaboration with SME functions end note A1P --> A1P: retrieve policy type information A1P -> rApp : <<R1>> Query A1 policy type response (A1 policy type information) Deactivate A1P @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 91 Figure 10.4.4.1-1: Query A1 policy type use case flow diagram |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.4.5 Required data | For querying an A1 policy type, the rApp provides the rAppId and an A1 policy type identifier. The A1 policy functions respond with the information about the A1 policy type. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5 A1-Related use case 3: Query A1 policy identifiers | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5.1 Overview | This use case provides the description and requirements for querying the A1 policy identifiers. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5.2 Background and goal of the use case | Query A1 policy identifiers procedure is defined as part of A1 policy management service in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5.3 Entities/resources involved in the use case | 1) A1 Policy functions: a) support functionality to allow rApps to query the A1 policy identifiers. 2) rApp: a) initiates the Query A1 policy identifiers procedure. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 92 |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5.4.1 Query A1 policy identifiers | Table 10.5.4.1-1: Query A1 policy identifiers Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp retrieves the existing A1 policy identifiers. Actors and Roles - rApp in the role of A1 policy management service Consumer. - A1 policy functions in the role of A1 policy management service Producer. Assumptions rApp is authorized to consume the A1 policy management service. Preconditions n/a Begins when The rApp determines the need to query the A1 policy identifiers. Step 1 (M) The rApp queries the A1 policy identifiers with the A1 policy functions and may provide an A1 policy type identifier and/or a Near RT RIC identifier. Step 2 (M) The A1 policy functions validate if the rApp is authorized to query A1 policy identifiers. Step 3 (M) The A1 policy functions respond with the list of A1 policy identifiers that matches with the query criteria. Ends when The rApp has the list of A1 policy identifiers. Exceptions n/a Post Conditions The rApp has the list of A1 policy identifiers. Traceability REQ-R1-A1P-FUN2. @startuml 'https://plantuml.com/sequence-diagram' !pragma teoz true skinparam ParticipantPadding 5 skinparam BoxPadding 10 skinparam defaultFontSize 12 skinparam lifelineStrategy solid autonumber box "Non-RT RIC" #whitesmoke box #ivory participant rApp as rApp endbox box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue participant "A1 policy functions " as A1P endbox rApp -> A1P : <<R1>> Query A1 policy identifers request (rAppId) activate A1P A1P --> A1P : AuthZ note right Check authorization in collaboration with SME functions end note A1P -> rApp : <<R1>> Query A1 policy identifers response (list of A1 policy identifers) Deactivate A1P @enduml ETSI ETSI TS 104 230 V10.0.0 (2026-02) 93 Figure 10.5.4.1-1: Query A1 policy identifiers use case flow diagram |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.