Merge remote-tracking branch 'origin/refactor-ulsch' into integration_2025_w33 (!3521)
Refactor ULSCH scheduler towards more TDD pattern flexibility Refactors ULSCH scheduler, notably to support "UL-heavy" TDD patterns, e.g., DSUUU. Also allows to run TDD pattern2 with UL slots, which was a limitation in the previous code.
This commit is contained in:
+10
-5
@@ -49,9 +49,11 @@ The value of `pdcch_cl_adjust` is clamped to range <0,1>, the increment value is
|
||||
the decrement value is 0.01. These values are selected to ensure PDCCH success rate is high.
|
||||
See Examples below for futher explaination.
|
||||
|
||||
The possible values of aggregation level on UE SS can be configured via `uess_agg_levels` configuration
|
||||
option. By default the gNB uses only aggregation level 2 which translates to `uess_agg_levels` set to
|
||||
`[0, 1, 0, 0, 0]`. For example, to enable aggregation level 2 and 4 set `uess_agg_levels` to `[0, 1, 1, 0, 0]`.
|
||||
The possible values of aggregation level on UE SS can be configured via
|
||||
`uess_agg_levels` configuration option. By default the gNB uses two candidates
|
||||
in aggregation level 2 which translates to `uess_agg_levels` set to `[0, 2, 0,
|
||||
0, 0]`. For example, to enable one candidate on aggregation levels 2 and 4 set
|
||||
`uess_agg_levels` to `[0, 1, 1, 0, 0]`.
|
||||
|
||||
### Examples:
|
||||
#### Example 1:
|
||||
@@ -79,8 +81,8 @@ Example:
|
||||
UE RNTI 2460 CU-UE-ID 2 in-sync PH 28 dB PCMAX 24 dBm, average RSRP -74 (8 meas)
|
||||
UE 2460: CQI 15, RI 2, PMI (14,1)
|
||||
UE 2460: UL-RI 2 TPMI 0
|
||||
UE 2460: dlsch_rounds 32917/5113/1504/560, dlsch_errors 211, pucch0_DTX 1385, BLER 0.19557 MCS (1) 23
|
||||
UE 2460: ulsch_rounds 3756/353/182/179, ulsch_errors 170, ulsch_DTX 285, BLER 0.33021 MCS (1) 27 (Qm 8 dB) NPRB 5 SNR 31.0 dB
|
||||
UE 2460: dlsch_rounds 32917/5113/1504/560, dlsch_errors 211, pucch0_DTX 1385, BLER 0.19557 MCS (1) 23 CCE fail 3
|
||||
UE 2460: ulsch_rounds 3756/353/182/179, ulsch_errors 170, ulsch_DTX 285, BLER 0.33021 MCS (1) 27 (Qm 8 dB) NPRB 5 SNR 31.0 dB CCE fail 0
|
||||
UE 2460: MAC: TX 1530943191 RX 194148 bytes
|
||||
UE 2460: LCID 1: TX 651 RX 3031 bytes
|
||||
UE 2460: LCID 2: TX 0 RX 0 bytes
|
||||
@@ -159,6 +161,9 @@ The fourth and fifth line show HARQ-related information:
|
||||
should be close to the target in the gNB configuration file,
|
||||
`pusch_TargetSNRx10`, which should be around 10 times the value shown in the
|
||||
log
|
||||
* Both ULSCH/DLSCH `CCE fail`: lists the number of failed CCE attempts. If this
|
||||
number gets high, it signifies that the scheduler tried to scheduled this UE,
|
||||
but could not allocate the DCI.
|
||||
|
||||
In the last lines:
|
||||
* `MAC` shows the amount of MAC PDU bytes scheduled in transmit (`TX`,
|
||||
|
||||
+3
-2
@@ -95,8 +95,9 @@ can proceed as follows:
|
||||
- in `vnf.conf`
|
||||
* modify `MACRLCs` section to configure south-bound nFAPI transport
|
||||
* delete `L1s`, `RUs`, and radio-specific sections.
|
||||
* in `gNBs` section, increase the `ra_ResponseWindow` by one to extend the RA
|
||||
window: this is necessary because the PNF triggers the scheduler in the VNF
|
||||
* in `gNBs` section, select a sufficiently large `ra_ResponseWindow` if a UE
|
||||
does not connect with a message that the response window timed out:
|
||||
this is necessary because the PNF triggers the scheduler in the VNF
|
||||
in advance, which might make the RA window more likely to run out
|
||||
- copy `monolithic.conf`, which will be your PNF file (`pnf.conf`)
|
||||
- in `pnf.conf`
|
||||
|
||||
@@ -82,9 +82,6 @@ gNBs =
|
||||
#powerRampingStep
|
||||
# 0=dB0,1=dB2,2=dB4,3=dB6
|
||||
powerRampingStep = 1;
|
||||
#ra_ReponseWindow
|
||||
#1,2,4,8,10,20,40,80
|
||||
ra_ResponseWindow = 5;
|
||||
#ssb_perRACH_OccasionAndCB_PreamblesPerSSB_PR
|
||||
#1=oneeighth,2=onefourth,3=half,4=one,5=two,6=four,7=eight,8=sixteen
|
||||
ssb_perRACH_OccasionAndCB_PreamblesPerSSB_PR = 4;
|
||||
|
||||
Reference in New Issue
Block a user