name: NGEN-DC
full_form: Non-Geran E-UTRA-NR Dual Connectivity
context: In MR-DC, the UE has a single RRC state, based on the MN RRC and a single C-plane connection towards the Core Network. Figure 4.2.1-1 illustrates the Control plane architecture for MR-DC. Each radio node has its own RRC entity (E-UTRA version if the node is an eNB or NR version if the node is a gNB) which can generate RRC PDUs to be sent to the UE. RRC PDUs generated by the SN can be transported via the MN to the UE. The MN always sends the initial SN RRC configuration via MCG SRB (SRB1), but subsequent reconfigurations may be transported via MN or SN. When transporting RRC PDU from the SN, the MN does not modify the UE configuration provided by the SN. In E-UTRA connected to EPC, at initial connection establishment SRB1 uses E-UTRA PDCP. If the UE supports EN-DC, regardless whether EN-DC is configured or not, after initial connection establishment, MCG SRBs (SRB1 and SRB2) can be configured by the network to use either E-UTRA PDCP or NR PDCP (either SRB1 and SRB2 are both configured with E-UTRA PDCP, or they are both configured with NR PDCP). Change from E-UTRA PDCP to NR PDCP (or vice-versa) is supported via a handover procedure (reconfiguration with mobility) or, for the initial change of SRB1 from E-UTRA PDCP to NR PDCP, with a reconfiguration without mobility before the initial security activation. If the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC), the UE can be configured to establish a SRB with the SN (SRB3) to enable RRC PDUs for the SN to be sent directly between the UE and the SN. RRC PDUs for the SN can only be transported directly to the UE for SN RRC reconfiguration not requiring any coordination with the MN. Measurement reporting for mobility within the SN can be done directly from the UE to the SN if SRB3 is configured. In NR-DC, the UE can be configured to establish a SRB with the SN (SRB5) to enable RRC messages which include application layer measurement report information to be sent directly between the UE and the SN. The application measurement report can be sent directly from the UE to the SN if SRB5 is configured and indicated by the network for the application measurement reporting. Split SRB is supported for all MR-DC options, allowing duplication of RRC PDUs generated by the MN, via the direct path and via the SN. Split SRB uses NR PDCP. This version of the specification does not support the duplication of RRC PDUs generated by the SN via the MN and SN paths. In EN-DC, the SCG configuration is kept in the UE during suspension. During connection resumption, if the UE supports resuming with EN-DC, the UE can be configured to release, restore, or reconfigure the SCG configuration. Otherwise, the UE releases the SCG configuration (but not the radio bearer configuration) during resumption initiation. In MR-DC with 5GC, the UE stores the PDCP/SDAP configuration and the SCG configuration when moving to RRC Inactive. During connection resumption, if the UE supports resuming with MR-DC, the UE can be configured to release, restore, or reconfigure the SCG configuration. Otherwise, it releases the SCG configuration. Figure 4.2.1-1: Control plane architecture for EN-DC (left) and MR-DC with 5GC (right).
description: Non-Geran E-UTRA-NR Dual Connectivity (NGEN-DC) is a technology that enables dual connectivity between Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and New Radio (NR) in the context of Multi-Radio Dual Connectivity (MR-DC). It allows for the simultaneous use of both E-UTRA and NR radio access technologies, enabling seamless handovers and improved network performance. NGEN-DC is a key feature in 5G networks, supporting the coexistence of different radio access technologies and enhancing user experience.
explanation: NGEN-DC is classified as a Technology because it refers to a specific standard or method for achieving dual connectivity between E-UTRA and NR in MR-DC scenarios. The provided context from 3GPP TS 37.340 highlights the control plane architecture and procedures for NGEN-DC, demonstrating its role as a technological enabler for advanced network operations.
section_title: 4.2.1 Control Plane
biotag_Context: O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,O,B-Network Function,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,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Message,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,B-Message,B-Protocol,O,O,B-Network,B-Connection,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Protocol,B-Connection,O,O,O,O,B-Network Function,O,O,O,O,B-Device,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Connection,O,B-Technology,O,O,O,B-Device,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Protocol,O,B-Network,B-Protocol,O,B-Connection,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Network,O,O,O,B-Technology,B-Protocol,O,B-Network,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,B-Technology,B-Protocol,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Network Function,O,O,O,B-Technology,O,O,O,B-Device,O,O,O,O,O,O,B-Connection,O,O,B-Message,O,O,O,B-Protocol,O,O,O,B-Message,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,B-Message,O,O,O,O,O,O,O,B-Device,O,B-Message,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,B-Device,O,O,B-Message,O,B-Connection,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Connection,O,O,B-Message,O,O,O,B-Protocol,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,O,O,O,B-Device,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Technology,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Message,O,O,B-Network Function,O,B-Message,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,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Device,O,O,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,B-Technology,O,O,B-Technology,O,B-Network,O
biotag_Description: B-Technology,I-Technology,I-Technology,I-Technology,O,O,O,O,O,O,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,I-Network,O,O,B-Technology,I-Technology,O,O,O,O,O,B-Technology,I-Technology,I-Technology,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O