hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 3 Definition of terms, symbols and abbreviations | |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 3.1 Terms | For the purposes of the present document, the terms given in A1GAP [1] apply. |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 3.2 Symbols | Void. |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in A1GAP [1] and the following apply: IETF Internet Engineering Task Force JWT JSON Web Tokens RFC Request For Comments |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 4 A1 interface protocol stack | |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 4.1 General | The architecture for the A1 interface is specified in A1GAP [1]. The protocol stack for the A1 interface supports application protocol and data models as specified in A1AP [2] and A1TD [3]. |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 4.2 Reference model | The A1 interface is defined between the Non-RT RIC and the Near-RT RIC functions. The A1 architecture and principles are described in A1GAP [1]. Figure 4.2-1 illustrates the reference model for the A1 interface. ETSI ETSI TS 103 986 V3.3.0 (2025-05) 7 Non-RT RIC Near-RT RIC A1 interface Figure 4.2-1: A1 interface refer... |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 4.3 Functions and protocol stack | The following layers of the protocol stack for the A1 interface are described in the following clauses: • TCP as specified in IETF RFC 793 [4] provides the communication service at the transport layer; • TLS as specified in IETF RFC 8446 [6] is used to provide secure HTTP connections; • HTTP as specified in IETF RFC 91... |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 5 Network layer | A1 may be transported over IPv6 as specified in IETF RFC 8200 [12] and/or IPv4 as specified in IETF RFC 791 [13]. |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 6 Transport layer | TCP as specified in IETF RFC 793 [4] shall be used as transport protocol. An HTTP connection is mapped to a TCP connection. ETSI ETSI TS 103 986 V3.3.0 (2025-05) 8 Both Non-RT RIC and Near-RT RIC can act as HTTP client and HTTP server. As a result, Non-RT RIC and Near-RT RIC can establish a TCP connection for each dire... |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 7 Security | TLS, mTLS, and OAuth2.0 shall be supported as specified in clause 5.2.1 of SRS [16]. mTLS and OAuth 2.0 with JWT shall be supported as specified in clause 4.7 of SPS [17]. |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 8 Application | As application layer, HTTP/1.1 as specified in IETF RFC 9112 [19] shall be supported, and HTTP/2 as specified in IETF RFC 9113 [20] should be supported. HTTP over TLS as specified in IETF RFC 9110 [18] and IETF RFC 9112 [19] shall be supported. If HTTP/2 is supported, HTTP/2 over TLS as specified in IETF RFC 9113 [20] ... |
805e515bf90c5925b0bc59b17623dca1 | 103 986 | 9 Data interchange | As a data interchange format, JSON as specified in IETF RFC 8259 [11] shall be supported. The objects transported in HTTP messages, and the data types in JSON format, are specified in A1TD [3]. ETSI ETSI TS 103 986 V3.3.0 (2025-05) 9 Annex A (informative): Change history Date Revision Description 2019.09.30 01.00 First... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 1 Scope | The present document specifies the use cases and requirements for the A1 interface. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 2 References | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.1 Terms | For the purposes of the present document, the terms given in A1GAP [1] apply. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.2 Symbols | Void. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in A1GAP [1] apply. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.4 Conventions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.4.1 General | For the purposes of the present document, the conventions in the following clauses apply. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.4.2 Requirements | The requirements and solutions for use cases are based on the methodology specified in ITU-T M.3020 [7], clause A.1.2. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 3.4.3 UML diagrams | The sequence diagrams for the messages that are exchanged between use case actors are based on the OMG UML [8], clause 17.4.4.1 and an example is illustrated in figure 3.4.3-1. Figure 3.4.3-1: Example of UML messages For each message in the present document, the following information is indicated: • interface name and ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 4 General | Non-RT RIC with A1 termination function and A1 related functions in the SMO/Non-RT RIC framework is defined in Non-RT RIC Architecture [5]. Near-RT RIC with A1 Termination and internal functions is defined in Near-RT RIC Architecture [6]. The A1 policy management service (A1-P) and the A1-P procedures are defined in A1... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 5 Requirements | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 5.1 Functional requirements | For the A1 policy management service (A1-P), the functional requirements are included in table 5.1-1. Table 5.1-1: A1 Policy management service (A1-P) functional requirements REQ Description Note REQ-A1-P-FUN1 A1-P shall support discovery of policy type identifiers REQ-A1-P-FUN2 An A1 policy type shall be identified by... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6 Use cases for A1 policy management | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1 Policy type discovery use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.1 Background and goal of the use cases | The policy type discovery use cases define how Non-RT RIC can detect which A1 policy types are available in a Near-RT RIC and how Non-RT RIC can retrieve information about one or more A1 policy types. Policy type information is provided by the Near-RT RIC and is used by Non-RT RIC for creating and by Near-RT RIC for va... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Discovers A1 policy types available in Near-RT RIC. 2) Near-RT RIC: b) Makes A1 policy types available to Non-RT RIC for which it can support A1 policies. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 11 |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.3.1 Query all policy type identifiers | Table 6.1.3.1-1: Query all policy type identifiers use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to discover policy type identifiers for A1 policy types that are available in Near-RT RIC Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions A1 pol... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.3.2 Query single policy type | Table 6.1.3.2-1: Query single policy type use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to retrieve policy type information about an A1 policy type Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy type identifier known to the Non-R... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.3.3 Query multiple policy types | Table 6.1.3.3-1: Query multiple policy types use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to retrieve policy type information for a selection of A1 policy types it is interested in Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.3.4 Query all policy type information | Table 6.1.3.4-1: Query all policy type information use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to retrieve policy type information for all A1 policy types that are available in Near-RT RIC Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions Th... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.1.4 Required data | An A1 policy type is identified by a policy type identifier. A list of policy type identifiers is provided by Near-RT RIC corresponding to available A1 policy types. The Non-RT RIC provides a policy type identifier when querying for information about a single A1 policy type. The Near-RT RIC includes policy type informa... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2 Policy type status use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.1 Background and goal of the use cases | The policy type status use cases define how Non-RT RIC can detect status of an A1 policy type and subscribe to notifications for changes in availability and state of policy types. Policy type status information is provided by the Near-RT RIC and is used by Non-RT RIC when managing A1 policies. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Requests policy type status. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 14 b) Subscribes to notifications for changes in policy type status. 2) Near-RT RIC: a) Responds to queries for policy type status. b) Handles subscriptions and notifies Non-RT RIC about changes in availability and state of policy type... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.3.1 Query policy type status | Table 6.2.3.1-1: Query policy type status use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to retrieve policy type status information for an A1 policy type Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy type identifier known to the ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.3.2 Subscription for policy type status notification | Table 6.2.3.2-1: Subscribe policy type status use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to subscribe to notifications for policy type status information for A1 policy types Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions Non-RT RIC is in... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.3.3 Notify policy type status | Table 6.2.3.3-1: Notify policy type status use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to receive policy type status information for an A1 Policy type Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions Pre-conditions A1 interface is establish... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.2.4 Required data | The policy type status information includes policy type availability change information (i.e. if A1 policy type has been made available or unavailable) and/or state change information related to an A1 policy type. The state of the A1 policy type indicates if A1 policies can be created for the policy type or not, and if... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.3 Create policy use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.3.1 Background and goal of the use cases | The create policy use cases define how Non-RT RIC can create an A1 policy for an A1 policy type and subscribe to notifications for changes in policy status. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.3.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Creates A1 policy in Near-RT RIC. 2) Near-RT RIC: b) Enforces A1 policies for available A1 policy types. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 18 |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.3.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.3.3.1 Create single policy | Table 6.3.3.1-1: Create single policy use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to create A1 policy for an A1 policy type Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy type information known to the Non-RT RIC corresponds to ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.3.4 Required data | For creating an A1 policy of a certain policy type, the Non-RT RIC provides the policy identifier and the policy information, the callback URI for policy result delivery, and optionally the callback URI for policy status notifications. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4 Query policy use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4.1 Background and goal of the use cases | The query policies use cases define how Non-RT RIC can query for information on existing A1 policies. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Discovers A1 policies that exist in the Near-RT RIC. b) Retrieves policy information. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 19 2) Near-RT RIC: a) Handles A1 policies. b) Responds to queries for policy identifiers and policy information. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4.3.1 Query policy identifiers | Table 6.4.3.1-1: Query policy identifiers use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to discover policy identifiers for A1 policies that exist in Near-RT RIC Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions A1 policies exist in Near-RT RIC... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4.3.2 Query single policy | Table 6.4.3.2-1 Query single policy use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to retrieve information about an A1 policy Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The A1 policy identifier known to the Non-RT RIC corresponds to an e... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.4.4 Required data | For querying policy identifiers, the Non-RT RIC optionally provides a policy type identifier as filter parameter. For querying an A1 policy, the Non-RT RIC provides a policy identifier. The policy information includes the A1 policy definition. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.5 Update policy use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.5.1 Background and goal of the use cases | The update policy use cases define how Non-RT RIC can update an existing A1 policy. Non-RT RIC provides updated policy information. The reason for the update can be related to state of the A1 policy type and received policy status information. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.5.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Updates A1 policy in Near-RT RIC that it has created. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 21 2) Near-RT RIC: b) Handles A1 policies for available policy types. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.5.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.5.3.1 Update single policy | Table 6.5.3.1-1: Update single policy use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to update an existing A1 policy Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy identifier known to the Non-RT RIC corresponds to an existing A1 p... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.5.4 Required data | For updating an A1 policy, the Non-RT RIC provides the policy identifier and updated policy information and/or callback URI for policy status notifications. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.6 Delete policy use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.6.1 Background and goal of the use cases | The delete policy use cases define how Non-RT RIC can delete an A1 policy. The reason for the deletion can be related to the state of the A1 policy type and received policy status information. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.6.2 Entities/resources involved in the use cases | 1) Non-RT RIC: ETSI ETSI TS 103 985 V1.4.0 (2025-05) 22 a) Deletes A1 policy in Near-RT RIC that it has created. 2) Near-RT RIC: b) Handles A1 policies for available policy types. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.6.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.6.3.1 Delete single policy | Table 6.6.3.1-1: Delete single policy use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to delete an existing A1 policy Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy identifier known to the Non-RT RIC corresponds to an existing A1 p... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.6.4 Required data | For deleting an A1 policy, the Non-RT RIC provides the policy identifier. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7 Policy status use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7.1 Background and goal of the use cases | The policy status use cases define how Non-RT RIC can detect status, and changes in status, of an A1 policy. Policy status information is provided by the Near-RT RIC and is used by Non-RT RIC when managing A1 policies. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7.2 Entities/resources involved in the use cases | 1) Non-RT RIC: ETSI ETSI TS 103 985 V1.4.0 (2025-05) 23 a) Requests A1 policy status. b) Receives notifications about changes in policy status. 2) Near-RT RIC: a) Handles A1 policy and responds to queries for policy status. b) Notifies Non-RT RIC about changes in policy status. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7.3.1 Query policy status | Table 6.7.3.1-1: Query policy status use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to retrieve policy status information for an existing A1 policy Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions The policy identifier known to the Non-RT RIC ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7.3.2 Notify policy status change | Table 6.7.3.2-1: Notify policy status change use case Use case stage Evolution / specification <<Uses>> Related use Goal Non-RT RIC to receive policy status change information for an existing A1 policy Actors and Roles Non-RT RIC as A1-P Consumer Near-RT RIC as A1-P Producer Assumptions Non-RT RIC has the schema for in... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 6.7.4 Required data | The policy status information includes the A1 policy status that is formulated based on, and validated against, the policy status schema and indicates if A1 policy is enforced or not enforced. The policy status change information includes indication about a change of the A1 policy status. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7 Use cases for A1 enrichment information | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1 EI discovery use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1.1 Background and goal of the use cases | The EI discovery use cases define how Near-RT RIC can detect which EI types are available in Non-RT RIC and how Near-RT RIC can retrieve information about EI types. EI type information is provided by Non-RT RIC and is used by Near-RT RIC for creating, and by Non-RT RIC for validating, EI jobs. EI type information is al... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Makes EI types available to Near-RT RIC for which it can support EI jobs and deliver EI job results. b) Provides information on EI types and constraints for EI jobs. 2) Near-RT RIC: a) Discovers EI types available in Non-RT RIC. b) Retrieves EI type information. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1.3.1 Query EI type identifiers | Table 7.1.3.1-1: Query EI type identifiers use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to discover EI type identifiers for EI types that are available in Non-RT RIC Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions EI types are available ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1.3.2 Query EI type | Table 7.1.3.2-1: Query EI type use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to retrieve EI type information about an EI type Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI type identifier known to the Near-RT RIC corresponds to a... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.1.4 Required data | An EI type is identified by an EI type identifier. A list of EI type identifiers is provided by Non-RT RIC corresponding to available EI types. The Near-RT RIC provides an EI type identifier when querying for information about an EI type. In response to a query for information about an EI type, the Non-RT RIC includes ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2 EI type status use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.1 Background and goal of the use cases | The EI type status use cases define how Near-RT RIC can detect status of an EI type and subscribe to notifications for changes in availability and status of EI types. EI type status information is provided by the Non-RT RIC and is used by Near-RT RIC when managing EI jobs. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 27 |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Responds to queries for EI type status. b) Handles subscriptions and notifies Near-RT RIC about changes in availability and state of EI types. 2) Near-RT RIC: a) Requests EI type status. b) Subscribes to notifications for changes in EI type status. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.3.1 Query EI type status | Table 7.2.3.1-1: Query EI type status use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to retrieve EI type status information for an EI type Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI type identifier known to the Near-RT RIC corr... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.3.2 Subscription for EI type status notification | Table 7.2.3.2-1: Subscribe EI type status use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to subscribe to notifications for EI type status information Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions Near-RT RIC is interested in notification... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.3.3 Notify EI type status | Table 7.2.3.3-1: Notify EI type status use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to receive EI type status information for an EI type Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions Pre-conditions A1 interface is established, and the ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.2.4 Required data | The EI type status information includes EI type availability change information (i.e. if EI type has been made available or unavailable) and/or state change information related to an EI type. The state of the EI type state indicates if EI jobs can be created for the EI type or not, and if EI jobs for the EI type would ... |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.3 Create EI job use cases | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.3.1 Background and goal of the use cases | The create EI job use cases define how Near-RT RIC can create an EI job for an EI type and subscribe to notifications for changes in EI job status. Near-RT RIC provides EI job definition information based on EI type information and considering the EI job constraints. |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.3.2 Entities/resources involved in the use cases | 1) Non-RT RIC: a) Handles EI jobs for available EI types. 2) Near-RT RIC: b) Creates EI job in Non-RT RIC. ETSI ETSI TS 103 985 V1.4.0 (2025-05) 31 |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.3.3 Solutions | |
f687403436bd8ed7f9d53c4101cec621 | 103 985 | 7.3.3.1 Create EI job | Table 7.3.3.1-1: Create EI job use case Use case stage Evolution / specification <<Uses>> Related use Goal Near-RT RIC to create EI job for an EI type Actors and Roles Non-RT RIC as A1-EI Producer Near-RT RIC as A1-EI Consumer Assumptions The EI type information known to the Near-RT RIC corresponds to an available EI t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.