RRC
Radio Resource Control: the Layer 3 protocol between UE and gNB that handles connection establishment, reconfiguration, handover, measurement configuration, and release.
RRC is the Layer 3 control protocol that runs the UE's life in a cell — setting up and tearing down the connection, reconfiguring it, configuring measurements, and steering handovers. Almost every meaningful change to how a device operates arrives as an RRC message, most often an RRCReconfiguration carrying the parameters for bearers, BWPs, CSI reporting, and the rest.
NR's notable addition is a third state. LTE had RRC_IDLE and RRC_CONNECTED; NR inserts RRC_INACTIVE between them. In INACTIVE the UE keeps its context and security stored in the network (the RAN, not just the core) but lets the radio sleep, so resuming to CONNECTED is far cheaper than a full setup from IDLE — fewer signalling round trips, faster wake-up, less battery drain. That matters enormously for bursty traffic and IoT, where devices constantly cycle between sending a little data and dozing. When you read about signalling-load problems or handover failures, RRC is usually where the diagnosis starts.
Frequently asked questions
- What is RRC_INACTIVE state in 5G?
- It's a middle ground between idle and connected, new in NR. The UE suspends its radio connection but the network keeps its context and security stored in the RAN. When data arrives, the UE resumes to connected with far less signalling than re-establishing from idle — fewer round trips and faster wake-up. It exists to handle bursty and IoT traffic efficiently without the battery and latency cost of full reconnection.
Related terms
Want to truly understand RRC? 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.