CafeTeleRadio Optimization SRPO-600 Enroll now ↗
‹ Day 1 · Hardware Portfolio Course / Day 1 / 1.1 Samsung RAN Hardware / Baseband
CDU
BB
1.1 · Baseband

Samsung Baseband — CDU, Cards, Ports & Configuration

The Cabinet DU (CDU) is where the gNB/eNB thinks — a card cage of Main, Channel and Unified cards that run the digital baseband, drive the radios over CPRI/eCPRI, host the DU side of the CU/DU split, and configure every cell. Two build variants: the Main-card build (GMA1 + Channel cards) and the Unified-card build (GUC1/GUC2 + GCC1/BCA1) — every value below verbatim from the Samsung CDU50 / CDU51 Product Specifications.

2G·4G·5GMulti-RAT baseband
12CPRI/eCPRI ports per channel card
25GBackhaul (×4 on GMA1)
1210 WMax (full CDU50 config)
GNSS + IEEE1588v2 PTP
Where the baseband sits — the CU / DU functional split

In 5G NR SA the gNB is split into CU (RRC, PDCP) and DU (High-PHY, MAC, RLC). The CDU runs the DU and drives the radios; the CU-CP/CU-UP run on the CU — increasingly virtualized on COTS servers under vRAN 3.0. F1 joins DU↔CU, E1 joins CU-CP↔CU-UP, NG joins the gNB to the 5GC.

RU → CDU (DU baseband) → CU → 5GCCDU = DU
F1NG
Radios
RRU / MMU
CPRI ↑
CDU · DU
High-PHY · MAC · RLC
gnb-du-function
CU-CP / CU-UP
RRC · PDCP · SDAP
vRAN 3.0 (virtualized)
E1
CU-CP ↔ CU-UP
Core
5GC / EPC
F1 (DU↔CU)The CDU is the purpose-built DU; vRAN 3.0 can also run a vDU/vCU on servers.
CDU50 system specification — the full sheet
CDU50 Product Specification (Ver 5.0)
ItemSpecification
Technology5G · LTE · GSM (multi-RAT)
Backhaul interface1G/10G/25G × 4 ports (GMA1) · × 2 ports (GUC1)
Fronthaul interface2.5G/5G/10G/25G × 12 (GCB4) · × 9 (GUC1) · 2.5G/5G ×6 (BCA1)
SynchronizationGNSS (GPS · GLONASS · Galileo) / IEEE1588v2 PTP
Input voltage−48 V DC (−40 to −57 V DC)
Power consumptionFull config (GMA1 + 3× GCB4): Typ 1017 W (25 °C, 50 %) · Max 1210 W
Dimensions (W×D×H)434 × 385 × 88 mm (2U, excl. ear mount)
Weight17 kg or less (full config, excl. optic modules)
CoolingFan cooling (FANM)
Operating temperature0 °C to +50 °C (to +55 °C at CDU inlet)
Operating humidity5–95 % RH, non-condensing (≤ 30 g/m³)
Altitude−60 to 1800 m
Acoustic noise≤ 60 dBA @ 25 °C (1.0 m)
Ingress protectionIEC 60529 · IP20 (indoor)
EarthquakeTelcordia GR-63-CORE Zone 4 · EN 300 019-1-3
Chassis anatomy — UCBS card cage, power & cooling

The CDU is a UCBS card cage: a UCDB backplane the cards plug into, a PDPM power distribution module fed by −48 V DC, and a FANM fan module (with an air filter) that cools the stack. The Main card and the Channel cards slot into the backplane.

UCBS chassis — power → backplane → cards, fan-cooled2U card cage
−48V
PDPM
Power module
−48 V DC in
UCDB
Backplane
HSI fabric
FANM
Fan + air filter
Slot · Main
GMA1 / GUC1
Slot · Channel
GCB4 / LCC2 / BCA1
Slot · Channel
×2 / ×3
CPRI L0–L11
to radios
data path power/coolingUCBS = the chassis · UCDB = backplane · PDPM = power · FANM = fan.
Per-card specification — size, power & ports
CDU card specifications (356 × 370 × 21 mm blades)
CardClassWeightFronthaulBackhaulInter-card / clock
GMA1Main1/10/25G × 4 (BH0–3, QSFP+)HSI · SYNC · GNSS
GCB4Channel · NR2.8 kgCPRI 12 ports (L0–L11, SFP+/SFP28)HSI 3 ports (QSFP+)
GUC1Unified<3.1 kgCPRI 9 ports (L0–L8)1/10G Eth (BH0/1, SFP+/SFP28)Clock: GPS
LCC2Channel · LTE2.5 kgCPRI 12 ports (L0–L11)
BCA1Channel · BTS2.5 kgeCPRI 12 ports (L0–L11, SFP+)

