E2 Interface
O-RAN interface between the near-RT RIC and O-CU/O-DU, carrying control messages and telemetry for real-time RAN optimization.
E2 is the link that makes the near-RT RIC useful — it connects the RIC to the RAN nodes (the O-CU and O-DU, collectively called E2 Nodes) and carries both directions of the conversation: telemetry up, control and policy down. Without it the RIC would be blind and mute. It's the channel an xApp uses to subscribe to measurements and then act on them within the near-real-time loop.
What makes E2 more than a single protocol is its service models. E2SM definitions specify what you can monitor and what you can control for a given function — there are service models for things like KPM (key performance measurement, the reporting side), RC (RAN control), and others. An xApp is effectively written against one or more of these service models, so the set a node supports determines what optimisation is even possible. When a third-party xApp doesn't work against a particular RAN node, mismatched or unsupported E2 service models are one of the first things to check.
Related terms
Want to truly understand E2 Interface? Learn it in context.
E2 Interface is taught inside our O-RAN & Open Networks course with diagrams and worked examples. The first module is free with an account; labs, TelcoMentor and the rest of the curriculum are on Pro.
- Free to join
- First module of every course
- 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.