name: NGAP
full_form: NG Application Protocol
context: and the F1 interface the same principles for AP IDs apply as for UE-associated logical connections. The definitions of AP IDs as used on NG interface or Xn interface or F1 interface or E1 interface are shown below: RAN UE NGAP ID: A RAN UE NGAP ID shall be allocated so as to uniquely identify the UE over the NG interface within an gNB. When an AMF receives an RAN UE NGAP ID it shall store it for the duration of the UE-associated logical NG-connection for this UE. Once known to an AMF this is included in all UE associated NGAP signalling. The RAN UE NGAP ID shall be unique within the logical NG-RAN node. AMF UE NGAP ID: An AMF UE NGAP ID shall be allocated so as to uniquely identify the UE over the NG interface within the AMF. When a NG-RAN node receives an AMF UE NGAP ID it shall store it for the duration of the UE-associated logical NG-connection for this UE. Once known to a NG-RAN node this ID is included in all UE associated NGAP signalling. The AMF UE NGAP ID shall be unique
description: NG Application Protocol (NGAP) is a protocol used for signaling between the Access and Mobility Management Function (AMF) and the Next Generation Radio Access Network (NG-RAN) node over the NG interface. It enables the exchange of information necessary for managing UE connections, such as UE-associated logical connections and AP IDs.
explanation: The context explicitly mentions NGAP in relation to signaling between network functions (AMF and NG-RAN node), which aligns with the definition of a protocol in telecommunications. The detailed description of how NGAP is used for handling Application Protocol Identities further supports its classification as a protocol.
section_title: 6.2.1Principle of handling Application Protocol Identities
biotag_Context: O,O,B-Interface,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Interface,O,O,B-Interface,I-Interface,O,B-Interface,O,O,B-Interface,O,O,O,O,B-Network,B-Device,B-Protocol,O,O,B-Network,B-Device,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Interface,O,O,O,O,O,O,B-Network Function,O,O,B-Network,B-Device,B-Protocol,B-Parameter,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,B-Device,O,B-Protocol,O,O,B-Network,B-Device,B-Protocol,B-Parameter,O,O,O,O,O,O,B-Network Function,O,B-Network Function,B-Device,B-Protocol,O,O,B-Network Function,B-Device,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Interface,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,B-Device,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,B-Device,O,B-Protocol,O,O,B-Network Function,B-Device,B-Protocol,B-Parameter,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O