All cards: 356 × 370 × 21 mm blades, −48 V DC. Fronthaul ports run 2.5G/5G/10G/25G (SFP+/SFP28); backhaul 1/10/25G (QSFP+/SFP28); HSI (high-speed inter-card) uses QSFP+/QSFP28 across the UCDB backplane.

The interface map — every port on the baseband
GMA1 Main card — north (transport/timing) & GCB4 — south (fronthaul)port map
CPRI
Backhaul ×4 · 25G
SYNC · GNSS · PTP
LMT · ETH · RST (O&M)
GMA1
Main card
transport · timing · O&M
HSI · QSFP+
backplane fabric
GCB4
Channel card
L0–L11
12× CPRI → RU
fronthaul CPRIMain card carries transport (backhaul), timing (GNSS/PTP) and O&M; Channel cards carry the 12× fronthaul each.
The card lineup — every CDU card, decoded
CDU cards (from CDU50 / CDU51 Product Specifications)
CardFull nameClassRole
GMA1gNodeB Main card type A1MainMain processor, network interface, clock generation/distribution, per-board reset, O&M storage
GUC1gNodeB Unified Card type C1UnifiedMain + Channel combined (processor + CPRI) on one board
GUC2gNodeB Unified Card type C2UnifiedUnified card variant — adds NAVIC GNSS constellation
GCB4gNodeB Channel card type B4ChannelSubscriber channel processing; modulates data → 12× CPRI → RU (NR)
LCC2LTE Channel card type C2ChannelLTE subscriber channel processing; 12× CPRI
BCA1BTS Channel card type A1Channel2G/BTS channel processing; 12× eCPRI external interface
GCC1gNodeB card type C1CardUsed in the GUC-based CDU50/CDU51 configuration
i
Naming decode: G=gNodeB · L=LTE · B=BTS(2G); M=Main · C=Channel · U=Unified. So GMA1=gNodeB-Main-A1, LCC2=LTE-Channel-C2, GUC1=gNodeB-Unified-C1, BCA1=BTS-Channel-A1.
The Unified-Card build — CDU50 & CDU51 for GUC1/GUC2/GCC1/BCA1 ◆ Product Spec Ver 1.0

Samsung ships the CDU in two mutually-exclusive builds. The Main-card build above pairs a dedicated Main card (GMA1) with Channel cards. The build documented in the CDU50 and CDU51 Product Specifications (for GUC1, GUC2, GCC1, BCA1) folds the main processing and a channel onto one Unified card (GUC1 / GUC2), then adds pure Channel cards — GCC1 for LTE/NR, BCA1 for GSM. Straight from the spec: “the Main Card and Unified Card cannot be mounted on the same shelf; the Unified Card is mounted at the Main Card position.”

