1 module o-ran-uplane-conf {
3 namespace "urn:o-ran:uplane-conf:1.0";
4 prefix "o-ran-uplane-conf";
6 import o-ran-processing-element {
10 import ietf-interfaces {
14 import o-ran-module-cap {
18 import o-ran-compression-factors {
22 import o-ran-wg4-features {
26 import ietf-hardware {
30 import o-ran-hardware {
34 import o-ran-usermgmt {
38 organization "O-RAN Alliance";
44 "This module defines the module capabilities for
45 the O-RAN Radio Unit U-Plane configuration.
47 Copyright 2021 the O-RAN Alliance.
49 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS'
50 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
51 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
52 ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
53 LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
54 CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
55 SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
56 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
57 CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
58 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
59 POSSIBILITY OF SUCH DAMAGE.
61 Redistribution and use in source and binary forms, with or without
62 modification, are permitted provided that the following conditions are met:
64 * Redistributions of source code must retain the above copyright notice,
65 this list of conditions and the above disclaimer.
66 * Redistributions in binary form must reproduce the above copyright notice,
67 this list of conditions and the above disclaimer in the documentation
68 and/or other materials provided with the distribution.
69 * Neither the Members of the O-RAN Alliance nor the names of its
70 contributors may be used to endorse or promote products derived from
71 this software without specific prior written permission.";
73 revision "2022-12-05" {
77 1) PRB range limit for SE 12 and HP section
78 2) Introduction of PRB ranges
79 3) uplane-only-dl-mode-enable
80 4) Deprecation of power-related capabilities and addition of min-gain
81 5) se 23 max mplane limits
82 6) support Section Type 4 and associated commands";
84 reference "ORAN-WG4.M.0-v11.00";
87 revision "2022-08-15" {
91 1) clarified description statements for representative-t/rx-eaxc-id
92 2) clarified description statements for max-num-t/rx-eaxc-ids-per-group
93 4) clarified description statements for component carrier
94 5) style guide corrections
95 6) introduction of O-RU connector functionality
97 8) introducing new feature for ACK NACK feedback
98 9) added SHARED-ORU-MULTI-OPERATOR anf SHARED-ORU-MULTI-ODU features";
100 reference "ORAN-WG4.M.0-v10.00";
103 revision "2022-04-18" {
107 1) Descriptions fixed for max-beam-updates-per-slot / max-beam-updates-per-slot
108 2) Added references to CUS-Plane spec for parameters 'frame-structure' and
109 'supported-frame-structures'
110 3) clarified max-beams-per-symbol, max-beams-per-slot, max-beam-updates-per-slot,
111 max-beam-updates-per-symbol parameters
112 4) Clarification of cp-length and cp-length-other
113 5) deprecation of rw-type and rw-duplex-scheme";
115 reference "ORAN-WG4.M.0-v09.00";
118 revision "2021-12-01" {
122 1) Various descriptions corrected and/or clarified
123 2) Configuration for Beamforming weights were added together with changes and updates to compressions
124 3) Added new leaf node 'beam-update-contention-control-limits-required' to 'endpoint-types'
125 to indicate endpoint capability to support beam update contention control processing limits.
126 4) Added instance of 'beam-update-contention-control-limits' to 'endpoint-types'.
127 5) Added new leaf node boolean flag 'beam-update-contention-control-enabled' for O-DU to indicate
128 support of feature BEAM-UPDATE-CONTENTION-CONTROL feature.
129 6) deprecate 'channel-information-iq-bitwidth' , and define a new parameter
130 'channel-information-bitwidth' under the container 'compression'
131 7) add capability and configuration for channel information PRB granularity.
132 8) Add support for multiple transport-session-type per O-RU.
133 9) add capability and configuration for channel information compression.
134 10) deprecate 'channel-information-iq-bitwidth' , and define a new parameter
135 'channel-information-bitwidth' under the container 'compression'";
137 reference "ORAN-WG4.M.0-v08.00";
140 revision "2021-07-26" {
144 1) Added new grouping 'per-cplane-message-limits' containing params to limit
145 per C-Plane packet processing when CPLANE-MESSAGE-PROCESSING-LIMITS feature is
146 supported by O-RU and used by O-DU.
147 2) Added new leaf node 'cplane-message-processing-limits-required' to 'endpoint-types'
148 to indicate endpoint capability to support C-Plane message processing limits.
149 3) Added instances of 'per-cplane-message-limits' to 'endpoint-types' and
150 'endpoint-capacity-sharing-groups'.
151 4) Added new leaf node to low-level-tx/rx-endpoint 'cplane-message-processing-limits-enabled'
152 for O-DU to configure support for C-Plane limits
153 5) Added t-da-offset and t-au-offset for external antenna support
154 6) Added Channel IQ bitwidth for ST6
155 7) Added ordered-by user to leaf-list member-tx-eaxc-id and leaf-list member-rx-eaxc-id
156 8) Added new PRACH formats
157 9) Ensuring beam-ids can only be 15 bits
158 10) Clarify mixed numerology restrictions";
160 reference "ORAN-WG4.M.0-v07.00";
164 revision "2021-03-22" {
168 1) typographical corrections in descriptions.
169 2) Updates to transmission window control.
170 3) Introduces to existing grouping 'endpoint-section-capacity' two new leaf nodes 'max-uplane-section-header-per-symbol' and
171 'max-uplane-section-header-per-slot' to limit U-Plane data section header addition/parsing.
172 4) deprecated parameter 'max-remasks-per-section-id' since it is duplicate of leaf node 'max-control-sections-per-data-section'.
173 5) introduces new leaf nodes 'max-beams-updates-per-slot' and ''max-beams-updates-per-symbol'
174 to grouping 'endpoint-beam-capacity'
175 6) added new SRS features:
176 STATIC-TRANSMISSION-WINDOW-CONTROL
177 DYNAMIC-TRANSMISSION-WINDOW-CONTROL
178 UNIFORMLY-DISTRIBUTED-TRANSMISSION
180 INDEPENDENT-TRANSMISSION-WINDOW-CONTROL";
182 reference "ORAN-WG4.M.0-v06.00";
185 revision "2020-12-10" {
189 1) introduces new coupling method coupling-via-frequency-and-time-with-priorities-optimized
190 2) introduces new max-highest-priority-sections-per-slot parameter";
192 reference "ORAN-WG4.M.0-v05.00";
195 revision "2020-08-10" {
199 1) parameters allowing for static PRACH configuration introduced
200 2) parameters allowing for static SRS configuration introduced
201 3) parameters allowing for configuration of TDD pattern introduced
202 4) Backward compatible change to introduce new parameter 'coupling-method' related
203 to Section Description Priority to serve for CUS-Plane CR";
205 reference "ORAN-WG4.M.0-v04.00";
208 revision "2020-04-17" {
212 1) Adding optional little endian support
213 2) Adding a new capability parameter to indicate that the O-RU
214 supports regularizationFactor in section type 5
215 3) Added support for Dynamic Spectrum Sharing feature
216 4) Clarify the supported number of reMasks in RU side
217 5) Section extension for grouping multiple ports
218 6) adding PRACH formats to endpoint capabilities";
220 reference "ORAN-WG4.M.0-v03.00";
223 revision "2019-07-03" {
227 1) added new leaf multiple-numerology-supported to enable O-RU to report
228 whether it supports multiple numerologies.
230 2) fixing broken constraints (configuration cannot be dependent on
231 operational state). This is a backwards incompatible revision.
233 As these constraints only apply when the LAA feature is used, and also
234 when considering the limited number of implementation that need to be
235 taken into consideration for backwards compatibility, it has been
236 agreed to NOT increment the namespace integer.
238 3) added frequency related capabilities for tx-arrays and rx-array
240 4) removed redundant LAA import";
242 reference "ORAN-WG4.M.0-v01.00";
245 revision "2019-02-04" {
249 1) imported model from xRAN
250 2) changed namespace and reference from xran to o-ran";
252 reference "ORAN-WG4.M.0-v01.00";
255 feature EAXC-GAIN-CORRECTION {
257 "Presence of feature indicates that O-RU supports eAxC specific gain correction.";
260 feature TX-REFERENCE-LEVEL {
262 "Presence of feature indicates that O-RU supports TX gain reference level control";
265 typedef prach-preamble-format {
269 "LTE PRACH Preamble format 0";
273 "LTE PRACH Preamble format 1";
277 "LTE PRACH Preamble format 2";
281 "LTE PRACH Preamble format 3";
285 "LTE PRACH Preamble format 4";
289 "LTE Narrowband PRACH format 0";
293 "LTE Narrowband PRACH format 1";
297 "5GNR PRACH Preamble format 0";
301 "5GNR PRACH Preamble format 1";
305 "5GNR PRACH Preamble format 2";
309 "5GNR PRACH Preamble format 3";
313 "5GNR PRACH Preamble format A1";
317 "5GNR PRACH Preamble format A2";
321 "5GNR PRACH Preamble format A3";
325 "5GNR PRACH Preamble format B1";
329 "5GNR PRACH Preamble format B2";
333 "5GNR PRACH Preamble format B3";
337 "5GNR PRACH Preamble format B4";
341 "5GNR PRACH Preamble format C0";
345 "5GNR PRACH Preamble format C2";
349 "LTE Narrowband PRACH format 0-a";
353 "LTE Narrowband PRACH format 1-a";
357 "LTE Narrowband PRACH format 2";
362 "PRACH preamble format definition";
365 typedef polarisation_type {
368 description "MINUS_45";
374 description "PLUS_45";
377 description "PLUS_90";
380 description "Type definition for polarisations";
383 grouping transmission-buffering-capacity {
385 "UL U-plane buffering capacity available for scheduled transmission of UL U-plane messages";
387 list transmission-buffering-capacity {
389 "Buffering capacity for specific IQ format.
390 If the list does not contain an entry for particular IQ format than endpoint
391 or group of endpoints then buffering capacity for this IQ format is
392 max-buffered-prbs = 0 and max-buffered-symbols = 0.";
394 uses cf:compression-details;
396 leaf max-buffered-prbs {
399 "Max number of PRBs (for IQ format given in compression-details) that can be buffered by an endpoint
400 or buffered collectively by group of endpoints sharing capacity. This is divided between symbols buffered";
403 leaf max-buffered-symbols {
406 "Max number of symbols (for IQ format given in compression-details) that can be buffered by an endpoint
407 or buffered collectively by group of endpoints sharing capacity";
412 grouping general-config {
413 description "a group for general configuration";
415 container general-config {
416 description "a container for general configuration";
418 leaf regularization-factor-se-configured {
422 "Informs if regularization factor in section extension is configured(true) or not(false), this
423 leaf indicates whether the O-DU will send the regularization factor in section extension.
425 If the O-RU does not support regularization-factor-se-supported in o-ran-module-cap.yang,
426 this leaf is ignored.";
429 leaf little-endian-byte-order {
434 "If little endian byte order for C/U plane data flows is supported by
435 the O-RU, indicates if the O-RU should use little endian byte order
436 for all UL and DL C/U plane data flows.
438 If little endian byte order is NOT supported, this node is ignored
439 (and the default bigendian byte order used)";
442 leaf uplane-only-dl-mode-enable {
443 if-feature feat:UPLANE-ONLY-DL-MODE;
447 "If set to true, enable IQ data transfer without C-Plane in DL for all
448 endpoints as specified in the CUS specification clause 8.2.2.";
451 leaf st4-for-time-domain-beamforming-weights-enabled {
452 if-feature feat:ST4-SLOT-CONFIG-MSG-SUPPORT;
456 "If O-RU indicates support for Section Type 4 command 'TIME_DOMAIN_BEAM_CONFIG' , O-DU may
457 configure the O-RU to use Section Type 4 TIME_DOMAIN_BEAM_CONFIG command by setting this
458 flag to 'true'. In which case, O-DU shall use only Section Type 4 TIME_DOMAIN_BEAM_CONFIG
459 for specifying time-domain beam information. refer to clause 12.4.3.4.4 of CUS-Plane spec.";
464 grouping laa-carrier-config {
465 description "Carrier Configuration for support of LAA. ";
466 leaf ed-threshold-pdsch {
470 "This value indicates Energy Detection(ED) threshold for LBT for PDSCH and for measurements in dBm.";
473 leaf ed-threshold-drs {
477 "This value indicates Energy Detection(ED) threshold for LBT for DRS in dBm.";
480 leaf tx-antenna-ports {
483 "This value indicates Tx antenna ports for DRS (1, 2, 4)";
486 leaf transmission-power-for-drs {
490 "This value indicates offset of Cell specific reference Signal(CRS) power to reference signal power (dB).
491 DRS signal consists of CRS, PSS, SSS, and optionally CSI-RS.";
504 enum ONE-HUNDRED-SIXTY {
511 "This value indicates DRS measurement timing configuration (DMTC) period in ms";
518 "This value indicates dmtc offset in Subframes.";
525 "This value indicates LBT Timer in milliseconds.";
528 list max-cw-usage-counter {
529 when "/mcap:module-capability/mcap:rw-sub-band-info/mcap:rw-self-configure = 'true'";
535 description "priority 1";
538 description "priority 2";
541 description "priority 3";
544 description "priority 4";
547 description "This value provides the priority class traffic for which the counter is calculated.";
554 description "This value indicates the maximum value of counter
555 which shows how many max congestion window value is used for backoff
556 number of priority class traffic. This value is defined at 3GPP 36.213
557 section 15.1.3 as K.";
562 grouping coupling-methods {
564 "Grouping for configuration of desired C-Plane / U-Plane coupling methods (if supported)";
567 path "/mcap:module-capability/mcap:ru-capabilities/mcap:coupling-methods/mcap:coupling-via-frequency-and-time";
568 require-instance false;
572 "RW instance of RO parameter.";
574 leaf coupling-method {
575 when "../coupling-to = 'true'";
578 description "Coupling via sectionId value. This value can be used always.";
580 enum FREQUENCY_AND_TIME {
581 description "Coupling via frequency and time. Can be used when coupling-via-frequency-and-time = true
582 or coupling-via-frequency-and-time-with-priorities = true in o-ran-module-cap.yang";
584 enum FREQUENCY_AND_TIME_WITH_PRIORITIES {
585 description "Coupling via frequency and time with priorities. Can be used when
586 coupling-via-frequency-and-time-with-priorities = true in o-ran-module-cap.yang";
588 enum FREQUENCY_AND_TIME_WITH_PRIORITIES_OPTIMIZED {
589 description "Coupling via frequency and time with priorities optimized. Can be used when
590 coupling-via-frequency-and-time-with-priorities-optimized = true in o-ran-module-cap.yang";
595 "Method of coupling between C-Plane and U-Plane messages; see methods of coupling
596 of C-Plane and U-Plane in CUS-Plane specification. If an O-RU doesn't support the
597 necessary capability as defined in o-ran-module-cap.yang, the O-RU shall respond
598 with rpc-error including an error-message describing the error condition";
604 "One eAxC identifier (eAxC ID) comprises a band and sector
605 identifier (BandSector_ID), a component-carrier identifier (CC_ID) and a
606 spatial stream identifier (RU_Port_ID).
608 In this version of the specification, one eAxC contains only one spatial
609 stream (i.e. one beam per subcarrier) at a time.
611 Bit allocation is subdivided as follows:
612 * O_DU_Port_ID: Used to differentiate processing units at O-DU
613 * BandSector_ID: Aggregated cell identifier
614 * CC_ID: distinguishes Component Carriers
615 * RU_Port_ID: Used to differentiate spatial streams or beams on the O-RU
617 The bitwidth of each of the above fields is variable this model is supposed to check
618 if we are occupying bits continuously, but we do not have to occupy all 16 bits";
621 leaf o-du-port-bitmask {
625 "mask for eaxc-id bits used to encode O-DU Port ID";
628 leaf band-sector-bitmask {
632 "mask for eaxc-id bits used to encode the band sector ID";
639 "mask for eaxc-id bits used to encode the component carrier id";
642 leaf ru-port-bitmask {
646 "mask for eaxc-id bits used to encode the O-RU Port ID";
653 "encoded value of eaxcid to be read by CU-Plane";
657 grouping parameters {
659 "Grouping of all parameters common between UL and DL";
664 description "Unique name of array antenna";
667 leaf number-of-rows {
670 description "Number of rows array elements are shaped into - M";
673 leaf number-of-columns {
676 description "Number of columns array elements are shaped into - N";
679 leaf number-of-array-layers {
682 description "Number of array layers array elements are shaped into - Q";
685 leaf horizontal-spacing {
691 description "Average distance between centres of nearby AE in horizontal direction (in array coordinates system)";
694 leaf vertical-spacing{
700 description "Average distance between centres of nearby AE in vertical direction (in array coordinates system)";
703 container normal-vector-direction {
705 "Counter-clockwise rotation around z and y axis.";
713 description "Azimuth angle, counter-clockwise rotation around z-axis. Value 'zero' points to broad-side, value '90' points to y-axis";
721 description "Zenith angle, counter-clockwise rotation around y-axis. Value 'zero' points to zenith, value '90' points to horizon";
725 container leftmost-bottom-array-element-position {
726 description "Structure describing position of leftmost, bottom array element.";
733 description "X dimension of position of leftmost, bottom array element";
742 description "Y dimension of position of leftmost, bottom array element";
751 description "Z dimension of position of leftmost, bottom array element";
760 "List of supported polarisations.";
766 "Polarisation index. See CUS-plane";
770 type polarisation_type;
772 description "Type of polarisation supported by array.";
777 path "/mcap:module-capability/mcap:band-capabilities/mcap:band-number";
781 "This parameter informing which frequency band particular antenna
782 array is serving for.
783 Intended use is to deal with multiband solutions.";
786 list related-o-ru-connectors {
791 path '/hw:hardware/hw:component/hw:name';
793 must "derived-from-or-self(deref(current())/../hw:class, 'or-hw:O-RU-ANTENNA-CONNECTOR')";
795 "Referenced name of O-RU connector used by the antenna array.";
797 leaf-list array-element-id {
800 "Identifiers of array element(s) related to specific O-RU connector. Allowed values and semantic - as per CUS-Plane spec, clause 'Identification and Ordering of Array Elements'";
803 "List of unique names that identify instances of O-RU's connectors the external [tr]x-array is reachable through.";
807 grouping array-choice {
808 choice antenna-type {
812 path "/o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:tx-arrays/o-ran-uplane-conf:name";
816 "Leafref to tx array if such is chosen";
822 path "/o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:rx-arrays/o-ran-uplane-conf:name";
826 "Leafref to rx array if such is chosen";
830 "Choice for antenna type";
833 "Elements which groups choice for antenna type";
836 grouping scs-config {
838 "It groups all parameters related to SCS configuration";
840 leaf frame-structure {
844 "This parameter provides value of frame structure. For semantics and allowed values see CUS-Plane Specification, clause 'frameStructure (frame structure)'";
851 "Normal cyclic prefix";
856 "Extended cyclic prefix";
861 "Provides type of CP (cyclic prefix) if section type 3 is not used or type of CP cannot be determined from cpLength.";
869 "Provides length of CP used for the first symbol after subframe boundary or half-subframe boundary.
872 If a section type 3 is used in C-plane messages addressed to the endpoint, then O-RU takes length of CP from
873 C-Plane cpLength Information Element and the value of this leaf shall be ignored by the O-RU. See cpLength (cyclic prefix length)
874 in CUS-Plane for details.
876 If a static configuration (see static-prach-configurations) is applicable to the endpoint, then O-RU takes
877 length of CP from M-Plane cp-length leaf in static-prach-configurations and the value of this leaf shall be ignored by the O-RU.";
880 leaf cp-length-other {
885 "Provides length of CP used for symbols other than provided by cp-length.
887 If a section type 3 is used in C-plane messages addressed to the endpoint, then O-RU takes length of CP from
888 C-Plane cpLength Information Element and the value of this leaf shall be ignored by the O-RU. See cpLength (cyclic prefix length)
889 in CUS-Plane for details.
891 If a static configuration (see static-prach-configurations) is applicable to the endpoint, then O-RU takes
892 length of CP from M-Plane cp-length leaf in static-prach-configurations and the value of this leaf shall be ignored by the O-RU.";
895 leaf offset-to-absolute-frequency-center {
899 "This provides value of freqOffset to be used if section type 3 is not used. See freqOffset in CUS-plane.
900 offset-to-absolute-frequency-center defines the relative spacing between the centre of RE#0 of RB#0 to the center-of-channel-bandwidth.
901 If offset-to-absolute-frequency-center for NR with SCS=15kHz is odd,
902 it implies that 7.5kHz shift as indicated by the 3GPP parameter frequencyShift7p5khz for UL is applied,
903 which means enable the NR UL transmission with a 7.5 kHz shift to the LTE raster, as defined in 3GPP TS 38.331.
904 When type (in tx/rx-array-carrier) is DSS, 'offset-to-absolute-frequency-center' indicates the 1st RE of 1st RB of NR.";
907 list number-of-prb-per-scs {
910 "List of configured for each SCS that will be used.";
913 type mcap:scs-config-type;
915 "Value corresponds to SCS values defined for frameStructure in C-plane.
916 Note: set of allowed values is restricted by SCS derived from values in supported-frame-structures.";
923 "Determines max number of PRBs that will be used in all sections per one symbol.
924 This is affecting allocation of resources to endpoint. Value shall not exceed constrains
925 defined by max-prb-per-symbol of endpoint type. In addition, sum (over all used endpoints
926 within a group of endpoints sharing resources) of number-of-prb rounded up to the
927 nearest value from prb-capacity-allocation-granularity shall not exceed max-prb-per-symbol of the group.";
932 grouping tx-common-array-carrier-elements {
934 "This grouping contains all common parameters for tx-array-carriers and rx-array-carriers";
936 leaf absolute-frequency-center {
940 "deprecated in version 5.0.0 and replaced with offset-to-absolute-frequency-center
941 and common FREF translated from absolute-frequency-center (NREF) as defined in 38.104";
944 leaf center-of-channel-bandwidth {
949 "Centre frequency of channel bandwidth in Hz. Common for all numerologies.
950 center-of-channel-bandwidth is the FREF translated from absolute-frequency-center (NREF) as per 3GPP TS 38.104.
951 Refer to Table 5: Centre Bandwidth Calculation in M-plane spec for calculation of this parameter
952 for even and odd number of PRBs in LTE, NR and DSS carrier configuration.";
955 leaf channel-bandwidth {
961 "Width of carrier given in Hertz";
968 "carrier does not provide signal - transmission is disabled";
972 "carrier is fully configured and was active but is energy saving mode";
976 "carrier is fully configured and properly providing the signal";
982 "Indicates if transmission is enabled for this array carriers. Note that NETCONF server uses state parameter
983 to indicate actual state of array carriers operation. When array carriers is in sleep status,
984 NETCONF server rejects all other operation request to tx-array-carriers object except either request to change from sleep
985 to active status or delete MO operation (see 4.8) to the object.";
992 "array carrier is not active - transmission of signal is disabled.";
996 "array carrier is processing an operation requested by change of active parameter.
997 When array carriers is BUSY the transmission of signal is not guaranteed.";
1001 "array carrier had completed activation operation - is active and transmission of signal is ongoing.";
1007 "Indicates state of array carriers activation operation";
1021 if-feature mcap:DSS_LTE_NR;
1023 "NR and LTE technologies in Dynamic Spectrum Sharing mode";
1027 "Type of carrier. Indicates array-carrier technology.";
1030 leaf duplex-scheme {
1044 "Type of duplex scheme O-RU supports.";
1046 leaf rw-duplex-scheme {
1048 path "/user-plane-configuration/tx-array-carriers[name=current()/../name]" + "/duplex-scheme";
1049 require-instance false;
1053 "Config true type of duplex scheme.
1054 Status is deprecated because 'lte-tdd-frame' container, where it was used, is also deprecated.
1055 Additionally duplex-scheme is derived from the band-number.";
1059 path "/user-plane-configuration/tx-array-carriers[name=current()/../name]" + "/type";
1060 require-instance false;
1064 "Config true type of carrier.
1065 Status is deprecated because leafref is to a 'config true' schema-node";
1069 grouping rx-common-array-carrier-elements {
1071 "This grouping contains all common parameters for tx-array-carriers and rx-array-carriers";
1073 leaf absolute-frequency-center {
1077 "deprecated in version 5.0.0 and replaced with offset-to-absolute-frequency-center
1078 and common FREF translated from absolute-frequency-center (NREF) as defined in 38.104";
1081 leaf center-of-channel-bandwidth {
1086 "Centre frequency of channel bandwidth in Hz. Common for all numerologies.
1087 center-of-channel-bandwidth is the FREF translated from absolute-frequency-center (NREF) as per 3GPP TS 38.104.
1088 Refer to Table 5: Centre Bandwidth Calculation in M-plane spec for calculation of this parameter
1089 for even and odd number of PRBs in LTE, NR and DSS carrier configuration.";
1092 leaf channel-bandwidth {
1098 "Width of carrier given in Hertz";
1105 "carrier does not provide signal - transmission is disabled";
1109 "carrier is fully configured and was active but is energy saving mode";
1113 "carrier is fully configured and properly providing the signal";
1119 "Indicates if transmission is enabled for this array carriers. Note that NETCONF server uses state parameter
1120 to indicate actual state of array carriers operation. When array carriers is in sleep status,
1121 NETCONF server rejects all other operation request to tx-array-carriers object except either request to change from sleep
1122 to active status or delete MO operation (see 4.8) to the object.";
1129 "array carrier is not active - transmission of signal is disabled.";
1133 "array carrier is processing an operation requested by change of active parameter.
1134 When array carriers is BUSY the transmission of signal is not guaranteed.";
1138 "array carrier had completed activation operation - is active and transmission of signal is ongoing.";
1144 "Indicates state of array carriers activation operation";
1158 if-feature mcap:DSS_LTE_NR;
1160 "NR and LTE technologies in Dynamic Spectrum Sharing mode";
1164 "Type of carrier. Indicates array-carrier technology.";
1167 leaf duplex-scheme {
1181 "Type of duplex scheme O-RU supports.";
1185 grouping endpoint-section-capacity {
1186 leaf max-control-sections-per-data-section {
1191 "Max number of C-plane sections (C-plane section is part of C-plane message that carries 'section fields')
1192 referring to same U-plane section (U-plane section is part of U-plane message that carries
1193 'section header fields' and 'PRB fields') that is supported by endpoint.
1194 Note that additional limitations specific for each section type apply on top of this number.";
1196 leaf max-sections-per-symbol {
1199 "Max number of sections within one symbol that can be processed by endpoint
1200 or processed collectively by group of endpoints sharing capacity";
1202 leaf max-sections-per-slot {
1205 "Max number of sections within one slot that can be processed by endpoint
1206 or processed collectively by group of endpoints sharing capacity.";
1208 leaf max-highest-priority-sections-per-slot {
1210 must "current() < ../max-sections-per-slot" {
1211 error-message "the sectionID for the highest priority needs to be less than the max sectionIds per slot";
1214 "Max number of highest priority sections within one slot that can be processed by endpoint or processed collectively by
1215 group of endpoints sharing capacity. This leaf applies only when coupling-via-frequency-and-time-with-priorities-optimized
1216 is true, in other instances this leaf is ignored by the O-RU. The sectionId for highest priority section descriptions shall
1217 start from 0 to specified max value and is a subset of max-sections-per-slot and must be less than max-sections-per-slot.";
1220 leaf max-remasks-per-section-id {
1227 "maximum number of different reMask values that is applied to a PRB
1228 within one section id. This value can be processed by endpoint
1229 or processed collectively by group of endpoints sharing capacity.
1230 This parameter is duplicated max-control-sections-per-data-section, hence being deprecated.";
1232 leaf max-uplane-section-header-per-symbol {
1235 "Maximum number of U-Plane data section header within one symbol that can be processed by an endpoint or processed collectively by group of
1236 endpoints sharing capacity. Clarification for multiple U-Plane data section headers per C-Plane section description is specified in sectionId IE
1237 description in CUS-Plane specification. For the cases where this optional parameter is not populated by O-RU or an older version O-DU does not
1238 interpret this parameter, O-DU may optionally use max-sections-per-symbol as the default value to limit of U-Plane data section messages which
1239 can be processed by the O-RU. If none of the above limitations are supported, O-RU and O-DU may rely on offline negotiation.
1240 As an example, this parameter can be used to limit O-RU processing while using Section extension type#6 and #12, which are used for non-contiguous
1241 PRB allocation, and hence results in multiple U-Plane data section headers for a given C-Plane section description.";
1243 leaf max-uplane-section-header-per-slot {
1246 "Maximum number of U-Plane data section headers within one slot that can be processed by an endpoint or processed collectively by group of
1247 endpoints sharing capacity. Clarification for multiple U-Plane data section headers per C-Plane section description is specified in sectionId IE
1248 description in CUS-Plane specification. For the cases where this optional parameter is not populated by O-RU or an older version O-DU does not
1249 interpret this parameter, O-DU may optionally use max-sections-per-slot as the default value to limit of U-Plane data section messages which can
1250 be processed by the O-RU. If none of the above limitations are supported, O-RU and O-DU may rely on offline negotiation.
1251 As an example, this parameter can be used to limit O-RU processing while using Section extension type#6 and #12, which are used for non-contiguous
1252 PRB allocation, and hence results in multiple U-Plane data section headers for a given C-Plane section description.";
1256 "Parameters describing section capacity where section is understood as number of different sectionId values. Additionally, max limits for U-Plane data sections
1257 refer to U-Plane data section headers";
1260 grouping endpoint-section-extension-limits {
1261 leaf max-mcscaleremask-per-prb {
1264 "This parameter limits the number of sets of {mcScaleReMask, csf, mcScaleOffset} values per symPrbPattern the O-RU can support when SE 23 is used in a
1265 data section description. Refer to clause 7.7.23.1 of the CUS-Plane specification.";
1267 leaf max-prb-ranges-per-sec-ext-12 {
1270 "Optional parameter reported by O-RU which applies to Section Extension 12 and specifies
1271 the maximum number of frequency ranges R per section description supported by O-RU.
1272 If this limit is exceeded by the O-DU, the O-RU is responsible for sending alarm notification
1273 with 'fault-id = 31' to subscribers following the procedures defined in Clause 11 and
1274 Table A.1-1 of O-RAN.WG4.MP.0.
1275 As an example, the O-RU can include the following in the corresponding active-alarm list
1276 entry and alarm-notification message:
1277 <fault-text>Error C-Plane message</fault-text>
1278 <probable-cause>Maximum number of frequency ranges in SE-12 per section description exceeded</probable-cause>
1279 <proposed-repair-actions>Reduce frequency ranges per section description used in SE-12</proposed-repair-actions>";
1281 leaf max-freq-hops-per-sec-ext-13 {
1284 "Optional parameter reported by O-RU which applies to Section Extension 13 and specifies
1285 the maximum number of frequency hops R per section description supported by O-RU.
1286 If this limit is exceeded by the O-DU, the O-RU is responsible for sending alarm notification
1287 with 'fault-id = 31' to subscribers following the procedures defined in Clause 11 and
1288 Table A.1-1 of O-RAN.WG4.MP.0.
1289 As an example, the O-RU can include the following in the corresponding active-alarm list
1290 entry and alarm-notification message:
1291 <fault-text>Error C-Plane message</fault-text>
1292 <probable-cause>Maximum number of frequency hops in SE 13 per section description exceeded</probable-cause>
1293 <proposed-repair-actions>Reduce frequency hops per section description used in SE-13</proposed-repair-actions>";
1297 "Parameters describing C-Plane section extension limits/capacities.";
1300 grouping endpoint-beam-capacity {
1301 leaf max-beams-per-symbol {
1303 range "min .. 32767";
1306 "Max number of beams within one symbol that can be processed by endpoint
1307 or processed collectively by group of endpoints sharing capacity
1309 If the parameter is absent or if value 0 is reported for the parameter,
1310 then the endpoint does not support beamforming operation.";
1312 leaf max-beams-per-slot {
1314 range "min .. 32767";
1317 "Max number of beams within one slot that can be processed by endpoint
1318 or processed collectively by group of endpoints sharing capacity
1320 If the parameter is absent or if value 0 is reported for the parameter,
1321 then the endpoint does not support beamforming operation.";
1323 leaf max-beam-updates-per-slot {
1325 range "min .. 32767";
1328 "Max number of beams within one slot that can be updated by endpoint
1329 or processed collectively by group of endpoints sharing capacity
1331 If the parameter is absent or if value 0 is reported for the parameter,
1332 then the endpoint does not support beamforming operation.";
1334 leaf max-beam-updates-per-symbol {
1336 range "min .. 32767";
1339 "Max number of beams within one symbol that can be updated by endpoint
1340 or processed collectively by group of endpoints sharing capacity
1342 If the parameter is absent or if value 0 is reported for the parameter,
1343 then the endpoint does not support beamforming operation.";
1347 "Parameters describing beam capacity where number of beams is understood as number of different beamId values.
1348 Parameters defined for beam updates shall be used to put a maximum limit on number of beam/beamIds which can be updated
1349 every slot/symbol. Note: This parameter does not put any restriction on which beams/beamIds can be updated.
1351 If the parameters defining beam capacity and beam updates are absent or if value 0 is reported for the parameters
1352 defining beam capacity and beam updates, then the endpoint does not support beamforming operation.";
1355 grouping endpoint-prb-capacity {
1356 leaf max-prb-per-symbol {
1359 "Max number of prbs within one symbol that can be processed by endpoint
1360 or processed collectively by group of endpoints sharing capacity";
1363 leaf max-prb-ranges-per-symbol {
1366 "Optional parameter reported by O-RU which indicates the maximum number of PRB ranges
1367 that can be processed by single endpoint or processed collectively by group of endpoints
1368 sharing capacity within one symbol. For details please see O-RAN WG4 CUS-Plane specification,
1369 Clause 7.8.2.1.2 'Limits of number of PRB ranges'.
1371 In case CU-Plane traffic generated by the O-DU exceeds the limit, an O-RU is responsible
1372 for sending alarm notification with 'fault-id = 31' to subscribers following the procedures
1373 defined in Clause 11 and Table A.1-1 of O-RAN.WG4.MP.0.
1375 As an example, the O-RU can include the following in the corresponding active-alarm list
1376 entry and alarm-notif message:
1377 <fault-text>Error C-Plane message</fault-text>
1378 <probable-cause>max-prb-ranges-per-symbol exceeded</probable-cause>
1379 <proposed-repair-actions>Reduce value of number of PRB ranges used per symbol</proposed-repair-actions>";
1383 "Attributes presenting processing capacity related to PRB.";
1386 grouping endpoint-numerology-capacity {
1387 leaf max-numerologies-per-symbol {
1390 "Max number of numerologies within one symbol that can be processed by endpoint
1391 or processed collectively by group of endpoints sharing capacity";
1395 "Attributes presenting processing capacity related to numerology.
1397 This leaf contains valid data only when multiple-numerology-supported
1401 grouping per-cplane-message-limits {
1402 leaf max-beams-per-cplane-message {
1405 "Maximum number of beams which can be recieved in one single C-Plane message. Number of beams,
1406 may include only beamIds, only beam weights or mix of beamIds and beamweights being received by
1407 an O-RU in a single C-Plane message.
1408 To avoid application layer fragmentation of C-Plane message across the fronthaul, O-RU should
1409 avoid setting this to a very low value.
1410 As a usage scenario, an O-RU may choose to define only a few quantized values e.g. (128, 256).
1411 If the value is set to 0 by O-RU, the O-DU need not restrict the number of beams it can send
1412 in single C-Plane message (except limited by MTU size).";
1415 leaf max-highest-priority-sec-per-cplane-message {
1418 "Maximum number of highest priority sections which can be received in one single C-Plane message.
1419 This leaf applies only when 'coupling-via-frequency-and-time-with-priorities' is true";
1422 leaf max-beams-per-slot-with-cplane-limits {
1425 "Maximum number of beams that are required to be processed by endpoint or processed collectively
1426 by group of endpoints sharing capacity when O-DU enables C-Plane limits. This value should replace
1427 'max-beams-per-slot' defined in 'endpoint-beam-capacity'";
1430 leaf max-highest-priority-sections-per-slot-with-cplane-limits {
1433 "Maximum number of highest priority sections that are required to be processed by endpoint or processed
1434 collectively by group of endpoints sharing capacity when O-DU supports C-Plane limits. This value should
1435 replace 'max-highest-priority-sections-per-slot' defined in 'endpoint-section-capacity'";
1438 leaf max-num-se22-per-cplane-message {
1441 "This value limits the max number of section extension 22 (ACK/NACK request) included in a C-Plane message as supported
1442 by the endpoint or collectively by group of endpoints sharing capacity when O-DU enables C-Plane limits
1443 and when section extension 22 (ACK/NACK request) and section type 8 (ACK/NACK feedback) are supported by the endpoint or endpoint sharing group.";
1446 leaf max-prb-ranges-per-hp-section-sec-ext-12 {
1449 "Optional parameter reported by O-RU which applies to Section Extension 12 and specifies the
1450 maximum number of frequency ranges R per highest priority section description supported by O-RU.
1451 If this limit is exceeded by the O-DU, the O-RU is responsible for sending alarm notification
1452 with 'fault-id = 31' to subscribers following the procedures defined in Clause 11 and
1453 Table A.1-1 of O-RAN.WG4.MP.0.
1454 As an example, the O-RU can include the following in the corresponding active-alarm list
1455 entry and alarm-notification message:
1456 <fault-text>Error C-Plane message</fault-text>
1457 <probable-cause>Maximum number of frequency hops per highest priority section description exceeded</probable-cause>
1458 <proposed-repair-actions>Reduce frequency range per highest section description</proposed-repair-actions>";
1462 "Attributes limit maximum instances of certian parameters contained in a C-Plane mesaage e.g. beams,
1463 highest priority sections. This limitation is useful for O-RUs which are packet processing based and are
1464 dimensioned to handle fixed number of parameters contained in a C-Plane message. In addition, if O-DU supports
1465 cplane limits, O-RU can operate more efficiently and endpoint capacity for applicable parameters are enhanced.
1466 as specified by 'max-beams-per-slot-with-cplane-limits' and 'max-highest-priority-sections-per-slot-with-cplane-limits'";
1469 grouping beam-update-contention-control-limits {
1470 leaf max-beams-per-symbol-with-beam-contention-control {
1473 "Maximum number of beams within one symbol that can be processed by an endpoint or processed collectively
1474 by group of endpoints sharing capacity when O-DU enables the O-RU feature BEAM-UPDATE-CONTENTION-CONTROL.
1475 This value should replace 'max-beams-per-symbol' defined in 'endpoint-beam-capacity'";
1478 leaf max-beams-updates-per-symbol-with-beam-contention-control {
1481 "Maximum number of beams within one symbol that can be updated by an endpoint or processed collectively
1482 by group of endpoints sharing capacity when O-DU enables the O-RU feature BEAM-UPDATE-CONTENTION-CONTROL.
1483 This value should replace 'max-beam-updates-per-symbol' defined in 'endpoint-beam-capacity'";
1487 "If O-DU supports BEAM-UPDATE-CONTENTION-CONTROL, O-RU can operate more efficiently and endpoint capacity for applicable
1488 parameters are enhanced.";
1491 grouping endpoint-static-config-support {
1492 leaf static-config-supported {
1496 "The endpoint does not support static PRACH / SRS configuration.
1497 Reception of PRACH / SRS is possible through real time C-Plane messages
1498 if other endpoint capabilities allow for that.";
1501 if-feature mcap:PRACH-STATIC-CONFIGURATION-SUPPORTED;
1503 "The endpoint supports statically configured PRACH reception";
1506 if-feature mcap:SRS-STATIC-CONFIGURATION-SUPPORTED;
1508 "The endpoint supports statically configured SRS reception";
1514 "The parameter informs if endpoint can be statically configured to process PRACH or SRS reception";
1517 leaf max-prach-patterns {
1518 when "(/user-plane-configuration/static-low-level-rx-endpoints[name=current()/../name]/static-config-supported = 'PRACH')";
1521 "Maximum number of PRACH patterns the endpoint can handle in PRACH configuration";
1524 leaf max-srs-patterns {
1525 when "(/user-plane-configuration/static-low-level-rx-endpoints[name=current()/../name]/static-config-supported = 'SRS')";
1528 "Maximum number of SRS patterns the endpoint can handle in SRS configuration";
1532 "Endpoint's capabilities related to static PRACH / SRS configuration.";
1535 grouping endpoint-tdd-pattern-support {
1536 leaf configurable-tdd-pattern-supported {
1537 if-feature mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED;
1542 "The parameter informs if endpoint supports configuration for TDD pattern";
1548 "Parameter is used to group static-low-level-[tr]x-endpoints.
1549 Note: [tr]x-array-carriers using static-low-level-[tr]x-endpoints
1550 having the same value of tdd-group, must have the same TDD switching
1551 points and the same directions to the air interface granted - regardless TDD switching
1552 is controlled by M-Plane or by C-Plane";
1556 "This grouping exposes static-low-level-[tr]x-endpoint's capabilities related to its support for configurable
1557 TDD patterns and limitations regarding common TDD switching per groups of endpoints.";
1560 grouping u-plane-transmission-control {
1562 "Configuration for UL U-plane transmission control";
1564 leaf transmission-window-control {
1565 if-feature "feat:STATIC-TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL";
1569 "O-RU will use normal transmission type with normal transmission window";
1572 if-feature feat:STATIC-TRANSMISSION-WINDOW-CONTROL;
1574 "O-RU will use transmission window offset and size and transmission type as configured over M-plane";
1577 if-feature feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL;
1579 "O-RU will use transmission window offset and size and transmission type as requested over C-plane";
1585 "Selects type of UL U-plane transmission window control for the endpoint";
1588 leaf transmission-window-schedule {
1589 when "(../transmission-window-control = 'STATIC')";
1590 if-feature feat:STATIC-TRANSMISSION-WINDOW-CONTROL;
1594 path "/user-plane-configuration/transmission-window-schedules/id";
1598 "Identifies U-plane transmission window schedule (which provides a list of symbol-specific offsets)
1599 to be used by the endpoint.
1600 Symbol-specific offset values from the schedule are added to endpoint specific offset value
1601 from transmission-window-offset.
1602 If this element is not present, the O-RU assumes as all symbol specific offsets are zero.
1603 For restrictions on values of symbol-specific offsets see description of transmission-window-offset.
1604 This parameter shall not be set to value other than empty if transmission control is not enabled
1605 by transmission-window-control.";
1608 leaf transmission-window-offset {
1609 when "(../transmission-window-control = 'STATIC')";
1610 if-feature feat:STATIC-TRANSMISSION-WINDOW-CONTROL;
1612 units "number of symbols";
1615 "Transmission window offset.
1616 The effective symbol-specific offset is sum of endpoint-specific offset value from transmission-window-offset
1617 and symbol-specific offset from transmission-window-schedules referenced by transmission-window-schedule.
1619 If this element is not present then O-RU assumes transmission-window-offset is zero.
1620 This parameter shall not be set to value other than 0 if transmission control is not enabled
1621 by transmission-window-control.
1623 There is no direct upper bound for this parameter (except value range defined by leaf type) but there are
1624 restrictions on combination of values of transmission-window-offset, transmission-window-offset,
1625 symbol-specific offset from transmission-window-schedules and transmission-window-size.
1627 Specifically, if endpoint is set for delay managed operation (non-time-managed-delay-enabled = FALSE)
1628 then O-RU handles U-Plane transmission as delay managed traffic and combination of values of
1629 transmission-window-offset, symbol-specific offset from transmission-window-schedules and
1630 transmission-window-size must not exceed O-RU buffering capacity (transmission-buffering-capacity)
1631 for the requested reception schedule.
1633 If endpoint is set for non-delay managed operation (non-time-managed-delay-enabled = TRUE)
1634 then O-RU handles U-Plane transmission on best effort basis. In this case any combination of values
1635 of transmission-window-offset, symbol-specific offset from transmission-window-schedules and
1636 transmission-window-size is permitted. This does not remove restrictions on parameters due to restrictions
1637 defined for value type or restrictions that depend on INDEPENDENT-TRANSMISSION-WINDOW-CONTROL feature
1639 Additional restrictions on values (and presence) of transmission-window-schedule, transmission-window-offset
1640 and transmission-window-size depend on presence of INDEPENDENT-TRANSMISSION-WINDOW-CONTROL feature.
1642 If INDEPENDENT-TRANSMISSION-WINDOW-CONTROL feature is not supported then all endpoints with
1643 transmission control enabled that handle the same carrier type and SCS must be configured
1644 (via M-plane or C-plane) with parameter values resulting in transmission windows that coincide
1645 between the endpoints. That is, for every symbol N, the effective transmission window for symbol N
1646 must be shared (start at the same time and end at the same time) by all the endpoints handling
1647 same carrier type and SCS. This restriction applies only to endpoints that have transmission
1650 If INDEPENDENT-TRANSMISSION-WINDOW-CONTROL feature is supported then restriction described
1651 above does not apply and a different transmission window (window offset and window size)
1652 can be used for every endpoint capable of transmission window control.";
1655 leaf transmission-window-size {
1656 when "(../transmission-window-control = 'STATIC')";
1657 if-feature feat:STATIC-TRANSMISSION-WINDOW-CONTROL;
1661 units "microsecond";
1664 "Transmission window size to be used; only values that are compatible with SCS used
1665 for the endpoint are allowed.
1666 Minimum supported value is determined by SCS specific transmission window size
1667 reported by O-RU in ru-delay-profile.
1669 Client can use special value 0 (zero) instead of the SCS specific transmission window
1670 size reported by O-RU in ru-delay-profile with the same effect.
1671 This parameter shall not be set to value other than 0 if transmission control is not enabled
1672 (transmission-window-control = NONE) or the endpoint is set for non-delay managed operation
1673 (non-time-managed-delay-enabled = TRUE).
1675 There is no direct upper bound for this parameter (except value range defined by leaf type) but there are
1676 restrictions on combination of values of transmission-window-offset, transmission-window-offset,
1677 symbol-specific offset from transmission-window-schedules and transmission-window-size.
1678 See description of transmission-window-offset for more details.";
1681 leaf transmission-type {
1682 when "(../transmission-window-control = 'STATIC')";
1683 if-feature "feat:STATIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION";
1687 "Normal transmission (unspecified within transmission window)";
1689 enum UNIFORMLY-DISTRIBUTED {
1690 if-feature feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION;
1692 "Uniformly distributed over transmission window: each of N messages in the window
1693 transmitted at random time in a separate subwindow; subwindow size is window size / N ";
1697 description "Type of delay supported by the endpoint";
1701 grouping tx-endpoint-compression-grouping {
1703 "Grouping for endpoint compression";
1705 container compression {
1707 "This container shall exists to avoid misaligned compression
1708 methods between devices";
1711 "Container which consists of global configurable parameters for compression";
1713 uses cf:compression-details;
1716 if-feature cf:CONFIGURABLE-FS-OFFSET;
1720 "Adjusts FS (full scale) value of IQ format relative to FS derived from unmodified IQ format.
1721 Please refer to CU-Plane specification for details";
1724 list dynamic-compression-configuration {
1725 when "../compression-type = 'DYNAMIC'";
1727 unique "compression-method iq-bitwidth fs-offset";
1729 "List of possible configuration in case dynamic configuration is used
1730 Note: In case of empty list all available compressions can be chosen dynamically
1731 and default fs-offset is taken (0).
1732 If the feature CONFIGURABLE-FS-OFFSET is not supported,
1733 fs-offset will not be considered as one of the criteria for unique statement.
1734 Refer to RFC7950 clause 7.8.3 for details of unique statement";
1739 "Identification number for particular compression";
1742 uses cf:compression-method-grouping;
1745 if-feature cf:CONFIGURABLE-FS-OFFSET;
1749 "Adjusts FS (full scale) value of IQ format relative to FS derived from unmodified IQ format.
1750 Please refer to CU-Plane specification for details";
1753 leaf channel-information-iq-bitwidth {
1759 "I/Q bitwidth for channel information in Section Type6.
1760 Leaf is deprecated as it should be independent of dynamic compression,
1761 NETCONF client instead uses channel-information-bitwidth schema node";
1765 leaf channel-information-bitwidth {
1770 "I/Q bitwidth for channel information in Section Type6.
1771 maximum value of 16bit is limitted by 4bit ciIqWidth in the C-Plane message.
1772 Note: This parameter shall be used when the NETCONF client does not make use of
1773 the CHANNEL-INFORMATION-COMPRESSION feature.";
1776 list channel-information-compressions {
1777 if-feature "feat:CHANNEL-INFORMATION-COMPRESSION";
1783 "Identification number for particular channel information compression";
1786 leaf channel-information-compression-method {
1787 type cf:ci-compression-method-def;
1789 "Channel information compression method";
1797 "Bitwidth to be used in compression, maximum value of 16bit is limitted by 4bit ciIqWidth in the C-Plane message.
1799 When this schema node is used in the configuration, the O-RU shall ignore the configuration of the
1800 /low-level-tx-endpoints/compression/channel-information-bitwidth schema node";
1804 "List of available compressions, that can be dynamically choosen, for channel information (e.g. ST6) for this endpoint.
1805 Note1: When only one compression is listed here, it implies that channel information compression
1806 is static and mentioned compression is taken into use.
1807 Note2: O-RU Shall reject configuration with compressions that are not supported";
1810 list bf-weights-compressions {
1816 "Identification number for particular beamforming compression";
1819 leaf bf-weights-compression {
1820 type cf:bf-compression-method-def;
1822 "Beamforming weight compression method";
1828 "Bitwidth to be used in compression";
1832 "List of available compressions, that can be dynamically choosen, for beamforming weights for this endpoint.
1833 Note1: When only one compression is listed here, it implies that beamforming weights compression
1834 is static and mentioned compression is taken into use.
1835 Note2: O-RU Shall reject configuration with compressions that are not supported";
1840 grouping rx-endpoint-compression-grouping {
1842 "Grouping for endpoint compression";
1844 container compression {
1846 "This container shall exists to avoid misaligned compression
1847 methods between devices";
1850 "Container which consists of global configurable parameters for compression";
1852 uses cf:compression-details;
1855 if-feature cf:CONFIGURABLE-FS-OFFSET;
1859 "Adjusts FS (full scale) value of IQ format relative to FS derived from unmodified IQ format.
1860 Please refer to CU-Plane specification for details";
1863 list dynamic-compression-configuration {
1864 when "../compression-type = 'DYNAMIC'";
1866 unique "compression-method iq-bitwidth fs-offset";
1868 "List of possible configuration in case dynamic configuration is used
1869 Note: In case of empty list all available compressions can be chosen dynamically
1870 and default fs-offset is taken (0).
1871 If the feature CONFIGURABLE-FS-OFFSET is not supported,
1872 fs-offset will not be considered as one of the criteria for unique statement.
1873 Refer to RFC7950 clause 7.8.3 for details of unique statement";
1878 "Identification number for particular compression";
1881 uses cf:compression-method-grouping;
1884 if-feature cf:CONFIGURABLE-FS-OFFSET;
1888 "Adjusts FS (full scale) value of IQ format relative to FS derived from unmodified IQ format.
1889 Please refer to CU-Plane specification for details";
1893 list bf-weights-compressions {
1899 "Identification number for particular beamforming compression";
1902 leaf bf-weights-compression {
1903 type cf:bf-compression-method-def;
1905 "Beamforming weight compression method";
1911 "Bitwidth to be used in compression";
1915 "List of available compressions, that can be dynamically choosen, for beamforming weights for this endpoint.
1916 Note1: When only one compression is listed here, it implies that beamforming weights compression
1917 is static and mentioned compression is taken into use.
1918 Note2: O-RU Shall reject configuration with compressions that are not supported";
1923 grouping supported-section-type4-config {
1925 "Set of parameters required for section type 4 slot configuration message.";
1926 list st4-supported-commands {
1927 key "st4-command-type";
1930 "This parameter specifies the list of Section Type 4 command types supported by O-RU.";
1931 leaf st4-command-type {
1933 enum TIME_DOMAIN_BEAM_CONFIG {
1934 description "O-RU support for receiving time domain beamforming command.";
1936 enum TDD_CONFIG_PATTERN {
1937 description "O-RU support for receiving TDD symbol pattern for a given slot.";
1941 "Section Type 4 command types supported by O-RU.";
1945 list st4-reception-mask {
1949 "List of symbol mask per command scope, specifying the O-RU capability to receive Section Type 4 message for a
1950 given command scope only for symbols for which the corresponding bit is set to '1' in the bitmask. If the O-RU
1951 receives a Section Type 4 message with associated command for a symbol whose bit value is set to '0' in this
1952 bitmask, the O-RU shall reject the Section Type 4 message";
1956 enum ARRAY-COMMAND {
1958 "Command applies to all endpoints assigned to the tx-array(s) and/or rx-array(s).If the O-RU
1959 is operating with multiple O-DUs, the scope of an individual O-DU is limited, to the
1960 endpoints assigned to the O-DU which was the originator of the command.";
1962 enum CARRIER-COMMAND {
1964 "Command applies to all endpoints assigned to the tx-array-carrier and/or rx-array-carrier.";
1968 "O-RU level command, i.e., one that applies to all arrays and carriers. If the O-RU
1969 is operating with multiple O-DUs, the scope of an individual O-DU is limited, as
1970 specified in CUS-Plane specification, clause 7.5.2.17.";
1973 description "Command scope for section type 4 commands";
1976 leaf st4-reception-bitmask {
1979 "This parameter specifies the O-RU capability to receive Section Type 4 message with associated commands for the symbols
1980 for which the corresponding bit is set to '1' in the bitmask. If the O-RU receives a Section Type 4 message with
1981 associated command for a symbol whose bit value is set to '0' in this bitmask, the O-RU shall reject the Section Type 4 message";
1986 grouping uplane-conf-group {
1988 "Grouping for uplane configuration related parameters";
1990 list low-level-tx-links {
1993 "Object model for low-level-tx-link configuration";
1998 "Unique name of low-level-tx-link object.";
2002 if-feature feat:SHARED-ORU-MULTI-OPERATOR;
2004 path "/or-user:users/or-user:user/or-user:sro-id";
2007 "An optional shared resource operator associated with this list entry.
2008 When present, indicates that the list entry corresponds to a low-level-tx-link
2009 associated with a shared resouce operator where the sro-id idenifies
2010 a specific shared resouce operator.
2011 This schema-node is used to refine NACM privileges for shared
2012 resource operators";
2015 leaf processing-element {
2017 path "/o-ran-pe:processing-elements/o-ran-pe:ru-elements/o-ran-pe:name";
2021 "Contains name of processing-element to be used as transport by low-level-tx-link,
2022 if 'transport-qualified-processing-element' is included in the configuration,
2023 the O-RU shall use 'transport-qualified-processing-element' instead of this schema node,
2024 an O-RU Controller shall still configure this schema node with a leafref to a valid ru-element,
2025 but this shall not be used by the O-RU.";
2028 leaf transport-session-type {
2029 if-feature "feat:MULTIPLE-TRANSPORT-SESSION-TYPE";
2031 enum ETH-INTERFACE {
2032 description "VLAN based CUS Transport ";
2034 enum UDPIP-INTERFACE {
2035 description "UDP/IP based CUS Transport ";
2037 enum ALIASMAC-INTERFACE{
2038 description "Alias MAC address based CUS Transport ";
2042 "transport session type used when an O-RU is configured with multiple processing elements of different transport session types,
2043 in which case it is used for referencing a processing element in 'transport-qualified-processing-element'";
2046 leaf transport-qualified-processing-element {
2047 if-feature "feat:MULTIPLE-TRANSPORT-SESSION-TYPE";
2049 path "/o-ran-pe:processing-elements/o-ran-pe:additional-transport-session-type-elements[o-ran-pe:transport-session-type = current()/../transport-session-type]/o-ran-pe:ru-elements/o-ran-pe:name";
2052 "Contains name of processing-element to be used as transport by low-level-tx-link.
2053 Used when the processing element is configured
2054 by the list 'additional-transport-session-type-elements'";
2057 leaf tx-array-carrier {
2059 path "/user-plane-configuration/tx-array-carriers/name";
2063 "Contains name of tx-array-carriers MO to be used as transport by low-level-tx-link";
2066 leaf low-level-tx-endpoint {
2068 path "/user-plane-configuration/low-level-tx-endpoints/name";
2072 "Contains name of low-level-tx-endpoints MO to be used as transport by low-level-tx-link";
2076 list low-level-rx-links {
2079 "Object model for low-level-rx-links configuration";
2085 "Unique name of low-level-rx-links object.";
2089 if-feature feat:SHARED-ORU-MULTI-OPERATOR;
2091 path "/or-user:users/or-user:user/or-user:sro-id";
2094 "An optional shared resource operator associated with this list entry.
2095 When present, indicates that the list entry corresponds to a low-level-rx-link
2096 associated with a shared resouce operator where the sro-id idenifies
2097 a specific shared resouce operator.
2098 This schema-node is used to refine NACM privileges for shared
2099 resource operators";
2102 leaf processing-element {
2104 path "/o-ran-pe:processing-elements/o-ran-pe:ru-elements/o-ran-pe:name";
2108 "Contains name of processing-element to be used as transport by low-level-rx-link,
2109 if 'transport-qualified-processing-element' is included in the configuration,
2110 the O-RU shall use 'transport-qualified-processing-element' instead of this schema node,
2111 an O-RU Controller shall still configure this schema node with a leafref to a valid ru-element,
2112 but this shall not be used by the O-RU.";
2115 leaf transport-session-type {
2116 if-feature "feat:MULTIPLE-TRANSPORT-SESSION-TYPE";
2118 enum ETH-INTERFACE {
2119 description "VLAN based CUS Transport ";
2121 enum UDPIP-INTERFACE {
2122 description "UDP/IP based CUS Transport ";
2124 enum ALIASMAC-INTERFACE{
2125 description "Alias MAC address based CUS Transport ";
2129 "transport session type used when an O-RU is configured with multiple processing elements of different transport session types,
2130 in which case it is used for referencing a processing element in 'transport-qualified-processing-element'";
2133 leaf transport-qualified-processing-element {
2134 if-feature "feat:MULTIPLE-TRANSPORT-SESSION-TYPE";
2136 path "/o-ran-pe:processing-elements/o-ran-pe:additional-transport-session-type-elements[o-ran-pe:transport-session-type = current()/../transport-session-type]/o-ran-pe:ru-elements/o-ran-pe:name";
2139 "Contains name of processing-element to be used as transport by low-level-rx-link.
2140 Used when the processing element is configured
2141 by the list 'additional-transport-session-type-elements'";
2144 leaf rx-array-carrier {
2146 path "/user-plane-configuration/rx-array-carriers/name";
2151 "Contains name of rx-array-carriers MO to be used as transport by low-level-rx-links";
2154 leaf low-level-rx-endpoint {
2156 path "/user-plane-configuration/low-level-rx-endpoints/name";
2161 "Contains name of low-level-rx-endpoints MO to be used as transport by low-level-rx-links";
2164 leaf user-plane-uplink-marking {
2166 path "/o-ran-pe:processing-elements/o-ran-pe:enhanced-uplane-mapping/o-ran-pe:uplane-mapping/o-ran-pe:up-marking-name";
2169 "Parameter to set the non-default marking for user-plane";
2172 leaf enhanced-user-plane-uplink-marking {
2173 if-feature "feat:MULTIPLE-TRANSPORT-SESSION-TYPE";
2175 path "/o-ran-pe:processing-elements/o-ran-pe:additional-transport-session-type-elements[o-ran-pe:transport-session-type = current()/../transport-session-type]/o-ran-pe:enhanced-uplane-mapping/o-ran-pe:uplane-mapping/o-ran-pe:up-marking-name";
2178 "Parameter to set the non-default marking for user-plane.
2179 Used when the enhanced-uplane-mapping is configured
2180 by the list 'additional-transport-session-type-elements'";
2184 list endpoint-types {
2188 "Properties of endpoint that are common to multiple endpoints if such are identified
2189 Note: For any endpoint supporting mixed numerology within slot/symbol (multiple-numerology-supported=TRUE)
2190 * Interval specific (per-slot and per-symbol) capacity constraints instantaneous capacity usage
2191 (i.e. capacity is shared/distributed between all numerologies used at an instant of time).
2192 * Instantaneous capacity usage is the sum of capacity usages of all intervals of a specific type (slot/symbol)
2193 that share the instant of time at which instantaneous capacity usage is evaluated regardless of numerology.
2194 * Capacity used in an interval is allocated at the start of the interval and is released at the end of the interval
2195 (e.g. capacity used for symbol #N of numerology #M is unavailable during symbol #N and available for reuse after symbol #N ends).";
2200 "Identifies type of endpoints sharing same properties. Values shall start with 0 and shall be allocated without gaps.";
2203 list supported-section-types {
2206 "Indicates section types and extensions endpoints of this type support";
2212 "This parameter determines the characteristics of U-plane data to be transferred or received from a beam with one pattern id.";
2215 leaf-list supported-section-extensions {
2219 "This parameter provides the extension types supported by the O-RU
2220 which provides additional parameters specific to the subject data extension";
2224 uses supported-section-type4-config {
2225 if-feature feat:ST4-SLOT-CONFIG-MSG-SUPPORT;
2228 leaf-list supported-frame-structures {
2232 "List of supported values of frame structure. For semantic and allowed values see CUS-Plane Specification, clause 'frameStructure (frame structure)'";
2235 leaf managed-delay-support {
2239 "Time managed delays are supported";
2244 "Non time managed delays are supported";
2249 "Both time managed and non time managed delays are supported";
2254 "Type of delay supported by the endpoint";
2257 leaf multiple-numerology-supported {
2261 "Indicates whether the endpoint type supports multiple numerologies";
2264 leaf max-numerology-change-duration {
2271 "Maximum gap of endpoint operation that will be caused by changing of
2274 This time is required for reconfiguration and flushing of pipes.
2276 This leaf contains valid data only when multiple-numerology-supported
2280 uses endpoint-section-capacity;
2281 uses endpoint-beam-capacity;
2282 uses endpoint-prb-capacity;
2283 uses endpoint-section-extension-limits;
2285 leaf-list prb-capacity-allocation-granularity {
2289 "List of capacity allocation steps. O-RU allocates PRB capacity rounding it up to nearest value N
2290 from prb-capacity-allocation-granularity such that M >= number-of-prb-per-scs.
2291 See also number-of-prb-per-scs/number-of-prb.";
2294 uses endpoint-numerology-capacity;
2296 leaf static-transmission-window-control-supported {
2297 if-feature feat:STATIC-TRANSMISSION-WINDOW-CONTROL;
2300 "Endpoint supports transmission-window-control = STATIC";
2303 leaf uniformly-distributed-transmission-supported {
2304 if-feature "feat:STATIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION";
2307 "Endpoint supports transmission-type = UNIFORMLY-DISTRIBUTED";
2310 leaf ordered-transmission-supported {
2311 if-feature feat:ORDERED-TRANSMISSION;
2314 "Endpoint supports ordered transmission of U-plane messages
2315 and can be configured with ordered-transmission = TRUE";
2318 leaf dynamic-transmission-window-control-supported {
2319 if-feature feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL;
2322 "Endpoint supports U-plane transmission window control via C-plane
2323 (supports transmission-window-control = DYNAMIC) with independent window offset and size per symbol";
2326 leaf dynamic-transmission-window-control-per-section-supported {
2327 when "../dynamic-transmission-window-control-supported = 'true'";
2328 if-feature feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL;
2331 "Endpoint supports U-plane transmission window control via C-plane
2332 (supports transmission-window-control = DYNAMIC) with independent window offset and size per section";
2335 leaf dynamic-uniformly-distributed-transmission-supported {
2336 if-feature "feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION";
2339 "Endpoint supports U-plane transmission window control via C-plane
2340 (supports transmission-window-control = DYNAMIC) with independent transmission type per symbol";
2343 leaf dynamic-uniformly-distributed-transmission-per-section-supported {
2344 when "../dynamic-uniformly-distributed-transmission-supported = 'true'";
2347 "Endpoint supports U-plane transmission window control via C-plane
2348 (supports transmission-window-control = DYNAMIC) with independent transmission type per section";
2351 uses transmission-buffering-capacity {
2352 when "static-transmission-window-control-supported = 'true' or dynamic-transmission-window-control-supported = 'true'";
2353 if-feature "feat:STATIC-TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL";
2356 leaf cplane-message-processing-limits-required {
2357 if-feature feat:CPLANE-MESSAGE-PROCESSING-LIMITS;
2361 "Endpoint requires applying C-Plane message processing limits defined in 'per-cplane-message-limits'.
2362 and can be configured with cplane-message-processing-limits-enabled = TRUE";
2365 uses per-cplane-message-limits {
2366 when "cplane-message-processing-limits-required = 'true'";
2367 if-feature feat:CPLANE-MESSAGE-PROCESSING-LIMITS;
2370 leaf beam-update-contention-control-limits-required {
2371 if-feature feat:BEAM-UPDATE-CONTENTION-CONTROL;
2375 "Endpoint requires applying beam update contention control limits defined in 'beam-update-contention-control-limits'.
2376 and can be configured with beam-update-contention-control-enabled = TRUE";
2379 uses beam-update-contention-control-limits {
2380 when "beam-update-contention-control-limits-required = 'true'";
2381 if-feature feat:BEAM-UPDATE-CONTENTION-CONTROL;
2384 leaf max-ack-nack-per-symbol {
2387 "This value indicates the max number of ACK/NACK feedbacks supported by the endpoint in a symbol when
2388 section extension 22 (ACK/NACK request) and section type 8 (ACK/NACK feedback) are supported by the endpoint.
2389 The number of ACK/NACK feedbacks in a symbol is defined as the sum of 'numberofACKs' + 'numberofNACKs' in all C-Plane
2390 messages sent by the endpoints in a symbol";
2394 list transmission-window-schedules {
2395 if-feature feat:STATIC-TRANSMISSION-WINDOW-CONTROL;
2399 "Parameters for scheduled UL U-plane message transmission (static transmission window control)";
2404 "Identifies a UL U-plane message transmission schedule";
2410 "Defines transmission window offset for given symbol.
2411 If no entry is present for a symbol then O-RU assumes offset=0 for that symbol.
2412 Entries with offset=0 shall be omitted.";
2417 "Number of a symbol within a frame for which transmission offset is given.";
2423 "Transmission window offset; expressed as number of symbols the transmission window start is delayed by.
2424 This value is added to u-plane-transmission-control/transmission-window-offset.
2425 For restrictions on value of offset see description of transmission-window-offset.";
2430 list endpoint-capacity-sharing-groups {
2434 "Represents groups of endpoints that share capacity. Depending on O-RU implementation,
2435 processing resources that handle CU-plane (e.g. memory to keep sections and beams)
2436 could be allocated per endpoint or shared between several endpoints.
2437 To address this O-RU shall report own capability per endpoint (see endpoint-types)
2438 and per group of endpoints sharing capacity.
2439 If endpoint is in multiple groups then resulting constraint is minimum over all groups.
2440 Note: values of parameters representing capacity that is not shared between endpoints in a group
2441 shall be set to max value of specific parameter; this effectively removes related constraint.
2442 Note: For any endpoint supporting mixed numerology within slot/symbol (multiple-numerology-supported=TRUE)
2443 * Interval specific (per-slot and per-symbol) capacity constraints instantaneous capacity usage
2444 (i.e. capacity is shared/distributed between all numerologies used at an instant of time).
2445 * Instantaneous capacity usage is the sum of capacity usages of all intervals of a specific type (slot/symbol)
2446 that share the instant of time at which instantaneous capacity usage is evaluated regardless of numerology.
2447 * Capacity used in an interval is allocated at the start of the interval and is released at the end of the interval
2448 (e.g. capacity used for symbol #N of numerology #M is unavailable during symbol #N and available for reuse after symbol #N ends).";
2453 "Identifies group of endpoints sharing resources.
2454 Values shall start with 0 and shall be allocated without gaps.";
2456 uses endpoint-section-capacity;
2457 uses endpoint-beam-capacity;
2458 uses endpoint-prb-capacity;
2459 uses endpoint-numerology-capacity;
2460 uses endpoint-section-extension-limits;
2462 leaf max-endpoints {
2465 "Indicates how many endpoints in the group can be used4 simultaneously";
2467 leaf max-managed-delay-endpoints {
2470 "Number of endpoints supporting managed delay that can be used (configured for use) at a time";
2472 leaf max-non-managed-delay-endpoints {
2475 "Number of endpoints supporting non-managed delay that can be used (configured for use) at a time";
2477 uses transmission-buffering-capacity {
2478 if-feature "feat:STATIC-TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL";
2481 uses per-cplane-message-limits {
2482 if-feature feat:CPLANE-MESSAGE-PROCESSING-LIMITS;
2485 leaf max-ack-nack-per-symbol {
2488 "This value indicates the max number of ACK/NACK feedbacks supported by the endpoint sharing group in a symbol when
2489 section extension 22 (ACK/NACK request) and section type 8 (ACK/NACK feedback) are supported by the endpoint sharing group.
2490 The number of ACK/NACK feedbacks in a symbol is defined as the sum of 'numberofACKs' + 'numberofNACKs' in all C-Plane
2491 messages sent by the endpoints in group in a symbol";
2495 list endpoint-prach-group {
2499 "Represents group of a series of PRACH preamble formats";
2504 "Identifies group of PRACH preamble formats.";
2507 leaf-list supported-prach-preamble-formats {
2508 type prach-preamble-format;
2511 "the list of PRACH preamble formats supported by the endpoint-type that is
2512 applicable to static-low-level-rx-endpoints in the O-RU";
2517 list supported-compression-method-sets {
2521 "List of available compression methods supported by device";
2526 "Identification number for compression method set";
2529 list compression-method-supported {
2530 uses cf:compression-method-grouping;
2531 uses cf:compresion-format-grp {
2535 leaf-list fs-offset {
2536 if-feature cf:CONFIGURABLE-FS-OFFSET;
2540 "Adjusts FS (full scale) value of IQ format relative to FS derived from unmodified IQ format.
2541 Please refer to CU-Plane specification for details";
2545 "List of supported compression methods by O-RU
2546 Note: if O-RU supports different compression methods per endpoint
2547 then please refer to endpoints to have information what
2548 exactly is supported on particular endpoint";
2552 list static-low-level-tx-endpoints {
2556 "Object model for static-low-level-tx-endpoints configuration";
2562 "Unique name of static-low-level-tx-endpoints object.";
2565 leaf-list restricted-interfaces {
2567 path "/if:interfaces/if:interface/if:name";
2570 "Optionally used to indicate that a low-level link is constrained to operate only via a subset of the available interfaces.";
2575 path "/user-plane-configuration/tx-arrays/name";
2579 "Contains distname of tx-arrays, particular low-level-tx-endpoints is in hardware dependency with.
2580 Note: single instance of tx-arrays can be referenced by many instances of low-level-tx-endpoints
2581 (e.g. to allow DU to handle multiple fronthauls and multiple component carriers).";
2584 leaf endpoint-type {
2586 path "../../endpoint-types/id";
2590 "Reference to endpoint type capabilities list element supported by this endpoint";
2593 leaf-list capacity-sharing-groups {
2595 path "../../endpoint-capacity-sharing-groups/id";
2599 "Reference to capacities of sharing-groups supported by this endpoint";
2602 list supported-reference-level {
2603 if-feature TX-REFERENCE-LEVEL;
2606 "Informs about supported ranges for gain reference level.";
2611 "Identification number for particular range";
2621 "Minimum of supported gain reference level";
2631 "Maximum of supported gain reference level";
2635 container compression {
2637 "Container collecting compression related parameters.";
2639 leaf dynamic-compression-supported {
2643 "Informs if endpoint supports dynamic compression method";
2646 leaf realtime-variable-bit-width-supported {
2650 "Informs if endpoint supports real-time variable bit with";
2653 leaf supported-compression-set-id {
2655 path "../../../supported-compression-method-sets/id";
2659 "Id of supported compression set for this endpoint";
2663 uses endpoint-tdd-pattern-support;
2667 list static-low-level-rx-endpoints {
2671 "Object model for static-low-level-rx-endpoints configuration";
2677 "Unique name of static-low-level-rx-endpoints object.";
2680 leaf-list restricted-interfaces {
2682 path "/if:interfaces/if:interface/if:name";
2685 "Optionally used to indicate that a low-level link is constrained to operate only via a subset of the available interfaces.";
2690 path "/user-plane-configuration/rx-arrays/name";
2694 "Contains distname of rx-arrays, particular low-level-rx-endpoints is in hardware dependency with.
2695 Note: single instance of rx-arrays can be referenced by many instances of low-level-rx-endpoints
2696 (e.g. to allow DU to handle multiple fronthauls and multiple component carriers).";
2699 leaf endpoint-type {
2701 path "../../endpoint-types/id";
2705 "Reference to endpoint type capabilities list element supported by this endpoint";
2708 leaf-list capacity-sharing-groups {
2710 path "../../endpoint-capacity-sharing-groups/id";
2714 "Reference to capacities of sharing-groups supported by this endpoint";
2719 path "../../endpoint-prach-group/id";
2720 require-instance false;
2723 "An optional leaf used for those rx endpoints that support PRACH, indicating
2724 the group id describing the set of of PRACH preambles supported";
2727 container compression {
2729 "Container collecting compression related parameters.";
2731 leaf dynamic-compression-supported {
2735 "Informs if endpoint supports dynamic compression method";
2738 leaf realtime-variable-bit-width-supported {
2742 "Informs if endpoint supports real-time variable bit with";
2745 leaf supported-compression-set-id {
2747 path "../../../supported-compression-method-sets/id";
2751 "Id of supported compression set for this endpoint";
2755 uses endpoint-static-config-support;
2757 uses endpoint-tdd-pattern-support;
2759 leaf transmission-order {
2760 when "(/user-plane-configuration/endpoint-types[id=current()/../endpoint-type]/ordered-transmission-supported = 'true')";
2761 if-feature feat:ORDERED-TRANSMISSION;
2764 "The value indicates relative order of sending U-plane messages specific to same symbol
2765 and transmission window by two endpoints with ordered-transmission = TRUE
2766 belonging to the same transmission-order-group;
2767 multiple endpoints may report the same value if their relative sending order is not guaranteed";
2770 leaf transmission-order-group {
2771 when "(/user-plane-configuration/endpoint-types[id=current()/../endpoint-type]/ordered-transmission-supported = 'true')";
2772 if-feature feat:ORDERED-TRANSMISSION;
2775 "The value indicates a group of endpoints that preserve relative ordering of message sending;
2776 message sending between endpoints in different groups is not guaranteed";
2780 list low-level-tx-endpoints {
2784 "Object model for low-level-tx-endpoints configuration - augmented static-low-level-tx-endpoints by local-address
2785 which cannot be added to static low-level-tx-endpoints as we cannot have modifiable element in static object";
2789 path "/user-plane-configuration/static-low-level-tx-endpoints/name";
2790 require-instance false;
2795 "Unique name of low-level-tx-endpoint object. Reference to static object";
2799 if-feature feat:SHARED-ORU-MULTI-OPERATOR;
2801 path "/or-user:users/or-user:user/or-user:sro-id";
2804 "An optional shared resource operator associated with this list entry.
2805 When present, indicates that the list entry corresponds to a low-level-tx-endpoint
2806 associated with a shared resouce operator where the sro-id idenifies
2807 a specific shared resouce operator.
2808 This schema-node is used to refine NACM privileges for shared
2809 resource operators";
2813 uses tx-endpoint-compression-grouping;
2820 "Contains local address of low level TX endpoint offered by NETCONF server.";
2823 uses coupling-methods;
2825 leaf configurable-tdd-pattern-supported {
2826 if-feature mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED;
2828 path "/user-plane-configuration/static-low-level-rx-endpoints[name=current()/../name]/configurable-tdd-pattern-supported";
2829 require-instance false;
2831 description "RO to RW parameter mapping - needed for conditional under tx-array-carrier";
2834 leaf cplane-message-processing-limits-enabled {
2835 if-feature feat:CPLANE-MESSAGE-PROCESSING-LIMITS;
2839 "TRUE: O-DU shall support the C-Plane message processing limits and has selected to adhere to the C-Plane limits defined in 'per-cplane-message-limits'.
2840 FALSE: O-DU shall not support C-Plane message processing limits and endpoint limits defined in 'per-cplane-message-limits' shall not apply";
2843 leaf beam-update-contention-control-enabled {
2844 if-feature feat:BEAM-UPDATE-CONTENTION-CONTROL;
2848 "TRUE: O-DU shall support beam update contention control feature of O-RU.Thus requiring O-DU to comply with beam
2849 updates restrictions defined in CUS-Plane Spec Section 'Weight-based dynamic beamforming'. In this case applicable
2850 beam limits defined in 'beam-update-contention-control-limits' shall apply.
2851 FALSE: O-DU shall not support beam update contention control feature of O-RU. Applicable beam limits defined in
2852 'endpoint-beam-capacity' shall apply";
2855 container channel-information-prb-group-configuration {
2856 if-feature feat:CHANNEL-INFORMATION-PRB-GROUP;
2858 "Container for configurable parameters for channel information prb group";
2860 leaf enable-ci-prb-group {
2863 "Informs whether or not to enable channel information PRB group in the O-RU,
2864 if its value is set to true, the O-RU shall receive and process channel
2865 information (e.g., ST6) with PRB group size of configured ci-prb-group-size.";
2868 leaf ci-prb-group-size {
2873 "The configured channel information PRB group size.
2874 If enable-ci-prb-group is configured as TRUE, and the IE ciPrbGroupSize doesn't exsit in a section description for channel information,
2875 the parameter ci-prb-group-size shall be used for this section description.
2876 If the IE ciPrbGroupSize exsits in a section description for channel information,
2877 no matter whether enable-ci-prb-group is configured as TRUE, the IE ciPrbGroupSize shall be used for this section description.";
2882 list low-level-rx-endpoints {
2886 "Object model for low-level-rx-endpoint configuration - augmented static-low-level-rx-endpoints by local-address
2887 which cannot be added to static low-level-rx-endpoints as we cannot have modifiable element in static object";
2891 path "/user-plane-configuration/static-low-level-rx-endpoints/name";
2892 require-instance false;
2897 "Unique name of low-level-rx-endpoint object. Reference to static object";
2901 if-feature feat:SHARED-ORU-MULTI-OPERATOR;
2903 path "/or-user:users/or-user:user/or-user:sro-id";
2906 "An optional shared resource operator associated with this list entry.
2907 When present, indicates that the list entry corresponds to a low-level-rx-endpoint
2908 associated with a shared resouce operator where the sro-id idenifies
2909 a specific shared resouce operator.
2910 This schema-node is used to refine NACM privileges for shared
2911 resource operators";
2914 uses rx-endpoint-compression-grouping;
2917 list ul-fft-sampling-offsets {
2920 "List of FFT sampling offsets configured for each SCS that will be used.
2921 Client shall configure one element for each SCS that will be used.";
2924 type mcap:scs-config-type;
2926 "Value corresponds to SCS values defined for frameStructure in C-plane
2927 Note: set of allowed values is restricted by SCS derived from values in supported-frame-structures.";
2930 leaf ul-fft-sampling-offset {
2935 "Determines time advance of capture window for FFT.
2936 Value represents time advance of capture window start in relation to the end of CP. Unit is Ts.
2937 Note: value of this parameter is usually set to '0' (zero) for PRACH channels.
2938 Any phase offset resulting from the non-zero value of this parameter is handled in O-DU.";
2946 "Contains local address of low level RX endpoint offered by NETCONF server.";
2949 leaf eaxc-gain-correction {
2950 if-feature EAXC-GAIN-CORRECTION;
2957 "eAxC specific part of overall gain_correction.
2958 gain_correction = common array-carrier gain-correction + eAxC-gain-correction.";
2961 leaf non-time-managed-delay-enabled {
2965 "Tells if non time managed delay shall be enabled";
2968 uses coupling-methods;
2970 leaf static-config-supported {
2972 path "/user-plane-configuration/static-low-level-rx-endpoints[name=current()/../name]/static-config-supported";
2973 require-instance false;
2975 description "RO to RW parameter mapping - for further conditionals";
2978 leaf static-prach-configuration {
2979 when "(/user-plane-configuration/low-level-rx-endpoints[name=current()/../name]/static-config-supported = 'PRACH')";
2980 if-feature mcap:PRACH-STATIC-CONFIGURATION-SUPPORTED;
2982 path "/user-plane-configuration/static-prach-configurations/static-prach-config-id";
2985 "This parameter creates reference to static PRACH configuration applicable for particular endpoint";
2988 leaf static-srs-configuration {
2989 when "(/user-plane-configuration/low-level-rx-endpoints[name=current()/../name]/static-config-supported = 'SRS')";
2990 if-feature mcap:SRS-STATIC-CONFIGURATION-SUPPORTED;
2992 path "/user-plane-configuration/static-srs-configurations/static-srs-config-id";
2995 "This parameter creates reference to static SRS configuration applicable for particular endpoint";
2998 leaf configurable-tdd-pattern-supported {
2999 if-feature mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED;
3001 path "/user-plane-configuration/static-low-level-rx-endpoints[name=current()/../name]/configurable-tdd-pattern-supported";
3002 require-instance false;
3004 description "RO to RW parameter mapping - needed for conditional under rx-array-carrier";
3007 uses u-plane-transmission-control;
3009 leaf ordered-transmission {
3010 if-feature feat:ORDERED-TRANSMISSION;
3014 "Commands O-RU to order UL U-plane message transmission between endpoints
3015 Meaningless when ordered transmission is not supported for particular endpoint.";
3018 leaf cplane-message-processing-limits-enabled {
3019 if-feature feat:CPLANE-MESSAGE-PROCESSING-LIMITS;
3023 "TRUE: O-DU shall support C-Plane message processing limits and has selected to adhere
3024 to the C-Plane limits defined in 'per-cplane-message-limits'.
3025 FALSE: O-DU shall not support C-Plane message processing limits and hence C-Plane and
3026 endpoint limits defined in 'per-cplane-message-limits' shall not apply";
3029 leaf beam-update-contention-control-enabled {
3030 if-feature feat:BEAM-UPDATE-CONTENTION-CONTROL;
3034 "TRUE: O-DU shall support beam update contention control feature of O-RU.Thus requiring O-DU to comply with beam
3035 updates restrictions defined in CUS-Plane Spec Section 'Weight-based dynamic beamforming'. In this case applicable
3036 beam limits defined in 'beam-update-contention-control-limits' shall apply.
3037 FALSE: O-DU shall not support beam update contention control feature of O-RU. Applicable beam limits defined in
3038 'endpoint-beam-capacity' shall apply";
3042 list tx-array-carriers {
3045 "Object model for tx-array-carriers configuration";
3051 "Unique name of tx-array-carriers object.";
3055 if-feature feat:SHARED-ORU-MULTI-ODU;
3058 "An optional list of o-du identities associated with this list entry.
3059 When present, indicates that the list entry corresponds to a tx-array-carrier
3060 associated with one or more particular odu-id(s).
3062 This list is used to enable enhanced watchdog operation when operating
3063 in a single operator environment, where watchdog supervision is performed
3064 on a per odu-id basis and supervision failure only results in a sub-set
3065 of carriers beign de-activated.";
3069 description "an o-du identity ";
3073 list sro-ids-and-odu-ids {
3074 if-feature "feat:SHARED-ORU-MULTI-ODU and feat:SHARED-ORU-MULTI-OPERATOR";
3075 key "odu-id sro-id";
3077 "An optional list of sro and o-du identities associated with this list entry.
3078 When present, indicates that the list entry corresponds to a tx-array-carrier
3079 associated with one or more particular odu-id(s) operated by a particular sro-id.
3081 This list is used to enable enhanced watchdog operationwhen operating
3082 in a multi operator environment, where watchdog supervision is performed on
3083 a per odu-id basis and supervision failure only results in a sub-set of
3084 carriers beign de-activated.";
3087 description "an o-du identity ";
3091 description "an sro identity ";
3095 uses tx-common-array-carrier-elements;
3098 if-feature mcap:LAA;
3100 path "/mcap:module-capability/mcap:band-capabilities/mcap:band-number";
3101 require-instance false;
3104 "This parameter informing which frequency band particular antenna
3105 array is serving for.
3106 Intended use is to deal with multi-band solutions.";
3109 container lte-tdd-frame {
3110 when "(/user-plane-configuration/tx-array-carriers/rw-type = 'LTE') and (/user-plane-configuration/tx-array-carriers/rw-duplex-scheme = 'TDD')";
3113 "Container which consists of global configurable parameters for tdd Frame.
3114 This contained is deprecated due to introduction of TDD pattern configuration
3115 applicable in a common way for LTE and NR.";
3117 leaf subframe-assignment {
3120 description "subframe assignment configuration 0";
3123 description "subframe assignment configuration 1";
3126 description "subframe assignment configuration 2";
3129 description "subframe assignment configuration 3";
3132 description "subframe assignment configuration 4";
3135 description "subframe assignment configuration 5";
3138 description "subframe assignment configuration 6";
3143 "Indicates DL/UL subframe configuration as specified in
3144 3GPP TS 36.211 [v15.3.0, table 4.2-2]";
3146 leaf special-subframe-pattern {
3149 description "special subframe pattern configuration 0";
3152 description "special subframe pattern configuration 1";
3155 description "special subframe pattern configuration 2";
3158 description "special subframe pattern configuration 3";
3161 description "special subframe pattern configuration 4";
3164 description "special subframe pattern configuration 5";
3167 description "special subframe pattern configuration 6";
3170 description "special subframe pattern configuration 7";
3173 description "special subframe pattern configuration 8";
3176 description "special subframe pattern configuration 9";
3179 description "special subframe pattern configuration 10";
3184 "Indicates TDD special subframe configuration as in TS 36.211
3185 [v15.3.0, table 4.2-1] ";
3189 container laa-carrier-configuration {
3190 when "../band-number = 46";
3191 if-feature mcap:LAA;
3192 description "Container to specify LAA feature related carrier configuration.";
3193 uses laa-carrier-config;
3204 "Transmission gain in dB. Value applicable to each array element carrier belonging to array carrier.
3206 The value of tranmsmission gain shall meet the constraints defined in CUS-Plane, clause 8.1.3.3.";
3209 leaf downlink-radio-frame-offset {
3216 "This parameter is used for offsetting the starting position of 10ms radio frame.
3217 Note: The value should have same value within DU to all tx-array-carriers that have same frequency and bandwidth.
3218 Note2: Unit is 1/1.2288e9 s. Then, its range is calculated 0..12288000.";
3221 leaf downlink-sfn-offset {
3223 range -32768..32767;
3228 "This parameter is used for offsetting SFN value.
3230 Note: The value should have same value within DU to all tx-array-carriers that have same frequency and bandwidth.";
3234 if-feature "feat:EXT-ANT-DELAY-CONTROL";
3239 "the time difference between the output of DL signal at the
3240 antenna connector of O-RU and the transmission over the air.
3241 units are Tc=~0.5ns=1/1.96608GHz.
3242 An O-RU with 'ext-ant-delay-capability' = 'PER-O-RU' shall reject any configuration
3243 where different values of t-da-offset are configured on tx-array-carriers;
3244 An O-RU with 'ext-ant-delay-capability' = 'PER-ARRAY' shall reject any configuration
3245 where different values of t-da-offset are configured on tx-array-carriers associated with the same tx-array.";
3248 leaf reference-level {
3249 if-feature TX-REFERENCE-LEVEL;
3256 "Allows to adjust reference level for sum of IQ signal power over eAxCs in this array-carrier.";
3259 leaf configurable-tdd-pattern {
3260 when "not(/user-plane-configuration/low-level-tx-endpoints[name = string(/user-plane-configuration/low-level-tx-links[tx-array-carrier = current()/../name]/tx-array-carrier)]/configurable-tdd-pattern-supported = 'false')";
3261 if-feature mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED;
3263 path "/user-plane-configuration/configurable-tdd-patterns/tdd-pattern-id";
3266 "This parameter creates reference to configuration for TDD pattern applicable for particular tx-array-carrier.
3267 The leaf may exist under tx-array-carrier only in case O-RU supports feature 'CONFIGURABLE-TDD-PATTERN-SUPPORTED'
3268 AND all low-level-tx-endpoints linked to this tx-array-carrier have configurable-tdd-pattern-supported = 'true'";
3272 list rx-array-carriers {
3275 "Object model for rx-array-carriers configuration";
3280 "Unique name of rx-array-carriers object.";
3284 if-feature feat:SHARED-ORU-MULTI-ODU;
3287 "An optional list of o-du identities associated with this list entry.
3288 When present, indicates that the list entry corresponds to a rx-array-carrier
3289 associated with one or more particular odu-id(s).
3291 This list is used to enable enhanced watchdog operation when operating
3292 in a single operator environment, where watchdog supervision is performed
3293 on a per odu-id basis and supervision failure only results in a sub-set
3294 of carriers beign de-activated.";
3298 description "an o-du identity ";
3302 list sro-ids-and-odu-ids {
3303 if-feature "feat:SHARED-ORU-MULTI-ODU and feat:SHARED-ORU-MULTI-OPERATOR";
3304 key "odu-id sro-id";
3306 "An optional list of sro and o-du identities associated with this list entry.
3307 When present, indicates that the list entry corresponds to a rx-array-carrier
3308 associated with one or more particular odu-id(s) operated by a particular sro-id.
3310 This list is used to enable enhanced watchdog operationwhen operating
3311 in a multi operator environment, where watchdog supervision is performed on
3312 a per odu-id basis and supervision failure only results in a sub-set of
3313 carriers beign de-activated.";
3316 description "an o-du identity ";
3320 description "an sro identity ";
3324 uses rx-common-array-carrier-elements;
3326 leaf downlink-radio-frame-offset {
3333 "This parameter is used for offsetting the starting position of 10ms radio frame.
3334 Note: The value should have same value within DU to all tx-array-carriers that have same frequency and bandwidth.
3335 Note2: Unit is 1/1.2288e9 s. Then, its range is calculated 0..12288000.";
3338 leaf downlink-sfn-offset {
3340 range -32768..32767;
3345 "This parameter is used for offsetting SFN value.
3347 Note: The value should have same value within DU to all tx-array-carriers that have same frequency and bandwidth.";
3350 leaf gain-correction {
3358 "Gain correction of RF path linked with array element or array layers.
3359 Common part of overall gain_correction.
3360 gain_correction = common array-carrier gain-correction + eAxC gain correction.";
3368 "Value of configurable N-TA offset
3369 units are Tc=~0.5ns=1/1.96608GHz";
3373 if-feature "feat:EXT-ANT-DELAY-CONTROL";
3378 "the time difference between the reception over the air and
3379 the input of UL signal at the antenna connector of O-RU.
3380 units are Tc=~0.5ns=1/1.96608GHz.
3381 An O-RU with 'ext-ant-delay-capability' = 'PER-O-RU' shall reject any configuration
3382 where different values of t-au-offset are configured on rx-array-carriers;
3383 An O-RU with 'ext-ant-delay-capability' = 'PER-ARRAY' shall reject any configuration
3384 where different values of t-au-offset are configured on rx-array-carriers associated with the same rx-array.";
3387 leaf configurable-tdd-pattern {
3388 when "not(/user-plane-configuration/low-level-rx-endpoints[name = string(/user-plane-configuration/low-level-rx-links[rx-array-carrier = current()/../name]/rx-array-carrier)]/configurable-tdd-pattern-supported = 'false')";
3389 if-feature mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED;
3391 path "/user-plane-configuration/configurable-tdd-patterns/tdd-pattern-id";
3394 "This parameter creates reference to configuration for TDD pattern applicable for particular rx-array-carrier.
3395 The leaf may exist under rx-array-carrier only in case O-RU supports feature 'CONFIGURABLE-TDD-PATTERN-SUPPORTED'
3396 AND all low-level-rx-endpoints linked to this rx-array-carrier have configurable-tdd-pattern-supported = 'true'";
3404 "Structure describing TX array parameters";
3415 "Min gain of RF path linked with array element (maximum over elements of array) or array layers";
3426 "Max gain of RF path linked with array element (minimum over elements of array) or array layers";
3429 leaf independent-power-budget {
3433 "If true then every element of array has own, power budget independent from power budget of other elements.
3434 Else all elements of array that are at same row and column and have same polarisation share power budget";
3439 "List of capabilities related to this tx-array";
3440 uses mcap:support-for-dl;
3447 description "Structure describing RX array parameters";
3450 container gain-correction-range {
3457 description "Array gain correction factor - maximum allowed value";
3465 description "Array gain correction factor - minimum allowed value";
3469 "Array gain correction factor";
3474 "List of capabilities related to this rx-array";
3475 uses mcap:support-for-ul;
3482 description "Structure describing relations between array elements";
3488 "Relation entity. Used as a key for list of relations.";
3495 "Defines name for first array";
3501 "Defines name for second array";
3504 key "relation-type";
3506 "Defines relation type and pairs for array elements for given arrays";
3508 leaf relation-type {
3511 description "SHARED";
3514 description "COALOCATED";
3517 description "Type of relation between array elements";
3520 key "element-array1";
3522 "defines related array elements";
3524 leaf element-array1 {
3528 "Tells about id of element from array1";
3530 leaf element-array2 {
3534 "Tells about id of element from array2";
3540 container eaxc-id-group-configuration {
3541 if-feature mcap:EAXC-ID-GROUP-SUPPORTED;
3543 "This is the container for eAxC ID group configuration.";
3544 leaf max-num-tx-eaxc-id-groups {
3546 path "/mcap:module-capability/mcap:ru-capabilities/mcap:eaxcid-grouping-capabilities/mcap:max-num-tx-eaxc-id-groups";
3547 require-instance false;
3549 description "eaxc-id-group-configuration";
3551 leaf max-num-tx-eaxc-ids-per-group {
3553 path "/mcap:module-capability/mcap:ru-capabilities/mcap:eaxcid-grouping-capabilities/mcap:max-num-tx-eaxc-ids-per-group";
3554 require-instance false;
3556 description "max-num-tx-eaxc-ids-per-group";
3558 leaf max-num-rx-eaxc-id-groups {
3560 path "/mcap:module-capability/mcap:ru-capabilities/mcap:eaxcid-grouping-capabilities/mcap:max-num-rx-eaxc-id-groups";
3561 require-instance false;
3563 description "max-num-rx-eaxc-id-groups";
3565 leaf max-num-rx-eaxc-ids-per-group {
3567 path "/mcap:module-capability/mcap:ru-capabilities/mcap:eaxcid-grouping-capabilities/mcap:max-num-rx-eaxc-ids-per-group";
3568 require-instance false;
3570 description "max-num-rx-eaxc-ids-per-group";
3573 list tx-eaxc-id-group {
3574 must "count(../tx-eaxc-id-group) <= ../max-num-tx-eaxc-id-groups" {
3575 error-message "too many tx-eaxcid-id groups";
3577 key "representative-tx-eaxc-id";
3579 "This is a list of the groups of the eAxC IDs assigned to low-level-tx-endpoints.
3580 Each group is a union of the 'member-tx-eaxc-id's and a 'representative-tx-eaxc-id'.
3581 The low-level-tx-endpoint associated to 'representative-tx-eaxc-id' is able to
3582 process the DL C-plane information for all the low-level-tx-endpoints associated
3583 to 'member-tx-eaxc-id's.
3585 Take Note: This list should only contain eAxC IDs assigned to a tx-endpoint.";
3588 leaf representative-tx-eaxc-id {
3591 "This parameter contains eAxC_ID that populates content of C-Plane section
3592 extension 10 to eAxC_IDs configured in the group as 'member-tx-eaxc-id'(s).";
3594 leaf-list member-tx-eaxc-id {
3596 must "count(../member-tx-eaxc-id) <= ../../max-num-tx-eaxc-ids-per-group" {
3597 error-message "too many tx-eaxcid-id members";
3599 must "current()!=../representative-tx-eaxc-id" {
3600 error-message "the representative eaxcid does not need to be a list member";
3604 "This is a list of member eAxC IDs, which together with the representative-tx-eaxc-id,
3605 are assigned to low-level-tx-endpoints in the group.
3606 This list is defined as 'ordered-by user', because the order of the eaxc-id list should be maintained,
3607 and the parameters in the SE10 are applied to the eaxc-ids based on the order of eaxc-ids in the list
3608 when the section extension conveys unique parameters (beamId/ueId) per eaxc-id.";
3612 list rx-eaxc-id-group {
3613 must "count(../rx-eaxc-id-group) <= ../max-num-rx-eaxc-id-groups" {
3614 error-message "too many rx-eaxcid-id groups";
3616 key "representative-rx-eaxc-id";
3618 "This is a list of the groups of the eAxC IDs assigned to low-level-rx-endpoints.
3619 Each group is a union of 'member-rx-eaxc-id's and a 'representative-rx-eaxc-id'.
3620 The low-level-rx-endpoint associated to 'representative-rx-eaxc-id' is able to
3621 process the UL C-plane information for all the low-level-rx-endpoints associated
3622 to 'member-rx-eaxc-id's.
3624 Take Note: This list should only contain eAxC IDs assigned to a rx-endpoint.";
3626 leaf representative-rx-eaxc-id {
3629 "This parameter contains eAxC_ID that populates content of C-Plane section
3630 extension 10 to eAxC_IDs configured in the group as 'member-rx-eaxc-id'(s).";
3633 leaf-list member-rx-eaxc-id {
3635 must "count(../member-rx-eaxc-id) <= ../../max-num-rx-eaxc-ids-per-group" {
3636 error-message "too many rx-eaxcid-id members";
3638 must "current()!=../representative-rx-eaxc-id" {
3639 error-message "the representative eaxcid does not need to be a list member";
3643 "This is a list of member eAxC IDs assigned to low-level-rx-endpoints in the group.
3644 This list is defined as 'ordered-by user', because the order of the eaxc-id list should be maintained,
3645 and the parameters in the SE10 are applied to the eaxc-ids based on the order of eaxc-ids in the list
3646 when the section extension conveys unique parameters (beamId/ueId) per eaxc-id.";
3651 list static-prach-configurations {
3652 if-feature mcap:PRACH-STATIC-CONFIGURATION-SUPPORTED;
3653 key static-prach-config-id;
3655 "List of static PRACH configurations. An O-RU shall reject any configuration
3656 modification which exceed the maximum permitted configurations supported by
3659 leaf static-prach-config-id {
3662 "Supplementary parameter acting as key in list of static PRACH configurations.";
3665 uses static-prach-configuration;
3668 grouping static-prach-configuration {
3670 "Set of parameters related to static PRACH configuration";
3672 leaf pattern-period {
3678 "Period after which static PRACH patterns are repeated. Unit: number of frames.";
3681 leaf guard-tone-low-re {
3685 "Number of REs occupied by the low guard tones.";
3692 "Number of contiguous PRBs per data section description";
3695 leaf guard-tone-high-re {
3699 "Number of REs occupied by the high guard tones.";
3702 leaf sequence-duration {
3709 "Duration of single sequence of the PRACH. Sequence may be considered as 'single PRACH symbol'";
3712 list prach-patterns {
3713 key prach-pattern-id;
3716 "Provides a PRACH pattern. Each record in the list represents a single PRACH occasion. Number of list entries cannot exceed max-prach-patterns";
3718 leaf prach-pattern-id {
3722 "Supplementary parameter acting as key for prach-pattern list.";
3725 leaf number-of-repetitions {
3731 "This parameter defines number of PRACH repetitions in PRACH occasion,
3732 to which the section control is applicable.";
3735 leaf number-of-occasions {
3739 "This parameter informs how many consecutive PRACH occasions is described by the PRACH pattern.";
3746 "Offset between the start of lowest-frequency RE of lowest-frequency PRB
3747 and the start of lowest-frequency RE belonging to the PRACH occasion.
3748 The re-offset is configured as number of PRACH REs.";
3751 list occasion-parameters {
3755 "This is list of cp-lengths, gp-lengths and beam-ids applicable
3756 per each PRACH occasion in PRACH pattern.
3757 Note: the number of records in this list MUST be equal
3758 to value of parameter number-of-occasions.";
3764 "Supplementary parameter acting as key in 'occasion-parameters' list";
3772 "Cyclic prefix length. See CUS-plane specification for detailed description.";
3779 "Guard period length.";
3784 range "min .. 32767";
3788 "This parameter defines the beam pattern to be applied to the U-Plane data.
3789 beamId = 0 means no beamforming operation will be performed.";
3799 "This parameter is an index inside the pattern-length, such that
3800 PRACH occasion is happening for SFN which fulfills following equation:
3801 [SFN mod pattern-length = frame-id]";
3808 "Identifier of sub-frame of the PRACH occasion. Value is interpreted in the same way
3809 as subframeId field in a section description of a C-Plane message.";
3817 "This parameter defines the time-offset from the start of the sub-frame
3818 to the start of the first Cyclic Prefix of PRACH pattern";
3823 grouping static-srs-configuration {
3825 "Set of parameters related to static PRACH configuration";
3827 leaf pattern-period {
3833 "Period after which static SRS patterns are repeated. Unit: number of frames.";
3840 "Provides a SRS pattern. Each record in the list represents a single PRACH occasion. Number of list entries cannot exceed max-srs-patterns.";
3842 leaf srs-pattern-id {
3846 "Supplementary parameter acting as key for srs-pattern list.";
3853 "Identifier of sub-frame of the Raw SRS occasion. Value is interpreted in the same way
3854 as subframeId field in a section description of a C-Plane message.";
3861 "Identifier of slot of the Raw SRS occasion. Value is interpreted in the same way
3862 as slotId field in a section description of a C-Plane message.";
3865 leaf start-symbol-id {
3869 "Identifier of first symbol of the Raw SRS occasion. Value is interpreted in the same way
3870 as startSymbolId field in a section description of a C-Plane message.";
3875 range "min .. 32767";
3879 "This parameter defines the beam pattern to be applied to the U-Plane data.
3880 beamId = 0 means no beamforming operation will be performed.";
3887 "This parameter defines number of consecutive symbols covered by specific srs-pattern.
3888 Single srs-pattern may address at least one symbol. However, possible optimisations
3889 could allow for several (up to 14) symbols.";
3898 "Identifier of first PRB of the Raw SRS occasion. Value is interpreted in the same way
3899 as startPrbc field in a section description of a C-Plane message.";
3906 "Number of PRBs of the Raw SRS occasion. Value is interpreted in the same way
3907 as numPrbc field in a section description of a C-Plane message.";
3912 grouping configurable-tdd-pattern {
3914 "Set of parameters related to configurable TDD pattern.
3915 Note: configurable-tdd-pattern shall not be used in case the usage would collide with
3916 deprecated 'lte-tdd-pattern'.";
3918 list switching-points {
3919 key switching-point-id;
3921 "List of switching points within frame, related to configurable TDD pattern.
3922 An O-RU shall reject any configuration modification which exceeds the maximum
3923 number of switching-points supported by the O-RU";
3925 leaf switching-point-id {
3928 "Supplementary parameter acting as key for switching-points list.";
3934 description "Uplink";
3937 description "Downlink";
3940 description "Guard period";
3945 "Parameter provides information regarding desired signal direction at the moment switching point occurs.";
3952 "Offset from DL air frame boundary transmitted at RF connector to the point in time that is characteristic to the operation on RF switches. Unit is 1/1.2288e9 s.";
3957 list static-srs-configurations {
3958 if-feature mcap:SRS-STATIC-CONFIGURATION-SUPPORTED;
3959 key static-srs-config-id;
3961 "List of static SRS configurations";
3963 leaf static-srs-config-id {
3966 "Supplementary parameter acting as key in the list of static SRS configurations.";
3969 uses static-srs-configuration;
3972 list configurable-tdd-patterns {
3973 if-feature mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED;
3976 "List of configured TDD patterns";
3978 leaf tdd-pattern-id {
3981 "Supplementary parameter acting as key in the list of configured TDD patterns.";
3984 uses configurable-tdd-pattern;
3988 grouping tx-array-notification-group {
3990 "Grouping for tx-array for notification";
3992 list tx-array-carriers{
3994 description "notification of state change for tx-array-carriers";
3998 path "/user-plane-configuration/tx-array-carriers/name";
4001 "name of tx-array-carriers is notified at state change";
4005 path "/user-plane-configuration/tx-array-carriers/state";
4008 "state of tx-array-carriers is notified at state change";
4013 grouping rx-array-notification-group {
4015 "Grouping for rx-array for notification";
4017 list rx-array-carriers{
4020 "Notification used to inform about state change of rx-array-carriers";
4023 path "/user-plane-configuration/rx-array-carriers/name";
4026 "name of rx-array-carriers is notified at state change";
4030 path "/user-plane-configuration/rx-array-carriers/state";
4033 "state of rx-array-carriers is notified at state change";
4038 // top level container
4039 container user-plane-configuration {
4040 description "top level container for user plane configuration";
4042 uses uplane-conf-group;
4043 uses general-config;
4046 //notification statement
4047 notification tx-array-carriers-state-change {
4049 "Notification used to inform about state change of tx-array-carriers";
4050 uses tx-array-notification-group;
4052 notification rx-array-carriers-state-change {
4054 "Notification used to inform about state change of tx-array-carriers";
4056 uses rx-array-notification-group;