A1 Interface
O-RAN interface from the non-RT RIC to the near-RT RIC, carrying policy guidance, ML model updates, and enrichment information.
A1 is the diplomatic channel between the two RICs — it runs from the non-RT RIC down to the near-RT RIC and carries guidance rather than direct control. Three kinds of thing flow over it: policies (declarative goals like "keep this slice's latency under X for these users"), enrichment information (outside context the RAN can't see on its own, such as a traffic or mobility prediction), and ML model management. The near-RT RIC takes that guidance and turns it into concrete fast-loop actions through its xApps.
The mental model that helps: A1 is about intent and steering, not commands. The non-RT RIC doesn't reach into the RAN and flip a parameter — it hands the near-RT RIC a policy and trusts the local xApps to honour it within the near-real-time loop. Contrast that with E2, which does carry direct control down to the RAN nodes. Keeping A1 (policy, slow, RIC-to-RIC) and E2 (control, fast, RIC-to-RAN) straight is one of the more common O-RAN interview stumbles.
Related terms
Want to truly understand A1 Interface? Learn it in context.
A free account opens all 13 courses — 404 video lessons, labs and full practice exams — for 7 days, no card. Prime Membership keeps them and adds the certification exam and a verifiable certificate.
- 7 days of every course
- Then the first module, free
- No card needed
- TELCOMA since 2009
Get one 5G/LTE engineering deep-dive a fortnight
One thing explained properly every other Tuesday — a real failure, and the lab or trace where you work it yourself. No spam, no marketing, just engineering. Unsubscribe in one click.