i
Decoded from the spec's own acronym appendix — CDU = Cabinet DU · UCBS = Universal platform type C Basic Shelf · UCDB = …Digital Backplane · PDPM = Power Distribution Panel Module · FANM = Fan Module · GUC = gNodeB Unified Card · GCC = gNodeB Channel card · BCA = BTS Channel card · UDA = User-Defined Alarm · UDE = User-Defined Ethernet · USM = Unified System Manager.
Verified spec sheet — CDU50 (2U) vs CDU51 (1U), Unified-Card build
ItemCDU50CDU51
Shelf assemblyUCBS-C4B (with FANM-C4N)UCBS-C4C (with FANM-C41)
Height · card slots2U · 4 slots (1 Unified + up to 3 Channel)1U · 2 slots (1 Unified + 1 Channel)
Dimensions (W×D×H)434 × 385 × 88 mm (excl. ear mount)436 × 385 × 44 mm (excl. ear mount)
Weight≤ 17 kg (full, excl. optics)≤ 11 kg (full, excl. optics)
Example basic configGUC2 + GCC1 + GCC1 + BCA1GUC2 + GCC1 / BCA1
Power — typ / maxGUC1 build 542 / 671 W
GUC2 build 593 / 733 W
GUC1+GCC1 335/442 · GUC2+GCC1 385/503
GUC1+BCA1 398/493* · GUC2+BCA1 469/580* W
Backhaul1G/10G/25G × 2 ports per Unified card (BH0, BH1 · SFP+/SFP28)
Fronthaul → RUGUC1 9 · GUC2 12 · GCC1 12 (6×2.5–25G + 6×2.5–10G) · BCA1 12 × 10G eCPRI
Technology5G · LTE · GSM (multi-RAT)
SynchronizationGNSS — GPS · GLONASS · Galileo · NAVIC (GUC2) — and IEEE1588v2 PTP
Input voltage−48 V DC (−40 to −57 V DC)
Environmental0 to +50 °C (+55 °C at CDU inlet) · 5–95 % RH non-cond. (≤30 g/m³) · −60 to 1800 m · ≤ 60 dBA @ 25 °C · IEC 60529 IP20
ComplianceTelcordia GR-63-CORE EQ Zone 4 · EN 300 019 (1-3 Cl.3.5 / 1-2 Cl.2.3) · CISPR 22/32 · IEC 62368-1 3rd Ed

* CDU51 GUC+BCA1 figures are predicted in the spec. Power values ±5 %, exclude optical modules, include FAN power. Source: Samsung CDU50 / CDU51 Product Specification for GUC1, GUC2, GCC1, BCA1, Ver 1.0.

CDU50 chassis population Figure 2 · 2U · UCBS-C4B
leftFANM-C4Nfan + STS
Slot #0GUC2Unified · 12 CPRI
Slot #1GCC1NR/LTE · 12 CPRI
Slot #2GCC1NR/LTE · 12 CPRI
Slot #3BCA1GSM · 12 eCPRI
rightAir filteroptional

−48 V DC enters the PDPM, is distributed across the UCDB backplane, and each card rectifies it locally. Max power (GUC2 build): 733 W.

CDU51 chassis population Figure 2 · 1U · UCBS-C4C
leftFANM-C41fan + STS
Slot #0GUC2Unified · 12 CPRI
Slot #1GCC1 / BCA1NR·LTE / GSM
rightAir filteroptional

Half-height 1U shelf — one Unified card + one Channel card. Max power (GUC2 build): 503 W; a compact-site CDU.

Inside the CDU — the real block diagram (Figure 3)

Downlink traffic from the BSC/EPC is TDMA/OFDMA-processed in the Modem (channel-card function), converted to a Digital I/Q + C&M optical signal by the built-in E/O device, and driven out over Optic CPRI/eCPRI to the RU. Uplink runs the reverse path through O/E. The Main-card function handles main processing, OAM and clock; the Reference Clock (GNSS / IEEE1588v2) and Power → EMI filter feed the whole card.

BSC/EPC → Main processing → Modem → E/O·O/E → Optic CPRI/eCPRI → RUFigure 3 · CDU Block diagram
I/Q
BSC / EPC
Samsung MBS core
user-plane
Main-card fn
Main Processing · OAM
transmission
Channel-card fn
Modem
TDMA / OFDMA
E/O · O/E
conversion
Digital I/Q + C&M
Optic
CPRI / eCPRI
SFP+ / SFP28
RU
Radio Unit
to antenna
Reference Clock
GNSS · IEEE1588v2 PTP
Power → EMI filter
−48 V DC
user-plane traffic clock / powerThe Unified card is the Main-card function and a Channel-card function on one board.
Card-port explorer — every port on every card ◆ all 7 cards · connector-exact

Pick any of the seven cards — Main (GMA1), Channel (GCB4 · LCC2 · GCC1 · BCA1) and Unified (GUC1 · GUC2) — to see its real front-panel layout from the Product Specification. Click any port for its exact connector type and function; colour codes the role. This is the "pure connectivity" view — every optical, electrical, sync and management port on the faceplate.

