name: ng-eNB
full_form: next-generation evolved Node B
context: The purpose of this procedure is to allow the ng-eNB to suspend an RRC connection to be resumed by the UE using User Plane CIoT 5GS Optimisation at a later time. The UE may resume the RRC connection in the same or different ng-eNB where the suspend took place. The UE and ng-eNB store the AS security context at suspend and reactivate the AS security context at resume. The UE and the ng-eNB may also use EDT (Early Data Transmission) or PUR (Preconfigured Uplink Resource) feature in this procedure, as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ]  [88] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ]  [69].
description: The next-generation evolved Node B (ng-eNB) is a critical component in the 5G network architecture, responsible for managing radio resources and controlling user equipment connections. It plays a key role in implementing features such as User Plane CIoT 5GS Optimisation, Early Data Transmission (EDT), and Preconfigured Uplink Resource (PUR). The ng-eNB is involved in procedures like RRC connection suspension and resumption, ensuring efficient network operations and seamless user experience.
explanation: ng-eNB is classified as a Network Function because it serves as a central element in managing radio resources, controlling UE connections, and implementing various features to optimize network performance. Its role in procedures such as RRC connection suspension and resumption further solidifies its categorization under this entity type.
section_title: 6.16.1 Security handling in Control Plane CIoT 5GS Optimization 6.16.2.1 General
biotag_Context: O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,B-Protocol,I-Protocol,B-Technology,B-Technology,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Device,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,B-Technology,O,B-Connection,O,O,O,O,O,O,O,O,B-Specification,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,O,O,O,B-Specification,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,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,O,O,O,O,O,B-Protocol,I-Protocol,B-Technology,B-Technology,O,B-Parameter,I-Parameter,I-Parameter,O,O,B-Technology,I-Technology,I-Technology,O,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O