04
4
◎
Day objective — push DL/UL throughput up without breaking latency, BLER or VoNR quality. Every feature below is a real SVR25B FGR; params come from the SVR25A DU Command Reference.
4.1
Throughput Optimization (LTE & NR)
Maximise the bits — the scheduling / MIMO / HARQ stack, Carrier Aggregation and DSS, higher-order modulation, and the KPIs (DL/UL throughput, PRB, MCS, MIMO Rank, CQI) that measure it.
★
- LTE throughput — the 5-layer ladder (GTP→PDCP→RLC→MAC→IP) · CA/MIMO/DRX · ladder localizer
- 5G NSA throughput — split-bearer anatomy (Fam 5126) · X2 tax · split visualizer
- 5G SA throughput — the 4-band PRB playbook · MCS/CQI/RI · FGR-RC/RS features · decision engine
The throughput stack — scheduler → MIMO → modulation → HARQSVR25B
each stage multiplies the bitsThroughput ≈ bandwidth × layers × modulation × coding × (1 − BLER).
MIMO features (SVR25B) — layers & beamforming
SU / MU / Massive MIMO
| FGR | Feature | What it adds |
|---|---|---|
FGR-RC0202 | DL SU-MIMO for NR | Multiple layers to one UE (rank up) |
FGR-RC0203 | DL MU-MIMO for NR | Pair multiple UEs on the same PRBs |
FGR-RC0204 | DL SRS-based SU-MIMO | SRS-driven precoding for SU-MIMO |
FGR-RC1000 | TDD DL Massive MIMO | Beamformed high-order MIMO (MMU) |
FGR-RC1041 | Channel Prediction for Massive MIMO | Predict channel for faster beam tracking |
FGR-RS0252 / RS0253 | UL SU-MIMO / UL MU-MIMO | Uplink spatial multiplexing |
FGR-RS1101 | UL Receive Beamforming (Massive MIMO) | Array gain on the uplink |
Scheduling, Carrier Aggregation & DSS (SVR25B)
Capacity features
| FGR | Feature | What it adds |
|---|---|---|
FGR-RC0100 | Carrier Aggregation (call procedure) | Add SCell(s) to widen the pipe |
FGR-RS0620 | Scheduling for CA | Cross-carrier scheduling of the aggregated cells |
FGR-RS0622 | Scheduling for IP-throughput enhancement | dl-ip-throughput-enhancement for burst TCP |
FGR-RS0703 | QoS Scheduling | Per-bearer GBR / non-GBR strategies |
FGR-RS7003 | DL prescheduling | Cut first-packet latency for bursty traffic |
FGR-RS1201 / RS1202 | LTE-NR DSS (frame / slot-level) | Share the carrier with LTE dynamically |
Throughput golden parameters (SVR25A DU Command Reference)
DU-side throughput params
| Parameter | Controls | Tune toward |
|---|---|---|
| mcs-table-config (256QAM) | Highest modulation order (64→256QAM) | 256QAM on for good-SINR cells |
| mu-mimo-config / ul-mu-mimo-config | MU-MIMO pairing & layers | Enable where UE density supports pairing |
| max rank (rank1…rank4) | Max MIMO layers per UE | Raise where RI reports support it |
| scell-config (CA) | SCell add / activation policy | Aggressive add for high-demand UEs |
| dss-mode | LTE-NR DSS operating mode | Balance NR vs LTE share (Day-5 DSS) |
| dl-ip-throughput-enhancement | Burst-TCP scheduling boost | On for eMBB IP throughput |
≡
What to read — DL/UL throughput, DL/UL PRB utilization, MCS distribution, MIMO Rank (RI) and CQI. Low throughput at high PRB → coverage/MCS-limited (raise SINR, check 256QAM eligibility); low throughput at low PRB → scheduler/CA not engaging (check SCell add, prescheduling).
4.2
Integrity Optimization
Protect the quality of the bits — latency, residual BLER, packet loss and VoNR voice quality, the HARQ/RLC/PDCP + DRX stack, and the SINR–CQI cascade that drives them.
The SINR → CQI → MCS → BLER cascadeintegrity chain
SINR sets the ceilingWrong CQI→MCS mapping → BLER spikes → HARQ retx → latency & lower throughput.
Integrity features (SVR25B)
Reliability / latency / voice
| FGR | Feature | Protects |
|---|---|---|
FGR-RS0501 | HARQ | Reliability — retransmit failed TBs |
FGR-CC6201 | NR Extended DRX (eDRX) | Battery vs latency in idle/inactive |
FGR-RS0301 | UL Power Control | UL SINR → UL BLER / coverage |
FGR-RS0401 | Timing Advance Control | UL orthogonality (avoids inter-symbol) |
FGR-RS1306 | UL VoNR Codec-adaptation scheduling | VoNR voice quality under load |
FGR-BC7002 | Max Rate Control per QCI/5QI/Slice | Shape rate per QoS class |
Integrity golden parameters & the DRX latency trade-off
DRX / HARQ / VoNR params (SVR25A DU)
| Parameter | Controls | Trade-off |
|---|---|---|
| drx-long-cycle | Sleep cycle length | Longer = battery↑ but latency↑ |
| drx-inactivity-timer | Stay-awake after activity | Longer = latency↓ but battery↓ |
| harq-config | Max HARQ retransmissions | More = reliability↑ but latency↑ |
| bler-target (link adaptation) | 1st-Tx BLER operating point | Lower = safer MCS but throughput↓ |
| TDD-power / UL power control | UL received power target | Higher = SINR↑ but interference↑ |
!
The core integrity tension — HARQ retransmissions and DRX both trade latency against reliability/battery. VoNR is the canary: rising jitter or packet loss on the QoS-1 bearer usually means DRX is too aggressive or BLER target is set too high — tune DRX-inactivity up and re-check MOS before touching the scheduler.
LAB
Hands-on Lab 4 — Throughput Trial & VoNR Quality
Run a throughput trial across scheduling / CA / MIMO, then tune a latency / VoNR quality case — and confirm one didn't cost the other.
Hands-on Lab 4
Scheduling / CA / MIMO trial · latency & VoNR tuning
⚡- 1Baseline throughput, PRB utilization, MCS, RI and CQI from counters
- 2Throughput trial — enable 256QAM (
mcs-table-config) / add SCell (CA) / raise MU-MIMO pairing - 3Latency / VoNR case — tune
drx-inactivity-timer&harq-config; watch VoNR MOS - 4Verify throughput gain with no BLER / VoNR regression
256QAMCA-SCellMU-MIMODRXVoNR
Deliverable — a throughput improvement proven safe against latency, BLER and voice-quality KPIs.