Connector reference — every connector type used across the CDU cards
ConnectorUsed forOn which cards / portsNotes
SFP+10G optical — backhaul & CPRI fronthaulGMA1 BH0–BH3 · ETH1 · all L-portsSmall Form-factor Pluggable Plus · ⚠ never look into the optic
SFP2825G optical — fronthaul & 25G backhaulGCB4/GUC1/GUC2 L-ports · GUC1/GUC2 BH0/BH1same cage as SFP+, higher rate
QSFP+ / QSFP2840/100G optical — inter-card High-Speed InterfaceGMA1 HSI · GCB4 HSI0–HSI2Quad SFP — links Channel cards to the Main card
RJ-45 (8-pin)electrical Gigabit EthernetGMA1/GUC LMT · GMA1 ETH0100/1000 Base-T — Local Maintenance Terminal + in-gNB Eth
SMAcoaxial RF — timingSYNC (1 PPS out) · GNSS (antenna in)screw-on coax; GNSS carries the satellite antenna feed
Harting (10-pin)reference-clock SYNC IN / OUTGMA1 CLK0/CLK1 · GUC CLKrugged clock daisy-chain between units
68-pin (UDA)external dry-contact alarmsall Main/Unified cardsUser-Defined Alarm — Rx 18 / Tx 2 ports
USB (4-pin)RS-232 CPU/DSP debugDBG / DBG0 / DBG1 on every cardserial console @115200 for board-level debug
CPRI/eCPRI → RUBackhaulOptical EthernetSync / clockMgmt / debugAlarmStatus LED
Click a port above to see its connector type and function…
Card matrix — Unified-Card build (verified)
CardTypeWeightFronthaul → RUBackhaulFeeds
GUC1Unified C1< 3.1 kg9× CPRI (L0–L8, SFP+/SFP28)2× 1/10/25G (BH0/1) + ETHClock: GPS
GUC2Unified C2< 3.1 kg12× CPRI (L0–L11, SFP+/SFP28)2× 1/10/25G (BH0/1)GNSS+NAVIC · PTP
GCC1Channel C1≈ 2.5 kg12× CPRI (L0–L5 → SFP28, L6–L11 → SFP+)→ GUC1/GUC2 (LTE/NR)
BCA1Channel A1≈ 2.5 kg12× eCPRI (L0–L11, SFP+)→ BSC via GUC (GSM)

STS status-LED decoder — the exact states from every card's LED table. This is what you read off the faceplate on a site visit:

Green — blinking · Normal operation ✓
Green — on · Software activation
Amber — on · Booting completion
Amber — blink slow / fast · ROM loader / SW download
Red — on · H/W reset / initialization
Red — blink · Board-removal prohibited (FW fusing)
Off · Power off
CLK amber-blink · GNSS antenna abnormal / not connected
!
Field tie-in — a CLK amber-blink (GNSS antenna abnormal / not connected) or a holdover state is the timing root-cause you rule out first in the Day-4 throughput and Day-2 retainability workflows — the same GNSS/PTP sync that keeps TDD in phase.
CDU51 in depth — the compact 1U baseband ◆ UCBS-C4C · FANM-C41

The CDU51 is CDU50's half-height sibling: the same brains (GUC1/GUC2 Unified + GCC1/BCA1 Channel cards), the same 5G·LTE·GSM multi-RAT, the same GNSS/PTP sync — packed into a 1U shelf that takes one Unified card + one Channel card. It's the pick for compact sites, low ceiling-height rooms and dense racks where a 2U CDU50 won't fit or isn't needed.

88 mm · 2U
GUC2GCC1GCC1BCA1
CDU50434 × 385 × 88 mm · ≤ 17 kg
4 card slots · up to 733 W
½the height,
~⅓ lighter (17 → 11 kg),
half the card slots
44 mm · 1U
GUC2GCC1/BCA1
CDU51436 × 385 × 44 mm · ≤ 11 kg
2 card slots · up to 580 W

Both are drawn to scale on the vertical axis (88 mm vs 44 mm). Depth (385 mm) and width (~435 mm) are effectively identical — only the height and slot count differ.

