CHAPTER 9 · MODULE M9 · NARRATED VIDEO + LAB
Prove it
actually works.
A multi-vendor promise is only as good as your ability to prove it. Open RAN testing climbs a pyramid: conformance (one box vs equipment, CONF.0), interoperability (two boxes together, IOT.0 profiles), and end-to-end (the whole network, TIFG). We walk a real 46-case interop campaign, build one for a given pairing, and map a product to its OTIC certificate or badge. From WG4 CONF.0/IOT.0, TIFG E2E, CGofOTIC.
3levelsconf · IOT · E2E
46casesclause-traceable
profilesIOT.0two boxes
OTIClabbadge path
cert·badgeconform · interwork
ENkaraoke subs
▶ VIDEO · CHAPTER 9 · NARRATED
Testing — the pyramid from conformance to a badge
The player screen is a live animation stage — the test pyramid stacks conformance → IOT → E2E, the 46-case campaign fills group by group, a product climbs from bench to badge, exactly as the narration reaches each idea. Karaoke subtitles EN + Persian, fullscreen.
◈
LAB · TEST-CAMPAIGN BUILDER
Build your campaign →
Toggle the planes and DUT; watch the 46-case matrix select the right groups and size your campaign.
LAB · TEST-CAMPAIGN BUILDER · IOT.0 v16 (46 cases)
Build an interop campaign
Pick the planes your pairing must prove; the 46-case matrix selects the relevant groups and sizes the campaign. Each group traces to its clause.
Toggle a plane on/off to add or drop its case group.
46 cases
of 46 · 5 groups selected
REFERENCE · THE THREE TEST LEVELS
The pyramid — each level proves what the one below cannot
| Level | Question | Setup | Spec |
|---|---|---|---|
| Conformance | does ONE box meet the spec? | one DUT vs calibrated test equipment | WG4 CONF.0 v16 |
| Interoperability | do TWO boxes work together? | real O-DU + real O-RU, matched profiles | WG4 IOT.0 v16 |
| End-to-end | does the NETWORK serve a user? | full stack + UE, functional & performance | TIFG E2E-Test v10 |
WHY ALL THREE
A box can pass conformance alone and still fail to interwork; a pair can pass interop and still fail end-to-end under real UE load. Conformance = one DUT vs equipment (for an O-RU, the reusable functional clauses are M-plane & S-plane; RF needs a shielded chamber = OTIC). Interop = two real implementations on matched profiles. E2E = a phone actually attaches and passes traffic.
A box can pass conformance alone and still fail to interwork; a pair can pass interop and still fail end-to-end under real UE load. Conformance = one DUT vs equipment (for an O-RU, the reusable functional clauses are M-plane & S-plane; RF needs a shielded chamber = OTIC). Interop = two real implementations on matched profiles. E2E = a phone actually attaches and passes traffic.
REFERENCE · THE 46-CASE MATRIX · IOT.0 v16
A real interop campaign, grouped
| Group | Exercises | Example clause |
|---|---|---|
| A · transport | VLAN plan, M vs C/U separation, tagging | MP.0 interface mgmt |
| B · sync | PTP lock LLS-C1 → C3, T-BC, SyncE | IOT.0 §7.2–7.4 |
| C · M-plane | DHCP, call home, capabilities, config | IOT.0 §6.2 / CONF.0 §3.1 |
| D · C/U-plane | eCPRI capture, delay management, decode | CUS.0 · IOT.0 §9.4–9.7 |
| E · cell & E2E | carrier activation, UE attach, DL/UL traffic | IOT.0 §8 · TIFG E2E §5–6 |
TRACEABILITY IS THE POINT
Each of the 46 cases cites its exact clause and a clear pass criterion (e.g. B-02: "O-RU reports LOCKED/PRC-traceable; stays locked 15+ min"). That traceability is the difference between a demo and a real acceptance campaign — it is what an operator's team signs off against.
Each of the 46 cases cites its exact clause and a clear pass criterion (e.g. B-02: "O-RU reports LOCKED/PRC-traceable; stays locked 15+ min"). That traceability is the difference between a demo and a real acceptance campaign — it is what an operator's team signs off against.
REFERENCE · OTIC · CGofOTIC / Cert-Badge
From passing results to a badge
| Thing | What it is |
|---|---|
| OTIC | Open Testing & Integration Centre — an accredited lab |
| CGofOTIC | the criteria & guidelines an OTIC operates by |
| Certificate | a product conforms to a spec |
| Badge | a pairing interworks (interop / E2E) |
THE JOURNEY
Conformance on the bench → interop in the lab → end-to-end on the network → an OTIC turns passing results into an O-RAN certificate (conforms) or badge (interworks), per the Cert-Badge spec. That badge is what an operator's procurement team actually asks to see before a purchase order.
Conformance on the bench → interop in the lab → end-to-end on the network → an OTIC turns passing results into an O-RAN certificate (conforms) or badge (interworks), per the Cert-Badge spec. That badge is what an operator's procurement team actually asks to see before a purchase order.
🛠 Engineer detail block — what you'll actually meet in the field
- Conformance ≠ interop ≠ works. Two datasheets that both cite the same spec version can still fail together. Budget an IOT campaign for every new O-DU/O-RU pairing — never assume conformance implies interworking.
- Traceability is your acceptance leverage. A vendor "passed our tests" means nothing; a 46-case matrix with clause references and pass criteria is what you withhold payment against. Insist on it.
- Most of a real campaign is M-plane and sync. Groups A/B/C (transport, PTP, bring-up) are where new pairings actually fail; C/U-plane decode and E2E come after the radio even talks.
- RF conformance is OTIC territory. You can run M-plane/S-plane functional clauses on a bench; RF (CONF.0 §3.2) needs a shielded chamber and calibrated equipment — plan lab time and budget for it.
- A badge is a procurement gate, not a nicety. Operators increasingly require an O-RAN badge for the specific pairing, not just per-box certificates. Know which OTIC and which badge before you promise a launch date.
✓ QUIZ · 8 QUESTIONS · SHUFFLED EVERY LOAD