name: NR-DC
full_form: NR-NR Dual Connectivity
context: 6.2.3.2.8.1 Is the source node e.g. eNB changed because it newly need to store for each neighbour e.g. HeNB whether it needs to address it via the proxy or direct? As for the specific property of HeNB serving only a single cell, the cell-data-model in the eNB becomes a ânode-data-modelâ, and one can argue at length whether this changes the eNB or not. The fact is that the eNB as for any other neighbour node, need to maintain X2-connectivity information. Whether the eNB is âconfusedâ of the fact that the same X2 address is used for several nodes is probably a matter of implementation. Further, during the X2 setup between the eNB and the X2-Proxy, the eNB is able to realise X2-connectivity towards the neighbouring HeNB via an X2-proxy, by noticing that the Served cells (i.e. HeNBs) of the X2-Proxy do not share the same 20-bit eNB ID of the X2-Proxy. The eNB saves the information of neighbouring cell received during the X2 setup procedure, and eNB configuration update procedure, then
description: NR-DC (NR-NR Dual Connectivity) is a technology feature that enables dual connectivity between two New Radio (NR) cells, allowing for improved network performance and user experience. It supports various power sharing mechanisms, including semi-static and dynamic power sharing, to optimize resource allocation between the Master Cell Group (MCG) and Secondary Cell Group (SCG). NR-DC also allows for slot-level synchronization between the Primary Cell (PCell) and Primary SCell (PSCell), although some UEs may only support NR-DC with ensured synchronization.
explanation: The context describes NR-DC as a technology feature within the 3GPP standard, focusing on its technical functionalities like dual connectivity, power sharing, and synchronization. This classification aligns with the definition of 'Technology' as a broad category encompassing innovations and advancements in various fields.
section_title: 5	Layer 1 related aspects
biotag_Context: 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,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,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,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,B-Network Function,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,B-Network Function,O,O,O,O
biotag_Description: B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,I-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,B-Network,I-Network,I-Network,O,O,B-Network Function,I-Network Function,I-Network Function,O,B-Technology,O,O,O,O,O,O,O,B-Parameter,I-Parameter,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,B-Technology,O,O,O