CDU51 Product Specification — the full sheet (Ver 1.0)
ItemSpecification
Shelf assemblyUCBS-C4C · 19-inch 1U shelf (backboard + power module + fan + air filter), fan-cooled with FANM-C41
Card slots2 slots — 1 Unified (GUC1/GUC2) + 1 Channel (GCC1 for LTE/NR, or BCA1 for GSM)
Technology5G · LTE · GSM (multi-RAT)
Backhaul interface1G/10G/25G × 2 ports per Unified card (BH0, BH1 · SFP+/SFP28)
Fronthaul interfaceGUC1 9 · GUC2 12 (2.5G/5G/10G/25G) · GCC1 12 (6×2.5–25G + 6×2.5–10G) · BCA1 12 × 10G eCPRI
SynchronizationGNSS (GPS · GLONASS · Galileo · NAVIC on GUC2) / IEEE1588v2 PTP
Input voltage−48 V DC (−40 to −57 V DC)
Power consumptionGUC1+GCC1 Typ 335 / Max 442 W · GUC2+GCC1 Typ 385 / Max 503 W · GUC1+BCA1 398 / 493 W* · GUC2+BCA1 469 / 580 W*
Dimensions (W×D×H)436 × 385 × 44 mm (1U, excl. ear mount)
Weight11 kg or less (full config, excl. optic modules)
CoolingFan cooling (FANM-C41)
Operating temperature0 °C to +50 °C (to +55 °C at CDU inlet)
Operating humidity5–95 % RH, non-condensing (≤ 30 g/m³)
Altitude−60 to 1800 m
Acoustic noise≤ 60 dBA @ 25 °C (1.0 m)
Ingress protectionIEC 60529 · IP20 (indoor)
Earthquake / vibrationTelcordia GR-63-CORE EQ Zone 4 · EN 300 019 (1-3 Cl.3.5 / 1-2 Cl.2.3)
EMC / safetyCISPR 22/32 · IEC 61000 series · IEC 62368-1 3rd Ed

* GUC1/GUC2 + BCA1 power figures are predicted in the spec (25 °C / 100 % and 50 °C / 100 %). Source: Samsung CDU51 Product Specification for GUC1, GUC2, GCC1, BCA1, Ver 1.0.

CDU51 config & power planner — pick the Unified card and the Channel card that go in the two slots. The planner reads out the verbatim power, fronthaul-port budget, backhaul, clock and RAT support for that exact combination:

Slot #0 · Unified card
Slot #1 · Channel card
GUC2 + GCC1NR + LTE
Typical
385 W
Maximum
503 W
Bars scaled to a 620 W ceiling. Typical = 25 °C / 50 % load · Max = 50 °C / 100 % load. Excludes optics, includes fan.
Optical fronthaul
24 ports → RU
Backhaul
2× 1/10/25G (BH0/1)
Clock source
GNSS + IEEE1588v2 PTP
Shelf load
1U · 2 / 2 slots used
Maximum fronthaul + 25G backhaul + NAVIC/PTP — the flagship 1U configuration.
i
Reading it — the Unified card sets the clock (GUC1 = GPS only; GUC2 = full GNSS + PTP) and whether 25G backhaul is available; the Channel card sets the third RAT (GCC1 keeps it NR/LTE; BCA1 adds GSM over eCPRI). Fronthaul ports are additive: Unified CPRI + Channel CPRI/eCPRI.
Slot configuration — how a CDU is populated
Config · 5G capacityGMA1 + 3× GCB436 CPRI
MainGMA1 (transport + timing)
Channel3× GCB4 (NR)
Fronthaul36× CPRI (12 per card)
Backhaul4× 25G on GMA1
PowerTyp 1017 W · Max 1210 W
Config · unifiedGUC1 (+ GUC2/GCC1)9 CPRI
CardGUC1 = main + channel in one
Fronthaul9× CPRI (L0–L8)
Backhaul2× 25G (BH0/BH1)
ClockGPS (+NAVIC on GUC2)
Fitcompact CDU51 (1U)
Config · multi-RATGMA1 + GCB4 + LCC2 + BCA15G·4G·2G
NRGCB4 (CPRI)
LTELCC2 (CPRI)
GSM / BTSBCA1 (eCPRI)
One siteall RATs on one CDU
Syncshared GNSS/PTP
ChassisCDU50 vs CDU512U · 1U
CDU50434×385×88 · 17 kg (2U)
CDU51436×385×44 · 11 kg (1U)
CDU50 cardsGMA1+GCB4+GUC1+LCC2+BCA1
CDU51 cardsGUC1+GUC2+GCC1+BCA1
Both−48 V · fan · GNSS+PTP
What the DU configures — real cell-configuration parameters

The baseband doesn't just carry data — it configures every cell. These are actual managed-object leaves under gnb-du-function / gutran-du-cell from the Samsung Parameter Description — the identity, frequency and SSB config each CDU cell is provisioned with:

