hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 P... |
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 Prod... |
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... |
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) suppor... |
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 Rol... |
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 ro... |
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... |
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 s... |
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 funct... |
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 d... |
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... |
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 subscri... |
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 managemen... |
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 exposu... |
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 serv... |
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 servic... |
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 s... |
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 ... |
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 a... |
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 T... |
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 ... |
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 defin... |
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 ... |
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 pertaini... |
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 perf... |
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 initia... |
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 co... |
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... |
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... |
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 ... |
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... |
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) rAp... |
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... |
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... |
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 po... |
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 l... |
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. Assumpt... |
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... |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.5.5 Required data | For querying the A1 policy identifiers, the rApp optionally provides an A1 policy type identifier and/or a Near RT RIC identifier as a query parameter. The A1 policy functions respond with the list of A1 policy identifiers. 10.6 A1-related use case 4: Create, Query, Update and Delete an A1 policy |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.1 Overview | This use case enables rApps to create an A1 policy, query an A1 policy, update an A1 policy, and delete an A1 policy. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.2 Background and goal of the use case | Create A1 policy, Query A1 policy, Update A1 policy, and Delete A1 policy procedures are defined as part of A1 policy management service in R1GAP [1]. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.3 Entities/resources involved in the use case | 1) A1 policy functions: a) support functionality to allow rApps to request creating7, querying, updating and deleting an A1 policy. 2) rApp: a) initiates the procedures for creating an A1 policy, querying an A1 policy, updating an A1 policy, and deleting an A1 policy. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 94 |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.4.1 Create a single A1 policy in an identified Near-RT RIC | Table 10.6.4.1-1: Create a single A1 policy in an identified Near-RT RIC Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp initiates creation of an A1 policy in an identified Near-RT RIC. Actors and Roles - rApp in the role of the A1 policy management service Consumer. - A1 policy functions in... |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.4.3 Update an A1 policy | Table 10.6.4.3-1: Update an A1 policy Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp updates an existing A1 policy. Actors and Roles - rApp in the role of an A1 policy management service Consumer. - A1 policy functions in the role of an A1 policy management service Producer. Assumptions The... |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.4.4 Delete an A1 policy | Table 10.6.4.4-1: Delete an A1 policy Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp deletes an existing A1 policy. Actors and Roles - rApp in the role of an A1 policy management service Consumer. - A1 policy functions in the role of an A1 policy management service Producer. Assumptions The... |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.6.5 Required data | For creating an A1 policy of a certain type in a Near-RT RIC, the rApp provides an A1 policy type identifier, A1 policy information, its rApp identifier (rAppId) and, a Near-RT RIC identifier. The A1 policy functions respond with the A1 policy identifier of the created policy. For querying an A1 policy, the rApp provid... |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.7 A1-Related use case 5: Query the status of an A1 policy | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.7.1 Overview | This use case provides the description and requirements for querying the status of an A1 policy status. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.7.2 Background and goal of the use case | Query A1 policy status procedure is defined as part of A1 policy management service in R1GAP [1]. ETSI ETSI TS 104 230 V10.0.0 (2026-02) 100 |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.7.3 Entities/resources involved in the use case | 1) A1 policy functions: a) support functionality to allow rApps to query the status of an A1 policy. 2) rApp: a) initiates the procedure for querying status of an A1 policy. |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.7.4 Solutions | |
e341f05abb94e155b675f29c6779693c | 104 230 | 10.7.4.1 Query the status of an A1 policy | Table 10.7.4.1-1: Query status of A1 policy Use Case Stage Evolution / Specification <<Uses>> Related use Goal The rApp is informed about the status of an A1 policy. 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. ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.