hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.3 Beamforming configuration update | This clause provides the method to modify and to apply the beamforming configuration (weights, attributes and/or beam properties). The modification of the beamforming information is allowed only if O-RU supports the feature "MODIFY-BF-CONFIG" used for defining the modification of beamforming configuration. The beamforming configuration is stored in the O-RU and comes from the O-RU's software, treated in clause 8. The O-RU shall locate the beamforming configuration file in the generic folder, i.e. O-RAN/beamforming/ or o-ran/beamforming/. To modify the beamforming configuration, the following steps are applied: 1) NETCONF client can retrieve the file list of the O-RU's folder: O-RAN/beamforming/ or o-ran/beamforming/. 2) NETCONF client can trigger the upload of the beamforming configuration file from the O-RU's folder. 3) Operator can recover the uploaded file and edit the beamforming configuration file offline. 4) NETCONF client can download the file to the original folder. The modified beamforming configuration file shall not have the same name as any other file in the folder. Its file name is the matter of implementation. The beam properties in o-ran-beamforming YANG module contain coarse-fine, coarse-fine-beam-relation and neighbor-beam (sic) for each beam-id. This information is received from the O-RU as O-RU's capability at O-RU start-up and typically are used by the scheduler in O-DU. A NETCONF client (O-RU Controller) can modify the beamforming information via file described in this clause. When the beamforming configuration (weight, attribute and beam properties) is modified via file, the configuration of the beam properties list in the o-ran-beamforming YANG module should be modified together via the same file if affected by the modified weight and/or attribute. An O-RU supporting the modification of beamforming configuration shall support the storage of at least two beamforming files per capabilities-group supported. For each capabilities-group, one file corresponds to the pre-defined (factory, read-only) beamforming configuration and at least one file corresponds to a modified (read-write) beamforming file. The O-RU has the responsibility to remove existing file and prepares space for new file when the NETCONF client file-download rpc is issued. When the O-RU only supports the storage of a single modified (read-write) beamforming file per band of operation, i.e. number-of-writable-beamforming-files = 1 the file- download operation for the modified beamforming configuration needs to be done while neither tx-array-carriers nor rx-array-carriers are configured in the O-RU to avoid the removal of the modified beamforming configuration file for the current active software. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 162 If the O-RU supports the capability to store two or more modified beamforming configuration files per band of operation in the O-RU, i.e. number-of-writable-beamforming-files > 1, the NETCONF file-download operation can be performed without any timing limitation. That is because the modified beamforming configuration file for the current beamforming configuration can be kept during the file-download operation. To apply the new modified beamforming configuration, the following steps are applied: 1) The NETCONF client can download the file to the beamforming folder if the O-RU supports the capability number-of-writable-beamforming-files > 1. 2) If the O-RU doesn't support in-service-bf-update, the NETCONF client shall deactivate tx-array-carriers and rx-array-carriers in the U-Plane configuration by setting "INACTIVE" for the active parameters if they are ACTIVE. When the supported capability in-service-bf-update is advertised by the O-RU, and if the NETCONF client supports the beamforming configuration update in service, the NETCONF client can activate the modified beamforming configuration without deactivating and deleting tx-array-carriers and rx-array-carriers in the U-Plane configuration. 3) Optionally, the NETCONF client shall delete tx-array-carriers and rx-array-carriers and the capability in-service-bf-update shall not be supported, if O-RU does not support the capability update-bf-non-delete. 4) Alternatively, the NETCONF client can trigger the download of the modified beamforming configuration file to the folder if the O-RU's capability is number-of-writable-beamforming-files =1. 5) Regardless of whether or not to deactivate tx-array-carriers and rx-array-carriers, the NETCONF client shall activate the modified beamforming configuration by using: - activate-beamforming-config-by-capability-group rpc and selecting the modified beamforming configuration file and the capabilities-group for which this modified configuration applies. 6) If a NETCONF client subscribes to the notification capability-group-beamforming-information-update in advance, the O-RU sends such notification to the notification subscriber. Then the NETCONF client can subsequently retrieve beam properties in o-ran-beamforming YANG module via NETCONF <get> operation. If the O-RU supports in-service-bf-update and completes the update beamforming, and the O-RU applies the new update beamforming information to the tx-array-carriers and rx-array-carriers, the O-RU sends the notification to the NETCONF client that have subscribed to receive the notification. NOTE: In service updating of beamforming weights without carrier deactivation entails an uncertainty of beamforming weight usage limited to the time between O-RU sending notifications to the time the NETCONF client receives the notification. This uncertainty could cause an interruption of user data traffic, so should be done with caution. Disabling the active carriers prior to making any configuration changes and then re-enabling the carriers after configuration changes are completed does not involve this uncertainty. 7) Optionally, the NETCONF client shall create tx-array-carriers and rx-array-carriers again, if the O-RU does not support the capability update-bf-non-delete. 8) The NETCONF Client shall activate tx-array-carriers and rx-array-carriers in the U-Plane configuration by setting "ACTIVE" for active parameters. If the NETCONF client did not deactivate tx-array-carriers and rx-array-carriers (in the step 2 of the procedure), the NETCONF client doesn't need to activate tx-array- carriers and rx-array-carriers. Then the new edited beamforming information is applied to the new tx-array-carriers and rx-array-carriers in the U-Plane configuration. [Abnormal handling] If the O-RU fails to activate the edited beamforming configuration file correctly, i.e. rpc error for rpc activate-beamforming-config-by-capability-group, the O-RU shall revert back to the pre-defined/factory beamforming configuration file and report this to the NETCONF client. At the reset rpc, the beamforming configuration information is switched to the pre-defined beamforming configuration. Even though the reset operation is issued, the O-RU may store the modified beamforming configuration file in the folder, which is not used, if O-RU supports the capability persistent-bf-files to store them in the reset-persistent memory. The file format of the beamforming configuration is O-RU implementation specific. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 163 Figures 15.4.3-1 and 15.4.3-2 show two methods to successfully modify the file of beamforming configuration information plus the method how to apply the modified file for beamforming configuration conformation to use. Figure 15.4.3-1: Method to Modify the File of Beamforming Configuration Information ETSI ETSI TS 104 023 V17.1.0 (2026-01) 164 Figure 15.4.3-2: Method to Apply the modified file for Beamforming Configuration Information ETSI ETSI TS 104 023 V17.1.0 (2026-01) 165 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.4 Tilting pre-defined beams | This clause describes the optional capability by which the O-RU's pre-defined beams may be tilted by using the "BEAM-TILT" feature defined in the o-ran-beamforming YANG model. This capability is an O-RU specific functionality, enabling adaptation of the service area associated with an O-RU without the need for operation of additional ALDs described in clause 14, or modifying the beamforming configuration using the "MODIFY-BF- CONFIG" feature described in clause 15.4.3. NOTE 1: The operation of the feature "BEAM-TILT" is independent to the operation of the "MODIFY-BF- CONFIG". When the "MODIFY-BF-CONFIG" feature is used to define a new default service area, the "BEAM-TILT" feature can be used to apply tilt-offsets to the newly defined service area. O-RU can change the service area by applying a tilt-offset to the elevation and/or azimuth pointing angles for the pre-defined beams. This feature allows to shift beam characteristic of all predefined-beams in elevation and/or azimuth direction (i.e. changing the service area or sector coverage) while preserving the beam adjacency among the beams within grid of beams. NOTE 2: offset-elevation-tilt-angle values smaller than 0 represents an up-shift of the default service area towards the zenith (i.e. corresponding to a decrease in zenith angle) and values larger than 0 represent a down-shift of the default service area away from the zenith (i.e. corresponding to an increase in zenith angle). Figure 15.4.4-1 shows the sequence diagram for predefined-beam-tilt-offset-information. To shift service area of the O-RU in a different direction, O-RU controller shall check whether the O-RU supports feature BEAM-TILT feature during capabilities negotiation of the NETCONF session. In the case that O-RU supports the BEAM-TILT feature, the O-RU shall ensure that at least one of the elevation-tilt-offset-granularity and azimuth-tilt-offset-granularity is greater than zero value from O-RU. Tilting is a per band operation and hence the parameters are defined per band. If O-RU supports BEAM-TILT feature, O-RU controller can configure the values of offset-elevation-tilt-angle and/or offset-azimuth-tilt-angle and the configuration values should meet the ranges and granularity information retrieved from predefined-beam-tilt-offset-information. Figure 15.4.4-1: Sequence diagram for predefined-beam-tilt-offset-information ETSI ETSI TS 104 023 V17.1.0 (2026-01) 166 Depending on O-RU's implementation, the O-RU may need some time to complete the change of service area according to the updated offset-elevation-tilt-angle and/or offset-azimuth-tilt-angle for a particular band-number. The O-RU shall report its capability via the parameter, run-time-tilt-offset-supported. For O-RU with run-time-tilt-offset- supported = FALSE, changing the values in offset-elevation-tilt-angle and/or offset-azimuth-tilt-angle for a specific band shall be allowed only if all tx-array-carriers/rx-array-carriers corresponding to the band is INACTIVE. When the service area change is completed in O-RU, the O-RU delivers the notification predefined-beam-tilt-offset- complete to inform the O-RU Controller which then may request to activate tx-array-carriers/rx-array-carriers in O-RU. For O-RU with run-time-tilt-offset-supported = TRUE, neither changing the state of tx-array-carriers/rx- array-carriers nor delivering notification predefined-beam-tilt-offset-complete is required. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 167 Figure 15.4.4-2: Procedure for the predefined-beam-tilt-offset ETSI ETSI TS 104 023 V17.1.0 (2026-01) 168 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.5 Dynamic beamforming control option | As option, O-RU may support dynamic beamforming control mode. Support for this type of beamforming control can be recognized in the case of weights-based dynamic beamforming from value of parameter rt-bf-weights-update-support (TRUE), and in the case of attributes-based dynamic beamforming from the value of parameter beamforming-trough- attributes-supported (TRUE), in o-ran-beamforming.yang module. In dynamic beamforming control mode DU updates content of lookup table in O-RU using eCPRI C-Plane messages. For details of eCPRI messaging, see ORAN-WG4.CUS specification, clause "Scheduling and Beamforming Commands". Dynamically updated content of lookup table is further addressed by DU in the same way as it is done for static beamforming - by requesting particular Beam ID to be applied. In case dynamic beamforming control is supported, O-RU indicates following supplementary information using parent leaf "static-properties" in o-ran-beamforming.yang module: • beamforming type (frequency domain, time domain, hybrid) • beamforming weight compression format (optional) • available range of Beam IDs, that can be dynamically updated by DU • supported time and frequency granularity for time domain and hybrid beamforming control NOTE: Neighbourhood relations between beams produced by beam IDs controlled by DU are unknown to O-RU, hence are not exposed. In the case of weights-based dynamic beamforming, to properly calculate beamforming weights DU needs to know antenna array geometry. This information DU obtains by reading the content of o-ran-uplane-conf.yang (list of tx-arrays and rx-arrays with their child parameters). Details of beamforming weight calculations are not a subject for M-Plane activity and as such are intentionally not covered in the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.6 Multiple beamId tables support | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.6.0 Introduction | The O-RU may choose to support multiple beamId tables instead of supporting a single global beamId table in the ORU by advertising O-RU support for M-Plane feature MULTIPLE-BEAMID-TABLES-SUPPORTED. The O-DU may choose to enable or disable this feature using the O-DU configurable flag multiple-beamId-tables-support-enabled. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.6.1 O-RU advertised parameters and restrictions | 1) The maximum number of beamId tables which can be supported by the O-RU is advertised by the O-RU using the parameter max-beamId-tables-supported within ru-capabilities. NOTE: If max-beamId-tables-supported is advertised as 1, it implies that O-RU supports single global beamId table. 2) Each beamId table is identified by a unique beamId table index. Multiple beamId tables supported by the O-RU are expected to be linearly indexed from 1 to 255. The list of beamId tables supported are advertised by the O-RU using a leaf-list tx-array-beamId-table-indexes/rx-array-beamId-table-indexes per capabilities[] list entry per tx-array and per rx-array respectively. 3) The maximum number of entries advertised by the O-RU in the leaf-list tx-array-beamId-table-indexes/rx- array-beamId-table-indexes shall be restricted by the O-RU level parameter max-beamId-tables-supported advertised by the O-RU which is a global value for the entire O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 169 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.6.2 O-DU configuration and restrictions | 1) When O-DU configures tx-array-carrier and/or rx-array-carrier, O-DU shall associate configured-tx-beamId- table-index/configured-rx-beamId-table-index with each tx-array-carrier and/or rx-array-carrier respectively. 2) The O-DU configured [tr]x-array-carrier(s) are expected to be configured based on parameters specified in capabilities[] list and hence configured-[tr]x-beamId-table-index value used for a given [tr]x-array-carrier is expected to be chosen from leaf-list [tr]x-array-beamId-table-indexes advertised by the O-RU per tx-array/rx-array. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.4.6.3 Restrictions, assumptions, and other impacts | 1) To ensure that legacy single beamId table is also supported by the O-RU after O-DU enables the feature MULTIPLE-BEAMID-TABLES-SUPPORTED, the first list entry in tx-array-beamId-table-indexes/rx- array-beamId-table-indexes shall always point to default global beamId table which shall be of size 32767. 2) O-RU shall use the beamId table configured for the array carrier associated with the endpoint receiving the beamId value in a C-plane message. 3) Per beamforming method beamId range is defined separately per beamId table. The new ranges are defined in defined in o-ran-beamforming.yang as a leaf-list parameter beamforming-params-for-mul-beamId-tables advertised by the O-RU. The range values initial-beam-id and max-number-of-beam-ids defined for each beamforming type shall be same for each beamId table supported by the O-RU. Also, for pre-defined beamforming a list of values, per tx-array-beamId-table-indexes/rx-array-beamId-table-indexes, is advertised by the O-RU using the leaf-list number-of-beams-per-beamId-table. Since the first list entry points to the global beamId table, the first entry in beamforming-params-for-mul-beamId-tables shall contain ranges for the global beamId table. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5 Antenna calibration | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.1 Background | Some antennas need to be calibrated to ensure their intended performance. Antenna calibration operation is an optional capability whose operation is dependent on O-RU design, i.e. different O-RUs may support different types of calibration, periodic vs on-demand, different calibration duration, short/medium/long, etc. In this clause, a common framework is defined which can accommodate various types of antenna calibration implementations. In this framework, the NETCONF client (O-DU) retrieves resource requirements for antenna calibration operation, e.g. timing and number of iterations/steps, from O-RU by getting the antenna-calibration-capabilities container defined in the o-ran-antenna-calibration YANG model. The O-DU can subscribe to antenna-calibration-required notifications to receive indications from the O-RU that calibration is required. When the O-RU indicates antenna calibration is required, or when the NETCONF Client decides to calibrate the O-RU, the NETCONF Client allocates time resources for antenna calibration and configures them in the O-RU using the start-antenna-calibration RPC request. The NETCONF client shall allocate the time resources for the calibration operation ensuring that these meet the minimum time necessary as reported by the O-RU using the antenna-calibration-capabilities. When available, the NETCONF client (O-DU) shall ensure that the frequency resources indicated in the dl-calibration-frequency-chunk and ul-calibration-frequency-chunk lists in the antenna-calibration-required notification are reserved for calibration operation, otherwise the NETCONF client shall consider that the full bandwidth of the carrier is being reserved for calibration operation. The O-RU shall perform antenna calibration operation using the time resources allocated in the antenna-calibration- start RPC and frequency resources declared in antenna-calibration-required notification and shall notify the completion of the antenna calibration operation to the notification subscriber. The O-DU should be configured to not schedule user data using the time frequency resources identified for antenna calibration operation. The O-DU may schedule data during calibration operation using time frequency resources not identified for calibration operation. When the O-DU is scheduling user data during calibration process using resources not used for calibration, it shall only schedule DL user data in DL calibration symbols and UL user data in UL calibration symbols. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 170 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.2 Overall operation | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.2.1 General | During the O-RU "start-up" procedure, the NETCONF client (O-DU) retrieves the O-RU's antenna calibration capability information including antenna calibration capability related parameters defined in o-ran-antenna- calibration.yang model. These parameters describe the O-RU's time resource requirements for calibration and the O-RU's capability of performing "self-calibration". The O-RU time resource requirements are described using the parameters number-of-calibration-symbols-per-block-dl and number-of-calibration-symbols-per-block-ul. One symbol block corresponds to a set of consecutive symbols in time required for the calibration operation, and it is the basic time unit of calibration. Sets of symbol blocks are grouped into one calibration step and the O-RU shall indicate how many symbol blocks constitute one calibration step using the number-of-calibration-blocks-per-step-dl and number-of-calibration-blocks-per-step-ul parameters. The O-RU indicates these parameters separately for downlink and uplink calibration. The O-RU shall also indicate the minimum time gap required between consecutive symbol block allocations (interval-between-calibration-block), number of calibration steps needed (number-of-calibration-steps) and the minimum required time gap between consecutive calibration step allocations (interval-between-calibration- step). Based on these parameters, the O-DU shall be able to allocate the time resources required for antenna calibration operation meeting the necessary time resources indicated by the O-RU. If the O-RU supports mixed numerology, the highest possible numerology supported by the O-RU shall be used as the common reference per component carrier according to the CUS plane definition for slot indexing with mixed numerologies. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.2.2 Initiation | Either the O-RU or O-DU may initiate calibration operation. The trigger condition for the O-DU and/or O-RU to initiate calibration is out of scope of the present document. The NETCONF client is assumed to have subscribed to the notifications defined in the o-ran-antenna-calibration YANG model. When an O-RU determines that it needs to perform antenna calibration operation, it notifies the notification subscriber using the notification antenna-calibration- required, including a list of frequency ranges corresponding to the minimum frequency resources required for calibration, or, when the O-RU supports the optional O-RU-COORDINATED-ANT-CAL feature, by using the antenna-calibration-coordinated notification. Upon reception of the antenna-calibration-required notification, the O-DU can allocate time frequency resources for calibration and can send the start-antenna-calibration RPC request, including the time resource allocation information for the antenna calibration. This operation is referred as 'O-RU initiated antenna calibration' operation. When coordinated-calibration-support is set to true, this indicates that the O-RU is able to determine a priori the time-frequency resources required for antenna self-calibration and the O-RU uses antenna-calibration-coordinated notification to indicate these to the O-DU instead of antenna-calibration-required notification. When the coordinated-calibration is supported and permitted, i.e. coordinated-calibration-support is true and coordinated- calibration-allowed is true, the O-RU may perform a coordinated self-calibration procedure. An O-RU may also report the optional capability of configured-preparation-timer-supported which indicates that it supports configuration of the preparedness timer that controls how far in advance of the coordinated self-calibration procedure the O-RU is required to send the notification of impacted resources. If configured by the NETCONF Client, the O-RU shall send the antenna-calibration-coordinated notification at least coordinated-ant-calib-prep-timer seconds before the operation of the coordinated antenna calibration procedure. If such an optional capability is not supported, the O-RU shall indicate that time-frequency resources are sent to a subscribed O-DU at least 60 seconds before the operation of the coordinated antenna calibration procedure. SFN wrap around will occur multiple times during these 60 seconds, this is handled according to statements in clause 15.5.2.4. The O-DU shall not send a start-antenna-calibration RPC request when a coordinated antenna calibration period is in progress. The O-RU is allowed to reject such a request if it is received during a coordinated antenna calibration period. An O-DU receiving an antenna-calibration-coordinated notification can beneficially use the indicated time-frequency resources to adapt its operation during the antenna calibration operation, e.g. consider the time-frequency resources as reserved for calibration. If no UL and/or DL frequency-chunk lists are provided in the notification, the O-DU may consider the full bandwidth of all configured UL and/or DL carriers reserved for calibration operation. If such U-Plane resources are scheduled by the O-DU, the operation of the O-RU may be degraded, including performance of the calibration procedure and handling of DL and UL U-plane traffic and any associated performance counters. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 171 The O-DU may also autonomously initiate calibration operation, using the same start-antenna-calibration RPC request, i.e. without receiving the antenna-calibration-required notification message from O-RU. This operation is referred as 'O-DU initiated antenna calibration' operation. If the O-RU has indicated the need for the calibration through sending the antenna-calibration-required notification, the O-DU shall consider that the use of frequency resources indicated using frequency range list within the notification as being affected during the calibration operation and if no frequency list is available, consider the full bandwidth of all configured carriers reserved is affected during calibration. After receiving "start-antenna-calibration RPC request" (antenna calibration start command), the O-RU shall send an RPC reply (antenna calibration start response) including ACCEPTED status to the NETCONF client, if the O-RU is able to start the calibration operation according to the time resources allocation information in the RPC request. Otherwise, the O-RU shall include a REJECTED status in the RPC reply, with a suitable error reason such as "resource mask mismatch with O-RU antenna calibration capability", "overlapped DL and UL masks", "insufficient memory", "O-RU internal reason" (if no other error reason matches the error condition) etc. If the O-RU does not receive a start-antenna-calibration RPC request within 60 seconds after triggering the sending of the first antenna-calibration- required notification, the O-RU shall raise a major alarm "Triggering failure of antenna calibration" (see Annex A for fault details). After the alarm is raised, the O-RU may resend the antenna-calibration-required notification multiple times. The O-RU shall not re-send the antenna-calibration-required notification in periods shorter than 60 seconds. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.2.3 Self-calibration operation | When the alarm "triggering failure of antenna calibration" alarm remains uncancelled, if self-calibration is supported and permitted, i.e. self-calibration-support is true and self-calibration-allowed is true, the O-RU may perform a self-calibration procedure. The O-RU shall wait a minimum 60 seconds after raising a major alarm and receiving no start-antenna-calibration RPC request from the NETCONF client before initiating its self-calibrate procedure. When self-calibration is not supported or not permitted, i.e. self-calibration-support is false or self-calibration-allowed is false, the O-RU may upgrade the severity of the alarm to critical according to clause 11.4. During the self-calibration, i.e. when O-RU exposes self-calibration-support with value TRUE and when O-DU sets self-calibration-allowed with value TRUE to O-RU, there could be no coordination of time-frequency resources between the O-RU and O-DU. The O-DU can continue to schedule user data during calibration process using the resources identified in antenna-calibration-required notification without impacting the operation of the calibration procedure. Scheduled user data will be affected by ongoing calibration procedure. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.2.4 Calibration completion | The O-RU shall indicate completion of all types of calibration procedures (i.e. rpc triggered, self-calibration and co- ordinated self-calibration) using the antenna-calibration-result notification (Calibration results) to the notification subscriber. If a self-calibration or co-ordinated self-calibration procedure completes but with status set to FAILURE, the O-RU may upgrade the severity of the alarm to critical. In some situations, SFN wrap around may happen causing O-DU and O-RU to interpret the 'start-SFN' parameter to point to different GPS seconds elapsed since GPS epoch. To avoid this situation, the O-DU to may decide not to schedule any user-plane data on the calibration time-frequency resources in all SFN cycles until the O-DU receives an antenna-calibration-result notification message from the O-RU. Once the calibration is complete, the O-DU schedules user data and sends C/U-Plane message as in normal operation state. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.2.5 Antenna calibration procedure | Figure 15.5.2.5-1 shows the overall operation for antenna calibration. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 172 Figure 15.5.2.5-1: Overall of antenna calibration operation ETSI ETSI TS 104 023 V17.1.0 (2026-01) 173 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.3 O-RU antenna calibration capability parameter configuration | The antenna calibration framework is a generic framework designed to support various vendor specific implementations of O-RU calibration. Therefore, the framework does not describe the details of how the O-RU calibrates its antenna, rather it defines a generic framework with necessary message flows and parameters for ensuring that the time and frequency resources required for calibration are coordinated between the O-DU and O-RU. The following parameters describe the O-RU's time resource needed for calibration: • self-calibration-support: Boolean value indicates whether O-RU is capable of supporting self-calibration. • number-of-calibration-symbols-per-block-dl: indicates how many consecutive symbols are required for DL antenna calibration operation, i.e. the size of DL Symbol-block. • number-of-calibration-symbols-per-block-ul: indicates how many consecutive symbols are required for UL antenna calibration operation, i.e. the size of UL Symbol-block. • interval-between-calibration-blocks: if a time interval is required between consecutive antenna calibration operation, this indicates the required time value as unit of symbols. A common value is used here for the intervals between DL-DL blocks, UL-UL blocks, DL-UL blocks and UL-DL blocks, which is the largest minimum interval required between any two adjacent calibration blocks. It shall be any value that O-RU implementation requires within this parameter range. • number-of-calibration-blocks-per-step-dl: indicates how many blocks are required for one step of DL antenna calibration operation. • number-of-calibration-blocks-per-step-ul: indicates how many blocks are required for one step of UL antenna calibration operation. • interval-between-calibration-steps: if a time interval is required between consecutive steps of antenna calibration operation, define indicates the required time value as unit of radio frames. It can be any value that the O-RU implementation requires within the defined parameter range. • number-of-calibration-steps: shows how many steps is required for whole DL/UL antenna calibration operation. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 174 Figure 15.5.3-1 shows the relationship between the various antenna calibration capabilities parameters described above. Figure 15.5.3-1: Relationship among Antenna Calibration Capability parameters ETSI ETSI TS 104 023 V17.1.0 (2026-01) 175 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.4 antenna-calibration-required notification parameters | If the O-RU initiates the calibration operation, the O-RU notifies the notification subscriber (O-DU) using the antenna-calibration-required notification message, including the O-RU's frequency resource requirements. The O-RU is able to indicate non-contiguous frequency "chunks" necessary for calibration using the dl-calibration-frequency- chunk and ul-calibration-frequency-chunk lists. These lists use the parameters below to describe the frequency resources required for calibration: • start-calibration-frequency-dl: indicates the lowest frequency value in Hz of the frequency range is required for DL antenna calibration operation. • end-calibration-frequency-dl: indicates the highest frequency value in Hz of the frequency range is required for DL antenna calibration operation. • start-calibration-frequency-ul: indicates the lowest frequency value in Hz of the frequency range is required for UL antenna calibration operation. • end-calibration-frequency-ul: indicates the highest frequency value in Hz of the frequency range is required for UL antenna calibration operation. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.5 Start-antenna-calibration RPC request parameters | The NETCONF Client sends the "start-antenna-calibration RPC request" including the time resource allocation parameters. These parameters indicate the exact symbols, slots, and frames that can be used for calibration. NOTE: Because the NETCONF Client (O-DU) allocates the time resources for calibration with the knowledge of UL and DL configuration, dynamic TDD operation is implicitly supported. The resource allocation information about symbol, slot, and frame are indicated using bitmasks for downlink and uplink calibration separately. The start SFN of the first calibration step is sent to the O-RU to synchronize the calibration starting point at both O-DU and O-RU. When indicated, the O-RU shall use the frequency resources indicated using the frequency ranges in the "NETCONF antenna-calibration-required notification" message for calibration. Table 15.5.5-1 lists the parameters configured in the O-RU using the "start-antenna-calibration RPC request". ETSI ETSI TS 104 023 V17.1.0 (2026-01) 176 Table 15.5.5-1: Antenna Calibration Parameters Parameters Type / Range Descriptions Symbol-bitmask-dl string Bitmask indicating DL calibration symbol within a calibration slot. First character in the string indicates first symbol, next character in the string indicates second symbol and so on. Value 1 indicates that the symbol is allocated for calibration and 0 means the symbol shall not be used for calibration. Symbol-bitmask-ul string Bitmask indicating UL calibration symbol within a calibration slot. First character in the string indicates first symbol, next character in the string indicates second symbol and so on. Value 1 indicates that the symbol is allocated for calibration and 0 means the symbol shall not be used for calibration. Slot-bitmask-dl string Bitmask indicating DL calibration slot within a calibration frame. First character in the string indicates first slot, next character in the string indicates second slot and so on. Value 1 indicates that the slot is allocated for calibration and 0 means the slot shall not be used for calibration. Slot-bitmask-ul string Bitmask indicating UL calibration slot within a calibration frame. First character in the string indicates first slot, next character in the string indicates second slot and so on. Value 1 indicates that the slot is allocated for calibration and 0 means the slot shall not be used for calibration. Frame-bitmask-dl string Bitmask indicating DL calibration frame within a calibration step. First character in the string indicates first radio frame equal to the start-SFN, next character in the string indicates the next frame and so on. Value 1 indicates that the frame is allocated for calibration and 0 means the frame shall not be used for calibration. Frame-bitmask-ul string Bitmask indicating UL calibration frame within a calibration step. First character in the string indicates first radio frame equal to the start-SFN, next character in the string indicates the next frame and so on. Value 1 indicates that the frame is allocated for calibration and 0 means the frame shall not be used for calibration. Calibration-step-size uint8 Number of frames within a calibration step. Calibration-step-number uint8 Number of calibration steps. Start-SFN unt16 SFN number of the first calibration step. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.6 Example antenna calibration operation | This clause illustrates an example of antenna calibration operation. For simplicity, the O-RU is the initiator in this example, but either O-RU or O-DU could initiate antenna calibration operation. In this example, the TDD configuration is assumed as shown in Figure 15.5.6-1. DL = Downlink slot UL = Uplink slot F = Flexible slot Figure 15.5.6-1: Example of TDD configuration This example illustrates calibration operation where an O-RU requires DL and UL antenna calibration operation in o-ran-antenna-calibration.yang with 2 calibration steps; within each step, 64 DL calibration blocks with 4 continuous DL symbols in each calibration block and 32 UL calibration blocks with 1 continuous UL symbol in each calibration block are required. Between each calibration block, a length of minimum 3 symbols interval is required, and a length of minimum 5 frames interval is required between consecutive calibration steps. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 177 Once antenna calibration operation is required by the O-RU, an antenna-calibration-required notification is sent to the notification subscriber (O-DU), including the O-RU's frequency resources requirement in a list of frequency ranges in Hz, which in this example uses a single chunk of frequencies from 1,8 GHz to 1,82 GHz. The O-DU considers that the frequency range indicated in the antenna-calibration-required notification will be subsequently used during antenna calibration. The O-DU allocates time resources for antenna calibration based on the TDD configuration together with the O-RU DL and UL antenna calibration capability, then configure the antenna calibration using the start-antenna-calibration RPC request. In this example, 64 DL calibration blocks in each calibration step are allocated in 4 frames, within each frame, 8 DL slots are allocated and within each DL slot, 2 calibration blocks are allocated for DL calibration. In parallel, 32 UL calibration blocks in each calibration step are allocated in 4 frames, within each frame, 4 UL slots are allocated and within each UL slot, 2 calibration blocks are allocated for UL calibration. To guarantee the interval between 2 calibration steps, the size of each calibration step is set to 10 frames. At least 3 symbols interval between each calibration block is also guaranteed in symbol bitmasks. The O-DU may allocate larger intervals than O-RU requires as shown in this example where a 9 symbols interval is allocated instead of the minimum of 3 symbols after second UL symbol block in all UL calibration slots. Figure 15.5.6-2: Example of message exchange ETSI ETSI TS 104 023 V17.1.0 (2026-01) 178 Figure 15.5.6-3: Time domain bitmask information from O-DU |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.5.7 Calibration with multiple timing resource sets | The O-RU may indicate its ability to support multiple time resource configuration sets for antenna calibration by support of the feature O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE in o-ran-antenna- calibration.yang module. The feature is intended to extend the antenna calibration framework to support multiple time resources instead of single time resource supported. This capability can be used by the O-RU to specify unique calibration time resources for different calibration types. O-RU which supports this capability, exposes a list of time resources (antenna-calibration-multiple-time-resource-list). O-RU indicates desired set of time resources in 'antenna- calibration-multiple-time-resource' notification using specific value of 'antenna-calibration-time-resource-index' parameter. This feature applies to O-RU initiated calibration where O-RU supporting this feature can use new notification 'antenna-calibration-multiple-time-resource' containing the parameter 'antenna-calibration-time-resource-index', defined in clause 15.5.8. Based on the index value in the notification respective antenna calibration time resource values should apply while initiating "start-antenna-calibration RPC request". O-RU can use this calibration feature only in case O-DU configured parameter 'coordinated-calibration-multiple-time-resources-allowed' is set to TRUE. NOTE: At any point in time only one calibration timing resources should be indicated the O-RU. 15.5.8 antenna-calibration-multiple-time-resource-params notification parameters If the O-RU supports O-RU-COORDINATED-ANT-CAL-MUL-TIMING-RES-CONFIG, to initiate the calibration operation, the O-RU notifies the notification subscriber (O-DU) using the antenna-calibration-multiple-time- resource-params notification message. Remaining parameter list of this notification includes the frequency resources required for calibration same as 'antenna-calibration-required' described in clause 15.5.3: • antenna-calibration-time-resource-index: key value to index the list 'antenna-calibration-variable-time- resource-list' based on the calibration duration required by the O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 179 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6 Static configuration for PRACH and SRS | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.1 Background | PRACH and raw SRS are periodic. Their location in time and frequency resources is constant for all periods. This makes it feasible to configure PRACH and raw SRS with M-Plane in a sense that handling PRACH and / or raw SRS processing by assigned low-level-rx-endpoints does not require real-time control through C-Plane messages. Static configuration of PRACH and SRS with M-Plane needs to cover following aspects: • Configuration of frequency resources assigned to PRACH / SRS • Configuration of time resources assigned to PRACH / SRS (including PRACH / SRS periodicity) • Configuration of compression, iFFT and SCS • Assignment of HW resources (low-level-rx-endpoints) for processing of PRACH / SRS Static configurations shall be provided to the O-RU as part of carrier configuration - before the configured carrier is activated. Static PRACH / SRS configuration provided for already active carrier shall be rejected by the O-RU. NOTE: In case a static-low-level-rx-endpoint exposes parameter static-config-supported with value NONE - such endpoint does not offer support for static configuration of PRACH nor SRS reception. In case the configuration provided to O-RU contains records for TDD pattern(s), PRACH patterns and/or SRS patterns, the O-RU validates consistency between patterns. Configuration where there is collision between patterns detected, shall be rejected by the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.2 Static configuration for PRACH processing | The O-RU exposes its ability to support static PRACH configuration by support of the feature PRACH-STATIC- CONFIGURATION-SUPPORTED in o-ran-module-cap.yang module. Presence of this feature means, that at least one of static-low-level-rx-endpoints offered by the O-RU supports static configuration for PRACH. From the model perspective, static PRACH configuration is supported by static-low-level-rx-endpoints having the parameter static- config-supported exposed as PRACH. Such static-low-level-rx-endpoint can be referenced by low-level-rx-endpoint designated for reception of PRACH. Specific PRACH configuration may be utilized by the low-level-rx-endpoint according to the optional parameter static-prach-configuration. NOTE: A single low-level-rx-endpoint can only reference to single instance of static-prach-configuration. However, a single static-prach-configuration may be referenced by many low-level-rx-endpoints. If parameters related to static PRACH configuration are set by NETCONF Client - real-time C-Plane control for PRACH opportunities shall not be provided to the O-RU, allowing for static configuration to be utilized. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.3 Frequency domain configuration | The meaning of frequency-related parameters is illustrated using Figure 15.6.3-1. NOTE: Parameter offset-to-absolute-frequency-center belongs to low-level-rx-endpoint. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 180 ... guard-tone-high-re guard-tone-low-re num-prach-re re-offset offset-to-absolute-frequency-center FREF numPrbc startPrbc RB #0 RB #96 RB #97 RB #98 RB #99 Other REs PRACH guard tone REs PRACH REs frequency Figure 15.6.3-1: Relation between frequency-related parameters of the PRACH occasion Relations between parameters allow to calculate startPrbc and numPrbc. For details of startPrbc and numPrbc, see O-RAN Fronthaul Working Group; Control, User and Synchronization Plane Specification [2], clause 7.5.3.2. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.4 Time domain configuration | Meaning of parameters is illustrated using Figure 15.6.4-1. time fn = 0 time-offset cp-length symbol-duration symbol-duration number-of-repetitions PRACH CP PRACH Symbol PRACH Symbol gp-length PRACH GP Figure 15.6.4-1: Timing-related parameters of single PRACH occasion Figure 15.6.4-1 shows a single PRACH occasion containing 2 PRACH Symbols. Figure 15.6.4-2: Timing-related parameters of one PRACH pattern Figure 15.6.4-2 shows a single PRACH pattern containing two occasions of 2 PRACH Symbols (reuse of occasion shown on figure for single PRACH occasion for simplified view). The corresponding parameters for Figure 15.6.4-2 are: ("number-of-prach-occasions" = 2, "number-of-repetitions" = 2). NOTE 1: time-offset is defined with reference to parameters frame-number and sub-frame-id under static-prach-configuration. This parameter applies for the first occasion of a PRACH pattern. For subsequent occasions of the same PRACH pattern, the O-RU utilizes the parameters cp-length, gp-length and beam-id to determine the time boundaries. The parameters are taken from the list occasion-parameters such that, the first occasion uses the first set of elements from the list. Subsequent occasions use consecutive sets of parameters. The number of sets of parameters in this list is equal to value of the parameter number-of-occasions. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 181 One static-prach-configuration instance allows to configure a set of PRACH patterns. For a single PRACH configuration, all corresponding PRACH patterns repeat over the period defined by the pattern-period parameter for such PRACH configuration. The PRACH patterns of single PRACH configuration shall not overlap in terms of time and frequency. At most one PRACH pattern shall start in a subframe (subframes in different frames are distinguished). PRACH pattern shall not cross boundary between subframes except PRACH pattern for long PRACH format with one occasion that spans boundary between subframes. An O-RU shall reject any configuration where the number of patterns in single static PRACH configuration exceeds the number exposed by capability parameter max-prach-patterns in o-ran-uplane-conf.yang module. CP1 sym0 sym1 sym2 sym3 GP Frame #0 Frame #1 Frame #2 Frame #3 Frame #4 Frame #5 Frame #6 Frame #7 Frame #8 Frame #9 Frame #10 Frame #11 Frame #12 Frame #13 Frame #14 Frame #15 Frame #16 Frame #17 Frame #18 Frame #19 CP2 sym0 sym1 sym2 sym3 GP CP3 sym0 sym1 sym2 sym3 GP CP1 sym0 sym1 sym2 sym3 GP sym4 sym5 CP2 sym0 sym1 sym2 sym3 GP sym4 sym5 CP1 sym0 sym1 sym2 sym3 GP sym4 sym5 CP2 sym0 sym1 sym2 sym3 GP sym4 sym5 prach-pattern #1 prach-occasion beam-id #1 beam-id #1 beam-id #1 beam-id #4 beam-id #2 beam-id #3 beam-id #5 prach-pattern #2 sub-frame x sub-frame y time-offset #1 time-offset #2 CP1 sym0 sym1 sym2 sym3 GP CP2 sym0 sym1 sym2 sym3 GP CP3 sym0 sym1 sym2 sym3 GP beam-id #1 beam-id #3 beam-id #3 beam-id #3 beam-id #4 beam-id #4 beam-id #4 beam-id #4 beam-id #4 beam-id #5 beam-id #5 beam-id #5 beam-id #5 beam-id #5 beam-id #1 beam-id #1 beam-id #1 beam-id #2 beam-id #3 beam-id #1 beam-id #3 beam-id #3 beam-id #3 beam-id #4 beam-id #5 beam-id #4 beam-id #4 beam-id #4 beam-id #4 beam-id #4 beam-id #5 beam-id #5 beam-id #5 beam-id #5 beam-id #5 beam-id #2 beam-id #2 beam-id #2 beam-id #2 beam-id #2 beam-id #2 Figure 15.6.4-3: Example PRACH configuration formed of two PRACH patterns having different number of PRACH Symbols NOTE 2: PRACH occasions are expanded for visual clarity. NOTE 3: Figure 15.6.4-3 shows a theoretical configuration - not necessarily standardised by 3GPP. This is to demonstrate the flexibility of the solution of static PRACH configuration offered by M-Plane configuration. The above configuration uses 2 prach-patterns: • Pattern #1 is having: number-of-repetitions = 4, number-of-occasions = 3 • Pattern #2 is having: number-of-repetitions = 6, number-of-occasions = 2 For the PRACH configuration shown in Figure 15.6.4-3, the parameter pattern-period = 10 as this is the number of frames after which PRACH pattern repeats. NOTE 4: Such a static PRACH configuration can be supported by static-low-level-rx-endpoints having parameter max-prach-patterns ≥ 2 as this configuration consists of 2 patterns. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 182 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.5 Operation | Static PRACH configuration shall be set and rx-endpoints shall be linked to it before rx-array-carrier activation. On carrier activation, the O-RU starts receiving RF signals corresponding to the configured prach-patterns list. Specifically, the O-RU receives RF signals corresponding to the prach-pattern p when: mod( , pattern-period ) = frame-numberp, and = sub-frame-idp, and t = time-offsetp. where: is the system frame number, mod( x, y ) is remainder of division of x by y, is the subframe number within system frame, t is the time since start of subframe, frame-number, sub-frame-idp and time-offsetp are parameters of prach-pattern p, pattern-period is a parameter of PRACH configuration. Offset to the start of pattern periods can be configured either in low-level-rx-endpoint or in static-prach-configuration with sfn-number parameter. If the value is provided in static-prach-configuration, then it takes the precedence over the value configured in low-level-rx-endpoint. Once the RF signal corresponding to the PRACH Symbol in PRACH occasion is received and processed, the O-RU sends the corresponding IQ values in a U-plane message or messages with header fields set as follows: frameId = mod( floor( / pattern-period ) • pattern-period + frame-numberp, 256 ) NOTE: This corresponds to value captured when prach-pattern p started. subframeId = sub-framep, slotId = zero-based PRACH occasion number within PRACH pattern, symbolId = zero-based PRACH Symbol number within PRACH occasion, sectionId = 4095, startPrbu = floor( ( re-offsetp + guard-tone-low-re ) / 12 ), numPrbu = ceil( (re-offsetp + guard-tone-low-re + num-prach-re ) / 12 ) - startPrbu. Where: is the system frame number, mod( x, y ) is remainder of division of x by y, floor( x ) is largest integer smaller than or equal to x, ceil( x ) is smallest integer greater than or equal to x, frame-numberp, sub-frame-numberp and re-offsetp are parameters of prach-pattern p. pattern-period, guard-tone-low-re and num-prach-re are parameters of PRACH configuration. If data section is subdivided due to application level fragmentation, resulting values of startPrbu and numPrbu shall be calculated as per general rules. If multiple PRACH Symbols are scheduled at the same time at different re-offset frequencies, the O-RU shall send corresponding data sections in one U-Plane message following message size restrictions. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 183 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.6 Static configuration for raw SRS processing | The O-RU exposes its ability to support static raw SRS configuration by support of the feature SRS-STATIC- CONFIGURATION-SUPPORTED in o-ran-module-cap.yang module. Presence of this feature means, that at least one of static-low-level-rx-endpoints offered by the O-RU supports static configuration for raw SRS reception. From the model perspective, static SRS configuration is supported by static-low-level-rx-endpoints having the parameter static-config-supported exposed as SRS. Such static-low-level-rx-endpoint can be referenced by a low-level-rx- endpoint designated for reception of SRS. Specific SRS configuration may be utilized by the low-level-rx-endpoint according to the optional parameter static-srs-configuration. NOTE: A single low-level-rx-endpoint can only reference to single instance of static-srs-configuration. However, a single static-srs-configuration can be referenced by many low-level-rx-endpoints. If parameters related to static SRS configuration are set by NETCONF Client - real-time C-Plane control for SRS shall not be provided to the O-RU, allowing for static configuration to be utilized. Static SRS configuration is used to configure NDM (Non-Delay Managed) raw SRS (Sounding Reference Signal) patterns in a static manner, such that raw SRS U-Plane traffic can be processed by the O-RU without receiving C-Plane messages conveying real-time raw SRS configuration. Raw SRS may capture non-beamformed (beam-id = 0) or beamformed (beam-id != 0) signals and uses non-delay managed U-Plane messages. One static-srs-configuration instance allows to configure a set of SRS patterns. For a single SRS configuration, all SRS patterns repeat over the period defined by pattern-period parameter for such SRS configuration. SRS patterns corresponding to a single SRS configuration shall not overlap in terms of time and frequency. An O-RU shall reject any configuration where the number of patterns in single static SRS configuration exceeds the number exposed by capability parameter max-srs-patterns in o-ran-uplane-conf.yang module. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.6.7 Operation | Static SRS configuration shall be set and rx-endpoints shall be linked to it before rx-array-carrier activation. On carrier activation, the O-RU starts receiving RF signals corresponding to the configured srs-patterns list. Specifically, the O-RU receives RF signal and sends corresponding U-plane messages as if, for each configured srs-pattern p, each rx-endpoint linked with the SRS configuration received C-plane messages with fields: dataDirection = 0 (RX), payloadVersion = 0, filterIndex = 0, frameId = mod( , 256 ), subframeId = sub-frame-idp, slotId = slot-idp, startSymbolId = start-symbol-idp, numberOfSections = 1, sectionId = 4095, rb = 0, symInc = 0, startPrbc = start-prbcp, numPrbc = num-prbcp, reMask = 0xFFF, numSymbol = num-symbolp, ef=0, ETSI ETSI TS 104 023 V17.1.0 (2026-01) 184 beamId = beam-idp, where: is the system frame number, mod( x, y ) is remainder of division of x by y, sub-frame-idp slot-idp, start-symbol-idp, beam-idp, start-prbcp and num-prbcp are parameters of srs-pattern p. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.7 TDD pattern configuration | The O-RU exposes its ability to support TDD pattern configuration by support of the feature CONFIGURABLE-TDD- PATTERN-SUPPORTED in o-ran-module-cap.yang module. Presence of this feature means, that at least one of static-low-level-[tr]x-endpoints offered by the O-RU supports configuration for TDD pattern, so that these static-low- level-[tr]x-endpoints can be used (through low-level-[tr]x-endpoints) by [tr]x-array-carriers having configurable TDD pattern assigned. Configured TDD pattern shall not be violated by C-Plane and U-Plane messages. In case configuration provided to ORU contains records for TDD pattern(s), PRACH patterns and/or SRS patterns, O-RU validates consistency between patterns. Configuration where there is collision between patterns detected, shall be rejected by O-RU. From the model perspective, configuration for TDD pattern is supported by static-low-level-[tr]x-endpoints having parameter configurable-tdd-pattern exposed as TRUE. Such static-low-level-[tr]x-endpoint can be respectively referenced by low-level-[tr]x-endpoint designated to serve for [tr]x-array-carrier having preconfigured TDD pattern assigned. Specific configuration of the TDD pattern may be utilized by [tr]x-array-carrier according to the optional parameter configurable-tdd-pattern. Absence of leaf configurable-tdd-pattern at [tr]x-array-carrier means, that such [tr]x-array-carrier has no configurable-tdd-pattern assigned. A configurable TDD pattern can be assigned to a [tr]x-array-carrier under the condition, that all static-low-level-[tr]x- endpoints serving such an [tr]x-array-carrier expose value of capability configurable-tdd-pattern-supported as TRUE. A single [tr]x-array-carrier can only reference to single instance of configurable-tdd-pattern. Whereas a single configurable-tdd-pattern shall be referenced by all cooperating [tr]x-array-carriers serving for a specific [tr]x-array. Linkage between tx-array-carriers and rx-array-carriers configured to use the same configurable-tdd-pattern shall be assured by the entity responsible for configuration provisioning to O-RU. For example, ensuring that all cooperating [tr]x-array-carriers use static-low-level-[tr]x-endpoints (through low-level-[tr]x-endpoints) having the same value of tdd-group. The practical implication of this is that static-low-level-[tr]x-endpoints exposing the same value of parameter tdd-group shall be used by low-level-[tr]x-endpoints serving for [tr]x-array-carriers having the same TDD switching points and the same directions to the air interface granted by TDD patterns they are configured to use. NOTE 1: M-Plane model allows an O-RU to be configured with more than one TDD patterns. This is capability can be used by O-RUs having more than one [tr]x-array. A single TDD pattern configuration consists of list of records. Each single record contains details for frame-offset and direction of signal that shall be applied at the moment a specific frame-offset occurs at air interface. Supported directions are UL (uplink), DL (downlink) and GP (neither uplink nor downlink). NOTE 2: Assignment of configurable-tdd-pattern to a [tr]x-array-carrier is only possible in case all following conditionals are met: O-RU supports feature CONFIGURABLE-TDD-PATTERN-SUPPORTED. all static-low-level-[tr]x-endpoint configured to serve for a specific [tr]x-array-carrier have capability configurable-tdd-pattern set to TRUE. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 185 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.8 C-Plane message limits | The O-RU exposes its ability to support C-Plane message limits by including support of the feature CPLANE- MESSAGE-PROCESSING-LIMITS in o-ran-wg4-features.yang module. Refer to clause 7.8.2.2 of CUS-Plane specification [2] to understand details of this feature. The presence of this feature means, that in addition to an O-RU's "per-endpoint processing limits" e.g. endpoint-section-capacity, endpoint-beam-capacity, endpoint-prb-capacity, an O-RU may also have "per-cplane message limits". To support this feature on a per endpoint basis, a new flag 'cplane- message-processing-limits-required' is added to 'endpoint-types' to indicate an endpoint's requirement to support C-Plane message processing limits. The flag shall be set to true for the endpoints to which C-Plane message processing limits apply. An additional configuration flag 'cplane-message-processing-limits-enabled' is added to low-level-[tr]x- endpoints (applicable only for endpoints to which C-Plane limit requirement is exposed by O-RU) to enable the O-DU to use this feature on a per endpoint basis. 1) If the O-DU supports C-Plane message processing limits, it can choose to indicate it adheres to the limits by configuring schema node 'cplane-message-processing-limits-enabled= true'. In such case, the O-DU shall follow limits specified by the parameters, e.g. 'max-beams-per-slot-with-cplane-limits' and 'max-highest- priority-sections-per-slot-with-cplane-limits' when forming C-Plane messages. 2) If O-DU does not support C-Plane message processing limits by configuring schema node 'cplane-message- processing-limits-enabled= false' OR O-RU does not indicate it supports the CPLANE-MESSAGE- PROCESSING-LIMITS YANG feature, no C-Plane message limits shall apply and O-RU continues to use endpoint capacity limits specified in existing endpoint by per-endpoint limits e.g. endpoint-section-capacity, endpoint-beam-capacity, endpoint-prb-capacity. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 15.9 Advanced endpoint capability report | Both endpoint-types and endpoint-capacity-sharing-groups provide an optional method for advanced endpoint capability and capacity reporting by using supported-configuration-combinations. The report is provided through supported-configuration-combinations which allows the O-RU to convey its supported configurations of endpoint UL/DL signal transmission/reception and processing as a function of different combinations. In short, the O-RU may report a different processing capacity dependent on a specified set of configurations. This clause describes the data structure of supported-configuration-combinations and provides examples of its usage. Figure 15.9-1 depicts the data structure in a condensed format. As shown supported-configuration-combinations is a three-level list consisting of the levels: supported-configuration-combinations, set, config. The parameter supported-configuration-combinations will henceforth be referred to as combination for the sake of brevity. An entry of config provides a specific configuration with several parameters to represent the processing capacity of one or more internal components of the O-RU when these are configured to a certain state via endpoint mapping. The parameters carrier-types and center-from-freqoffset may be omitted to indicate that their value does not affect the O-RU's resource usage, i.e. a wildcard entry. An entry of set provides a list of one or more config entries. The value of max-overlapping-instances indicates the number of config entries which may be activated simultaneously in time, including multiple activations of the same config entry within a set. When max-overlapping-instances is 1 the O-DU can only utilize one config entry from the set. Simultaneously overlapping is defined by the DL or UL signals overlapping in time when transmitted or received by the O-RU at the antenna connector. The config entries are indirectly activated when the O-RU receives C-plane messages which can be processed by the capabilities reported in those entries. NOTE: When Section Type 3 C-plane messages are received the O-RU may rely on fields such as filterIndex, timeOffset, frameStructure and freqOffset to map to internal processing resources. An entry of combination provides a list of one or more sets from which one or more config entries (dependent on the value of max-overlapping-instances of the specific set) may be activated at an overlapping moment in time. At any overlapping moment in time only a single combination entry shall be applied to the O-RU. I.e. config entries from different combination entries shall not be activated simultaneously. The combination entry which the O-DU intents to utilize shall be conveyed to the O-RU via combination-configuration as part of the general carrier configuration procedure. Optionally the O-DU may convey its intent to utilize a subset of sets and configs of the selected combination via the same parameter. If the list of configurations is not populated by the O-DU, the O-RU shall assume that the combination entry will be utilized to the greatest extent possible. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 186 In all cases the activation of a particular configuration is performed indirectly by a combination of M-plane configuration and received C-plane messages as they are mapped to the internal processing resources of the O-RU. In cases where conflicts arise between the capabilities of the endpoint conveyed via supported-configuration- combinations and other endpoint level capabilities it is the most restrictive capacity restriction option that shall apply. In other words, all applicable restrictions shall be met. Once the supported combinations are advertised by the O-RU, the O-DU is expected to comply with a given combination capability advertised by the O-RU. However, if the O-DU for any reason violates the O-RU advertised capabilities, the O-RU shall send an alarm notification, e.g. 'fault-id = 31' to subscribers following the procedures defined in clause 11 and Table A.1-1. combination[] set[] config[] scs max-prb-range filter-pass-bandwidth carrier-types center-from-freqoffset max-overlapping-instances supported-filter-indices Figure 15.9-1: Supported configuration combinations group list overview The config listed parameter center-from-freqoffset indicates whether deriving a new carrier center from a C-plane section type 3 message (as defined in [2] clause 15.4.1) is expected to be enabled for the activate configuration. It shall be enabled via the endpoint level parameter center-from-freqoffset-enabled. If an endpoint supports this capability, it shall report so by setting center-from-freqoffset-supported to TRUE. The config listed parameter filter-pass-bandwidth conveys the maximum size of the passband filter relative to the host carrier center, as defined by center-of-channel-bandwidth, and therefore defines the frequency range from which PRBs can be extracted with the endpoint. In turn, the O-DU configures the expected occupied bandwidth to the O-RU via occupied-bandwidth, e.g. refer to [2] clause 15.4.1, 15.4.2 and 15.4.3. A list of supported filter pass bandwidths is provided in supported-filter-pass-bandwidths. The config leaf-list parameter supported-filter-indices conveys the filter indices supported or intended by the config. As an example, the O-RU may use the parameter to restrict an endpoint to only support NB-IoT or a specific NB-IoT channel such as NPUSCH. A static-low-level-rx-endpoint intended to support a NB-IoT carrier with an NPUSCH and two NPRACH channels may be conveyed in a single combination entry, as illustrated in Figure 15.9-2. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 187 combination[0] set[0] config[0] scs=15 max-prb-range=1 carrier-types=lte filter-..bandwidth set[1] config[0] scs=3.75 max-..overlap..=1 Maximum available configuration: set[0]config[0] + set[1]config[0]x2 One set-config is an endpoint instance of configuration/ capacity Multiple instances may be supported with max- overlapping-instances center-from-freqoffset=TRUE max-prb-range=4 carrier-types=lte filter-..bandwidth center-from-freqoffset=TRUE max-..overlap..=2 Figure 15.9-2: Example a static-low-level-rx-endpoint indirectly indicating support for a single NB-IoT carrier support with one NPUSCH and two NPRACH channels A static-low-level-rx-endpoint may additionally support an LTE carrier and PRACH, however, not at the same time as an NB-IoT carrier. In which case, an additional combination entry may be listed to convey support for either NB-IoT or an LTE carrier as shown in Figure 15.9-3. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 188 combination[0] set[0] config[0] scs=15 max-prb-range=1 carrier-types=lte filter-..bandwidth set[1] config[0] scs=3.75 max-..overlap..=1 Maximum available configuration: set[0]config[0] + set[1]config[0]x2 Or the alternative combination: comb[1]set[0][config[0]+ comb[1]set[1][config[0/1] Center-from-freq-offset set to TRUE implies NB-IoT due to new indication of carrier center center-from-freqoffset=TRUE max-prb-range=4 carrier-types=lte filter-..bandwidth center-from-freqoffset=TRUE max-..overlap..=2 combination[1] set[0] config[0] scs=15 max-prb-range=100 carrier-types=lte filter-..bandwidth set[1] config[0] scs=1.25 max-..overlap..=1 center-from-freqoffset=FALSE max-prb-range=72 carrier-types=lte filter-..bandwidth center-from-freqoffset=FALSE max-..overlap..=1 config[1] scs=7.5 max-prb-range=14 carrier-types=lte filter-..bandwidth center-from-freqoffset=FALSE Figure 15.9-3: Example A static-low-level-rx-endpoint indirectly indicating support for either a NB-IoT and LTE carrier, however, not both at the same time Finally, an endpoint capability report may be structured to indicate a large degree of flexibility in terms of active configs as illustrated in combination-1 of Figure 15.9-4 which shows any three combinations of the listed configs may be utilized. Whereas combination-0 can only support a single instance of a 15 kHz channel. combination[0] set[0] config[0] scs=15 max-prb-range=1 carrier-types=lte filter-..bandwidth set[1] config[0] scs=3.75 max-..overlap..=1 center-from-freqoffset=TRUE max-prb-range=4 carrier-types=lte filter-..bandwidth center-from-freqoffset=TRUE max-..overlap..=2 combination[1] set[0] config[0] scs=15 max-prb-range=1 carrier-types=lte filter-..bandwidth config[1] scs=3.75 max-..overlap..=3 center-from-freqoffset=TRUE max-prb-range=4 carrier-types=lte filter-..bandwidth center-from-freqoffset=FALSE Figure 15.9-4: Example A static-low-level-rx-endpoint indirectly indicating support for a NB-IoT carrier with more flexibility in the right-hand side combination ETSI ETSI TS 104 023 V17.1.0 (2026-01) 189 15.10 U-Plane message limits O-RU may indicate that its endpoints have U-Plane message processing limits, as specified in clause 8.5.1 of [2], by including feature UPLANE-MESSAGE-PROCESSING-LIMITS in o-ran-wg4-features.yang. The presence of this feature means, an O-RU may expose data node uplane-message-processing-limits-required per static-low-level-tx- endpoint via endpoint-types. uplane-message-processing-limits-required indicates whether an endpoint has U-Plane message processing limits or not. 1) If O-DU supports feature UPLANE-MESSAGE-PROCESSING-LIMITS and supports the leaf max- section-headers-per-uplane-message , it should set uplane-message-section-header-limit-enabled to 'true' and should comply with O-RU limit specified by the parameters max-section-headers-per-uplane- message when forming U-Plane messages. 2) When the O-DU does not configure the leaf uplane-message-section-header-limit-enabled to 'true', O-RU shall process the U-Plane messages that exceed the limits even though the O-RU may operate with degraded performance or capacity, (refer to [2] clause 8.5.1 for more details). 3) When U-Plane message exceeds the limit reported by O-RU, O-RU may raise alarm to indicate the degraded performance or capacity. For details about alarm notification 'fault-id = 31', refer to Table A.1-1. 15.11 DRMS-BF capability and configuration management 15.11.1 Overview The DMRS based beamforming method is beamforming method where the O-RU computes beamforming or beamforming + equalization weights based on DMRS configuration from O-DU. The DMRS-BF feature comprises of new O-RU advertised feature capabilities, O-RU advertised limits and O-DU configurations which are described in detail in the following clauses. 15.11.2 O-RU advertised capabilities and capacity limits To support the DMRS based beamforming feature O-RU advertises to the O-DU a set of capability parameters which are mandatory to be supported by the O-RU and few other are optional. To support DMRS-BF new section type, new section extensions and various new functionalities have been added to the fronthaul CUS-Plane specification, each sub-functionality requires the O-RU to advertise a set of capabilities and maximum capacity limits. Below table intends to summarize all the parameters advertised by the O-RU and there scope i.e. at what granularity the parameters are advertised by the O-RU. Refer to Table C.2-1, feature numbers 67 to 77 and 81 for DMRS-BF related features in o-ran- wg4-features.yang. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 190 Table 15.11.2-1: DMRS-BF O-RU advertised capabilities and capacity limits S.No (feature num.param num) O-RU advertised DMRS-BF Capability/Limit parameter name Scope of parameter 1.1 rrm-meas-supported Per endpoint-type 1.2 max-ipn-unalloc-reports-supported Per endpoint-type 1.3 max-ipn-unalloc-symbols-supported Per endpoint-type 1.4 max-ipn-alloc-reports-supported Per endpoint-type 1.5 alloc-ipn-per-dmrs-sym-grp-supported Per endpoint-type 2.1 equalization-data-scaling O-RU level 2.2 eq-scale-offset-min Per endpoint-type 2.3 eq-scale-offset-max Per endpoint-type 3.1 supported-symb-reorder-capability Per endpoint-type 3.2 max-num-symbol-reordering-pattern-per-slot Per endpoint-type 3.3 up-symbolId-type-supported Per endpoint-type 4.1 ta3-min-2g Per non-default-ru-delay-profile and ru-delay-profile 4.2 ta3-max-2g Per non-default-type-ru-delay- profile and ru-delay-profile 5.1 sinr-reporting-supported Per endpoint-type 5.2 supported-sinr-resolutions sinr-max-data-layers, sinr-per-prb (listleaf), sinr-slot-mask (listleaf) Per endpoint-type 5.3 sinr-reference-level-min Per endpoint-type 5.4 sinr-reference-level-max Per endpoint-type 5.5 sinr-compression-method Per endpoint-type Per entry in supported-sinr- compression-methods 5.6 sinr-bitwidth Per endpoint-type Per entry in supported-sinr- compression-methods 5.7 sinr-block-size Per endpoint-type Per entry in supported-sinr- compression-methods 6.1 supported-entry-types Per endpoint-type 6.2 max-user-groups-per-slot Per endpoint-type, per group of endpoints sharing a capacity 6.3 max-entries-per-slot Per endpoint-type, per group of endpoints sharing a capacity 6.4 max-dmrs-configs-per-user-group-incl-first-last-prb Per endpoint-type 6.5 max-dmrs-configs-per-user-group-excl-first-last-prb Per endpoint-type 6.6 dmrs-symbol-mask Per endpoint-type 6.7 max-dmrs-ant-port-number Per dmrs-symbol-mask 6.8 max-user-data-layers Per dmrs-symbol-mask 6.9 list of supported pairs of { low-papr-type and hopping-mode } Per endpoint-type 6.10 list of supported pairs of { d-type, pusch-dmrs-muxing-supported } Per endpoint-type 6.11 different-transform-precoding-in-user-group-supported Per endpoint-type 6.12 different-cdm-without-data-in-user-group-supported Per endpoint-type 7.1 se-10-bgt-11b-supported Per endpoint-type 7.2 se10-member-candidate-list Per endpoint 8 user-group-self-assembly-mode Per endpoint-type 9 continuity-block-sizes-supported Per endpoint-type 10.1 ueid-max-layer-bits O-RU level 10.2 max-num-ues-supported O-RU level 10.3 max-num-ueids O-RU level 11 simultaneous-sinr-and-dmrs-sending-supported Per endpoint-type 12.1 ue-time-partial-overlap-supported Per endpoint-type 12.2 ue-freq-partial-overlap-supported Per endpoint-type 13 max-user-groups-per-ue-in-time Per endpoint-type ETSI ETSI TS 104 023 V17.1.0 (2026-01) 191 15.11.3 O-DU configurations of parameters Following O-RU capability advertisement, the O-DU is required to configure a set of parameters with restrictions on the scope of configuration. Below table intends to summarize all the parameters configured by the O-DU to enable the sub-functionalities/features advertised by the O-RU. Along with the parameter list the table also captures the scope of configuration of all the parameters to be configured by the O-DU. Table 15.11.3-1: DMRS-BF configurations S.No (feature num.param num) Configuration parameter Configuration Scope 1.1 rrm-meas-enabled Per endpoint 2.1 eq-scale-offset-config Per endpoint 2.2 eq-scale-offset-used Per endpoint 3.1 se26-usage-enabled Per endpoint 4.1 config-symb-reorder-method Per O-RU 4.2 config-up-symbolId-type Per O-RU 5.1 sinr-reporting-enabled Per endpoint 5.2 sinr-per-prb Per endpoint 5.3 sinr-slot-mask Per endpoint 5.4 sinr-reference-level-config Per endpoint 5.5 sinr-reference-level-used Per endpoint 5.6 sinr-compression-method Per endpoint 5.7 sinr-bitwidth Per endpoint 5.8 sinr-block-size Per endpoint 6 user-group-mode Per rx-array-carrier 7.1 continuity-block-size-configured Per rx-array-carrier 8.1 ueid-layer-bits-configured Per O-RU 9.1 port-reduced-dmrs-data-sending-enabled Per rx-array-carrier 9.2 point-a-offset-to-absolute-frequency-center Per rx-array-carrier 10 ueid-persistence-enabled Per O-RU 11 bf-method Per endpoint 15.11.4 DMRS-BF-EQ target value configuration For DMRS-BF-EQ, there are two parameters, eq-scale-offset-config (see clause 8.1.3.4 in CUS-plane specification [2]) and sinr-reference-level-config (see clause 7.2.10 in CUS-plane specification [2]), that use the method of target value configuration and used-value retrieval described in clause 9.1.9. The O-DU configures a target value for each of the parameters eq-scale-offset-config and sinr-reference-level-config as part of endpoint creation or reconfiguration including these two parameters. It is important for the O-DU to know (with sufficiently high precision) the actual values used, but it is possible that the O-RU cannot implement the target values precisely. The O-RU will instead report and use the value it is able to support but close to the target value. To report the used-values, the O-RU sets the read-only parameters eq-scale-offset-used and sinr-reference-level-used to the values that the O-RU used. The O-DU can retrieve the used-values before carrier activation and will then be aware of the precise value (to the precision of the M-plane data formats for each used-value) used by the O-RU. Refer to clause 9.1.9 for procedure details. 15.12 Description of feature SE10-MEMBER-CANDIDATE-LIST Support for the feature SE10-MEMBER-CANDIDATE-LIST enables the O-RU to explicitly advertise one or multiple entries in the list se10-member-candidate-[tr]x-lists. This list is advertised separately for TX endpoints and RX endpoints at the O-RU level. Each static-low-level-tx-endpoint and each static-low-level-rx-endpoint supporting Section Extension 10 points to one entry from the list se10-member-candidate-tx-lists/ se10-member-candidate-rx- lists using the parameter se10-member-candidate-list respectively. By virtue of an endpoint belonging to a given se10- member-candidate-[tr]x-list entry, the endpoints can be used as member eAxC_ID entry in the O-DU configured [tr]x-eaxc-id-group. Below tables explains the advertisement of shared list by the O-RU and association of shared list entry per endpoint. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 192 Table 15.12-1: Example of O-RU level global member list advertisement se10-member-candidate-rx-lists index Member static-low-level-rx-endpoint of member-candidates list 1 static-low-level-rx-endpoint-1 static-low-level-rx-endpoint-2 static-low-level-rx-endpoint-3 static-low-level-rx-endpoint-4 (note) static-low-level-rx-endpoint-8 (note) 2 static-low-level-rx-endpoint-3 static-low-level-rx-endpoint-5 static-low-level-rx-endpoint-6 static-low-level-rx-endpoint-7 static-low-level-rx-endpoint-8 (note) static-low-level-rx-endpoint-9 NOTE: These endpoints may also be representative endpoints, see table 15.12-2. Table 15.12-2: Example of O-RU advertised static-low-level-rx-endpoint and a given member-candidates list association O-RU advertised representative endpoint (endpoints supporting SE-10) Associated se10-member-candidate-[tr]x-lists index static-low-level-rx-endpoint-4 1 or 2 (note) static-low-level-rx-endpoint-8 1 or 2 NOTE: In this example static-low-level-rx-endpoint-4 can represent list se10-member-candidate-rx-lists index 2 but cannot be a member of se10-member-candidate-rx-lists index 2. Based on se10-member-candidate-list declared for endpoint that support Section Extension 10 by the O-RU, the O-DU configures a list tx/rx-eaxc-id-group, where each entry of this list comprises of representative-tx/rx-eaxc-id as the key/index of the list, where each list entry comprises of a list of member-tx/rx-eaxc-id (s) from one specific entry advertised in se10-member-candidate-list[] by the O-RU. NOTE: O-DU while configuring a given rx-eaxc-id-group[] entry, the O-DU excludes representative endpoint from the configured member-list Table 15.12-3: Example for O-DU configured representative and associated member list based on O-RU advertised se10-member-candidate-list-ref[] rx-eaxc-id-group[] indexed by representative-rx-eaxc-id as key O-DU configured member-rx-eaxc-id within rx-eaxc-id-group[] entry with members picked from se10-member-candidate-list[] list advertised by the O-RU low-level-rx-endpoint-4 low-level-rx-endpoint-1 low-level-rx-endpoint-2 low-level-rx-endpoint-3 low-level-rx-endpoint-8 low-level-rx-endpoint-8 low-level-rx-endpoint-5 low-level-rx-endpoint-6 low-level-rx-endpoint-7 low-level-rx-endpoint-9 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16 Licensed assisted access | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.1 Introduction | Licensed-Assisted Access (LAA) leverages the Carrier-Aggregation (CA) functionality. With LAA, CA is performed between licensed and unlicensed Component Carriers (CCs). This enables the LAA system to opportunistically benefit from using unlicensed spectrum (e.g. UNII bands in the 5 GHz spectrum) to enhance the aggregated capacity of the O-RU with the objective of enhancing the downlink throughput. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 193 Several modifications in the RAN are needed to enable LAA in the O-DU and O-RU such as Listen-Before-Talk (LBT), discontinuous transmission, carrier-selection, Discovery Reference Signal (DRS) transmission, etc. This clause is focused on the LAA-related messages and procedures needed in the M-plane. The C-plane related messages are defined in clause 7.2.5.2 of the CUS-plane specification [2]. This version of the M-plane spec supports only LAA based on Rel. 13 of the 3GPP specs, where transmission on the unlicensed spectrum can be done only in the downlink direction. The support of eLAA Rel. 14 (i.e. enabling UL transmission on the unlicensed spectrum) may be included in a later version of the M-plane spec. The modifications at M-plane to Support LAA can be summarized as follows: 1) LAA-initiation process: O-DU learns about O-RU capabilities and configures it. - O-RU LAA Support: The O-RU indicates it supports LAA by including support for the "urn:o-ran:laa:x.y" and "urn:o-ran:laa-operations:x.y" namespaces in its ietf-yang-library model as specified in IETF RFC 8525 [59]. - O-RU LAA Capability Information: When the LAA feature is enabled, leafs corresponding to LAA-related O-RU capabilities, such as the number of supported LAA SCarriers, maximum LAA buffer size, etc., are conveyed via the M-plane to the O-DU as part of the o-ran-module-cap.yang module. - O-RU LAA Configuration: The NETCONF client configures the unlicensed LAA component carrier with the LAA-related parameters such as the energy-detection threshold, DRS measurement timing configuration (DMTC) period, etc. as part of the o-ran-uplane-config.yang module. The configuration of the number of LAA SCarriers, multi-carrier type, etc. is performed using the o-ran-laa.yang Module. - For explanation of the LAA-initiation process, refer to Figure 6.1-1 in clause 6, where the O-RU LAA capability info is conveyed within the "Retrieval of O-RU information" step, while the O-RU LAA configurations are conveyed in "Configuring the O-RU operational parameters" step in Figure 6.1-1. 2) Carrier-selection: Selecting the best channel in the unlicensed band, both initially and dynamically over time, as illustrated in Figure 16.1-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 194 Figure 16.1-1: Carrier-Selection Call-flow |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.2 LAA-initiation process | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.2.1 LAA module capabilities | During LAA-initiation, the O-RU reports its LAA capabilities to the NETCONF client. These capabilities are sent at the start up as part of the o-ran-module-cap.yang module. The attributes included are: 1) sub-band-frequency-ranges: The unlicensed sub-bands (e.g. 46A, 46B, etc.) that are supported at the O-RU and their frequency ranges. 2) number-of-laa-scarriers (uint8): Number of LAA SCarriers that the O-RU can support. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 195 3) maximum-laa-buffer-size (uint16): Maximum O-RU buffer size in Kilobytes (KB) per CC. This parameter is needed at the O-DU to know how much data can be sent in advance and stored at the O-RU to address the LBT uncertainty. 4) maximum-processing-time (uint16): Maximum O-RU Processing time in microseconds at the O-RU to handle the received/transmitted packets from/to the O-DU. This parameter is needed at the O-DU to determine the time where it needs to send the data to the O-RU. 5) self-configure (Boolean): Capability to manage the contention window at the O-RU. Based on the CUS-spec, there are two modes of operation for LAA: 1) when the contention window is managed by the O-DU, and 2) when the contention window is managed by the O-RU. This field is set to True if the O-RU can manage the contention window locally. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.2.2 LAA O-RU parameter configuration | The second stage of the LAA-initiation process is the configuration message (using RPC edit-config). In this message, the O-DU configures the O-RU with the required parameters in the downlink direction. LAA parameters can be configured by Netconf Client after capability exchange is finished. It can also be sent as needed, to reconfigure the O-RU with new parameters (e.g. ed-threshold-pdsch, etc.). The attributes of this message (o-ran-laa.yang Module) include: 1) number-of-laa-scarriers (uint8): Number of LAA SCarriers to be used at the O-RU. This number should be less than or equal the number reported by the O-RU in its module capabilities. 2) multi-carrier-type (Enumeration): This value indicates the list of multi carrier types (A1, A2, B1, B2) as specified in clause 15.1.5 of ETSI TS 136 213 [32]. 3) multi-carrier-tx (Boolean): This value indicates whether self-deferral is activated or not. "True" indicates transmission on channel access win (i.e. no self-deferral). "False" indicates mutual transmission on multiple carriers. 4) multi-carrier-freeze (Boolean): This value indicates if the absence of other technology in the unlicensed band can be guaranteed. This attribute can only be used when the multi-carrier-type is A1. "False" indicates that absence of other technology is not guaranteed. 5) laa-ending-dwpts-supported (Boolean): This value indicates whether LAA ending in Downlink Pilot Time Slot (DwPTS) is supported. 6) laa-starting-in-second-slot-supported (Boolean): This value indicates LAA starting in second slot is supported. LAA carrier configurations (o-ran-uplane-conf.yang Module) include: 1) ed-threshold-pdsch (int8): This value indicates the energy detection (ED) threshold for LBT for PDSCH and for measurements in dBm. 2) ed-threshold-drs (int8): This value indicates the ED threshold for LBT for DRS in dBm. 3) tx-antenna-ports (uint8): This value indicates the Tx antenna ports for DRS. 4) transmission-power-for-drs (int8): This value indicates the offset of CRS power to reference signal power (dB). 5) dmtc-period (enumeration): This value indicates DMTC period in milliseconds. 6) dmtc-offset (uint8): This value indicates DMTC offset in Subframes. 7) lbt-timer (uint16): This value indicates LBT Timer in milliseconds. If Self Configure capability is set to "true", the following parameters are also needed to be configured. For every traffic priority class, the O-DU needs to configure maximum CW usage counter. This value indicates the maximum value of counter which shows how many max congestion window value is used for back off number of each priority class traffic. This value, as specified in clause 15.1.3 of ETSI TS 136 213 [32], is represented as K. Based on the 3GPP specification, this value is selected by O-RU from the set of values {1, 2, …, 8}. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 196 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.3 Carrier selection | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.3.1 LAA measurements | The function of the message "rpc start-measurements" is to order the O-RU to start measurements. This message can be used for carrier selection initially or dynamically over time. O-RU sends RPC response where status=ACCEPTED (positive case) or REJECTED (negative case). O-RU performs measurement and delivers result with respect to max response time. If result is not ready on time - O-RU sends notification with "measurement-success"=FALSE and with appropriate failure reason. For every configured band, the O-RU informs the NETCONF client whether the measurement was successful or not. For bands with successful measurements, the O-RU reports the occupancy ratio and average RSSI for each channel. For bands with failure measurements, the O-RU includes the reason (e.g. TIMEOUT when the O-RU is not able to finish the measurement for this specific band). The occupancy ratio of a given channel is defined as the percentage of the busy duration (i.e. measured signal power is larger than the energy-detection threshold) to the total measurement duration of this specific channel. The energy- detection threshold is specified in the o-ran-uplane-conf.yang module using the ed-threshold-pdsch leaf. Note that this threshold is the same as the energy-detection threshold used for LBT for PDSCH transmission. The total measurement duration per channel is specified in o-ran-laa-operation module using the duration-per-channel leaf. The range of the occupancy ratio is from 0 % (no signal is detected over the total measurement duration per channel) to 100 % (i.e. channel was always occupied during measurement). The average RSSI of the measured channel is the measured power of this specific channel averaged over the total measurement duration per channel. This parameter is reported to the NETCONF client in dBm and takes a value from the range 0 dBm to -128 dBm. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 16.3.2 LAA carrier frequency configuration | After receiving the measurements, the NETCONF client configures the O-RU with the new channel(s), if needed. To start radio transmission and reception with a new centre frequency, for every Component Carrier (CC) that needs to be re-configured with a new centre frequency, the O-DU shall first deactivate the TX carrier, delete it, then create a new TX carrier (using the new centre carrier frequency as well as any other new configurations), and then activate the TX carrier again to start OTA operation. The procedure for deactivating/deleting/creating/activating the carrier is explained in clause 15.3: Carrier Configuration, in the M-plane specification and elaborated in Figure 15.2.4-1. NOTE 1: The creation of LAA carriers is identical to the creation of regular carriers but in the unlicensed bands. O-RU responds to the configuration request with success or failure. NOTE 2: The carrier-selection algorithm at the O-DU (i.e. selecting the "best" channel based on the reported measurements from the O-RU) is an implementation issue and is out of the scope of the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17 Shared cell | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.1 Introduction | This clause specifies the support of the "Shared Cell" O-RU use case. The features of C/U-Plane aspects are described in clause 13 of [2]. The M-Plane aspects necessary to support Shared Cell are described in this clause 17. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.2 Architecture | The NETCONF client (O-RU Controller) establishes M-Plane connection individually to each O-RU, where the O-RUs are operating in either cascade mode or FHM mode, as illustrated in Figure 17.2-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 197 In Figure 17.2-1, solid lines indicate C/U-plane interface and dotted lines indicate M-plane interface. Therefore, from the M-Plane point of view, the same architecture model can be applied as specified in clause 5.1.2. New functionality which is required to be added, together with existing functionality which is required to be enhanced are specified in clauses 17.3 to 17.6. There are no changes to the functionality described in the following clauses and their associated YANG models: • Clause 8: Software management • Clause 11: Fault management • Clause 12: File management A NETCONF client with suitable privileges is able to trigger a reset procedure for each O-RU. It is strongly recommended that when triggering the reset procedures for multiple O-RUs, a NETCONF client should order the procedures such that a reset of an individual O-RU does not affect the operation of other O-RUs operating in either cascade or FHM mode. This can be achieved by correct ordering of the triggering of the reset procedure between the different O-RUs. For example, when triggering a reset involving multiple O-RUs operating in cascade mode, the ordering of the reset trigger sent by the NETCONF client should be done beginning with the last (most-southern) O-RU to the first (most northern) O-RU in chain. In configuration where FHM is used - when FHM reset is needed, O-RUs connected through this FHM should be reset first, then FHM reset can be performed. It is strongly recommended to disable carriers affected by such a reset procedure prior to the triggering of the reset to minimize the impact on C/U-plane traffic as much as possible. In case an O-RU connected through FHM requires to be reset - the reset does not impact to other O-RUs. NOTE: There is no difference between Hierarchical M-plane architecture and Hybrid M-plane architecture from the point of reset ordering in either cascade mode (chain topology), or FHM mode (tree topology). Using this approach, a NETCONF client can performs software management on multiple O-RUs. Since this procedure may require the reset of the O-RU to update the appropriate software file(s) for the O-RUs, the NETCONF client is recommended to order the software management procedures such that the reset procedure issued against one O-RU shall not impact the other O-RUs or FHM. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 198 Figure 17.2-1: M-Plane Connection |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.3 Start-up and Installation | This clause provides the consideration regarding the shared cell specific additional mechanism for the overall start-up mechanism for "O-RUs with Copy and Combine function" and for "O-RUs without Copy and Combine function". Each O-RU establishes M-Plane connection individually to the NETCONF client in the O-RU Controller. The procedures through Transport Layer initialization (DHCP process and VLAN scanning) and supervision of NETCONF connection are the same as Figure 6.1-1 in clause 6 for both "O-RUs with Copy and Combine function" and "O-RUs without Copy and Combine function". For the transport layer initialization, the following assumptions are made: • The order of each O-RU's M-plane establishment is not restricted because of the network transparency at O-RU (FHM and Cascade). • For simplification, the network should be configured using a common management plane vlan-id or untagged interface for all O-RUs within one shared cell network managed by same NETCONF client. As a result, the same vlan-id is learned by VLAN scanning by all O-RUs within the shared cell network. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 199 Figure 17.3-1: NETCONF establishment of the start-up In the step "retrieval of O-RU information", the NETCONF client retrieves the O-RUs' capability from the NETCONF servers by using individual M-plane connection in parallel. The Copy and Combine related capability is defined in clause 17.6.1. After the retrieval of O-RU information, the NETCONF client performs the topology discovery procedure in order to discover the topology of NETCONF servers within one shared cell network. (See clause 17.6.2.) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 200 Figure 17.3-2: RU information retrieval and topology detection at the start-up The NETCONF client performs software management per O-RU as described in clause 8. As described in clause 17.2, as the reset procedure is required during the software management procedure, it is recommended that the NETCONF client resets the O-RU while taking account of the topology of O-RUs and whether a reset of one O-RU will affect other O-RUs in the chain or star topology. Figure 17.3-3: Software management per O-RU After the software management steps are completed for all NETCONF servers, the NETCONF client performs shared cell configuration. (See clause 17.6.3.) The NETCONF client performs transport configuration, connectivity check configuration, C/U-plane transport connectivity check procedure, Retrieval of the O-RU Delay Profile and U-plane configuration procedures for all O-RUs. In the present document, the only processing element definition used for supporting shared cell is the Ethernet-type- flow which is a combination of VLAN identity and MAC address. The vlan-id(s) used for C/U-plane transport-flows is/are common to all O-RUs operating within one shared cell network. The Ethernet bridging functionality in an O-RU with Copy and Combine function is able to bridge the Ethernet Loopback messages between the O-DU and other O-RUs configured as part of the shared cell operation. For more details, see clause 17.6.2. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 201 The u-plane configuration in o-ran-uplane-conf module shall have identical configuration except config-false instances' names and low-level-tx(rx)-endpoints' names for all O-RUs operating within the one shared cell network. The value of gain in tx-array-carriers can be independently configured per O-RU (i.e. a common value is not mandatory). The u-plane configuration in o-ran-uplane-conf module is no longer required for O-RU (FHM). Instead, shared-cell- copy-uplane-config and shared-cell-combine-uplane-config in o-ran-shared-cell.yang module are used. (See clause 17.6.4.) NOTE: In this version of the specification, only eCPRI headers are supported for the C/U-Plane protocol (i.e. support of the IEEE 1914.3 header as specified in [i.9] is not defined). ETSI ETSI TS 104 023 V17.1.0 (2026-01) 202 Figure 17.3-4: Shared cell configuration and u-plane configuration The NETCONF client performs further steps for the regular start-up procedure as described in clause 6. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 203 Figure 17.3-5: Further steps for start-up procedure |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.4 Performance management | This clause provides description of the specific part of Performance Management for shared cell. NOTE 1: Clause 9.1 of CUS specification [2] indicates whether a particular performance measurement is mandatory or optional for Cascade/FHM O-RU. transceiver-stats: O-RU (Cascade / FHM) has multiple connections to O-DU and O-RU (Cascade/Normal). The baseline O-RU models permit O-RUs to be defined with multiple ports and multiple transceiver modules. Transceiver module is defined by o-ran-transceiver which refers the port-number for these interfaces. Refer to clause 17.6.1 O-RU Information for Shared Cell. In this case, the O-RU (Cascade / FHM) reports transceiver-stats per port- number. Rx-window-stats: O-RU (Cascade) monitors rx-window-stats per eaxc-id, per transport or per hardware component (O-RU) because it receives data flow from the north-node. An FHM has no radio transmission/reception functionality and hence cannot support RX_ON_TIME, RX_EARLY, RX_LATE, RX_ON_TIME_C, RX_EARLY_C, RX_LATE_C in rx-window-stats. NOTE 2: This version of the specification does support rx-window-stats to monitor the downlink reception window and does not support monitoring by an O-RU of the uplink traffic from south-node. Tx-stats: O-RU (Cascade / FHM) monitors tx-stats per eaxc-id, per transport or per hardware component (O-RU) because it transmits data flow to the north-node. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 204 NOTE 3: This version of the specification does support tx-stats to monitor uplink traffic and does not support monitoring by an O-RU of the downlink traffic to south-node. Shared-cell-stats: Cascade O-RU/FHM monitors shared-cell-stats on per TRANSPORT object-unit. NOTE 4: Monitoring by an O-RU of the uplink traffic from south-node can be achieved using shared-cell-stats. Epe-stats: O-RU (Cascade / FHM) monitors epe-stats per hardware component. Symbol-rssi-stats: O-RU monitors symbol-rssi-stats per rx-array-carrier. NOTE 5: O-RU without radio transmission/reception capability (FHM) does not support monitoring of symbol- rssi-stats. Tx-antenna-stats: O-RU monitors tx-antenna-stats per tx-array element, or connector and band number. NOTE 6: O-RU without radio transmission/reception capability (FHM) does not support monitoring of tx-antenna- stats. Tssi-stats-object: O-RU monitors tssi-stats-object per carrier_array_element. NOTE 7: O-RU without radio transmission/reception capability (FHM) does not support monitoring of tssi-stats- object. Rssi-stats-object: O-RU monitors rssi-stats-object per carrier_array_element. NOTE 8: O-RU without radio transmission/reception capability (FHM) does not support monitoring of rssi-stats- object. Tx-output-power-stats-object: O-RU monitors tx-output-power-stats-object per tx-array-carrier, tx-array-element, connector, carrier_array_element or array-carrier-connector. NOTE 9: O-RU without radio transmission/reception capability (FHM) does not support monitoring of tx-output- power-stats-object. ethernet-stats: O-RU (Cascade / FHM) has multiple connections to O-DU and O-RU (Cascade/Normal). The baseline O-RU models permit O-RUs to be defined with multiple ethernet ports. Refer to clause 17.6.1 O-RU Information for Shared Cell. In this case, the O-RU (Cascade / FHM) reports ethernet-stats per port-number. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 205 Table 17.4-1: Measurement-group of O-RU (Cascade / FHM) Measurement-group measurement-units transceiver-stats port-number (multiple) rx-window-stats eaxc-id, transport or hardware component (O-RU) tx-stats eaxc-id, transport or hardware component (O-RU) shared-cell-stats transport epe-stats hardware component symbol-rssi-stats- object rx-array-carrier tx-antenna-stats tx-array element, or connector and band number tssi-stats-object carrier_array_element rssi-stats-object carrier_array_element tx-output-power- stats-object tx-array-carrier, tx-array-element, connector, carrier- array-element or array-carrier-connector ethernet-stats ethernet interface name (multiple) For more detail, refer to the counters specified in Annex B. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.5 Delay management | In the shared cell environment, the use of O-RU Adaptive Delay capability is not permitted. The O-DU and each O-RU have their own delay parameters and supported transmission window and reception window. Also, the topology of the O-RU configuration can be detected by the topology discovery procedure. The O-DU can determine the delay budget between itself and the O-RUs considering the O-RUs' topology and delay parameters and its own transmission window and reception window. During this discovery, the required processing time of the O-RU is also considered. The O-RU processing time includes the copy operation for downlink operation, and the combine operation for uplink operation, and the delay periods for the copy and combine operations are defined as t-copy and t-combine in o-ran-shared-cell.yang module: • t-copy: Corresponding to the maximum FHM or cascade O-RU processing delay between receiving an IQ sample over the fronthaul interface from the north-node, coping it and transmitting it over the fronthaul interface to the south-node. • t-combine: Corresponding to the maximum FHM or cascade O-RU processing delay between receiving an IQ sample over the fronthaul interface from the south-node(s), combing them and transmitting it over the fronthaul interface to the north-node. Therefore, based on the above information, the O-DU can determine how many O-RUs are configured to operate in a shared cell instance. After the delay budget between the O-DU and the furthest (southern-most) O-RU in the chain is determined, multiple O-RUs can be configured to operate in between the O-DU and the furthest O-RU. The time budget between the O-DU and the furthest O-RU is constant and is shared for all O-RUs operating in cascade mode. For combine function operation, the O-RU shall await the successful reception of the eCPRI frame(s) from the south-node(s). Once the FHM receives the eCPRI frame from all of the south-nodes, the O-RU (FHM) can perform the combine operation. Once the cascade O-RU receives the eCPRI frame from the south-node, the O-RU can perform the combine operation using the eCPRI frame and received radio information. The maximum time an O-RU is permitted to wait for the required eCPRI frames is set by the ta3-prime-max configured by NETCONF client. If the O-RU cannot commence the combination procedure until a time after the configured ta3-prime-max minus t-combine, e.g. due to the delayed reception of eCPRI frame(s), the O-RU shall discard the delayed eCPRI frames if received and combine other received frames (for FHM mode) or radio information (for Cascade mode). The configurable ta3-prime-max shall be equal to or less than ta3-prime-max-upper-limit which is the capability of O-RU, related to the internal memory for combine operation. The detail for C/U-plane aspects is described in clause 13.4.3 of [2]. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 206 The ta3-prime-max schema node is relevant to the timing on each symbol. The scs schema node indicates each symbol timing. The capability of supported SCSes is reported by leaf-list scs-supported. Among them the intended SCSes should be informed to FHM/Cascade O-RU as scs schema node, associating with eaxc-id. SCS in an eaxc-id can be different from that of another eaxc-id. SCS in an eaxc-id can be also plural. FHM/Cascade O-RU reports the capability of supporting multiple SCS in a single eaxc-id as the feature MULTIPLE-SCS-IN-EAXC, and O-DU should check before configuring multiple SCS in a single eaxc-id. • ta3-prime-max: The latest time that FHM or cascade O-RU is allowed to send UL U-plane message to north-node relative to reception timing at O-RU antenna. • ta3-prime-max-upper-limit: The upper limit for the configurable ta3-prime-max value. This is the capability information of O-RU that comes from the O-RU internal memory for the combine operation. Clause 13.5.3 of the CUS Plane specification [2] introduces new parameters for controlling combine operations: • t-combine-net: is the read-only processing delay as the reported by the FHM/Cascade O-RU. • tx-duration: is a configurable parameter by O-DU or a calculated parameter by FHM/Cascade O-RU, corresponding to the message transmission duration. Where: the sum of t-combine-net processing delay and the maximum tx-duration transmission duration corresponds to the t-combine duration. NOTE: CUS Plane specification [2] refers to these parameters as T_Combine_net, Tx_Duration and T_Comb. An FHM/Cascade O-RU can signal to an O-RU Controller that it supports these parameters by indicating it supports the ENHANCED-T-COMBINE YANG feature. The O-DU configures such an FHM/Cascade O-RU to use the new parameters by setting the enhanced-t-combine-enabled to 'true'. In this case, the FHM/Cascade O-RU shall use t-combine-net and tx-duration to calculate the T_waiting (Refer to clause 13.5.3 of [2]) instead of t-combine. If enhanced-t-combine-enabled is set to ' true' and if no value of tx-duration is configured by the O-DU, the FHM/Cascade O-RU shall calculate tx-duration from shared-cell-combine-entities, ensuring that the maximum amount of calculation does not exceed the symbol duration without cyclic prefix designated by ta3-prime-max. When multiple SCSes are supported by FHM/Cascade O-RU, there are multiple combine delays according to SCSes or configured tx-duration per SCS. This capability may be exposed by FHM/Cascade O-RU through max-combine-delay- per-scs. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.6 Details of O-RU operations for shared cell | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.6.1 O-RU information for shared cell | This clause provides the function detail of O-RU operations for a shared cell. Interfaces to south-node of O-RU with Copy and Combine function Cascade O-RU may have one additional transport interface to south-node and FHM may have more than one additional transport interfaces to south-nodes, illustrated in Figure 17.6.1-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 207 Figure 17.6.1-1: Transport Interfaces of both side of O-RU Both the interface to north-node and the interface to south-node can be defined by ietf-interface YANG model with type = ethernetCsmacd, augmented by o-ran-interface for mac-address and port-number. Transceiver module is defined by o-ran-transceiver which refers the port-number for these interfaces. The maximum number of the interfaces is just the number of physical interfaces within the O-RU. NOTE: The present document defines the use of IEEE 802.1X port based access control, as described in clause 7.12. In order to use IEEE 802.1X, a supplicant PAE in an O-RU needs to signal with an authenticator PAE. The present document does not define operation of an authenticator PAE in an O-RU, instead only defining operation of the supplicant PAE functionality. Operators wanting to benefit from IEEE 802.1X when operating a shared cell configuration need to consider which network element(s) is/are responsible for supporting the authenticator PAE function. The role of interfaces shall be detected by topology discovery procedure described in clause 17.6.2. If the O-RU has any interfaces to south-node and if they are utilized for shared cell scenario, the NETCONF client shall configure the higher layer ietf-interface (type = l2vlan) including configuring the corresponding mac-address and C/U-plane vlan-id configuration for each ietf-interface (type = ethernetCsmacd) to south-node, in addition to the higher layer ietf-interface (type = l2vlan) configured for the ietf-interface (type =ethernetCsmacd) to north-node in clause 7.3. If an interface to a south-node is not used for shared cell scenario, the NETCONF client does not need to configure the higher layer ietf-interface (type = l2vlan) for it. Capability of O-RU with Copy and Combine function The configuration for Copy and Combine function is defined in the o-ran-shared-cell.yang module. The presence of this yang module signalled in O-RU's YANG library indicates that O-RU can support the copy and combine function. The shared-cell-module-cap container includes the information for the internal maximum processing delay for both the copy function and the combine function required for delay management operations. The shared-cell-module-cap container also includes the information defining the maximum numbers of copy and combine functions supported. This information is used by the NETCONF client to determine how many south-nodes can be supported and how many eaxc-ids can be used for copy and combine procedures. It also contains the information defining the compression capability supported by the FHM. It contains scs-supported capability of FHM in the present document. For the cascade mode, the cascade O-RU shall support normal O-RU operations, i.e. radio transmission and reception. For the FHM mode, the FHM does not have the capability for radio transmission and reception. The o-ran-shared- cell.yang module defines the feature FHM to indicate that O-RU acts as FHM and does not have the capability of radio transmission and reception. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 208 Yang modules for FHM mode Especially for the FHM mode, some of the yang modules are not necessary because the FHM does not have the capability for radio transmission and reception. The following yang modules are not applicable for O-RU (FHM). For more detail, see clause C.1. • o-ran-ald module and o-ran-ald-port: Antenna Line device is directly connected to O-RU. • o-ran-laa-operations and o-ran-laa: out-scope for LAA and radio transmission related only. • o-ran-module-cap: radio transmission related parameters only. • o-ran-beamforming: radio transmission (beamforming) specific parameters only. • o-ran-uplane-conf: radio transmission (uplane configuration) specific parameters only. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.6.2 Topology discovery procedure | The O-DU shall determine the topology (adjacency relationships) of O-RUs for the shared cell. In this version of the specification, only Ethernet based transport of C/U sessions for shared cells is supported. The shared cell topology discovery procedure operates at the Ethernet layer, using the LBM/LBR connectivity checking procedure defined in clause 7.6 to fill the Ethernet Forwarding Information Base (FIB), and is based on the O-DU recovering the FIB. The transparent bridge functionality is used in the shared cell capable O-RUs operating in FHM and/or cascade mode. In a typical operation, an O-DU performs a two-stage procedure for determining the topology: 1) In a first stage, the O-DU performs Ethernet connectivity monitoring on all discovered O-RU MAC addresses, using the procedures defined in clause 7.6.1. The sending of the Ethernet Loopback responses from the discovered MAC addresses ensures that the transparent bridges in the O-RUs operating in FHM and cascade mode automatically learns the MAC addresses switched through these devices. NOTE: In addition to Ethernet connectivity monitoring, DHCP discovery, call home and M-plane connection establishment can also be used to populate information in the FIB and so may be sufficient when an O-RU only has a single port configured for interfacing to its north-node. 2) In a second stage, the O-DU uses the o-ran-ethernet-forwarding.yang module to discover which MAC addresses have been learnt by the Ethernet bridge functionality. The O-DU uses the individual Ethernet forwarding table entries to determine the adjacency relationships. If the topology of the cascade architecture does not ensure that Ethernet frames sent between a south-node and a north-node are bridged by an O-RU, the O-DU needs information in addition to the O-RU FIB to perform topology discovery. How an O-DU becomes aware that additional information is required, together with the definition of such information, is outside the scope of the present document. Figure 17.6.2-1 illustrates an example of the MAC address configuration for a set of O-RUs configured in cascade mode and FHM mode of operations, together with the associated Transparent Bridge FIB tables. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 209 Figure 17.6.2-1: Bridge FIB table entries learned from LBM/LMR connectivity check procedures |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.6.3 Shared cell configuration on transport flow | Shared cell configuration consists shared-cell-copy-entities and shared-cell-combine-entities. Both define the transport-flows for the processing elements of the interface to north-node and the interface to south-node. The container shared-cell-combine-entities contains the ta3-prime-max and scs to be used in delay management as described in clause 17.5. As per conventional o-ran-processing-element.yang, the transport-flow (eth-flow) of the processing element is a combination of o-du-mac-address, ru-mac-address and vlan-id for legacy eth-flow. The present document introduces 2 more eth-flow options for shared cell scenario: • The transport-flow definition for the interface to north-node: north-eth-flow is a combination of north- node-mac-address, ru-mac-address and vlan-id. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 210 • The transport-flow definition for the interface to south-node: south-eth-flow is a combination of south-node- mac-address, ru-mac-address and vlan-id. Either legacy eth-flow or north-eth-flow can be used for last (southern) O-RUs in tree or chain topology. The leaf o-du-mac-address, north-node-mac-address, south-node-mac-address and ru-mac-address are configured as follows: • For FHM or Cascade O-RU which performs DL Copy function and UL Combine function: - north-eth-flow for the interface to north-node: north-node-mac-address: MAC address of the north-node (O-DU) ru-mac-address: MAC address of the interface to north-node in FHM/Cascade O-RU vlan-id - south-eth-flow for the interface to south-node: south-node-mac-address: MAC address of the south-node (O-RU) ru-mac-address: MAC address of the interface to south-node in FHM/Cascade O-RU vlan-id NOTE 1: Same vlan-id is configured on both sets of processing elements. • For Cascade O-RU in the last node, which does not perform DL Copy function and UL Combine function: - north-eth-flow for the interface to north-node: north-node-mac-address: MAC address of the north-node ru-mac-address: MAC address of the interface to north-node in O-RU vlan-id or - eth-flow for the interface to north-node: o-du-mac-address: MAC address of the north-node ru-mac-address: MAC address of the interface to north-node in O-RU vlan-id • For O-RU in the last node, but not cascade O-RU: - eth-flow for the interface to north-node: o-du-mac-address: MAC address of the north-node ru-mac-address: MAC address of the interface to north-node in O-RU vlan-id Copy and Combine functions are disabled if not configured, meaning the functions are disabled by default. Figure 17.6.3-1 illustrates the shared cell configuration and transport configuration. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 211 Figure 17.6.3-1: Relation of Shared Cell Copy and Combine Entities and Transport Configuration For the cascade O-RU, the processing element for north-node shall be connected to the low-level-[tr]x-links in u-plane configuration as in Figure 15.2.4-1 in clause 15.2.4. In the FHM, there is no radio transmission, so no low-level-[tr]x- links exists. Figure 17.6.3-2 illustrates the example of topology diagram and shared cell copy/combine entities. Each thick blue line indicates the transport-flow in the processing element. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 212 Figure 17.6.3-2: Example of Topology and Shared cell Copy/Combine entities The following is the information for this example of topology configuration. FHM mode: • One transport-flow for north-node corresponds to the two transport-flows for south-nodes: O-RU#2a and 2b respectively. O-RU#2a and #2b have same u-plane configuration. • Two transport-flows for north-node correspond to the two times two transport-flows for south-nodes: O-RU#2x and #2y respectively. O-RU#2x and #2y have same u-plane configuration. Cascade mode: • Two transport-flows for north-node correspond to two transport-flows for south-node and own u-plane- configuration. O-RU#1 and O-RU#2 have same u-plane configuration. NOTE 2: "two transport-flows" above is just the example scenario that two optical physical lines are used for fronthaul connection, which has been supported in the present document. The total capacity of the interfaces to north-node for FHM is assumed that required traffic can be transported for multiple shared cells. O-RU Controller shall ensure that the capacity of any link shall not be exceeded due to copy and combine configuration. Information only for the C/U-plane behaviour as the background at COMMON/SELECTIVE-BEAM-ID shared cell copy and combine mode. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 213 For the traffic from the north-node to O-RU (FHM / cascade), there are DL C-plane and U-plane traffic and UL C-plane traffic in the transport interface. When operating with COMMON shared cell copy and combine mode, all C/U-plane traffic received from north-node is copied and forwarded to the south-node(s). For the traffic from south-node, there is UL U-plane traffic only in each transport interface to south-node. When operating with COMMON shared cell copy and combine mode, all U-plane traffic received from the south-node(s) is combined and forwarded to the north-node. It is assumed that common compression mechanism for uplink is configured by M-plane for all O-RUs in one shared cell network. When operating with SELECTIVE-BEAM-ID shared cell copy and combine mode, some selected C/U-plane traffic received from the north-node are copied and forwarded to the south-node and some selected U-plane traffic received from south-node are combined and forwarded to the north-node. This version of the specification supports SELECTIVE-BEAM-ID. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.6.4 U-plane configuration for FHM | FHM does not have u-plane configuration defined in o-ran-uplane-conf.yang module. Instead, FHM has shared-cell specific u-plane configuration in shared-cell-copy-entities/shared-cell-combine-entities for DL Copy function and UL Combine function, See clause 13.2 of CUS specification [2] for the details of those functions. DL Copy function is performed on the received CU-Plane message to make multiple its messages to the specific south nodes. Different eAxC flow can arrive at its specific south node differently, so transport-flow is associated with eaxc- id, which is unique in shared-cell-copy-entities per data direction (DL/UL). The shared-cell-copy-uplane-config is the eaxc-id list used by DL C-plane, DL U-plane and UL C-plane traffic. UL Combine function is performed on the received U-Plane messages from the specific multiple south nodes to make a message to a single north node on the certain timing. Combine function extracts IQ data per RE from U-Plane message and combine multiple IQ data into a single IQ data. The shared-cell-combine-uplane-config includes the compression method of the UL U-plane messages from O-RUs within the shared cell network in shared cell combine function. The compression method is configurable per eaxc-id. It also contains downlink-radio-frame-offset, downlink-sfn-offset and n-ta-offset to define the uplink timing of t=0 for the configured ta3-prime-max. In addition, number-of-prb is also contained for the cases that all PRBs in numPrbc are controlled by C-plane message or tx-duration is calculated by FHM. FHM may have multiple sets of shared cell networks as described in Figure 17.6.3-2. E.g. O-RU#2a and O-RU#2b are one shared cell network. O-RU#2x and O-RU#2y are another shared cell network. These two shared cell networks are separated transport layer level definitions using separate processing-element/transport-flows. Nevertheless, the O-RU Controller shall ensure that the eaxc-id allocation for the shared cell networks shall be unique per link (downlink or uplink) in one O-RU (FHM). NETCONF client (O-RU Controller) shall ensure to allocate unique eaxc-id for O-RU(s) per link within the shared cell network(s) in one O-RU (FHM). NOTE 1: shared-cell-copy-uplane-config and shared-cell-combine-uplane-config are not applicable to the cascade mode. Instead, o-ran-uplane-conf.yang module is applied. NOTE 2: If the FHM supports the C/U-plane monitoring timer described in clause 7.10, then depending on how long the O-DU takes to initiate sending of C/U plane data flows, it may be advisable for the NETCONF client to initially disable the operation of the timer for the FHM before carrier activation to O-RUs that are south-nodes for the FHM. Such an approach avoids the FHM sending spurious alarm notifications triggered by O-DU delays in initializing the sending of C/U plane data that exceed the default timer value. Once C/U plane data flows have commenced, the NETCONF client can re-configure the timer with the desired value and hence activate monitoring of the C/U plane connectivity by the FHM. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.6.5 Support of selective transmission and reception function | This clause describes M-Plane support for selective transmission and reception function which is specified in clause 13.3 of [2]. There are two things to be introduced for supporting the function from M-Plane perspective: • Feature which indicates FHM support for selective transmission and reception function. • Configuration parameters which indicate the mapping information between global beamId, O-RU(s) and O-RU local beamId. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 214 If FHM indicates the feature "SELECTIVE-BEAM-ID" to O-DU, O-DU can configure the mapping information between global beamId, O-RU(s) and O-RU local beamId to the FHM to use selective transmission and reception function. For configuring the information, mapping-table-for-selective-beam-id is used. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.7 Cascade-FHM mode | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.7.1 Background | The introduction of Cascade-FHM mode is described in clause 13.7 of [2]. This clause describes mainly shared cell configuration on cascaded FHMs. For other common parts, like start-up procedures, topology discovery procedure, etc., refer to relevant parts in clause 17. In this version of the specification, the maximum level of cascaded FHMs is limited to 2. The first cascade FHM nearest to O-DU is named FHM#1, the second FHM is named FHM#2. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 17.7.2 Shared cell configuration on cascaded FHMs | The NETCONF client needs to configure shared cell copy entities and shared cell combine entities on FHM#1 and FHM#2 respectively. In Figure 17.7.2-1 there are two types of FHM to FHM traffic: 1) Type 1: the cell of traffic is on O-RUs of both FHM#1 and FHM#2. For example, the Cell#1 of Same cell scenario; 2) Type 2: the cell of traffic is only on O-RUs of FHM#2. For example, the Cell#2 of Two cells Scenario. In this scenario a single SCS per FHM is assumed. When multiple SCS are used in FHM, shared-cell-combine-entities are increased accordingly. Figure 17.7.2-1: Typical cell scenarios in Cascade-FHM mode For Type 1, taking Cell#1 of Same cell scenario as example, the shared cell configuration on FHM#1 and FHM#2 are as follows: FHM#1: - In DL direction, it needs one element of shared-cell-copy-entities with one of south nodes connecting to FHM#2 and other south nodes connecting to the O-RUs serving FHM#1, and with north node connecting to O-DU. NETCONF Client selects eaxc-ids carried by the CU-Plane messages who will go to FHM#2 and fills them to eaxc-id list of shared-cell-copy-uplane-config. - In UL direction, it needs one element of shared-cell-combine-entities with one of south nodes connecting to FHM#2 and other south nodes connecting to the O-RUs serving FHM#1, and with north node connecting to O-DU. NETCONF Client selects eaxc-ids carried by the U-Plane messages who are from FHM#2 and fills them to eaxc-id list of shared-cell-combine-uplane-config. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 215 FHM#2: - In DL direction, it needs one element of shared-cell-copy-entities with north node connecting to FHM#1 and south nodes connecting to the O-RUs serving FHM#2. NETCONF Client selects eaxc-ids carried by the CU-Plane messages who are from FHM#1 and fills them to eaxc-id list of shared-cell- copy-uplane-config. - In UL direction, it needs one element of shared-cell-combine-entities with north node connecting to FHM#1 and south nodes connecting to the O-RUs serving FHM#2. NETCONF Client selects eaxc-ids carried by the U-Plane messages who will go to FHM#1 and fills them to eaxc-id list of shared-cell- combine-uplane-config. For Type 2, taking Cell#2 of Two cells scenario as example, the shared cell configuration on FHM#1 and FHM#2 are as follows: FHM#1: - In DL or UL direction, existing only one south node which connects to FHM#2 and other steps are no difference with FHM#1 of Type 1. NOTE: In Two cells scenario, there will be two elements of shared-cell-copy-entities in DL direction in FHM#1, one is for Cell#1 and another is for Cell#2. Similarly, there will be two elements of shared-cell-combine- entities in UL direction in FHM#1, one is for Cell#1 and another is for Cell#2. FHM#2: - There is no difference with FHM#2 of Type 1. Both FHM#1 and FHM#2 do not need to have u-plane configuration defined in o-ran-uplane-conf.yang module since no radio transmission on the two FHMs. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18 Configured subscriptions | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.1 Introduction | The support by an O-RU of configured subscriptions is an optional capability, advertised by the O-RU indicating it supports the ietf-subscribed-notifications YANG model as specified in IETF RFC 8639 [37] in its YANG library together with the configured feature. This capability enables an O-RU Controller to install a subscription via configuration of the O-RU's datastore. Importantly, the lifetime of such a configured subscription is not limited to the lifetime of the NETCONF session used to establish it, enabling a configured subscription to persist even when an O-RU has been temporarily disconnected from the network. An O-RU may store configured subscription information in its reset-persistent memory. The ietf-subscribed-notifications YANG model defines a transport agnostic mechanism for subscribing to and receiving content from an event stream in an O-RU. An O-RU that supports configured subscriptions shall also support the encode-json feature together with the augmentation of the ietf-subscribed-notifications YANG model by the o-ran-ves-subscribed-notifications YANG model. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.2 Description | An O-RU controller can discover the event-streams supported by an O-RU. The O-RU Controller may then establish a configured subscription to a particular event-stream. The same NACM privileges defined in clause 6.5 shall be used by the O-RU in determining whether an O-RU controller has privileges to establish a configured subscription to a particular event-stream. Based on configured subscriptions, the O-RU sends asynchronous notifications over HTTPS to the configured Event-Collector. This capability can be used with any existing YANG notification, e.g. defined in YANG models published by the O-RAN Alliance or imported from other organizations. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 216 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.3 Procedure | The overall procedure is illustrated in Figure 18.3-1. Figure 18.3-1:Message sequence exchange for provisioning a configured notification Pre-condition: A NETCONF sessions is established between the O-RU and an O-RU Controller. 1) The O-RU controller gets the streams container and discovers the event-streams supported by an O-RU. 2) The O-RU controller uses the "edit-config" RPC to configure a subscription to an event-stream. The RPC includes the receiver container augmented with the notification-recipient schema node that encodes the URI of the Event-Collector. 3) If the O-RU controller has the correct privileges, the O-RU accepts the configured subscription. 4) As the lifetime of the configured subscription is not limited by the lifetime of the NETCONF session, the O-RU controller may terminate the NETCONF session without causing the subscription to be suspended. 5) After a subscription is successfully established, the O-RU immediately sends a "subscription-started" notification to the Event-Collector, as specified in clause 2.5 of IETF RFC 8639 [37]. 6) Upon an event that triggers a YANG notification, the O-RU sends a notification over HTTPS , according to clause 2.5 of IETF RFC 8639 [37]. Post-condition: The Event-Collector is able to update its operational-state datastore with the information received in the notification. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 217 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.4 Notification encoding | The O-RU shall support JSON encoding as specified in IETF RFC 7951 [38]. An example notification object generated using the o-ran-file-management.yang model and encoded following IETF RFC 7951 [38] is illustrated in Figure 18.4-1. Figure 18.4-1: Example of a JSON encoded YANG Notification |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.5 Notification transport | As described in IETF RFC 8639 [37] clause 2.5.7, an O-RU supporting configured subscriptions shall provide a YANG data model capturing the necessary transport-specific configuration parameters. O-RAN compliant Event-Producers shall support the o-ran-ves-subscribed-notifications YANG model. For transport, the notification JSON objects encoded according to clause 18.4 are further encapsulated in VES events. In order to enable the notifications sent to the Event-Collector to retain their native notification format/schema as defined in O-RAN, IETF and other YANG models, the ONAP/VES header is used to enable the decoupling of the notification payload from the overall VES event format, as illustrated in Figure 18.4-1. The VES common header shall include the following fields: • The value of the eventName field shall be set to "ORU-YANG/<model-identifier>:<notification-identifier>". • The value of the eventID field shall be set to "stndDefined-ORU-YANG-nnnnnnnnn", where nnnnnnnnn represents the integer key for the event. • The value of the sourceName and reportingEntityName fields shall both be set to the value of the ru-instance- id leaf defined in the o-ran-operations YANG model. Figure 18.5-1 illustrates an example of a JSON encoded VES Event Carrying a YANG Notification. { "ietf-restconf:notification": { "eventTime": "2020-11-11T20:20:00Z", "o-ran-file-management:file-upload-notification": { "local-logical-file-path": "o-ran/pm /C201805181300+0900_201805181330+0900_ABC0123456.csv", "remote-file-path": "sftp://nms-user@10.10.10.10/home/pm/ C201805181300+0900_201805181330+0900_ABC0123456.csv", "status": "SUCCESS" } } ETSI ETSI TS 104 023 V17.1.0 (2026-01) 218 Figure 18.5-1: Example of a JSON encoded VES Event Carrying a YANG Notification The VES events carrying the notifications are sent to the Event-Collector over HTTPS with a POST operation following the VES specification [i.2]. The complete protocol stack is illustrated in Figure 18.5-2. Figure 18.5-2: Protocol stack for O-RAN VES transport of YANG notifications 18.6 Monitoring the communications channel between O-RU and Event-Collector |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.6.1 Background | An O-RU controller can use the NETCONF monitoring capability described in clause 6.7 to trigger the repeated sending of a supervision-notification by the O-RU to a subscribed O-RU Controller to ensure the channel is operational and able to transport asynchronous notifications using NETCONF. An equivalent capability is required to be supported by those O-RUs that support configured subscriptions transported using JSON/HTTPS, to enable the monitoring of the communications channel from the O-RU to the Event-Collector. The format of the heartbeat notifications is identical to the Event-Collector Notification Format determined for the operation of pnfRegistration as described in clause 6.2.7, i.e. in this version of the specification, this capability adopts the ONAP defined guidelines for heartbeat, as defined in [i.2]. { "event": { "commonEventHeader": { "version": "4.1", "vesEventListenerVersions": "7.2", "domain": "stndDefined", "eventName": "ORU-YANG/o-ran-file-management:file-upload-notification", "eventID": "stndDefined-ORU-YANG-000000249", "sequence": 0, "priority": "Normal", "sourceName": "vendorA_ORUAA100_FR1918010111", "reportingEntityName": "vendorA_ORUAA100_FR1918010111", "stndDefinedNamespace": "urn:o-ran:file-management:1.0" "startEpochMicrosec": 1605126000000000, "lastEpochMicrosec": 1605126000000000 }, "stndDefinedFields": { "schemaReference": "https://gerrit.o-ran- sc.org/r/gitweb?p=scp/oam/modeling.git;a=blob;f=data-model/yang/published/o-ran/ru-fh/o-ran- file-management.yang", "data": { "ietf-restconf:notification": { "eventTime": "2020-11-11T20:20:00Z", "o-ran-file-management:file-upload-notification": { "local-logical-file-path": "o-ran/pm /C201805181300+0900_201805181330+0900_ABC0123456.csv", "remote-file-path": "sftp://nms-user@10.10.10.10/home/pm/ C201805181300+0900_201805181330+0900_ABC0123456.csv", "status": "SUCCESS" } } }, "stndDefinedFieldsVersion": "1.0" } }} ETSI ETSI TS 104 023 V17.1.0 (2026-01) 219 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.6.2 Heartbeat encoding | The VES common header shall include the following fields: • The value of the sourceName and reportingEntityName fields shall both be set to the value of the ru-instance- id leaf defined in the o-ran-operations YANG model. An example heartbeat encoding is illustrated in Figure 18.6.2-1. Figure 18.6.2-1: Example of a JSON encoded VES event carrying a heartbeat notification |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.6.3 Heartbeat control | Control of the heartbeat does not use the configured subscriptions capability. An O-RU controller configures heartbeat operation using the o-ran-supervision YANG model. An O-RU Controller shall configure the heartbeat-recipient-id to the address(es) of the heartbeat event-collector and optionally configure the heartbeat-interval leaf to a non-default heartbeat interval. In order to terminate operation of the monitoring the communications channel between O-RU and the Event-Collector, the O-RU Controller shall delete the configuration in the event-collector-monitoring container. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 18.6.4 Heartbeat procedure | Figure 18.6.4-1 illustrates the message sequence exchange for heartbeat operation. { "event": { "commonEventHeader": { "version": "4.1", "vesEventListenerVersions": "7.2", "domain": "heartbeat", "eventID": "heartbeat-00000001", "eventName": "heartbeat-oru", "sequence": 0, "priority": "Normal", "sourceName": "vendorA_ORUAA100_FR1918010111", "reportingEntityName": "vendorA_ORUAA100_FR1918010111", "startEpochMicrosec": 1605126000000000, "lastEpochMicrosec": 1605126000000000 }, "heartbeatFields": { "heartbeatFieldsVersion": "3.0", "heartbeatInterval": "60" } }} ETSI ETSI TS 104 023 V17.1.0 (2026-01) 220 Figure 18.6.4-1: Message sequence exchange for heartbeat operation In contrast to the monitoring of NETCONF connectivity described in clause 6.7 which define O-RU procedures when monitoring of NETCONF connectivity fails, there is no equivalent O-RU functionality defined if an O-RU determines that monitoring of the communications channel between O-RU and event-collector fails, e.g. if the O-RU is unable to establish a TLS connection to the event-collector. Operation of the SMO when it determines that the monitoring of the communications channel between an O-RU and event-collector fails is out of scope of the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 221 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19 Multi-Operator O-RU Operation | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.1 Introduction | The support by an O-RU of Multi-Operator O-RU operation is an optional capability, advertised by the O-RU indicating it supports the SHARED-ORU-MULTI-OPERATOR feature in its o-ran-wg4-features YANG model. All O-RUs that support the SHARED-ORU-MULTI-OPERATOR feature shall also support the SHARED-ORU- MULTI-ODU feature. These capabilities enable an O-RU to connect to multiple O-DUs that belong to different Shared Resource Operators. The Multi-Operator O-RU architecture enables a Shared Resource Operator to configure an agreed subset of shared O-RU resources independently from configuration and operating strategies of the other Shared Resource Operators. More specifically, a Shared O-RU Host makes available its shared O-RUs to enable connectivity to the O-DUs of one or more Shared Resource Operators allowing these Shared Resource Operators to configure and control such Shared O-RU. NOTE: How a Shared O-RU Host defines the partitioning of shared O-RU resources and communicates that information to a Shared Resource Operator is outside the scope of the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.2 High level shared O-RU architecture | When an O-RU is being configured by an independent Shared Resource Operator, a separate O-RU Controller associated with the Shared O-RU Host is required to configure the common aspects of the shared O-RU. Such a deployment is illustrated in Figure 19.2-1. When the Shared O-RU Host also operates an O-DU, the shared O-RU host may operate the M-Plane in either hybrid or hierarchical approach, as illustrated in Figures 19.2-2 and 19.2-3 respectively. In either case, the Shared O-RU Host uses a NETCONF client with "sudo" privileges, as defined in clause 6.5, to configure the shared O-RU. Each Shared Resource Operator uses NETCONF clients with " carrier" privileges that have parallel M-Plane connections with the shared O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 222 Figure 19.2-1: Shared O-RU M-Plane Architecture where Shared O-RU Host is independent of Shared Resource Operator(s) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 223 Figure 19.2-2: Shared O-RU M-Plane Architecture where the Shared O-RU Host is additionally a Shared Resource Operator managing Shared O-RU using hybrid approach ETSI ETSI TS 104 023 V17.1.0 (2026-01) 224 Figure 19.2-3: Shared O-RU M-Plane Architecture where the Shared O-RU Host is additionally a Shared Resource Operator managing Shared O-RU using hierarchical approach As illustrated in Figures 19.2-1, 19.2-2 and 19.2-3, from an Open Fronthaul perspective, the Shared O-RU is able to be deployed in variety of architectures. Clause 5.1.2 requires all O-RUs to support multiple NETCONF sessions, with the number of simultaneous sessions exposed using the maximum-simultaneous-netconf-sessions schema node in o-ran-operations YANG model. A Multi-Operator O-RU that is able to support (n) simultaneous NETCONF sessions, shall be able to support (m) Shared Resource Operators, where the cumulative NETCONF sessions operated by the (m) Shared Resource Operators is less than (n). ETSI ETSI TS 104 023 V17.1.0 (2026-01) 225 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.3 Shared O-RU "start up" procedure | 19.3.1 NETCONF server user account provisioning for shared resource operators The Shared O-RU Host shall use the procedures defined in clause 6.4 and the o-ran-usermgmt YANG model to configure separate user accounts on the shared O-RU's NETCONF server for each Shared Resource Operator. The user account for a Shared Resource Operator that is not also a Shared O-RU Host should only be configured with "carrier" access control group, as defined in clause 6.5. A user account is identified as being associated with a Shared Resource Operator by having one or more configured sro-ids. The sro-id is allocated by the Shared O-RU Host to the Shared Resource Operator(s) and is used in partitioning shared O-RU resources. NOTE 1: How a Shared O-RU Host communicates NETCONF user account information, including sro-id information, to a Shared Resource Operator is outside the scope of the present document. NOTE 2: The format of the sro-id string is not defined and not interpreted by the shared O-RU. In one example, the operators can agree to use a PLMN-Id corresponding to the Shared Resource Operator as the sro-id. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.3.2 NETCONF call home to shared resource operator O-DUs | The procedures defined in clauses 6.2.5 and 6.3 are used by the Shared O-RU Host to trigger the establishment of the NETCONF session with a NETCONF client of the Shared O-RU Host. The Shared O-RU Host can subsequently use the o-ran-mplane-int YANG model and the configured-client-info container to configure the Multi-Operator O-RU with NETCONF client information corresponding to the individual Shared Resource Operator(s) of the shared O-RU. Standard DHCP-based procedure, as specified in clause 5.1.4, still apply to retrieve NETCONF client information corresponding to the individual Shared Resource Operator(s) of the shared O-RU. NOTE: How the Shared O-RU Host becomes aware of information to identify the Shared Resource Operator's NETCONF clients to be used with a specific shared O-RU is out of scope of the present document. Following procedures defined in clause 6.3, this will trigger the Multi-Operator O-RU to perform additional call home procedures to any configured clients, which in this scenario will be the NETCONF clients corresponding to individual Shared Resource Operators. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.3.3 Enhanced sro-id based NETCONF access control | The resource configuration framework defines particular named list entries in the shared O-RU's configuration that can be allocated to an sro-id. The enhanced NACM privileges defined in this clause enable the Shared Resource Operator to configure the shared O-RU's list entries that have been previously configured by the Shared O-RU Host with the shared resource operator's sro-id. The O-RU NETCONF access control techniques defined in clause 6.5 are enhanced for operation with NETCONF clients corresponding to Shared Resource Operators of a shared O-RU, i.e. those where the user account of the NETCONF client has been configured with an sro-id. Specifically, the NETCONF access control read permissions for group name "carrier" are further refined for the following YANG models: • urn:o-ran:processing-elements:x.y • urn:o-ran:uplane-conf:x.y • urn:o-ran:performance-management:x.y • urn:o-ran:message5:x.y • urn:o-ran:shared-cell:x.y For the above models, the read privileges for specific node-instance-identifiers defined in Table 19.3.3-1 through Table 19.3.3-5 are refined based on the sro-id(s) associated with the user account of the NETCONF client. Normal NACM rules shall apply to any node-instance identifier not listed in the table. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 226 Table 19.3.3-1: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:processing-elements:x.y Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user- list entry containing a configured sro-id o-ran- elements:processing- elements/o-ran- elements:ru-elements A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-elements:processing- elements/o-ran-elements:ru-elements/o-ran-elements:sro-id leaf matches the sro-id of the NETCONF client. Table 19.3.3-2: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:uplane-conf:x.y Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user- list entry containing a configured sro-id o-ran-uplane-conf:user- plane-configuration/o-ran- uplane-conf:low-level-tx- links A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-tx-links/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user- plane-configuration/o-ran- uplane-conf:low-level-rx- links A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-rx-links/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user- plane-configuration/o-ran- uplane-conf:low-level-tx- endpoints A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user- plane-configuration/o-ran- uplane-conf:low-level-rx- endpoints A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user- plane-configuration/o-ran- uplane-conf:tx-array- carriers A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:tx-array-carriers/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user- plane-configuration/o-ran- uplane-conf:rx-array- carriers A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:rx-array-carriers/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 227 Table 19.3.3-3: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:performance-management:x.y Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user- list entry containing a configured sro-id o-ran-pm:performance- measurement-objects/o- ran-pm:rx-window- measurement-objects A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-pm:performance- measurement-objects/o-ran-pm:rx-window-measurement-objects/o-ran-pm:tr- measured-result/o-ran-pm:name leaf refers to an o-ran-elements:processing-elements/o-ran-elements:ru-elements list entry where the o-ran-elements:processing-elements/o-ran-elements:ru- elements/o-ran-elements:sro-id leaf represents the sro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran-pm:rx-window- measurement-objects/o-ran-pm:eaxc-measured-result/o-ran-pm:eaxc-id leaf matches a value of eaxcid in the container o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:e-axcid where the sro-id in o-ran-uplane-conf:user-plane-configuration/o-ran-uplane- conf:low-level-rx-endpoints/o-ran-uplane-conf:sro-id matches the sro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran- pm:rx-window-measurement-objects/o-ran-pm:eaxc-measured-result/o-ran- pm:eaxc-id leaf matches a value of eaxcid in the container o-ran-uplane-conf:user- plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:e- axcid where the sro-id in o-ran-uplane-conf:user-plane-configuration/o-ran-uplane- conf:low-level-tx-endpoints/o-ran-uplane-conf:sro-id matches the sro-id of the NETCONF client. o-ran-pm:performance- measurement-objects/o- ran-pm:tx-measurement- objects A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-pm:performance- measurement-objects/o-ran-pm:tx-measurement-objects/o-ran-pm:tr-measured- result/o-ran-pm:name leaf refers to an o-ran-elements:processing-elements/o-ran-elements:ru-elements list entry where the o-ran-elements:processing-elements/o-ran-elements:ru- elements/o-ran-elements:sro-id leaf represents the sro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran-pm:tx-measurement- objects/o-ran-pm:eaxc-measured-result/o-ran-pm:eaxc-id leaf matches a value of eaxcid in the container o-ran-uplane-conf:user-plane-configuration/o-ran-uplane- conf:low-level-rx-endpoints/o-ran-uplane-conf:e-axcid where the sro-id in o-ran- uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints/o- ran-uplane-conf:sro-id matches the sro-id of the NETCONF client or where the o-ran- pm:performance-measurement-objects/o-ran-pm:tx-measurement-objects/o-ran- pm:eaxc-measured-result/o-ran-pm:eaxc-id leaf matches a value of eaxcid in the container o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level- tx-endpoints/o-ran-uplane-conf:e-axcid where the sro-id in o-ran-uplane-conf:user- plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane- conf:sro-id matches the sro-id of the NETCONF client. NOTE: The enhanced sro-id based NACM privileges in Table 19.3.3-3 do not limit the privileges of a NETCONF client associated with an sro-id to read Rx and Tx performance management results when the object-unit-id is configured as RU. A Shared O-RU Host can exclude such value of object-unit-id from the configuration of the o-ran-performance-management YANG model to avoid enabling a first Shared Resource Operator from recovering aggregate O-RU level performance data that may include performance data related to the resources of a second Shared Resource Operator. Table 19.3.3-4: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:message5:x.y Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user- list entry containing a configured sro-id o-ran-msg5:ecpri-delay- message/o-ran- msg5:message5- sessions/o-ran- msg5:session-parameters A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges those list entries where the o-ran-msg5:ecpri-delay- message/o-ran-msg5:message5-sessions/o-ran-msg5:session-parameter/o-ran- msg5:processing-element-name leaf refers to an o-ran-elements:processing-elements/o-ran-elements:ru-elements list entry where the o-ran-elements:processing-elements/o-ran-elements:ru- elements/o-ran-elements:sro-id leaf represents the sro-id of the NETCONF client. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 228 Table 19.3.3-5: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:shared-cell:x.y Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user- list entry containing a configured sro-id o-ran-sc:shared-cell/o- ran-sc:shared-cell- config/o-ran-sc:shared- cell-copy-entities A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran- sc:shared-cell-config/o-ran-sc:shared-cell-copy-entities/o-ran-sc:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-sc:shared-cell/o- ran-sc:shared-cell- config/o-ran-sc:shared- cell-combine-entities A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran- sc:shared-cell-config/o-ran-sc:shared-cell-combine-entities/o-ran-sc:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-sc:shared-cell/o- ran-sc:shared-cell- config/o-ran-sc:shared- cell-copy-entities- selective-beam-id A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran- sc:shared-cell-config/o-ran-sc:shared-cell-copy-entities-selective-beam-id /o-ran- sc:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-sc:shared-cell/o- ran-sc:shared-cell- config/o-ran-sc:shared- cell-combine-entities-for- selective-beam-id A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran- sc:shared-cell-config/o-ran-sc:shared-cell-combine-entities-for-selective-beam-id /o-ran-sc:sro-id leaf-list includes the sro-id of the NETCONF client. For example, if the Shared O-RU has been configured to operate with two Shared Resource Operators, sro-id "23415" and sro-id "23410", then when a NETCONF client of the first Shared Resource Operator attempts to read the processing element configuration of the shared O-RU it can receive a reply as shown Figure 19.3.3-1, where the O-DU of the first Shared Resource Operator has an Ethernet MAC-address of 11:95:a0:af:5f:b9 and VLAN 100 is being used for the control and user-plane traffic between the shared O-RU and the O-DU of the first Shared Resource Operator. <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <processing-elements xmlns="urn:o-ran:processing-element:1.0"> <ru-elements> <name>element1</name> <sro-id>23415</sro-id> <transport-flow> <interface-name>10Geth0.100</interface-name> <eth-flow> <ru-mac-address>00:e0:fe:00:23:30</ru-mac-address> <vlan-id>100</vlan-id> <o-du-mac-address>11:95:a0:af:5f:b9</o-du-mac-address> </eth-flow> </transport-flow> <ru-elements> <processing-elements> </data> </rpc-reply> Figure 19.3.3-1: Example rpc-reply to a first sro-id "23415" Conversely, if the NETCONF client of the second Shared Resource Operator attempts to read the processing element configuration it can receive a reply as shown in Figure 19.3.3-2, where the O-DU of the second Shared Resource Operator has an Ethernet MAC-address of 5a:2a:a7:61:98:f0 and VLAN 200 is being used for the control and user-plane traffic between the Shared O-RU and the O-DU of the second Shared Resource Operator. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 229 <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <processing-elements xmlns="urn:o-ran:processing-element:1.0"> <ru-elements> <name>element2</name> <sro-id>23410</sro-id> <transport-flow> <interface-name>10Geth0.200</interface-name> <eth-flow> <ru-mac-address>00:e0:fe:00:23:30</ru-mac-address> <vlan-id>200</vlan-id> <o-du-mac-address>5a:2a:a7:61:98:f0</o-du-mac-address> </eth-flow> </transport-flow> <ru-elements> <processing-elements> </data> </rpc-reply> Figure 19.3.3-2: Example rpc-reply to a second sro-id "23410" In addition to the enhanced read access privileges, the NETCONF server of the shared O-RU shall implement additional write access privileges for the following YANG model: • urn:o-ran:uplane-conf:x.y For the above model, the write privileges for specific node-instance-identifiers are refined based on the sro-id associated with the user account of the NETCONF client, as described in Table 19.3.3-6. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 230 Table 19.3.3-6: Refined NETCONF Access Control Write Privileges for the "carrier" group with YANG module o-ran:uplane-conf:x.y Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured sro-id o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-tx-links/o-ran- uplane-conf:name The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-tx-links/o-ran- uplane-conf:sro-id The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-tx-links A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id shall only have write privileges to enable updating of those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-tx-links/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-rx-links/o-ran- uplane-conf:name The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-rx-links/o-ran- uplane-conf:sro-id The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-rx-links A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-rx-links/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-tx-endpoints/o- ran-uplane-conf:sro-id The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-tx-endpoints A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane- conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-rx-endpoints/o- ran-uplane-conf:sro-id The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:low-level-rx-endpoints A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane- conf:sro-id leaf-list includes the sro-id of the NETCONF client. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 231 Table 19.3.3-7: Refined NETCONF Access Control Write Privileges for the "carrier" group with YANG module o-ran:uplane-conf:x.y (continued) Restricted node-instance- identifier Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured sro-id o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:tx-array-carriers/o-ran- uplane-conf:sro-id The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:tx-array-carriers A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:tx-array-carriers/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:rx-array-carriers/o-ran- uplane-conf:sro-id The NETCONF client shall be prohibited from writing to this schema node for all list entries. o-ran-uplane-conf:user-plane- configuration/o-ran-uplane- conf:rx-array-carriers A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran-uplane-conf:user-plane- configuration/o-ran-uplane-conf:rx-array-carriers/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. 19.3.4 Supervision monitoring between shared O-RU and shared resource operator O-DUs An O-RU Controller associated with a Shared Resource Operator shall use the per O-DU monitoring capability specified in clause 14.1.1. The Shared O-RU Host shall configure the per-odu-monitoring container in o-ran- supervision YANG model with the sro-id and odu-id values agreed to be used by the Shared Resource Operator. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.4 Shared O-RU interface management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.4.1 VLAN and IP address management | The procedures defined in clauses 7.3 and 7.4 are used by the Shared O-RU Host to manage the VLAN and IP address configuration of the shared O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.4.2 Processing element configuration | The procedures defined in clause 7.5 are used by the Shared O-RU Host to configure the processing elements in the shared O-RU. The optional sro-id leaf shall be used by the Shared O-RU Host to configure a particular ru-element list entry as being uniquely associated with a particular Shared Resource Operator. NOTE 1: How the Shared O-RU Host becomes aware of information to identify the remote CU-Plane endpoints corresponding to the address(es) used by individual Shared Resource Operator O-DUs for control and user-plane traffic and included in the configuration of an ru-element list entry is out of scope of the present document. The Shared Resource Operator O-DU needs to become aware of the local endpoint(s) in the O-RU configured for use in processing element(s) used by a particular Shared Resource Operator. One approach for the Shared Resource Operator O-DU to become aware of such information is for the NETCONF client of the Shared Resource Operator O-DU to subscribe to receive notifications due to updates of the O-RU's configuration datastore, using the techniques described in clause 6.4. NOTE 2: Any other approaches by with the operator of a Shared Resource Operator O-DU becomes aware of information related to the configured processing elements is out of scope of the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 232 19.4.3 Shared resource operator O-DU verification of C/U-Plane transport connectivity The procedures defined in clause 7.6 are used by the Shared O-RU Host to configure the operation of C/U plane transport connectivity checks. These checks are able to be simultaneously performed between the individual Shared Resource Operator O-DUs and the shared O-RU. A Shared Resource Operator O-DU is able to recover details of the configured Maintenance End Point (MEP) and other necessary information on the Shared O-RU by reading the configuration associated with the o-ran-lbm YANG model. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.5 Shared O-RU C/U-Plane delay management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.5.1 Adaptive delay operation with shared O-RU | Clause 14.2 of [2] specifies that the Shared O-RU Host configures shared O-RU aspects related to delay management. When a shared O-RU indicates that it supports the optional ADAPTIVE-RU-PROFILE feature, the Shared O-RU Host can decide not to employ such a feature. If the Shared O-RU Host decides to use the ADAPTIVE-RU-PROFILE feature, the Shared O-RU Host shall be responsible for configuring the adaptive-delay-configuration container. NOTE 1: How the Shared O-RU Host determines the parameters to use in the o-du-delay-profile container and/or the transport-delay container is out of scope of the present document. NOTE 2: Operation of the optional O-RU adaptive delay capability defined in clause 7.8 requires carriers to be disabled prior to the O-RU adapting its delay profile. If used by the Shared O-RU Host, how the shared O-RU host co-ordinates disablement of carriers amongst the Shared Resource Operators is out of scope of the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.5.2 Measuring transport delay parameters with Shared O-RU | As defined in clause 7.9, an O-RU that supports the optional eCPRI based delay measurement capability shall be able to support simultaneous operation of delay measurements over any configured processing element. Where these processing elements correspond to remote endpoints from different Shared Resource Operator O-DUs, the operation of eCPRI delay measurements will allow each Shared Resource Operator O-DU to recover the necessary timing compensation information from the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.6 Shared O-RU configuration management | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.6.1 Carrier configuration of the shared O-RU | The "carrier" NACM privileges defined in clauses 6.5 and 19.3.3 prevent a NETCONF client with "carrier" privileges, and whose user account is configured with an sro-id, from creating particular named list entries for the following lists: • o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-links • o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-links • o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints • o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints • o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:tx-array-carriers • o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:rx-array-carriers A NETCONF client with "carrier" privileges and whose user account is configured with an sro-id shall only be permitted to update list entries after the list entry has been created and configured with a sro-id associated with the Shared Resource Operator. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 233 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.6.2 Notification of configuration updates to shared resource operators | All Multi-Operator O-RUs shall support the Notification of Updates to its Configuration Datastore functionality, as described in clause 9.4. Hence, any Shared Resource Operator may configure subscriptions to receive notifications of modifications to a shared O-RU's datastore, according to the defined NETCONF access control privileges for NETCONF client of the Shared Resource Operator. In particular, such an approach can be used by a Shared Resource Operator to determine when the shared O-RU host has configured o-ran-uplane-conf list entries which include the Shared Resource Operator's sro-id. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.7 Shared O-RU performance management | The NETCONF client of a Shared Resource Operator is identified by using a user list entry in o-ran-usermgmt YANG model that contains a configured sro-id. Such a NETCONF client shall have restricted access privileges to the o-ran- performance-management YANG model as described in clause 19.3.3. An O-RU supporting the SHARED-ORU-MULTI-OPERATOR feature should support the GRANULARITY- TRANSPORT-MEASUREMENT and/or the GRANULARITY-EAXC-ID-MEASUREMENT features. These allow the O-RU to report rx-window-measurement-objects on a per ru-element and/or eaxcid basis, meaning window measurements pertain to the transport flows and/or eaxcids associated with a particular Shared Resource Operator. A Shared O-RU Host can configure multiple remote-file-uploads list entries corresponding to the individual file servers of different Shared Resource Operators. However, there is currently no role-based access control applied to file management based performance management reporting, as specified in clause 10.3.2. If access to configured measurement results needs to be controlled on a per Shared Resource Operator basis, file management based performance management should not be used. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.8 Shared O-RU fault management | There is no role-based access control applied to O-RU fault management. Any NETCONF client, including those corresponding to Shared Resource Operator NETCONF client, are able to recover the active-alarm-list from the shared O-RU and are able to subscribe to receive notifications of future alarms as described in clause 11. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 19.9 Synchronization aspects of shared O-RU | Clause 14.3 of [2] specifies the synchronization aspects of shared O-RU. Each individual Shared Resource Operator should subscribe to receive the notifications defined in the o-ran-sync YANG model. 19.10 Co-ordinating service impacting procedures 19.10.1 Reset operation The various procedures required to be performed by Shared O-RU Host may necessitate performing reset of the shared O-RU. The Shared O-RU Host should co-ordinate such procedures with the individual Shared Resource Operators. NOTE: How the Shared O-RU Host performs such co-ordination is out of scope of the present document. 19.10.2 Locked administrative state The Shared O-RU Host can configure the admin-state of the shared O-RU which permits the Shared O-RU Host to set the admin-state to locked. The Shared O-RU Host should co-ordinate any changes to the admin-state of the shared O-RU with the individual Shared Resource Operators. NOTE: How the Shared O-RU Host performs such co-ordination is out of scope of the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 234 19.10.3 Antenna calibration When the shared O-RU supports antenna calibration, the Shared O-RU Host shall be responsible for co-ordinating the operation of the antenna calibration procedure with individual Shared Resource Operators. NOTE: How the Shared O-RU Host performs such co-ordination is out of scope of the present document. 19.11 Partitioning of shared O-RU carrier resources 19.11.1 Partitioning of Shared O-RU advertised resources O-RU capabilities as a whole shall be advertised by the O-RU (e.g. parameters defined in o-ran-module-cap.yang, o-ran-beamforming.yang) at start-up to each SRO and Shared O-RU Host. Hence, each SRO sharing the O-RU shall be aware of complete O-RU resources. These O-RU resources shall be partitioned between multiple SROs based on pre-defined agreement (outside the scope of the present document). Each SRO is expected to configure and use its partitioned O-RU resources so that the maximum O-RU capacity is not exceeded. To clarify this with an example, value of parameters 'max-gain' and 'min-gain' in o-ran-uplane-conf YANG model, shall not be exceeded when multiple SROs use the same tx-array for the carriers configured by each of them. 19.11.2 Partitioning of eAxC identities The eAxC-IDs are required to be unique within the shared O-RU in the same direction (Tx or Rx) even across different processing elements that may correspond to connection to different Shared Resource Operators. The Shared O-RU Host partitions the eAxC-IDs between different Shared Resource Operators. NOTE: How the Shared O-RU Host decides on the eAxC-ID partitioning policy and how the partition policy information is signalled to the respective Shared Resource Operators is out of scope of the present document. The procedures described in clause 19.6.2 can be used by the Shared O-RU Host to confirm whether a Shared Resource Operator is adhering to the eAxC-ID partitioning policy. 19.11.3 Partitioning of links, endpoints and array carriers The Shared O-RU Host creates the list entries for low-level-tx-links, low-level-rx-links, low-level-tx-endpoints, low-level-rx-endpoints, tx-array-carriers and rx-array-carriers, including unique configured name and one or more configured sro-id. The sro-id is used to partition links and array carriers between separate Shared Resource Operators. 19.11.4 Partitioning of static endpoints The Shared O-RU Host allocates static-low-level-rx-endpoints and static-low-level-tx-endpoints to individual Shared Resource Operators. This allocation may take into account Shared Resource Operator requirements related to static configuration for PRACH and SRS as well as TDD pattern configuration. To allocate a static-low-level-tx-endpoint to a Shared Resource Operator, the Shared O-RU Host shall configure the low-level-tx-endpoints list entry with the name of the static-low-level-tx-endpoint and the sro-id of the Shared Resource Operator. To allocate a static-low-level-rx- endpoint to a Shared Resource Operator, the Shared O-RU Host shall configure a low-level-rx-endpoints list entry with the name of the static-low-level-rx-endpoint and the sro-id of the Shared Resource Operator. The procedures described in clause 19.6.2 can be used by the Shared O-RU Host to confirm whether a Shared Resource Operator is adhering to the static endpoint partitioning policy. 19.11.5 Shared O-RU beamforming configuration When the shared O-RU supports the o-ran-beamforming YANG model, the allocation of array carrier resources and band configuration to individual Shared Resource Operators will refer to any corresponding static beamforming configuration of the shared O-RU. In this version of the specification, the operation of a shared O-RU with rt-bf-weights-update-support set to true is not defined. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 235 19.11.6 Shared O-RU with antenna line devices When the shared O-RU is connected to one or more antenna line devices as described in clause 14.4, the shared O-RU host shall be responsible for the operation of the antenna line devices. NOTE 1: How the details of the configuration of the one or more antenna line devices are shared with the respective Shared Resource Operators is out of scope of the present document. The Shared O-RU Host may be required to co-ordinate antenna line operations with the different Shared Resource Operators, e.g. remote electrical tilt. NOTE 2: How the Shared O-RU Host coordinates such operations is out of scope of the present document. 19.12 Example shared O-RU carrier configuration and operation procedure An example procedure for configuring a shared O-RU is as follows: 1) The Shared O-RU Host is assigned "sudo" privileges. The Shared O-RU Host allocates an sro-id to the Shared Resource Operator and creates account(s) for the Shared Resource Operator's NETCONF client(s) on the O-RU's NETCONF server which includes the sro-id. The Shared O-RU Host communicates the account information to the Shared Resource Operator. Optionally, the Shared O-RU Host can subscribe to be notified of updates to the O-RU's configuration datastore, using the techniques specified in clause 9.4. 2) The Shared O-RU Host configures the list of ru-elements for the Shared Resource Operator based on agreed O-DU transport identifiers. Each such element has the corresponding sro-id parameter set to the value allocated to the Shared Resource Operator. NOTE 1: How the Shared O-RU Host becomes aware of information to identify the remote CU-Plane endpoints corresponding to the address(es) used by individual Shared Resource Operator O-DUs for control and user-plane traffic and included in the configuration of an ru-element list entry is out of scope of the present document. 3) The Shared O-RU Host creates the tx-array-carriers and rx-array-carriers list entries in relation to the agreed tx-arrays and rx-arrays for use by the Shared Resource Operator. Each of the list entries will have the corresponding sro-id allocated to the Shared Resource Operator configured in the list of sro-ids associated with the array carriers. NOTE 2: Configuring the tx-array-carriers and rx-array carriers list entries includes mandatory leaves which are specific to the Shared Resource Operator's configuration. The Shared O-RU Host can agree with the Shared Resource Operator how it will configure any mandatory parameters in its initial list configuration. 4) The Shared O-RU Host creates low-level-tx-endpoints and low-level-rx-endpoints related to agreed partitioned static-low-level-tx endpoints and static-low-level-rx-endpoints respectively. Each of the list entries will have the corresponding sro-id allocated to the Shared Resource Operator configured in the list of sro-ids associated with the endpoints. NOTE 3: Configuring the low-level-tx-endpoints and low-level-rx-endpoints list entries includes mandatory leaves which are specific to the Shared Resource Operator's configuration. The Shared O-RU Host can agree with the Shared Resource Operator how it will configure any mandatory parameters in its initial configuration. NOTE 4: The Shared O-RU Host and the Shared Resource Operator can agree how information describing the list entries created in steps 2, 3 and 4 are to be shared. In one example, information is shared out of band between the two operators. In a second example, the operators can agree that the Shared Resource Operator will use a GET RPC to read the list entries configured by the Shared O-RU Host. Using this second approach, the NACM privileges ensure that the Shared Resource Operator only has permissions to read list entries that have been configured with its sro-id. 5) The Shared Resource Operator enters the pre-configured list entry information into its management systems. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 236 6) The Shared O-RU Host configures the configured-client-info container with IP address(es) of the NETCONF client(s) used by the Shared Resource Operator. This triggers the shared O-RU to call home to the configured client. The Shared Resource Operator uses the shared account information to establish a NETCONF session to the shared O-RU. 7) The Shared Resource Operator uses the NETCONF session to complete the configuration of the relevant o-ran-uplane-conf defined list entries for tx-array-carriers, rx-array-carriers, low-level-tx-endpoints and low-level-rx-endpoints. As the list entries are all configured with the sro-id of the Shared Resource Operator, then the NACM privileges described in clause 19.3.3 permit the Shared Resource Operator to over-write the initial mandatory parameters configured by the Shared O-RU Host with its required operational values. If the Shared O-RU Host subscribed to be notified of modifications to the O-RU's configuration store in step 1, then the Shared O-RU Host will be automatically notified of the committed changes to the shared O-RU's configuration by the Shared Resource Operator. 8) The Shared O-RU Host can read the modified configuration of the shared O-RU and the information used to determine whether the configuration by the Shared Resource Operator adheres to pre-agreed sharing policies. NOTE 5: How to determine whether the configuration adheres to a pre-agreed policy as well as any response triggered by determining that a configuration does not adhere to a pre-agreed policy are not defined in the present document. With the above steps successfully performed, the relationship between C/U-Plane application endpoints at Shared Resource Operator's O-DU and shared O-RU is configured. 9) The Shared O-RU Host and Shared Resource Operator can subscribe to receive notifications of O-RU alarms. 10) The Shared O-RU Host configures the performance measurements performed by the shared O-RU. NOTE 6: The Shared O-RU Host and the Shared Resource Operator can agree how information describing the configured performance measurements are to be shared. In one example, information is shared out of band between the two operators. In a second example, the operators can agree that the Shared Resource Operator will use a GET RPC to read the performance management configuration. Using this second approach, the NACM privileges ensure that the Shared Resource Operator only has permissions to read performance management configuration associated with the ru-elements list entries and/or exacid values associated with the Shared Resource Operator's sro-id. 11) The Shared Resource Operator can subscribe to receive notifications related to the shared O-RU's performance management counters. The NACM privileges defined in clause 19.3.3 restricts the Shared Resource Operator to only be able to recover measurements associated with the ru-elements list entries and/or exacid values associated with the Shared Resource Operator's sro-id. 12) The Shared Resource Operator performs carrier activation by setting the value of the parameter "active" at tx-array-carrier element / rx-array-carrier element to "ACTIVE" for those list entries configured with the sro-id of the Shared Resource Operator. 13) The Shared Resource Operator performs shared resource operator supervision as specified in clause 19.3.4. If an O-RU enters shared resource supervision failure, then as described in clause 19.3.4, the shared O-RU will deactivate any carriers uniquely associated with the sro-id of the Shared Resource Operator and raise an alarm notification indicating that it has lost SRO based supervision. 19.13 Shared O-RU and LAA operation Operation of M-Plane procedures as specified in clause 16 by a Shared Resource Operator using a NETCONF account with "carrier" privileges is not defined in the present document. NOTE: This does not prevent the Shared O-RU Host from configuring LAA operation to operate in combination with its own component carriers. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 237 19.14 Shared O-RU operation in combination with shared cell Operation of M-plane procedures as specified in clause 17 by a Shared Resource Operator using a NETCONF account with "carrier" privileges is restricted based on the sro-id configured in the user-list entry for the NETCONF account. A shared O-RU that indicates it supports the o-ran-shared-cell model in its YANG library shall support the partitioning of copy and combine entities on an sro-id basis and limit read access to those list-entries where the configured sro-id matches that of the NETCONF account, as specified in clause 19.3.3. The present document further restricts all write access to the shared-cell YANG model from NETCONF accounts with user name user-list entry containing a configured sro-id and "carrier" privileges. As a consequence, the Shared O-RU Host shall be responsible for configuring shared cell copy and combine parameters on behalf of each Shared Resource Operator. NOTE: How the Shared O-RU Host co-ordinates the configuration of copy and combine parameters between one or more Shared Resource Operators is outside the scope of the present document. 19.15 Certificate and trust anchor management For mTLS, both the client and the server need to have access to a trust anchor to verify the peer. NOTE: It is the responsibility of the Shared Resource Operator and Shared O-RU Host to develop Trust Anchor management processes. Such processes are outside the scope of the present document. As explained in clause 6.2.6.0, a shared O-RU needs to be able to trace the peer's certificate path to a valid trust anchor. Also, the peer needs to be able to trace the shared O-RU's certificate path to a valid trust anchor. Peers of a shared O-RU include O-RU controllers operated by either the Shared O-RU Host or a Shared Resource Operator (SRO). In order to achieve mutual authentication: • The shared O-RU shall be enrolled with the Shared O-RU Host PKI as defined in clause 6.2.6.1 and enable new trust anchors to be provisioned as defined in clause 6.2.6.0. • An O-RU controller operated by the Shared O-RU Host should be enrolled with the Shared O-RU Host PKI and be provided with the trust anchor of the Shared O-RU Host PKI. • An O-RU controller owned by an SRO should be enrolled with that SRO's PKI and provide capabilities to be provisioned with new trust anchors. This allows a Shared O-RU Host to install the trust anchor(s) corresponding to SRO PKI(s) involved in the shared O-RU operation. This enables the O-RU to authenticate the O-RU controllers of all SROs and also allows all SROs involved in shared O-RU operation to install the trust anchor of the Shared O-RU Host PKI, enabling the O-RU controllers to authenticate the shared O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20 Network energy saving | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.1 Introduction | This clause describes the requirements and scope of energy savings techniques relevant to the lower layer split M-Plane interface. The following techniques are optionally supported by O-RUs to implement energy savings: • Carrier deactivation. • RF channel switch off/on (C-Plane controlled and M-Plane controlled). • Advanced sleep modes. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 238 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.2 Carrier deactivation for energy saving | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.2.1 High level principle of carrier deactivation for energy saving | This clause provides basic description of how an O-RU's carrier can be deactivated to achieve the energy savings within an O-RU. In order to achieve the energy saving, NETCONF Client uses the existing parameter [tr]x-array-carrier::active to activate or de-activate [tr]x-array-carriers. NETCONF Client configures the parameter to INACTIVE to deactivate specific carrier. This causes the parameter [tr]x-array-carrier::state transition to DISABLED (can go through BUSY). In a result, power consumption of O-RU is reduced because O-RU does not need to process C-Plane and U-plane traffic. Additionally, when [tr]x-array-carriers are inactive and when energy-saving-enabled is set to true, the O-RU may turn off circuitry associated with carrier processing to further reduce power consumption. NOTE 1: The actual reduced value of power consumption depends on the O-RU's implementation. NOTE 2: Prior to version 14 of the present document, the O-RU operation when active is set to SLEEP was not defined. Clause 15.3.2 now defines O-RU operation for such cases. NOTE 3: For details about how parameters energy-saving-enabled and [tr]x-array-carrier::active interact - see clause 9.1.3 "Modify state". |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.2.2 Synchronization aspects for carrier deactivation for energy saving | When power-state of o-ran-hardware is SLEEPING, C/U/S functions on O-RU may be stopped to reduce energy consumption. If O-RU stops S-plane function, a certain period which depends on the O-RU implementation will be required to make carrier activation again. NETCONF client should set energy-saving-enabled to FALSE to ensure O-RU is ready to immediately activate a carrier. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3 RF channel switch off/on for energy saving | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.1 TRX control - C-Plane controlled | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.1.1 Introduction | TRX control via C-Plane messages is used to achieve energy saving through disabling one or more O-RU array elements for a defined or undefined period of time. For example, an O-DU can switch off 32 out of 64 array elements of a massive MIMO antenna array. The TRX control capability is described below. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.1.2 TRX control module capabilities | The O-RU exposes the capability to support energy saving through disabling some or all of the O-RU's array elements by including support of the feature TRX-CONTROL in its o-ran-wg4-features.yang YANG module. If the feature is supported, then an O-RU controller can use the NETCONF session to recover the associated O-RU TRX control capability information and parameters. These capability attributes are defined for each [tr]x-arrays. These capabilities can be recovered by an O-RU controller at the O-RU start up as part of the o-ran-uplane-conf.yang YANG module operations. The attributes are: 1) trx-control-capability-info: A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to TRX Control for each [tr]x-arrays. The parameters in the container include the following: - supported-trx-control-masks: A list of TRX control configurations that are supported by the O-RU which are reported with their corresponding mask-name and antenna-mask values. Refer to the O-RAN CUS plane specification [2], clause 16.2 for more details on the usage of antenna masks. The absence of the list supported-trx-control-masks indicates that any combination of antenna mask is supported by the O-RU for a particular [tr]x-array. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 239 - sleep-mode-type: This value indicates the sleep modes supported by the O-RU for a particular [tr]x-array as specified in the O-RAN CUS plane specification [2], Table 16.1-1. - wake-up-duration: This value indicates the reported wake-up time (in microseconds) for each individual sleep mode for the TRX(s) corresponding to a particular [tr]x-array. The O-DU can convert the wake-up duration in microseconds to the respective number of slots based on the SCS(s) supported by the O-RU (for more details, refer to O-RAN CUS plane specification [2], clause 16.1). - wake-up-duration-guaranteed: The capability of the O-RU to guarantee the complete wake-up operation or to become active within the duration reported in wake-up-duration. The guaranteed wake- up time indicate a wake-up duration that is invariant to any O-RU condition. This field shall be reported as "FALSE" if the O-RU cannot assure the wake-up time, in which case the value reported in wake-up- duration is considered as the minimum wake-up duration. For sleep-mode-type reported as "SLEEP_MODE_0", the wake-up-duration-guaranteed shall be reported as "TRUE". Refer to the O-RAN CUS plane specification [2], clause 16.6 for more details on the differences between guaranteed and minimum wake-up durations. - defined-duration-sleep-supported: The capability of the O-RU to support the defined sleep functionality as specified in O-RAN CUS plane specification [2], clause 16.4. - undefined-duration-sleep-supported: The capability of the O-RU to support the un-defined sleep functionality as specified in O-RAN CUS plane specification [2], clause 16.5. 2) energy-saving-capability-common-info: A container in o-ran-module.cap.yang YANG module used to expose the O-RU capabilities common to both TRX control and advanced sleep modes. The parameters in the container include the following: - ST8-ready-message-supported: The capability of the O-RU to support the "ready" message via Section Type 8 command. This message is used to indicate the O-RU readiness after waking up from a commanded sleep mode having a non-guaranteed wake-up time. Refer to the O-RAN CUS plane specification [2], clauses 7.5.3.55 and 16.6.2 for more details on the ST8 ready command. - sleep-duration-extension-supported: The capability of the O-RU to support the extension of a defined sleep interval. Refer to the O-RAN CUS plane specification [2], clause 16.8 for more details on the sleep extension. - emergency-wake-up-command-supported: The capability of the O-RU to support emergency wake-up procedure. Refer to the clause 20.3.1.3 for more details on the emergency wake-up procedure. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.1.3 Emergency wake-up procedure for TRX control | This clause describes the optional capability by which the O-RU's CU plane processing units and/or array elements and/or other components that were put to sleep by a TRX Control command (or ASM command) can be woken up by the NETCONF client as specified in O-RAN CUS plane specification [2], clause 16.11. The O-RU exposes this ability to support emergency wake-up by including the leaf emergency-wake-up-command-supported in o-ran-module- cap.yang YANG module. A NETCONF client can send a <emergency-wake-up> RPC in order to wake-up the O-RU's CU plane processing units and/or array elements and/or other components that have been put to sleep by a TRX Control command as illustrated in Figure 20.3.1.3-1. In the case of Shared O-RU (O-RUs that support the SHARED-ORU-MULTI-OPERATOR feature), only the Shared O-RU Host can send a <emergency-wake-up> RPC which may include one or more optional sro-ids. Therefore, only the CU plane processing units and/or array elements that are specific to the O-DU that is associated with the received sro-id are woken-up. If sro-id is not included in the RPC, the O-RU shall wake-up all the CU plane processing units and/or array elements irrespective of the O-DU. Subsequently, a notification shall be sent by the O-RU to all subscribed O-DUs when the emergency wake-up procedure is complete, after which the O-DUs may activate carriers (if needed) and then operate the C-Plane and U-Plane to support user traffic. In the case of Shared O-RU (O-RUs that support the SHARED-ORU-MULTI- OPERATOR feature), separate notification shall be sent for each sro-id received in the RPC. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 240 Figure 20.3.1.3-1: Emergency Wake-up Procedure |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.1.4 Interaction with M-Plane processing | An O-RU supporting RF channel switch off/on for energy saving shall be able to disable C/U plane monitoring (see clause 7.10). For example, an O-RU may support the cu-plane-monitoring container in its o-ran-supervision.yang model, allowing an O-DU to disable C/U plane monitoring operation. Operation of other M-plane procedures, including measuring of transport delay (clause 7.9), C/U plane transport connectivity verification (clause 7.6) and O-RU synchronization (clause 13) shall not be affected by network energy savings functionality. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.2 TRX control - M-Plane controlled | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.2.1 Introduction | TRX control via M-Plane messages is used to achieve energy saving through disabling one or more O-RU array elements for an undefined period of time (until a next command is received). For example, an O-DU can switch off 32 out of 64 array elements of a massive MIMO antenna array. The TRX control capability and configuration are described in clauses 20.3.2.2 and 20.3.2.3. NOTE: Clause 15.3.2 specifies another set of conditions allowing O-RU to save energy by disabling array elements. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.2.2 TRX control capability | The O-RU exposes the capability to support energy saving through disabling some or all of the O-RU's antenna array elements by including support of the feature MPLANE-TRX-CONTROL in its o-ran-wg4-features.yang YANG module. If the feature is supported, then an O-RU controller can use the NETCONF session to recover the associated O-RU TRX control capability information and parameters. These capability attributes are defined for each [tr]x-arrays. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 241 These capabilities can be recovered by an O-RU controller at the O-RU start up as part of the o-ran-uplane-conf.yang YANG module operations. The attributes are: 1) mplane-trx-control-txarr-capability-info: A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to TRX Control for each tx-arrays. The parameters in the container include the following: - mplane-trx-control-supp-antenna-masks: A grouping which contains the list mplane-supported-trx- control-masks, which is a list of TRX control configurations that are supported by the O-RU which are reported with their corresponding antenna-mask values. Refer to the O-RAN CUS plane specification [2], clause 16.2 for more details on the usage of antenna masks. The absence of the list mplane-supported -trx-control-masks indicates that any combination of antenna mask is supported by the O-RU for a particular [tr]x-array. If an antenna mask list is present, an all-ones antenna mask shall be included in the list to assure all array elements can be turned on. NOTE: If the mplane-supported-trx-control-masks contains a single all-ones antenna mask, that means the only valid antenna mask to configure is all array elements activated, meaning the TRX Control capability is not present. 2) mplane-trx-control-rxarr-capability-info: A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to TRX Control for each rx-array. The parameters in the container include the following: - mplane-trx-control-supp-antenna-masks: Same as this parameter description within mplane-trx- control-txarr-capability-info above. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.2.3 TRX control configuration | To support [tr]x-array level O-DU controlled antenna array configuration, new O-RU level node array-config-group is introduced. For M-Plane TRX control the node contains two lists tx-array-antenna-mask-config and rx-array- antenna-mask-config, one each for specifying tx-array and rx-array configuration for TRX control respectively. The list is indexed using array-name and contains parameters antenna-bitmask and antenna-bitmask-index. These two parameters per tx-array and rx-array list entry may be used by the O-RU controller to perform TRX Control. It is problematic if TRX Control commands are issued for sub-arrays of a larger array due to the potential interaction of multiple TRX Control commands affecting the same array elements which are part of multiple [tr]x-arrays. Therefore, the antenna mask configuration shall be done for the largest tx or rx-array that is advertised by the O-RU, not for the tx-array or rx-array which is a subset of the largest array (multiple non-overlapping largest arrays are possible). The effect of the configuration command shall be to impact the largest array (whether that largest array has any carriers assigned to it or not). For the case where the O-RU advertises mplane-supported-trx-control-masks list, RPC edit-config shall be used to configure a specific antenna mask value by specifying a given antenna-bitmask-index for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config . EXAMPLE 1: Configuration of a given 32-bit tx antenna mask by specifying the antenna-index: <tx-array-antenna-mask-config> <array-name> tx-array-1 </array-name> <antenna-bitmask-index> 1 </antenna-bitmask-index> </tx-array-antenna-mask-config> For the case where the O-RU does not advertise mplane-supported-trx-control-masks list for a given [tr]x-array, the RPC edit-config shall be used to configure a specific antenna-bitmask value for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. EXAMPLE 2: Configuration of a 32-bit tx antenna mask is shown below: <tx-array-antenna-mask-config> <array-name> tx-array-1 </array-name> <antenna-bitmask >11111111000000000000000011111111</antenna-bitmask > ETSI ETSI TS 104 023 V17.1.0 (2026-01) 242 </tx-array-antenna-mask-config> NOTE: Binary values are encoded with a base-64 encoding (see reference [4]) so the above mask would actually be represented as "/wAA/w==". Prior to any M-Plane TRX Control antenna mask or associated antenna index being configured, the value of the antenna mask shall be considered to be all-ones, meaning all array-elements are enabled. Because updating an antenna mask via M-Plane is an asynchronous operation, the O-RU shall notify all notification subscribers that the [tr]x-array specific commanded mask or antenna mask index has been activated, using the mplane- trx-control-ant-mask-update notification. To reduce unexpected transient related to the turning-off process, the O-DU may send zero-value beamforming weights for any array element to be turned off prior to issuing the edit-config command turning off any array-elements, and may keep them at zero-value while the array-elements are off. To reduce unexpected transient related to the turning-on process, the O-DU may send zero-value beamforming weights for any disabled array element to be turned on prior to issuing the edit-config command turning on the array-elements, and may keep them at zero-value until receiving the notification that the new antenna mask activating those array elements is received. When TRX Control has disabled all array elements in a [tr]x-array, the O-RU may disable CU-Plane processing associated with all array-carriers using that [tr]x-array, and the O-DU should assume that the CU-Plane processing for those array-carrier has been halted by the O-RU. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.2.4 Interaction with M-Plane processing | An O-RU supporting M-Plane controlled TRX Control for energy saving shall be able to disable C/U plane monitoring (see clause 7.10). For example, an O-RU may support the cu-plane-monitoring container in its o-ran-supervision.yang model, allowing an O-DU to disable C/U plane monitoring operation. Operation of other M-plane procedures, including measuring of transport delay (clause 7.9), C/U plane transport connectivity verification (clause 7.6) and O-RU synchronization (clause 13) shall not be affected by this network energy savings feature's functionality. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.2.5 Interaction with C-Plane TRX Control and ASM | An O-DU using M-Plane TRX Control for energy saving shall be able to also use C-Plane TRX Control when an O-RU supports both. However, the O-DU shall ensure the current M-Plane-commanded antenna mask (using antenna-mask or antenna-index pointing to O-RU advertised supported antenna mask) is all-ones (all array elements active) prior to issuing any C-Plane TRX Control commands, and the O-DU shall ensure the current C-Plane-commanded antenna mask is all-ones (all array-elements active) prior to issuing any M-Plane TRX Control commands. An O-DU using M-Plane TRX Control for energy saving shall be able to also use C-Plane ASM when an O-RU supports both. However, the O-DU shall ensure the current M-Plane-commanded antenna mask is all-ones (all array elements active) prior to issuing any C-Plane ASM commands, and the O-DU shall ensure the current C-Plane- commanded ASM conditions are terminated prior to issuing any M-Plane TRX Control commands. NOTE: The antenna mask is considered to be all-ones prior to any M-Plane or C-Plane TRX Control command being issued. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.