name: MeNB
full_form: Master eNodeB
context: This procedure is used for the case the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU when only MCG SRB is available during EN-DC operation. Figure 8.2.2.1-1 shows the inter-gNB-DU mobility procedure using MCG SRB in EN-DC. Figure 8.2.2.1-1: Inter-gNB-DU Mobility using MCG SRB in EN-DC 1. The UE sends an ULInformationTransferMRDC message to the MeNB. 2. The MeNB sends RRC TRANSFER message to the gNB-CU. 3. The gNB-CU may send UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU to query the latest SCG configuration. 4. The source gNB-DU responds with an UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. 5. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the target gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes a CG ConfigInfo. 6. The target gNB-DU responds the gNB-CU with an UE CONTEXT SETUP RESPONSE message. 7. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU indicating to stop the data transmission to the UE. The source gNB-DU also sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. 8. The source gNB-DU responds the gNB-CU with an UE CONTEXT MODIFICATION RESPONSE message. 9. The gNB-CU sends an SGNB MODIFICATION REQUIRED message to the MeNB. 10/11. The MeNB Initiated SgNB Modification procedure may be triggered by the SgNB Initiated SgNB Modification procedure (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc...). 12. The MeNB and the UE perform RRC Connection Reconfiguration procedure. 13. The MeNB sends an SGNB MODIFICATION CONFIRM message to the gNB-CU. 14. Random Access procedure is performed at the target gNB-DU. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. NOTE: It is up to gNB-CU implementation whether to start sending DL User Data to gNB-DU before or after reception of the Downlink Data Delivery Status. 15. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. 16. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message.
description: The Master eNodeB (MeNB) is a network function that plays a crucial role in managing the inter-gNB-DU mobility procedure using MCG SRB in EN-DC. It acts as an intermediary between the gNB-CU and the UE, facilitating communication and data transfer during the handover process.
explanation: The MeNB is classified as a Network Function because it serves as a key component in controlling and managing the mobility of UEs within the network, specifically during inter-gNB-DU handovers. Its role involves coordinating with other network functions such as gNB-CU and gNB-DU to ensure seamless data transmission and reception.
section_title: 8.2.2.1 Inter-gNB-DU Mobility using MCG SRB
biotag_Context: O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Network Function,O,O,B-Network,B-Connection,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Network,B-Connection,O,O,O,O,O,O,O,B-Network,B-Connection,O,B-Technology,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,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-Device,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,B-Protocol,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,B-Connection,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,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,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Connection,O,O,O,B-Network Function,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Connection,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O