The architecture that was built to receive intelligence
The stage animates the machine as it is spoken: the ROP heartbeat, the five-shelf data estate, NWDAF answering the core’s questions, the two RICs with strategy flowing down A1 and live state up E2, the Ericsson floors from EIAP to the baseband, a Friday-evening traffic-steering story run through the wires, and the guardrail checklist that turns a clever model into a deployable colleague. English karaoke subtitles, word by word.
Place ten use cases on the control-loop ladder — then browse NWDAF
Pick a use case and see where it belongs — rApp, xApp, or silicon — with the interfaces it rides and the model family that fits. Then open the NWDAF analytics browser: every analytics ID, who consumes it, and what it answers.
Fifteen cards from ROP to guardrails
The data estate, the standards (TS 23.288 · TR 37.817 · O-RAN), the Ericsson stack, and the deployment discipline — each as one card with its load-bearing facts.
Every interface, function and discipline of Module 2
From the ROP to the oscillation jail — searchable, each term with its spec or origin and its one-line meaning.
| term | family | spec / origin | what it means |
|---|
The Module 2 mastery check
Ten questions from a pool of nineteen, reshuffled every load. Pass at 70%+ before Module 3 — the counter files are waiting.