name: RRC
full_form: Radio Resource Control
context: This clause gives the RRC inactive to other RRC states transition given that gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.6.2-1. Figure 8.6.2-1: RRC inactive to other RRC states transition procedure 1. If data is received from 5GC, the gNB-CU sends PAGING message to the gNB-DU. 2. The gNB-DU sends Paging message to UE. NOTE: Step 1 and 2 only exist in case of DL data arrival. 3. The UE sends RRCResumeRequest message either upon RAN-based paging, UL data arrival or RNA update. 4. The gNB-DU includes RRCResumeRequest in a non-UE associated INITIAL UL RRC MESSAGE TRANSFER message and transfer to the gNB-CU. 5. For UE Inactive to UE Active transitions, excluding transitions due to signalling exchange only, the gNB-CU allocates gNB-CU UE F1AP ID and sends UE CONTEXT SETUP REQUEST message to gNB-DU, which may include SRB ID(s) and DRB ID(s) to be setup, CellGroupConfig stored in gNB-CU or retrieved from the old NG-RAN node may also be included. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (in case of SNPNs the serving NID). 6. The gNB-DU responds with UE CONTEXT SETUP RESPONSE message, which contains RLC/MAC/PHY configuration of SRB and DRBs provided by the gNB-DU. NOTE: Step 5 and step 6 exist for inactive to active transitions, excluding transitions due to signalling exchange only. When gNB-CU successfully retrieves and verifies the UE context, it may decide to let the UE enter into RRC active mode. gNB-CU shall trigger UE context setup procedure between gNB-CU and gNB-DU, during which both SRB1, SRB2 and DRB(s) can be setup. For signalling exchange only transitions, gNB-CU does not trigger UE Context Setup procedure. For inactive to Idle transitions the gNB-CU does not trigger the UE Context Setup procedure. 7. The gNB-CU generates RRCResume/RRCSetup/RRCReject/RRCRelease message or receives RRCRelease message from the old NG-RAN node towards the UE. The RRC message is encapsulated in DL RRC MESSAGE TRANSFER message together with SRB ID. 8. The gNB-DU forwards RRC message to the UE either over SRB0 or SRB1 as indicated by the SRB ID. NOTE: In step 7, it is expected that gNB-CU takes appropriate action, e.g. generates RRC resume message for inactive to active state transition(for both cases of signaling exchange only, and UP data exchange), generates RRCSetup message for fallback to establish a new RRC connection, and generates or receives from the old NG-RAN node either RRCRelease message without suspend configuration for inactive to idle state transition, or RRCRelease message with suspend configuration to remain in inactive state. If step 5 and 6 are not performed, the gNB-DU deduces the SRB on which to deliver the RRC message in step 7 from the SRB ID, i.e. SRB ID â0â corresponds to SRB0, SRB ID â1â corresponds to SRB1. 9. The UE sends RRCResumeComplete/RRCSetupComplete message to the gNB-DU. 10. The gNB-DU encapsulates RRC in UL RRC MESSAGE TRANSFER message and send to the gNB-CU. NOTE: Step 9 and step 10 exist for inactive to active state transition (for both cases of signaling exchange only, and UP data exchange). UE generates RRCResumeComplete/RRCSetupComplete message for resume the existing RRC connection or fallback to a new RRC connection respectively.
description: Radio Resource Control (RRC) is a protocol in mobile telecommunications used for managing radio resources between User Equipment (UE) and the network. It plays a crucial role in controlling the configuration of radio bearers, handling mobility, and allocating radio resources efficiently within cellular networks.
explanation: RRC is classified as a Protocol because it defines the rules and procedures for communication between the UE and the network regarding radio resource management, aligning with the context provided which outlines specific RRC states transitions and message exchanges.
section_title: 8.6.2 RRC inactive to other states
biotag_Context: O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Network,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,B-Device,B-Protocol,B-Parameter,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,B-Network Function,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,B-Connection,O,O,O,B-Network Function,O,B-Protocol,O,O,O,B-Device,O,O,B-Connection,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Connection,O,O,B-Connection,B-Parameter,O,O,O,O,B-Connection,B-Parameter,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Network Function,O,B-Protocol,O,B-Connection,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Device,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O