O-RAN Advance Course  /  Chapter 2 — Functional Splits & the 7-2x Fronthaul
O-RAN R005 train · 2026
CHAPTER 2 · MODULE M2 · NARRATED VIDEO + LAB

Open the pink line.
Down to the last bit.

In Chapter 1 the Open Fronthaul was one pink cable. Here we split it open. Where you cut the protocol stack decides your radio's cost, its power, and the fiber you rent — so we climb the split ladder, prove why 7-2x won, place every PHY block inside the O-RU, decode an eAxC ID bit-by-bit, and compute the real gigabits. Built verbatim from 3GPP TR 38.801 §11 and O-RAN WG4 CUS.0 v21.

8splitsoption 1 → 8 ladder
7-2xwonfreq-domain IQ
BO-RU categories
16biteAxC decoded
~12Gb/s100 MHz 4T4R
ENkaraoke subs
3GPP TR 38.801 §11 (split options) · O-RAN.WG4.CUS.0-R005-v21.00 §4 (splits/data flows) · §5 (transport/QoS/fragmentation)
▶ VIDEO · CHAPTER 2 · 16:51 NARRATED

Functional splits & the 7-2x fronthaul — the full story

The player screen is a live animation stage — a tower rises, the fronthaul lights up, the split ladder assembles, IQ streams flow down the fiber and the bandwidth pipe fills, exactly as the narration reaches each idea. Karaoke subtitles in English + Persian, four subtitle modes, fullscreen.

Chapter 2 · Open RAN Masterclass · functional splits & 7-2x
Open the pink line — down to the last bit
0:00 / 0:00
LAB · SPLIT & BANDWIDTH SIMULATOR
Size your own fronthaul →
Drag bandwidth, layers, numerology and compression — watch the gigabits and the link headroom move in real time.
LAB · FRONTHAUL DIMENSIONING · CUS.0 §4 METHOD

Split & bandwidth simulator

Dial a radio and watch its Open-Fronthaul line rate. The formula: occupied subcarriers × symbol rate × 2 (I+Q) × bits/sample × streams, then link overhead. Category A ships antenna streams; Category B ships data layers.

0 Gb/s
line rate incl. ~15% eCPRI/Ethernet overhead · 0 Gb/s payload
occupied SC0
samples/s·ant0
bits / sample0
resource blocks0
streams on FH0
vs CPRI (opt 8)0
REFERENCE · THE SPLIT LADDER · TR 38.801 §11

Eight ways to cut a base station — slide the cut, watch the trade-off

One horizontal line across the stack. Cut high → cheap link, smart radio, relaxed latency. Cut low → fat link, simple radio, brutal latency. Pick an option: the stack splits into O-DU / O-RU, the fronthaul re-sizes, and the three meters move against each other. O-RAN lives at 7-2x.

O-DU · cloud
O-RU · radio
✂ cut
Fronthaul carries
frequency-domain IQ
already mapped to subcarriers
lowestCPRI · ~16× user rate
Fronthaul bandwidthmanageable
Latency tightness~100 µs class
Radio complexity / costmoderate
7-2x PLACEMENT · CUS.0 §4.2
In the 7-2x split the O-DU holds High-PHY (channel coding, rate matching, scrambling, modulation, layer mapping, and — for Category A — precoding), while the O-RU holds Low-PHY: (i)FFT, cyclic-prefix add/remove, PRACH filtering, digital beamforming (Cat B) and the RF front end. The fronthaul therefore carries frequency-domain IQ already mapped to subcarriers — the key reason its rate is far below CPRI's raw time-domain stream.
REFERENCE · THE eAxC IDENTIFIER · CUS.0 §5.4

Every flow's postal code — 16 bits, four fields

The eAxC (extended Antenna-Carrier) ID rides in every C-plane and U-plane message. Its 16 bits are partitioned into four sub-fields whose widths are configured per deployment and must sum to 16.

Sub-fieldNamesTypical widthMeaning
DU_Port_IDwhich O-DU processing port / spatial stream2–4 bitsties the flow to a DU pipeline
BandSector_IDband + sector3–6 bitswhich physical sector on the tower
CC_IDcomponent carrier1–4 bitswhich carrier in CA
RU_Port_IDspatial stream / antenna at the O-RU4–8 bitswhich stream inside the radio
WHY IT BITES
The O-DU and O-RU must agree on the bit-widths of each sub-field (o-ran-uplane-conf). If the O-DU packs [4|4|4|4] and the O-RU expects [2|6|2|6], every eAxC decodes to the wrong stream and the carrier never keys up — a classic first-integration failure you will meet in M6/M9.
REFERENCE · TRANSPORT · CUS.0 §5.1 / §5.3 / §5.5

Wrapping IQ for a switched network

EncapsulationStackWhenO-RAN status
eCPRI over EthernetEth ▸ (VLAN) ▸ eCPRI ▸ eAxC ▸ IQthe default L2 fronthauldominant ✓
IEEE 1914.3 (RoE)Eth ▸ RoE ▸ IQradio-over-Ethernet mapperpermitted
eCPRI / IQ over UDP/IPEth ▸ IP ▸ UDP ▸ eCPRI ▸ IQrouted / L3 fronthaulpermitted
PLANES · VLAN & QoS · CUS.0 §5.3
The C-, U- and S-planes share the switch, so they are separated by VLAN and prioritized by 802.1Q PCP / DSCP — S-plane (PTP) and C-plane must never queue behind bulk U-plane IQ. Because one slot of IQ can exceed an MTU, CUS.0 §5.5 defines fragmentation (eCPRI concatenation/segmentation, or IP fragmentation) so large transfers split and reassemble in order. Get VLAN + PCP wrong → intermittent timing alarms that look like a bad radio.

🛠 Engineer detail block — what you'll actually meet in the field

  • 25 GbE is not always enough. A 3-sector 64T64R site sending naive antenna streams wants >100 Gb/s per sector. Category B precoding + 9-bit BFP is what makes it fit on 25G optics — the bandwidth math chooses your radio.
  • Category is the first purchase question. Cat A = precoding in the O-DU (≤ 8 streams, simple macro). Cat B = precoding in the O-RU (mMIMO). Ask it before latency, before price.
  • eAxC bit-plan is a joint config. DU_Port / BandSector / CC / RU_Port widths must match on both ends. Mismatch = carrier never activates, and it looks like an RF fault.
  • Frequency-domain, not time-domain. 7-2x ships subcarrier IQ, which is why it beats CPRI (option 8). If someone says "CPRI fronthaul", they do not mean Open Fronthaul.
  • S-plane priority is sacred. The single most common fronthaul rookie error is letting U-plane bulk starve PTP. VLAN + PCP first, always.
✓ QUIZ · 8 QUESTIONS · SHUFFLED EVERY LOAD

Chapter 2 quiz