1 module o-ran-delay-management {
3 namespace "urn:o-ran:delay:1.0";
6 organization "O-RAN Alliance";
12 "This module covers off aspects of O-DU to O-RU delay management,
13 including configuration data related to O-RU transmission and reception
16 Copyright 2020 the O-RAN Alliance.
18 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS'
19 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
22 LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
23 CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
24 SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
25 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
26 CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
27 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
28 POSSIBILITY OF SUCH DAMAGE.
30 Redistribution and use in source and binary forms, with or without
31 modification, are permitted provided that the following conditions are met:
33 * Redistributions of source code must retain the above copyright notice,
34 this list of conditions and the above disclaimer.
35 * Redistributions in binary form must reproduce the above copyright notice,
36 this list of conditions and the above disclaimer in the documentation
37 and/or other materials provided with the distribution.
38 * Neither the Members of the O-RAN Alliance nor the names of its
39 contributors may be used to endorse or promote products derived from
40 this software without specific prior written permission.";
42 revision "2022-08-15" {
46 1) introducing new feature for ACK NACK feedback.";
48 reference "ORAN-WG4.M.0-v10.00";
51 revision "2021-12-01" {
55 1) typographical corrections in descriptions.
56 2) add new schema node beam-context-gap-period.";
58 reference "ORAN-WG4.M.0-v08.00";
61 revision "2020-08-10" {
65 1) introduction of new t1a-max-cp-dl leaf to enable decoupled timing between C- and U-Plane";
67 reference "ORAN-WG4.M.0-v04.00";
70 revision "2019-07-03" {
74 1) fixing descriptions of ta3-min and ta3-max.
75 2) introducing grouping/uses to enable model re-use by WG5";
77 reference "ORAN-WG4.M.0-v01.00";
80 revision "2019-02-04" {
84 1) imported model from xRAN
85 2) changed namespace and reference from xran to o-ran";
87 reference "ORAN-WG4.M.0-v01.00";
91 feature ADAPTIVE-RU-PROFILE {
93 "This feature indicates that the O-RU supports adaptive O-RU delay profile
94 based on information provided by the NETCONF client.";
99 range "200 | 1400 | 3000 | 5000 | 10000 | 15000 | 20000 | 25000 |
100 30000 | 40000 | 50000 | 60000 | 70000 | 80000 | 90000 | 100000
105 "transmission bandwidth configuration in units of kHz -
106 covering NBIoT through to New Radio - see 38.104";
109 grouping bandwidth-configuration {
111 "Grouping for bandwidth and SCS configuration";
116 "transmission bandwidth configuration in units of kHz -
117 covering NBIoT through to New Radio - see 38.104";
119 leaf subcarrier-spacing {
121 range "0 .. 240000 ";
124 description "sub-carrier spacing in Hz";
130 "configuration of t2a for uplink";
137 "the minimum O-RU data processing delay between receiving IQ data
138 message over the fronthaul interface and transmitting
139 the corresponding first IQ sample at the antenna";
146 "the earliest allowable time when a data packet is received before
147 the corresponding first IQ sample is transmitted at the antenna";
153 "Grouping for t2a CP for downlink";
160 "the minimum O-RU data processing delay between receiving downlink
161 real time control plane message over the fronthaul interface and
162 transmitting the corresponding first IQ sample at the antenna";
169 "the earliest allowable time when a downlink real time control message
170 is received before the corresponding first IQ sample is transmitted at
177 "Grouping for ta3 configuration";
184 "the minimum O-RU data processing delay between receiving an IQ sample
185 at the antenna and transmitting the first data sample over the
186 fronthaul interface";
193 "the maximum O-RU data processing delay between receiving an IQ sample
194 at the antenna and transmitting the last data sample over the
195 fronthaul interface";
201 "Grouping for t2a CP uplink";
208 "the minimum O-RU data processing delay between receiving real time
209 up-link control plane message over the fronthaul interface and
210 receiving the first IQ sample at the antenna";
217 "the earliest allowable time when a real time up-link control message
218 is received before the corresponding first IQ sample is received at
225 "Grouping for ta3-ack configuration";
230 "the minimum delay between the DL/UL air reference point (tDL=0 or tUL=0) of symbol M
231 and the time O-RU sends section type 8 (ACK/NACK feedback) to O-DU.
232 This value can be negative, which indicates it is in advance of the air reference point.
233 This leaf only exists if section extension 22 (ACK/NACK request) and section type 8 (ACK/NACK feedback)
234 are supported by at least one endpoint.";
241 "the maximum delay between the DL/UL air reference point (tDL=0 or tUL=0) of symbol M
242 and the time O-RU sends section type 8 (ACK/NACK feedback) to O-DU.
243 This value can be negative, which indicates it is in advance of the air reference point.
244 This leaf only exists if section extension 22 (ACK/NACK request) and section type 8 (ACK/NACK feedback)
245 are supported by at least one endpoint.";
249 grouping ru-delay-profile {
251 "Grouping for RU delay profile";
261 "the time difference (advance) between the reception window for
262 downlink real time Control messages and reception window for the
263 corresponding IQ data messages.";
271 grouping o-du-delay-profile {
273 "Grouping for O-DU delay profile";
279 "the earliest possible time which the O-DU can support transmitting
280 an IQ data message prior to transmission of the corresponding IQ
281 samples at the antenna";
287 "The maximum amount of time which the O-DU requires to transmit
288 all downlink user plane IQ data message for a symbol";
294 "the latest possible time which the O-DU can support receiving the
295 last uplink user plane IQ data message for a symbol.";
301 "The maximum time difference the O-DU can support between
302 receiving the first user plane IQ data message for a symbol and
303 receiving the last user plane IQ data message for the same symbol";
309 "The earliest possible time which the O-DU can support transmitting the
310 downlink real time control message prior to transmission of the
311 corresponding IQ samples at the antenna.";
323 "the minimum measured delay between DU port-ID and O-RU port-ID";
325 // additional leaf added by Samsung
330 "the maximum measured delay between CU port-ID and O-RU port-ID";
342 "the minimum measured delay between O-RU port-ID and CU port-ID";
344 // additional leaf added by Samsung
349 "the maximum measured delay between O-RU port-ID and CU port-ID";
353 grouping delay-management-group {
354 description "a delay management grouping";
355 list bandwidth-scs-delay-state {
356 key "bandwidth subcarrier-spacing";
358 "Array of structures containing sets of parameters for delay management.";
360 uses bandwidth-configuration;
362 container ru-delay-profile {
364 description "container for O-RU delay parameters";
366 uses ru-delay-profile;
370 container adaptive-delay-configuration {
371 if-feature ADAPTIVE-RU-PROFILE;
372 description "container for adaptive delay parameters";
373 list bandwidth-scs-delay-state {
374 key "bandwidth subcarrier-spacing";
376 "Array of structures containing sets of parameters for delay management.";
378 uses bandwidth-configuration;
380 container o-du-delay-profile {
382 "O-DU provided delay profile for adaptive delay configuration";
384 uses o-du-delay-profile;
388 container transport-delay {
390 "O-DU provided transport-delay parameters";
396 leaf beam-context-gap-period {
400 "Time gap between the end of reception window of the C-Plane message(Msg-A) with new beam weights for a given beamId and end of the reception window
401 of the C-Plane message(Msg-B) that cites the same beamId without weights in the new context.
402 Note: Value of '0' indicates that the end of the Msg-A and Msg-B reception windows are perfectly aligned, which should allow Msg-B to use the new
403 beamforming weights with a '0' microsecond beam-context-gap-period. Value of '65535' implies infinite gap, which means a beamId may not be reused
404 at all in a different context (applicable only to weight-based dynamic beamforming). If O-DU chooses not to interpret/honor this value, behaviour
405 of O-RU is unpredictable if a beamId has new weights loaded in one context and is reused in a different context. Please refer the CUS-Plane spec
406 Section 'Weight-based dynamic beamforming' for detailed description";
409 container delay-management {
410 description "top-level tree covering off O-DU to O-RU delay management";
412 uses delay-management-group;