name: UP
full_form: 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 User Plane (UP) is a critical component in the Next Generation Radio Access Network (NG-RAN) architecture, responsible for managing user data transmission and bearer contexts. It plays a pivotal role in the RRC Connected to RRC Inactive state transition procedure, handling tasks such as bearer context setup, modification, and release, as well as inactivity monitoring and notification.
explanation: UP is classified as a Network Function because it serves as a key component in managing user data transmission and bearer contexts within the NG-RAN architecture, aligning with the 3GPP's specifications for efficient network operations.
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-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,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