CN-122001698-A - Application Programming Interface (API) object-level based API billing

Abstract

Embodiments of the present disclosure relate to Application Programming Interface (API) charging based on API object levels. A method performed by an Application Programming Interface (API) opening function (AEF) in an API framework (CAPIF) is provided. The method includes receiving a request from an API caller to call a service API for an API object lifecycle or access operation of the API object. The method includes determining that an API object lifecycle or access operation is associated with at least one API object-related trigger condition of a satisfied charging event. The method includes triggering CAPIF a core function to report charging information for a charging event to a charging function. And the method includes sending a response to the request to the API caller.

Inventors

• U. Laushenbach
• J. A. Pereira Rodriguez

Assignees

• 诺基亚技术有限公司

Dates

Publication Date

20260508

Application Date

20251029

Priority Date

20241101

Claims (20)

1. 1. An apparatus for implementing an API open function, AEF, in a generic application programming interface, API, framework CAPIF, the apparatus comprising: at least one memory configured to store instructions, and At least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus at least to: receiving a request from an API caller to call an API object lifecycle of the API object or a service API of an access operation; determining that the API object lifecycle or access operation is associated with at least one API object related trigger condition of a satisfied charging event; Triggering CAPIF a core function to report charging information for the charging event to a charging function, and And sending a response to the request to the API calling party.
2. 2. The apparatus of claim 1, wherein the service API is one of at least one service API provided by the AEF and available for invocation.
3. 3. The apparatus of claim 1, wherein the API object is created by an API producer and persistently stored in a container of the API producer.
4. 4. The apparatus of claim 1, wherein the API object is a subscription resource of the service API, the subscription resource comprising one or more trigger conditions for one or more notifications generated by the subscription resource.
5. 5. The apparatus of claim 1, wherein the request is for an API object lifecycle operation, and the API object lifecycle operation is an API object creation operation or an API object deletion operation.
6. 6. The apparatus of claim 1, wherein the request is for an API object access operation, and the API object access operation is an API object read operation or an API object update operation.
7. 7. The apparatus of claim 6, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further collect API consumption information related to the API object access operations on the API object, and Wherein the CAPIF core function is triggered to report the charging information including the API consumption information.
8. 8. The apparatus of claim 1, wherein the at least one API object related trigger condition comprises the request for the API object lifecycle or access operation, and when the request is received, the CAPIF core function is triggered to report the billing information.
9. 9. The apparatus of claim 1, wherein the at least one API object related trigger condition comprises the response to the request for the API object lifecycle or access operation, and the CAPIF core function is triggered to report the billing information when the response is sent.
10. 10. The apparatus of claim 1, wherein the at least one API object related trigger condition includes the request for the API object lifecycle or access operation and the response to the request for the API object lifecycle or access operation, and the apparatus is caused to trigger the CAPIF core function comprises the apparatus is caused to: triggering the CAPIF core function to report initialized charging information indicating a cell reservation for the charging event when the request is received, and When the response is sent, the CAPIF core function is triggered to report charging information indicating termination of the unit reservation.
11. 11. An apparatus for implementing core functions of a generic application programming interface API framework CAPIF, the apparatus comprising: at least one memory configured to store instructions, and At least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus at least to: receiving at least one trigger from an API open function, AEF, the at least one trigger indicating that at least one API object-related trigger condition of a charging event is satisfied, the at least one API object-related trigger condition being associated with an API object lifecycle or access operation of an API object of a service API for an API object lifecycle or access operation call; Determining charging information for the charging event based on the at least one trigger; Reporting the charging information to a charging function for a charging process, and A response is received from the charging function indicating a result of the charging process.
12. 12. The apparatus of claim 11, wherein the billing information is reported to the billing function by or via a billing trigger function or a billing enabled function.
13. 13. The apparatus of claim 11, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to further send a notification to the AEF indicating the result of the billing process.
14. 14. The apparatus of claim 11, wherein the API object is created by an API producer and persistently stored in a container of the API producer.
15. 15. The apparatus of claim 11, wherein the API object is a subscription resource of the service API, the subscription resource comprising one or more trigger conditions for one or more notifications generated by the subscription resource.
16. 16. The apparatus of claim 11, wherein the service API is invoked by the service API call request received by the AEF from an API caller for the API object lifecycle or access operation of the API object, and a response to the request is sent by the AEF to the API caller.
17. 17. The apparatus of claim 16, wherein the request is for an API object lifecycle operation, and the API object lifecycle operation is an API object creation operation or an API object deletion operation.
18. 18. The apparatus of claim 16, wherein the request is for an API object access operation, and the API object access operation is an API object read operation or an API object update operation.
19. 19. The apparatus of claim 16, wherein the at least one API object related trigger condition comprises the request for the API object lifecycle or access operation, and Wherein when the request is received by the AEF from the API caller, the at least one trigger is received and the billing information is determined and reported.
20. 20. The apparatus of claim 16, wherein the at least one API object related trigger condition comprises the response to the request for the API object lifecycle or access operation, and Wherein the at least one trigger is received and the billing information is determined and reported when the response is sent by the AEF to the API caller.

