name: MRDC
full_form: Multi-Radio Dual Connectivity
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: Multi-Radio Dual Connectivity (MRDC) is a technology feature in 5G networks that enables user equipment (UE) to connect simultaneously to two different radio access technologies, such as LTE and NR. This allows for improved mobility, increased throughput, and better overall network performance. MRDC is particularly useful during EN-DC (E-UTRAN-NR Dual Connectivity) operations, where the UE can leverage both LTE and 5G radios for data transmission.
explanation: MRDC is classified as a Technology because it refers to a specific feature or capability within the 3GPP's 5G network architecture. The provided context describes the inter-gNB-DU mobility procedure using MRDC in EN-DC, highlighting its role in enhancing network performance and user experience.
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: B-Technology,I-Technology,I-Technology,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,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,B-Technology,O,O,O,O,O,O,B-Device,O,O,O,B-Technology,O,B-Technology,O,O,O,O