hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.3.4 Combining RIC services as a sequence of RIC services | RIC services defined in clause 5.3.2 may be combined using a sequence of different RIC services implemented using a procedure executed within the Near-RT RIC. Examples include: - REPORT followed by POLICY. In this case, at each occurrence of the defined Event Trigger, the E2 Node would be instructed to send a defined R... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.4 RAN Function E2 Service Model | As described in clause 5.1 the E2 interface is used to carry messages between a given E2 Node and Near-RT RIC. These messages may contain RAN Function specific content which is described in the corresponding RAN Function specific E2 Service Model. Each RAN Function is described in the following terms: - RAN Function De... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5 E2 support services | |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5.1 General | The E2 support services are supported by the following global procedures: - E2 Setup. - E2 Reset. - RIC Service Update. - E2 Node Configuration Update. - E2 Removal. - Reporting of General Error Situations. The E2 Setup, E2 Reset, RIC Service Update, E2 Node Configuration Update and E2 Removal procedures are described ... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5.2 E2 Setup procedure | The E2 Setup procedure is used to establish the E2 interface between the Near-RT RIC and an E2 Node. During this procedure the E2 Node provides: - List of supported RIC services and mapping of services to functions within the E2 Node. This information is specific to each RAN Function in the E2 node and is defined by a ... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5.3 E2 Reset procedure | The E2 Reset procedure is used by either the E2 Node or Near-RT RIC to reset the E2 interface. Information previous exchanged during E2 Setup, E2 Node Configuration Update and RIC Service Update procedures shall be maintained however the outcome of all previous RIC Subscription shall be deleted from the E2 Node and E2 ... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5.4 RIC Service Update procedure | The RIC Service Update procedure is used by the E2 Node to inform the Near-RT RIC of any change to the list of supported RIC services and mapping of services to functions within the E2 Node. This information is specific to each RAN Function in the E2 node and is defined by a specific E2 Service Model as described in cl... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5.5 E2 Node Configuration Update procedure | The E2 Node Configuration Update procedure is used by the E2 Node to inform the Near-RT RIC of any change to the configuration of the E2 Node and/or E2 Node initiated changes to TNL Associations associated with the E2 interface. This information is specific to the E2 Node type and defined by the E2 Node system specific... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 5.5.6 E2 Removal procedure | The E2 Removal procedure is used by either the E2 Node or Near-RT RIC to release the E2 signalling connection. If the procedure is E2 node initiated, after the E2 REMOVAL RESPONSE is received, the E2 node initiates termination of all TNL associations associated with this E2 interface. The Near-RT RIC and E2 nodes relea... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 6 E2 interface signalling | |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 6.1 E2 Control Plane Protocol (E2AP) | The control plane protocol stack of the E2AP interface is shown on Figure 6.1-1. The transport network layer is built on IP transport. For the reliable transport of signalling messages, IETF RFC 4960 [12] is added on top of IP. When configurations with multiple SCTP associations are supported, the Near-RT RIC may reque... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 6.2 Multiple TNLAs over E2 | The Near-RT RIC and E2 Node supports multiple TNL associations over E2 interface. An initial TNL association is established during E2 Setup procedure with E2 Node initiating SCTP connection. At this point the single TNL association is configured to be used for both RIC Services (clause 5.3) and E2 Support functions (cl... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 7 Security for the E2 interface | |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 7.1 General | The security requirements given in this clause only apply to the E2 interface. |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 7.2 Requirements for the E2 interfaces | The requirements given below apply to E2 interface defined in the present document: - E2 interface shall support confidentiality, integrity, replay protection and data origin authentication. ETSI ETSI TS 104 038 V4.1.0 (2024-10) 34 |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 7.3 Security mechanism for the E2 interface | In order to protect the traffic on the E2 interface, IPsec ESP implementation shall be supported according to IETF RFC 4303 [20] as profiled by ETSI TS 133 210 [21]. For IPsec implementation, tunnel mode is mandatory to support while transport mode is optional. The multiple IKE Security Associations (SAs), multiple IPs... |
726509adae72df2686cf4ad7fa82ea05 | 104 038 | 8 Other E2 interface specifications | 8.1 O-RAN E2 interface: E2 Application Protocol (E2AP) (ORAN-WG3.E2AP) ETSI TS 104 039 [2] specifies the signalling protocol between the Near-RT RIC and the E2 Node over the E2 interface. 8.2 O-RAN E2 interface: E2 Service Model (E2SM) specifications ETSI TS 104 040 [17] provides the list of the supported RAN Function-... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 1 Scope | The present document specifies the top-level use cases as defined by O-RAN WG1 UCTG (Use Case Task Group). For each use case, the document describes the motivation, resources, steps involved, and the data requirements. These top-level use cases are further detailed in relevant WGs along with the requirements for O-RAN ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 2 References | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 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... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 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... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 3 Definition of terms, symbols and abbreviations | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 3.1 Terms | For the purposes of the present document, the terms and definitions given in [i.1] and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in [i.1]. A1: interface between Non-RT RIC and Near-RT RIC to enable policy-driven guidance of Near-RT R... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 3.2 Symbols | Void. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in [i.1] and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in [i.1]. AI/ML Artificial Intelligence/Machine Learning ALD Antenna Line Device AMF API Manage... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4 Use cases | 4.1 Use case 1: Context-Based Dynamic HO Management for V2X |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.1.0 Introduction | This use case provides the background, motivation, and requirements for the Context-based Dynamic HO Management for V2X use case, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing latency and improving radio resource utilization. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.1.1 Background and goal of the use case | V2X communication allows for numerous potential benefits such as increasing the overall road safety, reducing emissions, and saving time. Part of the V2X architecture is the V2X UE (SIM + device attached to vehicle) which communicates with the V2X Application Server (V2X AS). The exchanged information comprises Coopera... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.1.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary performance, configuration, and other data for constructing/training relevant AI/ML models that will be deployed in Near-RT RIC to assist in the V2X HO management function. For example, this could be a clustering algorithm that classifies traffic situations and radio conditions that... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.1.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.1.3.1 Context-based Dynamic Handover Management for V2X | The context of the Context-based Dynamic Handover Management for V2X use case is captured in table 4.1.3.1-1. Table 4.1.3.1-1: Context-based Dynamic Handover Management for V2X Use Case Stage Evolution / Specification <<Uses>> Related use Goal Drive V2X UE HOs in RAN according to defined intents, policies, and configur... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.1.4 Required data | The measurement counters and KPIs (as defined by 3GPP) shall be appropriately aggregated by cell, QoS type, slice, etc. 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighboring cells. 2) UE connection and mobility/handover statistics with indication of successful and failed handovers and error ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.2.0 Introduction | This use case provides the background, motivation, and requirements for the support the use case of flight path based dynamic UAV Radio Resource Allocation, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing unnecessary handover and improving radio resource utilizat... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.2.1 Background and goal of the use case | The field trials' results show that the coverage for low altitude is good and can provide various services for terrestrial UEs with good performance. However, since the site along the flight is mainly for terrestrial UEs, the altitude of the UAV is always not within the main lobe of the ground station antenna. And the ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.2.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary of O-RAN Support for Aerial Vehicles related measurement metrics from network level measurement report and SMO (can acquire data from application) for constructing/training relevant AI/ML model that will be deployed in Near-RT RIC to assist in the O-RAN Support for Aerial Vehicles f... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.2.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.2.3.1 Flight path based dynamic UAV Radio Resource Allocation | The context of the flight path based dynamic UAV Radio Resource Allocation use case is captured in table 4.2.3.1-1. Table 4.2.3.1-1: Flight path based dynamic UAV Radio Resource Allocation Use Case Stage Evolution / Specification <<Uses>> Related use Goal In the O-RAN architecture, the flight path based dynamic UAV Rad... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.2.4 Required data | Multi-dimensional data are expected to be retrieved for AI/ML model training and policies generation. 1) Network level measurement report, including: a) UE level radio channel information, mobility related metrics. b) UE level location information. 2) Aerial Vehicles related measurement metrics collected from SMO (can ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.3.0 Introduction | This use case provides the background, motivation, and requirements for the UAV control vehicle use case, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing latency and improving radio resource utilization. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.3.1 Background and goal of the use case | As shown in figure 4.3.1-1, this scenario refers to a Rotor UAV flying at low altitude and low speed, and carrying cameras, sensors and other devices mounted. The Operation terminals work in the 5,8 GHz to remote control the UAV for border/forest inspection, high voltage/base station inspection, field mapping, pollutio... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.3.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Support sending resource allocation requirements to Near-RT RIC. b) Support receiving UE-level radio resource adjustment requirements from the Application Server. c) Support communication between Non-RT RIC and Near-RT RIC with UE-level policies. 2) Near-RT RIC: a) Support for receiving resource alloc... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.3.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.3.3.1 UAV Control Vehicle | The context of the UAV control vehicle use case is captured in table 4.3.3.1-1. Table 4.3.3.1-1: UAV control vehicle Use Case Stage Evolution / Specification <<Uses>> Related use Goal In the UAV control vehicle scenario, the UE-level radio resource configuration optimization is achieved through the delivery of policies... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.3.4 Required data | Multi-dimensional data are expected to be retrieved for policy generation and performance improvements brought by the policy: 1) The number of terminals accessed, the identification information such as an UE ID that distinguishes each UAV connected with UAV the control vehicle), and the resource information assigned by... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4 Use case 4: QoE Optimization | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support real-time QoE optimization. Moreover, some high-level description and requirements over Non-RT RIC, A1 and E2 interfaces are introduced. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 24 |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.1 Background and goal of the use case | The highly demanding 5G native applications like Cloud VR are both bandwidth consuming and latency sensitive. However, for such traffic-intensive and highly interactive applications, current semi-static QoS framework cannot efficiently satisfy diversified QoE requirements especially taking into account potentially sign... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary QoE related measurement metrics from network level measurement report and SMO (can acquire data from application) for constructing/training relevant AI/ML model that will be deployed in Near-RT RIC to assist in the QoE Optimization function. For example, this could be application cl... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.3.1 AI/ML Model training and distribution | The context of the model training and distribution is captured in table 4.4.3.1-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 25 Table 4.4.3.1-1: Model training and distribution Use Case Stage Evolution / Specification <<Uses>> Related use Goal Model training and Distribution. Actors and Roles Non-RT RIC, Near-RT RIC, SMO,... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.3.2 Policy generation and performance evaluation | The context of the policy generation and performance evaluation is captured in table 4.4.3.2-1. Table 4.4.3.2-1: Policy generation and performance evaluation Use Case Stage Evolution / Specification <<Uses>> Related use Goal Policy generation and performance evaluation. Actors and Roles Non-RT RIC, Near-RT RIC, SMO. As... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.3.3 RAN Performance Analytics | The context of the RAN Performance Analytics is captured in table 4.4.3.3-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 28 Table 4.4.3.3-1: RAN Performance Analytics Use Case Stage Evolution / Specification <<Uses>> Related use Goal Expose RAN analytics information to external applications or MEC. Actors and Roles Non-RT R... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.4.4 Required data | Multi-dimensional data are expected to be retrieved by Non-RT RIC for AI/ML model training and policies/intents generation. Network level measurement data from O-CU/O-DU are also expected to report to Near-RT RIC for RAN analytics information inference. 1) Network level measurement report, including: a) UE level radio ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5 Use case 5: Traffic Steering | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.0 Introduction | This use case provides the motivation, description, and requirements for traffic steering use case, allowing operators to specify different objectives for traffic management such as optimizing the network/UE performance, or achieving balanced cell load. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.1 Background and goal of the use case | 5G systems will support many different combinations of access technologies namely; LTE (licensed band), NR (licensed band), NR-U (unlicensed band), Wi-Fi® (unlicensed band) [i.3]. Several different multi-access deployment scenarios are possible with 5GC to support wide variety of applications and satisfy the spectrum r... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary performance, configuration, and other data for defining and updating policies to guide the behavior of traffic management function in Near-RT RIC. For example, the policy could relate to specifying different optimization objectives to guide the carrier/band preferences at per-UE or ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.3.1 Policy Based Traffic steering | The context of the traffic steering use case is captured in table 4.5.3.1-1. Table 4.5.3.1-1: Traffic steering Use Case Stage Evolution / Specification <<Uses>> Related use Goal Drive traffic management in RAN in accordance with defined intents, policies, and configuration. Actors and Roles Non-RT RIC: RAN policy contr... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.3.2 Enrichment Information Based Traffic Steering | In this variation, when the Near-RT detects cell congestion, it requests via A1-EI to Non-RT RIC analytics that can be used as additional information to assist in its efforts at alleviating that congestion. The context of the enrichment information based traffic steering use case is captured in table 4.5.3.2-1. Table 4... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.5.4 Required data | The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) shall be appropriately aggregated by cell, QoS type, slice, etc. 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighboring cells. In multi-access scenarios this will also include intra-RAT and inter-R... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6 Use case 6: Massive MIMO Beamforming Optimization | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.0 Introduction | This use case provides the motivation, description, and requirements for Non-RT and Near-RT loop Massive MIMO beamforming optimization use case. Massive MIMO system configuration can allow operators to optimize the network performance and QoS by e.g. Non-RT and Near-RT loop balancing cell loads or reducing inter-cell i... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.1 Background and goal of the use case | Massive MIMO (mMIMO) is among the key levers to increase performance and QoS in 5G networks. Capacity enhancement is obtained by means of beamforming of the transmitted signals, and by spatially multiplexing data streams for both Single User (SU) and for Multi User (MU) MIMO. Beamforming increases the received signal p... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.2 Entities/resources involved in the use case | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.2.1 Non-RT Massive MIMO GoB Beam Forming Optimization | 1) Non-RT RIC: a) Retrieve necessary configurations, performance indicators, measurement reports, user activity information and other data from SMO and RAN directly for the purpose of constructing/training relevant AI/ML models that will be deployed in Non-RT RIC to assist in the massive MIMO optimization function. b) ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.2.2 Near-RT Beam-based Mobility Robustness Optimization | 1) SMO: a) Trigger bMRO configuration. (O) b) Send bMRO configuration target to Near-RT RIC. c) Send GoB Beam Pattern related information (Beam Pattern configuration, Beam Pattern configuration list, Beam Pattern configuration switch timing/condition, Beam Pattern identifier etc.) to the Near-RT RIC. 2) Near-RT RIC: a)... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.3.1 Non-RT Massive MIMO GoB Beam Forming optimization | The context of the massive MIMO beamforming optimization is captured in table 4.6.3.1-1. Table 4.6.3.1-1: Massive MIMO GoB Beam Forming optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable flexible optimization of the multi-cell M-MIMO beamforming performance (capacity and coverage) by... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.3.2 Near-RT Massive MIMO Beam-based Mobility Robustness Optimization | The context of the Massive MIMO Beam-based Mobility Robustness Optimization is captured in table 4.6.3.2-1. Table 4.6.3.2-1: Beam-based Mobility Robustness Optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable flexible optimization of the Beam-based Mobility Robustness Optimization by m... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.4 Required data | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.4.1 Non-RT Massive MIMO GoB Beam Forming optimization | There are different types of data that are required from different parts of the network, and the following list summarizes with some examples: 1) Environment data: Cell site information (location), inter-site distance, BS system configuration, (e.g. operating frequency, bandwidth, frame structure, transmit power, defau... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.6.4.2 Near-RT Massive MIMO Beam-based Mobility Robustness Optimization | 1) Beam-specific handover related KPMs, as specified in 3GPP TS 28.552 [6], in 3GPP TS 28.622 [8] and in 3GPP TS 28.624 [9] from E2 Nodes, similar to: a) Too Early Handovers. b) Too Late Handovers. c) Attempted Handovers. d) Successful Handovers. e) Failed Handovers. f) The time granularity is an integer multiple of 1 ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7 Use case 7: RAN Sharing | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7.0 Introduction | This use case provides the motivation, description, and requirements for RAN sharing use case. The goal of this use case is to enable multiple operators to share the same O-RAN infrastructure, while allowing them to remotely configure and control the shared resources via a remote O1, O2 and E2 interface. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7.1 Background and goal of the use case | RAN sharing is envisioned as an efficient and sustainable way to reduce the network deployment costs, while increasing network capacity and coverage. Among the different RAN sharing models that have been experimented so far, a special focus is put here on the evaluation of the compatibility of the "Geographical Split" ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7.2 Entities/resources involved in the use case | 1) SMO-Sharing APP (site A): a) SLA Monitoring: checks that orchestration/management requests sent by Operator B are in line with the SLA. b) Remote provisioning and initial VNF deployment: asks the IMF to instantiate the VNFs for Operator B. c) Remote management operations via "O1, O2 remote": configures the VNF of Op... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7.3.1 RAN sharing | The context of the RAN Sharing Use Case is captured in table 4.7.3.1-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 44 Table 4.7.3.1-1: RAN Sharing Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable two operators to share the same O-RAN infrastructure, while allowing them to remotely configur... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.7.4 Required data | Multi-dimensional data are expected to be handled by the SMO-Sharing APP: 1) SLA data needs to be converted in a set of condition steps to be matched for each request of the Host Operator (Operator B). 2) SMO needs to handle O1, O2 messages sent by the Host Operator, converting them in local O1, O2 commands. The RAN of... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8 Use case 8: QoS Based Resource Optimization | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support RAN QoS based resource optimization. Moreover, some high-level description and requirements over Non-RT RIC and A1 interfaces are introduced. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8.1 Background and goal of the use case | QoS based resource optimization can be used when the network has been configured to provide some kind of preferential QoS for certain users. One such scenario can be related to when the network has been configured to support e2e slices. In this case, the network has functionality that ensures resource isolation between... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Monitor necessary QoS related metrics from network function and other SMO functions. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 47 b) Send policies to Near-RT RIC to drive QoS based resource optimization at RAN level in terms of expected behavior. 2) Near-RT RIC: a) Support interpretation and execution of... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8.3.1 QoS based resource optimization | The context of the QoS based resource optimization is captured in table 4.8.3.1-1. Table 4.8.3.1-1: QoS based resource optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Drive QoS based resource optimization in RAN in accordance with defined policies and configuration. Actors and Roles Non-... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.8.4 Required data | For this use case, different kind of observability need to be reported to Non-RT RIC. First Non-RT RIC shall monitor resource consumption in the area. As long as resource consumption is low, the RAN scheduler will be able to give all users in an area the needed resources. When resource consumption in an area increases ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9 Use case 9: RAN Slice SLA Assurance | The 3GPP standards architected a sliceable 5G infrastructure which allows creation and management of customized networks to meet specific service requirements that can be demanded by future applications, services and business verticals. Such a flexible architecture needs different requirements to be specified in terms ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9.1 Background and goal of the use case | In the 5G era, network slicing is a prominent feature which provides end-to-end connectivity and data processing tailored to specific business requirements. These requirements include customizable network capabilities such as the support of very high data rates, traffic densities, service availability and very low late... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve RAN slice SLA target from respective entities such as SMO, NSSMF. b) Long term monitoring of RAN slice performance measurements. c) Training of potential ML models that will be deployed in Non-RT RIC for slow loop optimization and/or Near-RT RIC for fast loop optimization. d) Support deployme... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9.3 Solutions | 4.9.3.1 Creation and deployment of RAN slice SLA assurance models and control apps The context of the creation and deployment of RAN slice SLA assurance models and control apps is captured in table 4.9.3.1-1. Table 4.9.3.1-1: Creation and deployment of RAN slice SLA assurance models and control apps Use Case Stage Evol... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9.3.2 Slow loop RAN Slice SLA optimization | The context of the slow loop RAN Slice SLA optimization is captured in table 4.9.3.2-1. Table 4.9.3.2-1: Slow loop RAN Slice SLA optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Slow loop RAN Slice SLA optimization. Actors and Roles Non-RT RIC, Near-RT RIC, SMO, RAN. Assumptions All relev... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9.3.3 Fast loop RAN Slice SLA optimization | The context of the fast loop RAN Slice SLA optimization is captured in table 4.9.3.3-1. Table 4.9.3.3-1: Fast loop RAN Slice SLA optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Fast loop RAN Slice SLA optimization. Actors and Roles Non-RT RIC, Near-RT RIC, SMO, RAN. Assumptions All relev... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.9.4 Required data | The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) shall be appropriately aggregated by cell, QoS type, slice, etc. 1) Per-UE performance statistics such as CSI, RSRP/CQI distribution. 2) Per slice performance statistics such as PDCP throughput, PRB usage. 3) Per UE performa... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10 Use case 10: Multi-vendor Slices | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.0 Introduction | This use case "Multi-vendor slices" is a case that vO-DU and vO-CU functions composing each slice is provided from different vendor. In this sub clause, concept, motivation and benefits of introducing "Multi-vendor slices" are explained and candidate solutions are studied. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 56 |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.1 Background and goal of the use case | Proposed use case enables multiple slices with functions provided from multi- vendors, such as slice #1 is composed with DU and CU provided from vendor A and slice #2 is composed with DU and CU provided from vendor B (see figure 4.10.1-1). Figure 4.10.1-1: Multi-vendor Slices To support Multi-vendor slicing, there are ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.2 Entities/resources involved in the use case | 1) SMO Multi-vendor Slice App: a) Configures vO-DU and vO-CU. b) Configures O-RU to connect to vO-DU. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 57 2) Near-RT RIC: a) Shares MAC related data unique for UE among vO-DUs. b) Support communication of configuration parameters to RAN. 3) E2 Nodes (vO-CU, vO-DU, O-RU): a) Primary... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.3.1 Data transmission call flow example for Multi-vendor slices use case | The context of data transmission call flow example for Multi-vendor slices use case is captured in table 4.10.3.1-1. Table 4.10.3.1-1: Data transmission call flow example for Multi-vendor slices use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal UE communicates on slice #1 and #2 respectively A... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.