hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.3 Data layer control | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.3.1 Introduction | Data layer control is used to achieve energy saving through reducing the number of data layers independent of TRX-Control. For example, the energy consumption of an O-RU can be reduced by turning off certain HW components like processing units of FPGA/GPUs or CPU/GPU cores or by running at a lower clock speed along with reduced processing requirements [i.6]. The methodology of data layer control using endpoint switch off/on is described in clause 20.3.3.2. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 243 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.3.3.2 Capability and configuration of data layer control | This clause provides basic description of how an O-RU's data layers can be reduced to achieve the energy savings within an O-RU. The O-RU exposes the capability to support energy saving by including support of the feature MPLANE-DATA-LAYER-CONTROL in its o-ran-wg4-features.yang YANG module. The support of this feature means an O-RU shall advertise the data node energy-sharing-group-id per static-low-level-[tr]x-endpoints. Multiple endpoints that have the same energy-sharing-group-id value signifies that these endpoints share common underlying HW components. When an O-RU indicates it supports the MPLANE-DATA-LAYER-CONTROL feature, a global configuration leaf-list parameter energy-sharing-groups-disabled is available in the o-ran-uplane-conf YANG model. An O-RU Controller may turn off a group of data layers by adding one or more energy-sharing-group-id into the energy- sharing-groups-disabled list. When one or more energy-sharing-group-id is included in the energy-sharing-groups- disabled list, the O-RU shall switch off the underlying HW components common to that energy-sharing-group-id thereby resulting in energy savings. If an endpoint has multiple energy-sharing-group-id, the underlying HW components associated with the endpoint shall be turned off if any of the energy-sharing-group-id corresponding to the endpoint is added to the leaf-list energy-sharing-groups-disabled. The O-RU controller shall trigger data layer control only for the energy-sharing-group of endpoints all of whose eAxC-id values are currently not being used by the O-DU (i.e. not referenced, either directly or indirectly, within any CU-plane messages, e.g. by using Section Extension 10). An O-RU controller may turn on a group of data layers by removing the energy-sharing-group-id from the energy- sharing-groups-disabled list. When the energy-sharing-group-id is removed from the energy-sharing-groups- disabled list, the O-RU shall switch on the underlying HW components common to that energy-sharing-group-id. If an endpoint has multiple energy-sharing-group-id, the underlying HW components associated with the endpoint shall be turned on only if all the energy-sharing-group-id corresponding to the endpoint are removed from the leaf-list energy-sharing-groups-disabled. Subsequently, when the wake-up procedure is complete a notification shall be sent by the O-RU to all subscribed O-RU controllers as detailed in Figure 20.3.3.2-1. Figure 20.3.3.2-1: Data layer control wake-up notification ETSI ETSI TS 104 023 V17.1.0 (2026-01) 244 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.4 Advanced sleep modes for energy saving | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.4.1 ASM module capabilities | The O-RU exposes its ability to support energy saving by disabling some part of the processing, which impacts the O-RU's array elements (based on the command scope of the received ST4 message) by including support of the feature ADVANCED-SLEEP-MODE in 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 O-RU ASM capabilities. 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. The attributes are: 1) asm-capability-info: A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to Advanced sleep modes for each [tr]x-arrays. The parameters in the container include the following: - sleep-mode-type: This value indicates the sleep mode 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 a particular sleep mode for 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 full wake-up operation within the time reported in wake-up-duration. 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 time. 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. NOTE: The leafs sleep-mode-type, wake-up-duration, wake-up-duration-guaranteed, defined-duration-sleep- supported, undefined-duration-sleep-supported defined in this clause are distinct from the leafs of the same name defined in clause 20.3.1.2. 2) The container energy-saving-capability-common-info as defined in clause 20.3.1.2 is also applicable for ASM. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.4.2 Emergency wake-up procedure for ASM | The O-RU shall support emergency wake-up procedure for Advanced sleep modes similar to TRX control as described in clause 20.3.1.3. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.4.3 Interaction with M-Plane processing | An O-RU supporting advanced sleep modes 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. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 245 |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.5 Deep-hibernate | |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.5.1 Introduction | Deep-hibernate is an O-RU mode used to achieve relatively higher energy saving by disabling all carriers and stopping the C/U/S/M functions and corresponding processing units when compared to power-state defined in clause 9.1.3 or advanced sleep mode defined in clause 20.4. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.5.2 Deep-hibernate module capabilities | The O-RU exposes its ability to support deep hibernate functionality by including support of the feature DEEP- HIBERNATE in its o-ran-wg4-features.yang YANG module. The support of this feature means an O-RU shall advertise the data node max-hibernate-time-duration and optionally advertise data node min-hibernate-time- duration. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 20.5.3 Configuration of deep-hibernate | This clause provides description of how deep-hibernate can be activated in the O-RU. An O-RU Controller shall send an RPC <deep-hibernate> to activate the deep-hibernate in O-RU, which initiates the corresponding timer. The RPC shall include the hibernate-time duration. Before the O-DU sends the deep-hibernate RPC, the O-DU shall ensure that all [tr]x-array-carrier(s) shall be deactivated as defined in Figure 15.3.2-0b. If an O-RU receives a deep-hibernate RPC while one or more [tr]x-array- carriers are active, then it shall reject the RPC, including in the error-message the reason why deep-hibernation cannot be activated. If the deep-hibernate RPC is accepted by the O-RU, the O-RU shall cease processing control-plane, user-plane and synchronization plane operations. If accepted, the O-RU shall send a notification to all subscribed O-RU Controllers to indicate the deep-hibernate is activated, where the notification shall also indicate the hibernate-time. Upon receiving notification from an O-RU, a subscribed O-RU Controller shall send the RPC <close-session> to the O-RU. The O-RU shall suspend all NECTONF call home operations and/or PNF Registration operations after deep-hibernate mode activated. Once all NETCONF sessions are terminated, the M-Plane functions on O-RU shall then be stopped to reduce the further energy consumption and O-RU enters deep-hibernate. The O-RU shall not respond to any incoming NECTONF session while in deep-hibernate mode. NOTE: If any NETCONF session is not closed by NETCONF Client then the O-RU behavior is unspecified. At the end of hibernate-time, the O-RU shall perform a re-start and follow the procedures defined in Figure 6.1-1. Upon restart, the O-RU shall set the restart-cause to DEEP-HIBERNATE-RESTART using o-ran-operations.yang YANG module. In case of autonomous O-RU restart while in deep-hibernate mode, e.g. because of some software failure, the O-RU is not expected to continue the deep-hibernate mode. In the case the O-RU is operating as a Shared O-RU as described in clause 19, an O-DU operating with "carrier" privileges as defined in Table 6.5-1 shall be prohibited from sending the RPC <deep-hibernate>. How the Shared O-RU Host coordinates with other O-DU(s) for the deep-hibernate activation is out of scope of the present document. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 246 Figure 20.5.3-1: Deep hibernate operation ETSI ETSI TS 104 023 V17.1.0 (2026-01) 247 21 Received power measurements for shared spectrum bands |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 21.1 Introduction | There exists some spectrum that is designated as shared spectrum. To improve the sharing experience, received power measurements can be beneficial in understanding the level to which the shared spectrum is being used. Citizens Broadband Radio Service (CBRS) is an example of such a shared spectrum allocation, corresponding to 150 MHz of spectrum in the 3,5 GHz band (3 550 MHz to 3 700 MHz) in the United States. CBRS band is lightly licensed and the use is expected to reduce the cost of data transmissions. The CBRS architecture introduces the Spectrum Access System (SAS) function that is responsible for authorization and manages use of the shared spectrum [i.8]. To help inform the SAS of the wireless environment, the O-RU can optionally support measurements of shared spectrum bands. An O-RU supporting such optional capability shall include the o-ran-frequency-band-measurement model in its YANG library. This clause 21 applies to O-RUs that support this optional capability. NOTE: This clause 21 defines the use of NETCONF-based procedures between an O-RU and an O-RU controller for performing measurements of shared spectrum bands. Signalling between the O-RU Controller and the SAS are out of scope of the present document. |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 21.2 Measurement Procedure | An O-RU controller can use the received-power-measurement-request RPC to trigger the O-RU to start measurements, as illustrated in Figure 21.2-1. The O-RU can report its capabilities to the NETCONF client. These capabilities are defined in o-ran-frequency-band- measurement.yang module. The attributes included are: • measurement-bands-supported: The supported frequency range for which an O-RU can perform the received power measurement. • in-service-measurement: Indicates whether O-RU can support measurements when tx-array carriers are active in measurement band. • in-service-measurement-only-carrier-freq: Indicate an O-RU only support measurement on frequency range as carrier is configured on when in-service-measurement is TRUE. • supported-measurement-points: Indicates which measurement point(s) are supported by the O-RU. Defined measurement points are NO_ARRAY, ONE_ARRAY and MULTIPLE_ARRAYS. Depending on the reported measurement points, the O-RU supports measurements without an rx-array name provided (NO_ARRAY), with a single rx-array name provided (ONE_ARRAY) and/or with multiple rx-array names provided (MULTIPLE_ARRAYS). If ONE_ARRAY or MULTIPLE_ARRAY is reported by the O-RU, then the O-RU controller shall configure the rx-array name(s) as the measurement point in the rx-array leaf-list in the received-power-measurement-request rpc. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 248 Figure 21.2-1: CBRS measurement flow |
520fd169b99a3782dbe78bb36391dd5e | 104 023 | 21.3 Measurement attributes | Following received-power-measurement-request rpc is used to trigger the measurement and subsequent notification of the measurement results. • rpc: received-power-measurement-request - input measurement-bandwidth: This is the measurement unit. measurement-start-frequency: This is the start frequency range requested for measurement. For band n48, the limited range is 3 550 - 3 700 MHz. O-RU can report the measurement of continuous spectrum or the limited discontinuous spectrum. When the O-RU does not have a spectrum grant from the CBRS system, received power shall be measured and reported over the entire CBRS band in segments that do not exceed 10 MHz per measurement report. When the O-RU has a spectrum grant from the CBRS system, received power shall be measured and reported over one or more frequency ranges that do not exceed 10 MHz per measurement report. rx-array: The measurement point for which the O-RU shall provide measurements. The supported values depend on the supported-measurement-points capability. If multiple rx-array names are provided, then the rx-arrays shall be allocated in the same sector and for each measurement (identified by measurement-start-frequency), only one value of received-power shall be reported. - output status: whether O-RU accepted or rejected the measure request. error-message: The detailed error message when the operation is failed. If the requested range is out of O-RU's Instantaneous BandWidth (IBW) then it can output status as FAILED with a detailed error-message. wait-time: Declare the expected time for report delivery in notification. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 249 measurement-id: Identify an RPC for one measurement. • notification: power-measurement-result - status: whether O-RU accepted or rejected the measure request. - error-message: The detailed error message when the operation is failed. - measurement-id: Identify an RPC for one measurement. - received-power-measurement: This list indicates the List of RSSI measurements. If O-RU controller uses "rpc received-power-measurement-request" to request measurement report, then O-RU performs and reports received power measurements over the requested-spectrum band in segments of measurement- bandwidth per measurement report. O-RU sends RPC response where status= SUCCEED or FAILED. O-RU performs measurement and delivers result to O-RU controller. O-RU sends error-message when status = FAILED and with appropriate failure reason. For CBRS, O-RU performs the received power measurement in segments with 5 or 10MHz measurement bandwidth per measurement report. The range bounded by measurement-start-frequency as the lower bound and measurement-start- frequency+ measurement-bandwidth as the upper bound expresses the frequency range used in making the measurement. Measurement bandwidth is fixed during each measurement. The possible expression range of the measurement parameter for CBRS is -100 dBm... -25 dBm. When the measurement result in O-RU is out of the range: • O-RU should report -100 dBm when result is lower than -100 dBm. • O-RU should report -25 dBm when result is higher than -25 dBm. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 250 Annex A (normative): Common alarm definition A.1 Introduction This clause contains common alarms which may be supported. Alarms that are not applicable in given HW design or SW configuration shall not be reported. For example, alarms related to fan monitoring are applicable to HW variants with fans. In many cases fault detection method is HW specific. It is assumed that fault detection method is reliable to avoid undetected alarms and false alarms. It is also expected that the NETCONF Server is applying mechanisms to avoid unreasonably fast toggling of alarms' state, for example use time filtering. The field that are mandatory for alarm-notif notifications are: • fault-id; • fault-source; • fault-severity; • is-cleared; and • event-time. The common alarms table has following columns: NOTE 1: The table columns do not represent the entire set of alarm fields defined in the o-ran-fm.yang model. Fault id - Numerical identifier of fault type of the alarm. This ID shall be used in <alarm-notif> message (fault-id parameter). Fault Name - Name of the fault. It may be used in the alarm-notif notification. Meaning - Description of alarm, describes high level meaning of the alarm. This field is informative. Start condition - Defines conditions that O-RU shall follow for raising the alarm. If specific filtering time is needed, then it shall be defined in this column. Cancel condition - Defines conditions that O-RU shall follow for ceasing the alarm. If specific filtering time is needed, then it shall be defined in this column. NETCONF Server actions on fault detection - Defines actions of the NETCONF Server when fault has been detected. This field is informative. Word 'None' in this field means no action is expected. NETCONF Server actions on fault recovery - Defines actions of NETCONF Server after fault detection determines the fault is recovered. This field is informative. Word 'None' in this field means no action is expected. NETCONF Client recovery actions - Describes gNB level recovery actions of the NETCONF Client after alarm has been indicated by NETCONF Server. This field is informative only; actions taken by the NETCONF Client are not restricted nor defined in the present document. NETCONF Client recovery action "Reset" refers to NETCONF Client forcing reset of O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 251 Source - Defines possible sources of the alarm (fault is localized to this source within O-RU). Alarm sources may directly reference a defined component or may use a predefined textual description. If the fault source can be represented by an object in the model, then the YANG instance-identifier should be set as the value. XML format can also be used. The following list provides examples of mapping between fault sources and XML encodings, describing the names of components that may be alarm sources: Module (hardware component is O-RAN-RADIO): < hardware xmlns= "urn:o- ran:hardware:1.0"><component><o-ran-name/></component></hardware> Fan supervision: <fan-tray xmlns= "urn:o-ran:fan:1.0"><fan-state><name/></fan-state></fan- tray> GNSS: <sync xmlns= "urn:o-ran:sync:1.0"><gnss-status><name/></gnss-status></sync> External input: <external-io xmlns= "urn:o- ran:externalio:1.0"><input><name/></input></external-io> External output: <external-io xmlns= "urn:o- ran:externalio:1.0"><output><name/></output></external-io> ALD port: <ald-ports-io xmlns= "urn:o-ran:ald-port:1.0"><ald-port><name/></ald-port></ald- ports-io> Port transceiver: <port-transceivers xmlns= "urn:o-ran:transceiver:1.0"><port-transceiver- data><name/></ port-transceiver-data ></port-transceivers> Ethernet interface: <interfaces xmlns= "urn:ietf:params:xml:ns:yang:ietf- interfaces"><interface><name/></interface></interfaces> Processing element: <processing-elements xmlns= "urn:o-ran:processing-element.1.0"><ru- elements><name/></ru-elements></processing-elements> Low level tx link: <o-ran-uplane-conf xmlns= "urn:o-ran:uplane-conf.1.0"><low-level-tx- links><name/></low-level-tx-links></ o-ran-uplane-conf> Low level rx link: <o-ran-uplane-conf xmlns= "urn:o-ran:uplane-conf.1.0"><low-level-rx- links><name/></low-level-rx-links></o-ran-uplane-conf> Tx-array: <o-ran-uplane-conf xmlns= "urn:o-ran:uplane-conf.1.0"><tx-arrays><name/></tx- arrays></o-ran-uplane-conf> Rx-array: <o-ran-uplane-conf xmlns= "urn:o-ran:uplane-conf.1.0"><rx-arrays><name/></rx- arrays></o-ran-uplane-conf> Tx-array carrier: <o-ran-uplane-conf xmlns= "urn:o-ran:uplane-conf.1.0"><tx-array- carriers><name/></tx-array-carriers></o-ran-uplane-conf> O-DU supervision: <o-ran-supervision xmlns= "urn:o-ran:supervision:1.0"><per-odu- monitoring><odu-id/></per-odu-monitoring></o-ran-supervision> Connector (hardware component derived from "O-RU-CONNECTOR"): <hardware xmlns= "urn:ietf:params:xml:ns:yang:ietf-hardware"><component><name/></component></hardware> Component (hardware component): <hardware xmlns= "urn:ietf:params:xml:ns:yang:ietf- hardware"><component><name/></component></hardware> The following list provides mapping between fault sources and predefined textual descriptions used to define the fault sources: • Antenna line: array's name:array element, where array's name follows either tx-array or rx-array name as defined above and array element is an ordinal number defining element within an array (see k in clause 12.5.3 Identification and Ordering of Array Elements in [2]). EXAMPLE 1: "tx-array-1:0" (alarm on the array element k=0 on the tx-array named "tx-array-1"). ETSI ETSI TS 104 023 V17.1.0 (2026-01) 252 EXAMPLE 2: "rx-array-2:15" (alarm on the array element k=15 on the rx-array named "rx-array-2"). • Tx-array carrier per antenna line: array carrier's name/array's name:array element, where array carrier's name follows tx-array carrier name as defined above, and array's name follows tx-array name as defined above and array element is an ordinal number defining element within an array (see k in clause 12.5.3 Identification and Ordering of Array Elements in [2]). EXAMPLE 1: "tx-array-carrier-1/tx-array-1:0" (alarm of tx-array-carrier named "tx-array-carrier-1" on the array element k=0 on tx-array named "tx-array-1"). EXAMPLE 2: "tx-array-carrier-3/tx-array-2:15 " (alarm of tx-array-carrier named "tx-array-carrier-3" on the array element k=15 on tx-array named "tx-array-2"). If an alarm is caused by an external device (fault localized external to the O-RU, e.g. caused by an Antenna Line Device), then fault source may not fit to any of the fault sources described above and additional text in an alarm notification is needed to clearly describe what may be a possible fault source. NOTE 2: Alarms, especially those defined in vendor specific range, may use other fault sources, which are not described above. Severity - Defines severity of the alarm as specified in Recommendation ITU-T X.733 [30]. - Critical - sub-unit for which alarm has been generated is not working and cannot be used. - Major - sub-unit for which alarm has been generated is degraded, it can be used but performance might be degraded. - Minor - sub-unit for which alarm has been generated is still working. Alarm Type - Indicates the type of alarm, as specified in ETSI TS 128 532 [60], Table 12.2.1.4.4.6-1. - The table of alarms in Annex A includes alarm-type values for the common alarms. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 253 Table A.1-1: Common O-RU Alarms Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 1 Unit temperature is high Unit temperature is higher than expected. Unit temperature exceeded HW implementation specific values. Unit temperature is below HW implementation specific values. SW implementation specific. None. None. Module Minor (e.g. above threshold1) or Major (e.g. above threshold2) ENVIRONME NTAL-ALARM 2 Unit dangerously overheating Unit temperature is dangerously high. Unit temperature exceeded HW implementation specific value for reasonably long filtering time (e.g. 1 minute). Unit temperature is below HW implementation specific value for reasonably long filtering time (e.g. 1 minute). AND Ambient temperature is below predefined HW implementation specific value. Unit deactivates all carriers to prevent HW damage. None. None. Module Critical ENVIRONME NTAL-ALARM 3 Ambient temperature violation Calculated ambient temperature value goes outside the allowed ambient temperature range. Calculated ambient temperature goes outside the allowed HW specific ambient temperature range. Calculated ambient temperature not any more outside the allowed HW specific ambient temperature range. SW implementation specific. None. None. Module Minor ENVIRONME NTAL-ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 254 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 4 Temperature too low During start-up: The temperature inside the unit is too low. Heating of unit is ongoing. Wait until the alarm is cancelled. During runtime: The temperature inside the module is too low. Unit temperature is below HW implementation specific value. Unit temperature is x Celsius above HW implementation specific value. Additionally: cancellation of critical alarm (reported during start-up) is mandatory within x minutes. HW implementation specific (e.g. enable heating) (note 1). HW implementation specific (e.g. disable the heating) (note 2). None. Module Critical during start-up Minor during runtime ENVIRONME NTAL-ALARM 5 Cooling fan broken Fan(s) do not run. HW implementation specific. HW implementation specific. None. None. None. Fan supervision Critical (if cooling is severely degraded) Major (otherwise) EQUIPMENT- ALARM 6 No fan detected Unit cannot identify the used fan type or the fan is not installed at all. HW implementation specific. HW implementation specific. SW implementation specific. None. None. Fan supervision Minor EQUIPMENT- ALARM 7 Tuning failure A filter has not been able to tune on an appropriate sub-band properly. HW implementation specific. HW implementation specific. None. None. None. Antenna line Critical EQUIPMENT- ALARM 8 Filter unit faulty Major failure has been detected by the filter. HW implementation specific. HW implementation specific. None. None. None. Antenna line Critical EQUIPMENT- ALARM 9 Transmission quality deteriorated The TX signal quality may be out of specification limits. HW and SW implementation specific. HW and SW implementation specific. None. None. None. Antenna line Major QUALITY-OF- SERVICE- ALARM 10 RF Module overvoltage protection faulty Module's overvoltage protection is broken. HW implementation specific. None. None. None. None. Module Minor EQUIPMENT- ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 255 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 11 Configuring failed Configuration failed because of a HW or SW fault. SW or HW fault detected during configuration. None. None. None. Reset. Module Critical PROCESSIN G-ERROR- ALARM 12 Critical file not found Critical configuration file is missing. Critical configuration file is detected missing. None. None. None. Reset. Module Critical PROCESSIN G-ERROR- ALARM 13 File not found Non-critical configuration file is missing. Non-critical configuration file is detected missing. None. None. None. None. Module Major PROCESSIN G-ERROR- ALARM 14 Configuration file corrupted conflicting or corrupted configuration data. conflicting or corrupted configuration data detected. Unit detects that previously missing file is present. None. None. None. Module or antenna line Major PROCESSIN G-ERROR- ALARM 15 Unit out of order The Unit is out of order because of a software or hardware fault. HW and SW implementation specific. HW and SW implementation specific. None. None. Reset. Module Critical EQUIPMENT- ALARM 16 Unit unidentified The permanent memory in the module is corrupted and the module product code or serial number is missing, or the module product code is unknown. Not able to read data from information storage or data is such that module identity or serial number is missing or module identity is unknown. None. None. None. None. Module Major PROCESSIN G-ERROR- ALARM 17 No external sync source The Unit lost lock to all incoming clocks. HW implementation specific. HW implementation specific. None. None. Reset or none. Module Major EQUIPMENT- ALARM 18 Synchronizati on Error Unit is out of synchronization. HW implementation specific (note 6). HW implementation specific. Unit shuts down all RF emission to prevent environment distortion and deactivates all carriers. None. Reset or none. Module Critical EQUIPMENT- ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 256 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 19 TX out of order TX path is not usable. HW implementation specific. HW implementation specific. None. None. Reset or none. Antenna line Critical EQUIPMENT- ALARM 20 RX out of order RX path is not usable. HW implementation specific. None. None. None. Reset or none. Antenna line Critical EQUIPMENT- ALARM 21 Increased BER detected on the optical connection Increased bit error rate has been detected on the optical link which results in sporadic errors in downlink baseband processing. HW implementation specific (the detected BER on optical link is degrading RF operation). HW implementation specific (the detected BER on optical link is not degrading RF operation). Module Agent starts HW implementation specific recovery to keep the RF operation ongoing. Module Agent stops HW implementation specific recovery actions. None. Module Major QUALITY-OF- SERVICE- ALARM 22 Post-test failed Power-on self test failed at start-up. HW and SW implementation specific. None. Unit reset x times for recovery. None. None. Module Critical PROCESSIN G-ERROR- ALARM 23 FPGA SW update failed The FPGA software update has failed. FPGA SW checksum is not correct match after FPGA SW update is detected. None. None. None. None. Module Major PROCESSIN G-ERROR- ALARM 24 (note 3) Unit blocked Unit is administratively locked. Parameter admin-state of the Module element is set to "locked". Parameter admin-state of the Module Element is set to "unlocked" or "shutting- down". Refer to clause 9.1.3 for description. None. None. Module Critical EQUIPMENT- ALARM 25 Reset Requested Unit detected a transient problem which significantly affects operation that requires a reset as a recovery. HW implementation specific. None. None. None. Reset. Module Critical EQUIPMENT- ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 257 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 26 Power Supply Faulty Input power to module has fault, unstable or broken. HW implementation specific. None. None. None. Reset or None. Module Minor, Major or Critical EQUIPMENT- ALARM 27 Power Amplifier faulty One or more power amplifiers in module has fault, unstable or broken. HW implementation specific. None. None. None. Reset or None. Tx-array and/or antenna line Major (Performance of tx-array and/or antenna line is degraded because of power amplifier issue) Or Critical (tx- array and/or antenna line is not working because of power amplifier issue) EQUIPMENT- ALARM 28 C/U-plane logical Connection faulty One of logical C/U-plane connection has fault, unstable or broken. One of C/U- plane processing elements detects the error of C/U- plane connection faulty, (when the O-RU's CU plane monitoring timer expires). C/U Plane connection recovered, or the carrier related fault source deactivated/ removed. None. None. None or reset. processing- element Major COMMUNICA TIONS- ALARM 29 Transceiver Fault Unit has detected a transceiver fault HW and SW implementation specific. None. None None. None. Module or port transceiver. Critical EQUIPMENT- ALARM 30 Interface Fault Unit has detected a fault with one of its interfaces. HW and SW implementation specific. None. Unit reset x times for recovery. None. None. Module Major or Critical EQUIPMENT- ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 258 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 31 Unexpected C/U-plane message content fault C/U-plane message content was faulty for undetermined reason. C/U-plane detects unexpected message content. Carrier that uses the fault source is disabled/ removed. SW implementation specific. None. None. Specific to low-level- [tr]x- endpoint in the C/U- Plane message Major, Minor or Warning COMMUNICA TIONS- ALARM 32 Triggering failure of antenna calibration O-RU has previously sent a notification antenna- calibration- required and has not received an antenna- calibration-start RPC. Major - O-RU has not received an RPC trigger for start antenna calibration within 60 seconds after triggering the sending of the antenna- calibration- required notification Critical - After O-RU specific number of repetitions based on O-RU implementation/ Failure of O-RU self-calibration. Arrival of RPC antenna calibration start/Success of O-RU self- calibration. Major-None, Critical-Reset or None. Major-None, Critical-None. Major -Send RPC antenna calibration start/self- calibration Critical- Reset. Module Major/ Critical PROCESSIN G-ERROR- ALARM 33 Dying Gasp O-RU is suffering from an unrecoverable condition such as power failure. Critical - O-RU is experiencing a dying gasp event. Re-starting of the O-RU, e.g. after power has been restored. HW implementation specific. None. None. Module Critical EQUIPMENT- ALARM 34 Clock source failure Clock source has failed. O-RU detects clock source failure. HW implementation specific. set the system clock to the current time recovered from available external sources. None. None. Module Critical EQUIPMENT- ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 259 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 35 Lost O-DU ID based Supervision An O-RU has lost supervision from one O-DU (note 4). Major - carriers associated with the O-DU are disabled. Re- establishment of NETCONF supervision by O-DU (note 5). Disable operation of carrier resources associated with O-DU. None. None. odu-id Major COMMUNICA TIONS- ALARM 36 Rx Signal quality deteriorated The RX signal quality may be out of specification limits. HW and SW implementation specific. HW and SW implementation specific. None. None. None. Antenna line Major QUALITY-OF- SERVICE- ALARM 37 High IQ Power The IQ Power level is higher than alarm threshold. Major - O-RU detects IQ- Power value exceeding HW implementation specific limit. Critical - O-RU detects IQ- Power value exceeding HW implementation specific limit which can cause HW a failure. tx-array-carrier is deactivated or IQ-Power value falls below threshold. implementation specific. None. None. Tx-array- carrier per antenna line Major Critical COMMUNICA TIONS- ALARM ETSI ETSI TS 104 023 V17.1.0 (2026-01) 260 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 38 (note 7) VSWR high VSWR has exceeded threshold limits. VSWR is higher than expected. VSWR is below the specific value. Implementation specific. None. None. Antenna line or Connector Minor (VSWR exceeds default or configured minor threshold) Major (VSWR exceeds default or configured major threshold) EQUIPMENT- ALARM 39 Certificate About to Expire The X.509 certificate used by O-RU for M plane is about to expire. minor-alarm- advance-time days prior to expiry for Minor alarm. When Major alarm is raised or when fault ID 40 is raised or when certificate is re-issued and certificate-lcm event generated. Follow the procedure specified in clause 6.2.6.4.3 depending on the cert-lcm- policy configured. After the certificate is re- issued, expect closure of existing NETCONF session from NETCONF controller. NETCONF client shall follow the process defined in clause 6.2.6.4.3 if the configured cert-lcm- policy is REISSUE_ ON_DEMA ND. Module Minor SECURITY- SERVICE- OR- MECHANISM -VIOLATION major-alarm- advance-time days prior to expiry for Major alarm. When Critical alarm is raised or when fault ID 40 is raised or when certificate is re-issued and certificate-lcm event generated. Major critical-alarm- advance-time days prior to expiry for Critical alarm. When fault ID 40 is raised or when certificate is re-issued and certificate-lcm event generated. Critical ETSI ETSI TS 104 023 V17.1.0 (2026-01) 261 Fault id Fault Name Meaning Start condition Cancel condition NETCONF Server actions on fault detection NETCONF Server actions on fault recovery NETCONF Client recovery actions Source Severity Alarm Type 40 Certificate Expired The X.509 certificate used by O-RU for M plane has expired. The X.509 certificate used by O-RU for M plane has expired. When certificate is re- issued and certificate-lcm event generated. None None. NETCONF client shall follow the process defined in clause 6.2.6. Module Critical SECURITY- SERVICE- OR- MECHANISM -VIOLATION 41 (note 8) Generic Hardware Failure Unit has detected a fault with one or more of its hardware (modules). HW and SW implementation specific HW and SW implementation specific. HW and SW implementation specific. Reset or None. Reset or None. Module or Component (note 9) Critical, Major or Minor EQUIPMENT- ALARM NOTE 1: Actions taken shall not interfere with normal unit operation if such is commanded by NETCONF Client. NOTE 2: Actions taken shall not interfere with normal unit operation if such is commanded by NETCONF Client. NOTE 3: The admin-state is conditioned on the optional hardware-state feature. The O-RU can support fault id #24 (Unit blocked) only if it supports optional feature hardware-state. NOTE 4: This alarm is only supported by O-RUs that implement the SHARED-ORU-MULTI-ODU feature. This alarm works per supervision session, meaning the O-RU is expected to report this alarm separately for each lost supervision session. NOTE 5: Cancellation of this alarm is per each recovered supervision session. NOTE 6: NETCONF Server shall not report fault id #18 during the initial synchronization establishment which happens as part of normal start-up procedure as described in clause 6.1 step 8, i.e. O-RU implementations are designed to prevent false alarms during normal start-up. NOTE 7: VSWR measurements are only valid when transmitted power exceeds a specific value which is either configured by O-RU Controller or predefined by O-RU. NOTE 8: Specifically defined alarms should be used first, and this alarm should be applied only for undefined hardware failure cases. NOTE 9: Source module shall be reported unless a more specific hardware component is reported in the component list. More detailed information may be included in the additional-information list. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 262 Annex B (normative): Counters B.1 Counter definition Table B.1-1: Counters definition measurement- group measurement-object report-info object-unit Note transceiver-stats RX_POWER MAXIMUM MINIMUM FIRST LATEST FREQUENCY_T ABLE PORT_NUMBER Type decimal64 including 4 fraction-digits for max, min, first and latest. A parameter date-and-time is reported for each additionally. Configurable parameters: function, bin-count, lower- bound, upper-bound are defined. For more detail see clause B.1.3. Type uint32 is used for frequency-bin-table. RX_POWER_LANE_2 RX_POWER_LANE_3 RX_POWER_LANE_4 TX_POWER TX_POWER_LANE_2 TX_POWER_LANE_3 TX_POWER_LANE_4 TX_BIAS_COUNT TX_BIAS_COUNT_LANE _2 TX_BIAS_COUNT_LANE _3 TX_BIAS_COUNT_LANE _4 VOLTAGE TEMPERATURE LASER_TEMPERATURE TEC_CURRENT rx-window-stats RX_ON_TIME COUNT RU, TRANSPORT, or EAXC_ID Type yang: counter64 is used for the count. When object-unit is EAXC_ID, TRANSPORT is reported as additional parameter for EAXC_ID. RX_EARLY RX_LATE RX_CORRUPT RX_DUPL RX_TOTAL RX_ON_TIME_C RX_EARLY_C RX_LATE_C RX_SEQID_ERR RX_SEQID_ERR_C RX_ERR_DROP tx-measurement- objects TX_TOTAL COUNT RU, TRANSPORT, or EAXC_ID Type yang: counter64 is used for the count. When object-unit is EAXC_ID, TRANSPORT is reported as additional parameter for EAXC_ID. TX_TOTAL_C ETSI ETSI TS 104 023 V17.1.0 (2026-01) 263 measurement- group measurement-object report-info object-unit Note epe-statistics POWER MAXIMUM MINIMUM AVERAGE FREQUENCY_T ABLE Hardware component type, e.g. O-RAN-RADIO, O-RU-POWER- AMPLIFIER, O-RU-FPGA, power-supply, fan, cpu Type decimal64 including 4 fraction-digits for max, min, average. Power measured using method specified in clause 5.1.1.19 of ETSI TS 128 552 [57] Unit of power: watts (W) Temperature measured using method specified in clause 5.1.1.19 of ETSI TS 128 552 [57] Unit of temperature: Celsius Voltage measured using method as specified in clause 5.1.1.19 of ETSI TS 128 552 [57] Unit of voltage: Volts Current measured using method specified in clause 5.1.1.19 of ETSI TS 128 552 [57] Unit of current: Amperes TEMPERATURE VOLTAGE CURRENT symbol-rssi-stats- object ALL-UL-SYMBOLS MAXIMUM MINIMUM AVERAGE FREQUENCY- TABLE rx-array-carrier Type decimal64 including 1 fraction-digit is used for max, min and avg. Type uint32 is used for frequency-bin-table. CONFIGURED- SYMBOLS shared-cell-stats RX_UP_UL COUNT TRANSPORT Type yang: counter64 is used for the count. RX_UP_UL_COMBINED tx-antenna-stats VSWR AVERAGE STD_DEVIATIO N MAXIMUM MAXIMUM_AND _TIME MINIMUM MINIMUM_AND_ TIME FIRST FIRST_AND_TIM E LATEST LATEST_AND_TI ME FREQUENCY_T ABLE ARRAY_ELEMEN T or CONNECTOR_BA ND Type decimal64 including 4 fraction-digits for max, min, first, latest, avg and std- deviation. A parameter date- and-time is reported for max, min, first and latest additionally if MAXIMUM_AND_TIME, MINIMUM_AND_TIME, FIRST_AND_TIME or LATEST_AND_TIME report-info was selected. Configurable parameters: bin-count, lower-bound, upper-bound are defined. tssi-stats-object TSSI-IQ-POWER-LEVEL MAXIMUM MINIMUM AVERAGE carrier_array_elem ent Type decimal64 including 2 fraction-digits is used for iq-tssi-level. rssi-stats-object RSSI MAXIMUM MINIMUM AVERAGE carrier_array_elem ent Type decimal64 including 1fraction-digit is used for rssi. tx-output-power- stats TX_OUTPUT_POWER MAXIMUM MINIMUM AVERAGE TX-ARRAY- CARRIER, TX-ARRAY- ELEMENT, CONNECTOR, CARRIER-ARRAY- ELEMENT or ARRAY-CARRIER- CONNECTOR Type decimal64 including 2 fraction-digit is used for max, min and avg. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 264 measurement- group measurement-object report-info object-unit Note Ethernet-stats IN-OCTETS COUNT Ethernet interface name Type yang: unit64 is used for the count. IN-UNICAST-PKTS IN-BROADCAST-PKTS IN-MULTICAST-PKTS IN-DISCARDS IN-ERRORS IN-UNKNOWN-PROTOS IN-CRC-ERRORS IN-FEC-CORRECTABLE- BLOCKS IN-FEC- UNCORRECTABLE- BLOCKS IN-PCS-STATUS- CHANGE-COUNT OUT-OCTETS OUT-UNICAST-PKTS OUT-BROADCAST-PKTS OUT-MULTICAST-PKTS OUT-DISCARDS OUT-ERRORS A parameter: measurement-interval is defined per group of measurement-objects. A parameter: active is defined per measurement-object. The object-unit for the measurement-object of rx-window-measurement can be selected per RU, per TRANSPORT, or EAXC_ID. RU is assumed to support one of the object-units for the rx-window-measurement. The object-unit for the measurement-object of shared-cell-measurement is per TRANSPORT. Clause 10.3.2 indicates how multiple object-unit-ids can be used for the shared-cell-measurement. TRANSPORT indicates the name of transport-flow in o-ran-processing-element YANG. The type Uint16 is used for EAXC_ID. Measurement result shall contain additional information name for its transport-flow when EAXC_ID is selected for the object-unit. A feature "GRANULARITY-EAXC-ID-MEASUREMENT" and a feature "GRANULARITY-TRANSPORT- MEASUREMENT" are defined as optional definition in O-RU. B.2 Transceiver statistics B.2.1 Transceiver measurements The transceiver-measurement includes the performance measurement of transceivers as shown in Table B.2.1-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 265 Table B.2.1-1: Transceiver Measurements measurement-object Description RX_POWER Measured Rx input power in mW for SFP or lane 1 of QSFP. RX_POWER_LANE_2 Measured Rx input power in mW for lane 2 of QSFP. RX_POWER_LANE_3 Measured Rx input power in mW for lane 3 of QSFP. RX_POWER_LANE_4 Measured Rx input power in mW for lane 4 of QSFP. TX_POWER Measured Tx input power in mW for SFP or lane 1 of QSFP. TX_POWER_LANE_2 Measured Tx input power in mW for lane 2 of QSFP. TX_POWER_LANE_3 Measured Tx input power in mW for lane 3 of QSFP. TX_POWER_LANE_4 Measured Tx input power in mW for lane 4 of QSFP. TX_BIAS_COUNT Internally measured Tx Bias Current in mA for SFP or lane 1 of QSFP. TX_BIAS_COUNT_LANE_2 Internally measured Tx Bias Current in mA for lane 2 of QSFP. TX_BIAS_COUNT_LANE_3 Internally measured Tx Bias Current in mA for lane 3 of QSFP. TX_BIAS_COUNT_LANE_4 Internally measured Tx Bias Current in mA for lane 4 of QSFP. VOLTAGE Internally measured transceiver supply voltage in mV. TEMPERATURE Internally measured optional module temperature in degrees Celsius. LASER_TEMPERATURE Internally measured optional laser temperature in degrees Celsius. TEC_CURRENT Internally measured transceiver module TEC current in mA. B.2.2 Statistics calculation When configured by the NETCONF client, the O-RU captures value of monitored parameters. Then the O-RU calculates x = f(s), where f(s) is a function selected for specific statistics instance. The function f(s) can be one of the following: f(s) = s f(s) = LOG10(s), where LOG10(s) is logarithm with base 10. To avoid issues with infinity, the O-RU assumes that for s < 10-128 value of LOG10(s) is -128. The value of x = f(s) is applied to first, latest, min and max values; related timestamps are also updated; frequency table is updated as described in clause B.2.3. When local measurement interval, which is not same as transceiver-measurement-interval of the measurement- object, passes the O-RU captures value of a monitored parameter (s). Then the O-RU calculates x = f(s), where f is a function selected for specific parameter. The local measurement interval is up to the O-RU implementation matter and typically around 10 sec - 60 sec at earliest. The value of x = f(s) is applied to latest value; related timestamp is updated. The O-RU updates statistics: • If x < min value then x is applied to min value and related timestamp is updated. • If x > max value then x is applied to max value and related timestamp is updated. • Value of x is used to update frequency table as described in clause B.2.3 below. After updates O-RU waits another interval to elapse. B.2.3 Frequency table generation Let n = bin-count, a = lower-bound, b = upper-bound, x = f(s) where s is value of monitored parameter and f is a function selected for statistics via parameter function. • If n = 0 then frequency table is empty and is not updated. • If n > 0 there are n bins: hk where k = 0...n-1. Initial value of each bin is zero (hk = 0 for k = 0...n-1). ETSI ETSI TS 104 023 V17.1.0 (2026-01) 266 • If x < a then bin h0 is incremented. • If b ≤ x and n > 1 then bin hn-1 is incremented. • If a ≤ x and x < b and n > 2 then bin hk is incremented for k such that: - k-1 ≤ (n-2) * (x-a) / (b-a) < k. where the value of a bin should saturate at maximum without overflowing (the value is not incremented above 232-1). Equivalently: • For k = 0, hk is a number of values x such that x < a. • For k = 1 ... n-2, hk is a number of values x such that: - a + (b-a) * (k-1) / (n-2) ≤ x < a + (b-a) * (k) / (n-2). • For k = n-1, hk is a number of values x such that b ≤ x. EXAMPLE: function = LOG10, bin-count = 14, lower-bound = -12, upper-bound = 0 • parameter value s = 0, x = f(0) = -128, -128 < -12 = a h0 is incremented • parameter value s = 1e-12, x = f(1e-12) = -12, (14 - 2) * (-12 - (-12)) / (0 - (-12)) = 12 * 0 / 12 < 1 h1 is incremented • parameter value s = 9,99e-12, x = f(9.99e-12) = -11,0004, (14 - 2) * (-11,0004 - (-12)) / (0 - (-12)) = 12*0,9996 / 12 < 1 h1 is incremented • parameter value s = 1e-1, x = f(1e-1) = -1, (14 - 2) * (-1 - (-12)) / (0 - (-12)) = 12 * 11 / 12 < 12 h12 is incremented • parameter value s = 1, x = f(1) = 0, 0 ≥ 0 = b h13 is incremented B.3 Rx window statistics B.3.1 Rx window measurement The rx-window-measurement includes the performance measurement for the reception window according to Table B.3-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 267 Table B.3-1: Rx Window Measurement measurement-object Description RX_ON_TIME The number of data packet received on time (applies to user data reception window) within the rx-window-measurement-interval RX_EARLY The number of data packet received too early (applies to user data reception window) within the rx-window-measurement-interval RX_LATE The number of data packet received too late (applies to user data reception window) within the rx-window-measurement-interval RX_CORRUPT The number of data packet, which is corrupt or whose header is incorrect, received within the rx-window-measurement-interval RX_DUPL This counter is deprecated RX_TOTAL The total number of received packet (data and control), within the rx-window-measurement-interval RX_ON_TIME_C The number of control packets, received on time within the rx-window-measurement-interval RX_EARLY_C The number of control packets, received before the start of reception window within the rx-window-measurement-interval RX_LATE_C The number of control packets, received after the end of reception window within the rx-window-measurement-interval RX_SEQID_ERR The number of data packets, received with an erroneous sequence ID within the rx-window-measurement-interval RX_SEQID_ERR_C The number of control packets, received with an erroneous sequence ID within the rx-window-measurement-interval RX_ERR_DROP The total number of inbound messages which are discarded by the receiving O-RAN entity for any reason within the rx-window- measurement-interval B.4 Tx statistics The tx-measurements include the measurement according to Table B.4-1. Table B.4-1: Tx Measurement measurement-object Description TX_TOTAL The number of outbound packets (data and control), transmitted within the tx-measurement-interval TX_TOTAL_C the number of outbound control packets, transmitted within the tx- measurement-interval (This counter is required only if RU supports LAA/LBT capabilities) B.5 Energy, power and environmental statistics The epe-stats include the performance measurement for energy, power and environmental parameters as shown in Table B.5-1. An O-RU shall report its supported measurement objects per hardware component class. Table B.5-1: Energy, Power and Environmental Measurements measurement-object Description POWER Value of measured power consumed by identified hardware component TEMPERATURE Value of measured temperature of identified hardware component VOLTAGE Value of measured voltage of identified hardware component CURRENT Value of measured current of identified hardware component ETSI ETSI TS 104 023 V17.1.0 (2026-01) 268 B.6 Symbol RSSI statistics B.6.1 Statistics calculation The symbol-rssi-stats is the time domain RSSI per symbol, the reference point for the TD-RSSI shall be the antenna connector of the O-RU. The value of Received Signal Strength Indicator(RSSI) per rx-array-carrier per configured OFDM symbol is measured. The RSSI shall be calculated as the linear average of the total received power observed in the configured OFDM symbol in the measurement bandwidth from all sources including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. over the total number of array elements of the array. The unit of the reported RSSI is dBm. If analogue or hybrid beamforming is enabled, the beamId used for RSSI measurement is: • When there is allocation of a beamId in this symbol, O-RU use that beamId for RSSI measurement. • When there is no allocation of a beamId in this symbol, it is up to O-RU implementation, for example, the O-RU can choose to use a common beamId or use a previous allocated beamId. Table B.6.1-1: Symbol RSSI Measurements measurement-object Description ALL-UL-SYMBOLS Measure and report symbol-rssi separately for all UL symbols in every configured number of slots (as defined by 'period' in 'symbol- rssi-measurement-objects'. And the UL symbols are decided by 'configurable-tdd-pattern', 'static-srs-configuration', 'static-prach- configuration', and 'dataDirection' in the C-plane messages. This option is recommended for static TDD case. If this option is used in dynamic TDD case, then O-RU measures only the allocates UL symbols because O-RU may not know 'candidate UL symbols' which are not allocated. CONFIGURED- SYMBOLS Measure and report symbol-rssi separately for all configured symbols as defined by the leaf-list 'symbol-index'. This can be used for non-dynamic TDD as well as dynamic TDD cases, the O-RU should measure all configured symbols, irrespective of whether the UL symbol is allocated or not. If a c-plane message indicates a symbol within the 'symbol-index' list to be a DL symbol, O-RU shall not measure rssi on this symbol. B.6.2 Frequency Table Generation Same as clause B.2.2. B.7 Shared cell statistics The shared cell measurements include the measurement according to Table B.7-1. Table B.7-1: Shared-cell Measurement measurement-object Description RX_UP_UL The number of received user plane packet in UL data direction corresponding to shared-cell-combine-entities within the sharedcell-measurement-interval RX_UP_UL_COMBINED The number of user plane packet in UL data direction which are processed by combine functional block within the shared-cell- measurement-interval ETSI ETSI TS 104 023 V17.1.0 (2026-01) 269 B.8 Tx antenna statistics B.8.1 Introduction The tx-measurements include the measurement according to Table B.8-1. Table B.8-1: Tx Measurement measurement-object Description VSWR The estimated value of Voltage Standing Wave Ratio (VSWR) for tx-array element, or connector and band. In case the value cannot be provided, the value of 0 is used. VSWR related measurements and counters are useful for monitoring and troubleshooting of radios with external antennas. B.8.2 Statistics calculation Statistics are calculated as defined in clause B.2.2, with the exception that the only permitted function is f(s) = s and parameter function is not used. B.8.3 Frequency Table Generation Frequency table is generated as defined in clause B.2.3, with the exception that the only permitted function is f(s) = s and parameter function is not used. B.9 TSSI statistics B.9.1 Statistics calculation The tssi-stats is transmit signal power as digital IQ level from baseband per tx-array-carrier on the specific tx-array- element in tx-array. When digital beamforming is used, TSSI shall indicate the signal power in digital domain after digital beamforming. The average TSSI-IQ-POWER-LEVEL shall be calculated as averaged value with the data (N samples of the DL symbols) in specific time duration. The unit of the tx-tssi-stats is dBFS. Table B.9.1-1: Tx TSSI Measurements measurement-object Description TSSI-IQ-POWER- LEVEL Measured digital IQ power level for a specific tx-array carrier on the specific tx-array-element in tx-array. B.10 RSSI statistics B.10.1 Statistics calculation The rssi-stats is the time domain RSSI per rx-array-carrier on the specific rx-array-element in rx-array. When digital beamforming is used, RSSI shall indicate the signal power in digital domain before digital beamforming. Based on the O-RU measured IQ power, the RSSI power is provided as dBm. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 270 NOTE: The present document does not define RSSI measurements when the O-RU supports analogue beamforming. Table B.10.1-1: Rx RSSI Measurements measurement-object Description RSSI Measured RSSI (Received Signal Strength Indication) for each rx-array carrier on the specific array element in decibel- milliwatts (dBm) B.11 Tx output power statistics B.11.1 Statistics calculation TX_OUTPUT_POWER is measured or estimated as defined in Table B.11.1-2 for different Object Unit. The unit of the reported Tx output power is dBm Table B.11.1-1: Tx output power Measurements measurement-object Description TX_OUTPUT_POWER Measured or estimated value of conducted transmission power for different Tx output power Object Units (as defined in Table B.11.1-2) in dBm. Table B.11.1-2: Tx output power Object Units Object unit Description TX-ARRAY-CARRIER (note 2) The estimated tx output power per tx-array-carrier. TX-ARRAY-ELEMENT The tx output power per tx-array element. CARRIER-ARRAY- ELEMENT (note 2) The estimated tx output power per tx-array element per tx-array- carrier. CONNECTOR (note 1) The tx output power per connector. ARRAY-CARRIER- CONNECTOR (note 1, note 2) The estimated tx output power per tx-array-carrier per connector. NOTE 1. Tx output power of connector is only applicable with O-RUs that report connector and using external antenna. NOTE 2. The tx output power per measurement object unit is estimated, may be based on power per tx-array element or connector. If multiple tx-array-carriers are configured to the tx-array- element or connector, then the tx output power per measurement object unit may be derived, may be based on the gain of the tx-array-carrier configured via M-plane and tx input IQ power level of each tx-array-carrier on the tx- array element or corresponding connector. B.12 Ethernet statistics The ethernet-measurement includes the performance measurement of ethernet interface monitoring as shown in Table B.12.1-1. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 271 Table B.12.1-1: Ethernet Monitoring Measurements measurement-object Description IN-OCTETS The total number of octets received on the interface, including framing characters. IN-UNICAST-PKTS The number of packets, delivered by this sub-layer to a higher (sub-)layer, that were not addressed to a multicast or broadcast address at this sub-layer. IN-BROADCAST-PKTS The number of packets, delivered by this sub-layer to a higher (sub-)layer, that were addressed to a broadcast address at this sub-layer. IN-MULTICAST-PKTS The number of packets, delivered by this sub-layer to a higher (sub-)layer, that were addressed to a multicast address at this sub-layer. For a MAC-layer protocol, this includes both Group and Functional addresses. IN-DISCARDS The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. IN-ERRORS The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. IN-UNKNOWN-PROTOS The number of packets received via the interface that were discarded because of an unknown or unsupported protocol. IN-CRC-ERRORS The number of received frames with CRC errors. IN-FEC-CORRECTABLE-BLOCKS Number of received erroneous blocks which were corrected with application of Forward Error Correction. IN-FEC-UNCORRECTABLE-BLOCKS Number of received erroneous blocks which could not be corrected with application of Forward Error Correction. IN-PCS-STATUS-CHANGE-COUNT Number of times PCS (Physical Coding Layer) of the receiver lost its operational state. Operational state of PCS is indicated by PCS_status as defined in clause 49 in [88]. OUT-OCTETS The total number of octets transmitted out of the interface, including framing characters. OUT-UNICAST-PKTS The total number of packets that higher-level protocols requested be transmitted and that were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. OUT-BROADCAST-PKTS The total number of packets that higher-level protocols requested be transmitted and that were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. OUT-MULTICAST-PKTS The total number of packets that higher-level protocols requested be transmitted and that were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC-layer protocol, this includes both Group and Functional addresses. OUT-DISCARDS The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. OUT-ERRORS The number of outbound packets that could not be transmitted because of errors. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 272 Annex C (informative): Optional multi-vendor functionality C.1 Optional multi-vendor namespace Some of the YANG models are optional for the O-RU to support. In this version of the management plane specification, the following YANG models are optional to support. If an O-RU/NETCONF server does not return the namespace associated with an optional YANG model, the NETCONF client can infer that the O-RU does not support the optional capability associated with the model. NOTE: Tables C.1-1 and C.1-2 do not apply for factory default software. Table C.1-1: Optional O-RAN Namespace No Optional Functionality Reference Namespace 1 Antenna Line Device Clause 14.4 "urn:o-ran:ald-port:x.y" "urn:o-ran:ald: x.y" 2 External IO Port Clause 14.5 "urn:o-ran:external-io:x.y" 3 eCPRI delay measurement Clause 7.7 "urn:o-ran:message5:x.y" 4 UDP Echo functionality for IP based transport verification Clause 7.6 "urn:o-ran:udpecho:x.y" 5 Beamforming Clause 15.4 "urn:o-ran:beamforming:x.y" 6 FAN - "urn:o-ran:fan:x.y" 7 LAA Clause 16 "urn:o-ran:laa:x.y" "urn:o-ran:laa-operations:x.y" 8 Antenna calibration Clause 15.5 "urn:o-ran:antcal: x.y" 9 Shared cell (common to FHM and Cascade modes) Clause 17 "urn:o-ran:shared-cell:x.y" "urn:o-ran:ethernet-fwd:x.y" 10 Configured subscription transported using VES common header Clause 18 "urn:o-ran:ves-sn:1.0" 11 Certificates to name mapping Clause 6.4.3.2 "urn:o-ran:certificates:1.0" 12 Received power measurements for shared spectrum bands Clause 21 "urn:o-ran:frequency-band- measurement:1.0" Table C.1-2: Optional Non-O-RAN Namespace No Optional Functionality Reference Namespace 1 Notification of Updates to Configuration Datastore Clause 9.4 "urn:ietf:params:xml:ns:yang:ietf- netconf-notifications" 2 Subscribed-Notifications Clauses 9.1.7.3 and 18 "urn:ietf:params:xml:ns:yang:ietf- subscribed-notifications" 3 Certificates to name mapping Clause 6.4.3.2 " urn:ietf:params:xml:ns:yang:ietf- x509-cert-to-name" 4 IEEE 802.1X Port based Access Control Clause 7.12 "urn:ieee:std:802.1X:yang:ieee802- dot1x" "urn:ieee:std:802.1Q:yang:ieee802- types" " urn:ietf:params:xml:ns:yang:iana- crypt-hash" " urn:ietf:params:xml:ns:yang:ietf- system" "urn:ieee:std:802.1X:yang:ieee802- dot1x-types" 5 Trust store Clause 6.2 "urn:ietf:params:xml:ns:yang:ietf- truststore" 6 Continuity Check Message Clause 7.6 "urn:ieee:std:802.1Q:yang:ieee802- dot1q-cfm" 7 O-RU supports configuration of IEEE 802.1X EAPOL destination address Clause 7.12.1 "urn:ieee:std:802.1X:yang:ieee802- dot1x-eapol" ETSI ETSI TS 104 023 V17.1.0 (2026-01) 273 Whereas Tables C.1-1 and C.1-2 describe those optional YANG modules associated with optional features, there are also scenarios where support of an optional feature means that previously defined mandatory YANG models become optional. Table C.1-3 describes those optional features that when supported result in YANG models becoming optional. Table C.1-3: Not mandatory O-RAN Namespace for FHM. No Optional Functionality Reference Namespace 1 FHM in shared cell Clause 17.6.1 "urn:o-ran:module-cap:x.y" "urn:o-ran:uplane-conf:x.y" C.2 Optional YANG features Some of the O-RAN defined YANG models define optional feature support using the ability to tag a portion of the model with a feature name. Theses portions of the model are only valid on O-RUs that indicate they support the specific YANG feature in their YANG library. The definition of the portion of the model tagged with a feature name can include definitions which allow an O-RU Controller to control when a particular O-RU capability associated with a feature tag is activated and/or deactivated. The optional capabilities identified using YANG feature tag names defined in the O-RAN defined YANG models are shown in Table C.2-1 below. Table C.2-1: Optional O-RAN WG4 defined feature support No Namespace YANG Feature Name Tag Description Optional Feature Control 1 "urn:o-ran:ald- port:x.y" OVERCURRENT- SUPPORTED ALD overcurrent reporting Subscription to over-current notifications 2 "urn:o-ran:antcal:1.0" O-RU-COORDINATED- ANT-CAL O-RU needs user traffic to be co-ordinated from O-DU for antenna calibration /antenna-calibration/self- calibration-policy/coordinated- calibration-allowed 3 O-RU-COORDINATED- ANT-CAL-MULTIPLE- TIME-RESOURCE Calibration with multiple timing resource sets /antenna-calibration/self- calibration-policy/coordinated- calibration-multiple-time- resources-allowed 4 "urn:o- ran:beamforming:x.y" MODIFY-BF-CONFIG Dynamic Beamforming Configuration activate-beamforming-config-by- capability-group remote procedure calls 5 BEAM-TILT Tilting pre-defined beams modify-predefined-beam-tilt-offset remote procedure call 6 "urn:o- ran:compression- factors:x.y" CONFIGURABLE-FS- OFFSET Configurable FS offset /user-plane-configuration /low- level-tx-endpoints /compression/fs-offset and/or /user-plane-configuration /low- level-tx-endpoints /compression/dynamic- compression-configuration/fs- offset and/or /user-plane-configuration /low- level-rx-endpoints /compression/fs-offset and/or /user-plane-configuration /low- level-rx-endpoints /compression/dynamic- compression-configuration/fs- offset 7 "urn:o-ran:delay:x.y" ADAPTIVE-RU- PROFILE Adaptive O-RU delay profile /delay-management/adaptive- delay-configuration 8 " urn:o-ran:fm:1.0" HISTORICAL-ALARM- LIST Historical Alarms List M-Plane activation not applicable 9 "urn:o- ran:hardware:x.y" ENERGYSAVING O-RU Energy saving /hardware/component/energy- saving-enabled 10 "urn:o- ran:interfaces:x.y" ALIASMAC-BASED-CU- PLANE Alias MAC address based C/U transport /processing-elements/ru- elements/transport-flow/aliasmac ETSI ETSI TS 104 023 V17.1.0 (2026-01) 274 No Namespace YANG Feature Name Tag Description Optional Feature Control 11 UDPIP-BASED-CU- PLANE UDP/IP based C/U Transport /processing-elements/ru- elements/transport-flow/udpip- flow 12 "urn:o-ran:module- cap:x.y" CONFIGURABLE-TDD- PATTERN- SUPPORTED Configurable TDD pattern /user-plane-configuration/tx-array- carriers/configurable-tdd-pattern and/or /user-plane- configuration/rx-array- carriers/configurable-tdd-pattern 13 DSS_LTE_NR Dynamic Spectrum Sharing /user-plane-configuration/tx-array- carriers/type and/or /user-plane- configuration/rx-array- carriers/type 14 EAXC-ID-GROUP- SUPPORTED EAXC-ID Grouping /user-plane-configuration/eaxc-id- group-configuration 15 LAA LAA Support /user-plane-configuration/tx-array- carriers/laa-carrier-configuration 16 TRANSPORT- FRAGMENTATION Transport Fragmentation M-Plane activation not applicable 17 PRACH-STATIC- CONFIGURATION- SUPPORTED Static configuration of PRACH pattern /user-plane-configuration/static- prach-configurations 18 SRS-STATIC- CONFIGURATION- SUPPORTED Static configuration of SRS pattern /user-plane-configuration/static- srs-configurations 19 "urn:o- ran:performance- management:x.y" GRANULARITY-EAXC- ID-MEASUREMENT EAXC_ID in rx-window- measurement /performance-measurement- objects/rx-window-measurement- objects/object-unit 20 GRANULARITY- TRANSPORT- MEASUREMENT TRANSPORT in rx- window-measurement /performance-measurement- objects/rx-window-measurement- objects/object-unit 21 "urn:o-ran:processing- element:x.y" SHARED_CELL Shared cell support /ru-elements/transport-flow/north- eth-flow and/or /ru- elements/transport-flow/south- eth-flow 22 "urn:o-ran:shared- cell:x.y" FHM FHM support, no capability of radio transmission and reception /shared-cell/shared-cell- config/shared-cell-copy-combine- mode/shared-cell-copy- entities/shared-cell-copy-uplane- config and /shared-cell/shared- cell-config/shared-cell-copy- combine-mode/shared-cell-copy- entities/shared-cell-combine- uplane-config 23 SELECTIVE-BEAM-ID FHM supports the selective combining function by using beamId /shared-cell/shared-cell- config/shared-cell-copy-entities- selective-beam-id and /shared- cell/shared-cell-config/shared- cell-combine-entities-for- selective-beam-id 24 "urn:o-ran:sync:x.y" ANTI-JAM GNSS Anti Jamming /sync/gnss-config/anti-jam-enable 25 GNSS GNSS Support Not applicable 26 "urn:o-ran:uplane- conf:x.y" EAXC-GAIN- CORRECTION eAxC specific gain correction /user-plane-configuration /low- level-rx-endpoints/eaxc-gain- correction 27 TX-REFERENCE- LEVEL TX gain reference level control /user-plane-configuration/tx-array- carriers/reference-level 28 "urn:o- ran:wg4feat:1.0" BEAM-UPDATE- CONTENTION- CONTROL O-RU requirements for beam weight update for a given beamId, to avoid beam update contentions. /user-plane-configuration /low- level-tx-endpoints/eaxc-gain- correction/beam-update- contention-control-enabled and /user-plane-configuration /low- level-rx-endpoints/eaxc-gain- correction/beam-update- contention-control-enabled ETSI ETSI TS 104 023 V17.1.0 (2026-01) 275 No Namespace YANG Feature Name Tag Description Optional Feature Control 29 CHANNEL- INFORMATION- COMPRESSION Compression for channel information in Section Type 6 (indicate at least static compression is supported) /user-plane-configuration /low- level-tx-endpoints/channel- information-compressions 30 CHANNEL- INFORMATION-PRB- GROUP Receiving and processing channel information with PRB group size greater than one /user-plane-configuration /low- level-tx-endpoints/channel- information-prb-group- configuration 31 CPLANE-MESSAGE- PROCESSING-LIMITS C-Plane Message Limits /user-plane-configuration/low- level-tx-endpoints/cplane- message-processing-limits- enabled and /user-plane- configuration /low-level-rx- endpoints/cplane-message- processing-limits-enabled 32 UPLANE-ONLY-DL- MODE O-RU supports U-Plane- only DL mode. /user-plane-configuration/general- config/uplane-only-dl-mode- enable 33 DYNAMIC- TRANSMISSION- WINDOW-CONTROL U-plane transmission window control configuration over C- plane /user-plane-configuration /low- level-rx-endpoints/transmission- window-control 34 EXT-ANT-DELAY- CONTROL O-RU supports external antenna delay control /user-plane-configuration/tx-array- carriers/t-da-offset and/or /user- plane-configuration/rx-array- carriers/t-au-offset 35 EXTENDED-PRACH- CONFIGURATION O-RU is able to support extended number of PRACH patterns and occasions provided by means of static PRACH. /user-plane-configuration/static- low-level-rx-endpoints/extended- max-prach-patterns /user-plane-configuration/static- prach-configurations/prach- patterns/prach-pattern-id /user-plane-configuration/static- prach-configurations/prach- patterns/number-of-occasions /user-plane-configuration/static- prach-configurations/prach- patterns/occasion- parameters/occasion-id 36 ENHANCED-T- COMBINE O-RU can support t- combine-net and tx- duration /shared-cell/shared-cell- config/enhanced-t-combine- enabled 37 INDEPENDENT- TRANSMISSION- WINDOW-CONTROL Independent U-plane transmission window per endpoint M-Plane activation not applicable 38 INTEGRITY-CHECK- AT-SW-DOWNLOAD O-RU can perform integrity check at file download /software-inventory/integrity- check-at-download-enabled 39 MULTIPLE-SCS-IN- EAXC FHM supports combining for multiple SCS or multiple c-plane- types/frameStructure in a single eAxC-id /shared-cell/shared-cell- config/multiple-scs-in-eaxc-used 40 MULTIPLE- TRANSPORT- SESSION-TYPE Multiple transport- session-type /processing-elements/additional- transport-session-type-elements 41 NON-PERSISTENT- MPLANE Optimizations for non- persistent M-Plane O-RU is configured with an event- collector identity (e.g. using DHCP) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 276 No Namespace YANG Feature Name Tag Description Optional Feature Control 42 NON-SCHEDULED- UEID O-RU endpoint is able to support non- scheduled -ueid /user-plane-configuration / low- level-tx-endpoints/ non- scheduled-ueid-enabled and/or /user-plane-configuration / low- level-rx-endpoints/ non- scheduled-ueid-enabled 43 ORDERED- TRANSMISSION Ordered transmission /user-plane-configuration /low- level-rx-endpoints/ordered- transmission 44 SE11-WITH- CONTINUITY-BIT- SUPPORT O-RU is able to support handling 'continuity' bit information in Section Extension 11 /user-plane-configuration/low- level-tx-endpoints/se-11- continuity-flag-enabled 45 SHARED-ORU-MULTI- ODU O-RU is able to support supervision on a per O- DU basis /supervision/per-odu-monitoring 46 SHARED-ORU-MULTI- OPERATOR O-RU is able to support operation with multiple shared resource operator O-DUs /users/user/sro-id 47 STATIC- TRANSMISSION- WINDOW-CONTROL U-plane transmission window control configuration over M- plane /user-plane-configuration /low- level-rx-endpoints/transmission- window-control 48 SUPERVISION-WITH- SESSION-ID O-RU uses the NETCONF session-id in supervision-notification Not applicable 49 UNIFORMLY- DISTRIBUTED- TRANSMISSION Transmission of UL U- plane messages distributed uniformly over transmission window /user-plane-configuration /low- level-rx-endpoints/transmission- type 50 UPLANE-MESSAGE- PROCESSING-LIMITS U-Plane message limits /user-plane-configuration/general- config/ uplane-message-section- header-limit-enabled 51 CALL-HOME- REACTIVATION- SUPPORTED The O-RU supports on- demand re-start of call home flows towards lost call home O-RU controller (s) Control not applicable. For details about intended usage, see clause 6.10 "On-demand renewal of Call Home procedure" 52 SEQ-ID-CHECKING- CONFIGURABLE O-RU supports disabling of sequence number checking /user-plane-configuration/general- config/ seq-id-checking-disabled 53 TRX-CONTROL O-RU Energy saving by TRX control via C-Plane M-Plane activation not applicable. 54 ADVANCED-SLEEP- MODE O-RU Energy saving by Advanced sleep mode M-Plane activation not applicable. 55 SE23-PRB-BLOCK- MODE-SUPPORT O-RU supports PRB- BLOCK mode of SE-23 M-Plane activation not applicable. 56 MPLANE-DATA- LAYER-CONTROL O-RU energy saving by data layer control using M-Plane procedures. M-Plane activation not applicable. 57 PER-PORT-PTP- CONFIG ITU-T G.8275.1 PTP profile specific per-port configuration for multi- port O-RUs M-Plane activation not applicable. 58 PER-PORT-SYNCE- CONFIG ITU-T G.781 SYNCE specific per-port configuration for multi- port O-RUs M-Plane activation not applicable. 59 PER-INT-TCP-MSS O-RU supports configuration of the TCP MSS on a per interface level /if:interfaces/if:interface/ip:ipv4/o- ran-int:tcp/o-ran-int:mss-adjust or /if:interfaces/if:interface/ip:ipv6/o- ran-int:tcp/o-ran-int:mss-adjust ETSI ETSI TS 104 023 V17.1.0 (2026-01) 277 No Namespace YANG Feature Name Tag Description Optional Feature Control 60 MULTIPLE-BEAMID- TABLES-SUPPORTED Multiple beamId table support in O-RU /user-plane-configuration/general- config/ /multiple-beamId-tables- support-enabled 61 MPLANE-TRX- CONTROL O-RU Energy saving by TRX control via M-Plane M-Plane activation not applicable. 62 DEEP-HIBERNATE O-RU Supports Energy saving by deep- hibernate. Activated by the RPC. 63 PRG-SIZE-SUPP-SE- 21-WITH-ST6 O-RU support for receiving prgSize information when SE 21 is sent with ST 6 /user-plane-configuration/low- level-tx-endpoints/prg-size-supp- se-21-with-st6-enabled 64 PRG-SIZE-SUPP-SE- 21-WITH-ST5 O-RU support for receiving prgSize information when SE 21 is sent with ST 5 /user-plane-configuration/low- level-tx-endpoints/prg-size-supp- se-21-with-st5-enabled 65 USER-GROUP- OPTIMIZATION O-RU support for USER-GROUP- OPTIMIZATION /user-plane-configuration /low- level-tx-endpoints/user-group- optimization-enabled-tx 66 BF-DELAY-PROFILE O-RU endpoints support multiple delay profiles based on beamforming methods. /user-plane-configuration /low- level-tx-endpoints /configured-bf- profile and/or /user-plane- configuration /low-level-tx- endpoints / configured-bf-profile 67 CONFIGURABLE- VSWR-THRESHOLDS O-RU supports configurable VSWR thresholds for VSWR alarm. /o-ran-uplane-conf:vswr- thresholds 68 DMRS-BF-EQ O-RU supports DMRS- BF-EQ functionality Feature is activated when a carrier is activated with endpoint that uses beamforming methods DMRS-BF-EQ 69 DMRS-BF-NEQ O-RU supports DMRS- BF-NEQ functionality Feature is activated when a carrier is activated with endpoint that uses beamforming methods DMRS-BF-NEQ 70 DMRS-BF-NEQ- UNALTERED-FREQ- OFFSET O-RU supports DMRS- BF-NEQ beamforming without changing frequency offset M-Plane activation not applicable. 71 DMRS-BF-NEQ- UNALTERED-TAE O-RU supports DMRS- BF-NEQ beamforming without changing TAE M-Plane activation not applicable. 72 RRM-MEAS- REPORTING O-RU supports RRM measurement reporting Feature is activated when any endpoint is configured using rrm- meas-enabled 73 SE10-MEMBER- CANDIDATE-LIST O-RU supports indicate candidate list for SE10 supported endpoints M-Plane activation not applicable. 74 USER-GROUP-SELF- ASSEMBLY O-RU support user group self assembly /user-plane-configuration/rx- array-carrier/user-group-mode 75 UEID-PERSISTENCE O-RU supports ue id persistence procedure /user-plane-configuration/general- config/ueid-persistence-enabled 76 CONTINUITY-BLOCK- SIZE O-RU supports one or more values of continuity block sizes M-Plane activation not applicable. 77 SELECTED-BF- METHOD- CONFIGURATION Configuration of BF method(s) by the O-DU /user-plane-configuration/low- level-tx-endpoints/bf-methods and/or /user-plane-configuration/low- level-rx-endpoints/bf-methods 78 CLIENT-AUTH-SSH- PUBLIC-KEY O-RU supports an optional feature to authenticate SSH client via SSHPUBLICKEY method. /users/user/ssh-public-key and/or chg-ssh-public-key remote procedure call ETSI ETSI TS 104 023 V17.1.0 (2026-01) 278 No Namespace YANG Feature Name Tag Description Optional Feature Control 79 SE27-ODU- CONTROLLED- DIMENSIONALITY- REDUCTION O-RU support for O-DU controlled dimensionality reduction using SE27. /user-plane-configuration/low- level-rx-endpoints/se-27-odu- controlled-dimensionality- reduction-enabled 80 MACSEC-BYPASS- POLICY O-RU supports MACsec bypass policies /if:interfaces/if:interface/o-ran- int:macsec-bypass-policy 81 POINT-A-OFFSET-TO- ABSOLUTE- FREQUENCY-CENTER O-RU supports point-a- offset-to-absolute- frequency-center per rx- array-carrier M-Plane activation not applicable. 82 SECURITY-LOGGING O-RU supports O-RAN defined security logging. M-Plane activation not applicable. 83 ORU-CONTROL-SINR- TIME-RESOLUTION O-RU supports O-RU controlled time resolution for SINR reporting /user-plane-configuration/low- level-rx-endpoints/oru-control- sinr-time-resolution-enabled 84 DYNAMIC-SINR-PER- PRB O-RU supports O-DU controlled frequency resolution for SINR reporting /user-plane-configuration/low-level-rx- endpoints/dynamic-sinr-per-prb- enabled Some of the O-RAN defined YANG models augment existing YANG models which have optional features defined. The optional features defined in these "common" models are shown in Table C.2-2 below. Table C.2-2: Optional feature support in common models No Optional Feature Namespace Feature name 1 IETF RFC 6933 [i.10]: Entity MIB "urn:ietf:params:xml:ns:yang:ietf- hardware" entity-mib 2 IETF RFC 4268 [i.11]: Entity State MIB "urn:ietf:params:xml:ns:yang:ietf- hardware" hardware-state 3 IETF RFC 3433 [i.12]: Entity Sensor Management Information Base "urn:ietf:params:xml:ns:yang:ietf- hardware" hardware-sensor 4 O-RU allows user-controlled interfaces to be named arbitrarily "urn:ietf:params:xml:ns:yang:ietf- interfaces" arbitrary-names 5 O-RU supports pre-provisioning of interface configuration, i.e. it is possible to configure an interface whose physical interface hardware is not present on the device "urn:ietf:params:xml:ns:yang:ietf- interfaces" pre-provisioning 6 IETF RFC 2863 [i.13]: The Interfaces Group MIB "urn:ietf:params:xml:ns:yang:ietf- interfaces" if-mib 7 O-RU supports configuring non-contiguous subnet masks "urn:ietf:params:xml:ns:yang:ietf- ip" ipv4-non-contiguous-netmasks 8 O-RU supports privacy extensions for stateless address autoconfiguration in IPv6 "urn:ietf:params:xml:ns:yang:ietf- ip" ipv6-privacy-autoconf 9 O-RU supports configured YANG Notifications "urn:ietf:params:xml:ns:yang:ietf- subscribed-notifications" configured 10 O-RU supports JSON encoding of subscriptions to YANG notifications "urn:ietf:params:xml:ns:yang:ietf- subscribed-notifications" encode-json C.3 Optional features exposed using O-RAN YANG models In addition to optional namespaces and optional YANG feature tags specified in O-RU supported namespaces, certain O-RAN defined YANG models include read-only YANG leaf nodes used to be able to indicate support by an O-RU of for certain optional capabilities by the O-RU. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 279 Table C.3-1: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:ald-port:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o-ran:ald- port:x.y " Control of ALD's DC power supply /ald-ports-io/ald-port/dc- control-support /ald-ports-io/ald-port/dc- enabled-status Table C.3-2: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:antcal:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:antcal:x.y" O-RU is able to perform self calibration /antenna- calibration/antenna- calibration-capabilities/self- calibration-support /antenna-calibration/self- calibration-policy/self- calibration-allowed 2 "urn:o- ran:antcal:x.y" O-RU supports configuration of the preparedness timer that controls how far in advance of the co-ordinated self calibration procedure the O-RU is required to send the notification of impacted resources /antenna- calibration/antenna- calibration- capabilities/configured- preparation-timer-supported Clause 15.5 defines use when supported. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 280 Table C.3-3: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:beamforming:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:beamformi ng:x.y" O-RU supports the capability to apply the modified beamforming configuration by using rpc activate-beamforming- config-by-capability-group without deletion of tx-array- carriers and rx-array-carriers /beamforming- config/operational- properties/update-bf-non- delete activate-beamforming- config-by-capability-group RPC 2 "urn:o- ran:beamformi ng:x.y" O-RU supports the capability to store the modified beamforming configuration file in the reset persistent memory /beamforming- config/operational- properties/persistent-bf-files M-Plane activation not applicable 3 "urn:o- ran:beamformi ng:x.y" O-RU supports dynamic beamforming control mode /beamforming-config/static- properties/rt-bf-weights- update-support M-Plane activation not applicable. CUS-Plane [2] clause 7.7.1.2 defines use when supported. 4 "urn:o- ran:beamformi ng:x.y" O-RU supports attributes based dynamic beamforming control mode beamforming- config/beamforming-trough- attributes-supported M-Plane activation not applicable. CUS-Plane [2] clause 7.7.2.1 defines use when supported. 5 "urn:o- ran:beamformi ng:x.y" O-RU supports beamforming based on UE channel information beamforming-config /beamforming-trough-ue- channel-info-supported M-Plane activation not applicable. CUS-Plane [2] clause 7.2.7 defines use when supported. 6 "urn:o- ran:beamformi ng:x.y" O-RU supports dynamic channel information compression /beamforming-config/ue- specific- beamforming/dynamic- channel-information- compression-supported M-Plane activation not applicable CUS-Plane [2] clause 7.5.2.15 defines use when supported. 7 "urn:o- ran:beamformi ng:x.y" O-RU support for DMRS- BD-EQ scaling function SCALING-F-1 or SCALING-F-2 /beamforming-config/dmrs- bf/general/capabilities/equali zation-data-scaling M-Plane activation not applicable. 8 "urn:o- ran:beamformi ng:x.y" O-RU supports the capability to apply the modified beamforming configuration without deactivating of tx-array- carriers and rx-array-carriers /beamforming- config/operational- properties/in-service-bf- update activate-beamforming- config RPC or activate-beamforming- config-by-capability-group RPC Table C.3-4: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:message5:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:message5: x.y" O-RU supports eCPRI message 5 one-step procedure for T34 measurements. /ecpri-delay-message/one- step-t34-supported M-Plane activation not applicable CUS-Plane [2] clause 4.4.4.4 defines use when supported. 2 "urn:o- ran:message5: x.y" O-RU supports eCPRI message 5 two-step procedure for T34 measurements. /ecpri-delay-message/two- step-t34-supported M-Plane activation not applicable CUS-Plane [2] clause 4.4.4.4 defines use when supported. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 281 Table C.3-5: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:hardware:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:hardware:x .y" O-RU supports the dying gasp alarm /hardware/component/dying -gasp-support M-Plane activation not applicable Table C.3-6: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:interfaces:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:interfaces:x .y" O-RU's rate able to be supported by an interface is less than nominal bit rate indicated by its transceiver model /interfaces/interface- grouping M-Plane activation not applicable 2 "urn:o- ran:interfaces:x .y" O-RU supports MACsec bypass policies based on destination MAC address, ethertype and/or vlan-id /interfaces/macsec-bypass- capabilities/supported-policy /interfaces/interface/mac sec-bypass-policy/policy Table C.3-7: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:module-cap:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:module- cap:x.y" O-RU supports Category B operation - precoding in the O-RU /module-capability/ru- capabilities/ru-supported- category M-Plane activation not applicable. CUS-Plane [2] clause 7.2.4 defines use when supported. 2 "urn:o- ran:module- cap:x.y" O-RU supports dynamic compression method /module-capability/ru- capabilities/format-of-iq- samples/dynamic- compression-supported M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.10 defines use when supported. 3 "urn:o- ran:module- cap:x.y" O-RU supports real-time variable bit with /module-capability/ru- capabilities/format-of-iq- samples/realtime-variable- bit-width-supported M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.10 defines use when supported. 4 "urn:o- ran:module- cap:x.y" O-RU supports iq compression methods O-RU sets the list /module- capability/ru- capabilities/format-of-iq- samples/compression- method-supported with compression methods the O-RU supports. M-Plane activation not applicable. CUS-Plane [2] clause 8.3.3.13 defines use when supported. 5 "urn:o- ran:module- cap:x.y" O-RU supports beamspace compression O-RU sets a list entry /module-capability/ru- capabilities/format-of-iq- samples/compression- method-supported with compression-method set to "BEAMSPACE" M-Plane activation not applicable. CUS-Plane [2] clause 8.3.3.13 defines use when supported. 6 "urn:o- ran:module- cap:x.y" O-RU supports variable bit width per channel /module-capability/ru- capabilities/format-of-iq- samples/variable-bit-width- per-channel-supported M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.10 defines use when supported. 7 "urn:o- ran:module- cap:x.y" O-RU supports symbol number increment command in a C-Plane /module-capability/ru- capabilities/format-of-iq- samples/syminc-supported M-Plane activation not applicable. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 282 No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 8 "urn:o- ran:module- cap:x.y" O-RU supports regularizationFactor in section type 5 /module-capability/ru- capabilities/format-of-iq- samples/regularization- factor-se-supported /user-plane- configuration/general- config/regularization- factor-se-configured 9 "urn:o- ran:module- cap:x.y" O-RU supports little endian /module-capability/ru- capabilities/format-of-iq- samples/little-endian- supported /user-plane- configuration/general- config/little-endian-byte- order 10 "urn:o- ran:module- cap:x.y" O-RU requires 4-byte aligned Section Type 6 /module-capability/ru- capabilities/st6-4byte- alignment-required M-Plane activation not applicable. CUS-Plane [2] clause 7.3.1 defines use when supported. 11 "urn:o- ran:module- cap:x.y" O-RU supports energy saving by transmission blanking /module-capability/ru- capabilities/energy-saving- by-transmission-blanks M-Plane activation not applicable. CUS-Plane [2] clause 8.4.2.3 defines use when supported. 12 "urn:o- ran:module- cap:x.y" O-RU supports dynamic transport delay management through eCPRI Msg 5 /module-capability/ru- capabilities/dynamic- transport-delay- management-supported M-Plane activation not applicable. CUS-Plane [2] clause 4.4.4.4 defines use when supported. 13 "urn:o- ran:module- cap:x.y" O-RU expects unique eCPRI sequence id for eAxC_IDs serving for UL and DL for the same Component Carrier /module-capability/ru- capabilities/support-only- unique-ecpri-seqid-per-eaxc M-Plane activation not applicable. CUS-Plane [2] defines use when supported. 14 "urn:o- ran:module- cap:x.y" O-RU supports coupling of C and U-plane messages by frequency and time /module-capability/coupling- methods/coupling-via- frequency-and-time M-Plane activation not applicable. CUS-Plane [2] clause 8.4.1 defines use when supported. 15 "urn:o- ran:module- cap:x.y" O-RU supports coupling of C and U-plane messages by frequency and time with priorities /module-capability/coupling- methods/coupling-via- frequency-and-time-with- priorities M-Plane activation not applicable. CUS-Plane [2] clause 7.9.7 defines use when supported. 16 "urn:o- ran:module- cap:x.y" O-RU supports coupling of C and U-plane messages by frequency and time with priorities optimized /module-capability/coupling- methods/coupling-via- frequency-and-time-with- priorities-optimized M-Plane activation not applicable. CUS-Plane [2] clause 7.9.8 defines use when supported. 17 "urn:o- ran:module- cap:x.y" O-RU supports optional field udCompLen in U-Plane messages /module-capability/ud-comp- len-supported M-Plane activation not applicable. CUS-Plane [2] clause 8.3.3.19 defines use when supported. 18 "urn:o- ran:module- cap:x.y" O-RU supports configuration of different t-da-offset on different tx-array-carriers, and different t-au-offset on different rx-array-carriers /module-capability/ext-ant- delay-capability set to "PER- ARRAY-CARRIER" M-Plane activation not applicable. CUS-Plane [2] clause 4.7 defines use when supported. 19 "urn:o- ran:module- cap:x.y" O-RU supports the configuration of different t- da-offset on different tx- array-carriers only when those tx-array-carriers belong to different tx-arrays /module-capability/ext-ant- delay-capability set to "PER- ARRAY" M-Plane activation not applicable. CUS-Plane [2] clause 4.7 defines use when supported. 20 "urn:o- ran:module- cap:x.y" O-RU supports the configuration of a common t- da-offset across all tx-array- carriers /module-capability/ext-ant- delay-capability set to "PER- O-RU" M-Plane activation not applicable. CUS-Plane [2] clause 4.7 defines use when supported. 21 "urn:o- ran:module- cap:x.y" O-RU supports sending NACK feedback if a section extension for ACK/NACK request is received /module-capability/nack- supported M-Plane activation not applicable. CUS-Plane [2] defines use when supported. 22 "urn:o- ran:module- cap:x.y" O-RU local management of the LAA contention window /module-capability/band- capabilities/sub-band- info/self-configure M-Plane activation not applicable. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 283 No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 23 "urn:o- ran:module- cap:x.y" O-RU supports Ready message via Section Type 8 /module-capability/ru- capabilities/energy-saving- capability-common-info/st8- ready-command-supported M-Plane activation not applicable. CUS-Plane [2] clause 16.6.2 defines use when supported. 24 "urn:o- ran:module- cap:x.y" O-RU supports extension of ongoing sleep interval. /module-capability/ru- capabilities/energy-saving- capability-common- info/sleep-duration- extension-supported M-Plane activation not applicable. CUS-Plane [2] clause 16.8 defines use when supported. 25 "urn:o- ran:module- cap:x.y" O-RU supports M-Plane Emergency wake-up procedure /module-capability/ru- capabilities/energy-saving- capability-common- info/emergency-wake-up- command-supported M-Plane activation not applicable. Clause 20.3.1.3 defines use when supported. 26 "urn:o- ran:module- cap:x.y" O-RU supports optional field scs in Section Type 8 /module-capability/ru- capabilities/st8-scs- supported M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.16 defines use when supported. 27 "urn:o- ran:module- cap:x.y" O-RU supports receiving non-zero values of bundleOffset in SE11. /module-capability/ru- capabilities/bundle-offset-in- se11-supported M-Plane activation not applicable. CUS-Plane [2] clause 7.7.11.10 defines use when supported. Table C.3-8: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:operations:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:operations: x.y" IEEE 1914.3 header support /operational- info/declarations/supported- header-mechanism/protocol M-Plane activation not applicable. CUS-Plane [2] clause 5.1.3.3 defines use when supported. 2 "urn:o- ran:operations: x.y" eCPRI Concatenation support /operational- info/declarations/supported- header-mechanism/ecpri- concatenation-support M-Plane activation not applicable. CUS-Plane [2] clause 5.1.3.2.4 defines use when supported. Table C.3-9: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:performance-management:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:performance- management:x.y" O-RU supports RX power transceiver measurement /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "RX_POWER" /performance- measurement/objects/tra nsceiver-measurement- objects 2 "urn:o- ran:performance- management:x.y " O-RU supports TX power transceiver measurement /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "TX_POWER" /performance- measurement/objects/tra nsceiver-measurement- objects 3 "urn:o- ran:performance- management:x.y " O-RU supports TX Bias Current transceiver measurement /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "TX_BIAS_COUNT" /performance- measurement/objects/tra nsceiver-measurement- objects 4 "urn:o- ran:performance- management:x.y " O-RU supports transceiver voltage measurement /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "VOLTAGE" /performance- measurement/objects/tra nsceiver-measurement- objects ETSI ETSI TS 104 023 V17.1.0 (2026-01) 284 No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 5 "urn:o- ran:performance- management:x.y " O-RU supports transceiver module temperature measurement /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "TEMPERATURE" /performance- measurement/objects/tra nsceiver-measurement- objects 6 "urn:o- ran:performance- management:x.y " O-RU supports RX Window on Time measurement /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_ON_TIME" /performance- measurement/objects/rx- window-measurement- objects 7 "urn:o- ran:performance- management:x.y " O-RU supports RX Window too early Time measurement /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_EARLY" /performance- measurement/objects/rx- window-measurement- objects 8 "urn:o- ran:performance- management:x.y " O-RU supports RX Window too late Time measurement /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_LATE" /performance- measurement/objects/rx- window-measurement- objects 9 "urn:o- ran:performance- management:x.y " O-RU supports RX Window corrupt measurement /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_CORRUPT" /performance- measurement/objects/rx- window-measurement- objects 10 "urn:o- ran:performance- management:x.y " O-RU supports RX Window duplicate measurement /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to RX_DUPL /performance- measurement/objects/rx- window-measurement- objects 11 "urn:o- ran:performance- management:x.y " O-RU supports RX Window on Time measurement for control packets /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_ON_TIME_C" /performance- measurement/objects/rx- window-measurement- objects 12 "urn:o- ran:performance- management:x.y " O-RU supports RX Window too early Time measurement for control packets /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_EARLY _C" /performance- measurement/objects/rx- window-measurement- objects 13 "urn:o- ran:performance- management:x.y " O-RU supports RX Window too late Time measurement for control packets /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_LATE_C" /performance- measurement/objects/rx- window-measurement- objects 14 "urn:o- ran:performance- management:x.y " O-RU supports RX Window sequence error measurements /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_SEQID_ERR" /performance- measurement/objects/rx- window-measurement- objects 15 "urn:o- ran:performance- management:x.y " O-RU supports RX Window sequence error measurements for control packets /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX_SEQID_ERR_C" /performance- measurement/objects/rx- window-measurement- objects 16 "urn:o- ran:performance- management:x.y " O-RU supports RX Window packet drop measurements /performance-management- objects/measurement- capabilities/rx-window- objects/measurement-object set to "RX _ERR_DROP" /performance- measurement/objects/rx- window-measurement- objects 17 "urn:o- ran:performance- management:x.y " O-RU supports TX Window measurements for all outbound packets /performance-management- objects/measurement- capabilities/tx-stats- objects/measurement-object set to "TX_TOTAL" /performance- measurement/objects/tx- measurement-objects ETSI ETSI TS 104 023 V17.1.0 (2026-01) 285 No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 18 "urn:o- ran:performance- management:x.y " O-RU supports TX Window measurements for outbound controlpackets /performance-management- objects/measurement- capabilities/tx-stats- objects/measurement-object set to "TX_TOTAL_C" /performance- measurement/objects/tx- measurement-objects 19 "urn:o- ran:performance- management:x.y " O-RU supports temperature measurements of specific hardware components /performance-management- objects/measurement- capabilities/epe-stats- objects/measurement-object set to "TEMPERATURE" /performance- measurement/objects/ep e-measurement-objects 20 "urn:o- ran:performance- management:x.y " O-RU supports power measurements of specific hardware components /performance-management- objects/measurement- capabilities/epe-stats- objects/measurement-object set to "POWER" /performance- measurement/objects/ep e-measurement-objects 21 "urn:o- ran:performance- management:x.y " O-RU supports voltage measurements of specific hardware components /performance-management- objects/measurement- capabilities/epe-stats- objects/measurement-object set to "VOLTAGE" /performance- measurement/objects/ep e-measurement-objects 22 "urn:o- ran:performance- management:x.y " O-RU supports current measurements of specific hardware components /performance-management- objects/measurement- capabilities/epe-stats- objects/measurement-object set to "CURRENT" /performance- measurement/objects/ep e-measurement-objects 23 "urn:o- ran:performance- management:x.y " O-RU supports VSWR measurements /performance-management- objects/measurement- capabilities/tx-antenna- stats-objects/measurement- object set to "VSWR" /performance- measurement/objects/tx- antenna-measurement- objects 24 "urn:o- ran:performance- management:x.y " O-RU supports transceiver laser temperature measurements /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "LASER_TEMPERATURE" /performance- measurement/objects/tra nsceiver-measurement- objects 24 "urn:o- ran:performance- management:x.y " O-RU supports transceiver module TEC current measurement /performance-management- objects/measurement- capabilities/transceiver- objects/measurement-object set to "TEC_CURRENT" /performance- measurement/objects/tra nsceiver-measurement- objects Table C.3-10: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:shared-cell:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:shared- cell:x.y" O-RU supports multi cell operation in shared cell cascade mode /shared-cell/shared-cell- module-cap/multi-cell-in- cascade-mode-supported M-Plane activation not applicable. CUS-Plane [2] clause 13.4 defines use when supported. Table C.3-11: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:software-management:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:software- management:x. y" O-RU requires separate download procedures to be re-used for downloading individual files in a software build, instead of a single archived package /software-inventory/build- content-download software-download rpc ETSI ETSI TS 104 023 V17.1.0 (2026-01) 286 Table C.3-12: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:sync:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:sync:x.y" O-RU supports PTP O-RU includes "PTP" enumeration in /sync/:sync- status/supported-reference- type list item /sync/ptp-config 2 "urn:o- ran:sync:x.y" O-RU supports Synchronous Ethernet O-RU includes "SYNCE" enumeration in /sync/:sync- status/supported-reference- type list item /sync/synce-config 3 "urn:o- ran:sync:x.y" O-RU supports GNSS O-RU includes "GNSS" enumeration in /sync/:sync- status/supported-reference- type list item /sync/gnss-config 4 "urn:o- ran:sync:x.y" O-RU supports the T-BC profiles in Recommendation ITU-T G.8275.1 [22] /sync/sync- capability/boundary-clock- supported M-Plane activation not applicable. 5 "urn:o- ran:sync:x.y" O-RU supports enhanced accuracy for sync as per IEEE 802.1CM [80] clause 6.4.1 O-RU sets /sync/sync- capability/sync-t-tsc to "ENHANCED" M-Plane activation not applicable. Table C.3-13: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:uplane-conf:x.y YANG model No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 1 "urn:o- ran:uplane- conf:x.y" Section types supported by the O-RU endpoint /user-plane- configuration/endpoint- types/supported-section- types/section-type M-Plane activation not applicable. CUS-Plane [2] clause 7.3.1 defines use when supported. 2 "urn:o- ran:uplane- conf:x.y" Section type extensions supported by the O-RU endpoint /user-plane- configuration/endpoint- types/supported-section- types/supported-section- extensions M-Plane activation not applicable. CUS-Plane [2] clause 7.3.2 defines use when supported. 3 "urn:o- ran:uplane- conf:x.y" Supported frame structures /user-plane- configuration/endpoint- types/supported-frame- structures M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.13 defines use when supported. 4 "urn:o- ran:uplane- conf:x.y" O-RU endpoint supports time managed delays /user-plane- configuration/endpoint- types/managed-delay- support set to "MANAGED" or "BOTH" /user-plane- configuration/low-level-rx- endpoints/non-time- managed-delay-enabled 5 "urn:o- ran:uplane- conf:x.y" O-RU endpoint supports multiple numerologies /user-plane- configuration/endpoint- types/multiple-numerology- supported set to "true" M-Plane activation not applicable. CUS-Plane [2] table 7.4-3 defines use when supported. 6 "urn:o- ran:uplane- conf:x.y" O-RU endpoint supports non-scheduled-ueid /user-plane-configuration/ endpoint-type/non- scheduled-ueid-supported set to "true" /user-plane-configuration / low-level-tx-endpoints/ non-scheduled-ueid- enabled and/or /user- plane-configuration / low- level-rx-endpoints/ non- scheduled-ueid-enabled ETSI ETSI TS 104 023 V17.1.0 (2026-01) 287 No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 7 "urn:o- ran:uplane- conf:x.y" O-RU supports defined duration sleep functionality for TRX Control. user-plane-configuration/tx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/trx-control- capability-info/defined- duration-sleep-supported and/or user-plane-configuration/rx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/trx-control- capability-info/defined- duration-sleep-supported M-Plane activation not applicable. CUS-Plane [2] clause 16.4 defines use when supported. 8 "urn:o- ran:uplane- conf:x.y" O-RU supports undefined duration sleep functionality for TRX Control. user-plane-configuration/tx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/trx-control- capability-info/undefined- duration-sleep-supported and/or user-plane-configuration/rx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/trx-control- capability-info/undefined- duration-sleep-supported M-Plane activation not applicable. CUS-Plane [2] clause 16.4 defines use when supported. 9 "urn:o- ran:uplane- conf:x.y" O-RU supports defined duration sleep functionality for ASM. /user-plane-configuration/tx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/asm- capability-info/defined- duration-sleep-supported and/or /user-plane-configuration/rx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/asm- capability-info/defined- duration-sleep-supported M-Plane activation not applicable. CUS-Plane [2] clause 16.5 defines use when supported. 10 "urn:o- ran:uplane- conf:x.y" O-RU supports undefined duration sleep functionality for ASM. /user-plane-configuration/tx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/asm- capability-info/undefined- duration-sleep-supported and/or /user-plane-configuration/rx- arrays/capabilities/supporte d-energy-saving- capabilities-dl/asm- capability-info/undefined- duration-sleep-supported M-Plane activation not applicable. CUS-Plane [2] clause 16.5 defines use when supported. 11 "urn:o- ran:uplane- conf:x.y" O-RU support for USER- GROUP-OPTIMIZATION /user-plane-configuration /low-level-tx-endpoints/ user-group-optimization- enabled-tx M-Plane activation not applicable. CUS-Plane [2] clause 7.9.14 defines use when supported. 12 "urn:o- ran:uplane- conf:x.y" O-RU support for USER- GROUP-OPTIMIZATION /user-plane-configuration /low-level-rx-endpoints/ user-group-optimization- enabled-rx M-Plane activation not applicable. CUS-Plane [2] clause 7.9.14 defines use when supported. 13 "urn:o- ran:uplane- conf:x.y" O-RU Support for Section Extension 10 beamGroupType = 11b /user-plane-configuration/ endpoint-type/se-10-bgt- 11b-supported set to "true" M-Plane activation not applicable. CUS-Plane [2] clause 7.7.10.1 defines use when supported. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 288 No Namespace Optional Feature Read-only YANG leaf indicating feature support Optional Feature Control 14 "urn:o- ran:uplane- conf:x.y" SINR reporting for DMRS- BF-EQ /user-plane- configuration/endpoint- types/sinr-reporting- supported /user-plane- configuration/low-level-rx- endpoints/sinr-reporting- enabled 15 "urn:o- ran:uplane- conf:x.y" User group self-assembly with group id for DMRS-BF /user-plane- configuration/endpoint- types/user-group-self- assembly-mode /user-plane- configuration/rx-array- carriers/user-group-mode 16 "urn:o- ran:uplane- conf:x.y" O-RU support for frequency offset /user-plane-configuration /low- level-rx-endpoints/se26-usage- enabled M-Plane activation not applicable. CUS-Plane [2] clause 7.7.26 defines use when supported. 17 "urn:o- ran:uplane- conf:x.y" O-RU support for symbol reordering /user-plane- configuration/endpoint- types/supported-symb-reorder- capabilitys /user-plane- configuration/general- config/config-symb-reorder- method or /user-plane- configuration/general- config/config-symb-reorder- upSymbId-type 18 "urn:o- ran:uplane- conf:x.y" O-RU support for rrm measurements: MEAS-UE-TAE MEAS-UE-LAYER-POWER MEAS-UE-FREQ-OFFSET MEAS-IPN-ALLOC MEAS-IPN-UNALLOC MEAS-ANT-DMRS-SNR /user-plane-configuration /endpoint-types/rrm-meas- supported /user-plane- configuration/low-level-rx- endpoints/rrm-meas- enabled Allowed values: MEAS-UE-TAE MEAS-UE-LAYER- POWER MEAS-UE-FREQ- OFFSET MEAS-IPN-ALLOC MEAS-IPN-UNALLOC MEAS-ANT-DMRS-SNR Table C.3-14: Optional features where support is indicated by YANG leaf nodes defined in urn:ieee:std:802.1X:yang:ieee802-dot1x YANG model No Namespace Optional Feature YANG leaf indicating feature support Optional Feature Control 1 "urn:ieee:std:8 02.1X:yang:iee e802-dot1x" O-RU supports MACsec Key Agreement /if:interfaces/if:interface/dot1 x:pae/dot1x:port- capabilities/dot1x:mka /if:interfaces/if:interface/d ot1x:pae/dot1x:kay: /dot1x:enable 2 "urn:ieee:std:8 02.1X:yang:iee e802-dot1x" O-RU supports MACsec /if:interfaces/if:interface/dot1 x:pae/dot1x:port- capabilities/dot1x:macsec and /if:interfaces/if:interface/dot1 x:pae/dot1x:kay/dot1x:macs ec/dot1x:capable Controlled by enabling MACsec Key Agreement ETSI ETSI TS 104 023 V17.1.0 (2026-01) 289 Annex D (informative): YANG module graphical representation D.1 Introduction This clause provides a set of "tree-views" of the modules to provide a simplified graphical representation of the data models. These trees have been automatically generated using the pyang YANG validator tool [i.4]. D.2 System folder D.2.1 o-ran-supervision.yang module The format for the supervision module is provided below. module: o-ran-supervision +--rw supervision +--rw cu-plane-monitoring! | +--rw configured-cu-monitoring-interval? uint8 +--rw event-collector-monitoring {or-feat:NON-PERSISTENT-MPLANE}? | +--rw heartbeat-interval? uint8 | +--rw heartbeat-recipient-id* event-collector-id +--rw per-odu-monitoring! {or-feat:SHARED-ORU-MULTI-ODU or or-feat:SHARED-ORU-MULTI-OPERATOR}? +--rw odu-ids* [odu-id] {or-feat:SHARED-ORU-MULTI-ODU}? | +--rw odu-id string +--rw sro-ids-and-odu-ids* [odu-id sro-id] {or-feat:SHARED-ORU-MULTI-ODU and or-feat:SHARED- ORU-MULTI-OPERATOR}? +--rw odu-id string +--rw sro-id string rpcs: +---x supervision-watchdog-reset +---w input | +---w supervision-notification-interval? uint16 | +---w guard-timer-overhead? uint16 | +---w context {or-feat:SHARED-ORU-MULTI-ODU or or-feat:SHARED-ORU-MULTI-OPERATOR}? | +---w odu-id? string {or-feat:SHARED-ORU-MULTI-ODU}? | +---w sro-id? -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? +--ro output +--ro next-update-at? yang:date-and-time +--ro error-message? string notifications: +---n supervision-notification +--ro session-id -> /ncm:netconf-state/sessions/session/session-id {or-feat:SUPERVISION- WITH-SESSION-ID}? D.2.2 o-ran-usermgmt.yang module The format for the user management module is provided below. module: o-ran-usermgmt +--rw users +--rw user* [name] +--rw name nacm:user-name-type +--rw account-type? enumeration +--rw password? password-type +--rw ssh-public-key {feat:CLIENT-AUTH-SSH-PUBLIC-KEY}? | +--rw public-key-format identityref | +--rw public-key binary +--rw enabled? boolean +--rw sro-id* string {feat:SHARED-ORU-MULTI-OPERATOR}? rpcs: +---x chg-password ETSI ETSI TS 104 023 V17.1.0 (2026-01) 290 | +---w input | | +---w currentPassword password-type | | +---w newPassword password-type | | +---w newPasswordConfirm password-type | +--ro output | +--ro status enumeration | +--ro status-message? string +---x chg-ssh-public-key {feat:CLIENT-AUTH-SSH-PUBLIC-KEY}? +---w input | +---w current-ssh-public-key | | +---w public-key-format identityref | | +---w public-key binary | +---w new-ssh-public-key | | +---w public-key-format identityref | | +---w public-key binary | +---w new-ssh-public-key-confirm | +---w public-key-format identityref | +---w public-key binary +--ro output +--ro status enumeration +--ro status-message? string D.2.3 o-ran-hardware.yang module The format for the hardware module is provided below. module: o-ran-hardware augment /hw:hardware/hw:component: +--ro label-content | +--ro model-name? boolean | +--ro serial-number? boolean +--ro product-code string +--rw energy-saving-enabled? boolean {ENERGYSAVING}? +--ro dying-gasp-support? Boolean +--rw last-service-date? yang:date-and-time {or-feat:NON-PERSISTENT-MPLANE}? augment /hw:hardware/hw:component: +--rw o-ran-name -> /hw:hardware/component/name augment /hw:hardware/hw:component/hw:state: +--ro power-state? energysaving-state {ENERGYSAVING}? +--ro availability-state? availability-type augment /hw:hardware/hw:component: +--ro connector-label? string augment /hw:hardware-state-oper-enabled: +--ro availability-state? -> /hw:hardware/component/state/o-ran-hw:availability-state {hw:hardware-state}? augment /hw:hardware-state-oper-disabled: +--ro availability-state? -> /hw:hardware/component/state/o-ran-hw:availability-state {hw:hardware-state}? D.2.4 o-ran-fan.yang module The format for the fan module is provided below. module: o-ran-fan +--ro fan-tray +--ro fan-state* [name] +--ro name string +--ro fan-location? uint8 +--ro present-and-operating boolean +--ro vendor-code? uint8 +--ro fan-speed? percent +--ro target-speed? uint16 D.2.5 o-ran-fm.yang module The format for the fault management module is provided below. module: o-ran-fm +--ro active-alarm-list | +--ro active-alarms* [] | +--ro fault-id uint16 | +--ro fault-source string ETSI ETSI TS 104 023 V17.1.0 (2026-01) 291 | +--ro affected-objects* [] | | +--ro name string | | +--ro identifier? yang:xpath1.0 | +--ro fault-severity enumeration | +--ro is-cleared boolean | +--ro fault-text? string | +--ro probable-cause? string | +--ro specific-problem? string | +--ro proposed-repair-actions? string | +--ro event-time yang:date-and-time | +--ro additional-information* [identifier] | | +--ro identifier string | | +--ro information? string | +--ro alarm-type? enumeration | +--ro fault-name? string +--rw historical-alarm-list {HISTORICAL-ALARM-LIST}? +--ro historical-alarms* [] +--ro fault-id uint16 +--ro fault-source string +--ro affected-objects* [] | +--ro name string | +--ro identifier? yang:xpath1.0 +--ro fault-severity enumeration +--ro is-cleared boolean +--ro fault-text? string +--ro probable-cause? string +--ro specific-problem? string +--ro proposed-repair-actions? string +--ro event-time yang:date-and-time +--ro additional-information* [identifier] | +--ro identifier string | +--ro information? string +--ro alarm-type? enumeration +--ro fault-name? string notifications: +---n alarm-notif +--ro fault-id uint16 +--ro fault-source string +--ro affected-objects* [] | +--ro name string | +--ro identifier? yang:xpath1.0 +--ro fault-severity enumeration +--ro is-cleared boolean +--ro fault-text? string +--ro probable-cause? string +--ro specific-problem? string +--ro proposed-repair-actions? string +--ro event-time yang:date-and-time +--ro additional-information* [identifier] | +--ro identifier string | +--ro information? string +--ro alarm-type? enumeration +--ro fault-name? string D.2.6 o-ran-ves-subscribed-notifications.yang module The format for the ves subscribed notifications module is provided below. module: o-ran-ves-subscribed-notifications augment /sn:subscriptions/sn:subscription/sn:receivers/sn:receiver: +--rw notification-recipient inet:uri D.2.7 o-ran-certificates.yang module The format for the certificates module is provided below. module: o-ran-certificates +--rw certificate-parameters +--rw cert-maps | +--rw cert-to-name* [id] | +--rw id uint32 | +--rw fingerprint x509c2n:tls-fingerprint | +--rw map-type identityref ETSI ETSI TS 104 023 V17.1.0 (2026-01) 292 | +--rw name string +--rw cert-expiry-policy | +--rw cert-lcm-policy? enumeration +--rw advance-cert-expiry-alarms-config +--rw minor-alarm-advance-time? uint16 +--rw major-alarm-advance-time? uint16 +--rw critical-alarm-advance-time? uint16 augment /ietf-sys:system/dot1x:pae-system: +--rw credential {ietf-ts:certificates}? +--rw ca-root? -> /ietf-ts:truststore/certificate-bags/certificate-bag/name +--rw ca-roots* -> /ietf-ts:truststore/certificate-bags/certificate-bag/name +--rw client-cert? -> /ietf-ks:keystore/asymmetric-keys/asymmetric- key/certificates/certificate/name notifications: +---n certificate-lcm +--ro certificate-name? -> /ietf-ks:keystore/asymmetric-keys/asymmetric- key/certificates/certificate/name +--ro cmpv2-procedure enumeration +--ro pki-status uint8 +--ro pki-failure-info* uint8 +--ro pki-free-text? string D.3 Operations folder D.3.1 o-ran-operations.yang module The format for the operations module is provided below. module: o-ran-operations +--rw operational-info +--ro declarations | +--ro ru-instance-id? string | +--ro supported-mplane-version? version | +--ro supported-cusplane-version? version | +--ro supported-header-mechanism* [protocol] | | +--ro protocol enumeration | | +--ro ecpri-concatenation-support? boolean | | +--ro protocol-version? version | +--ro supported-common-event-header-version? version {or-feat:NON-PERSISTENT-MPLANE}? | +--ro supported-ves-event-listener-version? version {or-feat:NON-PERSISTENT-MPLANE}? | +--ro supported-pnf-registration-fields-version? version {or-feat:NON-PERSISTENT-MPLANE}? | +--ro maximum-simultaneous-netconf-sessions? uint8 +--ro operational-state | +--ro restart-cause? enumeration | +--ro restart-datetime? yang:date-and-time | +--ro current-datetime? yang:date-and-time +--rw clock | +--rw timezone-name? timezone-name | +--rw timezone-utc-offset? int16 +--rw re-call-home-no-ssh-timer? uint16 +--rw max-call-home-attempts? uint8 rpcs: +---x reset +---x restart-call-home {or-feat:CALL-HOME-REACTIVATION-SUPPORTED}? +---x emergency-wake-up {or-feat:TRX-CONTROL or or-feat:ADVANCED-SLEEP-MODE}? | +---w input | | +---w sro-id* -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? | +--ro output | +--ro operational-status* [index] | +--ro index uint8 | +--ro sro-id? -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? | +--ro status? enumeration +---x deep-hibernate {or-feat:DEEP-HIBERNATE}? +---w input | +---w hibernate-time uint32 +--ro output +--ro status? enumeration +--ro error-message? string notifications: ETSI ETSI TS 104 023 V17.1.0 (2026-01) 293 +---n emergency-wake-up-complete {or-feat:TRX-CONTROL or or-feat:ADVANCED-SLEEP-MODE}? | +--ro sro-id? -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? +---n deep-hibernate-activated {or-feat:DEEP-HIBERNATE}? +--ro hibernate-time uint32 D.3.2 o-ran-file-management.yang module The format for the file management module is provided below. module: o-ran-file-management rpcs: +---x file-upload | +---w input | | +---w local-logical-file-path string | | +---w remote-file-path string | | +---w (credentials)? | | | +--:(password) | | | | +---w password! | | | | | +---w password string | | | | +---w server | | | | +---w keys* [algorithm] | | | | +---w algorithm asymmetric-key-algorithm-ref | | | | +---w public-key? binary | | | +--:(certificate) | | | +---w certificate! | | +---w application-layer-credential | | +---w appl-password? string | +--ro output | +--ro status? enumeration | +--ro reject-reason? string +---x retrieve-file-list | +---w input | | +---w logical-path string | | +---w file-name-filter? string | +--ro output | +--ro status? enumeration | +--ro reject-reason? string | +--ro file-list* string +---x file-download +---w input | +---w local-logical-file-path string | +---w remote-file-path string | +---w (credentials)? | | +--:(password) | | | +---w password! | | | | +---w password string | | | +---w server | | | +---w keys* [algorithm] | | | +---w algorithm asymmetric-key-algorithm-ref | | | +---w public-key? binary | | +--:(certificate) | | +---w certificate! | +---w application-layer-credential | +---w appl-password? string +--ro output +--ro status? enumeration +--ro reject-reason? string notifications: +---n file-upload-notification | +--ro local-logical-file-path string | +--ro remote-file-path string | +--ro status? enumeration | +--ro reject-reason? string +---n file-download-event +--ro local-logical-file-path string +--ro remote-file-path string +--ro status? enumeration +--ro reject-reason? string ETSI ETSI TS 104 023 V17.1.0 (2026-01) 294 D.3.3 o-ran-software-management.yang module The format for the software management module is provided below. module: o-ran-software-management +--ro software-inventory +--ro software-slot* [name] | +--ro name string | +--ro status enumeration | +--ro active? boolean | +--ro running? boolean | +--ro access? enumeration | +--ro product-code? -> /hw:hardware/component/o-ran-hw:product-code | +--ro vendor-code? string | +--ro build-id? string | +--ro build-name? string | +--ro build-version? string | +--ro files* [name] | +--ro name string | +--ro version? string | +--ro local-path string | +--ro integrity? enumeration +--ro build-content-download? Empty +--ro integrity-check-at-download-enabled? empty {or-feat:INTEGRITY-CHECK-AT-SW-DOWNLOAD}? rpcs: +---x software-download | +---w input | | +---w remote-file-path inet:uri | | +---w (credentials)? | | | +--:(password) | | | | +---w password! | | | | | +---w password string | | | | +---w server | | | | +---w keys* [algorithm] | | | | +---w algorithm asymmetric-key-algorithm-ref | | | | +---w public-key? binary | | | +--:(certificate) | | | +---w certificate! | | +---w application-layer-credential | | +---w appl-password? string | +--ro output | +--ro status enumeration | +--ro error-message? string | +--ro notification-timeout? int32 +---x software-install | +---w input | | +---w slot-name -> /software-inventory/software-slot/name | | +---w file-names* string | +--ro output | +--ro status enumeration | +--ro error-message? string | +--ro sw-install-timeout? int32 +---x software-activate +---w input | +---w slot-name -> /software-inventory/software-slot/name +--ro output +--ro status enumeration +--ro error-message? string +--ro notification-timeout? int32 notifications: +---n download-event | +--ro file-name string | +--ro status? enumeration | +--ro error-message? string +---n install-event | +--ro slot-name? -> /software-inventory/software-slot/name | +--ro status? enumeration | +--ro error-message? string +---n activation-event +--ro slot-name? -> /software-inventory/software-slot/name +--ro status? enumeration +--ro return-code? uint8 +--ro error-message? string ETSI ETSI TS 104 023 V17.1.0 (2026-01) 295 D.3.4 o-ran-lbm.yang module The format for the (Ethernet) loopback module is provided below. module: o-ran-lbm +--rw md-data-definitions +--rw maintenance-domain* [id] +--rw id string +--rw name? string +--rw md-level? md-level-type +--rw maintenance-association* [id] +--rw id string +--rw name? string +--rw component-list* [component-id] +--rw component-id uint32 +--rw name? string +--rw vid* -> /if:interfaces/interface/o-ran-int:vlan- id +--rw remote-meps* mep-id-type +--rw maintenance-association-end-point* [mep-identifier] +--rw mep-identifier mep-id-type +--rw interface -> /if:interfaces/interface/name +--rw primary-vid union +--rw administrative-state boolean +--ro mac-address? -> /if:interfaces/interface/o-ran-int:mac-address +--ro loopback +--ro replies-transmitted yang:counter32 D.3.5 o-ran-udp-echo.yang module The format for the udp echo module is provided below. module: o-ran-udp-echo +--rw udp-echo {o-ran-int:UDPIP-BASED-CU-PLANE}? +--rw enable-udp-echo? boolean +--rw dscp-config? enumeration +--ro echo-replies-transmitted? uint32 D.3.6 o-ran-ecpri-delay.yang module The format for the ecpri delay management module is provided below. module: o-ran-ecpri-delay +--rw ecpri-delay-message x--ro ru-compensation | +--ro tcv2? uint32 | +--ro tcv1? uint32 +--rw enable-message5? boolean +--ro one-step-t34-supported? boolean +--ro two-step-t34-supported? boolean +--rw message5-sessions +--rw session-parameters* [session-id] +--rw session-id uint32 +--rw processing-element-name? -> /element:processing-elements/ru- elements/name +--rw transport-session-type? enumeration {feat:MULTIPLE- TRANSPORT-SESSION-TYPE}? +--rw transport-qualified-processing-element-name? -> /element:processing- elements/additional-transport-session-type-elements[element:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? +--ro flow-state +--ro responses-transmitted? uint32 +--ro requests-transmitted? uint32 +--ro followups-transmitted? uint32 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 296 D.3.7 o-ran-performance-management.yang module The format for the performance management module is provided below. module: o-ran-performance-management +--rw performance-measurement-objects +--ro measurement-capabilitites | +--ro transceiver-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/transceiver-measurement- objects/measurement-object | | +--ro report-info* transceiver-report-info | | +--ro function* transceiver-function | | +--ro max-bin-count? uint16 | +--ro rx-window-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/rx-window-measurement- objects/measurement-object | +--ro tx-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/tx-measurement- objects/measurement-object | +--ro shared-cell-stats-objects* [measurement-object] {feat:SHARED-CELL-STATS}? | | +--ro measurement-object -> /performance-measurement-objects/shared-cell-measurement- objects/measurement-object | +--ro epe-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/epe-measurement- objects/measurement-object | | +--ro component-class* identityref | | +--ro report-info* epe-report-info | | +--ro max-bin-count? uint16 | +--ro symbol-rssi-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/symbol-rssi-measurement- objects/measurement-object | | +--ro report-info* symbol-rssi-report-info | | +--ro max-bin-count? uint16 | +--ro tssi-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/tssi-measurement- objects/measurement-object | | +--ro report-info* tssi-report-info | +--ro rssi-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/rssi-measurement- objects/measurement-object | | +--ro report-info* rssi-report-info | +--ro tx-antenna-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/tx-antenna-measurement- objects/measurement-object | | +--ro object-unit* tx-antenna-object-unit | | +--ro report-info* tx-antenna-report-info | | +--ro max-bin-count? uint16 | +--ro tx-output-power-stats-objects* [measurement-object] | | +--ro measurement-object -> /performance-measurement-objects/tx-output-power- measurement-objects/measurement-object | | +--ro report-info* tx-output-power-report-info | +--ro ethernet-objects* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/ethernet-measurement- objects/measurement-object x--rw enable-SFTP-upload? boolean +--rw enable-file-upload? boolean +--rw enable-random-file-upload? boolean x--rw remote-SFTP-uploads* [remote-SFTP-upload-path] | +--rw remote-SFTP-upload-path inet:uri | +--rw (credentials)? | | +--:(password) | | | +--rw password! | | | | +--rw password string | | | +--rw server | | | +--rw keys* [algorithm] | | | +--rw algorithm asymmetric-key-algorithm-ref | | | +--rw public-key? binary | | +--:(certificate) | | +--rw certificate! | +--rw application-layer-credential | +--rw appl-password? string +--rw remote-file-uploads* [remote-file-upload-path] | +--rw remote-file-upload-path inet:uri | +--rw (credentials)? | | +--:(password) | | | +--rw password! | | | | +--rw password string ETSI ETSI TS 104 023 V17.1.0 (2026-01) 297 | | | +--rw server | | | +--rw keys* [algorithm] | | | +--rw algorithm asymmetric-key-algorithm-ref | | | +--rw public-key? binary | | +--:(certificate) | | +--rw certificate! | +--rw application-layer-credential | +--rw appl-password? string +--rw transceiver-measurement-interval? uint16 +--rw epe-measurement-interval? uint16 +--rw rx-window-measurement-interval? uint16 +--rw tx-measurement-interval? uint16 +--rw shared-cell-measurement-interval? uint16 {feat:SHARED-CELL-STATS}? +--rw symbol-rssi-measurement-interval? uint16 +--rw tssi-measurement-interval? uint16 +--rw rssi-measurement-interval? uint16 +--rw tx-antenna-measurement-interval? uint16 +--rw tx-output-power-measurement-interval? uint16 +--rw ethernet-measurement-interval? uint16 +--rw notification-interval? uint16 +--rw file-upload-interval? uint16 x--ro max-bin-count? uint16 +--rw transceiver-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw report-info* transceiver-report-info | +--rw object-unit enumeration | +--rw function? transceiver-function | +--rw bin-count? uint16 | +--rw lower-bound? decimal64 | +--rw upper-bound? decimal64 | +--ro transceiver-measurement-result* [object-unit-id] | +--ro object-unit-id -> /if:interfaces/interface/o-ran-int:port-reference/port- number | +--ro min | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro max | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro first | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro latest | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | x--ro frequeny-table* uint32 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--rw rx-window-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit? enumeration | +--rw report-info? enumeration | +--ro (object-unit-id)? | +--:(RU) | | +--ro name? -> /hw:hardware/component/name | | +--ro count uint64 | +--:(TRANSPORT) | | +--ro tr-measured-result* [] | | +--ro name? -> /o-ran-elements:processing-elements/ru- elements/name | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | | +--ro count uint64 | +--:(EAXC_ID) | +--ro eaxc-measured-result* [] | +--ro eaxc-id? uint16 | +--ro count uint64 | +--ro data-direction? enumeration | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- elements/name | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? ETSI ETSI TS 104 023 V17.1.0 (2026-01) 298 | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? +--rw tx-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit? enumeration | +--rw report-info? enumeration | +--ro (object-unit-id)? | +--:(RU) | | +--ro name? -> /hw:hardware/component/name | | +--ro count uint64 | +--:(TRANSPORT) | | +--ro tr-measured-result* [] | | +--ro name? -> /o-ran-elements:processing-elements/ru- elements/name | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | | +--ro count uint64 | +--:(EAXC_ID) | +--ro eaxc-measured-result* [] | +--ro eaxc-id? uint16 | +--ro count uint64 | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- elements/name | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? +--rw shared-cell-measurement-objects* [measurement-object] {feat:SHARED-CELL-STATS}? | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit? enumeration | +--rw report-info? enumeration | +--ro (object-unit-id)? | +--:(TRANSPORT) | +--ro pe-measured-result* [processing-elements] | +--ro processing-elements -> /o-ran-elements:processing-elements/ru- elements/name | +--ro count uint64 +--rw epe-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit? -> /hw:hardware/component/class | +--rw report-info* epe-report-info | +--rw bin-count? uint16 | +--rw lower-bound? decimal64 | +--rw upper-bound? decimal64 | x--ro epe-measurement-result* [object-unit-id] | | +--ro object-unit-id -> /hw:hardware/component/class | | +--ro min? decimal64 | | +--ro max? decimal64 | | +--ro average? decimal64 | +--ro epe-measurement-resultv2* [object-unit-id] | +--ro object-unit-id -> /hw:hardware/component/name | +--ro min? decimal64 | +--ro max? decimal64 | +--ro average? decimal64 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--rw symbol-rssi-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw object-unit enumeration | +--rw per-rx-array-carrier-configuration* [rx-array-carrier] | | +--rw rx-array-carrier -> /up:user-plane-configuration/rx-array-carriers/name | | +--rw period? uint16 | | +--rw symbol-index* uint16 | | +--rw active? boolean | | +--rw report-info* symbol-rssi-report-info | | +--rw bin-count? uint16 | | +--rw lower-bound? int16 | | +--rw upper-bound? int16 | +--ro symbol-rssi-measurement-result* [object-unit-id] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 299 | +--ro object-unit-id -> /up:user-plane-configuration/rx-array-carriers/name | +--ro per-symbol-index-result* [symbol-index] | +--ro symbol-index uint16 | +--ro min | | +--ro value? decimal64 | +--ro max | | +--ro value? decimal64 | +--ro avg | | +--ro value? decimal64 | x--ro frequency-table* uint32 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--rw tssi-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit enumeration | +--rw report-info* tssi-report-info | +--ro tssi-measurement-result* [object-unit-id] | +--ro object-unit-id -> /up:user-plane-configuration/tx-array- carriers/name | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name | +--ro tx-array-element uint32 | +--ro avg | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | +--ro max | +--ro value? decimal64 +--rw rssi-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit enumeration | +--rw report-info* rssi-report-info | +--ro rssi-measurement-result* [object-unit-id] | +--ro object-unit-id -> /up:user-plane-configuration/rx-array- carriers/name | +--ro per-rx-array-element-index-result* [rx-array rx-array-element] | +--ro rx-array -> /up:user-plane-configuration/rx-arrays/name | +--ro rx-array-element uint32 | +--ro avg | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | +--ro max | +--ro value? decimal64 +--rw tx-antenna-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw report-info* tx-antenna-report-info | +--rw object-unit tx-antenna-object-unit | +--rw bin-count? uint16 | +--rw lower-bound? decimal64 | +--rw upper-bound? decimal64 | +--ro (object-unit-id)? | +--:(ARRAY_ELEMENT) | | +--ro tx-antenna-measurement-result-array-element* [tx-array tx-array-element] | | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name | | +--ro tx-array-element uint32 | | +--ro avg | | | +--ro value? decimal64 | | +--ro std-deviation | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro max | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro first | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro latest | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro frequency-bin-table* [bin-id] | | +--ro bin-id uint32 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 300 | | +--ro value? uint32 | +--:(CONNECTOR_BAND) | +--ro tx-antenna-measurement-result-connector-band* [related-o-ru-connector band- number] | +--ro related-o-ru-connector -> /hw:hardware/component/name | +--ro band-number -> /mcap:module-capability/band-capabilities/band- number | +--ro avg | | +--ro value? decimal64 | +--ro std-deviation | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro max | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro first | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro latest | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--rw tx-output-power-measurement-objects* [measurement-object] | +--rw measurement-object enumeration | +--rw active? boolean | +--rw object-unit tx-output-power- object-unit | +--rw report-info* tx-output-power- report-info | +--ro (object-unit-id)? | +--:(TX-ARRAY-CARRIER) | | +--ro tx-output-power-measurement-result-tx-array-carrier* [tx-array-carrier] | | +--ro tx-array-carrier -> /up:user-plane-configuration/tx-array-carriers/name | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(TX-ARRAY-ELEMENT) | | +--ro tx-output-power-measurement-result-tx-array-element* [tx-array] | | +--ro tx-array -> /up:user-plane-configuration/tx- arrays/name | | +--ro per-tx-array-element-index-result* [tx-array-element] | | +--ro tx-array-element uint32 | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(CONNECTOR) | | +--ro tx-output-power-measurement-result-connector* [related-o-ru-connector] | | +--ro related-o-ru-connector -> /hw:hardware/component/name | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(CARRIER-ARRAY-ELEMENT) | | +--ro tx-output-power-measurement-result-carrier-array-element* [tx-array-carrier] | | +--ro tx-array-carrier -> /up:user-plane-configuration/tx- array-carriers/name | | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] | | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name | | +--ro tx-array-element uint32 | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(ARRAY-CARRIER-CONNECTOR) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 301 | +--ro tx-output-power-measurement-result-carrier-connector* [tx-array-carrier] | +--ro tx-array-carrier -> /up:user-plane-configuration/tx- array-carriers/name | +--ro per-tx-array-connector-index-result* [related-o-ru-connector] | +--ro related-o-ru-connector -> /hw:hardware/component/name | +--ro avg | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | +--ro max | +--ro value? decimal64 +--rw ethernet-measurement-objects* [measurement-object] +--rw measurement-object enumeration +--rw active? boolean +--rw report-info* ethernet-report-info +--rw object-unit enumeration +--ro ethernet-measurement-result* [object-unit-id] +--ro object-unit-id -> /if:interfaces/interface/name +--ro count? uint64 notifications: +---n measurement-result-stats +--ro transceiver-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement- objects/transceiver-measurement-objects/measurement-object | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro transceiver-measurement-result* [object-unit-id] | | +--ro object-unit-id -> /if:interfaces/interface/o-ran-int:port-reference/port- number | | +--ro min | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro max | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro first | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro latest | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | x--ro frequeny-table* uint32 | | +--ro frequency-bin-table* [bin-id] | | +--ro bin-id uint32 | | +--ro value? uint32 | +--ro multiple-transceiver-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro transceiver-measurement-result* [object-unit-id] | +--ro object-unit-id -> /if:interfaces/interface/o-ran-int:port- reference/port-number | +--ro min | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro max | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro first | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro latest | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | x--ro frequeny-table* uint32 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--ro rx-window-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/rx- window-measurement-objects/measurement-object | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro (object-unit-id)? | | +--:(RU) | | | +--ro name? -> /hw:hardware/component/name | | | +--ro count uint64 | | +--:(TRANSPORT) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 302 | | | +--ro tr-measured-result* [] | | | +--ro name? -> /o-ran-elements:processing-elements/ru- elements/name | | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? | | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | | | +--ro count uint64 | | +--:(EAXC_ID) | | +--ro eaxc-measured-result* [] | | +--ro eaxc-id? uint16 | | +--ro count uint64 | | +--ro data-direction? enumeration | | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- elements/name | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | +--ro multiple-rx-window-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro (object-unit-id)? | +--:(RU) | | +--ro name? -> /hw:hardware/component/name | | +--ro count uint64 | +--:(TRANSPORT) | | +--ro tr-measured-result* [] | | +--ro name? -> /o-ran-elements:processing-elements/ru- elements/name | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- SESSION-TYPE}? | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | | +--ro count uint64 | +--:(EAXC_ID) | +--ro eaxc-measured-result* [] | +--ro eaxc-id? uint16 | +--ro count uint64 | +--ro data-direction? enumeration | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- elements/name | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- SESSION-TYPE}? | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? +--ro tx-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/tx- measurement-objects/measurement-object | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro (object-unit-id)? | | +--:(RU) | | | +--ro name? -> /hw:hardware/component/name | | | +--ro count uint64 | | +--:(TRANSPORT) | | | +--ro tr-measured-result* [] | | | +--ro name? -> /o-ran-elements:processing-elements/ru- elements/name | | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? | | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | | | +--ro count uint64 | | +--:(EAXC_ID) | | +--ro eaxc-measured-result* [] | | +--ro eaxc-id? uint16 | | +--ro count uint64 | | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- elements/name | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- TYPE}? ETSI ETSI TS 104 023 V17.1.0 (2026-01) 303 | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | +--ro multiple-tx-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro (object-unit-id)? | +--:(RU) | | +--ro name? -> /hw:hardware/component/name | | +--ro count uint64 | +--:(TRANSPORT) | | +--ro tr-measured-result* [] | | +--ro name? -> /o-ran-elements:processing-elements/ru- elements/name | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- SESSION-TYPE}? | | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | | +--ro count uint64 | +--:(EAXC_ID) | +--ro eaxc-measured-result* [] | +--ro eaxc-id? uint16 | +--ro count uint64 | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- elements/name | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- SESSION-TYPE}? | +--ro transport-qualified-name? -> /o-ran-elements:processing- elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? +--ro shared-cell-stats* [measurement-object] {feat:SHARED-CELL-STATS}? | +--ro measurement-object -> /performance-measurement- objects/shared-cell-measurement-objects/measurement-object | +--ro multiple-shared-cell-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro (object-unit-id)? | +--:(TRANSPORT) | +--ro pe-measured-result* [processing-elements] | +--ro processing-elements -> /o-ran-elements:processing-elements/ru- elements/name | +--ro count uint64 x--ro epe-stats | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | x--ro epe-measurement-result* [object-unit-id] | | +--ro object-unit-id -> /hw:hardware/component/class | | +--ro min? decimal64 | | +--ro max? decimal64 | | +--ro average? decimal64 | +--ro epe-measurement-resultv2* [object-unit-id] | +--ro object-unit-id -> /hw:hardware/component/name | +--ro min? decimal64 | +--ro max? decimal64 | +--ro average? decimal64 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--ro epe-statistics* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/epe- measurement-objects/measurement-object | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | x--ro epe-measurement-result* [object-unit-id] | | +--ro object-unit-id -> /hw:hardware/component/class | | +--ro min? decimal64 | | +--ro max? decimal64 | | +--ro average? decimal64 | +--ro epe-measurement-resultv2* [object-unit-id] | | +--ro object-unit-id -> /hw:hardware/component/name | | +--ro min? decimal64 | | +--ro max? decimal64 | | +--ro average? decimal64 | | +--ro frequency-bin-table* [bin-id] | | +--ro bin-id uint32 | | +--ro value? uint32 | +--ro multiple-epe-measurement-result* [] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 304 | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | x--ro epe-measurement-result* [object-unit-id] | | +--ro object-unit-id -> /hw:hardware/component/class | | +--ro min? decimal64 | | +--ro max? decimal64 | | +--ro average? decimal64 | +--ro epe-measurement-resultv2* [object-unit-id] | +--ro object-unit-id -> /hw:hardware/component/name | +--ro min? decimal64 | +--ro max? decimal64 | +--ro average? decimal64 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--ro symbol-rssi-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement- objects/symbol-rssi-measurement-objects/measurement-object | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro symbol-rssi-measurement-result* [object-unit-id] | | +--ro object-unit-id -> /up:user-plane-configuration/rx-array-carriers/name | | +--ro per-symbol-index-result* [symbol-index] | | +--ro symbol-index uint16 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | | +--ro value? decimal64 | | +--ro avg | | | +--ro value? decimal64 | | x--ro frequency-table* uint32 | | +--ro frequency-bin-table* [bin-id] | | +--ro bin-id uint32 | | +--ro value? uint32 | +--ro multiple-symbol-rssi-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro symbol-rssi-measurement-result* [object-unit-id] | +--ro object-unit-id -> /up:user-plane-configuration/rx-array- carriers/name | +--ro per-symbol-index-result* [symbol-index] | +--ro symbol-index uint16 | +--ro min | | +--ro value? decimal64 | +--ro max | | +--ro value? decimal64 | +--ro avg | | +--ro value? decimal64 | x--ro frequency-table* uint32 | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--ro tssi-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/tssi-measurement- objects/measurement-object | +--ro tssi-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro tssi-measurement-result* [object-unit-id] | +--ro object-unit-id -> /up:user-plane-configuration/tx-array- carriers/name | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name | +--ro tx-array-element uint32 | +--ro avg | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | +--ro max | +--ro value? decimal64 +--ro rssi-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/rssi-measurement- objects/measurement-object | +--ro rssi-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro rssi-measurement-result* [object-unit-id] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 305 | +--ro object-unit-id -> /up:user-plane-configuration/rx-array- carriers/name | +--ro per-rx-array-element-index-result* [rx-array rx-array-element] | +--ro rx-array -> /up:user-plane-configuration/rx-arrays/name | +--ro rx-array-element uint32 | +--ro avg | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | +--ro max | +--ro value? decimal64 +--ro tx-antenna-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/tx-antenna- measurement-objects/measurement-object | +--ro tx-antenna-measurement-result* [] | +--ro start-time? yang-types:date-and-time | +--ro end-time? yang-types:date-and-time | +--ro (object-unit-id)? | +--:(ARRAY_ELEMENT) | | +--ro tx-antenna-measurement-result-array-element* [tx-array tx-array-element] | | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name | | +--ro tx-array-element uint32 | | +--ro avg | | | +--ro value? decimal64 | | +--ro std-deviation | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro max | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro first | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro latest | | | +--ro value? decimal64 | | | +--ro time? yang-types:date-and-time | | +--ro frequency-bin-table* [bin-id] | | +--ro bin-id uint32 | | +--ro value? uint32 | +--:(CONNECTOR_BAND) | +--ro tx-antenna-measurement-result-connector-band* [related-o-ru-connector band- number] | +--ro related-o-ru-connector -> /hw:hardware/component/name | +--ro band-number -> /mcap:module-capability/band- capabilities/band-number | +--ro avg | | +--ro value? decimal64 | +--ro std-deviation | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro max | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro first | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro latest | | +--ro value? decimal64 | | +--ro time? yang-types:date-and-time | +--ro frequency-bin-table* [bin-id] | +--ro bin-id uint32 | +--ro value? uint32 +--ro tx-output-power-stats* [measurement-object] | +--ro measurement-object -> /performance-measurement-objects/tx-output- power-measurement-objects/measurement-object | +--ro tx-output-power-measurement-result* [] | +--ro start-time? yang- types:date-and-time | +--ro end-time? yang- types:date-and-time | +--ro (object-unit-id)? | +--:(TX-ARRAY-CARRIER) | | +--ro tx-output-power-measurement-result-tx-array-carrier* [tx-array-carrier] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 306 | | +--ro tx-array-carrier -> /up:user-plane-configuration/tx-array- carriers/name | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(TX-ARRAY-ELEMENT) | | +--ro tx-output-power-measurement-result-tx-array-element* [tx-array] | | +--ro tx-array -> /up:user-plane-configuration/tx- arrays/name | | +--ro per-tx-array-element-index-result* [tx-array-element] | | +--ro tx-array-element uint32 | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(CONNECTOR) | | +--ro tx-output-power-measurement-result-connector* [related-o-ru-connector] | | +--ro related-o-ru-connector -> /hw:hardware/component/name | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(CARRIER-ARRAY-ELEMENT) | | +--ro tx-output-power-measurement-result-carrier-array-element* [tx-array- carrier] | | +--ro tx-array-carrier -> /up:user-plane-configuration/tx- array-carriers/name | | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] | | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name | | +--ro tx-array-element uint32 | | +--ro avg | | | +--ro value? decimal64 | | +--ro min | | | +--ro value? decimal64 | | +--ro max | | +--ro value? decimal64 | +--:(ARRAY-CARRIER-CONNECTOR) | +--ro tx-output-power-measurement-result-carrier-connector* [tx-array-carrier] | +--ro tx-array-carrier -> /up:user-plane- configuration/tx-array-carriers/name | +--ro per-tx-array-connector-index-result* [related-o-ru-connector] | +--ro related-o-ru-connector -> /hw:hardware/component/name | +--ro avg | | +--ro value? decimal64 | +--ro min | | +--ro value? decimal64 | +--ro max | +--ro value? decimal64 +--ro ethernet-stats* [measurement-object] +--ro measurement-object -> /performance-measurement-objects/ethernet- measurement-objects/measurement-object +--ro ethernet-measurement-results* [] +--ro start-time? yang-types:date-and-time +--ro end-time? yang-types:date-and-time +--ro ethernet-measurement-result* [object-unit-id] +--ro object-unit-id -> /if:interfaces/interface/name +--ro count? uint64 D.3.8 o-ran-uplane-conf.yang module The format for the userplane configuration module is provided below. module: o-ran-uplane-conf +--rw user-plane-configuration +--rw low-level-tx-links* [name] | +--rw name string | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED- ORU-MULTI-OPERATOR}? ETSI ETSI TS 104 023 V17.1.0 (2026-01) 307 | +--rw processing-element -> /o-ran-pe:processing-elements/ru- elements/name | +--rw transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- SESSION-TYPE}? | +--rw transport-qualified-processing-element? -> /o-ran-pe:processing-elements/additional- transport-session-type-elements[o-ran-pe:transport-session-type = current()/../transport-session- type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | +--rw tx-array-carrier -> /user-plane-configuration/tx-array- carriers/name | +--rw low-level-tx-endpoint -> /user-plane-configuration/low-level-tx- endpoints/name +--rw low-level-rx-links* [name] | +--rw name string | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED- ORU-MULTI-OPERATOR}? | +--rw processing-element -> /o-ran-pe:processing-elements/ru- elements/name | +--rw transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- SESSION-TYPE}? | +--rw transport-qualified-processing-element? -> /o-ran-pe:processing-elements/additional- transport-session-type-elements[o-ran-pe:transport-session-type = current()/../transport-session- type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? | +--rw rx-array-carrier -> /user-plane-configuration/rx-array- carriers/name | +--rw low-level-rx-endpoint -> /user-plane-configuration/low-level-rx- endpoints/name | +--rw user-plane-uplink-marking? -> /o-ran-pe:processing-elements/enhanced- uplane-mapping/uplane-mapping/up-marking-name | +--rw enhanced-user-plane-uplink-marking? -> /o-ran-pe:processing-elements/additional- transport-session-type-elements[o-ran-pe:transport-session-type = current()/../transport-session- type]/enhanced-uplane-mapping/uplane-mapping/up-marking-name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? +--ro endpoint-types* [id] | +--ro id uint16 | +--ro supported-section-types* [section-type] | | +--ro section-type uint8 | | +--ro supported-section-extensions* uint8 | +--ro st4-supported-commands* [st4-command-type] {feat:ST4-SLOT-CONFIG-MSG-SUPPORT}? | | +--ro st4-command-type enumeration | | +--ro st4-command-scope-params* [cmd-scope] | | +--ro cmd-scope enumeration | | +--ro st4-reception-bitmask? uint16 | x--ro st4-reception-mask* [cmd-scope] {feat:ST4-SLOT-CONFIG-MSG-SUPPORT}? | | +--ro cmd-scope enumeration | | +--ro st4-reception-bitmask? uint16 | +--ro supported-frame-structures* uint8 | +--ro managed-delay-support? enumeration | +--ro multiple-numerology-supported? boolean | +--ro max-numerology-change-duration? uint16 | +--ro max-control-sections-per-data-section? uint8 | +--ro max-sections-per-symbol? uint16 | +--ro max-sections-per-slot? uint16 | +--ro max-highest-priority-sections-per-slot? uint16 | x--ro max-remasks-per-section-id? uint8 | +--ro max-uplane-section-header-per-symbol? uint16 | +--ro max-uplane-section-header-per-slot? uint16 | +--ro max-beams-per-symbol? uint16 | +--ro max-beams-per-slot? uint16 | +--ro max-total-beamids-per-symbol? uint16 | +--ro max-total-beamids-per-slot? uint16 | +--ro max-beams-per-symbol-multiple-beamid-tables? uint32 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? | +--ro max-beams-per-slot-multiple-beamid-tables? uint32 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? | +--ro max-total-beamids-per-symbol-multiple-beamid-tables? uint32 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? | +--ro max-total-beamids-per-slot-multiple-beamid-tables? uint32 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? | +--ro max-beam-updates-per-slot? uint16 | +--ro max-beam-updates-per-symbol? uint16 | +--ro max-prb-per-symbol? uint16 | +--ro max-prb-ranges-per-symbol? uint32 | +--ro max-mcscaleremask-per-prb? uint16 | +--ro max-prb-ranges-per-sec-ext-12? uint16 | +--ro max-freq-hops-per-sec-ext-13? uint16 | +--ro max-prb-blks-per-sec-ext-23? uint16 {feat:SE23- PRB-BLOCK-MODE-SUPPORT}? | +--ro prb-capacity-allocation-granularity* uint16 | +--ro max-numerologies-per-symbol? uint16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 308 | +--ro static-transmission-window-control-supported? boolean {feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? | +--ro uniformly-distributed-transmission-supported? boolean {feat:STATIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION}? | +--ro ordered-transmission-supported? boolean {feat:ORDERED-TRANSMISSION}? | +--ro dynamic-transmission-window-control-supported? boolean {feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? | +--ro dynamic-transmission-window-control-per-section-supported? boolean {feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? | +--ro dynamic-uniformly-distributed-transmission-supported? boolean {feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION}? | +--ro dynamic-uniformly-distributed-transmission-per-section-supported? boolean | +--ro transmission-buffering-capacity* [] {feat:STATIC-TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? | | +--ro iq-bitwidth? uint8 | | +--ro compression-type compression-type-def | | x--ro bitwidth? uint8 | | +--ro compression-method? compression-method-def | | x--ro (compression-format)? | | | +--:(no-compresison) | | | +--:(block-floating-point) | | | | +--ro exponent? uint8 | | | +--:(block-floating-point-selective-re-sending) | | | | +--ro sres-exponent? uint8 | | | +--:(block-scaling) | | | | +--ro block-scalar? uint8 | | | +--:(u-law) | | | | +--ro comp-bit-width? uint8 | | | | +--ro comp-shift? uint8 | | | +--:(beam-space-compression) | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | +--ro block-scaler? uint8 | | | +--:(modulation-compression) | | | | +--ro csf? uint8 | | | | +--ro mod-comp-scaler? uint16 | | | +--:(modulation-compression-selective-re-sending) | | | +--ro sres-csf? uint8 | | | +--ro sres-mod-comp-scaler? uint16 | | +--ro max-buffered-prbs? uint32 | | +--ro max-buffered-symbols? uint32 | +--ro cplane-message-processing-limits-required? boolean {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-beams-per-cplane-message? uint16 {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-highest-priority-sec-per-cplane-message? uint16 {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-beams-per-slot-with-cplane-limits? uint16 {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-highest-priority-sections-per-slot-with-cplane-limits? uint16 {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-num-se22-per-cplane-message? uint16 {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-prb-ranges-per-hp-section-sec-ext-12? uint16 {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro uplane-message-processing-limits-required? boolean {feat:UPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro max-section-headers-per-uplane-message? uint16 {feat:UPLANE-MESSAGE-PROCESSING-LIMITS,feat:UPLANE-MESSAGE-PROCESSING-LIMITS}? | +--ro beam-update-contention-control-limits-required? boolean {feat:BEAM-UPDATE-CONTENTION-CONTROL}? | +--ro max-beams-per-symbol-with-beam-contention-control? uint16 {feat:BEAM- UPDATE-CONTENTION-CONTROL}? | +--ro max-beams-updates-per-symbol-with-beam-contention-control? uint16 {feat:BEAM- UPDATE-CONTENTION-CONTROL}? | +--ro max-ack-nack-per-symbol? uint16 | +--ro non-scheduled-ueid-supported? boolean {feat:NON- SCHEDULED-UEID}? | +--ro se-11-continuity-flag-supported? boolean {feat:SE11-WITH-CONTINUITY-BIT-SUPPORT}? | +--ro se-23-prb-block-mode-supported? boolean {feat:SE23-PRB-BLOCK-MODE-SUPPORT}? | +--ro user-group-optimization-supported? boolean {feat:USER-GROUP-OPTIMIZATION}? | +--ro se-20-multi-sd-punc-pattern-suported? boolean {feat:SE20-MULTI-SD-PUNC-PATTERN-SUPPORT}? | +--ro supported-configuration-combinations* [combination-id] | | +--ro combination-id uint32 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 309 | | +--ro set* [set-id] | | +--ro set-id uint32 | | +--ro max-overlapping-instances? uint32 | | +--ro config* [config-id] | | +--ro config-id uint32 | | +--ro scs* mcap:scs-config-type | | +--ro carrier-types* enumeration | | +--ro filter-pass-bandwidth? uint64 | | +--ro max-prb-range? uint32 | | +--ro center-from-freqoffset? boolean | | +--ro supported-filter-indices* uint32 | +--ro center-from-freqoffset-supported? boolean | +--ro supported-filter-indices* uint32 | +--ro bf-profile-group* -> /user-plane- configuration/endpoint-bf-profile-group/bf-profile-id {feat:BF-DELAY-PROFILE}? | +--ro supported-pass-band-for-filterindex09-per-scs* [scs] | | +--ro scs mcap:scs-config-type | | +--ro supported-max-num-msg-for-filterindex0x9-per-scs? uint16 | | +--ro filter-bandwidth* uint64 | +--ro se24-dmrs-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | | +--ro supported-entry-types* uint8 | | +--ro ue-time-partial-overlap-supported? boolean | | +--ro ue-freq-partial-overlap-supported? boolean | | +--ro max-user-groups-per-ue-in-time? uint16 | | +--ro different-transform-precoding-in-user-group-supported? boolean | | +--ro different-cdm-without-data-in-user-group-supported? boolean | | +--ro max-dmrs-configs-per-user-group-incl-first-last-prb? uint32 | | +--ro max-dmrs-configs-per-user-group-excl-first-last-prb? uint32 | | +--ro max-user-groups-per-slot? uint32 | | +--ro max-entries-per-slot? uint32 | | +--ro transform-precoding-enabled | | | +--ro dmrs-mask-capability* [id] | | | | +--ro id uint16 | | | | +--ro dmrs-symbol-mask* uint16 | | | | +--ro max-dmrs-ant-port-number? uint32 | | | | +--ro max-user-data-layers? uint32 | | | +--ro low-papr-config* [id] | | | +--ro id uint16 | | | +--ro low-papr-type? uint16 | | | +--ro hopping-mode? uint16 | | +--ro transform-precoding-disabled | | +--ro dmrs-mask-capability* [id] | | | +--ro id uint16 | | | +--ro dmrs-symbol-mask* uint16 | | | +--ro max-dmrs-ant-port-number? uint32 | | | +--ro max-user-data-layers? uint32 | | +--ro dmrs-config* [id] | | +--ro id uint16 | | +--ro d-type? uint16 | | +--ro pusch-dmrs-muxing-supported? boolean | +--ro sinr-reporting-supported? boolean {feat:DMRS-BF-EQ}? | +--ro sinr-reporting-capabilities {feat:DMRS-BF-EQ}? | | +--ro simultaneous-sinr-and-dmrs-sending-supported? boolean | | +--ro oru-control-sinr-time-resolution-supported? boolean {feat:ORU-CONTROL-SINR- TIME-RESOLUTION}? | | +--ro supported-sinr-resolutions* [id] | | | +--ro id uint16 | | | +--ro sinr-max-data-layers? uint8 | | | +--ro sinr-per-prb* uint8 | | | +--ro sinr-slot-mask* uint16 | | +--ro supported-sinr-reference-level | | | +--ro sinr-reference-level-min? decimal64 | | | +--ro sinr-reference-level-max? decimal64 | | +--ro supported-sinr-compression-methods* [id] | | | +--ro id uint16 | | | +--ro sinr-bitwidth? uint8 | | | +--ro sinr-compression-method? sinr-compression-method-def | | | +--ro sinr-block-size? uint8 | | +--ro dynamic-sinr-per-prb-supported? boolean {feat:DYNAMIC-SINR-PER- PRB}? | | +--ro diff-freq-resolutions-supported? boolean {feat:DYNAMIC-SINR-PER- PRB}? | +--ro supported-symb-reorder-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | | +--ro supported-symb-reorder-capability* symb-reorder-capability | | +--ro max-num-symbol-reordering-pattern-per-slot? uint16 | | +--ro up-symbolId-type-supported* up-SymbolId-type ETSI ETSI TS 104 023 V17.1.0 (2026-01) 310 | +--ro supported-user-group-self-assembly-modes* user-group-self- assembly-mode {feat:USER-GROUP-SELF-ASSEMBLY}? | +--ro continuity-block-sizes-supported* uint16 {(feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ) and feat:CONTINUITY-BLOCK-SIZE}? | +--ro eq-scale-offset-min? decimal64 {feat:DMRS-BF-EQ}? | +--ro eq-scale-offset-max? decimal64 {feat:DMRS-BF-EQ}? | +--ro rrm-meas-supported* rrm-meas-types {feat:RRM-MEAS-REPORTING}? | +--ro max-ipn-unalloc-reports-supported? uint16 {feat:RRM- MEAS-REPORTING}? | +--ro max-ipn-unalloc-symbols-supported? uint16 {feat:RRM- MEAS-REPORTING}? | +--ro max-ipn-alloc-reports-supported? uint16 {feat:RRM- MEAS-REPORTING}? | +--ro alloc-ipn-per-dmrs-sym-grp-supported* uint8 {feat:RRM- MEAS-REPORTING}? | +--ro se-10-bgt-11b-supported? boolean | +--ro se-27-odu-controlled-dimensionality-reduction-supported* enumeration {feat:SE27-ODU-CONTROLLED-DIMENSIONALITY-REDUCTION}? | +--ro se-27-omission-when-enabled-supported? boolean {feat:SE27-ODU-CONTROLLED-DIMENSIONALITY-REDUCTION}? | +--ro supported-se-27-configurations* [number-of-ue-data-layers] {feat:SE27-ODU-CONTROLLED- DIMENSIONALITY-REDUCTION}? | +--ro number-of-ue-data-layers uint16 | +--ro supported-se-27-num-elements* uint16 +--rw transmission-window-schedules* [id] {feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? | +--rw id uint16 | +--rw schedule* [symbol] | +--rw symbol uint16 | +--rw offset? uint16 +--ro endpoint-capacity-sharing-groups* [id] | +--ro id uint16 | +--ro max-control-sections-per-data-section? uint8 | +--ro max-sections-per-symbol? uint16 | +--ro max-sections-per-slot? uint16 | +--ro max-highest-priority-sections-per-slot? uint16 | x--ro max-remasks-per-section-id? uint8 | +--ro max-uplane-section-header-per-symbol? uint16 | +--ro max-uplane-section-header-per-slot? uint16 | +--ro max-beams-per-symbol? uint16 | +--ro max-beams-per-slot? uint16 | +--ro max-total-beamids-per-symbol? uint16 | +--ro max-total-beamids-per-slot? uint16 | +--ro max-beams-per-symbol-multiple-beamid-tables? uint32 {feat:MULTIPLE- BEAMID-TABLES-SUPPORTED}? | +--ro max-beams-per-slot-multiple-beamid-tables? uint32 {feat:MULTIPLE- BEAMID-TABLES-SUPPORTED}? | +--ro max-total-beamids-per-symbol-multiple-beamid-tables? uint32 {feat:MULTIPLE- BEAMID-TABLES-SUPPORTED}? | +--ro max-total-beamids-per-slot-multiple-beamid-tables? uint32 {feat:MULTIPLE- BEAMID-TABLES-SUPPORTED}? | +--ro max-beam-updates-per-slot? uint16 | +--ro max-beam-updates-per-symbol? uint16 | +--ro max-prb-per-symbol? uint16 | +--ro max-prb-ranges-per-symbol? uint32 | +--ro max-numerologies-per-symbol? uint16 | +--ro max-mcscaleremask-per-prb? uint16 | +--ro max-prb-ranges-per-sec-ext-12? uint16 | +--ro max-freq-hops-per-sec-ext-13? uint16 | +--ro max-prb-blks-per-sec-ext-23? uint16 {feat:SE23-PRB- BLOCK-MODE-SUPPORT}? | +--ro max-endpoints? uint16 | +--ro max-managed-delay-endpoints? uint16 | +--ro max-non-managed-delay-endpoints? uint16 | +--ro transmission-buffering-capacity* [] {feat:STATIC-TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? | | +--ro iq-bitwidth? uint8 | | +--ro compression-type compression-type-def | | x--ro bitwidth? uint8 | | +--ro compression-method? compression-method-def | | x--ro (compression-format)? | | | +--:(no-compresison) | | | +--:(block-floating-point) | | | | +--ro exponent? uint8 | | | +--:(block-floating-point-selective-re-sending) | | | | +--ro sres-exponent? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 311 | | | +--:(block-scaling) | | | | +--ro block-scalar? uint8 | | | +--:(u-law) | | | | +--ro comp-bit-width? uint8 | | | | +--ro comp-shift? uint8 | | | +--:(beam-space-compression) | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | +--ro block-scaler? uint8 | | | +--:(modulation-compression) | | | | +--ro csf? uint8 | | | | +--ro mod-comp-scaler? uint16 | | | +--:(modulation-compression-selective-re-sending) | | | +--ro sres-csf? uint8 | | | +--ro sres-mod-comp-scaler? uint16 | | +--ro max-buffered-prbs? uint32 | | +--ro max-buffered-symbols? uint32 | +--ro max-beams-per-cplane-message? uint16 {feat:CPLANE- MESSAGE-PROCESSING-LIMITS}? | +--ro max-highest-priority-sec-per-cplane-message? uint16 {feat:CPLANE- MESSAGE-PROCESSING-LIMITS}? | +--ro max-beams-per-slot-with-cplane-limits? uint16 {feat:CPLANE- MESSAGE-PROCESSING-LIMITS}? | +--ro max-highest-priority-sections-per-slot-with-cplane-limits? uint16 {feat:CPLANE- MESSAGE-PROCESSING-LIMITS}? | +--ro max-num-se22-per-cplane-message? uint16 {feat:CPLANE- MESSAGE-PROCESSING-LIMITS}? | +--ro max-prb-ranges-per-hp-section-sec-ext-12? uint16 {feat:CPLANE- MESSAGE-PROCESSING-LIMITS}? | +--ro max-ack-nack-per-symbol? uint16 | +--ro supported-configuration-combinations* [combination-id] | | +--ro combination-id uint32 | | +--ro set* [set-id] | | +--ro set-id uint32 | | +--ro max-overlapping-instances? uint32 | | +--ro config* [config-id] | | +--ro config-id uint32 | | +--ro scs* mcap:scs-config-type | | +--ro carrier-types* enumeration | | +--ro filter-pass-bandwidth? uint64 | | +--ro max-prb-range? uint32 | | +--ro center-from-freqoffset? boolean | | +--ro supported-filter-indices* uint32 | +--ro center-from-freqoffset-supported? boolean | +--ro se24-dmrs-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | +--ro max-user-groups-per-slot? uint32 | +--ro max-entries-per-slot? uint32 +--ro endpoint-prach-group* [id] | +--ro id uint16 | +--ro supported-prach-preamble-formats* prach-preamble-format +--ro supported-compression-method-sets* [id] | +--ro id uint16 | +--ro compression-method-supported* [] | +--ro iq-bitwidth? uint8 | +--ro compression-method? compression-method-def | x--ro (compression-format)? | | +--:(no-compresison) | | +--:(block-floating-point) | | | +--ro exponent? uint8 | | +--:(block-floating-point-selective-re-sending) | | | +--ro sres-exponent? uint8 | | +--:(block-scaling) | | | +--ro block-scalar? uint8 | | +--:(u-law) | | | +--ro comp-bit-width? uint8 | | | +--ro comp-shift? uint8 | | +--:(beam-space-compression) | | | +--ro active-beam-space-coeficient-mask* uint8 | | | +--ro block-scaler? uint8 | | +--:(modulation-compression) | | | +--ro csf? uint8 | | | +--ro mod-comp-scaler? uint16 | | +--:(modulation-compression-selective-re-sending) | | +--ro sres-csf? uint8 | | +--ro sres-mod-comp-scaler? uint16 | +--ro fs-offset* uint8 {cf:CONFIGURABLE-FS-OFFSET}? +--ro static-low-level-tx-endpoints* [name] | +--ro name string | +--ro restricted-interfaces* -> /if:interfaces/interface/name ETSI ETSI TS 104 023 V17.1.0 (2026-01) 312 | +--ro array -> /user-plane-configuration/tx-arrays/name | +--ro endpoint-type? -> ../../endpoint-types/id | +--ro capacity-sharing-groups* -> ../../endpoint-capacity-sharing-groups/id | +--ro supported-reference-level* [id] {TX-REFERENCE-LEVEL}? | | +--ro id uint16 | | +--ro min decimal64 | | +--ro max decimal64 | +--ro compression | | +--ro dynamic-compression-supported? boolean | | +--ro realtime-variable-bit-width-supported? boolean | | +--ro supported-compression-set-id? -> ../../../supported-compression-method- sets/id | +--ro configurable-tdd-pattern-supported? boolean {mcap:CONFIGURABLE-TDD-PATTERN- SUPPORTED}? | +--ro tdd-group? uint8 | +--ro energy-sharing-group-id* uint8 {feat:MPLANE-DATA-LAYER-CONTROL}? | +--ro se10-member-candidate-list? -> /user-plane-configuration/se10-member- candidate-tx-lists/id {feat:SE10-MEMBER-CANDIDATE-LIST}? +--ro static-low-level-rx-endpoints* [name] | +--ro name string | +--ro restricted-interfaces* -> /if:interfaces/interface/name | +--ro array -> /user-plane-configuration/rx-arrays/name | +--ro endpoint-type? -> ../../endpoint-types/id | +--ro capacity-sharing-groups* -> ../../endpoint-capacity-sharing-groups/id | +--ro prach-group? -> ../../endpoint-prach-group/id | +--ro compression | | +--ro dynamic-compression-supported? boolean | | +--ro realtime-variable-bit-width-supported? boolean | | +--ro supported-compression-set-id? -> ../../../supported-compression-method- sets/id | +--ro static-config-supported? enumeration | +--ro max-prach-patterns? uint8 | +--ro extended-max-prach-patterns? uint32 {feat:EXTENDED-PRACH-CONFIGURATION}? | +--ro max-srs-patterns? uint8 | +--ro configurable-tdd-pattern-supported? boolean {mcap:CONFIGURABLE-TDD-PATTERN- SUPPORTED}? | +--ro tdd-group? uint8 | +--ro transmission-order? uint32 {feat:ORDERED-TRANSMISSION}? | +--ro transmission-order-group? uint32 {feat:ORDERED-TRANSMISSION}? | +--ro energy-sharing-group-id* uint8 {feat:MPLANE-DATA-LAYER-CONTROL}? | +--ro se10-member-candidate-list? -> /user-plane-configuration/se10-member- candidate-rx-lists/id {feat:SE10-MEMBER-CANDIDATE-LIST}? +--rw low-level-tx-endpoints* [name] | +--rw name -> /user-plane-configuration/static- low-level-tx-endpoints/name | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? | +--rw compression! | | +--rw iq-bitwidth? uint8 | | +--rw compression-type compression-type-def | | x--rw bitwidth? uint8 | | +--rw compression-method? compression-method-def | | x--rw (compression-format)? | | | +--:(no-compresison) | | | +--:(block-floating-point) | | | | +--rw exponent? uint8 | | | +--:(block-floating-point-selective-re-sending) | | | | +--rw sres-exponent? uint8 | | | +--:(block-scaling) | | | | +--rw block-scalar? uint8 | | | +--:(u-law) | | | | +--rw comp-bit-width? uint8 | | | | +--rw comp-shift? uint8 | | | +--:(beam-space-compression) | | | | +--rw active-beam-space-coeficient-mask* uint8 | | | | +--rw block-scaler? uint8 | | | +--:(modulation-compression) | | | | +--rw csf? uint8 | | | | +--rw mod-comp-scaler? uint16 | | | +--:(modulation-compression-selective-re-sending) | | | +--rw sres-csf? uint8 | | | +--rw sres-mod-comp-scaler? uint16 | | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? | | +--rw dynamic-compression-configuration* [id] | | | +--rw id uint16 | | | +--rw iq-bitwidth? uint8 | | | +--rw compression-method? compression-method-def | | | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? ETSI ETSI TS 104 023 V17.1.0 (2026-01) 313 | | | x--rw channel-information-iq-bitwidth? uint8 | | +--rw channel-information-bitwidth? uint8 | | +--rw channel-information-compressions* [id] {feat:CHANNEL-INFORMATION-COMPRESSION}? | | | +--rw id uint16 | | | +--rw channel-information-compression-method? cf:ci-compression-method-def | | | +--rw iq-bitwidth? uint8 | | +--rw bf-weights-compressions* [id] | | +--rw id uint16 | | +--rw bf-weights-compression? cf:bf-compression-method-def | | +--rw iq-bitwidth? uint8 | +--rw frame-structure? uint8 | +--rw cp-type? enumeration | +--rw cp-length uint16 | +--rw cp-length-other uint16 | +--rw offset-to-absolute-frequency-center int32 | +--rw number-of-prb-per-scs* [scs] | | +--rw scs mcap:scs-config-type | | +--rw number-of-prb uint16 | +--rw e-axcid | | +--rw o-du-port-bitmask uint16 | | +--rw band-sector-bitmask uint16 | | +--rw ccid-bitmask uint16 | | +--rw ru-port-bitmask uint16 | | +--rw eaxc-id uint16 | +--rw coupling-to? -> /mcap:module-capability/ru- capabilities/coupling-methods/coupling-via-frequency-and-time | +--rw coupling-method? enumeration | +--rw configurable-tdd-pattern-supported? -> /user-plane-configuration/static- low-level-tx-endpoints[name=current()/../name]/configurable-tdd-pattern-supported {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? | +--rw cplane-message-processing-limits-enabled? boolean {feat:CPLANE-MESSAGE- PROCESSING-LIMITS}? | +--rw uplane-message-section-header-limit-enabled? boolean {feat:UPLANE-MESSAGE- PROCESSING-LIMITS}? | +--rw beam-update-contention-control-enabled? boolean {feat:BEAM-UPDATE-CONTENTION- CONTROL}? | +--rw channel-information-prb-group-configuration {feat:CHANNEL-INFORMATION-PRB-GROUP}? | | +--rw enable-ci-prb-group? boolean | | +--rw ci-prb-group-size? uint8 | +--rw non-scheduled-ueid-enabled? boolean {feat:NON-SCHEDULED-UEID}? | +--rw se-11-continuity-flag-enabled? boolean {feat:SE11-WITH-CONTINUITY-BIT- SUPPORT}? | +--rw prg-size-supp-se-21-with-st6-enabled? boolean {feat:PRG-SIZE-SUPP-SE-21-WITH- ST6}? | +--rw prg-size-supp-se-21-with-st5-enabled? boolean {feat:PRG-SIZE-SUPP-SE-21-WITH- ST5}? | +--rw user-group-optimization-enabled-tx? boolean {feat:USER-GROUP-OPTIMIZATION}? | +--rw se-20-multi-sd-punc-pattern-enabled-tx? boolean {feat:SE20-MULTI-SD-PUNC- PATTERN-SUPPORT,feat:USER-GROUP-OPTIMIZATION}? | +--rw combination-configuration | | +--rw endpoint-type? -> /user-plane-configuration/static-low-level-tx- endpoints[name=current()/../../name]/endpoint-type | | +--rw combination-id? -> /user-plane-configuration/endpoint-types[id = current()/../endpoint-type]/supported-configuration-combinations/combination-id | | +--rw configurations* [id] | | +--rw id uint32 | | +--rw set-id? -> /user-plane-configuration/endpoint-types[id = current()/../../endpoint-type]/supported-configuration-combinations[combination-id = current()/../../combination-id]/set/set-id | | +--rw config-id? -> /user-plane-configuration/endpoint-types[id = current()/../../endpoint-type]/supported-configuration-combinations[combination-id = current()/../../combination-id]/set[set-id = current()/../set-id]/config/config-id | +--rw configured-bf-profile-id? -> /user-plane-configuration/endpoint- types/bf-profile-group {feat:BF-DELAY-PROFILE}? | +--rw bf-methods* beamforming-method-type {feat:SELECTED- BF-METHOD-CONFIGURATION and feat:BF-DELAY-PROFILE}? +--rw low-level-rx-endpoints* [name] | +--rw name -> /user-plane- configuration/static-low-level-rx-endpoints/name | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? | +--rw compression! | | +--rw iq-bitwidth? uint8 | | +--rw compression-type compression-type-def | | x--rw bitwidth? uint8 | | +--rw compression-method? compression-method-def | | x--rw (compression-format)? | | | +--:(no-compresison) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 314 | | | +--:(block-floating-point) | | | | +--rw exponent? uint8 | | | +--:(block-floating-point-selective-re-sending) | | | | +--rw sres-exponent? uint8 | | | +--:(block-scaling) | | | | +--rw block-scalar? uint8 | | | +--:(u-law) | | | | +--rw comp-bit-width? uint8 | | | | +--rw comp-shift? uint8 | | | +--:(beam-space-compression) | | | | +--rw active-beam-space-coeficient-mask* uint8 | | | | +--rw block-scaler? uint8 | | | +--:(modulation-compression) | | | | +--rw csf? uint8 | | | | +--rw mod-comp-scaler? uint16 | | | +--:(modulation-compression-selective-re-sending) | | | +--rw sres-csf? uint8 | | | +--rw sres-mod-comp-scaler? uint16 | | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? | | +--rw dynamic-compression-configuration* [id] | | | +--rw id uint16 | | | +--rw iq-bitwidth? uint8 | | | +--rw compression-method? compression-method-def | | | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? | | +--rw bf-weights-compressions* [id] | | +--rw id uint16 | | +--rw bf-weights-compression? cf:bf-compression-method-def | | +--rw iq-bitwidth? uint8 | +--rw frame-structure? uint8 | +--rw cp-type? enumeration | +--rw cp-length uint16 | +--rw cp-length-other uint16 | +--rw offset-to-absolute-frequency-center int32 | +--rw number-of-prb-per-scs* [scs] | | +--rw scs mcap:scs-config-type | | +--rw number-of-prb uint16 | +--rw ul-fft-sampling-offsets* [scs] | | +--rw scs mcap:scs-config-type | | +--rw ul-fft-sampling-offset? uint16 | +--rw e-axcid | | +--rw o-du-port-bitmask uint16 | | +--rw band-sector-bitmask uint16 | | +--rw ccid-bitmask uint16 | | +--rw ru-port-bitmask uint16 | | +--rw eaxc-id uint16 | +--rw eaxc-gain-correction? decimal64 {EAXC-GAIN- CORRECTION}? | +--rw non-time-managed-delay-enabled? boolean | +--rw coupling-to? -> /mcap:module- capability/ru-capabilities/coupling-methods/coupling-via-frequency-and-time | +--rw coupling-method? enumeration | +--rw static-config-supported? -> /user-plane- configuration/static-low-level-rx-endpoints[name=current()/../name]/static-config-supported | +--rw static-prach-configuration? -> /user-plane- configuration/static-prach-configurations/static-prach-config-id {mcap:PRACH-STATIC-CONFIGURATION- SUPPORTED}? | +--rw static-srs-configuration? -> /user-plane- configuration/static-srs-configurations/static-srs-config-id {mcap:SRS-STATIC-CONFIGURATION- SUPPORTED}? | +--rw configurable-tdd-pattern-supported? -> /user-plane- configuration/static-low-level-rx-endpoints[name=current()/../name]/configurable-tdd-pattern- supported {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? | +--rw transmission-window-control? enumeration {feat:STATIC- TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? | +--rw transmission-window-schedule? union {feat:STATIC- TRANSMISSION-WINDOW-CONTROL}? | +--rw transmission-window-offset? uint16 {feat:STATIC- TRANSMISSION-WINDOW-CONTROL}? | +--rw transmission-window-size? uint16 {feat:STATIC- TRANSMISSION-WINDOW-CONTROL}? | +--rw transmission-type? enumeration {feat:STATIC- TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION}? | +--rw ordered-transmission? boolean {feat:ORDERED- TRANSMISSION}? | +--rw cplane-message-processing-limits-enabled? boolean {feat:CPLANE-MESSAGE- PROCESSING-LIMITS}? | +--rw beam-update-contention-control-enabled? boolean {feat:BEAM-UPDATE- CONTENTION-CONTROL}? ETSI ETSI TS 104 023 V17.1.0 (2026-01) 315 | +--rw non-scheduled-ueid-enabled? boolean {feat:NON-SCHEDULED- UEID}? | +--rw center-from-freqoffset-enabled? boolean | +--rw user-group-optimization-enabled-rx? boolean {feat:USER-GROUP- OPTIMIZATION}? | +--rw se-20-multi-sd-punc-pattern-enabled-rx? boolean {feat:SE20-MULTI-SD- PUNC-PATTERN-SUPPORT,feat:USER-GROUP-OPTIMIZATION}? | +--rw combination-configuration | | +--rw endpoint-type? -> /user-plane-configuration/static-low-level-rx- endpoints[name=current()/../../name]/endpoint-type | | +--rw combination-id? -> /user-plane-configuration/endpoint-types[id = current()/../endpoint-type]/supported-configuration-combinations/combination-id | | +--rw configurations* [id] | | +--rw id uint32 | | +--rw set-id? -> /user-plane-configuration/endpoint-types[id = current()/../../endpoint-type]/supported-configuration-combinations[combination-id = current()/../../combination-id]/set/set-id | | +--rw config-id? -> /user-plane-configuration/endpoint-types[id = current()/../../endpoint-type]/supported-configuration-combinations[combination-id = current()/../../combination-id]/set[set-id = current()/../set-id]/config/config-id | +--rw configured-bf-profile-id? -> /user-plane- configuration/endpoint-types/bf-profile-group {feat:BF-DELAY-PROFILE}? | +--rw sinr-reporting-enabled? boolean {feat:DMRS-BF-EQ}? | +--rw oru-control-sinr-time-resolution-enabled? boolean {feat:ORU-CONTROL- SINR-TIME-RESOLUTION}? | +--rw sinr-reporting-configuration {feat:DMRS-BF-EQ}? | | +--rw sinr-resolution | | | +--rw sinr-per-prb? uint8 | | | +--rw sinr-slot-mask? uint16 | | | +--rw sinr-slot-masks* [sinr-slot-mask-id] {feat:ORU-CONTROL-SINR-TIME-RESOLUTION}? | | | +--rw sinr-slot-mask-id uint8 | | | +--rw sinr-slot-mask? uint16 | | +--rw sinr-compression | | +--rw sinr-bitwidth? uint8 | | +--rw sinr-compression-method? sinr-compression-method-def | | +--rw sinr-block-size? uint8 | | +--rw sinr-reference-level-config? decimal64 | | +--ro sinr-reference-level-used? decimal64 | +--rw dynamic-sinr-per-prb-enabled? boolean {feat:DYNAMIC-SINR- PER-PRB}? | +--rw se26-usage-enabled? boolean | +--rw bf-methods* beamforming-method-type {feat:SELECTED-BF-METHOD-CONFIGURATION and feat:BF-DELAY-PROFILE}? | +--rw eq-scale-offset-config? decimal64 {feat:DMRS-BF-EQ}? | +--ro eq-scale-offset-used? decimal64 {feat:DMRS-BF-EQ}? | +--rw rrm-meas-enabled* rrm-meas-types {feat:RRM- MEAS-REPORTING}? | +--rw se-27-odu-controlled-dimensionality-reduction-enabled? enumeration {feat:SE27-ODU- CONTROLLED-DIMENSIONALITY-REDUCTION}? | +--rw se-27-num-elements? uint16 {feat:SE27-ODU- CONTROLLED-DIMENSIONALITY-REDUCTION}? +--rw tx-array-carriers* [name] | +--rw name string | +--rw odu-ids* [odu-id] {feat:SHARED-ORU-MULTI-ODU}? | | +--rw odu-id string | +--rw sro-ids-and-odu-ids* [odu-id sro-id] {feat:SHARED-ORU-MULTI-ODU and feat:SHARED-ORU- MULTI-OPERATOR}? | | +--rw odu-id string | | +--rw sro-id string | x--rw absolute-frequency-center? uint32 | +--rw center-of-channel-bandwidth uint64 | +--rw channel-bandwidth uint64 | +--rw active? enumeration | +--ro state enumeration | +--ro availability-status* o-ran-cmn:availability-status | +--rw type? enumeration | +--ro duplex-scheme? enumeration | x--rw rw-duplex-scheme? -> /user-plane-configuration/tx-array- carriers[name=current()/../name]/duplex-scheme | x--rw rw-type? -> /user-plane-configuration/tx-array- carriers[name=current()/../name]/type | +--rw occupied-bandwidth | | +--rw lower-bound? uint64 | | +--rw upper-bound? uint64 | +--rw configured-tx-beamId-table-index? uint8 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? | +--rw band-number? -> /mcap:module-capability/band-capabilities/band- number {mcap:LAA}? | x--rw lte-tdd-frame ETSI ETSI TS 104 023 V17.1.0 (2026-01) 316 | | +--rw subframe-assignment enumeration | | +--rw special-subframe-pattern enumeration | +--rw laa-carrier-configuration {mcap:LAA}? | | +--rw ed-threshold-pdsch? int8 | | +--rw ed-threshold-drs? int8 | | +--rw tx-antenna-ports? uint8 | | +--rw transmission-power-for-drs? int8 | | +--rw dmtc-period? enumeration | | +--rw dmtc-offset? uint8 | | +--rw lbt-timer? uint16 | | +--rw max-cw-usage-counter* [priority] | | +--rw priority enumeration | | +--rw counter-value? uint8 | +--rw gain decimal64 | +--rw downlink-radio-frame-offset uint32 | +--rw downlink-sfn-offset int16 | +--rw t-da-offset? uint32 {feat:EXT-ANT-DELAY-CONTROL}? | +--rw reference-level? decimal64 {TX-REFERENCE-LEVEL}? | +--rw configurable-tdd-pattern? -> /user-plane-configuration/configurable-tdd- patterns/tdd-pattern-id {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? | +--rw crb-to-prb-grid-offset? uint16 {feat:PRG-SIZE-SUPP-SE-21-WITH-ST6 or feat:PRG-SIZE-SUPP-SE-21-WITH-ST5}? +--rw rx-array-carriers* [name] | +--rw name string | +--rw odu-ids* [odu-id] {feat:SHARED-ORU-MULTI-ODU}? | | +--rw odu-id string | +--rw sro-ids-and-odu-ids* [odu-id sro-id] {feat:SHARED-ORU-MULTI-ODU and feat:SHARED-ORU- MULTI-OPERATOR}? | | +--rw odu-id string | | +--rw sro-id string | x--rw absolute-frequency-center? uint32 | +--rw center-of-channel-bandwidth uint64 | +--rw channel-bandwidth uint64 | +--rw active? enumeration | +--ro state enumeration | +--ro availability-status* o-ran-cmn:availability-status | +--rw type? enumeration | +--ro duplex-scheme? enumeration | +--rw occupied-bandwidth | | +--rw lower-bound? uint64 | | +--rw upper-bound? uint64 | +--rw configured-rx-beamId-table-index? uint8 {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | +--rw downlink-radio-frame-offset uint32 | +--rw downlink-sfn-offset int16 | +--rw gain-correction decimal64 | +--rw n-ta-offset uint32 | +--rw t-au-offset? uint32 {feat:EXT-ANT-DELAY-CONTROL}? | +--rw configurable-tdd-pattern? -> /user-plane- configuration/configurable-tdd-patterns/tdd-pattern-id {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? | +--rw user-group-mode? enumeration {feat:USER-GROUP-SELF- ASSEMBLY}? | +--rw point-a-offset-to-absolute-frequency-center? int32 {(feat:DMRS-BF-EQ or feat:DMRS- BF-NEQ) and feat:POINT-A-OFFSET-TO-ABSOLUTE-FREQUENCY-CENTER}? | +--rw continuity-block-size-configured? uint8 {(feat:DMRS-BF-EQ or feat:DMRS- BF-NEQ) and feat:CONTINUITY-BLOCK-SIZE}? | +--rw port-reduced-dmrs-data-sending-enabled? boolean {feat:DMRS-BF-EQ or feat:DMRS- BF-NEQ}? +--ro tx-arrays* [name] | +--ro name string | +--ro number-of-rows uint16 | +--ro number-of-columns uint16 | +--ro number-of-array-layers uint8 | +--ro horizontal-spacing? decimal64 | +--ro vertical-spacing? decimal64 | +--ro normal-vector-direction | | +--ro azimuth-angle? decimal64 | | +--ro zenith-angle? decimal64 | +--ro leftmost-bottom-array-element-position | | +--ro x? decimal64 | | +--ro y? decimal64 | | +--ro z? decimal64 | +--ro polarisations* [p] | | +--ro p uint8 | | +--ro polarisation polarisation_type | +--ro band-number -> /mcap:module-capability/band- capabilities/band-number | +--ro related-o-ru-connectors* [name] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 317 | | +--ro name -> /hw:hardware/component/name | | +--ro array-element-id* uint16 | +--ro min-gain? decimal64 | +--ro max-gain decimal64 | +--ro independent-power-budget boolean | +--ro capabilities* [] | | +--ro max-supported-frequency-dl? uint64 | | +--ro min-supported-frequency-dl? uint64 | | +--ro max-supported-bandwidth-dl? uint64 | | +--ro max-num-carriers-dl? uint32 | | +--ro max-carrier-bandwidth-dl? uint64 | | +--ro min-carrier-bandwidth-dl? uint64 | | +--ro supported-technology-dl* enumeration | | +--ro supported-filter-pass-bandwidths-dl | | | +--ro supported-filter-pass-bandwidths* [id] | | | +--ro id uint32 | | | +--ro type? enumeration | | | +--ro carrier-bandwidth? uint64 | | | +--ro filter-pass-bandwidth? uint64 | | +--ro tx-array-beamId-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | +--ro supported-energy-saving-capabilities-dl | | +--ro trx-control-capability-info {feat:TRX-CONTROL}? | | | +--ro supported-trx-control-masks* [index] | | | | +--ro index uint8 | | | | +--ro mask-name? string | | | | +--ro antenna-mask? binary | | | +--ro sleep-modes* [sleep-mode-type] | | | | +--ro sleep-mode-type enumeration | | | | +--ro wake-up-duration? uint32 | | | | +--ro wake-up-duration-guaranteed? boolean | | | +--ro defined-duration-sleep-supported? boolean | | | +--ro undefined-duration-sleep-supported? boolean | | +--ro asm-capability-info {feat:ADVANCED-SLEEP-MODE}? | | +--ro sleep-modes* [sleep-mode-type] | | | +--ro sleep-mode-type enumeration | | | +--ro wake-up-duration? uint32 | | | +--ro wake-up-duration-guaranteed? boolean | | +--ro defined-duration-sleep-supported? boolean | | +--ro undefined-duration-sleep-supported? boolean | +--ro mplane-trx-control-txarr-capability-info {feat:MPLANE-TRX-CONTROL}? | +--ro mplane-supported-trx-control-masks* [index] | +--ro index uint8 | +--ro antenna-mask? binary +--ro rx-arrays* [name] | +--ro name string | +--ro number-of-rows uint16 | +--ro number-of-columns uint16 | +--ro number-of-array-layers uint8 | +--ro horizontal-spacing? decimal64 | +--ro vertical-spacing? decimal64 | +--ro normal-vector-direction | | +--ro azimuth-angle? decimal64 | | +--ro zenith-angle? decimal64 | +--ro leftmost-bottom-array-element-position | | +--ro x? decimal64 | | +--ro y? decimal64 | | +--ro z? decimal64 | +--ro polarisations* [p] | | +--ro p uint8 | | +--ro polarisation polarisation_type | +--ro band-number -> /mcap:module-capability/band- capabilities/band-number | +--ro related-o-ru-connectors* [name] | | +--ro name -> /hw:hardware/component/name | | +--ro array-element-id* uint16 | +--ro gain-correction-range | | +--ro max decimal64 | | +--ro min decimal64 | +--ro capabilities* [] | | +--ro max-supported-frequency-ul? uint64 | | +--ro min-supported-frequency-ul? uint64 | | +--ro max-supported-bandwidth-ul? uint64 | | +--ro max-num-carriers-ul? uint32 | | +--ro max-carrier-bandwidth-ul? uint64 | | +--ro min-carrier-bandwidth-ul? uint64 | | +--ro supported-technology-ul* enumeration | | +--ro supported-filter-pass-bandwidths-ul ETSI ETSI TS 104 023 V17.1.0 (2026-01) 318 | | | +--ro supported-filter-pass-bandwidths* [id] | | | +--ro id uint32 | | | +--ro type? enumeration | | | +--ro carrier-bandwidth? uint64 | | | +--ro filter-pass-bandwidth? uint64 | | +--ro rx-array-beamId-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | +--ro supported-energy-saving-capabilities-ul | | +--ro trx-control-capability-info {feat:TRX-CONTROL}? | | | +--ro supported-trx-control-masks* [index] | | | | +--ro index uint8 | | | | +--ro mask-name? string | | | | +--ro antenna-mask? binary | | | +--ro sleep-modes* [sleep-mode-type] | | | | +--ro sleep-mode-type enumeration | | | | +--ro wake-up-duration? uint32 | | | | +--ro wake-up-duration-guaranteed? boolean | | | +--ro defined-duration-sleep-supported? boolean | | | +--ro undefined-duration-sleep-supported? boolean | | +--ro asm-capability-info {feat:ADVANCED-SLEEP-MODE}? | | +--ro sleep-modes* [sleep-mode-type] | | | +--ro sleep-mode-type enumeration | | | +--ro wake-up-duration? uint32 | | | +--ro wake-up-duration-guaranteed? boolean | | +--ro defined-duration-sleep-supported? boolean | | +--ro undefined-duration-sleep-supported? boolean | +--ro mplane-trx-control-rxarr-capability-info {feat:MPLANE-TRX-CONTROL}? | +--ro mplane-supported-trx-control-masks* [index] | +--ro index uint8 | +--ro antenna-mask? binary +--ro relations* [entity] | +--ro entity uint16 | +--ro array1 | | +--ro (antenna-type)? | | +--:(tx) | | | +--ro tx-array-name? -> /user-plane-configuration/tx-arrays/name | | +--:(rx) | | +--ro rx-array-name? -> /user-plane-configuration/rx-arrays/name | +--ro array2 | | +--ro (antenna-type)? | | +--:(tx) | | | +--ro tx-array-name? -> /user-plane-configuration/tx-arrays/name | | +--:(rx) | | +--ro rx-array-name? -> /user-plane-configuration/rx-arrays/name | +--ro types* [relation-type] | +--ro relation-type enumeration | +--ro pairs* [element-array1] | +--ro element-array1 uint16 | +--ro element-array2? uint16 +--rw eaxc-id-group-configuration {mcap:EAXC-ID-GROUP-SUPPORTED}? | +--rw max-num-tx-eaxc-id-groups? -> /mcap:module-capability/ru-capabilities/eaxcid- grouping-capabilities/max-num-tx-eaxc-id-groups | +--rw max-num-tx-eaxc-ids-per-group? -> /mcap:module-capability/ru-capabilities/eaxcid- grouping-capabilities/max-num-tx-eaxc-ids-per-group | +--rw max-num-rx-eaxc-id-groups? -> /mcap:module-capability/ru-capabilities/eaxcid- grouping-capabilities/max-num-rx-eaxc-id-groups | +--rw max-num-rx-eaxc-ids-per-group? -> /mcap:module-capability/ru-capabilities/eaxcid- grouping-capabilities/max-num-rx-eaxc-ids-per-group | +--rw tx-eaxc-id-group* [representative-tx-eaxc-id] | | +--rw representative-tx-eaxc-id uint16 | | +--rw member-tx-eaxc-id* uint16 | +--rw rx-eaxc-id-group* [representative-rx-eaxc-id] | +--rw representative-rx-eaxc-id uint16 | +--rw member-rx-eaxc-id* uint16 +--rw static-prach-configurations* [static-prach-config-id] {mcap:PRACH-STATIC-CONFIGURATION- SUPPORTED}? | +--rw static-prach-config-id uint8 | +--rw sfn-offset? uint32 | +--rw pattern-period uint16 | +--rw guard-tone-low-re uint32 | +--rw num-prach-re uint32 | +--rw guard-tone-high-re uint32 | +--rw sequence-duration uint32 | +--rw prach-patterns* [prach-pattern-id] | +--rw prach-pattern-id uint32 | +--rw number-of-repetitions uint8 | +--rw number-of-occasions uint32 | +--rw re-offset uint32 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 319 | +--rw occasion-parameters* [occasion-id] | | +--rw occasion-id uint32 | | +--rw cp-length uint16 | | +--rw gp-length? uint16 | | +--rw beam-id uint16 | +--rw frame-number uint16 | +--rw sub-frame-id uint16 | +--rw time-offset uint16 +--rw static-srs-configurations* [static-srs-config-id] {mcap:SRS-STATIC-CONFIGURATION- SUPPORTED}? | +--rw static-srs-config-id uint8 | +--rw pattern-period uint16 | +--rw srs-patterns* [srs-pattern-id] | +--rw srs-pattern-id uint16 | +--rw sub-frame-id uint16 | +--rw slot-id uint16 | +--rw start-symbol-id uint16 | +--rw beam-id uint16 | +--rw num-symbol uint16 | +--rw start-prbc uint16 | +--rw num-prbc uint16 +--rw configurable-tdd-patterns* [tdd-pattern-id] {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? | +--rw tdd-pattern-id uint8 | +--rw switching-points* [switching-point-id] | +--rw switching-point-id uint16 | +--rw direction enumeration | +--rw frame-offset uint32 +--ro endpoint-bf-profile-group* [bf-profile-id] {feat:BF-DELAY-PROFILE}? | +--ro bf-profile-id uint16 | +--ro supported-bf-methods* beamforming-method-type | +--ro supported-delay-profile? -> /or-dm:delay-management/non-default-ru-delay- profile/delay-profile-id +--ro se10-member-candidate-tx-lists* [id] {feat:SE10-MEMBER-CANDIDATE-LIST}? | +--ro id uint8 | +--ro member-candidates* -> /user-plane-configuration/static-low-level-tx-endpoints/name +--ro se10-member-candidate-rx-lists* [id] {feat:SE10-MEMBER-CANDIDATE-LIST}? | +--ro id uint8 | +--ro member-candidates* -> /user-plane-configuration/static-low-level-rx-endpoints/name +--rw general-config | +--rw regularization-factor-se-configured? boolean | +--rw little-endian-byte-order? boolean | +--rw uplane-only-dl-mode-enable? boolean {feat:UPLANE-ONLY-DL-MODE}? | +--rw st4-for-time-domain-beamforming-weights-enabled? boolean {feat:ST4-SLOT-CONFIG-MSG- SUPPORT}? | +--rw seq-id-checking-disabled? boolean {feat:SEQ-ID-CHECKING- CONFIGURABLE}? | +--rw multiple-beamId-tables-support-enabled? boolean {feat:MULTIPLE-BEAMID- TABLES-SUPPORTED}? | +--rw energy-sharing-groups-disabled* uint8 {feat:MPLANE-DATA-LAYER- CONTROL}? | +--rw config-symb-reorder-method? symb-reorder-method {feat:DMRS-BF- EQ or feat:DMRS-BF-NEQ}? | +--rw config-symb-reorder-upSymbId-type? -> ../../endpoint-types/supported- symb-reorder-capabilities/up-symbolId-type-supported {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | +--rw ueid-persistence-enabled? boolean {feat:UEID-PERSISTENCE}? | +--rw ueid-layer-bits-configured? uint8 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | +--rw vswr-thresholds {feat:CONFIGURABLE-VSWR-THRESHOLDS}? | +--ro default-vswr-thresholds | | +--ro default-vswr-minor-threshold? decimal64 | | +--ro default-vswr-major-threshold? decimal64 | +--ro vswr-thresholds-range | | +--ro min? decimal64 | | +--ro max? decimal64 | +--rw configurable-vswr-thresholds | +--rw global-vswr-monitoring-trigger-power? decimal64 | +--rw global-vswr-minor-threshold? decimal64 | +--rw global-vswr-major-threshold? decimal64 | +--rw vswr-threshold-per-tx-array-element* [tx-array-name array-element] | +--rw tx-array-name -> /user-plane-configuration/tx-arrays/name | +--rw array-element uint16 | +--rw vswr-minor-threshold? decimal64 | +--rw vswr-major-threshold? decimal64 | +--rw vswr-monitoring-trigger-power? decimal64 +--rw tx-array-antenna-mask-config* [array-name] {feat:MPLANE-TRX-CONTROL}? | +--rw array-name -> /user-plane-configuration/tx-arrays/name | +--rw antenna-bitmask? binary | +--rw antenna-bitmask-index? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 320 +--rw rx-array-antenna-mask-config* [array-name] {feat:MPLANE-TRX-CONTROL}? +--rw array-name -> /user-plane-configuration/rx-arrays/name +--rw antenna-bitmask? binary +--rw antenna-bitmask-index? uint8 notifications: +---n tx-array-carriers-state-change | +--ro tx-array-carriers* [name] | +--ro name -> /user-plane-configuration/tx-array-carriers/name | +--ro state? -> /user-plane-configuration/tx-array-carriers/state | +--ro availability-status? -> /user-plane-configuration/tx-array-carriers/availability- status +---n rx-array-carriers-state-change | +--ro rx-array-carriers* [name] | +--ro name -> /user-plane-configuration/rx-array-carriers/name | +--ro state? -> /user-plane-configuration/rx-array-carriers/state | +--ro availability-status? -> /user-plane-configuration/rx-array-carriers/availability- status +---n data-layer-control-wakeup-notification {feat:MPLANE-DATA-LAYER-CONTROL}? | +--ro energy-sharing-group* uint8 +---n mplane-trx-control-ant-mask-update {feat:MPLANE-TRX-CONTROL}? +--ro array-name? union +--ro array-type? enumeration +--ro updated-antenna-mask? binary +--ro updated-antenna-mask-index? uint8 D.3.9 o-ran-ald module The format for the ald module is provided below. module: o-ran-ald rpcs: +---x ald-communication +---w input | +---w port-id -> /ap:ald-ports-io/ald-port/port-id | +---w ald-req-msg? binary +--ro output +--ro port-id -> /ap:ald-ports-io/ald-port/port-id +--ro status enumeration +--ro error-message? string +--ro ald-resp-msg? binary +--ro frames-with-wrong-crc? uint32 +--ro frames-without-stop-flag? uint32 +--ro number-of-received-octets? uint32 D.3.10 o-ran-troubleshooting module The format for the troubleshooting module is provided below. module: o-ran-troubleshooting rpcs: +---x start-troubleshooting-logs | +--ro output | +--ro status? enumeration | +--ro failure-reason? string +---x stop-troubleshooting-logs +--ro output +--ro status? enumeration +--ro failure-reason? string notifications: +---n troubleshooting-log-generated +--ro log-file-name* string D.3.11 Void ETSI ETSI TS 104 023 V17.1.0 (2026-01) 321 D.3.12 o-ran-trace module The format for the trace operations module is provided below. module: o-ran-trace rpcs: +---x start-trace-logs | +--ro output | +--ro status? enumeration | +--ro failure-reason? string +---x stop-trace-logs +--ro output +--ro status? enumeration +--ro failure-reason? string notifications: +---n trace-log-generated +--ro log-file-name* string +--ro is-notification-last? Boolean D.3.13 o-ran-ieee802-dot1q-cfm module The format for the o-ran-ieee802-dot1q-cfm module is provided below. module: o-ran-ieee802-dot1q-cfm augment /dot1q-cfm:cfm/dot1q-cfm:maintenance-group/dot1q-cfm:mep: +--rw interface? if:interface-ref +--rw primary-vid? -> /if:interfaces/interface/o-ran-int:vlan-id D.4 Interfaces folder D.4.1 o-ran-interfaces.yang module The format for the interfaces module is provided below. module: o-ran-interfaces rpcs: +---x reset-interface-counters module: ietf-interfaces +--rw interfaces | +--rw interface* [name] | | +--rw name string | | +--rw description? string | | +--rw type identityref | | +--rw enabled? boolean | | +--rw link-up-down-trap-enable? enumeration {if-mib}? | | +--ro admin-status enumeration {if-mib}? | | +--ro oper-status enumeration | | +--ro last-change? yang:date-and-time | | +--ro if-index int32 {if-mib}? | | +--ro phys-address? yang:phys-address | | +--ro higher-layer-if* interface-ref | | +--ro lower-layer-if* interface-ref | | +--ro speed? yang:gauge64 | | +--ro statistics | | | +--ro discontinuity-time yang:date-and-time | | | +--ro in-octets? yang:counter64 | | | +--ro in-unicast-pkts? yang:counter64 | | | +--ro in-broadcast-pkts? yang:counter64 | | | +--ro in-multicast-pkts? yang:counter64 | | | +--ro in-discards? yang:counter32 | | | +--ro in-errors? yang:counter32 | | | +--ro in-unknown-protos? yang:counter32 | | | +--ro out-octets? yang:counter64 | | | +--ro out-unicast-pkts? yang:counter64 | | | +--ro out-broadcast-pkts? yang:counter64 | | | +--ro out-multicast-pkts? yang:counter64 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 322 | | | +--ro out-discards? yang:counter32 | | | +--ro out-errors? yang:counter32 | | +--rw ip:ipv4! | | | +--rw ip:enabled? boolean | | | +--rw ip:forwarding? boolean | | | +--rw ip:mtu? uint16 | | | +--rw ip:address* [ip] | | | | +--rw ip:ip inet:ipv4-address-no-zone | | | | +--rw (ip:subnet) | | | | | +--:(ip:prefix-length) | | | | | | +--rw ip:prefix-length? uint8 | | | | | +--:(ip:netmask) | | | | | +--rw ip:netmask? yang:dotted-quad {ipv4-non-contiguous-netmasks}? | | | | +--ro ip:origin? ip-address-origin | | | +--rw ip:neighbor* [ip] | | | | +--rw ip:ip inet:ipv4-address-no-zone | | | | +--rw ip:link-layer-address yang:phys-address | | | | +--ro ip:origin? neighbor-origin | | | +--rw o-ran-int:m-plane-marking? inet:dscp | | | +--rw o-ran-int:tcp! {feat:PER-INT-TCP-MSS}? | | | | +--rw o-ran-int:mss-adjust? mss | | | +--rw o-ran-int:diffserv-markings {UDPIP-BASED-CU-PLANE}? | | | +--rw o-ran-int:u-plane-marking? inet:dscp | | | +--rw o-ran-int:c-plane-marking? inet:dscp | | | +--rw o-ran-int:s-plane-marking? inet:dscp | | | +--rw o-ran-int:other-marking? inet:dscp | | | +--rw o-ran-int:enhanced-uplane-markings* [up-marking-name] | | | +--rw o-ran-int:up-marking-name string | | | +--rw o-ran-int:enhanced-marking? inet:dscp | | +--rw ip:ipv6! | | | +--rw ip:enabled? boolean | | | +--rw ip:forwarding? boolean | | | +--rw ip:mtu? uint32 | | | +--rw ip:address* [ip] | | | | +--rw ip:ip inet:ipv6-address-no-zone | | | | +--rw ip:prefix-length uint8 | | | | +--ro ip:origin? ip-address-origin | | | | +--ro ip:status? enumeration | | | +--rw ip:neighbor* [ip] | | | | +--rw ip:ip inet:ipv6-address-no-zone | | | | +--rw ip:link-layer-address yang:phys-address | | | | +--ro ip:origin? neighbor-origin | | | | +--ro ip:is-router? empty | | | | +--ro ip:state? enumeration | | | +--rw ip:dup-addr-detect-transmits? uint32 | | | +--rw ip:autoconf | | | | +--rw ip:create-global-addresses? boolean | | | | +--rw ip:create-temporary-addresses? boolean {ipv6-privacy-autoconf}? | | | | +--rw ip:temporary-valid-lifetime? uint32 {ipv6-privacy-autoconf}? | | | | +--rw ip:temporary-preferred-lifetime? uint32 {ipv6-privacy-autoconf}? | | | +--rw o-ran-int:m-plane-marking? inet:dscp | | | +--rw o-ran-int:tcp! {feat:PER-INT-TCP-MSS}? | | | | +--rw o-ran-int:mss-adjust? mss | | | +--rw o-ran-int:diffserv-markings {UDPIP-BASED-CU-PLANE}? | | | +--rw o-ran-int:u-plane-marking? inet:dscp | | | +--rw o-ran-int:c-plane-marking? inet:dscp | | | +--rw o-ran-int:s-plane-marking? inet:dscp | | | +--rw o-ran-int:other-marking? inet:dscp | | | +--rw o-ran-int:enhanced-uplane-markings* [up-marking-name] | | | +--rw o-ran-int:up-marking-name string | | | +--rw o-ran-int:enhanced-marking? inet:dscp | | +--rw o-ran-int:l2-mtu? uint16 | | +--ro o-ran-int:maximum-ethernet-payload-size? uint16 | | +--rw o-ran-int:vlan-tagging? boolean | | +--rw o-ran-int:class-of-service | | | +--rw o-ran-int:u-plane-marking? pcp | | | +--rw o-ran-int:c-plane-marking? pcp | | | +--rw o-ran-int:m-plane-marking? pcp | | | +--rw o-ran-int:s-plane-marking? pcp | | | +--rw o-ran-int:other-marking? pcp | | | +--rw o-ran-int:enhanced-uplane-markings* [up-marking-name] | | | +--rw o-ran-int:up-marking-name string | | | +--rw o-ran-int:enhanced-marking? pcp | | +--ro o-ran-int:interface-groups-id* -> /if:interfaces/o-ran-int:interface- grouping/interfaces-groups/interface-group-id | | +--rw o-ran-int:macsec-bypass-policy {feat:MACSEC-BYPASS-POLICY}? | | | +--rw o-ran-int:policy* [name] | | | +--rw o-ran-int:name string ETSI ETSI TS 104 023 V17.1.0 (2026-01) 323 | | | +--rw (o-ran-int:policy-type)? | | | +--:(o-ran-int:mac) | | | | +--rw o-ran-int:destination-mac-address* yang:mac-address | | | +--:(o-ran-int:ethertype) | | | | +--rw o-ran-int:ethertype* ethertype-string | | | +--:(o-ran-int:vlan-id) | | | +--rw o-ran-int:vlan-id* uint16 | | +--rw o-ran-int:base-interface? if:interface-ref | | +--rw o-ran-int:vlan-id? uint16 | | +--ro o-ran-int:last-cleared? yang:date-and-time | | +--rw o-ran-int:alias-macs* yang:mac-address {ALIASMAC-BASED-CU-PLANE}? | | +--rw o-ran-int:mac-address? yang:mac-address | | +--rw o-ran-int:port-reference | | +--rw o-ran-int:port-name? -> /hw:hardware/component/name | | +--rw o-ran-int:port-number? uint8 | +--ro o-ran-int:macsec-bypass-capabilities {feat:MACSEC-BYPASS-POLICY}? | | +--ro o-ran-int:per-interface-policy-list-max-elements? uint16 | | +--ro o-ran-int:cummulative-policy-list-max-elements? uint16 | | +--ro o-ran-int:supported-policy* enumeration | +--ro o-ran-int:interface-grouping! | +--ro o-ran-int:interfaces-groups* [interface-group-id] | +--ro o-ran-int:interface-group-id uint8 | +--ro o-ran-int:max-sustainable-ingress-bandwidth? uint32 | +--ro o-ran-int:max-sustainable-egress-bandwidth? uint32 x--ro interfaces-state x--ro interface* [name] x--ro name string x--ro type identityref x--ro admin-status enumeration {if-mib}? x--ro oper-status enumeration x--ro last-change? yang:date-and-time x--ro if-index int32 {if-mib}? x--ro phys-address? yang:phys-address x--ro higher-layer-if* interface-state-ref x--ro lower-layer-if* interface-state-ref x--ro speed? yang:gauge64 x--ro statistics | x--ro discontinuity-time yang:date-and-time | x--ro in-octets? yang:counter64 | x--ro in-unicast-pkts? yang:counter64 | x--ro in-broadcast-pkts? yang:counter64 | x--ro in-multicast-pkts? yang:counter64 | x--ro in-discards? yang:counter32 | x--ro in-errors? yang:counter32 | x--ro in-unknown-protos? yang:counter32 | x--ro out-octets? yang:counter64 | x--ro out-unicast-pkts? yang:counter64 | x--ro out-broadcast-pkts? yang:counter64 | x--ro out-multicast-pkts? yang:counter64 | x--ro out-discards? yang:counter32 | x--ro out-errors? yang:counter32 x--ro ip:ipv4! | x--ro ip:forwarding? boolean | x--ro ip:mtu? uint16 | x--ro ip:address* [ip] | | x--ro ip:ip inet:ipv4-address-no-zone | | x--ro (ip:subnet)? | | | x--:(ip:prefix-length) | | | | x--ro ip:prefix-length? uint8 | | | x--:(ip:netmask) | | | x--ro ip:netmask? yang:dotted-quad {ipv4-non-contiguous-netmasks}? | | x--ro ip:origin? ip-address-origin | x--ro ip:neighbor* [ip] | x--ro ip:ip inet:ipv4-address-no-zone | x--ro ip:link-layer-address? yang:phys-address | x--ro ip:origin? neighbor-origin x--ro ip:ipv6! x--ro ip:forwarding? boolean x--ro ip:mtu? uint32 x--ro ip:address* [ip] | x--ro ip:ip inet:ipv6-address-no-zone | x--ro ip:prefix-length uint8 | x--ro ip:origin? ip-address-origin | x--ro ip:status? enumeration x--ro ip:neighbor* [ip] x--ro ip:ip inet:ipv6-address-no-zone x--ro ip:link-layer-address? yang:phys-address x--ro ip:origin? neighbor-origin ETSI ETSI TS 104 023 V17.1.0 (2026-01) 324 x--ro ip:is-router? empty x--ro ip:state? enumeration D.4.2 o-ran-processing-elements.yang module The format for the processing element module is provided below. module: o-ran-processing-element +--rw processing-elements +--ro maximum-number-of-transport-flows? uint16 +--rw transport-session-type? enumeration +--rw enhanced-uplane-mapping! | +--rw uplane-mapping* [up-marking-name] | +--rw up-marking-name string | +--rw (up-markings)? | +--:(ethernet) | | +--rw up-cos-name? -> /if:interfaces/interface/o-ran-int:class-of- service/enhanced-uplane-markings/up-marking-name | +--:(ipv4) | | +--rw upv4-dscp-name? -> /if:interfaces/interface/ip:ipv4/o-ran-int:diffserv- markings/enhanced-uplane-markings/up-marking-name {o-ran-int:UDPIP-BASED-CU-PLANE}? | +--:(ipv6) | +--rw upv6-dscp-name? -> /if:interfaces/interface/ip:ipv6/o-ran-int:diffserv- markings/enhanced-uplane-markings/up-marking-name {o-ran-int:UDPIP-BASED-CU-PLANE}? +--rw ru-elements* [name] | +--rw name string | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? | +--rw transport-flow | +--rw interface-name? -> /if:interfaces/interface/name | +--rw aliasmac-flow {o-ran-int:ALIASMAC-BASED-CU-PLANE}? | | +--rw ru-aliasmac-address -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:alias-macs | | +--rw vlan-id? -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:vlan-id | | +--rw o-du-mac-address yang:mac-address | +--rw eth-flow | | +--rw ru-mac-address -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:mac-address | | +--rw vlan-id -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:vlan-id | | +--rw o-du-mac-address yang:mac-address | +--rw udpip-flow | | +--rw (address) | | | +--:(ru-ipv4-address) | | | | +--rw ru-ipv4-address? -> /if:interfaces/interface[if:name = current()/../../interface-name]/ip:ipv4/address/ip | | | +--:(ru-ipv6-address) | | | +--rw ru-ipv6-address? -> /if:interfaces/interface[if:name = current()/../../interface-name]/ip:ipv6/address/ip | | +--rw o-du-ip-address inet:ip-address | | +--rw ru-ephemeral-udp-port inet:port-number | | +--rw o-du-ephemeral-udp-port inet:port-number | | +--rw ecpri-destination-udp inet:port-number | +--rw north-eth-flow {SHARED_CELL}? | | +--rw ru-mac-address? -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:mac-address | | +--rw vlan-id? -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:vlan-id | | +--rw north-node-mac-address? yang:mac-address | +--rw south-eth-flow {SHARED_CELL}? | +--rw ru-mac-address? -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:mac-address | +--rw vlan-id? -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:vlan-id | +--rw south-node-mac-address? yang:mac-address +--rw additional-transport-session-type-elements* [transport-session-type] {feat:MULTIPLE- TRANSPORT-SESSION-TYPE}? +--rw transport-session-type enumeration +--rw enhanced-uplane-mapping! | +--rw uplane-mapping* [up-marking-name] | +--rw up-marking-name string | +--rw (up-markings)? | +--:(ethernet) | | +--rw up-cos-name? -> /if:interfaces/interface/o-ran-int:class-of- service/enhanced-uplane-markings/up-marking-name | +--:(ipv4) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 325 | | +--rw upv4-dscp-name? -> /if:interfaces/interface/ip:ipv4/o-ran-int:diffserv- markings/enhanced-uplane-markings/up-marking-name | +--:(ipv6) | +--rw upv6-dscp-name? -> /if:interfaces/interface/ip:ipv6/o-ran-int:diffserv- markings/enhanced-uplane-markings/up-marking-name +--rw ru-elements* [name] +--rw name string +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? +--rw transport-flow +--rw interface-name? -> /if:interfaces/interface/name +--rw aliasmac-flow {o-ran-int:ALIASMAC-BASED-CU-PLANE}? | +--rw ru-aliasmac-address -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:alias-macs | +--rw vlan-id? -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:vlan-id | +--rw o-du-mac-address yang:mac-address +--rw eth-flow | +--rw ru-mac-address -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:mac-address | +--rw vlan-id -> /if:interfaces/interface[if:name = current()/../../interface-name]/o-ran-int:vlan-id | +--rw o-du-mac-address yang:mac-address +--rw udpip-flow +--rw (address) | +--:(ru-ipv4-address) | | +--rw ru-ipv4-address? -> /if:interfaces/interface[if:name = current()/../../interface-name]/ip:ipv4/address/ip | +--:(ru-ipv6-address) | +--rw ru-ipv6-address? -> /if:interfaces/interface[if:name = current()/../../interface-name]/ip:ipv6/address/ip +--rw o-du-ip-address inet:ip-address +--rw ru-ephemeral-udp-port inet:port-number +--rw o-du-ephemeral-udp-port inet:port-number +--rw ecpri-destination-udp inet:port-number D.4.3 o-ran-transceiver.yang module The format for the (SFP) transceiver module is provided below. module: o-ran-transceiver +--rw port-transceivers +--rw port-transceiver-data* [interface-name port-number] +--rw interface-name -> /if:interfaces/interface/name +--rw port-number -> /if:interfaces/interface[if:name = current()/../interface-name]/o-ran-int:port-reference/port-number +--rw interface-names* -> /if:interfaces/interface/name +--rw name? string +--ro present boolean +--ro vendor-id? string +--ro vendor-part? string +--ro vendor-rev? string +--ro serial-no? string +--ro SFF8472-compliance-code? enumeration +--ro connector-type? enumeration +--ro identifier? enumeration +--ro nominal-bitrate? uint32 +--ro low-bitrate-margin? uint8 +--ro high-bitrate-margin? uint8 +--ro rx-power-type? enumeration +--ro rx-power? decimal64 +--ro tx-power? decimal64 +--ro tx-bias-current? decimal64 +--ro voltage? decimal64 +--ro temperature? decimal64 +--ro laser-temperature? decimal64 +--ro transceiver-not-supported? empty +--ro tec-current? decimal64 +--ro additional-multi-lane-reporting* [lane] +--ro lane uint8 +--ro interface-names* -> /if:interfaces/interface/name +--ro rx-power? decimal64 +--ro tx-bias-current? decimal64 +--ro tx-power? decimal64 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 326 D.4.4 o-ran-mplane-int.yang module The format for the management plane interface module is provided below. module: o-ran-mplane-int +--rw mplane-info +--rw searchable-mplane-access-vlans-info | +--rw searchable-access-vlans* vlan-id | +--rw vlan-range | | +--rw lowest-vlan-id? vlan-id | | +--rw highest-vlan-id? vlan-id | +--rw scan-interval? uint16 +--rw m-plane-interfaces | +--rw m-plane-sub-interfaces* [interface-name sub-interface] | | +--rw interface-name -> /if:interfaces/interface/name | | +--rw sub-interface -> /if:interfaces/interface[if:name = current()/../interface- name]/o-ran-int:vlan-id | | +--ro client-info | | +--ro mplane-ipv4-info* [mplane-ipv4] | | | +--ro mplane-ipv4 inet:ipv4-address | | | +--ro port? inet:port-number | | +--ro mplane-ipv6-info* [mplane-ipv6] | | | +--ro mplane-ipv6 inet:ipv6-address | | | +--ro port? inet:port-number | | +--ro mplane-fqdn-info* [mplane-fqdn] | | | +--ro mplane-fqdn inet:domain-name | | | +--ro port? inet:port-number | | x--ro mplane-fqdn* inet:domain-name | +--rw m-plane-ssh-ports | | +--rw call-home-ssh-port? inet:port-number | | +--rw server-ssh-port? inet:port-number | +--rw m-plane-tls-ports | +--rw call-home-tls-port? inet:port-number | +--rw server-tls-port? inet:port-number +--rw configured-client-info +--rw mplane-ipv4-info* [mplane-ipv4] | +--rw mplane-ipv4 inet:ipv4-address | +--rw port? inet:port-number +--rw mplane-ipv6-info* [mplane-ipv6] | +--rw mplane-ipv6 inet:ipv6-address | +--rw port? inet:port-number +--rw mplane-fqdn-info* [mplane-fqdn] | +--rw mplane-fqdn inet:domain-name | +--rw port? inet:port-number x--rw mplane-fqdn* inet:domain-name D.4.5 o-ran-dhcp.yang module The format for the dhcp module is provided below. module: o-ran-dhcp +--ro dhcp +--ro interfaces* [interface] | +--ro interface if:interface-ref | +--ro dhcpv4 | | +--ro client-id? string | | +--ro type-code? uint16 | | +--ro (duid-type)? | | | +--:(duid-llt) | | | | +--ro duid-llt-hardware-type? uint16 | | | | +--ro duid-llt-time? yang:timeticks | | | | +--ro duid-llt-link-layer-address? yang:mac-address | | | +--:(duid-en) | | | | +--ro duid-en-enterprise-number? uint32 | | | | +--ro duid-en-identifier? string | | | +--:(duid-ll) | | | | +--ro duid-ll-hardware-type? uint16 | | | | +--ro duid-ll-link-layer-address? yang:mac-address | | | +--:(duid-uuid) | | | | +--ro uuid? yang:uuid | | | +--:(duid-unstructured) | | | +--ro data? binary | | +--ro active-duid? binary | | +--ro identity-association | | | +--ro iaid? uint32 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 327 | | | +--ro ia-type? string | | +--ro dhcp-server-identifier? inet:ip-address | | +--ro domain-name? string | | +--ro domain-name-servers* inet:ip-address | | +--ro interface-mtu? uint32 | | +--ro default-gateways* inet:ip-address | | +--ro netconf-clients* [client] | | | +--ro client netconf-client-id | | | +--ro optional-port? inet:port-number | | +--ro ca-ra-servers* [servers] | | | +--ro servers ca-ra-server-id | | | +--ro port-number? inet:port-number | | | +--ro ca-ra-path? string | | | +--ro subject-name? string | | | +--ro protocol? enumeration | | +--ro segw* [gateways] | | | +--ro gateways segw-id | | +--ro event-collectors* event-collector-id {or-feat:NON-PERSISTENT- MPLANE}? | | +--ro event-collector-format? enumeration {or-feat:NON-PERSISTENT-MPLANE}? | +--ro dhcpv6 | x--ro dhcp-client-identifier | | +--ro type-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | | +--ro duid-llt-hardware-type? uint16 | | | +--ro duid-llt-time? yang:timeticks | | | +--ro duid-llt-link-layer-addr? yang:mac-address | | +--:(duid-en) | | | +--ro duid-en-enterprise-number? uint32 | | | +--ro duid-en-identifier? string | | +--:(duid-ll) | | | +--ro duid-ll-hardware-type? uint16 | | | +--ro duid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--ro uuid? yang:uuid | | +--:(duid-unknown) | | +--ro data? binary | +--ro dhcpv6-client-identifier | | +--ro type-code? uint16 | | +--ro (duid-type)? | | | +--:(duid-llt) | | | | +--ro duid-llt-hardware-type? uint16 | | | | +--ro duid-llt-time? yang:timeticks | | | | +--ro duid-llt-link-layer-address? yang:mac-address | | | +--:(duid-en) | | | | +--ro duid-en-enterprise-number? uint32 | | | | +--ro duid-en-identifier? string | | | +--:(duid-ll) | | | | +--ro duid-ll-hardware-type? uint16 | | | | +--ro duid-ll-link-layer-address? yang:mac-address | | | +--:(duid-uuid) | | | | +--ro uuid? yang:uuid | | | +--:(duid-unstructured) | | | +--ro data? binary | | +--ro active-duid? binary | | +--ro identity-association | | +--ro iaid? uint32 | | +--ro ia-type? string | x--ro dhcp-server-identifier | | +--ro type-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | | +--ro duid-llt-hardware-type? uint16 | | | +--ro duid-llt-time? yang:timeticks | | | +--ro duid-llt-link-layer-addr? yang:mac-address | | +--:(duid-en) | | | +--ro duid-en-enterprise-number? uint32 | | | +--ro duid-en-identifier? string | | +--:(duid-ll) | | | +--ro duid-ll-hardware-type? uint16 | | | +--ro duid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--ro uuid? yang:uuid | | +--:(duid-unknown) | | +--ro data? binary | +--ro dhcpv6-server-identifier | | +--ro type-code? uint16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 328 | | +--ro (duid-type)? | | | +--:(duid-llt) | | | | +--ro duid-llt-hardware-type? uint16 | | | | +--ro duid-llt-time? yang:timeticks | | | | +--ro duid-llt-link-layer-address? yang:mac-address | | | +--:(duid-en) | | | | +--ro duid-en-enterprise-number? uint32 | | | | +--ro duid-en-identifier? string | | | +--:(duid-ll) | | | | +--ro duid-ll-hardware-type? uint16 | | | | +--ro duid-ll-link-layer-address? yang:mac-address | | | +--:(duid-uuid) | | | | +--ro uuid? yang:uuid | | | +--:(duid-unstructured) | | | +--ro data? binary | | +--ro active-duid? binary | +--ro domain-name? string | +--ro domain-name-servers* inet:ip-address | +--ro netconf-clients* [client] | | +--ro client netconf-client-id | | +--ro optional-port? inet:port-number | +--ro ca-ra-servers* [servers] | | +--ro servers ca-ra-server-id | | +--ro port-number? inet:port-number | | +--ro ca-ra-path? string | | +--ro subject-name? string | | +--ro protocol? enumeration | +--ro segw* [gateways] | | +--ro gateways segw-id | +--ro event-collectors* event-collector-id {or-feat:NON-PERSISTENT-MPLANE}? | +--ro event-collector-format? enumeration {or-feat:NON-PERSISTENT-MPLANE}? +--ro m-plane-dhcp x--ro private-enterprise-number? uint16 +--ro private-enterprise-num? uint32 +--ro vendor-class-data? string D.4.6 o-ran-externalio.yang module The format for the external input/output module is provided below. module: o-ran-externalio +--rw external-io +--ro input* [name] | +--ro name string | +--ro port-in? uint8 | +--ro line-in? boolean | +--ro related-o-ru-connector? -> /hw:hardware/component/name +--ro output* [name] | +--ro name string | +--ro port-out uint8 | +--ro related-o-ru-connector? -> /hw:hardware/component/name +--rw output-setting* [name] +--rw name -> /external-io/output/name +--rw line-out? boolean notifications: +---n external-input-change +--ro current-input-notification +--ro external-input* [name] +--ro name -> /external-io/input/name +--ro io-port? -> /external-io/input/port-in +--ro line-in? -> /external-io/input/line-in D.4.7 o-ran-ald-port.yang module The format for the Antenna Line Device module is provided below. module: o-ran-ald-port +--rw ald-ports-io +--ro over-current-supported? boolean +--ro ald-port* [name] | +--ro name string | +--ro port-id uint8 | +--ro dc-control-support boolean | +--ro dc-enabled-status? boolean ETSI ETSI TS 104 023 V17.1.0 (2026-01) 329 | +--ro supported-connector enumeration | +--ro related-o-ru-connectors* -> /hw:hardware/component/name +--rw ald-port-dc-control* [name] +--rw name -> /ald-ports-io/ald-port/name +--rw dc-enabled? boolean notifications: +---n overcurrent-report {OVERCURRENT-SUPPORTED}? | +--ro overload-condition | +--ro overloaded-ports* -> /ald-ports-io/ald-port/name | +--ro related-o-ru-connectors* -> /hw:hardware/component/name +---n dc-enabled-status-change +--ro ald-port* [name] +--ro name -> /ald-ports-io/ald-port/name +--ro dc-enabled-status? -> /ald-ports-io/ald-port/dc-enabled-status D.4.8 o-ran-ethernet-forwarding.yang module The format for the module o-ran Ethernet forwarding is provided below. module: o-ran-ethernet-forwarding +--rw ethernet-forwarding-table +--rw aging-time? uint32 +--ro filtering-entry* [address vlan-id] +--ro address yang:mac-address +--ro vlan-id uint16 +--ro port-map* [port-ref] +--ro port-ref -> /if:interfaces/interface/or-if:port-reference/port-number D.5 Sync folder D.5.1 o-ran-sync.yang module The format for the synchronization module is provided below. module: o-ran-sync +--rw sync +--ro sync-status | +--ro sync-state enumeration | +--ro time-error? decimal64 | +--ro frequency-error? decimal64 | +--ro supported-reference-types* [item] | +--ro item enumeration +--ro sync-capability | +--ro sync-t-tsc? enumeration | +--ro boundary-clock-supported? boolean | +--ro extended-ql-tlv-supported? boolean +--rw ptp-config | +--rw domain-number? uint8 | +--rw accepted-clock-classes* [clock-classes] | | +--rw clock-classes uint8 | +--rw ptp-profile? enumeration | +--rw delay-asymmetry? int16 | +--rw g-8275-1-config | | +--rw multicast-mac-address? enumeration | | x--rw delay-asymmetry? int16 | | +--rw sources* [local-port-number] {or-feat:PER-PORT-PTP-CONFIG}? | | +--rw local-port-number -> /if:interfaces/interface/o-ran-int:port- reference/port-number | | +--rw time-transmitter-only? boolean | | +--rw not-time-transmitter? boolean | | +--rw local-priority? uint8 | +--rw g-8275-2-config | +--rw local-ip-port? -> /if:interfaces/interface/name | +--rw master-ip-configuration* [local-priority] | | +--rw local-priority uint8 | | +--rw ip-address? string | +--rw log-inter-sync-period? int8 | +--rw log-inter-announce-period? int8 +--rw ptp-status | +--rw reporting-period? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 330 | +--ro lock-state? enumeration | +--ro clock-class? uint8 | +--ro clock-identity? string | +--ro partial-timing-supported? boolean | +--ro sources* [local-port-number] | +--ro local-port-number -> /if:interfaces/interface/o-ran-int:port- reference/port-number | +--ro state? enumeration | +--ro two-step-flag? boolean | +--ro leap61? boolean | +--ro leap59? boolean | +--ro current-utc-offset-valid? boolean | +--ro ptp-timescale? boolean | +--ro time-traceable? boolean | +--ro frequency-traceable? boolean | +--ro source-clock-identity? string | +--ro source-port-number? uint16 | +--ro current-utc-offset? int16 | +--ro priority1? uint8 | +--ro clock-class? uint8 | +--ro clock-accuracy? uint8 | +--ro offset-scaled-log-variance? uint16 | +--ro priority2? uint8 | +--ro grandmaster-clock-identity? string | +--ro steps-removed? uint16 | +--ro time-source? uint8 +--rw synce-config | +--rw acceptance-list-of-ssm* ssm-code | +--rw ssm-timeout? uint16 | +--rw sources* [local-port-number] {or-feat:PER-PORT-SYNCE-CONFIG}? | +--rw local-port-number -> /if:interfaces/interface/o-ran-int:port-reference/port- number | +--rw ssm-send-enable? boolean | +--rw local-priority? uint8 +--rw synce-status | +--rw reporting-period? uint8 | +--ro lock-state? enumeration | +--ro sources* [local-port-number] | +--ro local-port-number -> /if:interfaces/interface/o-ran-int:port- reference/port-number | +--ro state? enumeration | +--ro quality-level? uint8 | +--ro enhanced-ssm-code? uint8 | +--ro ssm-quality-level? ssm-code | +--ro originator-synce-clock-id? string | +--ro flag0-mixed-eec-eeec? boolean | +--ro flag1-partial-chain? boolean | +--ro number-of-eeec? uint8 | +--ro number-of-eec? uint8 +--rw gnss-config {GNSS}? | +--rw enable? boolean | +--rw satellite-constelation-list* enumeration | +--rw polarity? enumeration | +--rw cable-delay? uint16 | +--rw anti-jam-enable? boolean {ANTI-JAM}? +--rw gnss-status {GNSS}? +--rw reporting-period? uint8 +--ro name? string +--ro gnss-sync-status? enumeration +--ro gnss-data +--ro satellites-tracked? uint8 +--ro location | +--ro altitude? int64 | +--ro latitude? geographic-coordinate-degree | +--ro longitude? geographic-coordinate-degree +--ro gnss-rx-time-error? decimal64 notifications: +---n synchronization-state-change | +--ro sync-state? -> /sync/sync-status/sync-state +---n ptp-state-change | +--ro ptp-state? -> /sync/ptp-status/lock-state +---n synce-state-change | +--ro synce-state? -> /sync/synce-status/lock-state +---n gnss-state-change {GNSS}? +--ro gnss-state? -> /sync/gnss-status/gnss-sync-status ETSI ETSI TS 104 023 V17.1.0 (2026-01) 331 D.6 Radio folder D.6.1 o-ran-module-cap.yang module The format for the module capabilities module is provided below. module: o-ran-module-cap +--rw module-capability +--ro ru-capabilities | +--ro ru-supported-category? enumeration | x--ro number-of-ru-ports? uint8 | +--ro number-of-ru-ports-ul? uint8 | +--ro number-of-ru-ports-dl? uint8 | +--ro number-of-spatial-streams? uint8 | +--ro number-of-spatial-streams-dl? uint8 | +--ro number-of-spatial-streams-ul? uint8 | +--ro max-num-bands? uint16 | x--ro max-power-per-pa-antenna? decimal64 | x--ro min-power-per-pa-antenna? decimal64 | +--ro fronthaul-split-option? uint8 | +--ro format-of-iq-sample | | +--ro dynamic-compression-supported? boolean | | +--ro realtime-variable-bit-width-supported? boolean | | +--ro compression-method-supported* [] | | | +--ro iq-bitwidth? uint8 | | | +--ro compression-type compression-type-def | | | x--ro bitwidth? uint8 | | | +--ro compression-method? compression-method-def | | | x--ro (compression-format)? | | | | +--:(no-compresison) | | | | +--:(block-floating-point) | | | | | +--ro exponent? uint8 | | | | +--:(block-floating-point-selective-re-sending) | | | | | +--ro sres-exponent? uint8 | | | | +--:(block-scaling) | | | | | +--ro block-scalar? uint8 | | | | +--:(u-law) | | | | | +--ro comp-bit-width? uint8 | | | | | +--ro comp-shift? uint8 | | | | +--:(beam-space-compression) | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | +--ro block-scaler? uint8 | | | | +--:(modulation-compression) | | | | | +--ro csf? uint8 | | | | | +--ro mod-comp-scaler? uint16 | | | | +--:(modulation-compression-selective-re-sending) | | | | +--ro sres-csf? uint8 | | | | +--ro sres-mod-comp-scaler? uint16 | | | +--ro fs-offset* uint8 {cf:CONFIGURABLE-FS-OFFSET}? | | +--ro variable-bit-width-per-channel-supported? boolean | | +--ro syminc-supported? boolean | | +--ro regularization-factor-se-supported? boolean | | +--ro little-endian-supported? boolean | | +--ro st6-4byte-alignment-required? boolean | | +--ro se6-rb-bit-supported? boolean | +--ro ul-mixed-num-required-guard-rbs* [scs-a scs-b] | | +--ro scs-a scs-config-type | | +--ro scs-b scs-config-type | | +--ro number-of-guard-rbs-ul? uint8 | +--ro dl-mixed-num-required-guard-rbs* [scs-a scs-b] | | +--ro scs-a scs-config-type | | +--ro scs-b scs-config-type | | +--ro number-of-guard-rbs-dl? uint8 | +--ro energy-saving-by-transmission-blanks boolean | +--ro eaxcid-grouping-capabilities {o-ran-module-cap:EAXC-ID-GROUP-SUPPORTED}? | | +--ro max-num-tx-eaxc-id-groups? uint8 | | +--ro max-num-tx-eaxc-ids-per-group? uint8 | | +--ro max-num-rx-eaxc-id-groups? uint8 | | +--ro max-num-rx-eaxc-ids-per-group? uint8 | +--ro dynamic-transport-delay-management-supported boolean | +--ro support-only-unique-ecpri-seqid-per-eaxc? boolean | +--ro coupling-methods | | +--ro coupling-via-frequency-and-time? boolean | | +--ro coupling-via-frequency-and-time-with-priorities? boolean ETSI ETSI TS 104 023 V17.1.0 (2026-01) 332 | | +--ro coupling-via-frequency-and-time-with-priorities-optimized? boolean | +--ro ud-comp-len-supported? boolean | +--ro ext-ant-delay-capability? enumeration {or-feat:EXT-ANT-DELAY- CONTROL}? | +--ro nack-supported? boolean | +--ro st8-scs-supported? boolean | +--ro energy-saving-capability-common-info {or-feat:TRX-CONTROL or or-feat:ADVANCED-SLEEP- MODE}? | | +--ro st8-ready-message-supported? boolean | | +--ro sleep-duration-extension-supported? boolean | | +--ro emergency-wake-up-command-supported? boolean | +--ro bundle-offset-in-se11-supported? boolean | +--ro max-beamId-tables-supported? uint8 {or-feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | +--ro min-hibernate-time-duration? uint32 {or-feat:DEEP-HIBERNATE}? | +--ro max-hibernate-time-duration uint32 {or-feat:DEEP-HIBERNATE}? +--ro band-capabilities* [band-number] | +--ro band-number uint16 | +--ro sub-band-info {o-ran-module-cap:LAA}? | | +--ro sub-band-frequency-ranges* [sub-band] | | | +--ro sub-band sub-band-string | | | +--ro max-supported-frequency-dl? uint64 | | | +--ro min-supported-frequency-dl? uint64 | | +--ro number-of-laa-scarriers? uint8 | | +--ro maximum-laa-buffer-size? uint16 | | +--ro maximum-processing-time? uint16 | | +--ro self-configure? boolean | +--ro max-supported-frequency-dl? uint64 | +--ro min-supported-frequency-dl? uint64 | +--ro max-supported-bandwidth-dl? uint64 | +--ro max-num-carriers-dl? uint32 | +--ro max-carrier-bandwidth-dl? uint64 | +--ro min-carrier-bandwidth-dl? uint64 | +--ro supported-technology-dl* enumeration | +--ro supported-filter-pass-bandwidths-dl | | +--ro supported-filter-pass-bandwidths* [id] | | +--ro id uint32 | | +--ro type? enumeration | | +--ro carrier-bandwidth? uint64 | | +--ro filter-pass-bandwidth? uint64 | +--ro tx-array-beamId-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | +--ro max-supported-frequency-ul? uint64 | +--ro min-supported-frequency-ul? uint64 | +--ro max-supported-bandwidth-ul? uint64 | +--ro max-num-carriers-ul? uint32 | +--ro max-carrier-bandwidth-ul? uint64 | +--ro min-carrier-bandwidth-ul? uint64 | +--ro supported-technology-ul* enumeration | +--ro supported-filter-pass-bandwidths-ul | | +--ro supported-filter-pass-bandwidths* [id] | | +--ro id uint32 | | +--ro type? enumeration | | +--ro carrier-bandwidth? uint64 | | +--ro filter-pass-bandwidth? uint64 | +--ro rx-array-beamId-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | +--ro max-num-component-carriers? uint8 | x--ro max-num-bands? uint16 | +--ro max-num-sectors? uint8 | x--ro max-power-per-antenna? decimal64 | x--ro min-power-per-antenna? decimal64 | x--ro codebook-configuration_ng? uint8 | x--ro codebook-configuration_n1? uint8 | x--ro codebook-configuration_n2? uint8 +--rw rw-sub-band-info {o-ran-module-cap:LAA}? +--rw rw-number-of-laa-scarriers? -> /module-capability/band-capabilities/sub-band- info/number-of-laa-scarriers +--rw rw-self-configure? -> /module-capability/band-capabilities/sub-band- info/self-configure ETSI ETSI TS 104 023 V17.1.0 (2026-01) 333 D.6.2 o-ran-delay-management.yang module The format for the delay management module is provided below. module: o-ran-delay-management +--rw delay-management +--rw bandwidth-scs-delay-state* [bandwidth subcarrier-spacing] | +--rw bandwidth bandwidth | +--rw subcarrier-spacing uint32 | +--ro ru-delay-profile | +--ro t2a-min-up uint32 | +--ro t2a-max-up uint32 | +--ro t2a-min-cp-dl uint32 | +--ro t2a-max-cp-dl uint32 | +--ro tcp-adv-dl uint32 | +--ro ta3-min uint32 | +--ro ta3-max uint32 | +--ro t2a-min-cp-ul uint32 | +--ro t2a-max-cp-ul uint32 | +--ro ta3-min-ack? int32 | +--ro ta3-max-ack? int32 | +--ro ta3-min-2g? uint32 {feat:RRM-MEAS-REPORTING}? | +--ro ta3-max-2g? uint32 {feat:RRM-MEAS-REPORTING}? +--rw non-default-ru-delay-profile* [delay-profile-id] {feat:BF-DELAY-PROFILE}? | +--rw delay-profile-id uint16 | +--rw non-default-bandwidth-scs-delay-state* [bandwidth subcarrier-spacing] | +--rw bandwidth bandwidth | +--rw subcarrier-spacing uint32 | +--ro non-default-ru-delay-profile | +--ro t2a-min-up? uint32 | +--ro t2a-max-up? uint32 | +--ro t2a-min-cp-dl? uint32 | +--ro t2a-max-cp-dl? uint32 | +--ro tcp-adv-dl? uint32 | +--ro ta3-min? uint32 | +--ro ta3-max? uint32 | +--ro t2a-min-cp-ul? uint32 | +--ro t2a-max-cp-ul? uint32 | +--ro ta3-min-ack? int32 | +--ro ta3-max-ack? int32 | +--ro ta3-min-2g? uint32 {feat:RRM-MEAS-REPORTING}? | +--ro ta3-max-2g? uint32 {feat:RRM-MEAS-REPORTING}? +--rw adaptive-delay-configuration {ADAPTIVE-RU-PROFILE}? | +--rw bandwidth-scs-delay-state* [bandwidth subcarrier-spacing] | | +--rw bandwidth bandwidth | | +--rw subcarrier-spacing uint32 | | +--rw o-du-delay-profile | | +--rw t1a-max-up? uint32 | | +--rw tx-max? uint32 | | +--rw ta4-max? uint32 | | +--rw rx-max? uint32 | | +--rw t1a-max-cp-dl? uint32 | +--rw transport-delay | +--rw t12-min? uint32 | +--rw t12-max? uint32 | +--rw t34-min? uint32 | +--rw t34-max? uint32 +--rw beam-context-gap-period? uint16 D.6.3 o-ran-beamforming.yang module The format for the beamforming module is provided below. module: o-ran-beamforming +--ro beamforming-config x--ro per-band-config* [band-number] | +--ro band-number -> /mcap:module-capability/band-capabilities/band-number | +--ro tx-array* -> /up:user-plane-configuration/tx-arrays/name | +--ro rx-array* -> /up:user-plane-configuration/rx-arrays/name | +--ro static-properties | | +--ro rt-bf-weights-update-support? boolean | | +--ro (beamforming-type)? | | | +--:(frequency) | | | | +--ro frequency-domain-beams | | | | +--ro max-number-of-beam-ids uint16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 334 | | | | +--ro initial-beam-id uint16 | | | | +--ro iq-bitwidth? uint8 | | | | +--ro compression-type compression-type-def | | | | x--ro bitwidth? uint8 | | | | +--ro compression-method? bf-compression-method-def | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro additional-compression-method-supported* [] | | | | | +--ro iq-bitwidth? uint8 | | | | | +--ro compression-type compression-type-def | | | | | x--ro bitwidth? uint8 | | | | | +--ro compression-method? bf-compression-method-def | | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | +--:(time) | | | | +--ro time-domain-beams | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | | +--ro frequency-granularity enumeration | | | | +--ro time-granularity enumeration | | | | +--ro iq-bitwidth? uint8 | | | | +--ro compression-type compression-type-def | | | | x--ro bitwidth? uint8 | | | | +--ro compression-method? bf-compression-method-def | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 335 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro additional-compression-method-supported* [] | | | | | +--ro iq-bitwidth? uint8 | | | | | +--ro compression-type compression-type-def | | | | | x--ro bitwidth? uint8 | | | | | +--ro compression-method? bf-compression-method-def | | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | +--:(hybrid) | | | +--ro hybrid-beams | | | +--ro max-number-of-beam-ids uint16 | | | +--ro initial-beam-id uint16 | | | +--ro frequency-granularity enumeration | | | +--ro time-granularity enumeration | | | +--ro iq-bitwidth? uint8 | | | +--ro compression-type compression-type-def | | | x--ro bitwidth? uint8 | | | +--ro compression-method? bf-compression-method-def | | | x--ro (compression-format)? | | | | +--:(no-compresison) | | | | +--:(block-floating-point) | | | | | +--ro exponent? uint8 | | | | +--:(block-floating-point-selective-re-sending) | | | | | +--ro sres-exponent? uint8 | | | | +--:(block-scaling) | | | | | +--ro block-scalar? uint8 | | | | +--:(u-law) | | | | | +--ro comp-bit-width? uint8 | | | | | +--ro comp-shift? uint8 | | | | +--:(beam-space-compression) | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | +--ro block-scaler? uint8 | | | | +--:(modulation-compression) | | | | | +--ro csf? uint8 | | | | | +--ro mod-comp-scaler? uint16 | | | | +--:(modulation-compression-selective-re-sending) | | | | +--ro sres-csf? uint8 | | | | +--ro sres-mod-comp-scaler? uint16 | | | +--ro additional-compression-method-supported* [] | | | | +--ro iq-bitwidth? uint8 | | | | +--ro compression-type compression-type-def | | | | x--ro bitwidth? uint8 | | | | +--ro compression-method? bf-compression-method-def | | | | x--ro (compression-format)? | | | | +--:(no-compresison) | | | | +--:(block-floating-point) | | | | | +--ro exponent? uint8 | | | | +--:(block-floating-point-selective-re-sending) | | | | | +--ro sres-exponent? uint8 | | | | +--:(block-scaling) | | | | | +--ro block-scalar? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 336 | | | | +--:(u-law) | | | | | +--ro comp-bit-width? uint8 | | | | | +--ro comp-shift? uint8 | | | | +--:(beam-space-compression) | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | +--ro block-scaler? uint8 | | | | +--:(modulation-compression) | | | | | +--ro csf? uint8 | | | | | +--ro mod-comp-scaler? uint16 | | | | +--:(modulation-compression-selective-re-sending) | | | | +--ro sres-csf? uint8 | | | | +--ro sres-mod-comp-scaler? uint16 | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | +--ro fd-weights-mapping* [fd-weight-number] | | | +--ro fd-weight-number uint16 | | | +--ro array-elements* uint16 | | x--ro number-of-beams? uint16 | | +--ro p-dash? uint16 | +--ro beam-information | +--ro number-of-beamforming-properties? uint16 | +--ro beamforming-properties* [beam-id] | +--ro beam-id uint16 | +--ro beamforming-property | +--ro beam-type? enumeration | +--ro beam-group-id? uint16 | x--ro coarse-fine-beam-relation* beam-reference | x--ro neighbour-beams* beam-reference | +--ro coarse-fine-beam-capability-based-relation* beam-capabilities-reference | +--ro neighbour-beams-capability-based* beam-capabilities-reference +--ro capabilities-groups* [capabilities-group] | +--ro capabilities-group uint16 | +--ro band-number? -> /mcap:module-capability/band-capabilities/band-number | +--ro tx-array* -> /up:user-plane-configuration/tx-arrays/name | +--ro rx-array* -> /up:user-plane-configuration/rx-arrays/name | +--ro static-properties | | +--ro rt-bf-weights-update-support? boolean | | +--ro (beamforming-type)? | | | +--:(frequency) | | | | +--ro frequency-domain-beams | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | | +--ro iq-bitwidth? uint8 | | | | +--ro compression-type compression-type-def | | | | x--ro bitwidth? uint8 | | | | +--ro compression-method? bf-compression-method-def | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro additional-compression-method-supported* [] | | | | | +--ro iq-bitwidth? uint8 | | | | | +--ro compression-type compression-type-def | | | | | x--ro bitwidth? uint8 | | | | | +--ro compression-method? bf-compression-method-def | | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) ETSI ETSI TS 104 023 V17.1.0 (2026-01) 337 | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | +--:(time) | | | | +--ro time-domain-beams | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | | +--ro frequency-granularity enumeration | | | | +--ro time-granularity enumeration | | | | +--ro iq-bitwidth? uint8 | | | | +--ro compression-type compression-type-def | | | | x--ro bitwidth? uint8 | | | | +--ro compression-method? bf-compression-method-def | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro additional-compression-method-supported* [] | | | | | +--ro iq-bitwidth? uint8 | | | | | +--ro compression-type compression-type-def | | | | | x--ro bitwidth? uint8 | | | | | +--ro compression-method? bf-compression-method-def | | | | | x--ro (compression-format)? | | | | | +--:(no-compresison) | | | | | +--:(block-floating-point) | | | | | | +--ro exponent? uint8 | | | | | +--:(block-floating-point-selective-re-sending) | | | | | | +--ro sres-exponent? uint8 | | | | | +--:(block-scaling) | | | | | | +--ro block-scalar? uint8 | | | | | +--:(u-law) | | | | | | +--ro comp-bit-width? uint8 | | | | | | +--ro comp-shift? uint8 | | | | | +--:(beam-space-compression) | | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | | +--ro block-scaler? uint8 | | | | | +--:(modulation-compression) | | | | | | +--ro csf? uint8 | | | | | | +--ro mod-comp-scaler? uint16 | | | | | +--:(modulation-compression-selective-re-sending) | | | | | +--ro sres-csf? uint8 | | | | | +--ro sres-mod-comp-scaler? uint16 | | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 338 | | | +--:(hybrid) | | | +--ro hybrid-beams | | | +--ro max-number-of-beam-ids uint16 | | | +--ro initial-beam-id uint16 | | | +--ro frequency-granularity enumeration | | | +--ro time-granularity enumeration | | | +--ro iq-bitwidth? uint8 | | | +--ro compression-type compression-type-def | | | x--ro bitwidth? uint8 | | | +--ro compression-method? bf-compression-method-def | | | x--ro (compression-format)? | | | | +--:(no-compresison) | | | | +--:(block-floating-point) | | | | | +--ro exponent? uint8 | | | | +--:(block-floating-point-selective-re-sending) | | | | | +--ro sres-exponent? uint8 | | | | +--:(block-scaling) | | | | | +--ro block-scalar? uint8 | | | | +--:(u-law) | | | | | +--ro comp-bit-width? uint8 | | | | | +--ro comp-shift? uint8 | | | | +--:(beam-space-compression) | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | +--ro block-scaler? uint8 | | | | +--:(modulation-compression) | | | | | +--ro csf? uint8 | | | | | +--ro mod-comp-scaler? uint16 | | | | +--:(modulation-compression-selective-re-sending) | | | | +--ro sres-csf? uint8 | | | | +--ro sres-mod-comp-scaler? uint16 | | | +--ro additional-compression-method-supported* [] | | | | +--ro iq-bitwidth? uint8 | | | | +--ro compression-type compression-type-def | | | | x--ro bitwidth? uint8 | | | | +--ro compression-method? bf-compression-method-def | | | | x--ro (compression-format)? | | | | +--:(no-compresison) | | | | +--:(block-floating-point) | | | | | +--ro exponent? uint8 | | | | +--:(block-floating-point-selective-re-sending) | | | | | +--ro sres-exponent? uint8 | | | | +--:(block-scaling) | | | | | +--ro block-scalar? uint8 | | | | +--:(u-law) | | | | | +--ro comp-bit-width? uint8 | | | | | +--ro comp-shift? uint8 | | | | +--:(beam-space-compression) | | | | | +--ro active-beam-space-coeficient-mask* uint8 | | | | | +--ro block-scaler? uint8 | | | | +--:(modulation-compression) | | | | | +--ro csf? uint8 | | | | | +--ro mod-comp-scaler? uint16 | | | | +--:(modulation-compression-selective-re-sending) | | | | +--ro sres-csf? uint8 | | | | +--ro sres-mod-comp-scaler? uint16 | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES- SUPPORTED}? | | | | +--ro max-number-of-beam-ids uint16 | | | | +--ro initial-beam-id uint16 | | | +--ro fd-weights-mapping* [fd-weight-number] | | | +--ro fd-weight-number uint16 | | | +--ro array-elements* uint16 | | x--ro number-of-beams? uint16 | | +--ro p-dash? uint16 | +--ro beam-information | +--ro number-of-beamforming-properties? uint16 | +--ro beamforming-properties* [beam-id] | +--ro beam-id uint16 | +--ro beamforming-property | +--ro beam-type? enumeration | +--ro beam-group-id? uint16 | x--ro coarse-fine-beam-relation* beam-reference | x--ro neighbour-beams* beam-reference | +--ro coarse-fine-beam-capability-based-relation* beam-capabilities-reference | +--ro neighbour-beams-capability-based* beam-capabilities-reference +--ro ue-specific-beamforming! | x--ro max-number-of-ues? uint8 | +--ro max-number-of-ues-15bit? uint16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 339 | +--ro channel-information-compression-method-supported* cf:ci-compression-method-def {feat:CHANNEL-INFORMATION-COMPRESSION}? | +--ro dynamic-channel-information-compression-supported? boolean {feat:CHANNEL- INFORMATION-COMPRESSION}? +--ro operational-properties {MODIFY-BF-CONFIG}? | +--ro number-of-writeable-beamforming-files uint8 | +--ro update-bf-non-delete? boolean | +--ro persistent-bf-files? boolean | +--ro in-service-bf-update? boolean +--ro dmrs-bf-general-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | +--ro equalization-data-scaling? EQ-SCALING-FUNCTION-TYPE {feat:DMRS-BF-EQ}? | +--ro max-num-ues-supported? uint16 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | +--ro ueid-max-layer-bits? uint8 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? | +--ro max-num-ueids? uint16 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? +--ro beamforming-trough-attributes-supported? boolean +--ro beamforming-trough-ue-channel-info-supported? boolean +--ro beam-tilt {BEAM-TILT}? +--ro predefined-beam-tilt-offset-information* [capabilities-group] | +--ro capabilities-group -> /beamforming-config/capabilities- groups/capabilities-group | +--ro elevation-tilt-offset-granularity uint8 | +--ro azimuth-tilt-offset-granularity uint8 | +--ro minimum-supported-elevation-tilt-offset int16 | +--ro maximum-supported-elevation-tilt-offset int16 | +--ro minimum-supported-azimuth-tilt-offset int16 | +--ro maximum-supported-azimuth-tilt-offset int16 | +--ro run-time-tilt-offset-supported boolean +--ro predefined-beam-tilt-state* [capabilities-group] +--ro capabilities-group -> /beamforming-config/capabilities- groups/capabilities-group +--ro elevation-tilt-offset-angle int16 +--ro azimuth-tilt-offset-angle int16 rpcs: x---x activate-beamforming-config {MODIFY-BF-CONFIG}? | +---w input | | +---w beamforming-config-file string | | +---w band-number? -> /mcap:module-capability/band-capabilities/band-number | +--ro output | +--ro status enumeration | +--ro error-message? string +---x activate-beamforming-config-by-capability-group {MODIFY-BF-CONFIG}? | +---w input | | +---w beamforming-config-file string | | +---w capabilities-group -> /beamforming-config/capabilities-groups/capabilities- group | +--ro output | +--ro status enumeration | +--ro error-message? string +---x modify-predefined-beam-tilt-offset {BEAM-TILT}? +---w input | +---w predefined-beam-tilt-offset* [capabilities-group] {BEAM-TILT}? | +---w capabilities-group -> /beamforming-config/capabilities- groups/capabilities-group | +---w elevation-tilt-offset-angle? int16 | +---w azimuth-tilt-offset-angle? int16 +--ro output +--ro status enumeration +--ro error-message? string notifications: x---n beamforming-information-update | +--ro band-number? -> /mcap:module-capability/band-capabilities/band-number +---n capability-group-beamforming-information-update | +--ro capabilities-group -> /beamforming-config/capabilities-groups/capabilities-group +---n predefined-beam-tilt-offset-complete {BEAM-TILT}? +--ro predefined-beam-tilt-state* [capabilities-group] +--ro capabilities-group -> /beamforming-config/capabilities- groups/capabilities-group +--ro elevation-tilt-offset-angle int16 +--ro azimuth-tilt-offset-angle int16 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 340 D.6.4 o-ran-laa.yang module The format for the LAA module is provided below. module: o-ran-laa +--rw laa-config! +--rw number-of-laa-scarriers? uint8 +--rw multi-carrier-type? enumeration +--rw multi-carrier-tx? boolean +--rw multi-carrier-freeze? boolean +--rw laa-ending-dwpts-supported? boolean +--rw laa-starting-in-second-slot-supported? boolean D.6.5 o-ran-antenna-calibration.yang module The format for the antenna calibration module is provided below. module: o-ran-antenna-calibration +--rw antenna-calibration +--ro antenna-calibration-capabilities | +--ro self-calibration-support? boolean | +--ro coordinated-calibration-support? boolean {O-RU-COORDINATED-ANT-CAL}? | +--ro number-of-calibration-symbols-per-block-dl uint8 | +--ro number-of-calibration-symbols-per-block-ul uint8 | +--ro interval-between-calibration-blocks? uint8 | +--ro number-of-calibration-blocks-per-step-dl uint8 | +--ro number-of-calibration-blocks-per-step-ul uint8 | +--ro interval-between-calibration-steps? uint8 | +--ro number-of-calibration-steps uint8 | +--ro calibration-period? uint16 {O-RU-COORDINATED-ANT-CAL}? | +--ro configured-preparation-timer-supported? boolean {O-RU-COORDINATED-ANT-CAL}? +--rw self-calibration-policy | +--rw self-calibration-allowed? boolean | +--rw coordinated-calibration-allowed? boolean {O-RU-COORDINATED- ANT-CAL}? | +--rw coordinated-ant-calib-prep-timer? uint8 {O-RU-COORDINATED- ANT-CAL}? | +--rw coordinated-calibration-multiple-time-resources-allowed? boolean {O-RU-COORDINATED- ANT-CAL and O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE}? +--ro antenna-calibration-multiple-time-resource {O-RU-COORDINATED-ANT-CAL and O-RU- COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE}? +--ro antenna-calibration-multiple-time-resource-list* [antenna-calibration-time-resource- index] +--ro number-of-calibration-symbols-per-block-dl uint8 +--ro number-of-calibration-symbols-per-block-ul uint8 +--ro interval-between-calibration-blocks? uint8 +--ro number-of-calibration-blocks-per-step-dl uint8 +--ro number-of-calibration-blocks-per-step-ul uint8 +--ro interval-between-calibration-steps? uint8 +--ro number-of-calibration-steps uint8 +--ro calibration-period? uint16 {O-RU-COORDINATED-ANT-CAL}? +--ro antenna-calibration-time-resource-index uint8 rpcs: +---x start-antenna-calibration +---w input | +---w symbol-bitmask-dl string | +---w symbol-bitmask-ul string | +---w slot-bitmask-dl string | +---w slot-bitmask-ul string | +---w frame-bitmask-dl string | +---w frame-bitmask-ul string | +---w calibration-step-size uint8 | +---w calibration-step-number uint8 | +---w start-sfn uint16 +--ro output +--ro status enumeration +--ro error-message? string notifications: +---n antenna-calibration-required | +--ro dl-calibration-frequency-chunk* [] | | +--ro start-calibration-frequency-dl? uint64 | | +--ro end-calibration-frequency-dl? uint64 | +--ro ul-calibration-frequency-chunk* [] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 341 | +--ro start-calibration-frequency-ul? uint64 | +--ro end-calibration-frequency-ul? uint64 +---n antenna-calibration-coordinated {O-RU-COORDINATED-ANT-CAL}? | +--ro dl-calibration-frequency-chunk* [] | | +--ro start-calibration-frequency-dl? uint64 | | +--ro end-calibration-frequency-dl? uint64 | +--ro ul-calibration-frequency-chunk* [] | | +--ro start-calibration-frequency-ul? uint64 | | +--ro end-calibration-frequency-ul? uint64 | +--ro symbol-bitmask-dl string | +--ro symbol-bitmask-ul string | +--ro slot-bitmask-dl string | +--ro slot-bitmask-ul string | +--ro frame-bitmask-dl string | +--ro frame-bitmask-ul string | +--ro calibration-step-size uint8 | +--ro calibration-step-number uint8 | +--ro start-sfn uint16 +---n antenna-calibration-result | +--ro status enumeration | +--ro detailed-reason? string +---n antenna-calibration-multiple-time-resource-params {O-RU-COORDINATED-ANT-CAL and O-RU- COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE}? +--ro antenna-calibration-time-resource-index? uint8 +--ro dl-calibration-frequency-chunk* [] | +--ro start-calibration-frequency-dl? uint64 | +--ro end-calibration-frequency-dl? uint64 +--ro ul-calibration-frequency-chunk* [] +--ro start-calibration-frequency-ul? uint64 +--ro end-calibration-frequency-ul? uint64 D.6.6 o-ran-shared-cell.yang module The format for the module o-ran shared cell is provided below. module: o-ran-shared-cell +--rw shared-cell +--ro shared-cell-module-cap | +--ro t-copy uint32 | +--ro t-combine uint32 | +--ro t-combine-net? uint32 | +--ro scs-supported* o-ran-cmn:scs-config-type {FHM}? | +--ro combine-delay-per-scs* [scs] | | +--ro scs o-ran-cmn:scs-config-type | | +--ro t-combine-net? uint32 | | +--ro t-combine? uint32 | +--ro ta3-prime-max-upper-range uint32 | +--ro max-number-node-copy-and-combine uint8 | +--ro max-number-eaxcid-copy uint8 | +--ro max-number-eaxcid-combine uint8 | +--ro copy-combine-capacity-per-port* [port-number] | | +--ro port-number -> /if:interfaces/interface/o-ran-int:port- reference/port-number | | +--ro copy-combine-capacity-type-id? -> ../../copy-combine-capacity-type/id | +--ro copy-combine-capacity-type* [id] | | +--ro id uint8 | | +--ro max-num-of-nodes-combine-in-port? uint8 | | +--ro max-num-of-eaxc-id-combine-in-port? uint16 | +--ro eaxc-id-group-capabilities {FHM}? | | +--ro max-num-rx-eaxc-id-groups? uint8 | | +--ro max-num-rx-eaxc-ids-per-group? uint8 | +--ro compression-method-supported* [] {FHM}? | | +--ro iq-bitwidth? uint8 | | +--ro compression-type compression-type-def | | x--ro bitwidth? uint8 | | +--ro compression-method? compression-method-def | | x--ro (compression-format)? | | +--:(no-compresison) | | +--:(block-floating-point) | | | +--ro exponent? uint8 | | +--:(block-floating-point-selective-re-sending) | | | +--ro sres-exponent? uint8 | | +--:(block-scaling) | | | +--ro block-scalar? uint8 | | +--:(u-law) | | | +--ro comp-bit-width? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 342 | | | +--ro comp-shift? uint8 | | +--:(beam-space-compression) | | | +--ro active-beam-space-coeficient-mask* uint8 | | | +--ro block-scaler? uint8 | | +--:(modulation-compression) | | | +--ro csf? uint8 | | | +--ro mod-comp-scaler? uint16 | | +--:(modulation-compression-selective-re-sending) | | +--ro sres-csf? uint8 | | +--ro sres-mod-comp-scaler? uint16 | +--ro multi-cell-in-cascade-mode-supported? boolean +--rw shared-cell-config +--rw (shared-cell-copy-combine-mode)? | +--:(COMMON) | | +--rw shared-cell-copy-entities* [name] | | | +--rw name string | | | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? | | | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED- ORU-MULTI-OPERATOR}? | | | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- elements/name | | | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- elements/name | | | +--rw shared-cell-copy-uplane-config {FHM}? | | | +--rw tx-eaxc-id* [eaxc-id] | | | | +--rw eaxc-id uint16 | | | +--rw rx-eaxc-id* [eaxc-id] | | | | +--rw eaxc-id uint16 | | | x--rw downlink-radio-frame-offset? uint32 | | | x--rw downlink-sfn-offset? int16 | | +--rw shared-cell-combine-entities* [name] | | +--rw name string | | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? | | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? | | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- elements/name | | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- elements/name | | +--rw scs? o-ran-cmn:scs-config-type | | +--rw ta3-prime-max? uint32 | | +--rw tx-duration? uint32 | | +--rw shared-cell-combine-uplane-config {FHM}? | | +--rw rx-eaxc-id* [eaxc-id] | | | +--rw eaxc-id uint16 | | | +--rw number-of-prb? uint16 | | | +--rw cp-ul-section-type* enumeration | | | +--rw comression-method | | | +--rw iq-bitwidth? uint8 | | | +--rw compression-type compression-type-def | | | x--rw bitwidth? uint8 | | | +--rw compression-method? compression-method-def | | | x--rw (compression-format)? | | | +--:(no-compresison) | | | +--:(block-floating-point) | | | | +--rw exponent? uint8 | | | +--:(block-floating-point-selective-re-sending) | | | | +--rw sres-exponent? uint8 | | | +--:(block-scaling) | | | | +--rw block-scalar? uint8 | | | +--:(u-law) | | | | +--rw comp-bit-width? uint8 | | | | +--rw comp-shift? uint8 | | | +--:(beam-space-compression) | | | | +--rw active-beam-space-coeficient-mask* uint8 | | | | +--rw block-scaler? uint8 | | | +--:(modulation-compression) | | | | +--rw csf? uint8 | | | | +--rw mod-comp-scaler? uint16 | | | +--:(modulation-compression-selective-re-sending) | | | +--rw sres-csf? uint8 | | | +--rw sres-mod-comp-scaler? uint16 | | +--rw downlink-radio-frame-offset uint32 | | +--rw downlink-sfn-offset int16 | | +--rw n-ta-offset uint32 | | x--rw number-of-prb uint16 | +--:(SELECTIVE-BEAM-ID) {FHM and SELECTIVE-BEAM-ID}? | +--rw shared-cell-copy-entities-selective-beam-id* [name] ETSI ETSI TS 104 023 V17.1.0 (2026-01) 343 | | +--rw name string | | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? | | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? | | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- elements/name | | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- elements/name | | +--rw mapping-table-for-selective-beam-id* [global-beam-id south-node-processing- elements] | | | +--rw global-beam-id uint16 | | | +--rw south-node-processing-elements -> /o-ran-pe:processing-elements/ru- elements/name | | | +--rw local-beam-id? uint16 | | +--rw shared-cell-copy-uplane-config {FHM}? | | +--rw tx-eaxc-id* [eaxc-id] | | | +--rw eaxc-id uint16 | | +--rw rx-eaxc-id* [eaxc-id] | | | +--rw eaxc-id uint16 | | x--rw downlink-radio-frame-offset? uint32 | | x--rw downlink-sfn-offset? int16 | +--rw shared-cell-combine-entities-for-selective-beam-id* [name] | +--rw name string | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- elements/name | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- elements/name | +--rw scs? o-ran-cmn:scs-config-type | +--rw ta3-prime-max? uint32 | +--rw tx-duration? uint32 | +--rw shared-cell-combine-uplane-config {FHM}? | +--rw rx-eaxc-id* [eaxc-id] | | +--rw eaxc-id uint16 | | +--rw number-of-prb? uint16 | | +--rw cp-ul-section-type* enumeration | | +--rw comression-method | | +--rw iq-bitwidth? uint8 | | +--rw compression-type compression-type-def | | x--rw bitwidth? uint8 | | +--rw compression-method? compression-method-def | | x--rw (compression-format)? | | +--:(no-compresison) | | +--:(block-floating-point) | | | +--rw exponent? uint8 | | +--:(block-floating-point-selective-re-sending) | | | +--rw sres-exponent? uint8 | | +--:(block-scaling) | | | +--rw block-scalar? uint8 | | +--:(u-law) | | | +--rw comp-bit-width? uint8 | | | +--rw comp-shift? uint8 | | +--:(beam-space-compression) | | | +--rw active-beam-space-coeficient-mask* uint8 | | | +--rw block-scaler? uint8 | | +--:(modulation-compression) | | | +--rw csf? uint8 | | | +--rw mod-comp-scaler? uint16 | | +--:(modulation-compression-selective-re-sending) | | +--rw sres-csf? uint8 | | +--rw sres-mod-comp-scaler? uint16 | +--rw downlink-radio-frame-offset uint32 | +--rw downlink-sfn-offset int16 | +--rw n-ta-offset uint32 | x--rw number-of-prb uint16 +--rw max-num-rx-eaxc-ids-per-group? -> /shared-cell/shared- cell-module-cap/eaxc-id-group-capabilities/max-num-rx-eaxc-ids-per-group {FHM}? +--rw max-num-rx-eaxc-id-groups? -> /shared-cell/shared- cell-module-cap/eaxc-id-group-capabilities/max-num-rx-eaxc-id-groups {FHM}? +--rw rx-eaxc-id-group* [representative-rx-eaxc-id] {FHM}? | +--rw representative-rx-eaxc-id uint16 | +--rw member-rx-eaxc-id* uint16 +--rw enhanced-t-combine-enabled? boolean {feat:ENHANCED-T- COMBINE}? +--rw multiple-scs-in-eaxc-used? boolean {feat:MULTIPLE- SCS-IN-EAXC}? ETSI ETSI TS 104 023 V17.1.0 (2026-01) 344 D.6.7 o-ran-laa-operations.yang module The format for the LAA operations module is provided below. rpcs: rpcs: +---x start-measurements {mcap:LAA}? +---w input | +---w band-config* [band-number] | | +---w band-number band-num | | +---w channel-center-frequency* uint16 | +---w duration-per-channel? uint16 | +---w maximum-response-time? uint16 +--ro output +--ro band-config* [band-number] +--ro band-number band-num +--ro carrier-center-frequency* uint16 +--ro status? enumeration +--ro error-message? string notifications: +---n measurement-result {mcap:LAA}? +--ro band-result* [band-number] +--ro band-number band-num +--ro measurement-success? boolean +--ro failure-message? enumeration +--ro channel-result* [measured-channel] +--ro measured-channel uint16 +--ro occupancy-ratio? uint8 +--ro average-rssi? int8 D.6.8 o-ran-frequency-band-measurement.yang module The format for the frequency band measurement module is provided below. module: o-ran-frequency-band-measurement +--ro measurement-capability +--ro measurement-bands-supported* [measurement-band-num] | +--ro measurement-band-num uint8 | +--ro frequencys-range-supported* [lower-frequency] | | +--ro lower-frequency uint32 | | +--ro upper-frequency? uint32 | +--ro measurement-bandwidth* measurement-bandwidth +--ro in-service-measurement? boolean +--ro in-service-measurement-only-carrier-freq? boolean +--ro supported-measurement-points* enumeration rpcs: +---x received-power-measurement-request +---w input | +---w measurement-bandwidth measurement-bandwidth | +---w measurement-start-frequency* uint32 | +---w rx-array* -> /up:user-plane-configuration/rx-arrays/name +--ro output +--ro status enumeration +--ro error-message? string +--ro wait-time? uint32 +--ro measurement-id? uint8 notifications: +---n power-measurement-result +--ro status enumeration +--ro error-message? string +--ro received-power-measurement* [measurement-frequency] | +--ro measurement-frequency uint32 | +--ro measurement-bandwidth measurement-bandwidth | +--ro received-power? decimal64 +--ro measurement-id? uint8 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 345 Annex E (normative): Corresponding YANG Module Definition The definitions for each method and resource defined in the clauses of the present document include normative references to schema nodes, notifications and remote procedure calls (RPCs) defined in a set of corresponding YANG models. The YANG models for present document are available in the file O-RAN.WG4.MP-YANGs-R004-v17.01.zip which can be downloaded from the O-RAN Alliance website http://www.o-ran.org/specifications/. If there is any conflict between the schema nodes, notifications and Remote Procedure Calls (RPCs) defined in the YANG models and the accompanying description in the present document, the definition of the YANG models shall take precedence. Table E-1 lists all of the O-RAN Alliance YANG models included in the O-RAN.WG4.MP-YANGs-R004-v17.01.zip file and their corresponding version numbers and revision dates. Table E-1: O-RAN Alliance defined YANG model versions to be used with the present document YANG Module Name Namespace Revision Date Description Version o-ran-ald urn:o-ran:ald:1.0 2021-12-01 1.2.0 o-ran-ald-port urn:o-ran:ald-port:1.0 2024-08-12 13.1.0 o-ran-beamforming urn:o-ran:beamforming:1.0 2024-12-23 17.0.0 o-ran-antenna-calibration urn:o-ran:antcal:1.0 2024-04-15 7.2.0 o-ran-certificates urn:o-ran:certificates:1.0 2024-12-23 17.0.0 o-ran-common-identity-refs urn:o-ran:wg1identityref:1.0 2022-08-15 1.0.0 o-ran-common-yang-types urn:o-ran:common-yang-types:1.0 2023-08-14 2.0.0 o-ran-compression-factors urn:o-ran:compression-factors:1.0 2024-08-12 16.0.0 o-ran-delay-management urn:o-ran:delay:1.0 2024-08-12 16.0.0 o-ran-dhcp urn:o-ran:dhcp:1.0 2024-08-12 10.1.0 o-ran-ecpri-delay urn:o-ran:message5:1.0 2024-12-23 17.0.0 o-ran-ethernet-forwarding urn:o-ran:ethernet-fwd:1.0 2021-12-01 3.1.0 o-ran-externalio urn:o-ran:external-io:1.0 2023-08-14 13.0.0 o-ran-fan urn:o-ran:fan:1.0 2021-12-01 1.2.0 o-ran-file-management urn:o-ran:file-management:1.0 2024-12-23 17.0.0 o-ran-fm urn:o-ran:fm:1.0 2024-08-12 15.1.0 o-ran-frequency-band- measurement urn:o-ran:frequency-band- measurement:1.0 2024-08-12 16.0.0 o-ran-hardware urn:o-ran:hardware:1.0 2024-04-15 15.0.0 o-ran-ieee802-dot1q-cfm urn:o-ran:o-ran-ieee802-dot1q-cfm:1.0 2023-04-10 12.0.0 o-ran-interfaces urn:o-ran:interfaces:1.0 2024-08-12 16.0.0 o-ran-laa urn:o-ran:laa:1.0 2022-08-15 1.2.0 o-ran-laa-operations urn:o-ran:laa-operations:1.0 2023-08-14 13.0.0 o-ran-lbm urn:o-ran:lbm:1.0 2024-08-12 1.4.0 o-ran-module-cap urn:o-ran:module-cap:1.0 2024-12-23 15.1.0 o-ran-mplane-int urn:o-ran:mplane-interfaces:1.0 2024-12-23 17.0.0 o-ran-operations urn:o-ran:operations:1.0 2024-12-23 15.1.0 o-ran-performance-management urn:o-ran:performance-management:1.0 2024-12-23 17.0.0 o-ran-processing-element urn:o-ran:processing-element:1.0 2024-12-23 10.1.0 o-ran-shared-cell urn:o-ran:shared-cell:1.0 2024-12-23 17.0.0 o-ran-software-management urn:o-ran:software-management:1.0 2024-04-15 11.1.0 o-ran-supervision urn:o-ran:supervision:1.0 2021-12-05 11.0.0 o-ran-sync urn:o-ran:sync:1.0 2024-04-15 15.0.0 o-ran-trace urn:o-ran:trace:1.0 2022-08-15 1.2.0 o-ran-transceiver urn:o-ran:transceiver:1.0 2024-12-23 17.0.0 o-ran-troubleshooting urn:o-ran:troubleshooting:1.0 2022-08-15 1.2.0 o-ran-udp-echo urn:o-ran:udpecho:1.0 2019-02-04 1.0.0 o-ran-uplane-conf urn:o-ran:uplane-conf:1.0 2024-12-23 17.0.0 o-ran-usermgmt urn:o-ran:user-mgmt:1.0 2024-08-12 16.0.0 o-ran-ves-subscribed-notifications urn:o-ran:ves-sn:1.0 2020-12-10 5.0.0 o-ran-wg4-features urn:o-ran:wg4feat:1.0 2024-12-23 17.0.0 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 346 Table E-2 lists all of the externally defined YANG models and their corresponding revision dates. These are not included in the O-RAN.WG4.MP-YANGs-R004-v17.01.zip file. Table E-2: Externally defined YANG model versions to be used with the present document YANG Module Name Namespace Revision Date iana-crypt-hash urn:ietf:params:xml:ns:yang:iana-crypt-hash 2014-08-06 iana-hardware urn:ietf:params:xml:ns:yang:iana-hardware 2018-03-13 iana-if-type urn:ietf:params:xml:ns:yang:iana-if-type 2017-01-19 ieee802-dot1x urn:ieee:std:802.1X:yang:ieee802-dot1x 2020-02-18 ieee802-dot1x-types urn:ieee:std:802.1X:yang:ieee802-dot1x-types 2020-02-18 ieee802-dot1x-eapol urn:ieee:std:802.1X:yang:ieee802-dot1x-eapol 2022-05-25 ieee802-types urn:ieee:std:802.1Q:yang:ieee802-types 2020-06-04 ietf-crypto-types urn:ietf:params:xml:ns:yang:ietf-crypto-types 2024-10-10 ietf-datastores urn:ietf:params:xml:ns:yang:ietf-datastores 2018-02-14 ietf-dhcpv6-common urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common 2021-01-29 ietf-dhcpv6-types urn:ietf:params:xml:ns:yang:ietf-dhcpv6-types 2018-09-04 ietf-hardware urn:ietf:params:xml:ns:yang:ietf-hardware 2018-03-13 ietf-inet-types urn:ietf:params:xml:ns:yang:ietf-inet-types 2013-07-15 ietf-interfaces urn:ietf:params:xml:ns:yang:ietf-interfaces 2018-02-20 ietf-ip urn:ietf:params:xml:ns:yang:ietf-ip 2018-02-22 ietf-keystore urn:ietf:params:xml:ns:yang:ietf-keystore 2024-10-10 ietf-netconf urn:ietf:params:xml:ns:netconf:base:1.0 2011-06-01 ietf-netconf-acm urn:ietf:params:xml:ns:yang:ietf-netconf-acm 2018-02-14 ietf-netconf-monitoring urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring 2010-10-04 ietf-netconf-notifications urn:ietf:params:xml:ns:yang:ietf-netconf-notifications 2012-02-06 ietf-network-instance urn:ietf:params:xml:ns:yang:ietf-network-instance 2019-01-21 ietf-restconf urn:ietf:params:xml:ns:yang:ietf-restconf 2017-01-26 ietf-subscribed-notifications urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications 2019-09-09 ietf-system urn:ietf:params:xml:ns:yang:ietf-system 2014-08-06 ietf-truststore urn:ietf:params:xml:ns:yang:ietf-truststore 2024-10-10 ietf-yang-library urn:ietf:params:xml:ns:yang:ietf-yang-library 2019-01-04 ietf-yang-schema-mount urn:ietf:params:xml:ns:yang:ietf-yang-schema-mount 2019-01-14 ietf-yang-types urn:ietf:params:xml:ns:yang:ietf-yang-types 2013-07-15 ietf-x509-cert-to-name urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name 2014-12-10 ieee802-dot1q-cfm urn:ieee:std:802.1Q:yang:ieee802-dot1q-cfm 2022-01-19 ieee802-dot1q-cfm-types urn:ieee:std:802.1Q:yang:ieee802-dot1q-cfm-types 2020-06-04 ieee802-dot1q-types urn:ieee:std:802.1Q:yang:ieee802-dot1q-types 2020-06-04 NOTE: Use of ietf-dhcpv6-types with a revision date of 2018-09-04 is deprecated. The reference to ietf-dhcpv6- common with a revision date of 2021-01-29 will be superseded once the corresponding RFCs are published. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 347 Annex F (informative): Out of scope functionality F.1 Out of scope functionality The present document does not include specific functions that, during the specification definition process, have been highlighted as useful enhancements. The list of identified functionalities is shown below. This can be used to prioritize future specification work within O-RAN Alliance. 1) Beam Id field interpretation for various types of beamforming. 2) Redundancy and failover scenario. 3) Shared cell support for IP-defined flows. 4) Enhancements to better align with O-RAN Alliance O1 specification. 5) Shared cell topology discovery for architectures that do not ensure Ethernet frames sent between a south-node and a north-node are bridged by an O-RU. 6) Void. 7) Dynamic sharing of O-RU carriers between multiple O-DUs. 8) Enhanced adaptive delay operation that allows O-RU delay adaptation without requiring active carriers to be disabled. 9) The role of a Shared Resource Operator's SMO when operating with a multi-operator O-RU operated by a third party Shared O-RU Host. ETSI ETSI TS 104 023 V17.1.0 (2026-01) 348 Annex G (informative): o-ran-lbm.yang and o-ran-ieee802-dot1q-cfm.yang co-ordination G.1 Model structure In o-ran-lbm.yang model, the YANG structure is illustrated in Figure G-1. Figure G-1: o-ran-lbm YANG structure In contrast, the ieee-802-dot1q-cfm YANG model has the structure illustrated in Figure G-2. Figure G-2: ieee-802-dot1q-cfm YANG structure ETSI ETSI TS 104 023 V17.1.0 (2026-01) 349 The ieee802-dot1q-cfm.yang model is not standalone model. It needs to be extended to work with ieee-dot1q-cfm- bridge model or some equivalent. In o-ran-ieee802-dot1q-cfm.yang, interface and primary-vid are used to map to o-ran-interfaces (where an l2vlan interface implicitly maps to an IEEE 802.1Q bridge equivalent). In both models, the maintenance association endpoint (mep) is mapped to a l2vlan interface (bridge interface) and the l2vlan interface is mapped to a bridge equivalent. In the /cfm/maintenance-group/mep, interface and primary-vid represents an ieee equivalent bridge instance. Association towards an ieee equivalent bridge is represented by parameter on MEP in maintenance -group. In o-ran-lbm.yang model, remote-meps and maintenance-association-end-points are defined on the same level under schema node component-list. Remote-meps contains MEP IDs that are in the MA but are located remotely (opposite to local) and maintenance-association-endpoint contains mep configurations. In ieee-802-dot1q-cfm model, information of meps is in two lists, maintenance-domain and maintenance-group. The ieee-802-dot1q-cfm maintenance-association-mep list contains mep-ids for all configured meps that are in the MA. The mep list in maintenance-group list has mep configurations for example mac address, enable parameter, etc. And in ieee-802-dot1q-cfm model, each mep contains a mep-db list used to store information of its remote-meps. In ieee-802-dot1q, if a maintenance-group is defined, remote MEP state machine is instantiated to all remote MEPs that are presented in maintenance-association-mep list (that is active). G.2 Mapping between models To map the a o-ran-lbm.yang configuration to ieee-802-dot1q-cfm, the level of component which represent a bridge will be mapped to ieee equivalent bridge instance which is represented by the combination of value interface and primary-vid. The remote-meps leaf-list in o-ran-lbm.yang will be mapped to the maintenance-association-mep list in ieee-802-dot1q-cfm model. To map the a o-ran-lbm.yang configuration to ieee-802-dot1q-cfm, maintenance-group will be generated for each MD, MA combination. maintenance-association-end-point configuration in o-ran-lbm.yang will be mapped as /maintenance-group/MEP in ieee-802-dot1q-cfm model, as illustrated in Tables G-1, G-2, G-3, and G-4 describe the mapping between the two YANG schemas. Table G-1: High level relationship between o-ran-lbm.yang and ieee-802-dot1q-cfm.yang Model: o-ran-lbm-.yang Model: ieee-802-dot1q-cfm.yang Comment /md-data-definition/maintenance- domain /cfm/maintenance-domain /md-data-definition/maintenance- domain/maintenance-association /cfm/maintenance-domain /maintenance-association /md-data-definition/maintenance- domain/maintenance-association /component-list To parameter interface and vid in /cfm/maintenance-group/mep /md-data-definition/maintenance- domain/maintenance-association /component-list/Remote-meps /cfm/maintenance-domain /maintenance-association /maintenance-association-mep The local mep ids in lbm model need to be added as well. /md-data-definition/maintenance- domain/maintenance-association /component-list /maintenance- association-end-point /cfm/maintenance-group/mep For each MD MA combination, a new maintenance-group can be created. Table G-2: Mapping between maintenance-domain in o-ran-lbm.yang and ieee-802-dot1q-cfm.yang List: /md-data- definition/maintenance-domain List: /cfm/maintenance-domain Comment id md-id name md-name md-level md-level ETSI ETSI TS 104 023 V17.1.0 (2026-01) 350 Table G-3: Mapping between maintenance-association lists in o-ran-lbm.yang and ieee-802-dot1q-cfm.yang /md-data- definition/maintenance- domain/maintenance- association /cfm/maintenance-domain /maintenance-association Comment parameter sub-parameter parameter id ma-id name ma-name Component-list Not mapped Component-id Not mapped name /cfm/maintenance- group/mep/interface vid /cfm/maintenance- group/mep/vid Remote-meps cfm/maintenance-domain /maintenance-association /maintenance-association-mep Maintenance- association-meps /cfm/maintenance-group/mep Table G-4: Mapping MEP configuration between o-ran-lbm.yang and ieee-802-dot1q-cfm.yang /md-data- definition/maintenance- domain/maintenance- association /component-list /maintenance-association-end- point /cfm/maintenance-group/mep Comment parameter sub-parameter parameter Mep-identifier mep-id interface interface Augmented in ieee- dot1q-cfm Primary-vid vid Augmented in ieee- dot1q-cfm Administrative-state enabled Mac-address Mac-address loopback N/A Reply-transmitted State/mep-lbr-out ETSI ETSI TS 104 023 V17.1.0 (2026-01) 351 Annex H (informative): Change history Date Revision Description 2019.03.11 01.00 First published version based on import of xRAN M-Plane 2019.07.03 02.00 Bug fixes and correction to v01.00 Addition of new functionality, including: - Beam tilting - Antenna calibration - CU plane monitoring - Trace - 3GPP MV PnP support - QSFP 2020.04.17 03.00 Bug fixes and correction to v02.00 - NACM table - Clarifications on CU plane monitoring - Clarification of allowed sync state transitions - Corrections on overall Start-Up operation Addition of new functionality, including: - Shared cell - Dying Gasp - PM Counters - Config Notification - Hybrid Health Warning - Dynamic Spectrum Sharing - Grouping of eAxC-IDs - Energy, Power and Environmental statistics ETSI ETSI TS 104 023 V17.1.0 (2026-01) 352 Date Revision Description 2020.08.10 04.00 Bug fixes and correction to v03.00: - Removing reference to Component eAxC references - Correcting YANG references for Non-Delay Managed Traffic - Correcting YANG references for enhanced U-Plane markings - Correcting YANG references in tables B.3 and C.3 - Clarify that validation of configuration is based on criteria which includes definitions in this document - Clarification of supervision Addition of new functionality, including: - Enabling static configuration of PRACH or SRS - Supporting flexible TDD pattern configuration - To allow for different delay management parameters for C and U-plane - New sync capabilities for reporting estimated time and frequency errors - New capability to define compression on an endpoint basis - New optional feature - configurable full-scale offset - New optional feature - eAxC specific gain correction - New optional feature - TX gain reference level control 2020.12.10 05.00 Bug fixes and correction to v04.00: - Clarify operation of default account for certificate access - Clarify operation of supervision in lock state - Clarify PRACH patterns - Fixing copy/paste errors in the S-plane PTP status definitions - Corrected omissions from optional feature table - Clarify centre bandwidth parameter - Replace previous NMS terms with SMO - Corrections to C/U plane monitoring for FHM Addition of new functionality, including: - New NACM permissions for SMO and hybrid O-DU - New optional feature for performing pnfRegistration - New optional feature for configured YANG subscriptions sent over JSON/REST - Updating mandatory cipher to AES128-CTR - Bandwidth management to avoid over-subscription of O-RU resources - Shared cell with selective Tx/Rx using Beam ID - Cascaded FHM Operation - New capability to support co-ordinated (self) antenna calibration ETSI ETSI TS 104 023 V17.1.0 (2026-01) 353 Date Revision Description 2021.03.22 06.00 Bug fixes and correction to v05.00: - Clarify operation of non-persistent M-Plane - Clarify operation of Software Management - Clarify operation of VLAN-IDs for C- and U-Plane - Clarify eaxc-id assignment - Clarify connectivity checks operation - Clarify procedures for deleting configuration - Clarify plug and play certificate aspects Addition of new functionality, including: - Optional support of NETCONF/TLS - Supporting IPv6 only O-RUs 2021.07.26 07.00 Bug fixes and correction to v06.00: - Clarify operation of configured subscriptions - Clarify username syntax - Correction to log management sequence diagrams - Clarify delay management operation - Clarify DHCP operation - Clarify operation of antenna calibration - Correct errors in text that describes low-level-[tr]x-endpoint creation - Clarify modify parameter section - Clarify revision and namespace compatibility handling - Clarify certificate enrolment - Clarify non-persistent operation with software management - Clarify Fault Management Activation - Correction to enable multiple measurements to be included in a notification - Clarify operation of NETCONF supervision with multiple NETCONF clients Addition of new functionality, including: - External antenna delay handling - Optional capability to optimize VLAN discovery - Capability to support C-Plane limits for packet processing - FTPES based file transfer - TD-RSSI measurement capability - EPE measurements for current and voltage - Configurable timer for co-ordinated antenna calibration - Enhanced antenna calibration using different resource sets ETSI ETSI TS 104 023 V17.1.0 (2026-01) 354 Date Revision Description 2021.10.28 07.01 Updates to align with ETSI PAS Process 2021.12.01 08.00 Bug fixes and correction to v07.01: - Deprecate leaf-list(frequency-table) and to add a new list(frequency-bin-table) - Correction for C-plane message limits - Antenna Calibration schema node reference corrections - Clarification for fault ID 24 - DHCP Clarifications - Clarifications to log management - Adding SCS information for FHM Combine operations - Shared cell performance management corrections Addition of new functionality, including: - Introduction of alarm-type - Enable IANA Private Enterprise Number to be used as Vendor Code in software management - Boundary Clock function - Capability for supporting multi cell operation - Compression support for Section Type 6 - Mandatory support of TLS, PKIX, and FTPES - Supporting multiple transport session types simultaneously - Shared cell enhancements introducing t-combine-net and tx-duration ETSI ETSI TS 104 023 V17.1.0 (2026-01) 355 Date Revision Description 2022.04.18 09.00 Bug fixes and correction to v08.00: - Updates to align with new O-RAN template - Updates to references to align with DFT guidelines - Clarify rejection of invalid configuration - Alignment of eventName field and "remote-file-path" format - Clarification of handling of an O-RU capable of BF and non-BF modes - Update clause cases - Correction Clarification of S-Plane interactions with M-Plane during Startup, and Loss/Recovery of Synchronization - Normative Reference to YANG models - Clarify NACM and user management - Clarify NETCONF monitoring and <get-schema> - Reset handling clarification - NETCONF event stream clarification - Software Management Clarification - SSH and SFTP host key clarification - SFTP host key correction Addition of new functionality, including: - New feature flag for O-RU to indicate support of 4-Byte aligned section type 6 - New build-content-download leaf and associated software management definition - New list for historical alarms - Defining loopback message to group destination address ETSI ETSI TS 104 023 V17.1.0 (2026-01) 356 Date Revision Description 2022.08.15 10.00 Bug fixes and correction to v09.00: - Clarify contradicting statements with regard to TLS 1.2 - Array element fault source and fault source improvements - Software management clarification - Correction for module privileges - Persistence of configured subscription - Correction for O-RU call home port - Clarify operation of filter based on xpath - Clarify operation with factory default software - Clarification to path definition for file management - Remove LAA "capability" option from Table C.3-1 - Password for FTPES server - Call home with multiple A/AAAA records - PKI Clarifications - Hybrid management clarifications Addition of new functionality, including: - Identifying default NETCONF accounts - Introduction of O-RU connectors - Configuration to map from certificates to NETCONF usernames - Update SFP compliance codes - DHCPv4 Client DUID/IAID definition - IEEE 802.1X Port based access control - Shared O-RU ETSI ETSI TS 104 023 V17.1.0 (2026-01) 357 Date Revision Description 2022.12.05 11.00 Bug fixes and correction to v10.00: - Correcting hardware access privileges for SMO - Correct fault ID 31 cancel condition and source - Correct o-ran-laa YANG tree - Add voltage and current EPE stats to Annex B.5 - Deprecation of power parameters for shared O-RU - Annex C.2 and C.3 reformat tables - Future topics annex - Clarification for handling of multiple interfaces per optical port - Clarify writable-running datastore - Clarification for PM measurement objects modification - Energy saving state clarification - Clarification of active parameter - Adding IEEE 802.1X recommendation Addition of new functionality, including: - U-Plane-only DL mode - SW build level file integrity check - Session supervision with session-id - Network energy savings ETSI ETSI TS 104 023 V17.1.0 (2026-01) 358 Date Revision Description 2023.04.10 12.00 Bug fixes and correction to v11.00: - Correct inconsistency in clause 9.1.3 - Update reference to DHCPv6 Options - Remove import of ietf-crypto-types@2019-04-29 - Confirmation of backwards compatibility - Clarification of the accounts name - DHCP options clarification - Clarify default operation of 802.1X - Correction Radio Timing for Copy - Correction to shared cell counters - Clarification of PRACH repetition - Clarified operational state for layer 3 configuration - Remove erroneous use of SZTP Addition of new functionality, including: - 802.1X as Mandatory - Add supported SCSes of FHM - Allow all NETCONF clients to change their own password - NB IoT - Advanced endpoint capability reporting for NB-IoT & other scenarios - Allow CA/RA server on non-production VLAN - Introduce ietf-truststore YANG model - Introduce SE11-WITH-CONTINUITY-BIT-SUPPORT - Addition of feature non-scheduled-ueid - Continuity Check Message support - U-plane message processing limits 2023.03.14 12.01 Corrections to v12.00: - Fixing typographical and cross reference errors ETSI ETSI TS 104 023 V17.1.0 (2026-01) 359 Date Revision Description 2023.08.14 13.00 Bug fixes and correction to v12.00: - Correction of feature name NON-PERSISTENT-MPLANE - Clarifying multiple instances of "is responsible" - Improve M-Plane stack illustration - Correct LBM terminology - Correction to CSV file format definitions - Keep alive for call home O-RU controllers - Clarify alarm dependency - Clarify carrier state's relationship to synchronization state Addition of new functionality, including: - Add optional Major severity for alarm 1 - Call home re-activation - Add optional Power Amplifier critical severity to alarm #27 - New availability status for [tr]x-array-carriers - O-RU connectors for ALD ports and External IO ports - Combine delays per SCS - Disabling sequence number handling - Enhanced Network Energy Savings functionality 2023.12.11 14.00 Bug fixes and correction to v13.00: - Reformat table 6.9.3-1 - Align Table B.1-1 with YANG Model - Clarify the information which software slot is active is reset persistent - Clarification for TAC level energy saving - Model name and namespace clarifications - C/U Plane Monitoring Clarification - Fault management clarifications Addition of new functionality, including: - New alarm for Rx signal quality - Adding ietf-netconf to imported folder - New feature SE23-PRB-BLOCK-MODE-SUPPORT - Performance Counter for Shared Cell - Energy saving by Data Layer Control - bundleOffset in SE 11 ETSI ETSI TS 104 023 V17.1.0 (2026-01) 360 Date Revision Description 2024.04.15 15.00 Bug fixes and correction to v14.00: - SWM Installation status enum fix - Clarify port transceiver source for alarm 29 - Clarify user and certificate persistent information - Correct cross reference to CUS-Plane DSS clause - Clarify carrier activation deactivation sequence - Clarifying NETCONF transaction operation - PM parameter handling - Lock O-RU clarifications - Clarifying array element terminology - Handling long DHCP options Addition of new functionality, including: - Per-port S-plane configuration of a multi-port O-RU - O-RU payload frame size per ethernet interface - Extended QL TLV Support - O-RU TCP MSS Configuration - Multiple beamId table support - M-Plane TRX Control energy savings - Deep hibernate energy savings - PRG size feature - Adding frequency-table support with EPE-Statistics - VSWR performance management reporting - MU-MIMO user group optimization feature - Delay profile per beamforming method ETSI ETSI TS 104 023 V17.1.0 (2026-01) 361 Date Revision Description 2024.08.29 16.01 Bug fixes and correction to v15.00: - ETSI cleanup editorials - Clarify interface connection - Clarification on update of network layers parameters via NETCONF - Trust store revision - Clarifying transport endpoints - Clarify alarm 28 - Clarify alarm 18 - Clarify vendor certificate and trust anchor handling - Clarify certificate and trust anchor management for shared O-RU - Clarify fault management Clause A - CMPv2 clarification - Clarify RFC 5277 and RFC 8639 subscriptions Addition of new functionality, including: - PAE credential definition - High IQ Alarm - VSWR Alarm - DRMS-BF - SE-10 feature SE10-MEMBER-CANDIDATE-LIST - Target value configuration and used-value retrieval - Configuring IEEE 802.1X addressing - RSSI measurements when operating in shared spectrum. - Simple Public Key Method for SSH Client Authentication - TSSI Measurements - RSSI Measurements - Section Extension 27 for O-DU controlled dimensionality reduction - In service beamforming configuration update - MACsec - Certificate lifecycle management ETSI ETSI TS 104 023 V17.1.0 (2026-01) 362 Date Revision Description 2024.12.23 17.00 Bug fixes and correction to v16.01: - British English corrections - Carrier general configuration - Backwards compatible clarification - Revision handling - Remove S-plane performance requirements - Correction of the sync state change descriptions - Correction to feature flag name for dying gasp alarm - Correction to step numbers in Cross Reference - Clarification of temperature measurements for transceivers - Remove case SELECTIVE from shared cell mode configuration - hardware-state-change clarification - Deprecate per-band-config list related RPC and Notification - Clarify ALD operations - Hybrid and hierarchical clarifications - Shared cell clarifications - Clarify U-Plane configuration steps - Clarify carrier availability status Addition of new functionality, including: - Add a generic hardware failure alarm to M-Plane - Add TX output power statistics to M-Plane - O-RAN defined security logging - Dynamic SINR reporting resolution - Switched to importing RFC 9640, 9641, 9642 instead of Internet-Drafts - New transceiver measurement for thermoelectric cooler (TEC) current - New Ethernet statistics counters 2025.01.27 17.01 Bug fixes and correction to v17.00: - Aligned all 3GPP References ETSI ETSI TS 104 023 V17.1.0 (2026-01) 363 History Version Date Status V12.0.1 May 2024 Publication V17.1.0 January 2026 Publication |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 1 Scope | The present document defines the performance test cases for Dedicated Short Range Communication (DSRC) transmission equipment (500 kbit/s / 250 kbit/s) operating in the 5 795 MHz to 5 815 MHz frequency band. NOTE: Technical requirements for conformance against article 3.2 of the Radio Equipment Directive [i.1] and related test procedures are defined in in ETSI EN 300 674-2-1 [i.2] and ETSI EN 300 674-2-2 [i.3]. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 2 References | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] EN 12253 (2004): "Road transport and traffic telematics. Dedicated short-range communication. Physical layer using microwave at 5,8 GHz", (produced by CEN). |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Directive 2014/53/EU of the European Parliament and of the Council of 16 April 2014 on the harmonisation of the laws of the Member States relating to the making available on the market of radio equipment and repealing Directive 1999/5/EC. [i.2] ETSI EN 300 674-2-1 (2022): "Transport and Traffic Telematics (TTT); Dedicated Short Range Communication (DSRC) transmission equipment (500 kbit/s / 250 kbit/s) operating in the 5 795 MHz to 5 815 MHz frequency band; Part 2: Harmonised Standard for access to radio spectrum; Sub-part 1: Road Side Units (RSU)". [i.3] ETSI EN 300 674-2-2 (2019): "Transport and Traffic Telematics (TTT); Dedicated Short Range Communication (DSRC) transmission equipment (500 kbit/s / 250 kbit/s) operating in the 5 795 MHz to 5 815 MHz frequency band; Part 2: Harmonised Standard for access to radio spectrum; Sub-part 2: On-Board Units (OBU)". [i.4] ISO 14906 (2022): "Electronic fee collection -- Application interface definition for dedicated short-range communication". [i.5] EN 13372 (2003): "Road transport and traffic telematics (RTTT). Dedicated short-range communication. Profiles for RTTT applications", (produced by CEN). ETSI ETSI TS 104 022 V1.1.1 (2024-06) 8 [i.6] EN 12795 (2003): "Road transport and traffic telematics. Dedicated short range communication (DSRC). DSRC data link layer. Medium access and logical link control", (produced by CEN). [i.7] EN 12834 (2003): "Road transport and traffic telematics. Dedicated Short Range Communication (DSRC). DSRC application layer", (produced by CEN). [i.8] IEC 60721-3-4 (2019):"Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations". [i.9] IEC 60721-3-5 (1997): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 5: Ground vehicle installations". [i.10] ETSI TS 103 052: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Radiated measurement methods and general arrangements for test sites up to 100 GHz". |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 3 Definition of terms, symbols and abbreviations | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 3.1 Terms | For the purposes of the present document, the following terms apply: bit: binary digit NOTE: It can have one out of two possible values, e.g. 0/1 or +1/-1 or low/high. bit rate: number of bits, in a bit stream, occurring per unit time, usually expressed in bits per second bore sight: direction of maximum radiation of a directional antenna NOTE: If bore sight cannot be determined unambiguously, then bore sight may be declared by the provider. carrier frequency: frequency fTx to which the RSU transmitter is tuned NOTE: In DSRC, the carrier frequency is in the centre of a channel, see table 2 of the present document. carrier signal or carrier: harmonic signal whose nominal single frequency fTx can vary within a range specified by the carrier frequency tolerance and which is capable of being modulated by a second, symbol-carrying signal channel: continuous part of the radio-frequency spectrum to be used for a specified emission or transmission NOTE: A radio-frequency channel may be defined by two specified limits, or by its centre frequency and its bandwidth, or any equivalent indication. It is often designated by a sequential number. A radio-frequency channel may be time-shared in order to allow radiocommunication in both directions by simplex operation. The term "channel" is sometimes used to denote two associated radio-frequency channels, each of which is used for one of two directions of transmission. cross-polar discrimination, ellipticity of polarization: antenna designed to transmit left hand circular waves may transmit some right hand circular waves in addition NOTE: Cross-Polar Discrimination (XPD) is defined as the ratio PLHCP/PRHCP of power PLHCP of the left hand circular polarized wave to the power PRHCP of the right-hand circular wave when the total power of the transmitted wave is PLHCP + PRHCP. environmental profile: range of environmental conditions under which equipment within the scope of the present document is required to comply with the provisions of the present document equivalent isotropic radiated power: signal power fed into an ideal loss-less antenna radiating equally in all directions that generates the same power flux at a reference distance as the one generated by a signal fed into the antenna under consideration in a predefined direction within its far field region integral antenna: antenna, with or without a connector, designed as an indispensable part of the equipment ETSI ETSI TS 104 022 V1.1.1 (2024-06) 9 OBU sleep mode: mode where the OBU can only detect the presence of DSRC down-link signal NOTE: An OBU may be either in sleep mode, the stand-by mode, or the transmit mode. The sleep mode is an optional mode for battery powered OBUs that allows to save battery power. In this mode, the OBU can only detect the presence of a DSRC down-link signal which under certain defined conditions, see EN 12253 [1], a transition to the stand-by mode is trigger by a wake-up event (detection of a DSRC down-link). OBU stand-by mode: mode in which the OBU is capable of receiving DSRC down-link signals NOTE: In stand-by mode the OBU is never transmitting. operating frequency: nominal frequency at which equipment is operated; also referred to as the operating centre frequency NOTE: Equipment may be able to operate at more than one operating frequency. polarization: locus of the tip of the electrical field vector in a plane perpendicular to the direction of transmission EXAMPLE: The polarization can be horizontal or vertical linear polarized, or left or right-hand circular polarized. provider: manufacturer, supplier, or person responsible for placing the apparatus on the market radiated measurements: measurements which involve the measurement of a radiated electromagnetic field |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: ACW Amplitude of CW signal Amod Amplitude of modulated signal ATNAT2 Attenuation of attenuator AT2 ATNBLN Attenuation of balun BLN ATNCA1 Attenuation of calibrated coaxial cable 1 BER Bit Error Ratio CF Number of frames transmitted CE Number of erroneous frames received d Distance between phase centres of transmitting and receiving antenna ddisplace Horizontal displacement of TTA and RTA antenna phase centres dF1 Distance from transmitting antenna to first Fresnel ellipse dF2 Distance from first Fresnel ellipse to receiving antenna Dfb Distance between neighbouring ferrite beads Di Directivity relative to an isotropic radiator D0,TA Largest linear dimension of test antenna D0,EUT Largest linear dimension of EUT antenna EIRPObuTx e.i.r.p. generated by the OBU within a single side band f Frequency FER Frame error ratio fs Nominal OBU sub-carrier frequency fTx Nominal RSU carrier frequency fu Nominal centre frequency of unwanted signal fu1, fu2 Centre frequencies of unwanted signal Gc Conversion gain GOBU,Rx Gain of OBU receiving antenna GOBU,Tx Gain of OBU transmitting antenna GRSA Gain of receiving substitution antenna ETSI ETSI TS 104 022 V1.1.1 (2024-06) 10 GTA Gain of test antenna GTSA Gain of transmitting substitution antenna lg(.) Logarithm to the base ten m Modulation index N Total number of transmitted bits within a single frame PCW Power of CW signal PD11a Power limit for communication (upper) PD11b Power limit for communication (lower) Pinc Incident signal power as received by an ideal isotropic receiving antenna Pinc,dBm Pinc in dBm PLHCP Signal power of left hand circular polarized wave Pmod Power of modulated signal PMMS2 Output signal power of MSS2 PObuRx Incident signal power to OBU, referred to an ideal isotropic receiving antenna PreTx Retransmitted signal power PRSA Signal power obtained from receiving substitution antenna PRHCP Signal power of right hand circular polarized wave Pssb Signal power within single side band Pu Power of unwanted signal RBW Resolution bandwidth TCW Duration of CW signal Tmod Duration of modulated signal Vmax, Vmin Maximal amplitude of modulated output signal of RSU caused by data bit 1, or 0 α Tilt angle of test antenna αdisplace Displacement angle between TTA and RTA θ Angle relative to OBU bore sight indicating worst case direction λ Wavelength ρRSA Reflection coefficient at antenna connector of the receiving substitution antenna ρTSA Reflection coefficient at antenna connector of the transmitting substitution antenna |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: General abbreviations: AT1 Attenuator 1 AT2 Attenuator 2 BER Bit Error Ratio BLN Balun BST Beacon Service table CA Corresponding Antenna CC Coaxial Circulator CEN Comité Européen de Normalisation CRC Cyclic Redundancy Checking CW Continuous Wave DC Direct Current DSRC Dedicated Short Range Communication e.i.r.p. Equivalent Isotropic Radiated Power EFC Electronic Fee Collection EU European Union EUT Equipment Under Test FCCA Ferrited Coaxial CAble FCCA1 Ferrited Coaxial CAble 1 FER Frame Error Ratio IEC International Electrotechnical Commission ETSI ETSI TS 104 022 V1.1.1 (2024-06) 11 ISO International Organization for Standardization LHCP Left Hand Circular Polarized LOS Line-Of-Sight LP Linear Polarized Mc Location of the OBU antenna phase centre Mcentre Centre point between phase centres of TTA and RTA MSS1 Monochromatic Signal Source 1 MSS2 Monochromatic Signal Source 2 n.a. not applicable OBU On Board Unit PM1 Power Meter 1 RBW Resolution BandWidth RD Receiving Device RF Radio Frequency RRxA RSU Receiving Antenna RSA Receiving Substitution Antenna RSU Road Side Unit RTA Receiving Test Antenna RTTT Road Transport and Traffic Telematics RTxA RSU Transmitting Antenna Rx Receiver SMS1 Signal or Message Source 1 SR Special Report SSB Single Side Band TA Test Antenna TM1 Test Message 1 TS1 Test Signal 1 TS2 Test Signal 2 TSA Transmitting Substitution Antenna TTA Transmitting Test Antenna TTT Transport and Traffic Telematics Tx Transmitter VBW Video BandWidth VST Vehicle Service table VSWR Voltage Standing Wave Ratio XP Cross Polarized XPD Cross-Polar Discrimination EN 12253 [1] list of down-link parameter abbreviations: D1 Carrier frequencies D3 OBU minimum frequency range D5 Polarization D5a Cross polarization D6 Modulation D6a Modulation index D6b Eye pattern D7 Data coding D8 Bit rate D8a Tolerance of bit clock D9a BER for communication D11a Power limit for communication (upper) D11b Power limit for communication (lower) D12 Cut-off power level of OBU EN 12253 [1] list of up-link parameter abbreviations: U1 Sub-carrier frequencies U1b Use of side bands U4a Maximum single side band e.i.r.p. (bore sight) U4b Maximum single side band e.i.r.p. (35°) U5 Up-link polarization ETSI ETSI TS 104 022 V1.1.1 (2024-06) 12 U5a Cross polarization U6 Sub-carrier modulation U6b Eye pattern/duty cycle U6c Modulation on carrier U7 Data coding U8 Bit rate U8a Tolerance of symbol clock U9a BER for communication U12 Conversion gain |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 4 General characteristics for testing | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 4.1 Units | Units can be either Road Side Units or On Board Units. Transmitters and receivers may be individual or combination units; some units may be transmitter only, some units may be receiver only and some units may combine transmitter and receiver functionalities. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 4.2 Environmental profiles | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 4.2.1 Environmental profile for testing | The technical requirements of the present document shall apply under the mandatory environmental profile for intended operation of the equipment as specified in clause 4.2.2. The equipment shall always comply with all the technical requirements of the present document when operating within the boundary limits of the mandatory environmental profile. The provider may additionally select environmental profiles as specified in clause 4.2.3 for testing. An environmental profile shall include at least the minimum and maximum value of the operational temperature range. The environmental conditions for tests shall be any convenient selection of environmental parameter values within the selected ranges from clause 4.2.2 and optionally from clause 4.2.3. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 4.2.2 Mandatory environmental conditions | The normal temperature and humidity conditions for tests shall be any convenient combination of temperature and relative humidity within the following ranges: • temperature: +15 ºC to +35 ºC; • relative humidity: 20 % to 75 %. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 4.2.3 Extreme environmental conditions | Extreme environmental conditions are classified in categories according to table 1. Table 1: Extreme environmental conditions Temperature category RSU OBU Category I (General): temperature: -20 °C to +55 °C temperature: -20 °C to +55 °C Category ll: IEC 60721-3-4 [i.8] / 4K2 IEC 60721-3-5 [i.9] / 5K2 Category III IEC 60721-3-4 [i.8] / 4K3 IEC 60721-3-5 [i.9] / 5K3 Category IV: IEC 60721-3-4 [i.8] / 4K4 IEC 60721-3-5 [i.9] / 5K4 ETSI ETSI TS 104 022 V1.1.1 (2024-06) 13 The extreme environmental conditions for tests shall be any convenient selection of environmental parameter values, except temperature, of a single category. For tests at extreme temperature, measurements shall be made at both, the upper and lower bound of the temperature range of the selected category. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 5 General characteristics of Road Side Unit | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 5.1 Power supply | The power supply shall meet the requirements given in clause A.1.2 for the selected operational conditions of the EUT. The power can be supplied by a built-in battery, an external battery or a stabilized power supply. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 5.2 Carrier frequencies | The present document applies to RSUs operating in some or all of the following channels detailed in table 2. The centre frequencies fTx indicated in table 2 are referred to as parameter D1 in EN 12253 [1]. Table 2: Frequency bands and centre frequencies fTx allocated for DSRC Pan European Service Frequencies National Service Frequencies Channel 1 5,795 GHz to 5,800 GHz, fTx = 5,7975 GHz Channel 2 5,800 GHz to 5,805 GHz, fTx = 5,8025 GHz Channel 3 5,805 GHz to 5,810 GHz, fTx = 5,8075 GHz Channel 4 5,810 GHz to 5,815 GHz, fTx = 5,8125 GHz Where equipment can be adjusted to operate at different operating frequencies other than channels 1 and 2, a minimum of two operating frequencies shall be chosen for the tests described in the present document such that the lower and higher limits of the provider's declared operating ranges of the equipment are covered. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 5.3 Antenna characteristic | All RSU antennas shall be LHCP in accordance with parameters D5 and D5a in EN 12253 [1]. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 5.4 Modulation | The carrier of frequency fTx, see table 2, shall be modulated in accordance with parameters D6, D6a and D6b in EN 12253 [1]. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6 General characteristics of On Board Unit | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.1 OBU sets | There exist two sets of OBUs called Set A and Set B which differ by the following parameters listed in table 3 either in terms of value or applicability, and which are defined in EN 13372 [i.5]. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 14 Table 3: Differences in OBU Sets EN 12253 [1] parameter abbreviation Set A Set B D11a Power limit for communication (upper) D12 n.a. Cut off power level of OBU U4a Maximum SSB e.i.r.p. (bore sight) U4b n.a. Maximum SSB e.i.r.p. (35°) U12b n.a. Conversion gain (upper limit) The provider shall declare which Set the unit complies with. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.2 OBU assemblies | The OBU as identically supplied for testing and usage by the end-user is a physical assembly which is located and operated in or on the vehicle to transmit and receive DSRC signals. The OBU may be assembled such that it is: • mountable in or on any part of the vehicle structure by the end-user according to guidelines in the user-manual, and optionally removable after proper installation; or • bonded to a part of the vehicle by a service station being authorized by the provider; or • an integral part of a vehicle component, such as a windscreen, bumper, or licence plate. In case the OBU is removable from its mounting device by the end-user, tests shall be performed with the OBU properly attached to its mounting device. The provider shall declare the physical assembly of the OBU. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.3 Power supply | The power supply shall meet the requirements given in clause A.1.2 for the selected operational conditions of the EUT. The power supply may be a built-in battery, an external battery, or a stabilized power supply, etc. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.4 Up-link sub-carrier frequencies | The sub-carrier signal or also called sub-carrier is a signal whose nominal single frequency fs can vary within a range specified by the sub-carrier frequency tolerance. It shall be capable of being modulated by a second, symbol-carrying signal, see clause 6.7. The up-link sub-carrier frequency is referred to as parameter U1 of EN 12253 [1]. Every DSRC OBU shall support the two sub-carrier frequencies fs of 1,5 MHz and 2,0 MHz. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.5 Antenna characteristic | All equipment antennas shall be LHCP according to parameters U5 and U5a in EN 12253 [1]. An OBU may provide either none, one, or two antenna connectors. In case an OBU does not provide an antenna connector, then either one antenna for receiving and transmitting, or one antenna for receiving and one antenna for transmitting are implemented. For a single antenna solution the phase centre of the OBU antenna is entitled Mc, see figure 1. For separated receive and transmit antennas it is assumed that they are close to each other and point approximately to the same direction. The centre between these two antennas then is entitled Mc. For easy reading of the present document Mc is referred to as "phase centre of the OBU antenna". ETSI ETSI TS 104 022 V1.1.1 (2024-06) 15 The minimum operational direction of the OBU receive and transmit antenna is characterized by a cone with opening angle θ around bore sight as depicted in figure 1. The OBU shall provide specific properties inside the cone. The border of the cone itself is referred to as worst case direction. The direction M0 and the phase centre Mc of the OBU antenna are related to measurements described in the present document. x y z θ θ boresight M0 M1 M2 M3 M4 Mc Figure 1: OBU antenna characteristic The angle θ is used in different tests of the present document. A value of θ = 35° is required for OBU minimum conversion gain and for OBU maximum single side band e.i.r.p. according to EN 12253 [1]. For other properties of the OBU, like sensitivity, the provider may declare an opening angle θ other than 35°. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.6 Carrier frequencies | According to parameter D3 in EN 12253 [1] every OBU shall be able to operate in all DSRC channels as indicated in table 2. For tests of OBU parameters described in the present document, only the carrier frequencies fTx defined for channel 1 and channel 4 in table 2 shall be considered. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 6.7 Modulation | The up-link sub-carrier, see clause 6.4, shall be modulated according to parameters U1b, U6, U6b and U6c in EN 12253 [1]. The modulated up-link sub-carrier then shall be used to modulate the carrier at frequency fTx received from an RSU, i.e.: the modulated up-link sub-carrier shall be multiplied with the received carrier. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 16 |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7 Parameter description and required limits | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.1 RSU | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.1.1 Modulation index | Figure 2 illustrates a two level amplitude modulated RSU carrier signal as required by parameter D6, D6a, and D6b in EN 12253 [1]. Vmax Vmin RSU transmit signal Signal amplitude Time Figure 2: Modulated RSU transmit signal The modulation index m is defined in equation (1) as: = (1) where Vmax, and Vmin are, respectively, maximum amplitudes of the modulated output signal of the RSU caused by bits 1 and 0. The modulation index is referred to as parameter D6a in EN 12253 [1]. The modulation index m shall be in the range 0,5 ≤ m ≤ 0,9. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.1.2 Intermodulation immunity | The intermodulation immunity is a measure of the capability of the receiver to receive a wanted modulated signal without exceeding a given degradation due to the presence of two or more unwanted signals with specific and different frequency relationships to the wanted signal frequency. This measure is given in terms of signal power Pu of the unwanted signals at the receiver antenna. For the purpose of the present document exactly two unwanted monochromatic signals shall be considered. The frequencies fu1 and fu2 of the two unwanted monochromatic signals shall be either at fu1 = 5 MHz and fu2 = 10 MHz displaced from the centre frequency of the wanted signal, or fu1 = -5 MHz and fu2 = -10 MHz displaced from the centre frequency of the wanted signal. The power levels Pu of the two unwanted monochromatic signals shall be equal. The power level of the wanted signal shall be 6 dB above the declared sensitivity level of the RSU receiver. The degradation limit is defined by the maximum allowed BER of 2,0 × 10-2. If not declared otherwise by the provider, then the intermodulation immunity shall be Pu ≥ -25 dBm. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 17 |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.2 OBU | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.2.1 Upper power limit for communication | Table 4: OBU upper power limit for communication for Sets A and B Upper power limit for communication PD11a according to parameter D11a of EN 12253 [1] Set A Set B −17 dBm −24 dBm The OBU shall provide a BER of less than or equal to 10-6 at the upper power limit for communication PD11a. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.2.2 Cut-off power level | This parameter applies only to Set B OBUs. The cut-off power level is the incident power level as received by a loss-less isotropic antenna below which an OBU shall not respond to a properly coded and modulated DSRC down-link signal. NOTE: There are protocol related requirements that request an OBU not to respond. These requirements are outside the scope of the present document. The cut-off power level is -60 dBm. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 7.2.3 Conversion gain | The conversion gain Gc is defined by Gc = EIRPObuTx / PObuRx, where PObuRx is the incident received carrier power level as referred to an isotropic loss-less antenna, and EIRPObuTx is the re-transmitted e.i.r.p. of the OBU in a single side-band. The OBU conversion gain is referred to as parameter U12 in EN 12253 [1]. NOTE: The OBU conversion gain includes receive antenna gain, transmit antenna gain and OBU losses. The OBU conversion gain Gc shall be at least 1 dB within a cone of θ = 35° relative to bore sight as depicted in figure 1. For Set B OBUs the OBU conversion gain Gc shall not exceed 10 dB. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8 Testing of Road Side Unit | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.1 Modulation index | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.1.1 General | This test shall be performed either with radiated or conducted measurements. Basic requirements and guidelines for measurements are provided in Annex A. Parameter descriptions and limits are provided in clause 7.1.1. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 18 |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.1.2 Radiated measurements | The test procedure shall be as follows: 1) Set up the measurement arrangement as detailed in clause A.6.6.1. 2) Set the transmit power level of the RSU to its maximum possible operational value. 3) Set the modulation index of the RSU to its minimum adjustable value within the allowed range. 4) Set the RSU to the mode, where it transmits continuously test signal TS1 as specified in table 5 in clause A.2. 5) Set the RSU transmit carrier frequency fTx to the initial value supported by this RSU in accordance with table 2 in clause 5.2. 6) Set the RD into the CW mode, also called zero span mode of operation, where the instrument is not sweeping across a frequency band. 7) Set the RBW to 2 MHz. 8) Measure Vmax and Vmin from envelope of RF signal, see figure 2. 9) Calculate the modulation index m according to equation 1 in clause 7.1.1. 10) Repeat steps 8 and 9 for the remaining value of the carrier frequency fTx in accordance with table 2 in clause 5.2. 11) Set the modulation index of the RSU to its maximum adjustable value within the allowed range and repeat steps 8 through 10. 12) For all measurements, the modulation index m shall be within the limits as specified in clause 7.1.1. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.1.3 Conducted measurements | The test procedure shall be as follows: 1) The output of the RSU transmitter shall be connected to the RD. 2) Set the transmit power of the RSU to its maximum possible operational value. 3) Set the modulation index of the RSU to its minimum adjustable value within the allowed range. 4) Set the RSU to the mode, where it transmits continuously test signal TS1 as specified in table 5 in clause A.2. 5) Set the RSU transmit carrier frequency fTx to the initial value supported by this RSU in accordance with table 2 in clause 5.2. 6) Set the RD into the CW mode, also called zero span mode of operation, where the instrument is not sweeping across a frequency band. 7) Set the RBW to 2 MHz. 8) Measure Vmax and Vmin from envelope of RF signal, see figure 2. 9) Calculate modulation index m according to equation 1 in clause 7.1.1. 10) Repeat steps 8 and 9 for the remaining value of the carrier frequency fTx in accordance with table 2 in clause 5.2. 11) Set the modulation index of the RSU to its maximum adjustable value within the allowed range and repeat steps 8 through 10. 12) For all measurements the modulation index m shall be within the limits as specified in clause 7.1.1. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 19 |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.2 Intermodulation immunity | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.2.1 General | Independent of the environmental profile declared by the provider, this test shall be performed only under normal test conditions defined in clause 4.2.2. This test shall be performed with radiated measurements. Basic requirements and guidelines for measurements are provided in Annex A. Parameter descriptions and limits are provided in clause 7.1.2. NOTE: The provider may extend the test in order to determine the actual value of the intermodulation immunity. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 8.2.2 Radiated measurements | The test procedure shall be as follows: 1) Set up the measurement arrangement as detailed in clause A.6.6.2. 2) Set the RSU to the mode that it transmits an unmodulated carrier. 3) Set the RSU output power to its maximum allowed value. 4) Set the modulation index to any convenient value if it is adjustable. 5) Set the RSU carrier frequency fTx to the initial value supported by this RSU in accordance with table 2 in clause 5.2. 6) Set the RSU to a mode such that the OBU shall use the lower sub-carrier frequency fs. 7) Set the frequency of the MSS1 to fTx + fs + 5 MHz and the frequency of the MSS2 to fTx + fs + 10 MHz. 8) Ensure that MSS1, MSS2 and the RSU are switched off. 9) Replace the RSU receiver by a power meter PM1. 10) Switch on MSS1 and adjust the power of its output signal such that PM1 measures a value of -25 dBm. 11) Switch off MSS1. 12) Switch on MSS2 and adjust the power of its output signal such that PM1 measures a value of -25 dBm. 13) Switch off MSS2. 14) Switch on the RSU transmitter and adjust AT1 such, that the incident signal power received by a loss-less isotropic antenna at the location of the OBU antenna equals -25 dBm to ensure reliable reception of messages by the OBU. 15) Set the OBU into a test mode that it transmits test signal TS2 as specified in table A.1 in clause A.2. 16) Adjust AT2 such, that the power measured by PM1 equals the sum of the sensitivity of the RSU declared by the provider plus 6 dB. 17) Replace the PM1 by the RSU receiver. 18) Set RSU and OBU to a mode so that they are able to process test messages TM1 as specified in table 5 in clause A.2. 19) Switch on MSS1 and MSS2. 20) Measure the BER of the RSU receiver according to clause A.9. If the BER is larger than 2,0 × 10-2 the test failed. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 20 21) Set the RSU to a mode such that the OBU shall use the upper sub-carrier frequency fs. 22) Repeat step 20. 23) Set the RSU to a mode such that the OBU shall use the lower sub-carrier frequency fs. 24) Set the frequency of the MSS1 to fTx + fs - 5 MHz and the frequency of the MSS2 to fTx + fs - 10 MHz. 25) Repeat steps 8 through 22. 26) Repeat steps 6 through 25 for the remaining value of the carrier frequency fTx in accordance with table 2 in clause 5.2. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9 Testing of On Board Unit | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.1 Upper power limit for communication | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.1.1 General | This test shall be performed either with radiated or conducted measurements. Basic requirements and guidelines for measurements are provided in Annex A. Parameter descriptions and limits are provided in clause 7.2.1. The description below assumes that a RSU is used to transmit down-link signals and to receive up-link signals, both of type TM1 as specified in table A.1 in clause A.2. NOTE: The provider may extend the test to determine the actual value of the upper power limit for communication. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.1.2 Radiated measurements | The test procedure shall be as follows: 1) Prepare the test site according to clause A.6.5.2. 2) Set the SMS1 such that it continuously transmits test signal TS1 as specified in table A.1 in clause A.2. 3) Set the carrier frequency fTx of SMS1 defined for channel 1 according to table 2 and clause 6.6. 4) Set the modulation index of the signal transmitted by the SMS1 to 0,9 or to the greatest possible value within the allowed range of 0,5 to 0,9 supported by the SMS1. 5) Replace the OBU receiver by an RSA such that their phase centres and bore sights coincide. Connect the RSA to the power meter PM1. 6) Adjust the output signal power level of the SMS1 such that the signal power level PRSA measured by the power meter PM1 amounts to: RSA = inc × RSA × 1 −|RSA| (2) where Pinc, and ρRSA denote, respectively, the maximum allowed value according to table 4 converted to Watt, and the reflection coefficient at the connector of the RSA. 7) Replace RSA by the OBU receiver. 8) Measure the BER of the OBU receiver according to clause A.9. If the BER is larger than 10-6 the test failed. 9) Repeat steps 5 through 8 for the carrier frequency fTx defined for channel 4 according to table 2 and clause 6.6. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 21 |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.1.3 Conducted measurements | The test procedure shall be as follows: 1) Prepare the test site according to clause A.5.4.2. 2) Set the SMS1 such that it continuously transmits test signal TS1 as specified in table A.1 in clause A.2. 3) Set the carrier frequency fTx of SMS1 defined for channel 1 according to table 2 and clause 6.6. 4) Set the modulation index m of the signal transmitted by the SMS1 to 0,9 or to the greatest possible value within the allowed range of 0,5 to 0,9 supported by the SMS1. 5) Replace the OBU receiver by a power meter PM1. 6) Adjust the output signal power of the SMS1 such that the signal power indicated by the power meter PM1 equals the sum of the maximum allowed value according to table 4 in dBm and the gain in dB of the OBU receive antenna as declared by the provider. 7) Replace PM1 by the OBU receiver. 8) Measure the BER of the OBU receiver according to clause A.9. If the BER is larger than 10-6 the test failed. 9) Repeat steps 5 through 8 for the carrier frequency fTx defined for channel 4 according to table 2 and clause 6.6. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.2 Cut-off power level | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.2.1 General | This test shall be performed either with radiated or conducted measurements. Basic requirements and guidelines for measurements are provided in Annex A. Parameter descriptions and limits are provided in clause 7.2.2. The description below assumes that an RSU is used to receive up-link signals and to generate down-link signals, both of type TM1 as specified in table A.1 in clause A.2. The test can be performed accordingly based on laboratory instruments, i.e. an RSU simulator, to generate down-link messages of type TM1 and to receive and evaluate up-link signals of type TM1. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.2.2 Radiated measurements | The test procedure shall be as follows: 1) Prepare the test site according to clause A.6.5.2. 2) Set the SMS1 such that it continuously transmits test message TM1 as specified in table A.1 in clause A.2, i.e. it invites the OBU for initialization by sending BSTs. 3) Set the carrier frequency fTx of SMS1 defined for channel 1 according to table 2 and clause 6.6. 4) Set the modulation index m of the signal transmitted by the SMS1 to 0,9. 5) Replace the OBU receiver by an RSA of gain GRSA such that their phase centres and bore sights coincide. Connect the RSA to the power meter PM1. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 22 6) Adjust the output signal power of the SMS1 such that the signal power indicated by the power meter PM1 amounts to: RSA = inc × RSA × 1 −|RSA| (3) where Pinc equals -61 dBm converted to Watt, and ρRSA denotes the reflection coefficient at the connector of the RSA. 7) Switch off the SMS1. 8) Replace the RSA by the OBU receiver and wait until the OBU is in sleep mode. 9) Switch on the SMS1. 10) Observe for the time needed for transmitting 100 subsequent BST messages whether the OBU responds with a VST. If a VST is received, then the test failed. 11) Repeat steps 5 through 10 for the carrier frequency fTx defined for channel 4 according to table 2 and clause 6.6. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.2.3 Conducted measurements | The test procedure shall be as follows: 1) Prepare the test site according to clause A.5.4.2. 2) Set the SMS1 such that it continuously transmits test message TM1 as specified in table A.1 in clause A.2, i.e. invites the OBU for initialization by sending BSTs. 3) Set the carrier frequency fTx of SMS1 defined for channel 1 according to table 2 and clause 6.6. 4) Set the modulation index m of the signal transmitted by the SMS1 to 0,9. 5) Replace the OBU receiver by the power meter PM1. 6) Adjust the output power level of the SMS1 such that the signal power level indicated by the power meter PM1 equals the sum of -61 dBm plus the maximum gain in dB of the OBU receive antenna as declared by the provider. 7) Switch off the SMS1. 8) Replace PM1 by the OBU receiver and wait until the OBU is in sleep mode. 9) Switch on the SMS1. 10) Observe for the time needed for transmitting 100 subsequent BST messages whether the OBU responds with a VST. If a VST is received, the test failed. 11) Repeat steps 5 through 10 for the carrier frequency fTx defined for channel 4 according to table 2 and clause 6.6. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.3 Conversion gain | |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.3.1 General | This test shall be performed either with radiated or conducted measurements. Basic requirements and guidelines for measurements are provided in Annex A. Parameter descriptions and limits are provided in clause 7.2.3. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 23 |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.3.2 Radiated measurement | The test procedure shall be as follows: 1) Prepare the test site according to clause A.6.5.1. The initial alignment of the OBU as needed in step 4 shall be according to M0 in figure 1, i.e.: the bore sight of the OBU antenna shall point towards the phase centre of the TA. 2) Switch on the MSS1, tune its frequency to the carrier frequencies fTx defined for channel 1 according to table 2 and clause 6.6. 3) Adjust the output power of the MSS1 such that the power PRSA measured by the power meter PM1 amounts to: RSA = inc × RSA × 1 −|RSA| (4) where Pinc, and ρRSA denote, respectively, the minimum allowed incident signal power level PD11b = -43 dBm (given by the OBU sensitivity limit), and the reflection coefficient at the connector of the RSA. 4) Replace the RSA by the OBU such that its phase centre Mc is as coincident with the axis of rotation of the turntable as possible. If the phase centre Mc of the OBU is unknown and no antenna is visible, the volume centre of the OBU shall be used instead. Align the OBU's bore sight as required. 5) Set the OBU to a test mode such that it re-transmits test signal TS2 as specified in table 5 in clause A.2 with sub-carrier frequency fs. 6) Measure the smaller of the power levels Pssb within the two side bands by the RD with a RBW of 100 kHz and report this value together with the value of fs and fTx and the orientation Mi, i = 0…4, see figure 1. 7) Repeat step 6 for the other value of the sub-carrier frequency fs. 8) Repeat steps 3 through 7 for the carrier frequency fTx defined for channel 4 according to table 2 and clause 6.6. 9) Repeat steps 2 through 8 for all remaining OBU orientations Mi as indicated in figure 1. 10) Replace the OBU by a LHCP calibrated TSA of gain GTSA and reflection coefficient ρTSA at its connector suited for the range of carrier frequencies fTx listed in table 2 in such a way that its phase centre coincides with the one of the OBU transmitting antenna. If the measurement arrangement with one test antenna is used, then the bore sight of the TSA shall point towards the phase centre of the TTA. If the measurement arrangement with two test antennas is used, then the bore sight of the TSA shall point towards position Mcentre. 11) Connect the output of the TSA via the optional balun BLN, if required, of feed through attenuation ATNBLN, and the calibrated FCCA1 of feed through attenuation ATNCA1 to the calibrated MSS2 that shall be tuned to the frequency which is the sum of the carrier frequency fTx as set in step 2 and the sub-carrier frequency ± fs as set in step 5. The sign of the sub-carrier frequency is defined by the side band, which provided the smaller of the two power levels Pssb in step 6. 12) Adjust the output signal level PMSS2 of the MSS2 until the level, measured on the RD, becomes identical to the corresponding value of Pssb recorded in step 6. Calculate the retransmitted power: reTx = MSS2×TSA× | TSA| CA1× BLN (5) where all the parameters in equation (5) are related to the corresponding measurement frequencies, and report it together with the value of fs and fTx. 13) Repeat step 12 for all remaining combinations of fs and fTx for which a result is available from step 6. 14) The conversion gain Gc of the OBU shall be calculated by: = reTx inc (6) ETSI ETSI TS 104 022 V1.1.1 (2024-06) 24 None of the calculated conversion gains shall be outside the limits specified in clause 7.2.3. |
fd33e04bff2cf7c00365635588bca5b2 | 104 022 | 9.3.3 Conducted measurement | The test procedure shall be as follows: 1) Prepare the test site according to clause A.5.4.1. The gain of the OBU's receive and transmit antenna for the initial alignment of the OBU as needed in step 4 is assumed to be according to direction M0 in figure 1. 2) Tune the frequency of the MSS1's output signal to the carrier frequencies fTx defined for channel 1 according to table 2 and clause 6.6. 3) Replace the OBU receiver by the power meter PM1. 4) Adjust the output power of the MSS1 such that the power measured by the power meter PM1 matches the minimum allowed incident signal power level Pinc,dBm = PD11b = -43 dBm (given by the OBU sensitivity limit) increased by the maximum gain GOBU,Rx(Mi) of the OBU receive antenna, i.e. in direction Mi, i = 0…4, according to figure 1, as declared by the provider. 5) Replace the power meter PM1 by the OBU receiver. 6) Set the OBU to a test mode such that it re-transmits test signal TS2 as specified in table A.1 in clause A.2 with sub-carrier frequency fs. 7) Measure the smaller of the power levels Pssb within the two side bands by the RD with a RBW of 100 kHz considering all losses the signal suffers between the output connector of the OBU and the input connector of the RD and report this value together with the value of fs and fTx. 8) The retransmitted power PreTx of the OBU shall be calculated by: reTxMi = ssb × OBU,TxMi (7) where GOBU,Tx(Mi) is the OBU's transmit antenna gain in the direction Mi. 9) Repeat steps 7 and 8 for the other value of the sub-carrier frequency fs. 10) Repeat steps 3 through 9 for the carrier frequency fTx defined for channel 4 according to table 2 and clause 6.6. 11) Repeat steps 2 through 10 for all remaining OBU orientations Mi as indicated in figure 1. 12) The conversion gain Mi of the OBU shall be calculated by: Mi = reTxMi inc (8) None of the calculated conversion gains Mi shall be outside the limits specified in clause 7.2.3. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 25 Annex A (normative): Basics of testing A.1 General conditions A.1.1 Environment Tests defined in the present document shall be carried out at representative points within the boundary limits of the mandatory environmental conditions as defined in clause 4.2.2. Where technical performance varies subject to environmental conditions, tests may also be carried out under conditions as declared by the provider and being within the boundary limits of the declared operational environmental profile in order to give confidence of compliance for the affected technical requirements. A possible provider declaration can be based on the extreme categories I, II, III as defined in clause 4.2.3. A.1.2 Power source For testing the equipment, it shall be powered by a test power source, capable of producing test voltages as declared by the provider. For battery operated equipment the battery shall be removed when possible, and an external test power source shall be suitably decoupled. For radiated measurements any external power leads shall be arranged so as not to affect the measurements. If necessary, the external test power source may be replaced with the supplied or recommended internal batteries at the required voltage, or a battery simulator. This shall be stated on the test report. For radiated measurements on portable equipment, fully charged internal batteries shall be used. The batteries used shall be as supplied or recommended by the provider of the EUT. During tests the external test power source voltages shall be within a tolerance of ±1 % relative to the voltage at the beginning of each test. The value of this tolerance can be critical for certain measurements. Using a smaller tolerance provides a better uncertainty value for these measurements. If internal batteries are used, at the end of each test the voltage shall be within a tolerance of ±5 % relative to the voltage at the beginning of each test. The internal impedance of the external test power source shall be low enough for its effect on the test results to be negligible. The voltage of the external test power source shall be measured at the input terminals of the equipment. A.1.3 Thermal balance Before measurements are made the equipment shall have reached thermal balance in the test chamber. The equipment shall be switched off during the temperature stabilizing period. In the case of equipment containing temperature stabilization circuits designed to operate continuously, the temperature stabilization circuits shall be switched on for a time period as declared by the provider such that thermal balance has been obtained, and the equipment shall then meet the specified requirements. If the thermal balance is not checked by measurements, a temperature stabilizing period of at least one hour, or such period as may be decided by the test laboratory, shall be allowed. The sequence of measurements shall be chosen and the relative humidity content in the test chamber shall be controlled so that condensation does not occur. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 26 A.2 Test signals Test signals and test messages are defined in table A.1. Table A.1: Test signals and messages Test signal/message Description Test Messages (TM1) Set of DSRC messages supporting initialization and ECHO command compliant to EN 12795 [i.6], EN 12834 [i.7] and ISO 14906 [i.4]. Test Signal (TS1) Properly modulated and coded DSRC signal where the data is a continuously repeated maximum length pseudo-random sequence generated by a linear feedback shift register. The period of the pseudo-random sequence shall be 511 bits. Test Signal (TS2) Continuous DSRC up-link signal with unmodulated sub-carrier. The sub-carrier frequency shall be settable to fs = 1,5 MHz and fs = 2,0 MHz, respectively. Data coding and bit rates in down-link and up-link shall be according to parameters D7, U7 and D8, D8a, U8, U8a of EN 12253 [1], respectively. A.3 Test sites A.3.1 Test sites overview All tests specified in the present document can be performed in a shielded anechoic chamber or at an open area test site. The modulation index test can alternatively also be done in a test fixture. Basics on test sites are specified in the following clauses. More details on test sites can be found in ETSI TS 103 052 [i.10]. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 27 A.3.2 Shielded anechoic chamber A typical anechoic chamber is shown in figure A.1. This type of test chamber attempts to simulate free space conditions. Absorber Absorber Absorber Absorber Reference points Test antenna d Non-conductive supports EUT Shielding Figure A.1: Typical anechoic chamber The chamber contains suitable antenna supports on both ends. The supports carrying the test antenna and EUT shall be made of a non-permeable material featuring a low value of its relative permittivity. The anechoic chamber shall be shielded. Internal walls, floor and ceiling shall be covered with radio absorbing material. The shielding and return loss for perpendicular wave incidence versus frequency as detailed in figure A.2 shall be met by anechoic chambers used to perform tests. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 28 0 10 20 30 40 50 60 70 80 90 100 110 Loss / dB 10k 100k 1M 10M 100M 1G 10G 100G 30M 300M 26G Frequency f / Hz 105 Minimum shielding loss Minimum return loss Figure A.2: Minimal shielding and return loss for shielded anechoic chambers Both absolute and relative measurements can be performed in an anechoic chamber. Where absolute measurements are to be carried out the chamber shall be verified. The shielded anechoic chamber test site shall be validated for the frequency range being applicable. A.3.3 Open area test site A typical open area test site is shown in figure A.3. Range length 3 m or 10 m Turntable Ground plane Dipole antennas Antenna mast Figure A.3: Typical open area test site The ground plane shall provide adequate size, such as to approximate infinite size. Relevant parts of the ground plane shall be covered by absorbing material. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 29 Measurements performed in open area test sites follow the same procedures as detailed for radiated measurements performed in shielded anechoic chambers. The open area test site shall be calibrated and validated for the frequency range being applicable. A.3.4 Test fixture A test fixture is a device that allows for conducted measurements of an EUT that does not provide antenna connectors itself. The EUT can be either an OBU or an RSU. A test fixture consists of at least one RF connector featuring a characteristic impedance of 50 Ω, subsequently called 50 Ω RF connector, and a device for electromagnetic coupling to the EUT. It incorporates a means for repeatable positioning of the EUT. The following figure A.4 illustrates a typical test fixture. Figure A.4: Typical test fixture The coupling device usually comprises a small antenna that is placed, physically and electrically, close to the EUT. This coupling device is used for sampling or generating the test fields when the EUT is undergoing testing. Figure A.5 illustrates an EUT mounted on a test fixture. Figure A.5: EUT mounted in a typical test fixture The entire assembly of test fixture plus EUT is generally compact and it can be regarded as a EUT with antenna connector. Its compactness enables the whole assembly to be accommodated within a test chamber, usually a climatic facility. The circuitry associated with the RF coupling device should contain no active or non-linear components and should present a VSWR of better than 1,5 to a 50 Ω line. Absolute measurements shall not be made in a test fixture. Since the antennas of the EUT and the test fixture might be mutually in the near-field of each other. Hence, only relative measurements shall be performed that have to be related to results taken on a verified free field test site. The way to relate the results is by a process, referred to as field equalization, in which the relevant parameter, e.g.: effective radiated power, receiver sensitivity, etc. is initially measured on a free field test site under normal environmental conditions and then subsequently re-measured using the test fixture under the very same environmental conditions. The relation between the two results is termed the coupling factor of the test fixture and provides the link between all the results of EUT tests carried out in the test fixture and its performance on a verified free field test site. Generally, the coupling factor should not be greater than 20 dB. Emission tests are limited to the nominal frequencies, for which the performance of the test fixture has been verified. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 30 Only after it has been verified that the test fixture does not affect performance of the EUT, the EUT can be confidently tested. The test fixtures shall be calibrated and validated for the frequency range they are used for. A.4 General requirements for RF cables All RF cables including their connectors at both ends used within the measurement arrangements and set ups shall be of coaxial type featuring within the frequency range they are used: • a nominal characteristic impedance of 50 Ω; • a VSWR of less than 1,2 at both of their ends, preferably better; • a shielding loss exceeding 60 dB, preferably better. All RF cables exposed to radiation shall be loaded with ferrite beads spaced with a gap of Dfb between each other along the entire length of the cable. Such cables are referred to as FCCA. The gap Dfb shall be smaller than half of the signal's wavelength under test. All RF cables shall be routed suitably in order to reduce impacts on antenna radiation pattern, antenna gain, antenna impedance. A.5 Conducted measurements A.5.1 One antenna connector arrangement Figure A.6 shows the measurement arrangements that shall be used in case of a single antenna connector at the EUT. MSS1 or SMS1 RD a) CC PM MSS 1 RD off b) MSS 2 MSS 1 off RD c) CC CC EUT FCCA FCCA FCCA FCCA FCCA FCCA FCCA FCCA FCCA Figure A.6: Measurement arrangement with one antenna connector: a) for measurement of EUT parameters b) for adjusting input power to EUT c) for substitution measurements ETSI ETSI TS 104 022 V1.1.1 (2024-06) 31 A.5.2 Two antenna connectors arrangement Figure A.7 shows the measurement arrangements that shall be used in case of a two antenna connectors at the EUT. MSS1 or SMS 1 RD a) MSS 1 RD off b) PM RD MSS 1 off c) MSS 2 EUT FCCA FCCA FCCA FCCA FCCA FCCA Figure A.7: Measurement arrangement with two antenna connectors: a) for measurement of EUT parameters b) for adjusting input power to EUT c) for substitution measurements A.5.3 Test site requirements Conducted measurements shall be performed at the antenna connector(s) of the EUT. A.5.4 Site preparation A.5.4.1 Monochromatic signals If the measurement arrangement with one antenna connector is used, the measurement set up depicted in figure 6 applies and the site preparation is as follows: 1) The calibrated MSS1 shall be connected to the antenna connector of the EUT via the calibrated CC providing three terminals. 2) The RD shall be connected to the antenna connector of the EUT via the remaining third terminal of the calibrated CC. If the measurement arrangement with two antenna connectors is used, the measurement set up depicted in figure A.7 applies and the site preparation is as follows: 1) The calibrated MSS1 shall be connected to the receive antenna connector of the EUT. 2) The RD shall be connected to the transmit antenna connector of the EUT. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 32 A.5.4.2 Modulated signals If the measurement arrangement with one antenna connector is used, the measurement set up depicted in figure A.6 applies and the site preparation is as follows: 1) The calibrated SMS1 shall be connected to the antenna connector of the EUT via the calibrated CC providing three terminals. 2) The RD, i.e. either an RSU receiver or a measurement receiver, shall be connected to the antenna connector of the EUT via the remaining third terminal of the calibrated CC. If the measurement arrangement with two antenna connectors is used, the measurement set up depicted in figure A.7 applies and the site preparation is as follows: 1) The calibrated SMS1 shall be connected to the receive antenna connector of the EUT. 2) The RD, i.e. either an RSU receiver or a measurement receiver, shall be connected to the transmit antenna connector of the EUT. A.6 Radiated measurements A.6.1 One antenna arrangement Figure A.8 shows the measurement arrangements that shall be used in case one test antenna TA for transmitting and receiving signals are selected for testing the EUT. Far-field region & free-space condition d MSS 2 Test antenna (TA) Gain GTA boresight MSS 1 off RD TSA FCCA c) Far-field region & free-space condition d Test antenna (TA) Gain GTA boresight MSS1 or SMS1 RD off RSA b) Far-field region & free-space condition CC d EUT Test antenna (TA) Gain GTA boresight MSS 1 RD a) PM 1 Gain GRSA Gain GTSA CC CC FCCA FCCA FCCA FCCA FCCA FCCA FCCA FCCA FCCA Figure A.8: Measurement arrangement with one test antennas: a) for measurements of EUT parameters b) for adjustment of the incident power to the EUT c) for measurement steps using the substitution antenna ETSI ETSI TS 104 022 V1.1.1 (2024-06) 33 A.6.2 Two antennas arrangement Figure A.9 shows the measurement arrangements that shall be used in case two test antennas, i.e. TTA and RTA, are selected for testing the EUT. Far-field region & free-space condition TTA RTA d MCentre boresight α boresight α boresight MSS1 or SMS1 RD Far-field region & free-space condition TTA RTA d MCentre boresight α boresight α boresight MSS 1 RSA RD off Far-field region & free-space condition TTA RTA d MCentre boresight α boresight α boresight RD TSA MSS 1 off a) b) c) Gain GRSA Gain GTSA EUT PM 1 MSS 2 ddisplace ddisplace ddisplace FCCA FCCA FCCA FCCA FCCA FCCA FCCA Figure A.9: Measurement arrangement with two test antennas: a) for measurements of EUT parameters b) for adjustment of the incident power to the EUT c) for measurement steps using the substitution antenna ETSI ETSI TS 104 022 V1.1.1 (2024-06) 34 A.6.3 Test site requirements A.6.3.1 Measurement distances Within an open area test site or a shielded anechoic chamber the measurement distance or range length d depicted in figures A.8 and A.9 shall be such, that the antennas on both sides of the radio link are mutually in the far field of each other, i.e. d shall be according to the most stringent of the following three equations: > ×0,TA0,EUT , > 5 × 0,TA + 0,EUT and d > 2 × λ, (A.1) where D0,TA, D0,EUT and λ denote the largest dimension of the test antenna, the EUT antenna, and the wavelength, respectively. This distance d shall be measured between: • the centre of aperture of the test antenna TA, in case of a horn antenna, or the feeding point in case the TA is of another type; and • the feeding point of the EUT antenna if the location of the EUT antenna is known, or the volume centre of the EUT if the location of its antennas is unknown. A.6.3.2 Free-space wave propagation Within an open area test site or a shielded anechoic chamber, a radio path between a transmitting and receiving antenna requires a certain amount of clearance around the central or direct ray if the signal expected from free-space propagation is to be received. The clearance is usually quoted in terms of Fresnel zones. As depicted in figure A.10 the first Fresnel zone encloses all radio paths from the transmitting to the receiving antenna for which the detour path length dF1 + dF2 relative to the length d of the direct radio path does not exceed half of the wavelength λ, i.e. a phase change of 180°, of the radiated signal in air: dF1 + dF2 - d ≤ λ/2. (A.2) Disregarding the non-conductive, dielectric supports of the EUT and the test antenna(s) the clearance around the LOS path between the transmitting and receiving antenna shall be such that at least the first Fresnel zone is free of any obstacles. Reference or focal points Test antenna Non-conductive supports 1st Fresnel Zone EUT d dF1 dF2 Central or direct path Detour path Figure A.10: First Fresnel zone with direct and detour radio path ETSI ETSI TS 104 022 V1.1.1 (2024-06) 35 A.6.4 Test and substitution antennas Test antennas are used to detect the radiation from the EUT or to transmit a signal towards the EUT while substitution antennas together with signal generators are used to replace the EUT and its antenna in substitution measurements. The test or substitution antenna shall be either LHCP, LP, or XP, whichever is required in the test procedure of the respective EUT parameter. Cross-polarized test or substitution antennas require a XPD > 25 dB within their specified frequency range. Preferably test or substitution antennas with pronounced directivities shall be used. However, their directivities Di relative to an isotropic radiator shall be such that the antennas on both sides of the radio link are mutually in the far field region of each other. If the symmetry of the test or substitution antenna does not match the one of its feeding cables, a symmetry matching circuit (balun) shall be inserted between the antenna output and the input of its feeding RF cable. The return loss at the terminal of the test or substitution antenna shall exceed 15 dB within its specified frequency range. When measuring signals in the frequency range up to 1 GHz the test or substitution antenna shall be either: • a half wavelength dipole, resonant at the operating frequency; or • a shortened dipole, calibrated to the half wavelength dipole; or • a biconical antenna. For measurements between 1 GHz and 4 GHz either: • a half wavelength dipole; or • a biconical antenna; or • a horn radiator may be used. When measuring signals in the frequency range above 4 GHz a horn antenna shall be used. The type of test or substitution antenna used in the tests shall be stated in the test report. A.6.5 Site preparation for OBU measurements A.6.5.1 Monochromatic signals If the measurement arrangement with one test antenna is used, the measurement set up depicted in figure A.8 applies and the site preparation is as follows: 1) The LHCP calibrated Test Antenna (TA, TTA: transmit path, RTA: receive path) shall be suited for the range of carrier frequencies fTx in accordance with clause 6.6. It shall be mounted in a shielded anechoic chamber on a vertical pole. The distance between any part of this TA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). The height of the phase centres above floor of the TA and the CA shall be equal. The CA is either the OBU antenna (EUT) or the RSA. The bore sight of the TTA shall point towards the phase centre of the CA. 2) The TA shall be connected via a CC featuring three terminals to a calibrated MSS1 using calibrated FCCAs. The remaining third terminal of the circulator shall be connected via a calibrated FCCA to the input of a calibrated RD, i.e. spectrum analyser or measuring receiver, calibrated at the frequencies of the monochromatic signals under consideration. Appropriate precautions shall be taken to prevent overloading the input of the RD. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 36 3) The LHCP calibrated RSA of gain GRSA shall be suited for the range of carrier frequencies fTx in accordance with clause 6.6. It shall be mounted on a vertical pole within the "quiet zone" at the other end of the shielded anechoic chamber. This pole shall be mounted on a turntable allowing rotating the RSA's phase centre around a vertical axis. The distance between any part of the RSA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). Further, the distance d between the TTA and the RSA shall be such that the two antennas are mutually in the far field of each other, see clause A.6.3.1. The bore sight of the RSA shall point towards the phase centre of the TA. The output of the RSA shall be connected directly to the power sensor of power meter PM1 that shall be calibrated to the frequency of the monochromatic signal under consideration. If the measurement arrangement with two test antennas is used, the measurement set up depicted in figure A.9 applies and the site preparation is as follows: 1) The LHCP calibrated TTA and the LHCP calibrated RTA shall each be suited for the range of carrier frequencies fTx in accordance with clause 6.6. They shall be mounted in a shielded anechoic chamber on a vertical pole. These two antennas shall be displaced either horizontally or vertically such as to minimize the coupling between them. Vertically polarized TTA and RTA shall be displaced vertically whilst horizontally polarized TTA and RTA shall be displaced horizontally. Additionally, the phase centre of the TTA shall be displaced from the phase centre of the RTA by a distance ddisplace such that the coupling loss between the two antennas becomes larger than 30 dB and the overall uncertainty of the measurement set-up shall comply with the requirements specified in table B.1. The actual coupling loss and the distance ddisplace between the TTA and the RTA shall be stated in the test report together with a unique identification of the TTA and the RTA used. The position between both phase centres is denoted Mcentre. The distance between any part of the TTA and the RTA with respect to the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). The height of Mcentre and the phase centre of the CA above floor shall be equal. The CA is either the OBU antenna or the RSA. The bore sight of the TTA and the RTA shall point towards the phase centre of the CA. 2) The TTA shall be connected to the calibrated MSS1 using calibrated FCCAs. 3) The RTA shall be connected to the input of the calibrated RD, i.e. a spectrum analyser or a measuring receiver, using calibrated FCCA. The RD shall be calibrated at the frequencies of the monochromatic signals under consideration. Appropriate precautions shall be taken to prevent overloading the input of the RD. 4) The LHCP RSA of gain GRSA shall be suited for the range of carrier frequencies fTx in accordance with clause 6.6. It shall be mounted on a vertical pole within the "quiet zone" at the other end of the shielded anechoic chamber. This pole shall be mounted on a turntable allowing to rotate the RSA's phase centre around a vertical axis. The RSA shall be positioned close to the middle between the ceiling and the floor. Its bore sight shall point to the centre between the phase centres of the TTA and the RTA. The distance between any part of the RSA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). Further, the distance d between the TTA and the RSA as well as between the RTA and the RSA shall be such that the two antennas on both sides of the radio link are mutually in the far field region of each other, see clause A.6.3.1. Additionally, the distance d between CA and the position Mcentre shall be such that the displacement angle αdisplace between TTA and RTA as observed from the CA complies with: displace = 2 × displace × , (A.3) displace ≤2 for horizontally displaced antennas, (A.4) displace ≤6 for vertically displaced antennas. (A.5) The output of the RSA shall be connected directly to the power sensor of power meter PM1 that shall be calibrated at the frequencies of the monochromatic signals under consideration. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 37 A.6.5.2 Modulated signals If the measurement arrangement with one test antenna is used, the measurement set up depicted in figure A.8 applies and the site preparation is as follows: 1) The LHCP calibrated test antenna (TA, TTA: transmit path, RTA: receive path) shall be suited for the range of carrier frequencies fTx in accordance with clause 6.6. It shall be mounted in a shielded anechoic chamber on a vertical pole. The distance between any part of this TA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). The height of the phase centres above floor of the TA and the CA shall be equal. The CA is either the OBU antenna (EUT) or the RSA. The bore sight of the TTA shall point towards the phase centre of the CA. 2) The TA shall be connected via a CC featuring three terminals to the calibrated SMS1 using calibrated FCCAs. The remaining third terminal of the circulator shall be connected via a calibrated FCCA to the input of the calibrated RD, i.e. RSU receiver or measuring receiver, calibrated at the frequencies of the modulated signals or messages under consideration. Appropriate precautions shall be taken to prevent overloading the input of the RD. 3) The LHCP calibrated RSA of gain GRSA shall be suited for the range of carrier frequencies fTx in accordance with clause 6.6. It shall be mounted on a vertical pole within the "quiet zone" at the other end of the shielded anechoic chamber. This pole shall be mounted on a turntable allowing to rotate the RSA's phase centre around a vertical axis. The distance between any part of the RSA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). Further, the distance d between the TTA and the RSA shall be such that the two antennas are mutually in the far field of each other, see clause A.6.3.1. The bore sight of the RSA shall point towards the phase centre of the TA. The output of the RSA shall be connected directly to the power sensor of power meter PM1 that shall be calibrated at the frequencies of the signals under consideration. If the measurement arrangement with two test antennas is used, the measurement set up depicted in figure A.9 applies and the site preparation is as follows: 1) The LHCP calibrated TTA and the LHCP calibrated RTA shall each be suited for the range of carrier frequencies fTx in accordance with clause 6.6. They shall be mounted in a shielded anechoic chamber on a vertical pole. These two antennas shall be displaced either horizontally or vertically such as to minimize the coupling between them. Vertically polarized TTA and RTA shall be displaced vertically whilst horizontally polarized TTA and RTA shall be displaced horizontally. Additionally, the phase centre of the TTA shall be displaced from the phase centre of the RTA by a distance ddisplace such that the coupling loss between the two antennas becomes larger than 30 dB and the overall uncertainty of the measurement set-up shall comply with the requirements specified in table B.1. The actual coupling loss and the distance ddisplace between the TTA and the RTA shall be stated in the test report together with a unique identification of the TTA and the RTA used. The position between both phase centres is denoted Mcentre. The distance between any part of the TTA and the RTA with respect to the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). The height of Mcentre and the phase centre of the CA above floor shall be equal. The CA is either the OBU antenna or the RSA. The bore sight of the TTA and the RTA shall point towards the phase centre of the CA. 2) The TTA shall be connected to a calibrated SMS1 using calibrated FCCAs. 3) The RTA shall be connected to the input of the calibrated RD, i.e. an RSU receiver or a measuring receiver, using a calibrated FCCA. The RD shall be calibrated to the frequency of the modulated signal or message under consideration. Appropriate precautions shall be taken to prevent overloading the input of the RD. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 38 4) The LHCP RSA of gain GRSA shall be suited for the range of carrier frequencies fTx in accordance with clause 6.6. It shall be mounted on a vertical pole within the "quiet zone" at the other end of the shielded anechoic chamber. This pole shall be mounted on a turntable allowing to rotate the RSA's phase centre around a vertical axis. The RSA shall be positioned close to the middle between the ceiling and the floor. Its bore sight shall point to the centre between the phase centres of the TTA and the RTA. The distance between any part of the RSA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). Further, the distance d between the TTA and the RSA as well as between the RTA and the RSA shall be such that the two antennas on both sides of the radio link are mutually in the far field region of each other, see clause A.6.3.1. Additionally, the distance d between the CA and the position Mcentre shall be such that the displacement angle αdisplace between the TTA and the RTA as observed from the CA complies with: displace = 2 × displace × , (A.6) displace ≤2 for horizontally displaced antennas, (A.7) displace ≤6 for vertically displaced antennas. (A.8) The output of the RSA shall be connected directly to the power sensor of the power meter PM1 that shall be calibrated at the frequencies of the signals under consideration. A.6.6 Site preparation for RSU measurements A.6.6.1 Arrangement for transmit parameters Figure A.11 details the arrangement used for measurement of the modulation index. Far-field region & free-space condition d RD RSU Transmitting Antenna (RTxA) Gain GRTxA boresight RSU RTA Gain GRTA FCCA FCCA Figure A.11: RSU transmit parameter measurement arrangement 1) The LHCP RTxA shall be mounted on a vertical pole within the "quiet zone" of the shielded anechoic chamber. The distance between any part of the RTxA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). 2) The RTA shall be suited for the range of carrier frequencies fTx in accordance with table 2 in clause 5.2. It shall be mounted on a pole at the other end of the shielded anechoic chamber. The distance between any part of the RTA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). The RTA shall be LHCP if not stated otherwise in the test procedures. 3) The distance d between the RTxA and the RTA shall be such that the two antennas are mutually in the far field of each other, see clause A.6.3.1. 4) The phase centres of the RTxA and the RTA shall be at the same height above floor. 5) The bore sight of the RTA shall point towards the phase centre of the RTxA. The bore sight of the RTxA shall point towards the phase centre of the RTA. 6) Connect the RSU transmitter to the RTxA via an FCCA. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 39 7) Connect the RTA to the RD via an FCCA. A.6.6.2 Arrangement for receive parameters Figures A.12 and A.13 detail the arrangements used for measuring the intermodulation immunity. Figure A.12 is related to an RSU with separate antenna connectors for receive and transmit path. Figure A.12: RSU receive parameter measurement arrangement for horizontally separated antennas In case the RSU under test provides only a single antenna connector for both, the transmit and receive path, a CC shall be used in order to split up the single antenna connector into two antenna connectors, one for the receive path and one for the transmit path; see figure A.13. Figure A.13: RSU receive parameter measurement arrangement with CC for horizontally separated antennas 1) The RTxA shall be mounted on a vertical pole within the "quiet zone" of the shielded anechoic chamber. The distance between any part of the RTxA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). Far-field region & free-space condition RTxA RRxA d Mcentre boresight α boresight α boresight ddisplace OBU AT1 FCCA FCCA AT2 RSU Rx RSU Tx RSU Combiner FCCA FCCA MSS1 MSS2 Far-field region & free-space condition RTxA RRxA d Mcentre boresight α boresight α boresight ddisplace OBU AT1 FCCA FCCA AT2 Combiner FCCA FCCA MSS1 MSS2 CC RSU Tx & Rx ETSI ETSI TS 104 022 V1.1.1 (2024-06) 40 2) The RRxA shall be mounted on a vertical pole within the "quiet zone" of the shielded anechoic chamber. The distance between any part of the RRxA and the ceiling, floor or walls shall be at least 0,5 m (see also clause A.6.3.2). 3) The phase centre of the RTxA shall be displaced from the phase centre of the RRxA by ddisplace. The position between both phase centres is denoted Mcentre. 4) The displacement shall either be horizontally or vertically such as to minimize the coupling between these antennas. The distance ddisplace shall be such that the coupling loss between the two antennas exceeds 30 dB. The actual coupling loss and the distance ddisplace shall be stated in the test report together with the unique identification of the RTxA and RRxA used. 5) The OBU shall be mounted on a vertical pole at the other end of the shielded anechoic chamber, such that its bore sight points towards Mcentre. 6) The height of the phase centres above floor of the RTxA, RRxA and the OBU antenna shall be equal. 7) Bore sight of the RTxA shall point towards the phase centre of the OBU antenna. 8) Bore sight of the RRxA shall point towards the phase centre of the OBU antenna. 9) The OBU antenna(s) shall be mutually in the far field of RTxA and RRxA, see clause A.6.3.1. 10) Connect the RSU transmitter to the RTxA via an adjustable attenuator AT1 and an FCCA. 11) Connect the RRxA to the RSU receiver via a combiner with four terminals, an isolator, an adjustable attenuator AT2 with attenuation ATNAT2 and an FCCA. 12) Connect a MSS1 via a FCCA to one of the remaining terminals of the combiner. 13) Connect a MSS2 via a FCCA to the remaining terminal of the combiner. A.7 Instruments A.7.1 Receiving device The RD shall be either a spectrum analyser or a measurement receiver. The subsequent requirements shall apply for a spectrum analyser: 1) The level of the superposition of all RF signals simultaneously fed to the input of the spectrum analyser shall be within its range of specification applying for its calibrated operational mode of operation. 2) The RD shall be operated only within modes for which the instrument has been calibrated. 3) For any frequency to be measured, the noise floor of the RD shall be at least 10 dB below any power value intended to be measured. 4) The DC voltage fed to the input of the spectrum analyser shall be within its range of specification applying for its calibrated operational mode of operation. 5) The frequency error of the spectrum analyser shall be compliant with table B.1. 6) The nominal characteristic impedance of the spectrum analyser's input connector shall match the nominal characteristic impedance of the device connected to this input connector. The VSWR shall be smaller than 2,0. If this cannot be met, an attenuator or an isolator featuring a VSWR smaller or equal to 2,0 within the frequency range of the measurement shall be attached to the input of the spectrum analyser and the EUT shall be connected to the input of this attenuator or isolator. 7) The Video BandWidth (VBW) shall always be equal to or larger than the Resolution BandWidth (RBW) selected. The RBW will also be referred to as the reference or equivalent bandwidth. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 41 8) Signal power measurements performed using the spectrum analyser's CW mode shall equal to the arithmetic average of the largest and smallest signal level measured during the observation time. 9) The spectrum analyser shall be used only after the instrument has warmed up. The minimum warm up duration is usually specified in the manual of the spectrum analyser. If this is not the case, a warmup time of at least half an hour shall be considered. 10) The spectrum analyser shall be calibrated before usage. 11) If the dynamic range of the spectrum analyser in conjunction with the required setting of the RBW is not sufficient to measure relevant weak signals in the presence of irrelevant strong signal components appropriate measures to suppress the irrelevant strong signal components shall be applied in agreement between provider and test laboratory and shall be described in the test report. 12) The rms detector shall be used. For the usage of a measurement receiver the above requirements shall apply as well with the exception, where requirements are not applicable, like the VBW. A.7.2 RF power sensor The subsequent requirements shall apply for RF signal power measurements. 1) RF signal power measurements shall not be performed before warmup of the RF power sensor and the RF power meter. The warmup duration is usually specified in the manual of the instrument. If this is not the case the instrument shall be allowed for a warmup time of at least half an hour. 2) The RF power sensor and RF power meter shall be calibrated and zeroed before usage according to the requirements and the procedure specified in the manual of the instrument. 3) The RF power sensor shall be kept within a small enough temperature range such as to keep the measurement uncertainty of the measurement set up within the range specified in clause B.2. 4) The VSWR at the input of the RF power sensor shall be less than 1,5 within the frequency range of the measurement under investigation. 5) The level of the superposition of all signals simultaneously fed to the input of the RF power sensor shall be within the dynamic range of the RF power sensor as stated by its provider for its operational mode. 6) The power sensor shall be dedicated for the signal waveform under consideration. A.7.3 Combiner All RF combiners used within the measurement arrangements and set ups shall provide coaxial connectors at all ports and feature within the frequency range they are used: • a nominal characteristic impedance of 50 Ω at each port; • a VSWR of less than 1,5 at each port; • an isolation between the input ports of at least 10 dB; and • an amplitude balance between each of the input ports and the output port of less than 1 dB. A.8 Power level of modulated RSU carrier Figure A.14 illustrates as an example the basic time-dependent sequence of unmodulated and modulated RSU transmit signals for a case of a modulation index m = 0,5, where the transmit signal power Pmod, and PCW, respectively, of the modulated, and unmodulated signal parts are equal. The condition of equal power levels Pmod = PCW is not required by the present document. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 42 NOTE: Figure A.14 does not allow extracting valid timing relations between carrier frequency and bit rate. RSU signal time RSU CW signal with power PCW Modulated RSU signal with power Pmod Modulation index m = 0,5 ACW PCW = Pmod Amod Amod + m Amod - m Figure A.14: RSU transmit signal An RSU normally allows for a transmit mode "send unmodulated carrier", i.e. continuous transmission of the unmodulated carrier. Thus it is possible to measure the power of the unmodulated signal in figure A.14, CW = CW , by means of a thermal power sensor or a spectrum analyser. An RSU does normally not allow for continuous transmission of the modulated carrier. Modern test equipment can do a gated power level measurement in time domain to overcome this problem. Following procedure allows to estimate the power = mod 1 + of the modulated carrier without doing gated power level measurements: 1) Set the RSU in a mode that it transmits an unmodulated carrier. Measure PCW. 2) Set the RSU in a mode that it transmits BSTs of maximum possible duration Tmod with a repetition period as close as possible to twice of the duration of a BST transmission. The gap between subsequent BST transmissions has duration TCW. The duration Tmod and TCW shall be constant within the following test. 3) Measure the average signal power level Pavg of the signal transmitted according to step 2 with a measurement duration of at least ten times the repetition period TCW + Tmod. 4) Measure the duration Tmod and TCW. 5) Calculate = + − . A.9 Bit error ratio measurements A.9.1 Basics The required BER for communication is referred to as parameters D9a and U9a in EN 12253 [1]. BER measurements shall be conducted either in a direct or indirect way. The direct way requires the possibility to generate and receive a continuous bit stream of significant length. The fraction of erroneous bits out of the total number of received bits is the BER. This approach uses standard laboratory equipment for BER measurement and requires a modification of the EUT. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 43 The indirect way is based on generating and receiving frames of limited length where any bit errors in the frame can be detected by means of a CRC. The fraction of erroneous frames out of the total number of frames, which is called the FER, allows to estimate the BER assuming that bit errors are equally distributed. Precautions shall be taken to prevent drops of error-free received frames caused by specific implementation of upper layers. A.9.2 BER measurement BER may be measured indirectly, see clause 9.3. A.9.3 FER measurement A.9.3.1 Mathematical expressions Assuming equally distributed and statistically independent occurrence of erroneous bits the following relations between FER, BER, and total number N of transmitted bit within a single frame apply: FER = 1 - (1 - BER)N, (A.9) = 1 −10 = 1 −√1 − . (A.10) The minimum number CF of frames together with the frame size shall be reported. EXAMPLE 1: With BER = 10-6 and frame length N = 1 000 the equivalent FER amounts to approximately 1,0 × 10-3. A reasonable number CF of frames to be transmitted is 10 000, i.e. 10 frames may be lost on average. EXAMPLE 2: For a large value of FER, e.g. 0,9999 which results from a BER = 9,2 × 10-3 and a frame length N = 1 000, a reasonable number CF of frames to be transmitted is 100 000, i.e. 10 frames may be error-free on average. The very large number of frames to be transmitted is necessary to estimate the BER, since a small variation in erroneous frames may cause a significant change of the corresponding estimated BER. A.9.3.2 Equipment FER measurements can be easily conducted using the set of test messages TM1 as specified in table A.1 in clause A.2. Thus, standard DSRC equipment might be used if the following software configuration has been implemented: • initialization with BST and VST is implemented; see EN 12795 [i.6] and EN 12834 [i.7]; • the EFC command ECHO is implemented; see ISO 14906 [i.4]. In case of a bit error performance measurement of the RSU receiver, the following additional configuration requirements apply: • An ECHO.request transmitted by the RSU and not responded by the OBU shall be treated as "never transmitted", as in this case the ECHO.request was received erroneous. • An erroneous ECHO.response received shall not result in a retransmission of the related ECHO.request as normally required by the DSRC protocol. It shall just lead to an increment of the frame error counter. In case of a bit error performance measurement of the OBU receiver, the following additional configuration requirements apply: • An ECHO.request transmitted by the RSU and not responded by the OBU shall not result in a retransmission of the related ECHO.request as normally required by the DSRC protocol. It shall just lead to an increment of the frame error counter. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 44 • An erroneous ECHO.response received shall not result in a retransmission of the related ECHO.request as normally required by the DSRC protocol, it shall just be ignored, as in this case the ECHO.request was received error free at the OBU. A.9.3.3 Procedure 1) The RSU shall perform initialization with the OBU by exchanging BST and VST. The signal level at the receiver input relevant for BER measurement shall be set to the level required for the test. The signal level at the other receiver input shall be set at a reasonable high value as declared by the provider such that error free reception is very likely. In the unexpected case of transmission errors, the initialization attempt shall be repeated. During initialization any additional interfering signals as requested by a specific test procedure shall be switched off. 2) The RSU shall transmit a single ECHO command of maximum length. Reception of the corresponding response from the OBU is expected to be error free. In case of errors, repetitions of the ECHO command according to the DSRC protocol shall happen. This finalizes initialization. In case of a bit error performance measurement of the RSU receiver, the following additional procedural steps shall be processed: 3) Repeat step 2 CF times, CF see clause A.9.3.1, and report the total number CE of erroneous ECHO.response frames received by the RSU. Calculate the actual Frame Error Ratio FER = CE / CF. Continue with step 5. In case of a bit error performance measurement of the OBU receiver, the following additional procedural steps shall be processed: 4) Repeat step 2 for CF times, CF see clause A.9.3.1, and report the total number CE of ECHO.response frames not received by the RSU. Calculate the actual Frame Error Ratio FER = CE / CF. 5) Calculate BER out of FER according to clause A.9.3.1. ETSI ETSI TS 104 022 V1.1.1 (2024-06) 45 Annex B (normative): Interpretation of results and measurement uncertainty B.1 Interpretation of results The interpretation of the results recorded in the test report for the measurements described in the present document shall be as follows: - the measured value related to the corresponding limit shall be used to decide whether an equipment meets the requirements of the present document; - the measurement uncertainty value for the measurement of each parameter shall be included in the test report. B.2 Measurement uncertainty Table B.1 shows the recommended values for the maximum measurement uncertainty figures. Table B.1: Maximum measurement uncertainty Parameter Uncertainty RF power (conducted) ±1,5 dB RF frequency, relative ±1 x 10-7 Radiated emission of transmitter, valid to 40 GHz ±6 dB Sensitivity ±3 dB Two and three signal measurements ±4 dB Two and three signal measurements using radiated fields ±6 dB Radiated emission of receiver, valid to 40 GHz ±6 dB Temperature ±1 K Relative humidity ±5 % ETSI ETSI TS 104 022 V1.1.1 (2024-06) 46 History Document history V1.1.1 June 2024 Publication |
562623eb2258223d90ec398702267f56 | 104 021-1 | 1 Scope | The present document describes the general guidance on Optical Distribution Network (ODN) quick construction and digitalization. The digitalized Quick ODN enables the carriers to improve the fibre deployment efficiency, achieve digital resource management, and consequently improve the operation and management efficiency. The present document describes the composition of the digitalized quick ODN and the general requirements on physical label, digitalized quick ODN devices, intelligent management terminal, intelligent optical path analysis equipment and intelligent management system. The present document is mainly based on intelligent optical distribution networks that can collect the ODN device information through intelligent optical path analysis equipment or intelligent management terminal (such as a smart phone with the ODN management application). It can also be used as a reference for other networks with optical fibre connections. For optical distribution networks that collect label information in other methods, it is possible to refer to the present document similarly. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 2 References | |
562623eb2258223d90ec398702267f56 | 104 021-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. Not applicable. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document, but they assist the user with regard to a particular subject area. Not applicable. ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 6 |
562623eb2258223d90ec398702267f56 | 104 021-1 | 3 Definition of terms, symbols and abbreviations | |
562623eb2258223d90ec398702267f56 | 104 021-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: Digitalized quick Optical Distribution Network (ODN): digitalized quick ODN is a methodology that uses physical labels or optical path labels to uniquely identify ODN passive devices to enable the implementation of intelligent management functions such as automatic storage of optical information, automatic identification of optical fibre connection, information calibration of optical fibre resources and visualized onsite operation guide NOTE: The network is constructed based on QuickConnect cables and terminals, the network connection can be done by plug-and-play operation on site. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 3.2 Symbols | Void. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CO Central Office EMS Element Management System FAT Fibre Access Terminal LC FDB Fibre Distribution Box GIS Geographic Information System ODN Optical Distribution Network OLT Optical Line Terminal ONT Optical Network Terminal ONU Optical Network Unit OSS Operation Support Systems PON Passive Optical Network QR Quick Response RH Relative Humidity RTT Round Trip Time SN Serial Number UV Ultraviolet |
562623eb2258223d90ec398702267f56 | 104 021-1 | 4 Composition of Digitalized Quick ODN | |
562623eb2258223d90ec398702267f56 | 104 021-1 | 4.1 General | During the entire lifecycle including planning, construction, acceptance, operation, and maintenance, by adopting new technologies such as digitalization and artificial intelligence, digitalized Quick ODN can build an intelligent ODN management mechanism to implement highly automatic and self-calibrated resource management and fast service provisioning on passive ODN networks, improving operation and maintenance efficiency and quality. DQ ODN mainly has digital and quick features. Through digitally encoding technology, digitalization can make ODN network data flow paperless, resource changes can be automatically collected, and optical path status can be visualized. Quick means rapid network construction and high reliability of the ODN network. In the construction phase, the Digitalized Quick ODN shall be able to enrol ODN resources to the system through digitalized information technologies such as scanning codes, and bind GIS information and addresses of resources. In the project acceptance phase, the digitalized Quick ODN shall be able to remotely inspect ODN optical paths, identify optical path quality and optical path length, and assist home broadband services, new community ODN lines in quick network access, capacity expansion, etc. ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 7 In the operation phase, the digitalized Quick ODN shall be able to automatically construct the optical link topology, identify the occupation status of key optical path resources, and assist in resource utilization planning and management; besides, it shall be able to automatically establish the association between logical optical paths and service devices. The digitalized Quick ODN shall support routine inspection, fault demarcation and locating. In routine inspection mode, the system shall automatically and periodically inspect each optical paths. The inspect item should include the optical power and generates an alarm if it exceeds the threshold. The system shall be able to identify and accurately locate potential optical path faults, such as continuous optical attenuation, abnormal optical path attenuation, and optical passing length, and provide warnings in advance. When the user triggers the start, the system supports the user to start temporary fault locating. The system shall be able to identify whether the user complaint is caused by the optical path in minutes, whether the fault is group fault or individual fault, and accurately locate the fault. After the optical path fault is rectified, the quality of the optical path shall be accepted. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 4.2 Position in the Access Network | As figure 4-1 shows, the Digitalized Quick ODN system connects the OLT and ONU through the digital ODN hardware, connects to the carrier's Operation Support System (OSS) upwards (including the resource management system and fault management system), and collects optical path information from the ODN network downwards, restores the optical path topology, and demarcates and locates faults. Figure 4-1: Composition Reference Model |
562623eb2258223d90ec398702267f56 | 104 021-1 | 4.3 Composition Reference Model | The Digitalized Quick ODN system consists of Physical label, Digitalized Quick ODN devices, Intelligent optical path analysis equipment, Intelligent management terminal and Intelligent management system. They can interconnect with a third-party Operations Support System (OSS). Figure 4-2 shows the composition reference model, with description of each part in clause 4.4 and interface definitions in clause 4.5. Digitalized Quick ODN system EMS OLT ONU 1 ONU n OSS ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 8 Figure 4-2: Composition Reference Model |
562623eb2258223d90ec398702267f56 | 104 021-1 | 4.4 Functional Entity | |
562623eb2258223d90ec398702267f56 | 104 021-1 | 4.4.1 Physical label | Labels used to identify Digitalized Quick ODN devices features, such as QR codes and RFID, generally used on the surface of optical splitters, patch cords, pigtails, or terminals (including closures, FAT, FDB, etc.). 4.4.2 Digitalized Quick ODN devices ODN devices with digital functions, including optical splitter, optical fibre, cables, closures and so on. The digital functions include optical path labels on optical splitter which modulates the optical path information, and physical labels on optical cables, connectors, terminals, etc. Digital Quick ODN devices provide digital capabilities in passive mode. 4.4.3 Intelligent optical path analysis equipment Equipment which can read and analyse ODN resource data and optical path quality data, and report to the Intelligent management system on demand. 4.4.4 Intelligent management terminal As a portable device with an ODN management software application, like a smart phone, tablet computer, it provides a management operation interface to identify intelligent ODN devices and manage onsite operations. It communicates with the intelligent management system through the I4 interface and communicates with the OSS through the I6 interface. The intelligent management terminal provides the following functions: a) Scan physical labels on ODN devices and obtain related information (including the device type, device specification, production date, GIS, etc.). OSS Intelligent management t Intelligent management l Digitalized Quick ODN device 1 Physical label Intelligent optical path analysis Digitalized Quick ODN device 2 Physical label Digitalized Quick ODN device n Physical label …… I I2 I2 I 2 I3 I4 I5 I6 I I1 ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 9 b) Scan the physical labels of the cables and terminals to identify the status of the ports (Occupied or idle) and the connection relationship between cables and terminal ports. 4.4.5 Intelligent management system The intelligent management system mainly implements the function of managing the digitalized quick ODN devices through the intelligent optical path analysis equipment or intelligent management terminal, communicates with intelligent optical path analysis equipment through the I3 interface, and communicates with the intelligent management terminal through the I4 interface, and communicates with the OSS through the I5 interface. The intelligent management system provides the following functions: a) Visualized optical network topology (including device connection relationship and port connection status). b) ODN optical path quality inspection capability and inspection report. c) ODN optical path fault diagnosis capability located in PON ports. d) Manages on digitalized quick ODN devices, and stores, inputs, and outputs correspondent information. e) Receives, processes, and forwards work orders. f) Manages alarm information and reports it to the OSS. 4.5 Interface 4.5.1 I1 interface The I1 interface is located between the intelligent optical path analysis equipment and the digitalized quick ODN devices. The intelligent optical path analysis equipment reads the optical path information of the PON network (including the OLT and ONU) and the Digitalized Quick ODN devices through the I1 interface. 4.5.2 I2 interface The I2 interface is located between the physical label and the intelligent management terminal. The Intelligent management terminal reads the information on the physical label through the I2 interface. The I2 interface provides the following functions: a) Scan physical labels on ODN devices and obtain related information (including the device type, device specification, production date, GIS, etc.). b) Scan the physical labels of the cables and terminals, and to identify the status of the terminal ports (occupied or idle) and connection relationship between cables and terminal ports. 4.5.3 I3 interface The I3 interface is located between the intelligent optical path analysis equipment and the intelligent management system. The intelligent management system collects optical path information from the intelligent optical path analysis device through the I3 interface, including ONU receive/transmit optical power, ONU RTT information, and optical path information of the ODN network. 4.5.4 I4 interface The I4 interface is located between the intelligent management system and the intelligent management terminal. The intelligent management system communicates with the intelligent management terminal through the I4 interface. The interactive information on the I4 interface includes the device type, device specifications, production date, GIS, etc. ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 10 4.5.6 I5 interface The I5 interface is the northbound interface of the intelligent management system. It is located between the intelligent management system and the OSS. The interaction information on the I5 interface includes ODN topology data and ODN optical path fault data. 4.5.7 I6 interface (optional) The I6 interface is located between the intelligent management terminal and the OSS. The interaction information on the I6 interface includes: a) Order information received by the intelligent management terminal from the OSS. b) The order processing result sent from intelligent management terminal to the OSS. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 5 General requirements on physical label | The general requirements of physical label are as following: a) The number information carried by the physical label shall be unique. b) The information carried by the physical label shall be readable. c) The physical label shall be firmly attached to the associated devices, such as fibre connectors, cables or terminals. d) The label shall meet the same environmental performance requirements as the product, such as the change of temperature, water immersion, resistance to chemical solvents and other environmental tests, and there shall be no digital reading function failure after the above tests. e) The label shall meet certain mechanical performance requirements, such as wear resistance, alcohol wiping resistance, and there shall be no digital reading function failure after the above tests. f) Physical labels (such as QR code labels) in outdoor scenarios should meet the test requirements of long-term UV, high temperature and high humidity, and anti-mold aging, and there shall be no digital reading function failure after the above tests. 6 General requirements on Digitalized Quick ODN devices |
562623eb2258223d90ec398702267f56 | 104 021-1 | 6.1 Structure | Traditional ODN links, ODN system without Digital function, can use either a one-stage or a two-stage equal-ratio optical networking structure. Two-stage equal-ratio optical network is recommended for scenarios with high user density, while unequal-ratio optical networking structure is recommended for scenarios with low user density. This clause focuses on the key feature requirements of components related to unequal-ratio QuickConnect network. Figure 6-1 illustrates that digitalized quick ODN devices are mainly including the QuickConnect Hubbox, QuickConnect Subbox, QuickConnect Endbox, QuickConnect distribution cable, QuickConnect drop cable, and adaptor. Similar to the FDT in the traditional ODN network, the Hubbox is the transfer point between the feeder end and the distribution section in the ODN network, which realizes the conversion between the multi-core and the single-core distribution cable. The Subbox and the Endbox are used in the distribution and drop sections, which are similar to the second-stage box in the traditional ODN network. Their functions are similar, but the difference is as follows: the subbox has a built-in optical splitter with unequal ratio, which provides the functions of connecting users and cascading. The endbox has a built-in optical splitter with equal ratio, which is used at the end of the network and can only connect users without cascading. Both Subbox and Endbox are fully sealed. ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 11 Similar to the traditional ODN network, the distribution cable is used in the distribution section, but can be directly plugged into the terminal box with both ends pre-connected with hardened connectors. The drop cable is used in the home section to connect the access point and the user ONU. Figure 6-1: Schematic diagram of a structure of digitalized quick ODN devices 6.2 Requirements on components 6.2.1 Hubbox Figure 6-2 illustrates the schematic diagram of a structure of QuickConnect Hubbox. The general requirements of QuickConnect Hubbox are the following: a) Should support the access of multi-core optical cables or the access of QuickConnect cables. The output end is the QuickConnect distribution optical cable, which can be single-core or multi-core. b) Should support splitting function. c) Shall support readable physical labels on the surface of the boxes, which should be identified through the image recognition technology in order to get connection relationship between the cables and the box ports. d) Shall support the optical path information collection function, and work with intelligent optical path analysis equipment and intelligent management system to realize the topology restoration of the network and the monitoring of the network status. e) Shall meet the requirements of waterproof level IPx5 (overhead scenarios) or IPx8 (underground scenarios). f) Shall test long-term reliability for 1 000 h under the condition of 75 °C, 95 % RH. After the above tests, there shall be no damage affecting the function, products shall meet the requirements of optical and waterproof performance, as well as impact level IK08 (overhead scenarios) or IK09 (underground scenarios). ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 12 Figure 6-2: Schematic diagram of a structure of Hubbox 6.2.2 Subbox Figure 6-3 illustrates the schematic diagram of a structure of QuickConnect Subbox. The general requirements of QuickConnect Subbox are the following: a) The adapter ports shall be on the surface of the box body, and the QuickConnect cables can be plugged and unplugged without opening the box. b) There shall be readable physical labels on the surface of the boxes, which should be identified through the image recognition technology in order to get connection relationship between the cables and the box ports. c) Shall support the optical path information collection function, and work with intelligent optical path analysis equipment and intelligent management system to realize the topology restoration of the network and the monitoring of the network status. d) Shall meet the requirements of waterproof level IPx5 (overhead scenarios) or IPx8 (underground scenarios). e) Shall test long-term reliability for 1 000 h under the condition of 75 °C, 95 % RH. After the above tests, there shall be no damage affecting the function, products shall meet the requirements of optical and waterproof performance, as well as impact level IK08 (overhead scenarios) or IK09 (underground scenarios). Figure 6-3: Schematic diagram of a structure of Subbox 6.2.3 Endbox Figure 6-4 illustrates the schematic diagram of a structure of QuickConnect Endbox. The general requirements of the QuickConnected Endbox are the following: a) The adapter ports shall be on the surface of the box body, and the QuickConnect cables can be plugged and unplugged without opening the box. b) There shall be readable physical labels on the surface of the boxes, which should be identified through the image recognition technology in order to get connection relationship between the cables and the box ports. ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 13 c) Shall support the optical path information collection function, and work with intelligent optical path analysis equipment and intelligent management system to realize the topology restoration of the network and the monitoring of the network status. d) Shall meet the requirements of waterproof level IPx5 (overhead scenarios) or IPx8 (underground scenarios). e) Shall test long-term reliability for 1 000 h under the condition of 75 °C, 95 % RH. After the above tests, there shall be no damage affecting the function, products shall meet the requirements of optical and waterproof performance, as well as impact level IK08 (overhead scenarios) or IK09 (underground scenarios). Figure 6-4: Schematic diagram of a structure of Endbox 6.2.4 QuickConnect distribution cables Figure 6-5 illustrates the schematic diagram of a structure of QuickConnect distribution cables. The general requirements of QuickConnect distribution cables are the following: a) The connector shall be hardened connectors, which meets the requirements of waterproof level IPx5 (overhead scenarios) or IPx8 (underground scenarios). b) The connector shall attach physical labels and support digital identification. The physical label codes on connectors at both ends shall be the same. c) Shall support the optical path information collection function, and work with intelligent optical path analysis equipment and intelligent management system to realize the topology restoration of the network and the monitoring of the network status. d) The attenuation average value of random mated single-core hardened connectors shall be no more than 0,08 dB. e) The tensile force of the hardened connectors shall be no less than 800 N to ensure high reliability during installation. f) Shall test long-term reliability for 1 000 h under the condition of 75 °C, 95 % RH. After the above tests, there shall be no damage affecting the function, products shall meet the requirements of optical and waterproof performance. ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 14 Figure 6-5: Schematic diagram of a structure of QuickConnect distribution cables 6.2.5 QuickConnect drop cables The general requirements of QuickConnect drop cables are the following: a) The connector shall be Hardened connectors, which meets the requirements of waterproof level IPx5 (overhead scenarios) or IPx8 (underground scenarios). b) The connector shall attach physical labels and support digital identification. The physical label codes on connectors at both ends shall be the same. c) Should support the optical path information collection function, and work with intelligent optical path analysis equipment and intelligent management system to realize the topology restoration of the network and the monitoring of the network status. d) The tensile force of the hardened connectors shall be no less than 300 N. e) Shall test long-term reliability for 1 000 h under the condition of 75 °C, 95 % RH. After the above tests, there shall be no damage affecting the function, products shall meet the requirements of optical and waterproof performance. 6.2.6 Adaptor Figure 6-6 illustrates the schematic diagram of a structure of Adaptors. Adaptors are usually constructed with plug- socket type, with one end connected to the terminal and the other end connected to the QuickConnect drop cables. The general requirements of adaptors are the following: a) Shall meet the requirements of waterproof level IPx5 (overhead scenarios) or IPx8 (underground scenarios). b) Should attach physical labels and support digital identification. c) Should support the optical path information collection function, and work with intelligent optical path analysis equipment and intelligent management system to realize the topology restoration of the network and the monitoring of the network status. Figure 6-6: Schematic diagram of a structure of adaptors ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 15 7 General requirements on intelligent management terminal The intelligent management terminal shall provide digital and visualized ODN resource management capabilities through the entire lifecycle of ODN construction, installation, and maintenance. The general requirements of the intelligent management terminal are the following: a) Automatic identification and recording of intelligent ODN devices information and port information by scanning digital labels. b) Download, import, export, query, delete, and feedback work order processing results. c) Provision of visualized onsite operation guide services through the management interface. d) Communication with the intelligent management system. e) Communication with the OSS (Optional). 8 General requirements on intelligent optical path analysis equipment The general requirements of the intelligent optical path analysis equipment are the following: a) Collects optical path information (such as scattering) of the backbone and branch in the ODN network as required. b) Measures the end-to-end insertion loss of fibre links. c) Demarcates and locates faults. d) Continuously provides functions such as intelligent digital ODN topology restoration, fibre quality acceptance, and fault diagnosis. 9 General requirements on intelligent management system 9.1 General Intelligent management system is located in the network management centre. It can realize visual resource management, optical path quality monitoring, fault diagnosis and provide northbound interface to OSS. |
562623eb2258223d90ec398702267f56 | 104 021-1 | 9.2 Topology restoration for passive optical network | The Digitalized Quick ODN shall provide topology restoration function. A topology restoration achieves ODN dumb resources inventory management and improve resource report accuracy. It supports planning and design of new ODN network construction or stock expansion and construction acceptance. To realize logical topology restoration through optical path labels, the general requirements of intelligent management system are the following: a) Shall support identification of first-stage optical splitter and its ports status which includes connect to second- stage splitter, connect to ONU, vacant and connect to cable (the other end of cable is not connected). ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 16 NOTE: Connect to second-stage splitter and connect to ONU can be called 'occupied', and vacant and connect to cable can be combined together as 'idle'. b) Shall support identification of second-stage optical splitter and ONT group information. Shall be able to show the distance from OLT to second-stage splitter and the information of connected ONT including product ID, SN, LODI. To realize physical topology restoration through physical labels, the general requirements of intelligent management system are the following: a) Should support checking ODN resource location and connection relationship based on GIS information. b) Overall resource status and proportion shall be displayed and queried. c) Location stage of ODN devices shall be visualized. d) ODN device port status (idle or occupied) and information including coordinate and name shall be visualized. Interface definition of optical splitter resource and the connection relationship on ODN network are described in table 9-1. Table 9-1: Interface definition of optical splitter resource and the connection relationship on ODN network Field example Null or not Required / Optional Description deviceSN N Required ODN device SN code deviceName N Required ODN device name deviceAddress N Required ODN device address information deviceFloor Y Optional ODN device floor information deviceGis N Required ODN device GIS information deviceImages Y Optional ODN device image information devicePorts N Required ODN device port information deviceStatus Y Optional ODN device acceptance status deviceIP Y Optional ODN device Internet Protocol(IP) information portNumber N Required ODN device port identifier portCable Y Optional ODN device port cable code portOntSn Y Optional ODN device port connected ONT code |
562623eb2258223d90ec398702267f56 | 104 021-1 | 9.3 Quality monitoring of passive optical network | The digitalized quick ODN shall provide ODN network quality monitoring function, support self-defined periodic automatic ODN network quality diagnosis, actively initiate optical network optimization and fault diagnosis. To realize above functions, the general requirements of intelligent management system are the following: a) Shall support quality control of feeder optical network, including fibre break, high insertion loss. b) Should support quality control of distribution optical network, including fibre break, high insertion loss. c) Should support quality control of home connection optical network, including fibre break, high insertion loss. Visualized interface definition of the optical network is described in table 9-2. Table 9-2: Visualized interface definition of the optical network Field example Null or not Required/Optional Description Name N Optional Node name (corresponding to the optical splitter resource interface model) or connection name (corresponding to the ODN connection interface model) Type N Optional Connection relationship/Splitter Attenuation N Optional Attenuation of the network ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 17 |
562623eb2258223d90ec398702267f56 | 104 021-1 | 9.4 Fault diagnosis of passive optical network | The Digitalized Quick ODN shall provide ODN network fault diagnosis function, supports initiating fault diagnosis of specific PON port network in case of sudden ODN network fault, guides fast demarcation, fast search for optical network fault location and fast repair, so as to provide high-quality network services. To realize above functions, the general requirements of intelligent management system are the following: a) Shall support Fault diagnosis of feeder optical network. Shall provide diagnostic results such as the distance between the nodes before and after the failure location, the attenuation of the abnormal point, suggestions. b) Should support Fault diagnosis of distribution optical network. Should provide diagnostic results such as fibre break, the distance between the nodes before and after the failure location, suggestions. c) Should support Fault diagnosis of home connection optical network. Should provide diagnostic results such as fibre break, the distance between the nodes before and after the failure location, suggestions. Interface definition of the fault diagnosis function is described in table 9-3. Table 9-3: Interface definition of the fault diagnosis function Field example Null or not Required / Optional Description OLT N Required IP of OLT that the fault belongs to PONPorts N Required Port of OLT that the fault belongs to DiagResult N Required Diagnostic result SugMeasure N Required Suggest measurement WeakONT N Required ONT that the fault occurs FailLoc N Required failure location DistFailtoCO(m) N Required Distance from failure location to CO room(m) DistFailtoFirst(m) N Required Distance between failure location to first-stage splitter(m) AttenuFail(dB) N Required Attenuation in failure location (dB) NbeforeFail N Required Node before the failure location DistFailtoNbefore(m) N Required The distance from failure location to the Node before the failure location (m) NafterFail N Required Node after the failure location DistFailtoNafter(m) N Required The distance from failure location to the Node after the failure location (m) ETSI ETSI TS 104 021-1 V1.1.1 (2025-02) 18 History Document history V1.1.1 February 2025 Publication |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 1 Scope | The present document specifies each algorithm in the suite of authentication and key management algorithms TAA2, each designed to meet the requirements set out in the requirements specification [i.1]. |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 2 References | |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 100 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 7: Security". |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] TCCE(22)000038 / TCCE06(22)000018: "Requirements Specification for additions to the TETRA Authentication and Key Management Algorithm Suite, Revision 2". [i.2] Daemen, J. and Rijmen, V. (1999): "AES proposal: Rijndael", document version 2. Submission to NIST AES competition (1999). [i.3] Black, J., Rogaway, P. and Shrimpton, T. (2002): "Black-Box Analysis of the Block-Cipher-Based Hash-Function Constructions from PGV", in Yung, M. (ed.) Advances in Cryptology - CRYPTO 2002. Berlin, Heidelberg: Springer Berlin Heidelberg (Lecture Notes in Computer Science), pp. 320-335. doi:10.1007/3-540-45708-9-21. |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 3 Definition of terms, symbols and abbreviations | |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 3.1 Terms | For the purposes of the present document, the following terms apply: Cipher Key (CK): value used to determine the transformation of plain text to cipher text in a cryptographic algorithm ETSI ETSI TS 104 053-4 V1.1.1 (2024-07) 7 Encryption Cipher Key (ECK): cipher key used as input to the encryption algorithm where an air interface encryption algorithm from TEA set A is in use Extended Cipher Key (CKX): value used to determine the transformation of plain text to cipher text in a cryptographic algorithm where an air interface encryption algorithm from TEA set B is in use Initialization Value (IV): sequence of symbols that randomize the KSG inside the encryption unit |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 3.2 Symbols | Void. |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CCK-id CCK identifier CCKX eXtended Common Cipher Key CK Cipher Key CKX eXtended Cipher Key DCK Derived Cipher Key NOTE: DCK1 and DCK2 are components of the Derived Cipher Key. DCKX eXtended Derived Cipher Key ECK Encryption Cipher Key GCK Group Cipher Key GCKN Group Cipher Key Number GCK-VN GCK-Version Number GCKX Extended Group Cipher Key GSKO Group Session Key for OTAR GSKO-VN GSKO-Version Number GSKOX Extended Group Session Key for OTAR IV Initialization Value K2 authentication Key KS, KS' Session authentication Key KSG Key Stream Generator KSO Session Key for OTAR KSOX eXtended Session Key for OTAR MF Manipulation Flag MGCKX eXtended Modified Group Cipher Key MNI Mobile Network Identity RAND1 RANDom challenge 1 RAND2 RANDom challenge 2 RES RESponse RS Random Seed RSO Random Seed for OTAR SCCKX Sealed Extended Common Cipher Key SCK Static Cipher Key SCKN Static Cipher Key Number SCK-VN SCK-Version Number SCKX eXtended Static Cipher Key SGCKX Sealed Extended Group Cipher Key SGSKOX Sealed Extended Group Session Key for OTAR SSCK Sealed Static Cipher Key SSCKX Sealed Extended Static Cipher Key TAA1 TETRA Authentication Algorithm set 1 TAA2 TETRA Authentication Algorithm set 2 TEA TETRA Encryption Algorithm NOTE: Used with specific numeric algorithm identity e.g. TEA5. ETSI ETSI TS 104 053-4 V1.1.1 (2024-07) 8 XOR eXclusive OR |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 4 Introduction | |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 4.0 General | The set of algorithms TAA2 described in the present document are the associated algorithms used for providing TETRA air interface authentication and key management as specified in detail by ETSI TS 100-392-7 [1]. The present document is organized as follows. Notations and definitions for TAA2 are covered in clauses 4.1 and 5 provides the specification of all TAA2 algorithms. |
64d160e6d9835511d1369c3f13f7f6cb | 104 053-4 | 4.1 Notation and Definitions | The inputs and outputs of the TAA2 algorithms are always sequences of bits. A Boolean value is represented by single bit, with 0 denoting False and 1 denoting True. The notation A || B has been used to denote concatenation of two sequences of bits A and B, meaning a sequence of bits consisting of the bits of sequence A followed by those of the sequence B. Many algorithm definitions involve interpreting a sequence of bits, of length 8n for some n, as a sequence of bytes of length n, and vice versa. In this correspondence the first bit appears as the most significant bit of the first byte, the second bit as the second most significant bit of the first byte, …, and the last bit as the least significant bit of the last byte. More precisely, a bit sequence B[1], …, B[8n] corresponds to the byte sequence b[1], …, b[n], where b[i] = 27B[8i-7] + 26B[8i-6] + … + B[8i] for i = 1, …, n When the length of a sequence of bits is not a multiple of 8, it is represented by the sequence of bytes corresponding to the sequence of bits padded with the smallest number of 0s required to make its length a multiple of 8. C(i) is used to denote the sequence of 8 bits corresponding to the single byte with integer value i, using the correspondence just defined: so, for example, C(5) is the 8-bit sequence 0, 0, 0, 0, 0, 1, 0, 1. The argument i is written in decimal. For any m in the set {128, 192, 256} and n in the set {128, 192, 224, 256}, the notation Rijndael(Km, Bn) is used to denote the variant of Rijndael [i.2] with m-bit key and n-bit block size. Rijndael with block size n = 224 is defined in section 12.1 of [i.2]. In [i.2], the Rijndael plaintext block, ciphertext block and key are all expressed as arrays of bytes. In this specification, Rijndael plaintext blocks, ciphertext blocks and keys are referred to as arrays of bits. The correspondence mentioned above applies here, interpreting sequences of bits as sequences of bytes and vice versa. For any two sequences A and B of bits of the same length, A ⊕ B is defined as the bit sequence whose bit in any position is the XOR of the bits from A and B in the corresponding position. This also defines an operation a ⊕ b on byte sequences, via our identification of a byte sequence with a corresponding bit sequence. The notation Z(n) denotes a sequence of n bits, each with value 0. For some algorithms a function H(M, n) is used to produce an n-bit sequence which is the hash of an m-bit message M, for m ≥ 1 and n ≥ 256. H is calculated as follows: Write M || Z = M1 || … || Mr, where r = ⎡m/256⅂, the smallest integer ≥ the floating-point quotient m / 256; Z is the sequence of 256r-m bits, each 0; and M1, …, Mr are each 256 bits long. (In our applications, r will be either 1 or 2. In each particular application, the length of M will be fixed.) 1) Set X to be the sequence of 256 bits, each 0. 2) For i := 1 to r do: a) Let C be the result of encrypting the block X under Rijndael (K256, B256) with key Mi. ETSI ETSI TS 104 053-4 V1.1.1 (2024-07) 9 b) Set X := C ⊕ X. 3) Return the first n bits of X as the function result. Note that this is construction f5 from [i.3], also widely referred to as the Davies-Meyer scheme. The function H(M,n) is illustrated in figure 1. Figure 1: The Function H(M,n) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.