hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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 entity/resources serve as the basis for understanding a service model. The actors are trying to accomplish a particular goal, and the actions between the actors are the services that are the basis of a service model. The service model is a basis for an information model. Sometimes, the actors in the sub-use cases perform differing operations, and sometimes there is a variable number of entities depending on the function. |
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 Orchestration rApp: a) Supports partitioning of individual carriers of a Shared O-RU between multiple different O-DUs operated by different operators. |
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 whether to upgrade operational software of Shared O-RU (hierarchical management model). ETSI ETSI TS 104 036 V12.0.0 (2025-04) 102 |
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 Shared O-RU carrier configuration. 3) Shared O-RU Orchestration rApp: a) Responsible for determining which O-DU performs Shared O-RU common configuration (hierarchical management model). b) Responsible for receiving notifications of modifications to Shared O-RU's configuration (multi-MNO deployment model). 4) Shared O-RU: a) Responsible for notifying any subscriber of its modified configuration. 5) Sharing Coordinator: a) Confirms that the Shared O-RU's configuration complies with a sharing agreement (multi-MNO deployment model). |
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 Shared O-RU's supervision timer. 3) SMO: a) Responsible for subscribing to alarm notifications (hybrid management model). b) Responsible for forwarding alarm notifications to Shared O-RU orchestration rApp. |
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 Measurement data or reports. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 103 |
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 between OFH and HDLC. 4) ALD (one or more ALD devices): a) Responsible for terminating HDLC. |
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 available. 2) O-DUs (Host/Tenant/ &other O-DUs): a) All the O-DUs connected to the Shared O-RU are actors that are relevant in some way during a resiliency operation. The Primary O-DU is main O-DU that performs the basic LCM and FCAPS functionality and ALD operations with the O-RU. In the various resiliency situations, where the Primary O-DU fails, then the other O-DU(s) connected to the Shared O-RU get involved in managing and helping the system remain operational. 3) SMO: a) The SMO makes high-level decisions related failures and the various resiliency situations. For example, in a case where a O-DU is taken out of service, it might be intentionally removed, or physically removed permanently which has attendant consequences to the Shared O-RU operation. Maintenance, software upgrade, network failure, power outages, communication links down are just some of the many possible resiliency situations. In some cases, the operator using the SMO will decide to switchover the host/primary with the other O-DU still remaining to become a new primary. |
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 calibration. 3) Shared O-RU (HW): a) Responsible for implementing co-ordinated calibration. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 104 |
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 will now be attached to. 4) SMO: a) It is also possible to rehome to a O-RU to a new management system (SMO). As such, the O-RU can be rehomed to a different SMO. |
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 command. 3) SMO: a) The operator using the SMO can issue the shut-down/reset command, and starts the use case for the operation. |
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 still available. 2) O-DUs (Host/Tenant/ &other O-DUs): a) All the O-DUs connected to the Shared O-RU are actors that are relevant in some way during a resiliency operation. The host(primary) O-DU is main O-DU that performs the basic LCM and FCAPS functionality and ALD operations with the O-RU. In the various resiliency situations, where the [hostprimary] O-DU fails, then the other O-DU(s) connected to the Shared O-RU get involved in managing and helping the system remain operational. 3) SMO: a) The SMO makes high-level decisions related failures and the various resiliency situations. For example, in a case where a O-DU is taken out of service, it might be intentionally removed, or physically removed permanently which has attendant consequences to the Shared O-RU operation. Maintenance, software upgrade, network failure, power outages, communication links down are just some of the many possible resiliency situations. In some cases, the operator using the SMO will decide to switchover the host/primary with the other O-DU still remaining to become a new primary. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 105 |
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 they perform the load balancing working with the O-RU. They can also provide measurements relevant to the load-balancing policy. 3) Policy Enforcer (SMO, RIC, etc.): a) The Policy Enforcer is an actor that executes the load-balancing policy. The policy defines the characteristics, triggers, and timing of how and when load-balancing occurs. |
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 (non-SOH SROs): a) All the O-DUs connected to the Shared O-RU are actors that are relevant because they can request a coordinate reset also for the Shared O-RU. 4) SMO/ Operator: a) The SMO operator can initiate a coordinated Reset for the Shared O-RU. 5) Partner SMO / Partner Operator: a) The SMO / partner operator can initiate a coordinated Reset for the Shared O-RU. 4.20.2.15 Management of Shared O-RU during O-DU Software Update sub-use case for Shared O-RU The following description details the actors involved in the management of Shared O-RU during the SW update of O- DU subusecase: 1) Shared O-RU: • The Shared O-RU which has its resources shared with the SW updated O-DU and other O-DUs. 2) O-DU SW Change Management rApp: • The rApp that supports SMO and Non-RT RIC in managing the SW change of the O-DU. This is an optional functionality which can alternately be implemented as an extended capability in one of the existing SMO functions. The capabilities of the O-DU SW Change Management rApp includes but not limited to the following: a) Validation of change management plan & impact assessment. b) Identification of the candidate Shared O-RU resources that can be shared based on the change plan and associated policies. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 106 c) Identification of the candidate O-DU for SW update. d) Translation of change management plan to O-DU and O-RU configurations. e) Recommendation of the configuration for Shared O-RU provisioning for m-plane setup with updated O- DU. f) Recommendation of configuration for traffic evacuation of Shared O-RU and O-DU before the O-DU SW update. g) Monitoring and management of SW Update by coordinating with other SMO functions, Shared O-RU and rApps. h) Management of fallout scenarios and recovery. 3) Shared O-RU Orchestration rApp: • Supports partitioning of individual carriers of a Shared O-RU between updated O-DU and other O-DUs. This is an optional functionality which can alternately be implemented as an extended capability in one of the existing SMO functions. 4) SMO: • Maintains inventory of Shared O-RUs and O-DUs. • Configures O-DUs and O-RUs with the support of the rApps. • Subscribe to alarms, notifications and measurements from O-DU and O-RU. • Sharing of alarm, notification and measurements from O-DU and O-RU with the rApps. 5) O-DU SW Planner: Personnel: • Prepares O-DU SW change management strategy and associated plan. Based on the strategy and plan O-DU SW Planner identifies the right software version, prepares Target O-DU identification policies (for e.g. least loaded O-DU), Shared O-RU load sharing criteria (e.g. component carrier to be allocated), identifies carrier evacuation criteria, etc. 6) Sharing Coordinator: Personnel: • Confirms that the Shared O-RU's configuration complies with a sharing policy defined as per the O-DU SW change management requirement. 7) Updated O-DU: • Responsible for load sharing the O-RU resources such as component carriers with other active O-DUs. 8) Original O-DUs: • The original O-DU(s) are the O-DUs that the Shared O-RU were originally attached to. |
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 share similar goals, assumptions, actors, and roles and are captured in table 4.20.3.1-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 107 Table 4.20.3.1-1: General aspects of solutions for all Shared O-RU use cases Use Case Stage Evolution / Specification <<Uses>> Related use Common Goals All the following sub-use cases involve either getting the Shared O-RU operational or keeping it operational. Each of the sub-use cases explore a different aspect of these two common goals. Each of the sub-use cases has a different specific goal and is trying to accomplish a particular dimension of Shared O-RU operation. This sub-use case is only applicable to the hierarchical configuration. Bringing into operation - Many of the sub-use cases have the goal to get the Shared O-RU operational and capable of supporting over the air traffic. These include the resource partitioning, start-up, configuration, and supervision sub-use cases. They are "day 0" related use cases. Maintaining Service - The other set of sub-use cases are related to maintaining service. These include the supervision, performance, and resiliency sub-use cases. These use cases relate to the continued operation of the Shared O-RU, thus "day 2" operation. Common Actors The Shared O-RU and the multiple O-DUs that the Shared O-RU is connected to are common actors that apply to all the following sub-Use Cases. The common configurations that apply to the sub-use cases many also involve the management system between two operators. Some actors can be controlled by different operators and / or provided by different solution providers. Common Assumptions For the following sub-use cases it is assumed that all relevant functions and components are instantiated. Inventory management systems identify Shared O-RU and the available O- DUs as inventory elements. For all of the sub-use cases, an O-RU resources are statically partitioned between O-DUs (static configuration). All the sub-use cases also apply a set of common configurations. These sub-use cases are intended to apply to Single Operator (SNO) and Multiple Operator (MNO) configurations. The configurations will be important to service providers, wireless operators as they roll out new networks. Those configurations can then be further broken down into either Hybrid or Hierarchical configurations. In a Hierarchical configuration the SMO performs configuration and FCAPS/LCM with the O-DU which in does that for the O-RUs. In a Hybrid configuration, the SMO can perform operations with either the O-DU and/or the O-RU. The O-DUs that share the O-RU can be from either common or different vendors. It can be envisaged that many more possible configurations or variations of those basic configurations could be supported by the following sub-use cases. For example, more than just two O-DUs. Sub-use cases present solutions that are intended to apply to all these possible configurations. Exceptions can arise from the variations of the Resiliency sub-use case. The collection of the sub-use cases either bring a Shared O-RU into operation by performing vital aspects of getting a Shared O-RU initially working; or they try to keep a Shared O-RU operational. Additionally, these sub-use cases apply to some other use cases such as class 2 BBU pooling (BBU Pooling to achieve RAN Elasticity use case), RAN Sharing, and advanced multi-vendor multi-operator Network Slicing operation (Multi-vendor Slices). Support for different configuration, resiliency operation and, supervision that apply to Shared O-RU will often be relevant to these other related Use Cases as well. These other related use cases can use the following sub-use cases as building blocks operations because they provide basic goals and objectives to getting a Shared O-RU operational and keeping it running. Thus, the sub-use cases are likely be applicable to many those use cases outside of just this Shared O-RU Use Case. |
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 Evolution / Specification <<Uses>> Related use Goal rApp has details on how a Shared O-RU's resource are to be partitioned. Actors and Roles SMO provides inventory details of Shared O-RU and O-DUs. Sharing co-ordinator recovers inventory and decides on partitioning of carriers between O-DUs. Sharing co-ordinator uses resource partitioning rApp to partition resource configuration of a Shared O-RU between O-DUs. Assumptions All relevant functions and components are instantiated. Inventory management systems identify Shared O-RU carrier capabilities and available O-DUs. Begins when Sharing co-ordinator decides to share an O-RU between multiple O-DUs. Preconditions Inventory system is up to date. Step 1 (M) Sharing co-ordinator recovers O-RU and O-DU inventory and decides on resource partitioning. Step 2 (M) Sharing co-ordinator resource partitioning rApp to partition Shared O-RU between multiple O-DUs. Step 3 (M) rApp signals O-DU identity(ies) to configuration management system. Step 4 (M) Configuration management system configures transport systems with call home identity(ies) for O-DU(s). O-RAN.WG4.MP [23], clause 6.2.5 Ends when rApp has details on how Shared O-RU's resource are to be partitioned. Exceptions None identified. Post Conditions None identified. The flow diagram of the Resource partitioning use case is given in figure 4.20.3.2-1. Figure 4.20.3.2-1: Resource partitioning Use Case |
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 Goal The Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DU(s) and, for hybrid deployments, the SMO. Actors and Roles Shared O-RU calls home and establishes network management session. SMO is responsible for software management for the Shared O-RU when operating in hybrid management mode. O-DU is responsible for software management for the Shared O-RU when operating in hierarchical management mode. Assumptions None. Begins when Shared O-RU powers on. Preconditions Transport systems (DHCP server) has been configured with call home configuration information. Step 1 (M) ESTABLISH SYNCHRONISATION: Each O-DU and Shared O-RU establish synchronisation with a timing source, for example PTP (IEEE 1588) or Sync-E. See note 1, note 2. Step 2 (M) SYNCHRONISATION STATE CHANGE NOTIFICATION: After the O-RU has a synchronisation source, all subscribed O-DU(s) are notified through a Synchronisation State Change Notification. We expect the O-RU to be in the sync state "LOCKED". The Synchronisation State Change Notification goes from Shared O-RU to all subscribed O-DU(s). It is possible that the synchronisation procedure can happen in parallel to the other steps of the start-up sub-use case. Thus, many of the other steps in this use case can happen as the synchronization procedure occurs. Even though this is shown as "step 2" this can complete after other steps. Step 3 (ALT) [Shared O-RU operated in hybrid management mode] Shared O-RU calls home and triggers establishment of network management session with SMO. O-RAN.WG4.MP [23], clause 6.3 and/or clause 6.9.2 Step 4 (ALT) [Shared O-RU operated in hierarchical management mode] Shared O-RU calls home and triggers establishment of network management session with O-DU#1. O-RAN.WG4.MP [23], clause 6.3 Step 5 (ALT) [Shared O-RU operated in hierarchical management mode] Shared O-RU calls home and triggers establishment of network management session with O-DU#2. O-RAN.WG4.MP [23], clause 6.3 Step 6 (ALT) [Shared O-RU operated in hybrid management mode] SMO recovers software inventory. O-RAN.WG4.MP [23], clause 8.4 Step 7 (O) [Shared O-RU operated in hybrid management mode and software update required] SMO triggers download of new software. O-RAN.WG4.MP [23], clause 8.5 Step 8 (O) [Shared O-RU operated in hybrid management mode and software update required] O-RU downloads software files. O-RAN.WG4.MP [23], clause 8.5 Step 9 (O) [Shared O-RU operated in hybrid management mode and software update required] SMO triggers the installation and activation of the software. O-RAN.WG4.MP [23], clauses 8.6 and 8.7 Step 10 (O) [Shared O-RU operated in hybrid management mode and software update required] SMO brings active software into operation. O-RAN.WG4.MP [23], clause 8.7 Step 11 (ALT) [Shared O-RU operated in hierarchical management mode] O-DU recovers software inventory. O-RAN.WG4.MP [23], clause 8.4 ETSI ETSI TS 104 036 V12.0.0 (2025-04) 110 Use Case Stage Evolution / Specification <<Uses>> Related use Step 12 (O) [Shared O-RU operated in hierarchical management mode and software update required] O-DU triggers download of new software. O-RAN.WG4.MP [23], clause 8.5 Step 13 (O) [Shared O-RU operated in hierarchical management mode and software update required] O-RU downloads software files. O-RAN.WG4.MP [23], clause 8.5 Step 14 (O) [Shared O-RU operated in hierarchical management mode and software update required] O-DU triggers the installation and activation of the software. O-RAN.WG4.MP [23], clause 8.6 and 8.7 Step 15 (O) [Shared O-RU operated in hierarchical management mode and software update required] O-DU brings active software into operation. O-RAN.WG4.MP [23], clause 8.7 Ends when The Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DU and, for hybrid deployments, the SMO. Exceptions None identified. Post Conditions None identified. NOTE 1: It is expected the O-RU and all O-DUs connected it would share the same synchronisation source otherwise, the O-DUs will drift in timing. NOTE 2: For more details on O-RU sync and O-RU loss of sync, see O-RAN.WG4.MP [23], clause 15.3.3. The flow diagram of the Shared O-RU Start-up use case is given in figure 4.20.3.3-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 111 Figure 4.20.3.3-1: Shared O-RU Start-up Use case |
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 <<Uses>> Related use Goal The Shared O-RU is configured to operate with multiple O-DUs. Actors and Roles SMO responsible for Shared O-RU common configuration when operating in hybrid management mode. SMO optionally can subscribe to receive notifications of modifications to Shared O-RU's configuration. When operating in hierarchical management mode, rApp is responsible for determining which O-DU is responsible for common configuration aspects. Shared O-RU responsible for role based accessccontrol based on PLMN-Id. O-DU is responsible for Shared O-RU carrier configuration and optionally, when operating in hierarchical management mode, the Shared O-RU common configuration. Sharing co-ordinator can check the Shared O-RU's committed configuration complies with any sharing agreement. Assumptions None. Begins when Shared O-RU has started up and has been configured with correct software version. Preconditions None. Step 1 (O) [Shared O-RU operated in hierarchical management mode] rApp determines which O-DU is responsible for common configuration of Shared O-RU. Step 2 (M) rApp triggers the configuration of the common aspects of the Shared O-RU. Step 3 (M) Non-RT RIC triggers the configuration of the common aspects of the Shared O-RU. Step 4 (ALT) [Hybrid or neutral host management mode] SMO uses OpenFronthaul interface to configure common aspects of Shared O-RU. O-RAN.WG4.MP [23], clause 9 Step 5 (ALT) [Hierarchical management mode] SMO uses O1 interface to configure Shared O-RU's common aspects via O-DU. Step 6 (ALT) [Hierarchical management mode] O-DU uses OpenFronthaul interface to configure common aspects of Shared O-RU. O-RAN.WG4.MP [23], clause 9 Step 7 (O) Shared O_RU calls home to tenant's O-DU (multi-operator). Step 8 (O) Shared O-RU calls home to tenant's SMO (multi-operator). Step 9 (O) rApp triggers the configuration of the carrier aspects of the Shared O-RU (non-neutral host). Step 10 (O) Non-RT RIC triggers the configuration of the carrier aspects of the Shared O-RU. Step 11 (O) SMO configures O-DU#1 and partitioned carrier information #1. Step 12 (O) O-DU#1 configures partitioned carrier information #1 on Shared O-RU non-neutral host). O-RAN.WG4.MP [23], clause 9 Step 13( O) Tenant's SMO configures O-DU#2 and partitioned carrier information #2 (multi-operator). Step 14 (M) O-DU#2 configures partitioned carrier information #2 on Shared O-RU. O-RAN.WG4.MP [23], clause 9 Step 15 (O) Shared O-RU implements role-based access control based oplmn-id#2. Step 16 (O) The Shared O-RU notifies SMO of its modified configuration. O-RAN.WG4.MP [23], clause 9.4 Step 17 (O) SMO signals Non-RT RIC information pertaining to changed configuration. Step 18 (O) Non-RT RIC signals changed configuration to Shared O-RU Orchestration rApp. Step 19 (O) Sharing co-ordinator checks that the changed configuration compliance with the sharing agreement. Step 20 (O) Host sharing co-ordinator indicates non-compliance with tenant sharing co-ordinator and remedial actions agreed (out of band exchange). ETSI ETSI TS 104 036 V12.0.0 (2025-04) 113 Use Case Stage Evolution / Specification <<Uses>> Related use Ends when The Shared O-RU is configured with common aspects and partitioned carrier#1 for O-DU#1 and partitioned carrier #2 for O-DU#2. Exceptions None identified. Post Conditions See note. NOTE: Before activation of carriers, O-RU needs to have sync state "LOCKED" with its sync source. For more details, see O-RAN.WG4.MP [23], clause 15.3.3. The flow diagram of the Shared O-RU Configuration use case is given in figure 4.20.3.4-1. Figure 4.20.3.4-1: Shared O-RU Configuration Use Case |
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 <<Uses>> Related use Goal The Shared O-RU operates watchdog timers with each of its O-DUs and ceases transmitting on a partitioned carrier associated with an O-DU if is watchdog timer to that O-DU expires. Actors and Roles Shared O-RU operates watchdog timers and deactivates any carriers associated with an expired watchdog timer. O-DU repeatedly resets the Shared O-RU's supervision timer. SMO forwards any alarms to Shared O-RU rApp. Assumptions O-DUs are operating fronthaul control and user plane for their respective partitioned carriers. SMO has subscribed to receive alarm notifications (hybrid management model). Begins when An O-DU subscribes to receive supervision notifications. Step 1 (Loop) O-DU#1 performs supervision operations. Step 2 (O) Shared O-RU detects supervision failure with O-DU#1 and ceases transmitting on partitioned carrier associated with O-DU. Step 3 (O) Shared O-RU sends alarm notification to Fault Management. Step 4 (O) Fault management sends alarm notification to Non-RT RIC. Step 5 (O) Non-RT RIC sends alarm notification to Shared o-RU Orchestration rApp. Step 6 (Loop) O-DU#2 performs supervision operations. Step 7 (O) Shared O-RU detects supervision failure with O-DU#2 and ceases transmitting on partitioned carrier associated with O-DU. Step 8 (O) Shared O-RU sends alarm notification to Fault Management. Step 9 (O) Fault management sends alarm notification to Non-RT RIC. Step 10 (O) Non-RT RIC sends alarm notification to Shared O-RU Orchestration rApp. Ends when O-DU terminates subscription to supervision notification. Exceptions None identified. Post Conditions None identified. The flow diagram of the Supervision use case of a Shared O-RU is given in figure 4.20.3.5-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 115 Figure 4.20.3.5-1: Supervision use case of a Shared O-RU |
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 Stage Evolution / Specification <<Uses>> Related use Goal Each O-DU has established subscriptions to receive performance management notifications regarding operation of the fronthaul between the O-DUs and Shared O-RU. Actors and Roles Shared O-RU generates performance management notifications on a per partitioned carrier basis. O-DU subscribes to receive performance management notifications from Shared O-RU. Assumptions O-DU has configured performance management metrics for respective partitioned carrier. Begins when Fronthaul Control and User Plane is operational between O-DU and Shared O-RU. Step 1 (M) ODU#1 subscribes to receive PM notifications from Shared O-RU. Step 2 (M) ODU#2 subscribes to receive PM notifications from Shared O-RU. Step 3 (loop) Shared O-RU sends PM Notification to O-DU#1. Step 4 (loop) Shared O-RU sends PM Notification to O-DU#2. Ends when O-DU terminates subscription to performance management notification. Exceptions None identified. Post Conditions None identified. The flow diagram of the Performance management use case of a Shared O-RU is given in figure 4.20.3.6-1. Figure 4.20.3.6-1: Performance management use case of a Shared O-RU ETSI ETSI TS 104 036 V12.0.0 (2025-04) 117 |
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>> Related use Goal The ALD connected to Shared O-RU is configured to operate with ALD Controller. Actors and Roles rApp is responsible for determining which O-DU is responsible for ALD Controller aspects. O-DU is responsible for implementing ALD Controller. O-RU is responsible for bridging between OFH and HDLC. ALD is responsible for terminating HDLC. Assumptions None. Begins when Shared O-RU has started up and has been configured with correct software version. Preconditions None. Step 1 (M) rApp determines which O-DU is responsible for performing ALD Controller functionality. Step 2 (M) rApp triggers the configuration of the ALD Controller for Shared O-RU. Step 3 (M) Non-RT RIC triggers the configuration of ALD Controller for Shared O- RU. Step 4 (M) SMO uses O1 interface to configure ALD Controller in O-DU. Step 5 (M) O-DU uses OpenFronthaul interface to configure ALD aspects of Shared O-RU. O-RAN.WG4.MP [23], clause 9 Step 6 (M) O-DU uses OpenFronthaul interface to signal ALD. O-RAN.WG4.MP [23], clause 14.4 Step 7 (M) Shared O-RU provides interworking between OFH and HDLC. O-RAN.WG4.MP [23], clause 14.4 Ends when ALD connected to Shared O-RU is configured correctly. Exceptions None identified. Post Conditions None identified. The flow diagram of the Antenna Line Device Use Case is given in figure 4.20.3.7-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 118 Figure 4.20.3.7-1: Antenna Line Device Use Case |
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-use case is to handle situations related to resiliency operations with the Shared O-RU. For example, during maintenance the host O-DU has removed from service, and how the system can keep the Shared O-RU operational in this maintenance operation. This is a service impacting use case. Actors and Roles Shared O-RU: • The associations and control of the Shared O-RU is affected O-DUs. • O-DUs (Primary/Secondary O-DUs). • All the O-DUs connected to the Shared O-RU are actors that are relevant in some way during a resiliency operation. SMO: • The SMO makes high-level decisions related failures and the various resiliency situations. Assumptions It is assumed that there is always at least one O-DU still operational with the Shared O-RU. It is assumed that the resiliency operations are intended to maintain as much operational service for the Shared O-RU as possible. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 119 Use Case Stage Evolution / Specification <<Uses>> Related use Begins when There are many possible operations that trigger the resiliency use case. In this basic Resiliency use case, only the full failure of a O-DU is considered. Other variations of failures are described in the advanced Resiliency sub-use case(s). The purpose of the Resiliency use case is to keep the Shared O-RU & O-DU system operational in the face of a failure of the active Primary O-DU. There are many possible situations where the active Primary O-DU fails or is purposefully removed from operation which are all triggers for this use case. This use case begins when the Primary O-DU encounters a failure (Operational State = disabled). Preconditions The Shared O-RU has connectivity to one or more O-DUs (and one of them is serving the primary role). The Shared O-DU has been configured originally by the active O-DU, and also carriers for the standby O-DUs. CU Plane Monitoring has been properly configured which sets up a communication monitoring interval for the interface between the Shared O-RU and O-DU. O-DUs have subscribed to alarm notifications successfully. Step 1 (M) CONFIGURE O-DU#1 FOR ACTIVE OPERATION Step 2 (M) CONFIGURE O-DU#2 FOR STANDBY OPERATION Step 3 (M) ACTIVE Primary O-DU FAILS Active Primary O-DU (the one serving as the primary role) is no longer operational. The O-DU is no longer able to provide service. The O-DU has Operational State = disabled. The Shared O-RU losses communication with the active O-DU. See note 1. M-PLANE FAILURE/REMOVAL STEPS Step 4.1 (M) M-PLANE MONITORING In the Shared O-RU, when M-Plane OAM Monitoring interval timer triggers, the Shared O-RU will detect that is has lost OAM communication to the Active O-DU. Step 4.2 (M) Carriers Associated with that M-Plane connection are disabled. Step 4.3 (M) O-RU DETECTS M-PLANE LOSS PERFORMS CALL HOME The Shared O-RU detects the M-Plane loss connectivity and tries to recover the M-Plane by performing a Call Home. Step 4.4 (M) O-RU RAISES ALARMS TO SUBSCRIBERS The Shared O-RU raises the M-Plane loss connectivity alarm to Subscriber(s). The simple case shows that the O-DU#1 and O-DU#2 are subscribers. The Shared O-RU Raises an alarm to subscribers (O-DUs) that are still active, connected and subscribed. Step 4.5 (M) ALARM FORWARDED The Shared O-RU alarm is forwarded to the managing entity, such as the SMO. It is possible that the SMO will make the decision for making the standby O-DU#2 into the active O-DU. See note 2. Step 4.6 (M) MANAGEMENT SYSTEM MAKES ANOTHER O-DU AS NEW PRIMARY O-DU The Management system, SMO makes the standby O-DU#2 now becomes the active Primary O-DU for the Shared O-RU. The message from the management system, SMO is sent to operational O-DU. See note 3. Step 4.7 (M) STANDBY O-DU BECOMES ACTIVE The formerly standby O-DU#2 now becomes the active Primary O-DU for the Shared O-RU. See note 4. Step 4.8 (M) CONFIGURATION FROM NEW ACTIVE PRIMARY O-DU The newly active O-DU can perform connectivity or configuration operations as it becomes the new active Primary O-DU. See note 5. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 120 Use Case Stage Evolution / Specification <<Uses>> Related use CU-PLANE FAILURE STEPS Step 5.1 (M) CU-PLANE MONITORING In the Shared O-RU, when CU Plane Monitoring interval timer triggers, the Shared O-RU will detect that is has lost CU logical plane is lost or payload is lost. Conditional - only carriers running, and only those carriers generate alarms. Lack of carrier traffic generates the alarms. Step 5.2 (M) O-RU RAISES ALARMS TO SUBSCRIBERS The Shared O-RU raises the M-Plane loss connectivity alarm to Subscriber(s). The simple case shows that the O-DU#1 and O-DU#2 are subscribers. Step 5.3 (M) O-RU RAISES ALARMS TO SUBSCRIBERS The Shared O-RU raises the M-Plane loss connectivity alarm to Subscriber(s). The simple case shows that the O-DU#1 and O-DU#2 are subscribers. The Shared O-RU Raises an alarm to subscribers (O-DUs) that are still active, connected and subscribed. Step 5.4 (M) ALARM FORWARDED The Shared O-RU alarm is forwarded to the managing entity, such as the SMO. It is possible that the SMO will make the decision for making the standby O-DU#2 into the active Primary O-DU. See note 6. Step 5.5 (M) MANAGEMENT SYSTEM MAKES STANDBY O-DU AS NEW PRIMARY O-DU The Management system, SMO makes the standby O-DU#2 now becomes the new Primary O-DU for the Shared O-RU. The message from the management system, SMO is sent to operational O-DU. See note 7, note 8. Step 5.6 (M) STANDBY O-DU BECOMES ACTIVE PRIMARY The formerly standby O-DU#2 now becomes the active Primary O-DU for the Shared O-RU. See note 9. Step 5.7 (M) CONFIGURATION FROM NEW ACTIVE PRIMARY O-DU The newly active O-DU can perform connectivity or configuration operations as it becomes the new active Primary O-DU. See note 10. SYNCHRONIZATION LOST Step 6.1 (M) S-PLANE MONITORING O-RU Detects loss of Synchronization. Step 6.2 O-RU RAISES ALARMS TO SUBSCRIBERS A new Primary O-DU is switched to. The Shared O-RU raises the S-Plane loss connectivity alarm to Subscriber(s). Step 6.3 O-RU RAISES ALARMS TO SUBSCRIBERS The Shared O-RU raises the M-Plane loss connectivity alarm to Subscriber(s). The Shared O-RU Raises an alarm to subscribers (O-DUs) that are still active, connected and subscribed. Ends when The Use Case ends when the standby O-DU, O-DU #2 shown in the flow diagram has taken over for the previously active O-DU, O-DU #1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 121 Use Case Stage Evolution / Specification <<Uses>> Related use Exceptions There are many possible exceptions. Some of these include: If the Shared O-RU fails during a switch over. If the Standby O-DU #2 also becomes unavailable when it is due to become active. If any event messaging for the flow is lost. If configuration was not done properly. If the Standby O-DU losses the configuration data from the configuration replica. If the Active Primary O-DU returns to service while the Standby O-DU is trying to become the active Primary O-DU. If the connectivity, or functionality of the management system (SMO) becomes unavailable. Post Conditions SUCCESSFUL POST-CONDITION - On a successful post-condition, the Shared O-RU is connected to the newly active Primary O-DU, the newly active Primary O-DU is operational and has properly synced with the O-RU. FAILURE POST-CONDITION - If one of the various exception cases occurs, there are a variety of failure post conditions. If no O-DUs are available and the O-RU is orphaned no service is available and the O-RU shall shut down operations. If misconfiguration occurs the O-RU will respond accordingly. If there are ever two active O-DUs, the Shared O-RU will operate accordingly. NOTE 1: The active O-DU can be no longer operational for a variety of reasons. (see the "Begins when" section). NOTE 2: There are many possible variations of this use case, where the SMO directly makes the decision of whether to make a standby O-DU into an active O-DU. This can happen even without a failure. These will be documented in other sub-use cases. NOTE 3: There might be multiple other O-DUs, but only one active Primary O-DU. The management system, SMO, shall know and coordinate and ensure that there is only one active O-DU. NOTE 4: There are preconditions that are relevant and necessary for this to happen. It is necessary that a call home between the O-RU and standby O-DU, and the replication of the configuration information has occurred, and that the standby O-DU has the configuration of the active O-DU. NOTE 5: The new active O-DU has control only of its carriers. It will not have control of ALD devices. NOTE 6: There are many possible variations of this use case, where the SMO directly makes the decision of whether to make a standby O-DU into an active Primary O-DU. This can happen even without a failure. These will be documented in other sub-use cases. NOTE 7: There might be multiple other O-DUs, but only one active Primary O-DU. The management system, SMO, shall know and coordinate and ensure that there is only one active Primary O-DU. NOTE 8: The SMO can make the decision to switch the active Primary O-DU for the O-RU based on other triggers as well. NOTE 9: There are preconditions that are relevant and necessary for this to happen. It is necessary that a call home between the O-RU and standby O-DU, and the replication of the configuration information has occurred, and that the standby O-DU has the configuration of the active O-DU. NOTE 10: The new active O-DU has control only of its carriers. It will not have control of ALD devices. The flow diagram of the Resiliency use case is given in figure 4.20.3.8-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 122 Figure 4.20.3.8-1: Resiliency use case |
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>> Related use Goal The goal of this sub-use case is to describe the flow related to reset of Shared O-RU for a Single MNO Operator configuration. This is a service impacting use case. Actors and Roles Shared O-RU: The Shared O-RU is a key actor. It undergoes reset in this use case. The Shared O-RU can be reset by intention / request or autonomously. O-DUs (Host/Tenant/ &other O-DUs): All the O-DUs connected to the Shared O-RU are actors are involved in the reset operation. O-DU#1 has the role of the Shared O-RU Host, it also has a role of Shared Resource Operator (SRO). O-DU#2 is only a SRO. SMO: The SMO is informed by the O-DU that O-RU has been reset or issues a reset. Assumptions It is assumed that there is always at least one O-DU still operational with the Shared O-RU. This use case describes the flow for a Single MNO Operator configuration. Begins when The reset of a Shared O-RU use case can be invoked when there is a direct request to reset the Shared O-RU or it can be reset autonomously. There are many possible reasons why a Shared O-RU can need to be intentionally reset. Maintenance, software upgrade, network failure, power outages, communication link issues are just some of the many possible situations where the active O-RU would be reset. Preconditions The Shared O-RU has connectivity to one or more O-DUs (and one of them is serving the primary role). The Shared O-DU has been configured originally by the active O-DU, and also carriers for the standby O-DUs. O-DUs have subscribed to alarm notifications successfully. Step 1 (M) [SHARED O-RU RESET FLOW] RESET REQUEST FROM SMO A reset request is communicated from the SMO to the Shared O-RU Host (O-DU #1). The reset request can be originated from the SMO for a variety of reasons. Step 2 (M) RESET REQUEST FROM O-DU The reset request is communicated onward from the Shared O-RU Host (O-DU #1) to the Shared O-RU through the open front-haul interface. Step 3 (M) RESET REPLY The Shared O-RU RPC Reply Acknowledge is sent from the Shared O-RU to the Shared O-RU Host (O-DU #1). Step 4 (M) SHARED O-RU RESET Once invoked, the Shared O-RU goes through its reset sequence to complete the reset operation. Step 5 (M) RESET RESPONSE The Shared O-RU Host (O-DU #1) informs the SMO with a reset response. Step 6 (M) [AUTONOMOUS RESET FLOW] AUTONOMOUS SHARED O-RU RESET The Shared O-RU is Autonomously Reset. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 124 Use Case Stage Evolution / Specification <<Uses>> Related use Step 7 (M) O-DU INITIAL DETECTS LOSS OF CONNECTION The Shared O-DU Host (O-DU #1) detects Loss of polling as a result of the autonomous O-RU reset. It can also detect a Call Home Signal from a Shared O-RU that just had a valid M-Plane session. Step 8 (M) O-DU DETERMINES LOSS OF CONNECTION The O-DU can deduce that O-RU has a lost connection with broken polling with the O-DU. The O-DU does not know if the O-RU was performing a reset or if there was other reason for the lost connection, for example, a broken optical fiber. The O-DU can only report lost connection to O-RU in such a case. The O-DU redetects the Shared O-RU through a Call home from the Shared O-RU. Then the Shared O-RU Start up sequence of that sub-use case happens (see the ref flow). Afterwards, the O-DU can read the reset cause from the Shared O-RU. Step 9 (M) O-DU INFORMS SMO When the O-DU #1 starts sensing Call Home signals from O-RU, O-DU can deduce that O-RU has returns to service after a reset. Afterwards, the O-DU #1 can read the restart cause. Then, the Shared O-DU host can report to SMO that O-RU is re-detected and what was the reason why the O-RU reset. Then O-DU can fill update its aggregated model with details obtained from the O-RU and populate this information to SMO. Step 14 When O-DU redetects, the SMO can clear the alarm. Ends when The Use Case ends the Shared O-RU has reset whether by reset or by autonomous reset. Exceptions There are many possible exceptions. Some of these include: The Shared O-RU was not able to successfully reset. The O-DU #1 was not able to properly detect lost connection with the Shared O-RU through loss of polling or call home signal was never sent. The O-DU #1 was not able to establish a restore connection to the Shared O-RU after reset. Post Conditions SUCCESSFUL POST-CONDITION - On a successful post-condition, the Shared O-RU is reset, and has restored connectivity to the Shared O-RU Host (O-DU #1). FAILURE POST-CONDITION - One of the failure exceptions has been encountered. The flow diagram of the Reset use case is given in figure 4.20.3.11-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 125 Figure 4.20.3.11-1: Reset use case ETSI ETSI TS 104 036 V12.0.0 (2025-04) 126 |
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 / Specification <<Uses>> Related use Goal Coordinated reset of a Shared O-RU. Actors and Roles Host SMO - The connected Host SMO to the Host O-DU. Partner SMO - The partner operator SMO. It connects to the SROs. Host O-DU - Host O-DU connected to the Shared O-RU. Operator O-DU - The SRO O-DU connected to the Shared O-RU. Shared O-RU - The target Shared O-RU that will be reset. Assumptions None Begins when There are four basic variations of a coordinated reset of a Shared O-RU. These are described in the following steps and diagrams: (1) Coordinated Reset of a Shared O-RU initiated by host personnel. (2) Coordinated Reset of a Shared O-RU initiated by SRO personnel. (3) Coordinated Reset of a Shared O-RU autonomously initiated by host O-DU. (4) Coordinated Reset of a Shared O-RU autonomously initiated by SRO O-DU. Preconditions None COORDINATED RESET OF SHARED O-RU INITIATED BY HOST PERSONNEL Step 1 (M) RESET REQUEST FROM OPERATOR The request for the coordinated reset of a Shared O-RU is initiated from the Host Operator and is received by the Host Operator SMO. Step 2 (M) HOST SMO INFORMS PARTNER SMOs The Host Operator SMO informs associated SMOs that the coordinated reset of a Shared O-RU has been initiated. Associated SMOs are other SMOs which are connected to O-DUs that are connected to the affected Shared O-RU. See note 1, note 2. Step 3.1 (ALT) RESET REQUEST FROM HOST SMO TO HOST O-DU (Hierarchal Mode) The request for the coordinated reset of the target Shared O-RU is sent from the Host Operator SMO to the Host O-DU over the O1 interface. See note 3. Step 3.2 (ALT) RESET REQUEST FROM HOST O-DU TO SHARED O-RU (Hierarchical Mode) In Hierarchical mode, the coordinated reset request of the target Shared O-RU is sent from the Host O-DU to the target Shared O-RU through the Fronthaul as an RPC request. Step 3.3 (ALT) RESET REQUEST FROM HOST SMO TO SHARED O-RU (Hybrid Mode) In Hybrid mode, the coordinated reset request of the target Shared O-RU is sent from the host SMO to target Shared O-RU as an RPC request via the M-Plane. See note 4. Step 4 (M) SHARED O-RU NOTIFIES THE HOST O-DU The affected Shared O-RU notifies the host O-DU (hierarchical mode) or Host SMO (hybrid mode). See note 5, note 6, note 7. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 127 Use Case Stage Evolution / Specification <<Uses>> Related use Step 5 (M) HOST O-DU NOTIFIES THE SMO The Host O-DU informs the Host SMO with a "Shared O-RU reset initiated" notification. Step 6 (M) SHARED O-RU NOTIFIES OTHER CONNECTED O-DUs The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. Step 7 (M) O-DU NOTIFIES ASSOCIATED SMO The O-DU (SRO) informs its associated SMO with a "Shared O-RU reset initiated" notification. Step 8 (M) SHARED O-RU NOTIFIES OTHER CONNECTED O-DUs The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. Step 9 (M) O-DU NOTIFIES ASSOCIATED SMO The O-DU (SRO) informs its associated SMO with a "Shared O-RU reset initiated" notification. Step 10 (M) SHARED O-RU NOTIFIES CONNECTED HOST O-DU The target Shared O-RU notifies the host O-DU (hierarchical mode) or Host SMO (hybrid mode) with a Reset Response. This is an RPC reply-acknowledgement. Step 11 (M) HOST O-DU NOTIFIES THE SMO The Host O-DU informs the Host operator SMO that the Shared O-RU has executed the reset with a Shared O-RU Reset Executed notification. Step 12 (M) SHARED O-RU RESET & STARTUP The Shared O-RU resets; and then initiates its start-up sequence. COORDINATED RESET OF SHARED O-RU INITIATED BY SRO PERSONNEL Step 1 (M) RESET PROCEDURE INITIATED The partner operator has identified a need to reset the target Shared O-RU and initiates a reset procedure. Step 2 (M) IDENTIFY HOST The Host for the target Shared O-RU is identified. Step 3 (M) RESET COORDINATION Coordination between the operators can occur, so that the partner operator can indicate to the host the need for a reset. Step 4 (M) RESET REQUEST FROM OPERATOR The reset request from the partner operator is sent to the partner SMO. Step 5 (M) IDENTIFY HOST The partner SMO identifies the proper host SMO for the target Shared O-RU. Step 6 (M) RESET REQUEST (COORDINATION) The partner shared operator SMO sends a request to the host SMO to initiate a coordinate reset of the target Shared O-RU. Step 7 (M) RESET RESPONSE (COORDINATION) The host SMO responds to the partner shared operator SMO regarding the initiation of a coordinate reset of the target Shared O-RU. Step 8.1 (ALT) RESET REQUEST FROM HOST SMO TO HOST O-DU (Hierarchal Mode) The request for the coordinated reset of the target Shared O-RU is sent from the Host Operator SMO to the Host O-DU over the O1 interface. See note 8. Step 8.2 (ALT) RESET REQUEST FROM HOST O-DU TO SHARED O-RU (Hierarchical Mode) In Hierarchical mode, the coordinated reset request of the target Shared O-RU is sent from the Host O-DU to the target Shared O-RU through the Fronthaul as an RPC request. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 128 Use Case Stage Evolution / Specification <<Uses>> Related use Step 8.3 (ALT) RESET REQUEST FROM HOST SMO TO SHARED O-RU (Hybrid Mode) In Hybrid mode, the coordinated reset request of the target Shared O-RU is sent from the host SMO to target Shared O-RU as an RPC request via the M-Plane. See note 9. Step 9 (M) SHARED O-RU NOTIFIES THE HOST O-DU The affected Shared O-RU notifies the host O-DU (hierarchical mode) or Host SMO (hybrid mode). See note 10, note 11, note 12. Step 10 (M) HOST O-DU NOTIFIES THE SMO The Host O-DU informs the Host SMO with a "Shared O-RU reset initiated" notification. Step 11 (M) SHARED O-RU NOTIFIES OTHER CONNECTED O-DUs The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. Step 12 (M) O-DU NOTIFIES ASSOCIATED SMO The O-DU (SRO) informs its associated SMO with a "Shared O-RU reset initiated" notification. Step 13 (M) SHARED O-RU NOTIFIES OTHER CONNECTED O-DUs The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. Step 14 (M) O-DU NOTIFIES ASSOCIATED SMO The O-DU (SRO) informs its associated SMO with a "Shared O-RU reset initiated" notification. Step 15 (M) SHARED O-RU NOTIFIES CONNECTED HOST O-DU The target Shared O-RU notifies the host O-DU (hierarchical mode) or Host SMO (hybrid mode) with a Reset Response. This is an RPC reply-acknowledgement. Step 16 (M) O-DU NOTIFIES THE SMO The Host O-DU informs the Host operator SMO that the Shared O-RU has executed the reset with a Shared O-RU Reset Executed notification. Step 17 (M) SHARED O-RU RESET & STARTUP The Shared O-RU resets; and then initiates its start-up sequence. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU Step 1 (M) RESET REQUEST FROM HOST O-DU TO SHARED O-RU The Reset request goes from the Host O-DU to Shared O-RU through the Fronthaul as an RPC request. Step 2 (M) RESET NOTIFICATION FROM HOST O-DU TO SMO The notification of a coordinated reset for a Shared O-RU goes from Host O-DU to the Host Operator SMO over the O1 interface. Step 3 (M) HOST SMO INFORMS PARTNER SMOs (COORDINATION) The Host Operator SMO informs associated SMOs that the coordinated reset of a Shared O-RU has been initiated. Associated SMOs are other SMOs which are connected to O-DUs that are connected to the affected Shared O-RU. Step 4 (M) PARNTER SMOs RESPOND TO HOST SMO (COORDINATION) The associated SMO responds to the Host Operator SMO regarding the Shared O-RU reset. Step 5 (M) SHARED O-RU NOTIFIES CONNECTED O-DUs The affected Shared O-RU notifies connected O-DUs including the host O-DU, SOH and other connected O-DUs, SROs. This is a notification message originating from the Shared O-RU and sent to all connected O-DUs. Step 6 (M) HOST O-DU NOTIFIES HOST SMO The host O-DU notifies the host SMO with a Shared O-RU Reset Initiated message that is triggered from the Reset requested by Host notification sent from the Shared O-RU. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 129 Use Case Stage Evolution / Specification <<Uses>> Related use Step 7 (M) SHARED O-RU NOTIFIES CONNECTED O-DUs The affected Shared O-RU notifies connected O-DUs including the host O-DU, SOH and other connected O-DUs, SROs. Step 8 (M) O-DU (SRO) NOTIFIES THE OPERATOR SMO The O-DU (SRO) informs its associated operator SMO that the Shared O-RU has initiated a reset. Step 9 (M) SHARED O-RU NOTIFIES CONNECTED O-DUs The affected Shared O-RU notifies connected O-DUs including the host O-DU, SOH and other connected O-DUs, SROs. Step 10 (M) O-DU (SRO) NOTIFIES THE OPERATOR SMO The O-DU (SRO) informs its associated operator SMO that the Shared O-RU has initiated a reset. Step 11 (M) SHARED O-RU NOTIFIES CONNECTED HOST O-DU The affected Shared O-RU notifies the host O-DUs with a Reset Response. This is an RPC reply-acknowledgement. Step 12 (M) HOST O-DU NOTIFIES THE HOST SMO WITH RESET EXECUTED The Host O-DU informs the host operator SMO that the Shared O-RU has executed the reset with a Shared O-RU Reset Executed notification. Step 13 (M) SHARED O-RU RESET & STARTUP The Shared O-RU resets; and then initiates its start-up sequence. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY SRO O-DU Step 1 (M) RESET REQUEST The SRO O-DU has determined that the target Shared O-RU needs to be reset. The SRO O-DU sends a reset request to its associated SMO. Step 2 (M) RESET REQUEST (COORDINATION) The partner shared operator SMO sends a request to the host SMO to initiate a coordinate reset of the target Shared O-RU. Step 3 (M) RESET RESPONSE (COORDINATION) The host SMO responds to the partner shared operator SMO regarding the initiation of a coordinate reset of the target Shared O-RU. Step 4.1 (ALT) RESET REQUEST FROM HOST SMO TO HOST O-DU (Hierarchal Mode) The request for the coordinated reset of the target Shared O-RU is sent from the Host Operator SMO to the Host O-DU over the O1 interface. See note 13. Step 4.2 (ALT) RESET REQUEST FROM HOST O-DU TO SHARED O-RU (Hierarchical Mode) In Hierarchical mode, the coordinated reset request of the target Shared O-RU is sent from the Host O-DU to the target Shared O-RU through the Fronthaul as an RPC request. Step 4.3 (ALT) RESET REQUEST FROM HOST SMO TO SHARED O-RU (Hybrid Mode) In Hybrid mode, the coordinated reset request of the target Shared O-RU is sent from the host SMO to target Shared O-RU as an RPC request via the M-Plane. See note 14. Step 5 (M) SHARED O-RU NOTIFIES THE HOST O-DU The affected Shared O-RU notifies the host O-DU (hierarchical mode) or Host SMO (hybrid mode). See note 15, note 16, note 17. Step 6 (M) HOST O-DU NOTIFIES THE SMO The Host O-DU informs the Host SMO with a "Shared O-RU reset initiated" notification. Step 7 (M) SHARED O-RU NOTIFIES OTHER CONNECTED O-DUs The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 130 Use Case Stage Evolution / Specification <<Uses>> Related use Step 8 (M) O-DU NOTIFIES ASSOCIATED SMO The O-DU (SRO) informs its associated SMO with a "Shared O-RU reset initiated" notification. Step 9 (M) SHARED O-RU NOTIFIES OTHER CONNECTED O-DUs The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. Step 10 (M) O-DU NOTIFIES ASSOCIATED SMO The O-DU (SRO) informs its associated SMO with a "Shared O-RU reset initiated" notification. Step 11 (M) SHARED O-RU NOTIFIES CONNECTED HOST O-DU The target Shared O-RU notifies the host O-DU (hierarchical mode) or Host SMO (hybrid mode) with a Reset Response. This is an RPC reply-acknowledgement. Step 12 (M) O-DU NOTIFIES THE SMO The Host O-DU informs the Host operator SMO that the Shared O-RU has executed the reset with a Shared O-RU Reset Executed notification. Step 13 (M) SHARED O-RU RESET & STARTUP The Shared O-RU resets; and then initiates its start-up sequence. Ends when The target Shared O-RU has been reset. Exceptions None identified. Post Conditions SUCCESS: The target Shared O-RU has been reset. FAILURE: The target Shared O-RU fails to be reset. NOTE 1: There are other use cases exploring operator to operator coordination and in 3GPP specifications as well. These are the Exposure of Management Services (SMO Services). NOTE 2: There might be some coordination between SMOs such that the Host SMO would not initiate a coordinated reset if the Partner SMOs objected, this would be part of the SMO decomposition work. Thus, there might be other transactions happening between the SMOs before step 4. NOTE 3: Once the coordinate reset request is issued from the Host SMO, the operation will be executed and can no longer be rejected by the system. This implies that any OSS/SMO coordination has finalized before reaching this step. NOTE 4: Step 3.3 is specifically for Hybrid mode configuration where the SMO could be a Host and thus initiate a coordinated reset of a Shared O-RU as an RPC request. NOTE 5: These set of notification messages originating from the Shared O-RU and are sent to all connected O-DUs. NOTE 6: The notification messages sent to all connected O-DUs in steps 4, 6, and 8 happen in an unspecified order. NOTE 7: In both Hybrid and Hierarchal mode, the Shared O-RU will inform all the connected O-DUs of a Reset requested by host notification. NOTE 8: Once the coordinate reset request is issued from the Host SMO, the operation will be executed and can no longer be rejected by the system. This implies that any OSS/SMO coordination has finalized before reaching this step. NOTE 9: Step 8.3 is specifically for Hybrid mode configuration where the SMO could be a Host and thus initiate a coordinated reset of a Shared O-RU as an RPC request. NOTE 10: These set of notification messages originating from the Shared O-RU and are sent to all connected O-DUs. NOTE 11: The notification messages sent to all connected O-DUs in steps 9, 11, and 13 happen in an unspecified order. NOTE 12: In both Hybrid and Hierarchal mode, the Shared O-RU will inform all the connected O-DUs of a Reset requested by host notification. NOTE 13: Once the coordinate reset request is issued from the Host SMO, the operation will be executed and can no longer be rejected by the system. This implies that any OSS/SMO coordination has finalized before reaching this step. NOTE 14: Step 4.3 is specifically for Hybrid mode configuration where the SMO could be a Host and thus initiate a coordinated reset of a Shared O-RU as an RPC request. NOTE 15: These set of notification messages originating from the Shared O-RU and are sent to all connected O-DUs. NOTE 16: The notification messages sent to all connected O-DUs in steps 5, 7, and 9 happen in an unspecified order. NOTE 17: In both Hybrid and Hierarchal mode, the Shared O-RU will inform all the connected O-DUs of a Reset requested by host notification. The flow diagram of the Coordinated Reset sub-use case 1 (Personnel triggered) is given in figure 4.20.3.14-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 131 Figure 4.20.3.14-1: Coordinated Reset sub-use case 1 (Personnel triggered) ETSI ETSI TS 104 036 V12.0.0 (2025-04) 132 The flow diagram of the Coordinated Reset sub-use case 2 (Autonomous) is given in figure 4.20.3.14-2. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 133 Figure 4.20.3.14-2: Coordinated Reset sub-use case 2 (Autonomous) ETSI ETSI TS 104 036 V12.0.0 (2025-04) 134 4.20.3.15 Management of Shared O-RU during O-DU Software Update sub-use case for Shared O-RU |
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-RU during the O-DU SW Change management planning. Actors and Roles • SMO: Maintains up-to-date information about the deployed RAN Nodes including inventory, FM and PM data that help to identify appropriate Shared O-RU resources that can be allocated for validating the O-DU SW Update. • O-DU SW Planner: Personnel who prepares deployment strategy of O-DU SW and associated plan based on the Shared O-RU resources that need to be allocated for validation. • O-DU SW Change Management rApp: The rApp that supports SMO and Non-RT RIC in managing the O-DU SW update based on the plan prepared by the Planner. • Non-RT RIC: Facilitates communication between rApps and SMO services over R1 interface. Assumptions • SW Updated O-DU shares the O-RU resources with an existing O- DU. • SW Updated O-DU and existing O-DUs address different set of component carriers and does not have common component carriers among them. • SW Updated O-DU is considered for single operator Shared O-RU scenario. Begins when O-DU SW planner identifies changes in O-DU software that need to be validated and rolled out on the RAN Node deployment with limited service disruption. Preconditions • O-DU SW planner received the O-DU software change specification (for example a document detailing the changes in the O-DU software with information about impact of change and priority). • O-DU SW planner collected the information about the RAN Nodes from the SMO Topology Exposure & InVentory Management (TE&IV) service. • O-DU SW planner collected the performance indicators and health/fault details of the RAN Nodes from the SMO. • O-DU SW planner identified the KPIs, PMJobs and scaling parameters of O-DU and Shared O-RU that need to be modified or redefined. This is to ensure that any temporary degradation during the software update does not result in false alarms or unintended actions. Step 1 (O) O-DU SW planner designs the change management plan for SW update based on the information collected from SMO services. The plan can include but not limited to: a) The version of O-DU software to be used for SW update. b) the policy to select the target O-DU (e.g. least loaded cell, particular S-NSSAI, random or specific O-DU ID. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 135 Use Case Stage Evolution / Specification <<Uses>> Related use c) evacuation policies of currently occupied component carriers associated with the Shared O-RU which need to be reallocated based on the O-DU SW update. d) the traffic-distribution or component carrier allocation policy between target O-DU and existing O-DU. e) performance and fault indicators with threshold values, monitoring schedule for the updated O-DU. f) Mitigation policy in case of a SW update failure or any disruptions. The availability of plan can be notified to the subscribed SMO services and rApps (for example O-DU SW Change Management rApp). See note. Step 2 (M) The O-DU SW planner initiates SW update of O-DU through the O-DU SW Change Management rApp with reference to the change management plan prepared and made available to the O-DU SW Change Management rApp. Step 3 (O) O-DU SW Change Management rApp collects the change management plan for O-DU software update. Step 4 (O) O-DU SW Change Management rApp validates the change management plan. Step 5 (ALT) Upon successful validation, the O-DU SW Change Management rApp prepares the provisioning configurations for the Shared O-RU and O-DU (target and existing), along with the execution steps for the software update, for the designated RAN Nodes. Step 6 (O) O-DU SW Change Management rApp notifies the O-DU SW planner about the execution steps, target RAN Nodes and configuration changes. Step 7 (O) O-DU SW planner verifies and sends approval to the O-DU SW Change Management rApp. Step 8 (O) Prepares detailed execution plan which can be notified to the subscribed SMO Services and rApps. Step 9 (ALT) If the validation of the change management plan failed, a notification is sent to the O-DU SW planner with the reason for failure. Ends when The change management plan for SW update is ready for execution. The execution can be auto triggered, or it can be manually initiated by the O-DU SW planner. Exceptions None. Post Conditions None. NOTE: It is optional to store the change management plan for SW update in SMO TE&IV. The change management plan can be stored in alternate SMO Functions registered with and authorized by SMO Data Management and exposure functions based on the implementation choice. The O-DU SW update change management planning sequence diagram is given in figure 4.20.3.15.1-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 136 Figure 4.20.3.15.1-1: O-DU SW update change management planning sequence diagram |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.15.2 Shared O-RU Management during O-DU SW Update | The context of the Shared O-RU Management during O-DU SW Update is captured in table 4.20.3.15.2-1. Table 4.20.3.15.2-1: Shared O-RU Management during O-DU SW Update Use Case Stage Evolution / Specification <<Uses>> Related use Goal Shared O-RU Management during O-DU SW update. Actors and Roles • SMO: Facilitates the execution of O-DU SW Update and associated Shared O-RU provisioning by enabling interaction across SMO services, rApps and RAN Nodes - These services include but not limited to - TE&IV, OAM Functions, O2 related functions. • O-RU Sharing co-ordinator retrieves change management plan for O-DU SW update and decides on partitioning of carriers between O-DUs. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 137 Use Case Stage Evolution / Specification <<Uses>> Related use • Sharing co-ordinator uses Shared O-RU Orchestration rApp to partition resource configuration of a Shared O-RU between O-DUs. • O-DU SW Change Management rApp: The rApp that supports SMO and Non-RT RIC in managing the O-DU SW update based on the plan prepared by the O-DU SW Planner. • Non-RT RIC: Facilitates communication between rApps and SMO services over R1 interface. • O-DU(#n): An active O-DU in the RAN being managed by the SMO. • O-DU(Updated): O-DU updated with new SW based on the change management plan. Assumptions • SW updated O-DU shares the O-RU resources with an existing O-DU. • SW updated O-DU and existing O-DUs address different set of component carriers and does not have common component carriers among them. • SW Updated O-DU and existing O-DUs do not have common cell IDs. • SW update for O-DU is considered for single operator Shared O-RU scenario. Begins when O-DU SW Change Management rApp receives confirmation about the O-DU SW update and Shared O-RU provisioning steps Preconditions O-DU Software update and Shared O-RU provisioning steps approved by the O-DU SW Planner and made available to the O-DU SW Change Management rApp. Step 0 (Ref) • O-DU SW Change Management rApp, based on the Change management plan identifies Software version to be updated and recommends (via R1 interface) to SMO the specifics of change like the software version and O-DU identifier. • For Software update of an existing O-DU, the designated O-DU (Updated) is updated using O-RAN.WG6.ORCH-USE-CASES [21], clause 3.2.4 (Steps 1 to 4). Step 1 (M) Initial Provisioning of O-DU (Updated) as per Change management plan- Refer to O-RAN.WG10.OAM-Architecture [22], clause 2.2.1 See note 1. Step 2 (M) O-DU SW Change Management rApp request (via R1 and SMO/Non-RT RIC) Shared O-RU Orchestration rApp to facilitate resource sharing between O-DU (Updated) and existing O-DUs based on the change management plan. See note 2. Step 3 (M) Shared O-RU Orchestration r-App initiates configuration of the Shared O-RU Common aspects. Step 4-6 (M) Common aspect provisioning of Shared O-RU as per clause 4.20.1.1 which include the include the security, operational, transmission, and connectivity related parameters. Step 7 (M) Based on the call home procedure, Shared O-RU establishes management session with O-DU (Updated). See note 3. Step 8-10 (O) Notification of configuration update to SMO OAM Functions and subsequently to Shared O-RU Orchestration rApp. See note 4. Step 11-13 (O) Carrier aspect provisioning to deactivate and evacuate component carriers designated for the O-DU (Updated) from the existing O-DU i.e. O-DU (#1). Step 14-15 (O) Carrier aspect provisioning to activate component carriers designated for the O-DU (Updated). Step 16-18 (O) Notification of committed Carrier aspect configuration to SMO OAM Functions. Step 19-20 (O) Notification of configuration aspect to Shared O-RU Orchestration rApp. Step 21 (O) Notification to Sharing Coordinator to validate the committed configuration. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 138 Use Case Stage Evolution / Specification <<Uses>> Related use Step 22 (O) Validation of committed configuration by Shared O-RU Orchestration rApp. Step 23 (O) Validation of committed configuration by O-DU SW Change Management rApp based on the change management plan. Step 24 (O) O-DU SW Change Management rApp coordinates with OAM functions to provision KPIs, PM Jobs or Scaling parameters used for assessing the health of the RAN Nodes so that any variations anticipated due to O-DU SW Update does not lead to false alarms or unintended actions. Ends when Committed configuration associated with the Shared O-RU is accepted by Sharing Co-Ordinator and validation of the configuration is acknowledged by the O-DU SW Change Management rApp. SMO TE&IV service is updated with inventory details about the O-DU (Updated) and Shared O-RU. Exceptions None. Post Conditions • SW updated O-DU is ready for health & sanity check and is actively handling UE sessions. NOTE 1: It is assumed that based on the O-DU (Updated) Provisioning procedure SMO TE&IV is updated with the inventory information of O-DU (Updated) as per Change management plan. NOTE 2: Refer to the Resource Partitioning use case described in clause 4.20.3.2. NOTE 3: After O-DU (Updated) deployment, before m-plane connection establishment, there is a possibility of race condition depending on when the Shared O-RU attempts call-home and the readiness of O-DU (Updated) to process the call-home requests. There are two potential scenarios and associated approaches for addressing this: • Scenario 1: O-DU (Updated) is ready for establishing m-plane connection when call home signals are still being sent by Shared O-RU: o In the O-RAN operations yang model (o-ran-operations.yang) there are two parameters that govern the call-home connection attempts: re-call-home-no-ssh-timer : A common timer used by the O-RAN equipment to trigger the repeated call-home procedure to all identified call-home servers to which the O-RAN equipment has not already an established NETCONF connection. max-call-home-attempts : counter to repeat call-home procedures. In case counter is set with value zero O-RU shall not repeat call-home procedure. In order for the deployed O-DU (Updated) to be ready to receive and process call-home requests from the Shared O-RU, the above parameters shall be optimized, so that adequate time is allocated for the O-DU (Updated) to become operational. • Scenario 2: O-DU (Updated) becomes ready after a long time duration and Shared O-RU is not performing call home procedure anymore due to expiration of the timers. o In the O-RAN operations yang model (o-ran-operations.yang) restart-call-home RPC allows any active 'call home O-RU Controller' having necessary permissions to instruct O-RU to re-activate call-home procedures. By triggering this request through an existing 'call-home O-RU controller', the O-RU will initiate call home towards all known 'call-home O-RU controllers' that do not currently have an active m-plane session. NOTE 4: The steps for hybrid scenario are not shown explicitly, but it is similar to hierarchical scenario. Refer to clause 4.20.3.4 for details. The O-DU SW update sequence diagram is given in figure 4.20.3.15.2-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 139 Figure 4.20.3.15.2-1: O-DU SW Update sequence diagram |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.3.15.3 Shared O-RU Management during O-DU SW Update Monitoring and Mitigation | The context of the Shared O-RU Management during O-DU SW Update Monitoring and Mitigation is captured in table 4.20.3.15.3-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 140 Table 4.20.3.15.3-1: Shared O-RU Management during O-DU SW Update Monitoring and Mitigation Use Case Stage Evolution / Specification <<Uses>> Related use Goal Shared O-RU Management during O-DU SW Update Monitoring and Mitigation. Actors and Roles • SMO: Facilitates the monitoring, and mitigation of O-DU SW Update and associated Shared O-RU provisioning by enabling interaction across SMO services, rApps and RAN Nodes - These services include but not limited to - TE&IV, OAM Functions, O2 related functions. • O-DU SW planner: Personnel who prepares O-DU SW change management strategy and associated plan based on the identified change in the O-DU software. • O-DU SW change management rApp: The rApp that supports SMO and Non-RT RIC in managing the O-DU SW update and associated Shared O-RU provisioning based on the plan prepared by the O-DU SW Planner and subsequent health monitoring to decide on mitigation actions. • Shared O-RU Orchestration rApp is used to rebalance the Shared O-RU resources based on the health monitoring and mitigation action selection by the O-DU SW change management rApp. • Non-RT RIC: Facilitates communication between rApps and SMO services over R1 interface. • O-DU(#n): An active O-DU in the RAN being managed by the SMO. • O-DU (Updated): A new O-DU deployed through SW change management procedure. Assumptions • Software updated O-DU shares the O-RU resources with an existing O-DU. • Software updated O-DU and existing O-DUs address different set of component carriers and does not have common component carriers among them. • Software updated O-DU and existing O-DUs do not have common cell IDs. • Software update of O-DU is considered for single operator Shared O-RU scenario. Begins when O-DU SW planner subscribes to the health monitoring events for the updated RAN Nodes, based on access granted by SMO external exposure service . OR As per the predefined plan O-DU SW change management rApp initiates health check of the SW updated O-DU. Preconditions • Successfully completed the SW update of target O-DU. • Planned Shared O-RU resources allocated to O-DU (Updated) and activated. • O-DU (Updated) sharing O-RU resources with an existing O-DU. • O-DU (Updated), existing O-DUs, Shared O-RU are ready for monitoring of KPIs and actively handling the UE sessions. Step 1 (O) O-DU SW planner subscribes to change management events from O-DU SW change management rApp via SMO/Non-RT RIC. Step 2 (M) O-DU SW change management rApp subscribes to PM/FM data from O-DU (Updated)_ and existing O-DU, i.e. O-DU (#1) through R1 interface. Step 3 (M) Non-RT RIC forwards the subscription request to OAM Function. Step 4 (M) OAM Function subscribes to the FM/PM Data Updates for O-DU (Updated) and existing O-DU, i.e O-DU (#1) via O1 interface. Step 5 (M) O-DU (Updated) subscribes to FM/PM Data Updates from Shared O-RU based on the O-DU_ID of O-DU (Updated) as the filter criteria. Step 6 (M) Notification of FM/PM data from Shared O-RU to O-DU (Updated) over OFH. Step 7 (M) Notification of FM/PM data from O-DU (Updated) to OAM Functions over O1. Step 8 (M) OAM Function forwards notification of FM/PM data received from O-DU (Updated) to Non-RT RIC through SMO internal interface. Step 9 (M) Non-RT RIC notifies O-DU SW change management rApp about FM/PM data received from O-DU (Updated). ETSI ETSI TS 104 036 V12.0.0 (2025-04) 141 Use Case Stage Evolution / Specification <<Uses>> Related use Step 10 (M) O-DU SW change management rApp evaluates FM/PM data against the change management plan. Step 11 (O) If the health and sanity of the O-DU (Updated) and Shared O-RU are not as per plan, O-DU SW change management rApp analyses mitigation action based on evaluation of the FM/PM data. Step 12 (O) If the health and sanity of the O-DU (Updated) is not as per plan O-DU SW change management rApp sends change management report consisting of sanity, health details and mitigation action(s) to O-DU SW Planner. See note 1. Step 13 (O) O-DU SW planner verifies the mitigation action and sends approval if action is within the scope of the plan. Step 14 (O) If mitigation involves provisioning of Shared O-RU, O-DU SW change management rApp recommends to Shared O-RU Orchestration rApp re-provisioning of O-RU resources based on recommended action. See note 2. Step 15 (O) Shared O-RU Orchestration rApp recommends re-configuration to OAM Functions over R1 interface. Step 16 (O) Non-RT RIC forwards Configuration request to OAM Functions. Step 17 (O) OAM Functions initiates configuration of O-DU (Updated) and partitioned carrier information. Step 18 (O) O-DU (Updated) initiates reconfiguration of partitioned carrier information on Shared O-RU. This can include required evacuation procedures if applicable. Step 19 (O) OAM Functions initiates configuration of O-DU (#n) and partitioned carrier information on the O-RU shared with O-DU (Updated). Step 20 (O) O-DU (#n) initiates reconfiguration of partitioned carrier information on Shared O-RU. Step 21 (O) O-DU (#n) sends notification about configuration update to OAM Functions over O1 interface. Step 22 (O) O-DU (Updated) sends notification about configuration update to OAM Functions over O1 interface. Step 23 (O) O-DU SW change management rApp sends revised report to O-DU SW planner. Ends when O-DU SW planner validates the change management report and certifies the O-DU SW update. SMO TE&IV service is updated with inventory details about the O-DU (Updated) and Shared O-RU. Exceptions NA. Post Conditions SW updated O-DU is functioning as per the change management plan. NOTE 1: Sanity check and Health check are assumed to be implementation specific and depends on the pre-defined change management plan for O-DU SW update. In general, the sanity check assesses whether the SW update satisfies the designated performance and connectivity objectives, while also ensuring compliance with the policies established in accordance with the plan. On the other hand, the health check examines the responsiveness and overall condition of the updated O-DU. NOTE 2: The mitigation action depends on the change management plan and specific implementation strategy. This can include but not limited to readjustment of component carriers in Shared O-RU between O-DU (Updated) and other O-DUs. The O-DU SW Update Monitoring and Mitigation sequence diagram is given in figure 4.20.3.15.3-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 142 Figure 4.20.3.15.3-1: O-DU SW Update Monitoring and Mitigation sequence diagram |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4 Required data | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.1 Required data for all Shared O-RU Use Cases | The following required data is relevant to the following sub-use cases: Resource partitioning, Start-up, Configuration, Supervision, Performance Management, ALD control, Antenna Calibration, Rehoming, and Shutdown: • Inventory system maintains inventory data for the Shared O-RUs because it needs to be able to identify Shared O-RUs. • The resource partitioning rApp maintains carrier resource information because it needs to be able to partition the Shared O-RU carrier resources between different O-DU nodes. • In hierarchical management mode, the configuration rApp maintains the active/standby state & status for O- DUs because needs to determine which O-DU is responsible for configuring the common aspects of a Shared O-RU. • The supervision needs to include the O-DU identity because the Shared O-RU needs to be able to support supervision on a per O-DU basis. • Alarm data needs to be kept at the Shared O-RU because the Shared O-RU needs to be able to terminate transmissions associated with an O-DU when it loses supervision with that O-DU and to continue to operate with other O-DUs. There will be a history of Alarm data. • Shared O-RU measurement counters and KPIs (as defined by O-RAN.WG4.MP [23]) shall be available on a per O-DU basis. • O-DU needs to include its O-DU identity to enable supervision operation on a per O-DU basis. • The ALD control rApp maintains data to keep track which O-DU is responsible for ALD controller functionality because it needs to be able to select which O-DU is responsible for ALD controller functionality. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 143 |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.2 Required data for single MNO Configurations | The following data applies for single operator configurations when used by the other Shared O-RU sub-use cases: • Non-RT RIC needs to be able to partition the Shared O-RU carriers between O-DU nodes operated by the same MNO. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.3 Required data for multi-MNO Configurations | The following data applies for multi-operator configurations when used by the other Shared O-RU sub-use cases: • The resource partitioning rApp needs to be able to partition the Shared O-RU carrier resources between different O-DU nodes of different MNOs. • Shared O-RU needs to be able to associate management accounts with an MNO. • The Shared O-RU needs to be able to implement role-based access control on a per-MNO basis. • The Shared O-RU needs to associate carrier resources with MNOs. • Measurement counters and KPIs (as defined by O-RAN WG4) need to be available on a per MNO basis. • Tenant SMO needs to be able to support common Shared O-RU configuration defined by host operator. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.20.4.4 Required data for Resiliency Use Cases | The following data is used by the resiliency use case: • The supervision needs to include the O-DU identity because the Shared O-RU needs to be able to support supervision on a per O-DU basis. • Alarm data needs to be kept at the Shared O-RU because the Shared O-RU needs to be able to terminate transmissions associated with an O-DU when it loses supervision with that O-DU and to continue to operate with other O-DUs. There will be a history of Alarm data. • The configuration data from the active Primary O-DU is passed to the standby O-DU. • The configuration information of carriers of the standby O-DU are configured for the O-RU. • The management system has the state & status data regarding which O-DU is and shall be active. • The management system has the state & status data regarding which O-DUs are and shall be standby. • The management system has the alarm history and alarm information for the Shared O-RU. NOTE: There are many different situations and variations of the Resiliency sub-use cases. Some of them need not require all the above data. 4.20.4.5 Required data for Shared O-RU Management during O-DU SW Update sub- use case for Shared O-RU The following data is used by SW update of O-DU and associated Shared O-RU provisioning: • The configuration data for provisioning the SW updated O-DU based on the change management plan for SW update. • The configuration information of carriers of the SW updated O-DU configured on the Shared O-RU. • The management system has state and status details of O-DUs to identify the right candidate to be used for SW update. • The management system has state and status details of SW Updated O-DU to verify the status and health of the SW Update. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 144 • The management system has the alarm history and alarm data of the Shared O-RU to verify functionality and sanity of the SW updated O-DU. • Non-RT RIC needs to be able to partition the Shared O-RU carriers between SW updated O-DU and other O-DU nodes operated by the same MNO. • Alarm data and Performance Data needs to be kept at Shared O-RU to verify the sanity of O-DU SW update. • O-DU SW change management rApp maintains the change management plan data for O-DU SW update to initiate & supervise the SW update process and to validate the sanity of the deployment against the plan. • Historical configuration and Software details of the O-DU is maintained for SW update so that the mitigation step of the SW update can bring the O-DU to the situation before SW update. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21 Use case 21: Energy Saving | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.0 Introduction | This section provides the motivations, descriptions, and proposed solutions for different Energy Efficiency and Energy Saving features (sub-use cases). While there are energy savings by improving base station hardware efficiency and by the evolution of radio access technologies, the EE/ES use case primarily addresses enhancements in software efficiency and optimized configuration/control of various elements and functions, which are often AI/ML based. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.1 Background and goal of the use case | The RAN is responsible for a major part of the Energy Consumption (EC) of a mobile network, and the O-RU accounts for the largest part of the energy consumption of the RAN. The rarefication of fossil fuel-based energy resources and the urgent need to reduce CO2 emissions make the EC a strategic topic for network operators, in addition of being a significant component of the operators' OPEX. EC can be reduced by improving the Energy Efficiency (EE) of the network, and by introducing different Energy Saving (ES) mechanisms. Several ES mechanisms are related to switching off certain components in the network and differ from one another by their scope, time scale and network area. Applicable ES methods are for instance strongly load dependent. Optimization efficiency might be further improved by AI/ML based configuration thereof. RAN functions related to network energy saving solutions have been studied in 3GPP RAN3 in Rel.17 as part of the Study on Enhancement for Data Collection for NR and EN-DC. The outcome is documented in 3GPP TR 37.817 [i.2]. 3GPP RAN2 and RAN3 might specify enhancements for the Minimization of Drive Tests (MDT) procedures and/or signaling procedures that rely on Xn signaling in Rel.18. While 3GPP RAN WGs work on solutions with ML model inference within the gNB, O-RAN specifies solutions that benefit from ML model inference in the Near-RT or Non-RT RIC (e.g. optimizing the network in larger service areas). For EE related network management, use cases, requirements and solutions are specified in 3GPP TS 28.310 [3]. Furthermore, EC measurements and KPIs for 5G networks, Network Functions, NG-RAN and gNBs such as Energy Efficiency and Energy Consumption KPIs and performance measurements are specified in 3GPP TS 28.554 [7]. Centralized and Distributed ES Management Functions are specified in 3GPP TS 28.541 [5]. EE can be considered for the whole network (i.e. end-to-end), for a sub-network or per single network element. Within a network element it could be applicable per specific radio resource management mechanism or per radio or transport network link. Network wise EE is defined as the ratio between the data volume delivered in the network and the network EC observed during the time-period required to deliver such data, with possible adaptations to account for different deployment scenarios and load situations (ETS ES 203 228 [i.5], 3GPP TR 38.913 [i.4]). 3GPP has launched a study item within Rel-18 (RP-213554: "Study on network energy saving for NR") that will include among others, an evaluation methodology and KPIs for EC and ES gains and their impact on network and UE performance and EE. To assess EE and ES associated to radio resource management mechanisms and links, appropriate KPIs are necessary. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 145 In a timescale of minutes, hours and above, and when the cell load is low, ES can be achieved by switching off one or more carriers or the cell. In a timescale from seconds to minutes, ES can be achieved by switching off RF channels (including possibly antennas) of a Massive MIMO system. Tx and Rx parts might be switched independently. In a very short timescale corresponding to a symbol, subframe or frame, Advanced Sleep Modes (ASM) can be considered. RF channel on/off switching can be used at medium load and ASM might be usable even at high load. Lastly, ES solutions can be applied to the O-Cloud, namely to the O-CU and O-DU, and can cover mechanisms such as scale in/out processes, workload placement or hardware processors' sleep modes etc. AI/ML is useful for all the above mechanisms with the important role of determining the switch off/on time that maximizes ES gain. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.2 Entities/resources involved in the use case | Editor's note: If possible, single common description for all sub-use cases. Deployment option 1: AI/ML inference host located in the Non-RT RIC 1) Non-RT RIC: a) Collect configurations, performance indicators and measurement reports (e.g. cell load related information and traffic information, EE/EC measurement reports, geolocation information) from SMO, E2 Nodes and O-RUs (forwarded by SMO), for the purpose of training and inference of AI/ML models that assist in the EE/ES functions. b) Trigger EE/ES AI/ML model training/retraining. c) Deploy or update and configure EE/ES AI/ML models in Non-RT RIC. d) Analyse the received data from SMO, E2 Nodes and O-RUs to determine EE/ES optimization (e.g. if carriers or cells need to be switched off/on) using AI/ML models and signal updated configuration for EE/ES optimization to E2 Nodes via R1/O1 and optionally O-RU via R1/Open FH M-Plane. 2) E2 Node: a) Report cell configuration, performance indicators and measurement reports (e.g. cell load related information and traffic information, EE/EC measurement reports) to SMO via O1 interface. b) Perform actions required for EE/ES optimization. 3) O-RU Node: a) Report EC and EE related information via Open FH M-Plane interface to O-DU or alternatively to SMO directly. b) Support actions required to perform EE/ES optimization. Deployment option 2: AI/ML inference host located in the Near-RT RIC 1) Non-RT RIC: a) Collect configurations, performance indicators and measurement reports (e.g. cell load related information and traffic information, EE/EC measurement reports, geolocation information) from SMO, E2 nodes and O-RUs (forwarded by SMO), for the purpose of training AI/ML models that assist in the EE/ES functions. b) Trigger EE/ES AI/ML model training/retraining. c) Deploy or update EE/ES AI/ML models in NearRT RIC. d) Configure EE/ES AI/ML models to Near-RT RIC via R1/O1 interface. e) Provide optimization trigger, optimization targets and intent based policies (e.g. set energy target to 50 % of peak power consumption) to Near-RT RIC via R1/O1 or A1 interface. 2) Near-RT RIC: a) Collect configurations, performance indicators and measurement reports (e.g. cell load related information and traffic information, EE/EC measurement reports) from E2 nodes. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 146 b) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. c) Receive EE/ES related configuration management via O1 interface and/or policies via A1 interface for consideration during optimization. d) Analyse the received data from E2 Nodes and perform AI/ML model inference to determine EE/ES. optimization (e.g. if carriers or cells need to be switched off/on) considering the optimization targets/policies. e) Provide policies or required information via E2 interface to trigger actions for EE/ES optimization. 3) E2 Node: a) Report cell configuration, performance indicators and measurements reports (e.g. cell load related information and traffic information, EE/EC measurement reports) per cell/carrier via O1 interface to SMO and via E2 interface to Near-RT RIC. b) Perform actions required for EE/ES optimization. 4) O-RU Node: a) Report EC and EE related information via Open FH M-Plane interface to O-DU or alternatively to SMO directly. b) Support actions required to perform EE/ES optimization. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.3.0 Introduction | Editor's note: Sub-use case specific solutions with detailed descriptions in fully separate sections. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.3.1 Carrier and Cell switch off/on | Mobile networks often utilize multiple frequency layers (carriers) to cover the same service area. At low load, ES can be achieved by switching off one or more carriers or entire cells without impairing the network performance. The switch off/on decision can be made by an AI/ML model within the inference host, deployed at the Non-RT RIC (deployment option 1) or at the Near-RT RIC (deployment option 2), as described above. Among others, the AI/ML models' functionality can include prediction of future traffic, user mobility, and resource usage and can also predict expected energy efficiency enhancements, resource usage, and network performance for different ES optimization states. Before switching off/on carrier(s) or cell(s), the E2 Node can perform some preparation actions for off switching (e.g. to enable, disable, modify Carrier Aggregation and/or Dual Connectivity, to trigger HO traffic and UEs from cells/carriers to other cells or carriers, informing neighboring nodes via X2/Xn interface etc.) as well as for on switching (e.g. cell probing, informing neighboring nodes via X2/Xn interface, etc.). Deployment option 1: AI/ML inference host located in the Non-RT RIC. The context of Carrier and cell switch off/on: AI/ML inference via Non-RT RIC is captured in table 4.21.3.1-1. Table 4.21.3.1-1: Carrier and cell switch off/on: AI/ML inference via Non-RT RIC Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable Carrier and Cell switch off/on Energy Saving functions in the Network by means of configuration parameter change and Actions controlled by Non-RT RIC and allow for AI/ML-based solutions. Actors and Roles Non-RT RIC acting as Energy Saving decision making function. E2 Node and O-RU acting as configuration enforcement function. Assumptions O1 interface connectivity is established towards E2 Nodes, Non-RT RIC and SMO. Open FH M-Plane interface is established between E2 node and O-RU and/or SMO and O-RU directly. Network is operational. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 147 Use Case Stage Evolution / Specification <<Uses>> Related use Pre-conditions Operator has set the targets for Energy Saving functions in the Non-RT RIC. Begins when Operator enables the optimization functions for carrier and cell switch off/on Energy Saving functions and E2 Node and O-RU become operational. Step 1 (M) SMO initiates specific measurement data collection request towards E2 Node and O-RU for AI/ML model training and inference. Step 2 (M) E2 Node and O-RU send the configured measurement data to SMO periodically or event based. Step 3 (M) Non-RT RIC retrieves the collected measurement data for processing. Step 4 (M) Non-RT RIC trains the AI/ML models with the collected data. Trained AI/ML models are deployed, configured, and activated. Non-RT RIC constantly monitors: (i) performance and energy consumption of the E2 Node(s). (ii) energy consumption of O-RU(s). Step 5 (M) Based on the AI/ML inference the Non-RT RIC can request the SMO to configure E2 Node to prepare and execute cell or carrier switch off/on. Step 6 (M) SMO instructs E2 node via O1 interface to perform the received request(s) from the Non-RT RIC. O-RU is informed about the updated O-RU configuration via Open FH M-Plane interface either by E2 Node, or by SMO directly. E2 Node / O-RU will notify SMO once cell or carrier switch off/on is completed. Step 7 (M) Non-RT RIC continuously analyses performance of AI/ML model. If energy saving objectives are not achieved, it can decide to initiate fallback mechanism, and/or AI/ML model update or retraining. Ends when E2 Node becomes non-operational or when the operator disables the optimization functions for Energy Saving. Exceptions None. Post Conditions Non-RT RIC continues close loop monitoring of Energy Saving function at E2 Node and O-RU. E2 Node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). The flow diagram of the Carrier and cell switch off/on: AI/ML inference via Non-RT RIC is given in figure 4.21.3.1-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 148 Figure 4.21.3.1-1: Carrier and cell switch off/on flow diagram: AI/ML inference via Non-RT RIC Deployment option 2: AI/ML inference via Near-RT RIC The context of Carrier and cell switch off/on: AI/ML inference via Near-RT RIC is captured in table 4.21.3.1-2. Table 4.21.3.1-2: Carrier and cell switch off/on: AI/ML inference via Near-RT RIC Use Case Stage Evolution / Specification <<Uses>> Related use Goal Enable Carrier and Cell switch off/on Energy Saving functions in the Network by means of configuration parameter change and Actions controlled by Near-RT RIC and allow for AI/ML-based solutions. Actors and Roles Near-RT RIC acting as Energy Savings decision making function. E2 Node and O-RU acting as configuration enforcement function. Assumptions O1 interface connecting the SMO with E2 Node, Near-RT RIC and Non-RT RIC is established. E2 interface connectivity is established between E2 Node and Near-RT RIC. A1 interface is established between Non-RT RIC and Near-RT RIC. Open FH M-Plane interface is established between E2 node and O-RU. Network is operational. Pre-conditions Operator has set the targets for Energy Saving function in the Non-RT RIC. Begins when Operator enables the optimization functions for carrier and cell switch off/on Energy Saving functions and E2 Node and O-RU become operational. Step 1 (M) SMO initiates specific measurement data collection request towards E2 Node and O-RU for AI/ML model training. Step 2 (M) E2 Node and O-RU send the configured measurement data to SMO periodically or event based. Step 3 (M) Non-RT RIC retrieves the collected measurement data for processing ETSI ETSI TS 104 036 V12.0.0 (2025-04) 149 Use Case Stage Evolution / Specification <<Uses>> Related use Step 4 (M) Non-RT RIC trains the AI/ML models with the collected data. Trained AI/ML models are deployed, configured, and activated in the Near-RT RIC. Step 5 (M) SMO can trigger EE/ES optimization and might provide policies guiding the Near-RT RIC EE/ES function via O1 and/or A1 interface. Step 6 (M) Near-RT RIC constantly monitors: (i) performance and energy consumption of the E2 Node(s). (ii) energy consumption of O-RU(s). Based on the AI/ML inference, considering optimization policies, the Near-RT RIC can request the E2 Node to prepare and execute cell or carrier switch off/on. E2 Node can request O-RU Node to prepare and execute cell or carrier switch off/on. E2 Node will notify Near-RT RIC once cell or carrier switch off/on is completed. Ends when E2 Node becomes non-Operational or when the operator disables the optimization functions for Energy Saving. Exceptions None. Post Conditions Near-RT RIC continues close loop monitoring of Energy Saving function at E2 Node and O-RU. E2 Node and O-RU operate using the newly deployed parameters/models and state (off/on). The flow diagram of the Carrier and cell switch off/on: AI/ML inference via Near-RT RIC is given in figure 4.21.3.1-2. Figure 4.21.3.1-2: Carrier and cell switch off/on flow diagram: AI/ML inference via Near-RT RIC |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.21.4 Required data | Input Data 1) E2 Node to SMO and Near-RT RIC (when Near-RT RIC serves as inference host): ETSI ETSI TS 104 036 V12.0.0 (2025-04) 150 • EE/EC measurement reports. • Load statistics per cell and per carrier, such as number of active users, average number of RRC connections, average number of scheduled active users per TTI, PRB utilization, DL/UL throughput. • UE mobility information including cell or beam level measurements (e.g. UE RSRP, RSRQ, SINR). • Latency statistics per cell (if URLLC slices are involved, latency is used in the EE definition, 3GPP TS 28.554 [7] shall apply). 2) O-RU to E2 Node (O-DU) or to SMO directly via Open FH M-Plane: • Power consumption metrics: Mean total/per carrier power consumption, mean total/per carrier transmit power (Site/O-RU input power are needed for certain EE KPIs). Output Data 1) Non-RT RIC via SMO to E2 Node or Near-RT RIC to E2 Node (when Near-RT RIC serves as inference host): • Carrier(s) and cell(s) recommended to be switched off/on. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22 Use case 22: MU-MIMO Optimizaiton | This use case provides the motivation, description, and requirements for a near real time MU-MIMO optimization control loop deployment. Deploying MU-MIMO application in the Near-RT RIC enables new solutions that can optimize UE and cell level performance in certain deployments by e.g. deriving channel estimation/prediction and UEs selections with their associated precoding coefficients, resulting in increased per UE and overall cell throughput. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.1 Background and goal of the use case | MU-MIMO is one of the key technologies available for increasing UE and cell capacities using existing time/frequency resources. The use of multiple antennas enables the pointing of beams to multiple UEs with each beam spatially filtering the interference from the other beams. This has the potential to provide higher total cell capacity when there are multiple eNB/gNB antennas. In a commercial deployment, some subscribers can be stationary, some can be pedestrian moving slowly, and some can be moving at high speed. Traditional MU-MIMO solutions are very sensitive to subscriber's mobility and as a result the capacity gains achieved with multiple antennas is limited. New beamforming solutions are emerging that support MU-MIMO with less time sensitivity allowing them to be implemented in the Near-RT RIC. These solutions are applicable to both downlink and uplink data channels and to TDD as well as FDD and can provide high user and cell performance for subscribers moving within a wide range of speeds. The objective of this use case is to allow the operator to improve user throughput and overall cell capacity by deploying an application in the Near-RT RIC that can use information collected from the E2 Nodes to calculate and send to the E2 Nodes user selections and applicable precoding coefficients in a near real time loop. This use case will also open the door for future expansion of the MU-MIMO to supporting CoMP covering both ICIC and joint multi sites MU-MIMO. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.2 Entities/resources involved in the use case | 1) Near-RT RIC: a) Retrieve cell configuration and UE states from E2 nodes. b) Send configurations for DL channel estimation reporting and UL SRS and DMRS to the E2 nodes. c) Retrieve DL/UL traffic, and DL/UL channel quality information from E2 nodes. d) Use the retrieved information to select the UEs to be spatially multiplexed per frequency and time resources and for each selection calculate the relevant MCS and precoder coefficients for optimal UE and cell throughput. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 151 e) Send the recommended UE selections with their resource assignments, MCS, and precoding coefficients to the E2 nodes. 2) E2 nodes: a) Collect and report to Near-RT RIC information related to cell configuration, UE states, DL/UL traffic, and DL/UL channel quality. b) Apply the configurations received from the Near-RT RIC for DL channel estimation reporting and UL SRS transmissions. c) Apply MU-MIMO parameters following Near-RT RIC recommendations (while handling time critical events separately). |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.3 Solutions | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.3.1 MU-MIMO Optimization | The context of MU-MIMO Optimization is captured in table 4.22.3.1-1. Table 4.22.3.1-1: MU-MIMO Optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal MU-MIMO optimization using Near-RT RIC control loop. Actors and Roles Near-RT RIC: configures E2 nodes' measurements, collects data from E2 Nodes, performs MU-MIMO optimization function, and sends MIMO recommendations to E2 nodes. E2 Nodes: Report measurements to Near-RT RIC and execute MU-MIMO recommendations. Assumptions E2 connectivity is established between Near-RT RIC and E2 Nodes. Network is operational. Pre conditions All relevant functions and components are instantiated. MU-MIMO Optimization xApp is deployed with initial configuration. All relevant subscriptions established on E2 interface. Begins when Preconditions are met. Step 1 (M) Near-RT RIC initiates data collection from E2 Nodes (cell configuration, UE states, RRC connection, UL/DL traffic and channel information). Step 2 (M) E2 Nodes send cell configuration, UE states, and RRC connection information to Near-RT RIC. Step 3 (M) E2 nodes send UL/DL traffic and channel information to Near-RT RIC. Step 4 (O) Near-RT RIC sends DL channel estimation reporting and UL SRS and DMRS configuration to E2 Nodes. Step 5 (M) E2 nodes continuously send UL/DL traffic and channel information to Near-RT RIC. Step 6 (M) E2 nodes send updated UE states and RRC connections information to Near-RT RIC. Step 7 (M) Near-RT RIC uses the collected information to estimate channels and select UE groupings per ranges of frequency and time resources. Step 8 (M) Near-RT RIC calculates MCS and precoding coefficients for each selection of UEs. Step 9 (M) Near-RT RIC sends optimized MU-MIMO parameters (UE selections with their resource assignments, MCS, and precoding coefficients) to E2 Nodes. Step 10 (M) E2 nodes schedule MU-MIMO transmissions using the parameters received from the Near-RT RIC. Step 11 (O) Near-RT RIC sends updated DL channel estimation reporting and UL SRS and DMRS configuration to E2 Nodes. Ends when Operator uninstalls MU-MIMO Optimization xApp. Exceptions None identified. Post Conditions The E2 Nodes operate using the newly received parameters. The flow diagram of MU-MIMO Optimization is given in figure 4.22.3.1-1. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 152 Figure 4.22.3.1-1: MU-MIMO Optimization flow |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.22.4 Required data | The Near-RT RIC requires different types of data from the E2 Nodes as summarized below with examples: 1) Cell configuration information (e.g. frequency and BW, FDD/TDD, SCS, UL-DL configuration) 2) List of connected UEs 3) UE connection updates (setup, release, handover) 4) UE RRC state changes (connected, inactive, idle) 5) UL channel information (e.g. SRS, ACK/NACK counts) 6) DL channel information (e.g. CQI, RI, PMI, ACK/NACK counts) 7) DL PDCP and RLC buffer status and UL BSR |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.23 Use case 23: Sharing Non-RT RIC Data with the Core | Void. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 153 |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24 Use case 24: Industrial vision SLA Assurance | |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support industrial vision Service Level Agreement (SLA) Assurance. Moreover, some high-level description and requirements over Non-RT RIC, A1 and E2 interfaces are introduced. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.1 Background and goal of the use case | Industrial vision is an image recognition technology used for work piece inspecting, processing and assembling automation, as well as the monitoring and controlling of production process by replacing human eyes with cameras for various measurements and judgments. The main feature of industrial vision system is that it needs to collect the images of the products to be tested or processed in the area with dense production lines, and then transmit the images to the vision server for detection and feed back the results. Because the industrial vision system shall accommodate to the production speed of the production line, there are strict delay and reliability requirements for visual acquisition, transmission, judgment and execution. For example, a production line which processes 8 000 work pieces per hour has an operation interval of 450 ms for each product in the production line. Considering the image recognition, results execution time and the mechanical execution time, the two-way data transmission delay left for the transmission network is even less. When 5G is applied in the industrial vision business scenario, the main challenge is the assurance of image data transmission delay and reliability of 5G wireless network in an ultra-dense networking environment. 5G pre-scheduling technology is introduced to reduce the transmission delay and improve the transmission reliability. However, the traditional static pre-scheduling mechanism could not adapts to changing production environments. It always allocates fixed air interface resource according to the static configuration, regardless of the actual data arrival, resulting mis-alignment of resource allocation and uplink transmission needs, causing increased and unstable delay, waste of PRB resources and significant decline in the actual bearable traffic of the cell. Therefore, dynamic pre-scheduling, which allocates uplink resources according to actual work piece arrival time, is deemed to be a more efficient way to enable industrial vision deployment in production line. In O-RAN, RIC can be used to dynamically optimize the pre-scheduling parameters, so that accurate matching between uplink data arrival and uplink transmission resource allocation could be achieved. This helps to reduce uplink transmission delay and improve the resource efficiency. With Enrichment Information from Application Server/Manufacturing Execution System (MES), e.g. Production-line and industrial camera configuration and image transmission delay related data, Near-RT RIC can calculate and iteratively update pre-scheduling parameter (e.g. pre-scheduling data size, pre-scheduling period and pre-scheduling start time), and send those parameters to E2 Nodes vis E2 interface. Note that the configured parameters mentioned above only serve as scheduling recommendations to E2 Nodes. Actual PRB scheduling depends on many other factors not captured by this use case. E2 Node might for instance supersede Near-RT RIC's recommendation in case high priority delay critical data needs to be scheduled. One Example method to transmit Non-RAN Application Server/MES data into Non-RT RIC is through SMO External Interface. Application Server/MES is registered as SMO External System, which serves as a data source outside the O-RAN Domian that provides data to the SMO. By leveraging SMO External Interface (the interface between the SMO and an SMO External System), Production-line and industrial camera configuration and image transmission delay related data is transmitted to SMO as Enrichment Information, which is consumed by Non-RT RIC and bypassed to Near-RT RIC through A1. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Support communication of non-RAN data to enrich control functions in Near-RT RIC (enrichment information). 2) Near-RT RIC: a) Support communication of pre-scheduling configuration parameters to E2 Node. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 154 3) E2 Node: a) Support pre-scheduling parameters configuration over E2 interface. b) Report necessary performance, configuration, and other data for performing pre-scheduling parameter configuration in the Near-RT RIC over E2 interface. 4) Application Server/ MES: a) Support communication of non-RAN data about production line information and data transmission information to Non-RT RIC as enrichment information. |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.3 Solutions | The context of Industrial vision assurance is captured in table 4.24.3-1. Table 4.24.3-1: Industrial vision assurance Use Case Stage Evolution / Specification <<Uses>> Related use Goal Meeting industrial vision service SLA requirement via dynamic pre-scheduling parameter configuration. Actors and Roles Non-RT RIC, Near-RT RIC, E2 Node, Application Server/ MES Assumptions All relevant functions and components are instantiated. A1, E2 interface connectivity is established. Pre conditions Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them. E2 interface is established between Near-RT RIC and E2 Node. Begins when Production line is started. Periodical industrial vision service is started. Step 1 (M) MES sends the Production-line and industrial camera configuration related data to the Non-RT RIC. Step 2 (M) The Non-RT RIC sends the enrichment information to the Near-RT RIC over the A1 interface. Step 3 (M) Based on the received production-line and industrial camera configuration related enrichment information from the Non-RT RIC over the A1 interface, the Near-RT RIC sends initial time-domain pre-scheduling parameters, which includes pre-scheduling data size, pre-scheduling period and pre-scheduling start time, to the E2 Node. Step 4 (M) Industrial vision application server sends the image data transmission delay related enrichment data to the Non-RT RIC. Step 5 (M) The E2 node and the Non-RT RIC sends service data transmission information, which includes relevant measurement (e.g. pre-scheduling time-domain resource utilization which is the ratio of the time-domain resource of the data to be scheduled to the total pre-scheduled time-domain resource, and the image data transmission delay related enrichment information) to the Near-RT RIC. Near-RT RIC receives the service data transmission information and then based on those information, evaluates the performance of the pre-scheduling and iteratively updates pre-scheduling start time. Then the Near-RT RIC sends the updated pre-scheduling start time to the E2 Node over E2 interface. Step 6 (M) Based on the pre-scheduling data size, pre-scheduling period and pre-scheduling start time received from the Near-RT RIC, E2 Node pre-schedules the time-domain resource for the terminal device. Repeat steps 4, 5, 6 until the situation in step "Ends When" is met. Ends when When the industrial vision service data transmission information (including pre-scheduling time-domain resource utilization fed back from E2 Node and the image data transmission delay related enrichment information from the Non-RT RIC) becomes stable within reasonable range, the Near-RT RIC stops updating the pre-scheduling start time. Exceptions None identified. Post Conditions The Non-RT RIC monitors the service performance by collecting and monitoring the relevant performance KPIs and counters from the RAN and the application server. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 155 The flow diagram of Industrial vision assurance use case is given in figure 4.24.3-1. Figure 4.24.3-1: Industrial vision assurance use case flow diagram |
90bcf7b13befe222ebcc419f28dd32b6 | 104 036 | 4.24.4 Required data | Enrichment Information are expected to be retrieved by Non-RT RIC for industrial vision SLA assurance. Service data transmission information from E2 Node are also expected to be collected by Near-RT RIC for industrial vision assurance. 1) Enrichment information: a) Production-line and industrial vision camera configuration related data, e.g. production line speed, image color, pixel. (collected from Application Server/MES) b) Service-related performance measurement metrics collected from application server, e.g. image data transmission delay. (collected from Application Server/MES) 2) Service data transmission information: e.g. pre-schedule time-domain resource utilization, which is the ratio of the time-domain resource of the data to be scheduled to the total pre-scheduled time-domain resource. (new E2 measurements) 4.25 Use case 25: Non-Public Network (NPN) RAN-Sharing via Midhaul for Multi-Operator Coverage Void. ETSI ETSI TS 104 036 V12.0.0 (2025-04) 156 Annex A (informative): Additional Information A.1 Traffic Steering use case A1 interface usage example NOTE: Please refer to WG2 Use Cases and Requirements Specification for more details and up to date definitions of this use case A1 interface usage examples. An example scenario is here used to describe the use of A1 for traffic steering, implying the Non-RT RIC sending policies for allocation of the control plane (RRC) and the user plane for different services, identified by their 5QI. In the scenario a UE with UEid=1, belonging to a subnet slice identified by S-NSSAI=1, having a Voice (5QI=1) and an MBB (5QI=9) connection established, enters an area covered by four frequency bands. The Non-RT RIC understands the requirements and characteristics of the services and decides to let the Voice and RRC connection reside on the low band (here covered by a macro cell B becoming the PCell), while the MBB connection should preferably use the higher band (here provided by a smaller cell C and D becoming the SCells) and avoid the low band if possible. Cell A is used for MBB if required for coverage reasons. Policies are sent to any cell of concern, e.g. where the UE resides and can move. The desired use of the cells is shown in figure A.1-1. Figure A.1-1: Desired use of the cells Two policies over A1 are needed to accomplish the desired behavior, described in JSON format below. Note that as part of the scope, the cell_id is optional, and if omitted it is up to the Near-RT RIC to locate the UE and there enforce the policy. { "policy_id": "1", "scope": { "ue_id": "1", "slice_id": "1", "qos_id": "1", "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D ETSI ETSI TS 104 036 V12.0.0 (2025-04) 157 }, "statement": { "cell_id_list": "B", "preference": "Shall", "primary": true // Control plane on Cell B (becoming PCell) }, "statement": { "cell_id_list ": "B", "preference": "Shall", "primary": false // Voice on Cell B } } { "policy_id": "2", "scope": { "ue_id": "1", "slice_id": "1", "qos_id": "9", "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D }, "statement": { "cell_id_list ": {"B", "A"}, "preference": "Avoid", "primary": false // Avoid MBB on Cell A and Cell B }, "statement": { "cell_id_list": {"C", "D"}, "preference": "Prefer", "primary": false // Prefer MBB on Cell C and Cell D } } ETSI ETSI TS 104 036 V12.0.0 (2025-04) 158 Annex B (informative): Change history Date Version Information about changes 2019.10.17 01.00 • First version with initial set of use cases. Describes selected O-RAN use cases in further details to facilitate relevant O-RAN Work Groups to define requirements for associated O-RAN functions and interfaces. 2020.03.11 02.00 • Updates to the existing use cases. • Addition of RAN sharing use case. • Addition of QoS based resource optimization use case. • Addition of Annex A. 2020.07.16 03.00 • Addition of RAN slice SLA assurance use case. • Enhancements to traffic steering use case. 2020.11.13 04.00 • Addition of dynamic spectrum sharing use case. • Addition of long term NSSI optimization use case. 2021.03.13 05.00 • Addition of signaling storm protection use case. • Updates to massive MIMO optimization use case. 2021.07.19 06.00 • Additions to massive MIMO beam forming use case. 2021.11.23 07.00 • Updates to NSSI resource optimization use case. 2022.04.04 08.00 • Addition of local indoor positioning use case. • Updates to QoE optimization use case based on RAN analytics information exposure feature. 2022.08.01 09.00 • Addition of energy savings use case. • Addition of MU-MIMO optimization use case. • Addition of Shared O-RU use case. 2022.11.18 10.00 • Addition of integrated RRM-SON use case. • Updates to Shared O-RU use case. • Updates to RAN slice SLA assurance use case (Reliability assurance). • Updates to traffic steering use case (Enrichment based optimization). 2023.03.24 11.00 • Updates to Shared O-RU use case. • Updates to multi-vendor slices use case. • Editorial updates. 2023.07.27 12.00 • Updates for O-RAN Drafting Rules (ODR) compliancy. • Addition of industrial vision SLA assurance use case. • Addition of two sub-use cases to Shared O-RU use case (Resiliency of Shared O- RU, Software update of O-RU). ETSI ETSI TS 104 036 V12.0.0 (2025-04) 159 History Document history V12.0.0 April 2025 Publication |
98d566ac142ee06783f646c81587b072 | 104 025 | 1 Scope | The present document defines the interfaces through which a DVB-HB Local Server can redistribute broadcast signals and associated metadata to DVB-HB Clients and specifies mechanisms allowing a DVB-HB Local Server to announce its presence on the LAN and its capabilities, and a DVB-HB Client to discover it. It includes backwards-compatible extensions to the SAT>IP and DVB-I specifications. |
98d566ac142ee06783f646c81587b072 | 104 025 | 2 References | |
98d566ac142ee06783f646c81587b072 | 104 025 | 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 are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] EN 50585: "Communications protocol to transport satellite delivered signals over IP networks", produced by CENELEC. . [2] ETSI TS 103 285: "Digital Video Broadcasting (DVB); MPEG-DASH Profile for Transport of ISOBMFF Based DVB Services over IP Based Networks". [3] ETSI TS 103 770: "Digital Video Broadcasting (DVB); Service Discovery and Programme Metadata for DVB-I". [4] ETSI EN 300 421: "Digital Video Broadcasting (DVB); Framing structure, channel coding and modulation for 11/12 GHz satellite services". [5] ETSI EN 302 307-1: "Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications; Part 1: DVB-S2". [6] ETSI EN 302 307-2: "Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications; Part 2: DVB-S2 Extensions (DVB-S2X)". [7] ETSI EN 300 744: "Digital Video Broadcasting (DVB); Framing structure, channel coding and modulation for digital terrestrial television". [8] ETSI EN 302 755: "Digital Video Broadcasting (DVB); Frame structure channel coding and modulation for a second generation digital terrestrial television broadcasting system (DVB-T2)". [9] ETSI EN 300 429: "Digital Video Broadcasting (DVB); Framing structure, channel coding and modulation for cable systems". [10] ETSI EN 302 769: "Digital Video Broadcasting (DVB); Frame structure channel coding and modulation for a second generation digital transmission system for cable systems (DVB-C2)". [11] ETSI TS 101 154: "Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcast and Broadband Applications". [12] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". ETSI ETSI TS 104 025 V1.1.1 (2024-07) 10 [13] ISO/IEC 29341-1-1: "Information technology - UPnP device architecture - Part 1-1: UPnP Device Architecture Version 1.1". [14] IETF RFC 6763: "DNS-Based Service Discovery". [15] IETF RFC 6762: "Multicast DNS". [16] IETF RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)". [17] IETF RFC 5261: "An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors". [18] ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems". [19] ETSI TS 102 809: "Digital Video Broadcasting (DVB); Signalling and carriage of interactive applications and services in Hybrid Broadcast/Broadband environments". |
98d566ac142ee06783f646c81587b072 | 104 025 | 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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] DVB Document A180: "Native IP Broadcasting". [i.2] ETSI EN 303 560: "Digital Video Broadcasting (DVB); TTML subtitling systems". [i.3] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". [i.4] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". [i.5] IETF RFC 9110: "HTTP Semantics". [i.6] IETF RFC 1918: "Address Allocation for Private Internets". [i.7] W3C®: "Private Network Access - W3C Community Group Draft Report, 29 April 2024". [i.8] W3C®: "Encrypted Media Extensions - "W3C Recommendation 18 September 2017 (Link to Editor's Draft updated 19 December 2019)". [i.9] W3C®: "Mixed Content - Editor's Draft, 23 February 2023". [i.10] CA/Browser Forum: "Baseline Requirements for the Issuance and Management of Publicly- Trusted Certificates", Version 1.6.3". [i.11] T. Rigoudy: "Private Network Access update: Introducing a deprecation trial", Chrome for Developers, February 10, 2022. [i.12] Android Developers Guides: "Supported media formats", Google®. [i.13] D. Nandakumar, S. Kotecha, K. Sampath, P. Ramachandran, T. Vaughan: "Efficient Multi-Rate HEVC Encoding for Adaptive Streaming", IBC White Paper, Amsterdam, 2016. [i.14] FFmpeg: "Creating Multiple Outputs". [i.15] IEEE 802.11™: "IEEE Standard for Information technology--Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". ETSI ETSI TS 104 025 V1.1.1 (2024-07) 11 [i.16] D. Murray, T. Koziniec, M. Dixon and K. Lee: "WiFi multicast streaming using AL-FEC inside the trains of high-speed rails", IEEE international Symposium on Broadband Multimedia Systems and Broadcasting, Seoul, 2012, pp. 1-6. [i.17] H. Chiao, S. Chang, K. Li, Y. Kuo and M. Tseng: "WiFi multicast streaming using AL-FEC inside the trains of high-speed rails", IEEE international Symposium on Broadband Multimedia Systems and Broadcasting, Seoul, 2012, pp. 1-6. [i.18] C.A.G.D. Silva and C.M. Pedroso: "MAC-Layer Packet Loss Models for Wi-Fi Networks: A Survey", in IEEE Access, vol. 7, pp. 180512-180531, 2019. [i.19] Y.J. Liang, J.G. Apostolopoulos and B. Girod: "Analysis of Packet Loss for Compressed Video: Effect of Burst Losses and Correlation Between Error Frames", in IEEE Transactions on Circuits and Systems for Video Technology, vol. 18, no. 7, pp. 861-874, July 2008. [i.20] S. Aramvith, Chia-Wen Lin, S. Roy and Ming-Ting Sun: "Wireless video transport using conditional retransmission and low-delay interleaving", in IEEE Transactions on Circuits and Systems for Video Technology, vol. 12, no. 6, pp. 558-565, June 2002, doi:10.1109/TCSVT.2002.800326. [i.21] T.K. Sarkar, M.C. Wicks, M. Salazar-Palma, R.J. Bonneau: "A Survey of Various Propagation Models for Mobile Communication," in Smart Antennas, IEEE, 2003, pp. 239-307. [i.22] Han Longzhe, Park Sungjun, Kang Seung-Seok and In Hoh: "An Adaptive Cross-Layer FEC Mechanism for Video Transmission over 802.11 WLANs", TIIS, 4, 2010. [i.23] M. Gast: "802.11 Wireless Networks: The Definitive Guide", Definitive Guide Series, "O'Reilly Media, Inc.", 2005. [i.24] C. Lin, H. Zhang, C. Shieh and W. Hwang: "Performance analysis of MPEG-4 video stream with FEC error recovery over IEEE 802.11 DCF WLANs", 11th International Symposium and Workshops on Modeling and Optimization in Mobile, Ad Hoc and Wireless Networks (WiOpt), Tsukuba Science City, 2013, pp. 634-640. [i.25] P. Bucciol, G. Davini, E. Masala, E. Filippi and J. C. De Martin: "Cross-layer perceptual ARQ for H.264 video streaming over 802.11 wireless networks", IEEE Global Telecommunications Conference, 2004. GLOBECOM '04., Dallas, TX, 2004, Vol. 5, pp. 3027-3031, doi:10.1109/GLOCOM.2004.1378908. [i.26] M. Podolsky, S. McCanne and M. Vetterli: "Soft ARQ for Layered Streaming Media", VLSI Signal Processing. 27, 81-97 (2001), doi:10.1023/A:1008123631453. [i.27] M. Portoles-Comeras et al.: "Modeling and Exploiting the Relation Between Packet Losses and Hidden Traffic," in IEEE Wireless Communications Letters, vol. 2, no. 4, pp. 391-394, August 2013, doi:10.1109/WCL.2013.050613.130159. [i.28] S. Afzal, V. Testoni, C.E. Rothenberg, P. Kolan and I. Bouazizi: "A Holistic Survey of Wireless Multipath Video Streaming.", arXiv:1906.06184 (2019). [i.29] IETF RFC 6265: "HTTP State Management Mechanism". [i.30] ISO/IEC 13818 (Parts 1 to 3): "Information technology - Generic coding of moving pictures and associated audio information". |
98d566ac142ee06783f646c81587b072 | 104 025 | 3 Definition of terms, symbols and abbreviations | |
98d566ac142ee06783f646c81587b072 | 104 025 | 3.1 Terms | For the purposes of the present document, the following terms apply: DVB Gateway: device which may provide functions of a DVB-HB Local Server, a DVB-NIP Gateway or both ETSI ETSI TS 104 025 V1.1.1 (2024-07) 12 DVB-HB Client: unit capable of connecting to a DVB-HB Local Server and processing and/or rendering content NOTE: A DVB-HB Client consumes only one DVB service at a time. Multiple DVB-HB Clients may be hosted on a single DVB-HB Client Device. DVB-HB Local Server: unit capable of serving a DVB-HB Client with zero, one or more service lists, and capable of serving DVB-HB Clients with a DVB service from a broadcast it has direct access to DVB-I Client: implementation of the client side of ETSI TS 103 770 [3] NOTE: This may be integrated into the User Interface of a device such as a TV set or Set-Top-Box or part of an app on devices such as mobile phones or tablets. DVB-NIP Gateway: device including one or more broadcast reception frontends plus all functions required to interface with DVB-NIP Clients according to DVB Document A180 [i.1] HTML5: fifth version of HTML, a markup language used for structuring and presenting content on the World Wide Web NOTE: It is a W3C recommendation. MPEG-2: ISO/IEC 13818 set of standards NOTE: Systems coding is defined in part 1, video coding is defined in part 2, and audio coding is defined in part 3 of ISO/IEC 13818 [i.30]. QR code: two-dimensional machine-readable optical barcode that contains information about the item to which it is attached |
98d566ac142ee06783f646c81587b072 | 104 025 | 3.2 Symbols | Void. |
98d566ac142ee06783f646c81587b072 | 104 025 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACFEC Adaptive Cross-layer Forward Error Correction AIT Application Information Table AL-FEC Application Layer - Forward Error Correction AP Access Point API Application Programming Interface APP APPlication-specific ARP Address Resolution Protocol ARQ Automatic Repeat reQuest AVC Advanced Video Coding BMFF Base Media File Format CA Certificate Authority CAS Conditional Access System CDN Content Delivery Network CORS Cross-Origin Resource Sharing COTS Commercial Off-The-Shelf CPU Central Processing Unit CSV Comma Separated Values DASH Dynamic Adaptive Streaming over HTTP DDNS Distributed Domain Name System DHCP Dynamic Host Configuration Protocol DNS Domain Name System DNS-SD Domain Name System - Service Discovery DOM Document Object Model DSM-CC Digital Storage Media - Command and Control DTH Direct To Home ETSI ETSI TS 104 025 V1.1.1 (2024-07) 13 DVB Digital Video Broadcasting DVB-C DVB Cable Framing and Modulation DVB-C2 DVB Cable Framing and Modulation, Second Generation DVB-HB DVB Home Broadcast DVB-I DVB Internet DVB-IPTV DVB Internet Protocol TeleVision DVB-NIP DVB Native IP DVB-S DVB Satellite Framing and Modulation DVB-S2 DVB Satellite Framing and Modulation, Second Generation DVB-S2X DVB Satellite Framing and Modulation, Second Generation Extensions DVB-T DVB Terrestrial Framing and Modulation DVB-T2 DVB Terrestrial Framing and Modulation, Second Generation EIT Event Information Table EME Encrypted Media Extensions FEC Forward Error Correction FQDN Fully Qualified Domain Name GOP Group Of Pictures HbbTV® Hybrid Broadcast Broadband TeleVision HEVC High Efficiency Video Coding HTML HyperText Markup Language HTTP HyperText Transfer Protocol HTTPS HyperText Transfer Protocol Secure ID IDentifier IEEE Institute of Electrical and Electronic Engineers IP Internet Protocol IRD Integrated Receiver Decoder ISO International Organization for Standardization IT Information Technology LAN Local Area Network LCN Logical Channel Numbering LNB Low Noise Block M3U MPEG audio layer 3 Uniform resource locator MAC Media Access Control MCS Modulation and Coding Scheme mDNS Multicast Domain Name System MPD Media Presentation Description MPEG Moving Pictures Expert Group MPTS Multi-Programme Transport Stream NT Notification Type NTS Notification Sub Type OCR Optical Character Recognition OSCP Online Certificate Status Protocol OSI Open Systems Interconnection PC Personal Computer PFR Playable Frame Rate PID Packet IDentifier PMT Program Map Table PSNR Peak Signal to Noise Ratio PTR Pointer PVR Personal Video Recorder QEF Quasi Error Free QoE Quality of Experience QoS Quality of Service QR Quick Response RAP Random Access Point RF Radio Frequency RTCP RTP Control Protocol RTP Real Time Protocol RTSP Real Time Streaming Protocol SAT>IP® SATellite over Internet Protocol SD Standard Definition (Video) SDP Session Description Protocol ETSI ETSI TS 104 025 V1.1.1 (2024-07) 14 SDT Service Description Table SI Service Information SPTS Single Programme Transport Stream SRV Service SSDP Simple Service Description Protocol STB Set Top Box TCP Transmission Control Protocol TLS Transport Layer Security TS DVB Transport Stream TTL Time To Live TTML Timed Text Markup Language TV TeleVision TXT Text UDP User Datagram Protocol UI User Interface UPnP Universal Plug and Play URI Unified Resource Identifier URL Uniform Resource Locator URN Uniform Resource Name USB Universal Serial Bus USN Unique Service Name UUID Universally Unique IDentifier W3C World Wide Web Consortium Wi-Fi WIreless FIdelity WLAN Wireless Local Area Network XML eXtensible Markup Language |
98d566ac142ee06783f646c81587b072 | 104 025 | 4 Concepts and overview | The DVB Home Broadcast (DVB-HB) concept enables client devices to access and consume broadcast content that has been retransmitted, through Internet Protocol (IP) means, by a local server located in the same IP subnetwork such as a Local Area Network (LAN). Client devices, including those which cannot access linear broadcast services directly (for example because they do not have a tuner, like smartphones and tablets, or because they are only equipped, e.g. with a terrestrial tuner and not satellite), can receive them from a DVB-HB Local Server instead of via the Internet, as those services are already available at full quality at the antenna home plug. This allows: • Broadcasters to guarantee the desired picture quality to all users even when they are using an IP-connected device, and at the same time to reduce their Content Delivery Network (CDN) distribution costs. • Telecom operators to reduce risks of network congestion in case of traffic peaks due to popular live events. • Users to consume live TeleVision (TV) services on their IP-connected devices with a high and steady picture quality, even in digital-divide areas, where broadband connectivity is not yet optimal. • Designers of in-building network infrastructures (e.g. for hospitality, campus, etc.) to easily integrate TV distribution with other Information Technology (IT) services. Two general functions can be identified for a typical DVB-HB Local Server: • Announcement on the LAN and exposure of device capabilities, including signalling of available services. • Tuning to a Radio Frequency (RF) signal upon request of a DVB-HB Client and subsequent redistribution of the content via IP network, possibly after audio/video transcoding to match the capabilities of the device hosting the DVB-HB Client. Four general functions can be identified for a typical DVB-HB Client: • Presentation to an end-user of a catalogue of the available services. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 15 • Signalling exchanges with a DVB-HB Local Server (possibly with the aid of an external repository). • Reception of content from a DVB-HB Local Server. • Display and/or processing of the content received. In order to address all significant deployment scenarios, the present document includes two Profiles, named Profile A and Profile B: Profile A Based on SAT>IP as specified in EN 50585 [1], extending it with a number of additional optional features, foreseeing redistribution of the selected TV services as DVB Transport Stream (TS) over IP. Profile B Targeting compatibility with DVB-I Clients, foreseeing redistribution of the selected TV services as Moving Pictures Expert Group (MPEG) Dynamic Adaptive Streaming over HTTP (DASH) according to ETSI TS 103 285 [2] together with service discovery metadata according to ETSI TS 103 770 [3]. Profile B also supports browser-based client applications. The present document specifies: • Mechanisms allowing a DVB-HB Local Server to announce its presence on the LAN and a DVB-HB Client to discover it. • Mechanisms allowing a DVB-HB Local Server to expose its capabilities in terms of available resources and distributed services. • Backwards-compatible optional extensions to the SAT>IP specification, improving supported capabilities and network resilience. • Backwards-compatible extensions to the DVB-I specification, adding support to DVB-HB functionalities. Additionally, the present document provides informative guidelines on a number of aspects, e.g.: • Conversion of DVB-Service Information (SI) metadata to DVB-I format. • Combined use of HyperText Transfer Protocol (HTTP) and HyperText Transfer Protocol Secure (HTTPS) in browser-based DVB-HB Clients. • Encoding and packaging requirements and recommendations. • Provision of Hybrid Broadcast Broadband TeleVision (HbbTV®) applications to DVB-HB Clients. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5 DVB-HB Reference architecture | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.1 Introduction | The relationships between the logical functions in the reference architecture are identified by named reference points. In a practical deployment, each of these is realized by a concrete interface and conveys information between the relevant functions using a specific protocol. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.2 Reference architecture diagram | Figure 1 summarizes the simplified DVB-HB reference architecture, showing the reference points and the logical functions. Data plane interactions are depicted using solid lines. Control plane interactions are depicted using dotted lines. Interactions that lie within the scope of the present document are depicted as black lines with a reference point name. Those beyond the scope of the present document (but relevant to the functional architecture and described by means of informative guidelines) are shown with grey lines. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 16 The architecture is then illustrated with more details in figure 2 and figure 3 for Profiles A and B respectively. In these figures, logical functions are depicted as named boxes and these may be nested in cases where a high-level function is composed of several subfunctions. Optional functions are represented with dotted blocks. Figure 1: Simplified reference architecture (Profiles A and B) Figure 2: Reference architecture for Profile A ETSI ETSI TS 104 025 V1.1.1 (2024-07) 17 Figure 3: Reference architecture for Profile B |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3 Reference points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1 Data plane reference points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.1 Introduction | The reference points defined in this clause are used primarily to transport content and service list metadata. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.2 Generic data plane reference points (Profiles A and B) | I Input RF interface between Digital Video Broadcasting (DVB) broadcast networks and the Tuners function of a DVB-HB Local Server. Input signals can be any of the following: • DVB Satellite Framing and Modulation (DVB-S) signals as defined in ETSI EN 300 421 [4]. • DVB Satellite Framing and Modulation, Second Generation (DVB-S2) signals as defined in ETSI EN 302 307-1 [5]. • DVB Satellite Framing and Modulation, Second Generation Extensions (DVB-S2X) signals as defined in ETSI EN 302 307-2 [6]. • DVB Terrestrial Framing and Modulation (DVB-T) signals as defined in ETSI EN 300 744 [7]. • DVB Terrestrial Framing and Modulation, Second Generation (DVB-T2) signals as defined in ETSI EN 302 755 [8]. • DVB Cable Framing and Modulation (DVB-C) signals as defined in ETSI EN 300 429 [9]. • DVB Cable Framing and Modulation, Second Generation (DVB-C2) signals as defined in ETSI EN 302 769 [10]. Carriage of A/V content and related information in a TS is as specified in ETSI TS 101 154 [11], clause 4. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 18 L Interaction between the Content Playback function of a DVB-HB Client and the Content publication function of a DVB-HB Local Server. M Interaction between the Service discovery and selection function of a DVB-HB Client and the Service List publication function of a DVB-HB Local Server. This interface includes the fetching of Service List(s) and Content Guide. NOTE: The Service List publication function may be hosted on a remote server published on the web (how the service list is produced in this case is out of scope of the present document). A HTTP or HTTPS interaction between the Service discovery and selection function of a DVB-HB Client and the Resource availability map function of a DVB-HB Local Server. T Distribution of the TS, as received by the Tuners function, to Service List publication and Content Preparation functions in a DVB-HB Local Server. Pin Provision of content to a Content publication function by a Content preparation function within a DVB-HB Local Server. This may be implemented as a push interface, or content may be pulled on demand from a Content packaging function (out of scope of the present document). E External provision of service list metadata (out of scope of the present document, it may be a proprietary interface). |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.3 Specific data plane reference points for Profile A | I See clause 5.3.1.2. L_A Delivery of content via Real Time Streaming Protocol (RTSP)/Real Time Protocol (RTP) or HTTP interaction between the Content publication function of a Profile A DVB-HB Local Server and the Content Playback function of a Profile A DVB-HB Client, according to EN 50585 [1], and additional optional Application Layer - Forward Error Correction (AL-FEC) packets as defined in clause 8.4.2. NOTE: CL_A and L_A reference points physically correspond to requests and responses of the RTSP or HTTP communication between Streaming Server (SAT>IP) and SAT>IP client subfunctions. M_A HTTP(S) interaction between the Service discovery and selection function of a Profile A DVB-HB Client and the Service List publication function of a Profile A DVB-HB Local Server. This interface includes the fetching of the service list(s) in MPEG audio layer 3 Uniform resource locator (M3U) or eXtensible Markup Language (XML) format. A HTTP(S) interaction between the Service discovery and selection function of a DVB-HB Client and the Resource availability map function of a DVB-HB Local Server. T See clause 5.3.1.2. Pin_A Provision of content in the form of TS packets over IP to a Content publication function by a Content preparation function in a Profile A DVB-HB Local Server (out of scope of the present document). E See clause 5.3.1.2. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 19 |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.1.4 Specific data plane reference points for Profile B | I See clause 5.3.1.2. L_B HTTP(S) interaction between the Origin server subfunction of a Profile B DVB-HB Local Server and the DVB-DASH client subfunctions of a Profile B DVB-HB Client for content delivery, and eventually the Data file extraction subfunction in case of additional data files (e.g. an interactive application). NOTE 1: The L_B reference point aggregates interfaces D2, E1 and E2 defined in ETSI TS 103 770 [3], i.e. all interaction between Origin server and DVB-DASH client subfunctions except request for DASH Media Presentation Description (MPD): the latter, while being carried over the same physical interface, is represented by the CL_B reference point. M_B HTTP(S) interaction between the Service discovery and selection) function of a Profile B DVB-HB Client and the Service List publication function of a Profile B DVB-HB Local Server. This interface includes the fetching of the service list(s) in XML format according to ETSI TS 103 770 [3]. NOTE 2: The M_B reference point aggregates interfaces A1, A2, B1 and B2 defined in ETSI TS 103 770 [3]. A HTTP(S) interaction between the Service discovery and selection function of a DVB-HB Client and the Resource availability map function of a DVB-HB Local Server. T See clause 5.3.1.2. Pin_B Provision of content in the form of files (i.e. DASH segments, eventually data files) to a Content publication function by a Content preparation function in a Profile B DVB-HB Local Server (out of scope of the present document). E See clause 5.3.1.2. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2 Control plane reference points | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.1 Introduction | The reference points defined in this clause are used for control signalling. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.2 Generic control plane reference points (Profiles A and B) | CL Control interface for request of a specific service by a DVB-HB Client. CA Control interface for discovery and capability exposure of DVB-HB Local Servers. CS Control interface for forwarding service requests to the Service Request Handler) function (out of scope of the present document). CT Control interface for commands to the Tuners function (out of scope of the present document). CU Control interface to control content playback in a DVB-HB Client according to the selected service. It is out of scope of the present document, but would generally involve passing a Uniform Resource Locator (URL) to initiate playback. CM Control interface between the Resource allocation subfunction of the Service request handler function and the Resource availability map function, for keeping the availability map up-to-date (out of scope of the present document). ETSI ETSI TS 104 025 V1.1.1 (2024-07) 20 |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.3 Specific control plane reference points for Profile A | CL_A Control interface for request of a specific service by a Profile A DVB-HB Client, based on RTSP or HTTP requests according to EN 50585 [1]. NOTE: CL_A and L_A reference points physically correspond to requests and responses of the RTSP or HTTP communication between Streaming Server (SAT>IP) and SAT>IP client subfunctions. CA_A Control interface for discovery and capability exposure of Profile A DVB-HB Local Servers according to EN 50585 [1]. CS_A Control interface for commands to the Tuners function in case of Profile A (out of scope of the present document). CT See clause 5.3.2.2. CU_A Control interface to control content playback in a Profile A DVB-HB Client according to the selected service. It is out of scope of the present document, but would generally involve passing a URL to initiate playback. CM See clause 5.3.2.2. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.3.2.4 Specific control plane reference points for Profile B | CL_B Control interface for request of a specific service by a Profile B DVB-HB Client, based on HTTP(S) requests of MPD files according to ETSI TS 103 285 [2]. NOTE: The CL_B reference point corresponds to interface D1 defined in ETSI TS 103 770 [3]. CA_B Control interface for discovery and exposure of capabilities of Profile B DVB-HB Local Servers (see also clause 6 and clause 7.2). CS_B Control interface for commands to the Tuners function in case of Profile B (out of scope of the present document). CT See clause 5.3.2.2. CN_B Control interface used by the Service List publication function to communicate file names to be adopted by the DVB-DASH packager subfunction, as defined in the Service List, for the generation of the requested service according to ETSI TS 103 285 [2]. CE_B Control interface used by the Encoding configuration agent subfunction to communicate the encoding parameters, as defined in the Service List for the specific selected service, to the Content encoding subfunction. CU_B Control interface to control content playback in a Profile B DVB-HB Client according to the selected service. It is out of scope of the present document, but would generally involve passing a URL to initiate playback. CM See clause 5.3.2.2. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4 Functions | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.1 DVB broadcast networks | This is an external function, out of scope of the present document. It represents deployed on-the-air DVB satellite and/or terrestrial and/or cable broadcast networks, delivering audio/video services to consumer devices (e.g. TVs/Set Top Box (STB)s). ETSI ETSI TS 104 025 V1.1.1 (2024-07) 21 |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.2 Tuners | Hardware modules receiving and demodulating on-the-air DVB-S/DVB-S2/DVB-S2X/DVB-T/DVB-T2/DVB-C/DVB- C2 signals, providing in output the relevant TS. Multiple modules may be available, each of them producing a TS. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3 Service List publication | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3.1 General description | The Service List publication function generates and maintains the Service List and the associated Content Guide describing the services offered by a DVB-HB Local Server, and publishes it on the LAN for DVB-HB Clients requesting it. The function includes a Service List compilation subfunction generating Service List(s) according to the supported formats and a Web server subfunction for publication (HTTP(S) server). It may generate the Service List and associated Content Guide locally on the basis of the DVB-SI metadata received over the T reference point, or it may rely on metadata retrieved from an External repository (how the service list is produced in this second case is out of scope of the present document). |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3.2 Service List publication for Profile A | In case of Profile A, Service List publication is an optional function, i.e. DVB-HB Clients can use other means for service discovery, e.g. frequency scan via remote tuning commands. The Service List compilation subfunction should generate service lists according to M3U format and/or according to XML format as defined in ETSI TS 103 770 [3], so that the features associated with metadata of the service list published in this format are made available to the DVB-HB Clients (e.g. Logical Channel Numbering (LCN), regionalization, multiple instances, etc.). NOTE: Other service list formats are not prevented by EN 50585 [1]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.3.3 Service List publication for Profile B | In case of Profile B, the Service List compilation subfunction generates Service List(s) and associated Content Guide according to the XML formats as defined in ETSI TS 103 770 [3]. Eventually, it may also generate additional signalling files, e.g. an XML-encoded Application Information Table (AIT) associated to an interactive application (see also annex Annex D). Additionally, it provides file names over the CN_B reference point, to be adopted by the DVB-DASH packager subfunction, as defined in the Service List, for the generation of the requested service in DVB-DASH format by the DVB-HB Local Server. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4 Content preparation | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4.1 General description | The Content preparation function has the task of producing the selected audio/video content for publication on the LAN, on the basis of the TS demodulated by the Tuners function. It includes a PID selection/processing subfunction, with the task of selecting the Packet IDentifier (PID)s associated with the desired service and apply proper manipulations as needed, and additional profile-specific subfunctions, as described in clause 5.4.4.2 and clause 5.4.4.3. Redistribution of services protected by a Conditional Access System (CAS), including for example decryption and re- protection, is out of scope of the present document, but is not prevented. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 22 |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4.2 Content preparation for Profile A | In case of Profile A, in addition to the PID selection/processing subfunction described in clause 5.4.4.1, a TS/IP encapsulation subfunction has the task of encapsulating TS packets in RTP packets carried in User Datagram Protocol (UDP) packets carried in IP datagrams (i.e. TS/RTP/UDP/IP) as defined in EN 50585 [1]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.4.3 Content preparation for Profile B | In case of Profile B, in addition to the PID selection/processing subfunction described in clause 5.4.4.1, the following subfunctions exist: • Content decoding subfunction, with the task of decoding the A/V content (and associated data) of the selected service. • Content encoding subfunction, with the task of transforming the source media streams produced by the Content decoding subfunction into encoded media at the desired bit-rate. A single source media stream may be transformed into a number of different encoded representations to match delivery conditions or DVB-HB Client device capabilities. Virtual segment boundary markers may be placed in the encoded media representation to assist an adaptive Content playback function in its operation. The output of the Content encoding subfunction is a stream formatted so as to be suitable for ingest by the DVB-DASH packager subfunction. • DVB-DASH packager subfunction, with the task of ingesting the media streams of one (or more) encoded representations and formatting each one according to the International Organization for Standardization (ISO) Base Media File Format (BMFF) packaging format as defined in ETSI TS 103 285 [2]. In the context of dynamic adaptive streaming, the output of the packager is a sequence of packaged media segments with representation switching points that are aligned across different representations of the same source media stream. • Data file extraction subfunction, with the task of decoding data files carried over the TS according to a specific format (e.g. an interactive application transported as a Digital Storage Media - Command and Control (DSM-CC) carousel in the incoming TS). • The Content preparation function should also include extraction of subtitles from the incoming TS and their conversion to a DASH-compatible format according to ETSI TS 103 285 [2], clause 7. If the incoming subtitles are encoded as DVB Timed Text Markup Language (TTML) according to ETSI EN 303 560 [i.2], the translation is a simple repackaging. For other forms of subtitles a transcoding is required. DVB bitmap subtitles require Optical Character Recognition (OCR) support for decoding. Teletext subtitles require text remapping and translation of position and colour information. NOTE: Broadcasters wishing to support Profile B DVB-HB Clients may consider adding a DVB TTML component to services. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5 Content publication | |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5.1 General description | The Content publication function has the following tasks: • Listening to requests from DVB-HB Clients over the CL reference point and triggering tuning commands by forwarding such requests in a proper format to the Service request handler function over the CS reference point. • Making the content available for delivery to the Content playback function over the L reference point. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5.2 Content publication for Profile A | In case of Profile A, the Streaming server (SAT>IP) subfunction interacts with the Content playback function by receiving requests over the CL_A reference point, triggering tuning commands and delivering the requested content over the L_A reference point according to the protocols defined in EN 50585 [1]. ETSI ETSI TS 104 025 V1.1.1 (2024-07) 23 Optionally, additional AL-FEC packets associated with the data packets are sent by the Network resilience (Tx) subfunction over the L_A reference point for error protection, as defined in clause 8.4.2. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.5.3 Content publication for Profile B | In case of Profile B, the Content Publication function consists of an Origin Server subfunction (HTTP(S) server), which interacts with the Content playback function by receiving requests over the CL_B reference point, triggering tuning commands and delivering the requested content over the L_B reference point according to ETSI TS 103 285 [2]. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.6 Service request handler | The Service request handler function has the task of converting DVB-HB Client requests, as intercepted by the Content publication function and forwarded over the CS reference point, to tuning commands sent to the Tuners function over the CT reference point. It consists of a Resource allocation subfunction, responsible of optimizing the available resources of a DVB-HB Local Server (e.g. tuners, Central Processing Unit (CPU), etc.) according to the overall requests simultaneously managed by the device at each point of time, and a Tuning request agent subfunction, responsible of sending the actual tuning commands to the Tuners function. Additionally, in case of Profile B, it also consists of an Encoding configuration agent subfunction, which may provide the encoding parameters, as defined in the Service List for the specific selected service, to the Content encoding subfunction over the CE_B reference point. |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.7 DVB-HB Local Server announcement | The DVB-HB Local Server announcement function has the task of providing advertisements of the presence of a DVB-HB Local Server on the LAN and providing description of the DVB-HB Local Server capabilities (e.g. number and type of tuners, etc.). |
98d566ac142ee06783f646c81587b072 | 104 025 | 5.4.8 DVB-HB Local Server discovery | The DVB-HB Local Server discovery function is a function of a DVB-HB Client with the task of searching on the LAN for available DVB-HB Local Servers and retrieving their capabilities. See also clause 6 for protocols used. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.