gnb-du-function / gutran-du-cell — cell provisioning (real MO)
LeafRangeDefaultWhat it sets
nr-physical-cell-id−1 … 1007−1NR PCI — how UEs distinguish this cell
nr-arfcn-dl0 … 32791650Downlink carrier centre (NR-ARFCN)
subcarrier-spacing-common15/60 · 30/120 kHz30/120SCS of SIB1 / Msg2·4 / broadcast SI
ssb-subcarrier-spacing15 / 30 kHz30 kHzSSB sub-carrier spacing
ssb-periodicity20 … 160 ms40 msSSB burst period (cell lock to change)
cell-barredbarred / not-barrednot-barredManually bar the cell (access control)
tracking-area-code-usageuse / not-useuseUse the 5GS TAC of the NR cell
This is the bridge to the rest of the course — PCI planning (Day 3 mobility), SSB/SCS (Day 4 throughput), cell-barred (access) and TAC (mobility/registration) all live here in the DU. The baseband is the object tree you actually edit in LSM.
Synchronization — GNSS multi-constellation + IEEE1588v2 PTP

TDD (n78, B40/n40) demands tight phase sync so neighbouring cells don't transmit into each other's receive slots. The CDU takes timing from GNSS — GPS, GLONASS, Galileo and (on GUC2) NAVIC — over the GNSS antenna port, and/or IEEE1588v2 PTP over the backhaul as a backup / GNSS-free option.

GPSGLONASSGalileoNAVIC (GUC2)IEEE1588v2 PTPGNSS antenna portTDD phase sync
!
Why it matters — a sync fault (GNSS antenna abnormal / not connected raises an alarm on GMA1) shows up first as TDD interference and dropped throughput. Timing is a root-cause you rule out early in the Day-4 (throughput) and Day-2 (retainability) workflows.
The sync engine as MOs — …/hardware-management/digital-unit/clock-unit (AU PD SVR25B v2.0, verbatim)
ParameterRangeDefaultWhat it does
switch-mode / quality-level-modeauto | forced · user-defined | actualql-modeauto · user-definedhow the clock source is chosen — auto follows quality level
apts-modeoff | onoffAssisted Partial Timing Support — PTP helps GNSS through outages (G.8273.4 class)
ptp-info/log-sync-interval-g8275-1−4 (16 msg/s)−4full-timing-support telecom profile (phase) — the TDD baseline
ptp-info/log-sync-interval-g8275-2 / -g8265-1−6 (64 msg/s)−6partial-timing (phase) / frequency-only profiles
ptp-hybrid-modedisable | enabledisablePTP phase + SyncE frequency together (hybrid) — tightest holdover
ptp-phase-holdover-exceed-threshold0m | 5m | 10m | …holdover-5mhow long phase holdover is trusted before alarm/action
ptp-frequency-holdover-exceed-threshold7d | 30dholdover-30dfrequency holdover budget — much longer than phase
synce-info: quality-level-mode / acceptance-QLenabled · ql-eprtc…ql-ssuenabled · ql-prcSyncE input policing — refuse sources below QL-PRC by default
synce-assisted-holdover-extension-enableoff | onoffSyncE stretches PTP phase holdover when the PRTC is lost
holdover-exceed-switchover-enableoff | onoffauto-switch source when a holdover budget is exceeded
ucr: expected-holdover-time / gps-positionread-onlythe unit's own estimate of how long it can free-run — read it during backhaul works

TDD phase-sync failure chain to remember: GNSS lost → PTP (G.8275.1) carries phase → past holdover-5m the cell is a slot-format interferer. apts-mode + SyncE assistance are the two knobs that stretch that window.

Tx & Rx utilization — what they mean & how to troubleshoot

Once the CDU drives a radio, the two questions you ask every busy hour are: how full is the downlink (Tx) and how full — and how clean — is the uplink (Rx). "Utilization" has two layers: the air resource (PRB usage, from the DU counters) and the radio path (Tx power + Rx noise floor, from the AU MOs on the Radios page). Read them together — a PRB number without its RF context lies.

Tx utilization — the downlink

