hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.3.2 Data transmission call flow example for RAN sharing use case | The context of data transmission call flow example for RAN sharing use case is captured in table 4.10.3.2-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 61 Table 4.10.3.2-1: Data transmission call flow example for RAN sharing use case Use Case Stage Evolution / Specification <<Uses>> Related use Goal UE communicates on seco... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.10.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 CSI. 2) Per slice performance statistics such as PDCP throughput, PRB usage. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11 Use case 11: Dynamic Spectrum Sharing | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11.0 Introduction | This use case provides the background, motivation, and requirements to realize Dynamic Spectrum Sharing (DSS) over the ORAN architecture. This is to enable operators to adapt radio resource allocation policies and control to dynamically share radio spectrum between 4G and 5G networks. ETSI ETSI TS 104 036 V12.0.0 (2025... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11.1 Background and goal of the use case | As we transition from 4G to 5G, the spectral resources used for 5G deployment is a key consideration and this situation varies from one operator to another. Though, new C-band resources between 3-6 GHz and mmWave bands have been acquired by operators, these bands suffer from great propagation and penetration loss, limi... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Receive SMO's DSS specific service requirement for the RAN and translate them into resource sharing policies. b) Provide long-term policies in terms of scheduling guidance to 4G and 5G scheduler over A1 to Near-RT RIC, considering business, user, spatial and temporal workload factors, policies related... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11.3.1 Dynamic Spectrum Sharing for 4G and 5G | The context of the Dynamic Spectrum Sharing for 4G and 5G is captured in table 4.11.3.1-1. Table 4.11.3.1-1: Dynamic Spectrum Sharing for 4G and 5G Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable operators to dynamically share spectrum in the existing 4G deployment with 5G systems, based on th... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.11.4 Required data | Multiple observability data from RAN need to be reported to SMO, Non-RT RIC and Near-RT RIC for DSS to operate. The required data for DSS use case is captured in table 4.11.4-1. Table 4.11.4-1: Required data for DSS use case Category Parameters / Measurements RAT Source / Interface Reference 4G/5G DSS configuration and... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12 Use case 12: NSSI Resource Allocation Optimization | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12.0 Introduction | This use case provides the background, motivation, description, and requirements for the NSSI resource allocation optimization use case, allowing operators to optimize the allocation resources to NSSI(s) with wide range service requirements. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12.1 Background and goal of the use case | 5G networks are becoming increasingly complex with the densification of millimeter wave small cells, and various new services, such as enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC) that are characterized by high speed high data volume... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12.2 Entities/resources involved in the use case | 1) SMO: a) Pre-provision the default NSSI resource quota policy as constraint for NSSI resource allocation optimization. This information is optionally used by the Non-RT RIC in case the resource quota that needs to be allocated per slice is not specified during the slice creation and for conflict resolution at the tim... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12.3.1 NSSI Resource Allocation Optimization | The context of the NSSI Resource Allocation Optimization is captured in table 4.12.3.1-1. Table 4.12.3.1-1: NSSI Resource Allocation Optimization Use Case stage Evolution/Specification <<Uses>> Related use Goal To automatically optimize the NSSI resource allocation by leveraging the AI/ML model that was trained via the... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.12.4 Required data | The measurement counters, as specified in 3GPP TS 28.552 [6], which are measured on per S-NSSAI include: • DL PRB used for data traffic (3GPP TS 28.552 [6], clause 5.1.1.2.5 shall apply) • UL PRB used for data traffic (3GPP TS 28.552 [6], clause 5.1.1.2.7 shall apply) • Average DL UE throughput in gNB (3GPP TS 28.552 [... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13 Use case 13: Local Indoor Positioning in RAN | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support local indoor positioning. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.1 Background and goal of the use case | Real-time indoor positioning based on cellular network has aroused attention with the development of 5G vertical industries, individuals and operators. NR positioning is introduced by 3GPP Rel.16. The location management function (LMF) resides in core network request the NG-RAN node to report positioning measurements, ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary positioning-related indicators (e.g. RSSI, labeled user location by manual or by minimal drive test, etc.) from positioning measurement report or network level measurement report or enrichment information from SMO (can acquire data from application). The data is for constructing/tra... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.3.1 Local Indoor Positioning in RAN (1) | The context of the Local Indoor Positioning in RAN (1) is captured in table 4.13.3.1-1. Table 4.13.3.1-1: Local Indoor Positioning in RAN (1) Use Case Stage Evolution / Specification <<Uses>> Related use Goal Expose positioning results to external applications. Actors and Roles Near-RT RIC, SMO, application server. Ass... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.3.2 Local Indoor Positioning in RAN (2) | The context of the Local Indoor Positioning in RAN (2) is captured in table 4.13.3.2-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 75 Table 4.13.3.2-1: Local Indoor Positioning in RAN (2) Use Case Stage Evolution / Specification <<Uses>> Related use Goal Expose positioning results to external applications. Actors and Roles... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.4 Required data | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.4.0 Non-RT RIC and Near-RT RIC required data | Multi-dimensional data are expected to be retrieved by Non-RT RIC for AI/ML model training and policies/intents generation. 1) Network level measurement report, including UE level radio channel information, mobility related metrics, e.g. RSRP, RSSI, etc. 2) Positioning measurement report, including UE level E-CID, OTDO... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.13.4.1 RAN Analytics Information | Radio performance analytics data are expected to be exposed by Near-RT RIC to application server. 1) UE positioning results, including location coordinates, coordinate system, position methods used (in the case of success indication provided), failure cause (in the case of failure indication provided), achieved locatio... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.14 Use case 14: Massive SU/MU-MIMO Grouping Optimization | Void. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15 Use case 15: O-RAN Signalling Storm Protection | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.0 Introduction | This use case provides the background, motivation, and requirements for the O-RAN Signaling Storm Protection use case, allowing protecting the mobility network against signaling storms initiated by devices. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.1 Background and goal of the use case | Society is increasingly dependent on network connectivity at any time and in any place and increasing diversity of device types ranging from complex devices such as smart phone to very simple and low-cost IoT devices are connecting to the network. The sheer number of connected devices, as well as the wide range of devi... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.2 Entities/resources involved in the use case | 1) Non-RT RIC in SMO domain: a) Maintains overall view of network wide phenomenon of signaling storms using Signaling Storm Detection rApp. The detection of distributed signaling storms that spread over many geographical locations and are more difficult to be observed locally. This overall view is broken down by locati... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.3.1 Mode 1 - Local Signaling Storm Protection Policy | The context of the Local Signaling Storm Protection Policy is captured in table 4.15.3.1-1. Table 4.15.3.1-1: Local Signaling Storm Protection Policy Use Case Stage Evolution / Specification <<Uses>> Related use Goal Detect localized signaling storms based on "default parameters" and apply policy to mitigate the attack... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.3.2 Mode 1 - Local Signaling Storm Protection Insert-Control (Optional) | The context of the Local Signaling Storm Protection Insert-Control is captured in table 4.15.3.2-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 80 Table 4.15.3.2-1: Local Signaling Storm Protection Insert-Control Use Case Stage Evolution / Specification <<Uses>> Related use Goal Detect localized signaling storms based on "d... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.3.3 Mode 2 - Distributed Signaling Storm Protection | The context of the Distributed Signaling Storm Protection is captured in table 4.15.3.3-1. Table 4.15.3.3-1: Distributed Signaling Storm Protection Use Case Stage Evolution / Specification <<Uses>> Related use Goal Detect distributed signaling using Non-RT RIC and A1 policy initiates Mode 2 handling in Near-RT RIC with... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.15.4 Required data | The measurement counters, Detection within the Near-RT RIC is based upon analyzing per UE connection establishment messages events that include the following data: 1) Basic registration event parameters: timestamp, cell ID, temporary ID (e.g. C-RNTI, 5G-GUTI). 2) RAN parameters to correlate between a UE and registratio... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.16 Use case 16: Congestion Prediction and Management | Void. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.17 Use case 17: Industrial IoT Optimization | Void. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 84 |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.18 Use case 18: BBU Pooling to achieve RAN Elasticity | Void. 4.19 Use case 19: Integrated SON Function within the O-RAN framework |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.0 Introduction | This use case provides the motivation, description, and requirements for enabling the O-RAN framework to support a minimum SON function set. This use case enables realization of SON functions in the O-RAN architectural framework to help operators address issues seen from vendor specific SON implementation in earlier ge... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.1 Background and goal of the use case. | SON (Self-Organizing Network) functionalities reduces the cost of running a mobile network by providing control on aspects of network configuration and control and thus eliminating manual configuration of network elements right from initial deployment through the network operation. SON also helps better network perform... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.2 Entities/resources involved in the use case | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.2.1 SON Inventory and Deployment Management | 1) SMO: - Support SON inventory and deployment management for Non-RT RIC(s), Near-RT RIC(s) and E2 Node(s). - Support collection of SON configurations from Non-RT RIC(s), Near-RT RIC(s) and E2 Node(s). - Support decision making on setup of the SON functions in Non-RT RIC(s), Near-RT RIC(s) and E2 Node(s). - Configure N... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.2.2 Self Configuration (PCI Conflict detection/resolution, ANR) | 1) SMO: - Configure Self configuration SON functionality (PCI Conflict detection/resolution, ANR) in Non-RT RIC, Near-RT RIC or E2 Node. - Configure/Reconfigure the respective SON related parameters and measurements in the Non-RT RIC, Near-RT RIC and E2 Node. - Support collection of measurements or notifications from t... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.2.3 Self Optimization (MLB, MRO, CCO, RO) | 1) SMO: - Configure the Self Optimization (MLB, MRO, CCO, RO) SON functionality in Non-RT RIC, Near-RT RIC or E2 Node. 2) Non-RT RIC: - Support setup of SON function and configuration of relevant SON data inputs from SMO. - Configuration and collection of cell load related information, HO related reports, CCO related m... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.3.1 SON Inventory and Deployment Management | The context of the SON Inventory and Deployment Management is captured in table 4.19.3.1-1. Table 4.19.3.1-1: SON Inventory and Deployment Management Use Case Stage Evolution / Specification <<Uses>> Related use Goal • Management of SON configurations of Non-RT RIC, Near-RT RIC and E2 Node by the SMO. • Management of d... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.3.2 Self Configuration (PCI Conflict detection/resolution, ANR) | The context of the Self Configuration is captured in table 4.19.3.2-1. Table 4.19.3.2-1: Self Configuration Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable flexible deployment of the Self configuration SON Functions like PCI Conflict Detection/Resolution, ANR by means of configuration paramete... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.3.3 Self Optimization (MLB, MRO, CCO, RO) | The context of the Self Optimization is captured in table 4.19.3.3-1. Table 4.19.3.3-1: Self Optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable flexible optimization of the Self Optimizing SON Functions like MRO, MLB, CCO and RACH by means of configuration parameter change, regulatin... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.4 Required data | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.4.1 Self Configuration (PCI Conflict detection/resolution, ANR) | 1) SMO: - Network topology, GPS coordinates of the E2 Nodes, PCI allocation range as inputs from operator. - Information on PCI confusion or PCI conflict from E2 Node via O1 interface. - Neighbor information (PCI, ECGI, PLMN, TANAC, TAC, frequency bands) based on network topology as input from operator. 2) Non-RT RIC/ ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.19.4.2 Self Optimization (MLB, MRO, CCO, RO) | 1) Non-RT RIC/ Near-RT RIC and E2 Node: - MLB - Load reports from Xn/X2/F1/E1 interface Resource Status Reporting procedures and Xn, X2 and NG mobility messages defined in 3GPP via E2 interface from E2 Node. - MLB - HO trigger control parameters available as specified in 3GPP TS 28.541 [5], clause 7.1.5. to E2 Node via... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20 Use case 20: Shared O-RU | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1 Background and goal of the use case | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.1 Common aspects & background for all Shared O-RU use cases | This use case provides the background, motivation, and requirements for the Lower Layer Split Multi Node Support, allowing to share an O-RU between multiple O-DU nodes, including single operator and multi-operator use cases. Shared O-RU use cases deliver a range of different benefits depending on specific scenarios. Sh... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.2 Resource portioning use case of Shared O-RU | This sub-use case describes the procedures of how to decide on the partitioning of a Shared O-RU. The actors are the sharing co-ordinator, SMO, and the resource partitioning rApp (Shared O-RU). The sharing co-ordinator recovers the inventory from the SMO and decides on how to partition the resources of a Shared O-RU. T... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.3 Start-up use case of a Shared O-RU | This sub-use case describes the start-up of a Shared O-RU. The actors are the SMO, the O-DUs, the Shared O-RU, and their interactions that are needed for a Shared O-RU to boot up and enter into operation. The outcome is that the Shared O-RU is operating with the necessary software version and has established network co... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.4 Configuration use case of a Shared O-RU | This sub-use case describes the configuration of a Shared O-RU. The configuration is invoked after the start-up use case has completed. Configuration can occur with different actors in hybrid vs hierarchical management mode. The common aspects of the Shared O-RU configuration are configured by the O-DU when in hierarch... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.5 Supervision use case of a Shared O-RU | This sub-use case applies to the running / operation of Shared O-RU. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 97 This sub-use case describes the supervision operations of the Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. It is invoked dur... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.6 Performance Management use case of a Shared O-RU | This sub-use case applies to the running / operation of Shared O-RU. This sub-use case describes the performance management operations of the Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. It is invoked during run-time. The actors are th... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.7 Antenna Line Device (ALD) control use case of a Shared O-RU | This sub-use case applies to the running / operation of Shared O-RU. This sub-use case describes the operation of antenna line devices with the Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are one of the O- DUs, and Shared O... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.8 Basic Resiliency use case (Primary O-DU failure) for Single MNO | This sub-use case describes system recovery from a failure (Operational State = Disabled) of the Primary O-DU#1 for a Shared O-RU for Single MNO situation. A switch of the Primary O-DU to Secondary O-DU is done. This sub-use case only applies to the hierarchical management of the O-RU. The advanced resiliency sub-use c... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.9 Antenna calibration use case of a Shared O-RU (deferred) | This sub-use case applies to the running / operation of Shared O-RU. This sub-use case describes the operation of antenna calibration using a Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are the O-DUs, and Shared O-RU. The o... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.10 Rehoming use case of a Shared O-RU (deferred) | This sub-use case describes how a Shared O-RU is moved within a network and paired with new O-DUs. This might be a virtual rehoming in a cloud native deployment, or a physical move. This is typically done with replanning of a network, or rolling a new of an existing deploying (greenfield pocket in a brownfield network)... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.11 Reset use case of a Shared O-RU | The reset of a Shared O-RU sub-use case describes the operations related to taking a Shared O-RU out of service and resetting it. There are some important aspects to reset of Shared O-RU. Only the Shared O-RU Host would have permissions to perform the reset operation. In a multiple MNO configuration, reset operations w... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.12 Advanced Resiliency Sub-use cases of a Shared O-RU | Advanced Resiliency sub-use cases describes other more intricate interactions and response for Resiliency operations. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.13 Load-balancing Sub-use case of a Shared O-RU | Load-balancing is a use case where relevant actors can reallocate Share O-RU resources based on triggers, metrics, or policies. A key actor is a policy-enforcer that makes Shared O-RU resource allocation decisions based on inputs from measurements. For example, measurements can indicate the amount of traffic on each of... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.1.14 Coordinated Reset of a Shared O-RU Sub-use case | The coordinated reset of a Shared O-RU sub-use case describes the operations related to resetting a Shared O-RU when there are multiple Shared Resource Operator (SRO) O-DUs connected to the Shared O-RU. In a multiple MNO configuration, reset operations would need to be coordinated between operators. The active Shared O... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2 Entity/resources involved in the use case | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.1 General aspects of entity/resources for Shared O-RU | The following subsections describe the entity/resources that are important and key players for each of the sub-use cases for Shared O-RU. Many of the sub-use cases will have a similar set of actors/entities/resources involved in realise the operation related to that sub-use case. In general, the identification of entit... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.2 Resource partitioning use case of Shared O-RU | 1) Sharing co-ordinator: a) Recovers the inventory of Shared O-RUs and O-DUs and determines how to partition the resources of a Shared O-RU between multiple different O-DUs. 2) SMO: a) Provides inventory of Shared O-RUs and O-DUs. b) Configures call home identities in external transport systems. 3) Shared O-RU Orchestr... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.3 Start-up use case of a Shared O-RU | 1) Shared O-RU: a) Performs call home and triggers establishment of network management session. 2) SMO: a) Recovers the software inventory of Shared O-RU and decides whether to upgrade operational software of Shared O-RU (hybrid management model). 3) O-DU: a) Recovers the software inventory of Shared O-RU and decides w... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.4 Configuration use case of a Shared O-RU | 1) SMO: a) Responsible for Shared O-RU common configuration (hybrid management model). b) Responsible for receiving notifications of modifications to Shared O-RU's configuration (multi-MNO deployment model). 2) O-DU: a) Responsible for Shared O-RU common configuration (hierarchical management model). b) Responsible for... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.5 Supervision use case of a Shared O-RU | 1) Shared O-RU: a) Responsible for operating supervision on a per O-DU basis. b) Responsible for de-activating carriers associated with O-DU if there is supervision failure by O-DU. c) Responsible for signalling alarm to subscribers if O-DU supervision is lost. 2) O-DU: a) Responsible for repeatedly resetting the Share... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.6 Performance management use case of a Shared O-RU | 1) Shared O-RU: a) Responsible for generating performance management notifications on a per partitioned carrier basis. 2) O-DU: a) Responsible for subscribing to receive performance management notifications from Shared O-RU. 3) SMO: a) The operator, or SMO, or another entity is an endpoint for the Performance Measureme... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.7 Antenna Line Device (ALD) control use case of a Shared O-RU | The following actors are involved in the ALD control use case. 1) Antenna Line Device Control rApp (for the Shared O-RU): a) Responsible for determining which O-DU is responsible for ALD Controller aspects. 2) O-DU: a) Responsible for implementing ALD Controller. 3) Shared O-RU (Hardware): a) Responsible for bridging b... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.8 Basic Resiliency use case (Primary O-DU failure) for Single MNO | The following description details the actors involved in the Resiliency Use Case of a Shared O-RU: 1) Shared O-RU: a) The Shared O-RU plays a role in helped to identify the O-DU roles during a resiliency operation. For example, then a Primary O-DU fails, the Shared O-RU can help identify what connections are still avai... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.9 Antenna calibration use case of a Shared O-RU | The following are the principal actors in the Antenna Calibration use case for a Shared O-RU. 1) Antenna calibration rApp (Shared O-RU): a) Responsible for determining which O-DU is responsible for configuring common aspects of antenna calibration. 2) O-DU: a) Responsible for supporting Shared O-RU co-ordinated calibra... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.10 Rehoming use case of a Shared O-RU | The following are the principal actors in the Rehoming Use Case: 1) Shared O-RU: a) The Shared O-RU is the entity that is being rehomed. 2) Original O-DUs: a) The original O-DU(s) are the O-DUs that the Shared O-RU were originally attached to. 3) New O-DUs attached to a) These are the new O-DU(s) that the Shared O-RU w... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.11 Reset use case of a Shared O-RU | The following are the principal actors in the [shut down/reset] of a Shared O-RU Use case. 1) Shared O-RU: a) The Shared O-RU is the entity that is being affected by the operation ([shutdown/reset]). 2) The [primary/host] O-DU: a) The [primary/host] O-DU for the Shared O-RU is the managing entity that will execute the ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.12 Advanced Resiliency Sub-use cases of a Shared O-RU | The following description details the actors involved in the Resiliency Use Case of a Shared O-RU: 1) Shared O-RU: a) The Shared O-RU plays a role in helped to identify the O-DU roles during a resiliency operation. For example, then a host (primary) O-DU fails, the Shared O-RU can help identify what connections are sti... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.13 Load-balancing Sub-use case of a Shared O-RU | The following description details the actors involved in the Resiliency Use Case of a Shared O-RU: 1) Shared O-RU: a) The Shared O-RU is actor that has its resources adjusted by the Policy enforcer. 2) O-DUs (Host/Tenant/ &other O-DUs): a) All the O-DUs connected to the Shared O-RU are actors that are relevant because ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.2.14 Coordinated Reset of a Shared O-RU Sub-use case | The following description details the actors involved in the Coordinate Reset of a Shared O-RU Use Case: 1) Shared O-RU: a) The Shared O-RU is actor that would be reset from the Host O-DU. 2) Shared O-RU Host (SOH): a) The SOH coordinates and issues the coordinate reset of a Shared O-RU. 3) Shared Resource Operators (n... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3 Solution | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.1 General aspects of solutions for all Shared O-RU use cases | The following clauses describe solutions that apply to each of the sub-Use Cases. They describe different solutions for key aspects of Shared O-RU operation, such as the Start-up, configuration, supervision, and performance management among other things. There are a few general aspects of each of these solutions that s... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.2 Resource partitioning use case of Shared O-RU | The following describes the solution for the resource partitioning sub-use case for a Shared O-RU. The context of the Resource partitioning use case of Shared O-RU is captured in table 4.20.3.2-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 108 Table 4.20.3.2-1: Resource partitioning use case of Shared O-RU Use Case Stage E... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.3 Start-up use case of Shared O-RU | The following describes the solution for the start-up sub-use case for a Shared O-RU. The context of the Shared O-RU Start-up use case is captured in table 4.20.3.3-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 109 Table 4.20.3.3-1: Shared O-RU Start-up Use case Use Case Stage Evolution / Specification <<Uses>> Related use... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.4 Configuration use case of a Shared O-RU | The following describes the solution for the configuration sub-use case for a Shared O-RU. The context of the Shared O-RU Configuration use case is captured in table 4.20.3.4-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 112 Table 4.20.3.4-1: Shared O-RU Configuration use case Use Case Stage Evolution / Specification <<Use... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.5 Supervision use case of a Shared O-RU | The following describes the solution for the supervision sub-use case for a Shared O-RU. The context of the Supervision use case of a Shared O-RU is captured in table 4.20.3.5-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 114 Table 4.20.3.5-1: Supervision use case of a Shared O-RU Use Case Stage Evolution / Specification <... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.6 Performance management use case of a Shared O-RU | The following describes the solution for the performance management sub-use case for a Shared O-RU. The context of the Performance management use case of a Shared O-RU is captured in table 4.20.3.6-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 116 Table 4.20.3.6-1: Performance management use case of a Shared O-RU Use Case ... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.7 Antenna Line device (ALD) control use case of a Shared O-RU | The following describes the solution for the ALD control sub-use case for a Shared O-RU. The context of the Antenna Line Device control use case of a Shared O-RU is captured in table 4.20.3.7-1. Table 4.20.3.7-1: Antenna Line Device control use case of a Shared O-RU Use Case Stage Evolution / Specification <<Uses>> Rel... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.8 Basic Resiliency use case (Primary O-DU failure) of a Shared O-RU | The following describes the solution for the Resiliency sub-use case for a Shared O-RU. The context of the Resiliency use case of a Shared O-RU is captured in table 4.20.3.8-1. Table 4.20.3.8-1: Resiliency use case of a Shared O-RU Use Case Stage Evolution / Specification <<Uses>> Related use Goal The goal of this sub-... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.9 Antenna calibration use case of a Shared O-RU (deferred) | The following will describe the solution for the antenna calibration sub-use case for a Shared O-RU. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.10 Rehoming use case of a Shared O-RU (deferred) | The following will describe the solution for the rehoming sub-use case for a Shared O-RU. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.11 Reset use case of a Shared O-RU | The following will describe the solution for the reset sub-use case for a Shared O-RU. The context of the Reset use case of a Shared O-RU is captured in table 4.20.3.11-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 123 Table 4.20.3.11-1: Reset use case of a Shared O-RU Use Case Stage Evolution / Specification <<Uses>> Rela... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.12 Advanced Resiliency Sub-use cases of a Shared O-RU | Advanced Resiliency sub-use cases describes other more intricate interactions and response for Resiliency operations. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.13 Load-Balancing Sub-use cases of a Shared O-RU | The Load-balancing sub-use cases describes the flow of how actors involved execute a policy to load-balance the resources of the O-DUs and Shared O-RU coordinated through a policy enforcer (actor). |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.14 Coordinated Reset of a Shared O-RU Sub-use cases | The Coordinated Reset of a Shared O-RU sub-use cases describes the flow of how actors coordinate to reset Shared O-RU. The context of the Coordinated Reset of a Shared O-RU sub-use cases is captured in table 4.20.3.14-1. Table 4.20.3.14-1: Coordinated Reset of a Shared O-RU Sub-use cases Use Case Stage Evolution / Spec... |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.15.0 Introduction | This sub-use case describes the Shared O-RU management scenarios associated with various stages in the O-DU Software update such as planning, deployment and monitoring. The detailed steps for each of these stages are described in the subsequent sections. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.15.1 Shared O-RU Management during O-DU SW Change Management Planning | The context of the Shared O-RU Management during O-DU SW Change Management Planning is captured in table 4.20.3.15.1-1. Table 4.20.3.15.1-1: Shared O-RU Management during O-DU SW Change Management Planning Use Case Stage Evolution / Specification <<Uses>> Related use Goal Management scenarios associated with Shared O-R... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.