name: API
full_form: Application programming interface
context: Figure 5.4.2.3.1 describes the scenario where there is an API invocation request at the NEF for ECUR mode. Figure 5.4.2.3.1: API Invocation Request to NEF using ECUR 1. NEF receives an API invocation Request from an AF. 1ch-a. The NEF sends Charging Data Request [Initial] to CHF for the received API Invocation. 1ch-b. The CHF opens CDR for this API Invocation. 1ch-c. The CHF acknowledges by sending Charging Data Response [Initial] to the NEF. 2. NEF performs the actions needed to fulfil the API invoked. 3. If authorized, the NEF continues the API invocation processing and sends the API Invocation Response. 3ch-a. The NEF sends Charging Data Request [Termination] to the CHF for terminating the charging associated with the API Invocation. 3ch-b. The CHF closes the CDR for this API Invocation. 3ch-c. The CHF acknowledges by sending Charging Data Response [Termination] to the NEF.
description: An Application Programming Interface (API) is a set of defined rules that enable different applications, systems, or services to communicate with each other. In the context of 3GPP TS 32.254, API refers to the interface through which an Application Function (AF) invokes services from the Network Exposure Function (NEF), and the NEF interacts with the Charging Function (CHF) for charging purposes.
explanation: The provided text explicitly mentions 'API invocation request' and describes a scenario where an AF uses an API to interact with the NEF, which in turn communicates with the CHF. This interaction is facilitated through well-defined interfaces, making API an interface entity type.
section_title: 5.4.2.3API Invocation - ECUR
biotag_Context: O,O,O,O,O,O,O,O,O,B-Interface,O,O,O,O,B-Network Function,O,B-Procedure,O,O,O,B-Interface,O,O,O,B-Network Function,O,B-Procedure,O,B-Network Function,O,O,B-Interface,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,B-Interface,O,O,O,B-Network Function,O,B-Message,O,O,B-Interface,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,B-Interface,O,O,O,O,O,B-Network Function,O,O,B-Interface,O,O,O,O,O,B-Interface,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Interface,O,O,O,B-Network Function,O,O,B-Message,O,O,B-Interface,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Interface,I-Interface,I-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,B-Interface,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,B-Network Function,O,O,O,B-Network Function,I-Network Function,O,O,O,O