name: E1AP
full_form: E1 Application Protocol
context: NR-DC, the MN indicates the configured per-UE, FR1 or FR2 measurement gap pattern and the gap purpose to the SN. The SN can indicate to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. In (NG)EN-DC and NR-DC, SMTC can be used for PSCell addition/PSCell change to assist the UE in finding the SSB in the target PSCell. In case the SMTC of the target PSCell is provided by both MN and SN it is up to UE implementation which one to use. CLI measurements can be configured for NR cells in all MR-DC options. In EN-DC and NGEN-DC, only the SN can configure CLI measurements. In NE-DC, only the MN can configure CLI measurements. In NR-DC, both the MN and the SN can configure CLI measurements, and the MN informs the SN about the maximum number of CLI measurement resources that can be configured by the SN to ensure that the total number of CLI measurement resources does not exceed the UE capabilities. For MUSIM operation, when the UE is configured to operate in NR-DC
description: The E1 Application Protocol (E1AP) is a protocol used in the 5G New Radio (NR) architecture for communication between the gNB-CU-CP (Central Unit-Control Plane) and gNB-CU-UP (Central Unit-User Plane). It manages the exchange of control plane information, including error indication procedures. The E1AP ID IE (Information Element) identifies the UE (User Equipment) in the context of E1AP signaling.
explanation: The text explicitly states that E1AP is a protocol used for communication between gNB components within the 5G NR architecture. It defines specific functions like managing control plane information and error handling, which are characteristic of protocols.
section_title: 8.2.2.2	Successful Operation
biotag_Context: O,O,B-Network Function,O,O,O,O,B-Technology,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Network Function,O,O,O,B-Message,O,O,O,B-Technology,O,B-Measurement,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,B-Message,O,O,O,O,B-Device,O,O,O,O,O,B-Measurement,O,O,O,O,O,B-Network,O,O,O,B-Technology,O,O,B-Technology,O,O,O,O,B-Message,O,O,B-Measurement,O,O,O,O,O,B-Network Function,O,O,B-Measurement,O,O,O,O,O,B-Network Function,O,O,B-Message,O,O,B-Measurement,O,O,O,B-Network Function,O,O,B-Message,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,B-Device,O,O,B-Device,O,O,O,B-Device,O,O,O,O,O,B-Technology
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Technology,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-Protocol,B-Parameter,B-Message,O,O,O,O,B-Device,O,O,O,O,O,O,B-Protocol,O