name: NG-U
full_form: Next Generation-User plane
context: The procedure for changing the UE state from RRC-connected to RRC-inactive is shown in Figure 8.9.6.1-1. Figure 8.9.6.1-1: RRC Connected to RRC Inactive state transition. 1. The gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST message with UE/PDU session/DRB level inactivity timer. 2. The gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE message. 3. The gNB-CU-UP sends BEARER CONTEXT INACTIVITY NOTIFICATION message with inactivity monitoring results. 4. The gNB-CU-CP determines that the UE should enter RRC-inactive (e.g., after receiving Bearer Context Inactivity Notification procedure). 5. The gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST message with a Bearer Context Status Change to the gNB-CU-UP, which indicates that the UE is entering RRC-inactive state. The gNB-CU-CP keeps the F1 UL TEIDs. 6. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message including the PDCP UL and DL status that may be needed for e.g., data volume reporting. The gNB-CU-UP keeps the Bearer Context, the UE-associated logical E1-connection, the NG-U related resource (e.g., NG-U DL TEIDs) and the F1 UL TEIDs. 7. The gNB-CU-CP sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU serving the UE, together with the RRCRelease message to be sent to the UE. NOTE: step 5 and step 7 can be performed at the same time. 8. The gNB-DU sends the RRCRelease message to the UE. 9. The gNB-DU sends the UE CONTEXT RELEASE COMPLETE message to the gNB-CU-CP.
description: The Next Generation-User plane (NG-U) interface is a critical component in the 5G network architecture, specifically within the NG-RAN. It facilitates communication between the gNB-CU-CP (Central Unit-Control Plane) and the gNB-CU-UP (Central Unit-User Plane), enabling the exchange of control and user data necessary for managing UE sessions and state transitions, such as from RRC-connected to RRC-inactive.
explanation: NG-U is classified as an Interface because it represents a communication pathway between different network functions within the NG-RAN architecture. The provided context highlights its role in facilitating the exchange of messages and data necessary for managing UE states and sessions, aligning with the definition of an interface in the context of 3GPP specifications.
section_title: 8.9.6.1 RRC Connected to RRC Inactive
biotag_Context: O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,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,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,B-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,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Interface,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Interface,B-Connection,O,O,O,B-Interface,B-Connection,O,O,O,O,O,O,B-Device,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,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O
biotag_Description: O,B-Interface,I-Interface,I-Interface,O,O,O,O,O,O,O,O,B-Technology,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-Device,O,O,O,O,O,O,O,O,O,O