Unit of DRB.RlcDelayUl #1171
Replies: 5 comments
-
This is a bit urgent—any insights or suggestions at your earliest convenience would be greatly appreciated. Do the DRB.RlcDelayUl values require scaling by 0.1, or are they already in milliseconds as reported? |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hi, -Measurements Data: |
Beta Was this translation helpful? Give feedback.
-
Just to add a bit more context about the behavior: As mentioned earlier, I also tested using ping (one packet per second) with a packet size of 577 bytes. The observed RTT was around 35 ms, but the RLC uplink delay was around 8000 ms, which seems contradictory. Interestingly, when I reduced the packet size slightly to 566 bytes (i.e., 577 - 1), the RLC uplink delay dropped significantly to just 1 ms. |
Beta Was this translation helpful? Give feedback.
-
hi @ersuneetsingh, what xApp do you use? Can I have your script to run xApp with these metrics? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I’m using ORAN-SC RIC to monitor the RAN, and I generate UDP traffic using iperf to observe uplink RLC delay (RlcDelayUl) at 1-second intervals. However, I'm noticing that the reported RlcDelayUl values range between 700–1200 ms, which seems unusually high — I was expecting something in the range of 10–50 ms.
I also observed that the unit for DRB.RlcSduDelayDl is 0.1 ms, whereas for DRB.RlcDelayUl it's labeled simply as ms. So I’m unsure: do I need to multiply the RlcDelayUl values by 0.1 as well? Or are the values already in milliseconds?
If the units are correct as-is, I’m not sure what could be causing such high RLC delay. Could anyone provide insights or suggestions?
Beta Was this translation helpful? Give feedback.
All reactions