"How much of the cell's downlink am I using?" — two dimensions:

  • DL PRB utilization = TotDLUnicastPrbSche ÷ TotDLAvailablePrb (NR fam 5041 · LTE fam 55 TotPrbDLAvg). The air-capacity gauge — >70 % at busy hour = congestion.
  • Tx power headroom = actual output vs dl-max-tx-power (170 = 17 dBm/0.1 step) & tx-attenuation (AU carrier-control-info). Coverage vs the power ceiling.
  • PDCCH / CCE can cap DL before PRBs do — UsedCCEperSlot (fam 5012) + RatioSlotwBlockDL (fam 5097).

Rx utilization — the uplink

"How much of the uplink am I using, and is it clean?" — usage AND noise:

  • UL PRB utilization = TotULUsedPrb ÷ TotULAvailablePrb (NR 5041 · LTE 55 TotPrbULAvg). ⚠ interference inflates this — retransmissions burn PRBs.
  • Rx noise floor = per-path carrier-rssi + the rssi-high-alarm-threshold −620 (=−62 dBm) / rssi-low-alarm-threshold (AU MO). The interference & dead-path detector.
  • UL quality = PUSCH SINR (fam 5044) + interference power (fam 5045) + UL BLER (fam 5166). Clean UL = high SINR, low residual BLER.
Troubleshooting flow — symptom → what to open → root cause → action
SymptomOpen these (in order)Likely root causeAction
High DL PRB util (>70 %), thpt fallingDL PRB util → CQI (5018) → active-UE count (5087)genuine capacity limit, or a few heavy usersactivate CA/SCell · load-balance/offload via mobility · add a carrier; if few users → policy/QoS cap
High DL PRB but low thptCQI (5018) → DL BLER (5165) → 256QAM sharepoor DL radio quality — PRBs used inefficientlyfix coverage/interference first (tilt, power); PRBs aren't the problem, quality is
DL blocked, PRB not fullCCE util (5012) → RatioSlotwBlockDL (5097)PDCCH/control-channel congestion, not data PRBsincrease CORESET / aggregation-level tuning; PDCCH capacity, not PDSCH
High UL PRB util, poor UL thptUL PRB → PUSCH SINR (5044) → UL BLER (5166)usually UL interference → retransmissions eat PRBsif SINR low → hunt interference (below); if SINR fine → real UL load, add UL capacity
UL SINR low / UL BLER highper-path carrier-rssi (AU MO) → RSSI alarm (−62 dBm) → interference power (5045)external interference, PIM, or overshooting neighbourfind the offending band/direction; check PIM (feeder/connectors); coordinate/retilt the neighbour
One Rx path RSSI ≫ othersper-path carrier-rssi + temperature + current-amp-state (AU path-control)path imbalance — feeder/antenna/PIM or a sick PA pathswap/inspect that feeder+antenna; if PA fault → path-switch isolate; not a parameter fix
RSSI high-alarm firing (≥ −62 dBm)RSSI alarm threshold → spectrum sweep → neighbour liststrong external interferer or intermod (PIM)locate & remove the interferer; PIM test the passive chain; never mask it by raising the threshold
Low Tx util but coverage complaintsdl-max-tx-power · tx-attenuation · electrical-tilt · path-energy-saving-statepower capped/attenuated, tilt too high, or ES muted a path off-peakraise power / cut attenuation / adjust tilt; check ES state (default enable) before blaming coverage
Off-peak UL util/SINR shiftsradio-sleep-mode · path-energy-saving-state · carrier switchesenergy-saving muted carriers/paths in the low-traffic windowexpected behaviour — confirm ES schedule; only intervene if it hurts residual traffic
The golden rule for Tx/Rx utilization — a high PRB number is a symptom, never a diagnosis. DL: high PRB + good CQI = real capacity (add carriers/CA); high PRB + bad CQI = a quality problem wearing a capacity mask. UL: high PRB almost always means interference until SINR proves otherwise — so on the uplink you check SINR and per-path RSSI first, PRB second. The radio-path truth (Tx power, per-path carrier-rssi, PA temperature) lives in the AU MO tree; the air-resource truth (PRB, CQI, SINR, BLER) lives in the DU counters. Cross them, then act.

The baseband runs the DU — and configures every cell.

Main card thinks and carries transport + timing; Channel cards modulate 12 fronthaul ports each; the UCDB backplane ties them together; GNSS/PTP keeps it in phase — and the DU object tree provisions PCI, ARFCN and SSB for every cell. Next in 1.1: the small cells that extend coverage.