Description

Application Programming Interface (API) object-level based API billing Technical Field The present disclosure relates generally to telecommunications, and more particularly to processes in a generic Application Programming Interface (API) framework for API charging based on API objects. Background A telecommunication system may be seen as a facility that enables communication sessions between two or more entities, such as user terminals, base stations and/or other nodes, by providing carriers between the various entities involved in the communication path. The telecommunication system may be provided, for example, by a communication network and one or more compatible communication devices. The communication session may include, for example, data communications for carrying communications such as voice, video, electronic mail (email), text messages, multimedia, and/or content data. Non-limiting examples of services provided include bi-directional or multi-way calls, data communications or multimedia services, and access to data network systems such as the internet. In a wireless telecommunication system, at least a portion of a communication session between at least two stations occurs over a wireless link. Examples of wireless telecommunication systems include Public Land Mobile Networks (PLMNs), satellite-based communication systems, and different wireless local area networks, such as Wireless Local Area Networks (WLANs). Some wireless systems may be divided into cells and are therefore commonly referred to as cellular systems. The user may access the telecommunications system through an appropriate communication device or terminal. The user's communication equipment may be referred to herein as a User Equipment (UE) or user equipment. The communication device is provided with suitable signal receiving and transmitting means for enabling communication, e.g. enabling access to the communication network via an access node of the communication network or enabling communication directly with other user devices. A communication device may access a carrier provided by a station (e.g., a base station of a cell) and transmit and/or receive communications on the carrier. A telecommunications system and associated equipment typically operate in accordance with a given standard or specification which sets out what the various entities associated with the telecommunications system are permitted to do and how that should be achieved. Communication protocols and/or parameters which are used to connect the various entities are also typically defined. One example of a telecommunication system is the Universal Mobile Telecommunication System (UMTS). Other examples of telecommunication systems are Long Term Evolution (LTE) networks, LTE advanced networks and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3 rd generation partnership project (3 GPP). Disclosure of Invention Example implementations of the present disclosure relate to telecommunications, and more particularly, to processes in a universal Application Programming Interface (API) framework for API charging based on API objects. The present disclosure includes, but is not limited to, the following example implementations. Some example implementations provide an apparatus implementing an API open function (AEF) in a universal Application Programming Interface (API) framework (CAPIF) that includes at least one memory configured to store instructions, and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus at least to receive a request from an API caller to call an API object lifecycle of an API object or a service API of an access operation, determine that the API object lifecycle or the access operation is associated with at least one API object-related trigger condition of a satisfied billing event, trigger CAPIF a core function to report billing information of the billing event to the billing function, and send a response to the request to the API caller. Some example implementations provide a method performed by an Application Programming Interface (API) open function (AEF) in an API framework (CAPIF) that includes receiving a request from an API caller to call a service API for an API object lifecycle or access operation of the API object, determining that the API object lifecycle or access operation is associated with at least one API object-related trigger condition for a satisfied charging event, triggering CAPIF a core function to report charging information for the charging event to the charging function, and sending a response to the request to the API caller. Some example implementations provide an apparatus implementing a universal Application Programming Interface (API) framework (CAPIF) core function, the apparatus including at least one memory configured to store instructions, and at least one processing circuitry configured to access the at least