Methods, apparatus and computer programs for communication

By extending the CAPIF framework to provide quantum computing service subscriptions and secure credential management, the problem of the lack of standardized open quantum computing services in communication networks is solved, and secure and controllable access to terminal devices is achieved.

CN123075427APending Publication Date: 2026-11-10NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610592615.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-30
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

The lack of standardized mechanisms in existing communication networks to open up quantum computing services to end users makes it impossible to effectively utilize quantum computing capabilities.

Method used

By extending the core functionality (CCF) of the Universal Application Programming Interface Framework (CAPIF), the subscription and secure credential management of quantum computing services are enabled, allowing terminal devices to access and receive related services.

Benefits of technology

It enables secure and controllable access to quantum computing services and other available services to terminal devices across networks, meeting the needs of different scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123075427A_ABST
    Figure CN123075427A_ABST
Patent Text Reader

Abstract

A method, apparatus, and computer program for communication are provided, which causes the apparatus to perform: sending a request to a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device to subscribe to the device for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); and receiving a security credential from the CCF device, the security credential being used to authorize the device to access the CCF for receiving the first service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Various exemplary embodiments of this disclosure relate to a method, apparatus, system, and computer program, and particularly, but not exclusively, to an entity for receiving a first service by exposing functionality through an application programming interface (API). Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of a communication network. Communication devices may be served by application servers.

[0003] Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of these standards are the so-called 5G (fifth generation) and 6G (sixth generation) standards provided by 3GPP.

[0004] Modern communication network environments can have various types of networks (e.g., 5G core networks, 5G radio access networks, cloud computing networks, edge computing networks, public networks, private networks, etc.) that are interconnected to enable entities (e.g., users, applications, user equipment, network functions, etc.) to communicate with each other for a purpose within and / or across different types of networks. For example, an entity may need to access the services of another entity in one of these networks; for instance, an application may need to communicate with another application. Typically, access to a given application is facilitated through an Application Programming Interface (API). Therefore, an entity may first need to obtain access to the application's API, for which it seeks to utilize the corresponding services.

[0005] An API can be viewed as a mechanism that enables at least two applications to communicate with each other using a set of definitions and protocols, where applications can be considered software components with different services. Therefore, an API can be seen as a service contract between two applications that defines the various requests and responses that can be exchanged between them. API architectures are typically built from a client and server perspective. The application sending the request is called the client, and the application sending the response is called the server. Summary of the Invention

[0006] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of embodiments of this disclosure, nor are they intended to be used to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure.

[0007] According to a first aspect, an apparatus is provided, the apparatus comprising: at least one processor; and at least one memory including code, which, when executed by the at least one processor, causes the apparatus to perform: sending a request to a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device for subscribing to the apparatus for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); and receiving a security credential from the CCF device for authorizing the apparatus to access the CCF for receiving the first service.

[0008] According to a second aspect, an apparatus is provided, the apparatus including components for performing: sending a request to a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device to subscribe to the device for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); and receiving a security credential from the CCF device for authorizing the device to access the CCF for receiving the first service.

[0009] According to a third aspect, a method for a device is provided, the method comprising: sending a request to a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device to subscribe to the device for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); and receiving a security credential from the CCF device for authorizing the device to access the CCF for receiving the first service.

[0010] According to a fourth aspect, an apparatus is provided, comprising: a transmitting circuitry for sending a request to a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device for subscribing to the device, for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); and a receiving circuitry for receiving a security credential from the CCF device, the security credential being used to authorize the device to access the CCF for receiving the first service.

[0011] The following may apply to any one of the first to fourth aspects (e.g., one or more aspects, including all aspects).

[0012] The device can also be made to perform the following: when an application residing on the device outputs a request for a first service, the device is determined at a middleware component of the device to have authorization information for authorizing the device to receive the first service, wherein the authorization information is sent to the AEF when the first service is requested based on a request output by the application.

[0013] The device may also be made to perform: for each of a plurality of services, obtaining information indicating a description of the service and at least one condition for the device to use the service, wherein the plurality of services includes a first service; outputting a description of the first service and at least one first condition for the device to use the first service via a user display of the device; and receiving input via user input of the device, the input indicating whether the user of the device agrees that at least one first condition is met, wherein sending a request for authorization is performed based on the input indicating that the user of the device agrees that at least one first condition is met.

[0014] The subscription request may include an indication that the user device's user consents to at least one first condition is met.

[0015] Obtaining information may include: sending a request to the CCF device for information indicating which services are available to the device; and receiving information from the CCF device, for each of a plurality of services, the information indicating a description of the service and at least one condition for the device to use the service.

[0016] Sending a request for information indicating which services are available to the device can be performed by middleware configured on the device, and receiving the information is performed by a resource owner function configured on the device, wherein for each of a plurality of services, the information indicates a description of the service and at least one condition for the device to use the service.

[0017] The device can also be made to perform: an instruction that a user receiving the device has withdrawn their consent to at least one first condition being met; and, based on the received instruction that a user has withdrawn their consent to at least one first condition being met, delete at least one of the security credentials or authorization information.

[0018] According to a fifth aspect, an apparatus is provided, comprising: at least one processor; and at least one memory including code, which, when executed by the at least one processor, causes the apparatus to perform: receiving from a user equipment a request to subscribe to the user equipment for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); sending the request to an authorization function, the authorization function being delegated to generate security credentials enabling the apparatus to be authorized to receive the service via the AEF; receiving from the authorization function security credentials enabling the user equipment to receive the first service; and sending the security credentials to the user equipment.

[0019] According to a sixth aspect, an apparatus is provided, the apparatus comprising components for performing: receiving from a user equipment a request to subscribe to the user equipment for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); sending the request to an authorization function, the authorization function being delegated to generate security credentials enabling the apparatus to be authorized to receive the service via the AEF; receiving from the authorization function security credentials enabling the user equipment to receive the first service; and sending the security credentials to the user equipment.

[0020] According to a seventh aspect, a method for an apparatus is provided, the method comprising: receiving from a user equipment a request to subscribe to the user equipment for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); sending the request to an authorization function, the authorization function being delegated to generate security credentials enabling the apparatus to be authorized to receive the service via the AEF; receiving from the authorization function security credentials enabling the user equipment to receive the first service; and sending the security credentials to the user equipment.

[0021] According to an eighth aspect, an apparatus is provided, comprising: a receiving circuitry for receiving from a user equipment a request to subscribe to the user equipment, for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); a sending circuitry for sending the request to an authorization function, the authorization function being delegated to generate security credentials enabling the apparatus to be authorized to receive the service via the AEF; a receiving circuitry for receiving from the authorization function security credentials enabling the user equipment to receive the first service; and a sending circuitry for sending the security credentials to the user equipment.

[0022] The following may apply to any one of the above aspects from fifth to eighth (e.g., one or more aspects, including all aspects).

[0023] The apparatus may also be made to perform: receiving from a user equipment a request for information, for each of a plurality of services, the information indicating a description of the service and at least one condition for the user equipment to use the service, wherein the plurality of services includes a first service; and providing the requested information to the user equipment, for each of the plurality of services, the information indicating a description of the service and at least one condition for the apparatus to use the service, wherein the plurality of services includes a first service.

[0024] The subscription request may include an indication that at least one condition associated with the user's device and receipt of the first service is met.

[0025] According to a ninth aspect, an apparatus is provided, comprising: at least one processor; and at least one memory including code, which, when executed by the at least one processor, causes the apparatus to perform: receiving a request from a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device for subscribing to and / or authorizing a user device for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); determining that the user device is authorized to receive the first service; and providing the CCF device with at least one of a security credential or authorization information for authorizing the user device to receive the first service.

[0026] According to an eighth aspect, an apparatus is provided, the apparatus comprising components for performing: receiving from a Universal Application Programming Interface Framework (CAPIF) Core Function (CCF) device a request to subscribe to and / or authorize a user equipment for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); determining that the user equipment is authorized to receive the first service; and providing the CCF device with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.

[0027] According to the eleventh aspect, a method for an apparatus is provided, the method comprising: receiving from a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) apparatus a request for subscribing to and / or authorizing a user equipment for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); determining that the user equipment is authorized to receive the first service; and providing the CCF apparatus with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.

[0028] According to a twelfth aspect, an apparatus is provided, comprising: a receiving circuitry for receiving a request from a Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device for subscribing to and / or authorizing a user equipment, for receiving a first service identified in the request via an Application Programming Interface Open Function (AEF); a determining circuitry for determining that the user equipment is authorized to receive the first service; and a providing circuitry for providing the CCF device with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.

[0029] The following may apply to any one of the above aspects 9 through 12 (e.g., one or more aspects, including all aspects).

[0030] The device can also be made to: receive a request from the AEF to verify whether the authorization information is still valid; and provide the AEF with an indication that the authorization information is still valid.

[0031] The device can also be made to: receive a request from the AEF to verify whether the authorization information is still valid; and provide the AEF with an indication that the authorization information is invalid.

[0032] The device may also be made to perform at least one of the following: determine that a user of the user equipment has withdrawn their consent to meet one or more conditions for using the first service; or determine that the validity period associated with the authorization information has expired, wherein the indication that the authorization information is invalid is based on at least one of the preceding two determinations.

[0033] Requests for subscription and / or authorization may include an indication that at least one condition associated with the user's consent to receive the first service has been met.

[0034] The following may apply to any one of the first to twelfth aspects (e.g., one or more aspects, including all aspects).

[0035] The first service may be provided by at least one of the following: quantum computing-based application capabilities, artificial intelligence and / or machine learning-based application capabilities, or service provision.

[0036] According to one aspect, a non-transitory computer-readable medium is provided comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any one of the preceding aspects.

[0037] Many different embodiments have been described above. It should be understood that further embodiments may be provided by combination of any two or more of the embodiments described above. Attached Figure Description

[0038] Some exemplary embodiments will now be described by way of non-limiting and illustrative example only, with reference to the accompanying drawings, in which:

[0039] Figure 1 A representation of the communication system is shown;

[0040] Figure 2 The illustration shows examples of some of the embodiments. Figure 1 The representation of a communication system device;

[0041] Figure 3A and Figure 3B The diagram illustrates a sample Common Application Programming Interface Framework (CAPIF) configuration;

[0042] Figure 4 The illustration shows an example authorization configuration;

[0043] Figure 5 The illustration shows an example of the service offered;

[0044] Figure 6 The illustrations show example methods that can be performed between the devices described herein;

[0045] Figures 7 to 9 The illustrations show example methods that can be performed by the apparatus described herein; and

[0046] Figure 10 An example apparatus is illustrated that can perform one or more of the methods described herein. Detailed Implementation

[0047] Recent 3GPP studies have considered using quantum computing (QC) services to provide one or more of a variety of different functions. Quantum computing (QC) services involve computing systems that provide services that directly utilize quantum mechanical phenomena such as superposition and entanglement to perform complex and computationally expensive operations on data.

[0048] For example, a process performed on a user equipment (UE) that can benefit from QC capabilities available elsewhere in a computing service provider (CSP) network may include at least one of the following: • Random number generation (RNG); • Machine learning (ML) model training and / or ML inference; • Queue resource management; • Solve difficult optimization problems; • Resource allocation; • Radio channel estimation; or • Channel State Information (CSI) compression, CSPs can be viewed as entities that design, build, and operate communication services. These CSPs are responsible for ensuring the quality of service requirements during the operation of the communication services and for meeting expectations of automation and efficiency.

[0049] Being able to expose these QC capabilities to end users to provide services to (multiple) end users would be useful for a range of scenarios, including, for example, secure banking applications, energy-efficient machine learning, etc.

[0050] Furthermore, in the near future, QC infrastructure will likely be available to high-end companies, allowing their infrastructure to be used to provide QC services to UEs in order to monetize QC capabilities: for example, random number generation (RNG) using QC is a service associated with various applications in the UE, because the RNG process performed via QC is more unpredictable than the process performed by low-capability devices such as smartphones.

[0051] However, although QC has been considered for 6G, there is currently no standard available to open up quantum capabilities as a service to end users.

[0052] The following aims to provide one or more methods related to resolving these issues. In particular, the following aims to utilize and modify the current framework to allow QC services to be delivered to user equipment across the network.

[0053] Furthermore, one or more of these methods can be used to provide non-QC services to the UE, where the non-QC services are provided via a third-party domain (e.g., which may be exposed to the user via API Open Functions (AEF)). Therefore, it should be understood that references to quantum computing below also include one or more other services available via API Open Functions. These can be indicated by the example service list above, which may be available via CSP.

[0054] Although these principles will be explained in more detail below, the following provides an example of a communication environment in which the technologies described herein can be deployed. It should be understood that this communication environment is not restrictive and is only used to provide at least one example of where such technologies can be deployed.

[0055] In other words, in the following text, various example embodiments are explained with reference to communication devices capable of communicating with a communication system, such as those described below. Figures 1 to 4 As shown in the diagram.

[0056] Figure 1 A communication network environment 100 in which one or more illustrative embodiments may be implemented is illustrated. As shown, the communication network environment 100 includes a plurality of networks 102-1, 102-2, 102-3, ..., 102-N that are operatively coupled to each other via one or more communication networks 104.

[0057] Although not shown, it should be understood that each network may include one or more network nodes configured to communicate with at least one other network node and / or at least one terminal device.

[0058] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile device, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), machine-type communication (MTC) devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), data consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Terminal devices may also correspond to the mobile terminal (MT) portion of an integrated access and backhaul (IAB) node (e.g., a relay node). In the following description, the terms “terminal equipment”, “communication equipment”, “terminal”, “user equipment”, “user device” and “UE” are used interchangeably.

[0059] As used herein, the terms “network node” and / or “network device” are used interchangeably with “network access node” and refer to a node in a communication network through which terminal devices access the network and receive services. Network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio header (RRH), a relay, an integrated access and backhaul node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN), or non-terrestrial network equipment such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary orbit (GEO) satellites, aircraft network equipment, etc., depending on the terminology and technology applied. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. The IAB node consists of: the mobile terminal (IAB-MT) part, which behaves like a UE to the parent node; and the DU part of the IAB node, which behaves like a base station to the next-hop IAB node.

[0060] Communication in communication environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local area network communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM), and / or any other technologies currently known or to be developed in the future.

[0061] As described above, a communication network environment (such as communication network environment 100) can have various types of networks (e.g., 5G core network, 5G radio access network, cloud computing network, edge computing network, public network, private network, etc.), such as networks 102-1, 102-2, 102-3, ..., 102-N, etc. These networks are interconnected to enable entities (e.g., users, applications, user equipment, network functions, etc.) to communicate with each other for a certain purpose within and / or across different types of networks. Each network 102-1, 102-2, 102-3, ..., 102-N can be considered to have or represent a domain; however, in some embodiments, one or more of the networks 102-1, 102-2, 102-3, ..., 102-N can have or represent multiple domains. By way of example only, a domain can be a logical and / or physical grouping of one or more network services, one or more network components, one or more network functions, etc., with one or more common purposes.

[0062] Accordingly, an entity may need to access the services of another entity in one of the domains of one or more networks 102-1, 102-2, 102-3, ..., 102-N. For example, an application may need to communicate with another application. As further mentioned, access to a given application is facilitated through an API. However, an entity may first need to obtain access to the application's API for that application, for which the entity seeks to utilize its corresponding services. It should be recognized that there should be processes in place to ensure the security of API access within the communication network environment (e.g., communication privacy, identity verification, etc.).

[0063] 3GPP introduced a common framework for handling API-related requests. This common framework is called the Common API Framework (CAPIF).

[0064] More specifically, CAPIF was originally specified by 3GPP in Rel-15 to provide a framework for accessing the Northbound 3GPP API, which is an API that allows applications residing on the UE to use the communication network to perform specific services using an API provider.

[0065] The 3GPP specification for CAPIF defines three types of entities: a) An API provider is an entity that exposes one or more APIs. API providers are also known as API Open Functions (AEFs) (for example, in 5G networks, AEFs can be implemented by Network Open Functions or NEFs). b) The API caller, which is an entity that consumes one or more APIs; and c) CAPIF Core Functionality (CCF), which manages the interaction between AEF and API callers.

[0066] The 3GPP framework in Figure 3A and Figure 3B The image is shown in the middle. Specifically, Figure 3A The diagram illustrates the functional safety architecture for the CAPIF framework, where the resource owner is aware of northbound API access (RNAA), and Figure 3B Considered Figure 3A The two such CAPIF fields shown are interconnected. Figure 3A It is described more fully in 3GPP TS 33.122.

[0067] For example, the northbound interface is an API that enables lower-level network layers or components to communicate with higher-level network layers or components, while the southbound interface enables higher-level network layers or components to communicate with lower-level network layers or components.

[0068] Figure 3A The diagram illustrates a trusted domain, which includes: at least one resource owner function 301, CAPIF core functions 302 (including authorization function 302A and at least one CAPIF interface 302B), API provider domain 303 (including API management function 303A, API publishing function 303B, API opening function 303C and at least one service API 303D), and a first API caller 304. Figure 3A The diagram also illustrates the second API caller 305 located outside the trusted domain, as well as the various interfaces between the entities mentioned here.

[0069] Figure 3A This framework can use the authorization mechanism defined in the OAuth 2.0 framework. (Refer to...) Figure 3ABefore explaining this mechanism using specific entities, please refer to the brief overview of the OAuth 2.0 framework. Figure 4 Explained.

[0070] Figure 4 The diagram illustrates signaling that can be exchanged between at least two of the resource owner 401, user agent 402, and authorization server 403 or client 404.

[0071] More specifically, the following signaling service operations are defined: • Client identifier and redirection Uniform Resource Identifier service operation 405, which is passed from client 404 to authorization server 403 via user agent 402; • User authentication service operation 406, which is transmitted from the authorization server 403 to the resource owner 401 via the user agent 402; • Authorization code service operation 407, which is transmitted from the authorization server 403 to the client 404 via the user agent 402; • The authorization code and redirect URI 408, which is passed from the client (404) to the authorization server (403); and • Access token 409, which is passed from the authorization server 403 to the client 404. It should be understood that the terms "access token" and "security object" are used interchangeably herein. An access token can be understood as a value and / or signal that can be used to obtain access to some service or function (e.g., security service or security function). 3GPP TS 33.122 describes access tokens and / or security objects.

[0072] These five service operations 405 to 409 represent the signaling executed when the authorization server 403 authenticates the client 404.

[0073] More specifically, client 404 initiates the flow by redirecting the resource owner's user agent to the authorization endpoint in service operation 405 using the client identifier and redirection URI. The client includes its client identifier, the scope of the request to be authenticated, the client's local state, and the redirection URI, which the authorization server will send back to the user agent after access is granted (or denied).

[0074] The authorization server 403 uses the user authentication service operation 406 to authenticate the resource owner (via the user agent) to determine whether the resource owner 401 should grant or deny the client's access request.

[0075] Assuming the resource owner grants access with a 401 permission, the authorization server redirects the user agent back to the client using a previously provided redirect URI (e.g., in a 405 request or during signaling executed during client registration). The redirect URI includes an authorization code of 407 and any local state provided by the client.

[0076] The client, after encountering a 404 error, then requests an access token from the authorization server's token endpoint by including the stolen authorization code received in the previous step during the 408 signaling. The 408 signaling may include a redirect URI used to obtain the authorization code for verification.

[0077] The authorization server authenticates the client, verifies the authorization code, and ensures that the redirect URI received by the client matches the URI used to redirect the client. If valid, the authorization server responds to the client with an access token 409 and returns a 404 response. Although not shown, this signaling may optionally include a refresh token, which can be used to regenerate an access token when the access token in the 409 response expires.

[0078] Figure 4 The authorization method utilizes several concepts related to authorization, including: authorization code, implicit, resource owner password credentials, and client credentials.

[0079] More specifically, an authorization permission is a credential representing the resource owner's authorization (to access their protected resources), which the client uses to obtain an access token. Currently, four permission types are defined: authorization code, implicit, resource owner cryptographic credentials, and client credentials. An extensibility mechanism is also provided for defining other types of authorization permissions.

[0080] As described in Section 6.5.3 of 3GPP TS 33.122, this authentication and authorization method is already available for use. Figure 3A The CAPIF framework.

[0081] According to the 3GPP technical specifications, RNAA will use the OAuth 2.0 framework with the following roles to use token-based authorization: - The API caller has the role of an OAuth 2.0 client. - CCF acts as an OAuth 2.0 authorization server, that is, it provides access tokens used for RNAA. - AEF has the role of a resource server. - Depending on the use case and regulations, the resource owner can be a user of the UE or the owner of the subscription. If the resource is associated with a UE, the resource owner ID is specified as the corresponding UE's GPSI.

[0082] For API caller authorization, the following OAuth 2.0 flow can be used: a) Client credential stream (according to RFC 6749). b) Licensed bitstream (in accordance with RFC 6749), or c) An authorized bitstream with a proof key for code exchange (PKCE) (in accordance with RFC 7636).

[0083] Regarding the latter option (c), when the authorization stream (optionally having PKCE) is used by the API Open Function (AEF) to authorize API callers, it follows RFC 6749 (e.g., as referenced above). Figure 3A The procedures described in (and optional in RFC 7636) and RFC 7636.

[0084] As an example, an end user (e.g., the "resource owner" in this example) is playing a time-sensitive game using a gaming application (e.g., an API caller, also referred to as the OAuth 2.0 client in this document) and desires high-quality, low-latency communication for a better service experience. In this scenario, the gaming application (API caller) sends an authorization request to the CAPIF Core Function (CCF), which is configured to operate as an authorization function. The CCF obtains the end user's (resource owner's) consent and provides the gaming application (API caller) with an authorization code. The gaming application can use this authorization code to obtain an access token from the CCF.

[0085] Figure 3B The diagram shows Figure 3A How the CAPIF framework can be extended to consider multiple trusted domains. For clarity and brevity, Figure 3B The corresponding entity in the and Figure 3A The same references are used for different fields; unquoted references are used in the first field, and quoted references are used in the second (different) field. However, except... Figure 3A In addition to the interface, Figure 3B The diagram also illustrates the interface 320'' between CCFs located in different domains. This interface 320'' is typically labeled CAPIF-6e and / or CAPIF-6.

[0086] Figure 2 This is a block diagram illustrating the computational architecture of various participants in a method according to an illustrative embodiment. More specifically, system 200 is shown as including entities 202-1, ..., 202-N. For example, in the illustrative embodiment and with reference to... Figures 3A to 4Entities 202-1, ..., 202-N can be the API caller, the first CCF / CCF-B, the second CCF / CCF-A, the resource owner, and the AEF, respectively. It should be understood that entities 202-1, ..., 202-N are configured to interact to provide security management and other technologies described herein.

[0087] Each of entities 202-1, ..., 202-N (referred to individually or collectively as 202 herein) includes a processor 222 (222-1, ..., 222-N) coupled to a memory 226 (226-1, ..., 226-N) and interface circuitry 220 (220-1, ..., 220-N). Each processor 222 of each entity 202 includes a security management processing module 224 (224-1, ..., 224-N), which may be implemented at least partially in the form of software executed by the processor 222. The security management processing module 224 performs security management operations in conjunction with the following figures and otherwise described herein. Each memory 226 of each entity 202 includes a security management storage module 228 (228-1, ..., 228-N) storing data generated or otherwise used during security management operations.

[0088] Processor 222 may include, for example, a microprocessor, such as a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP) or other types of processing, and portions or combinations of such elements.

[0089] Memory 226 can be used to store one or more software programs that are executed by a corresponding processor 222 to implement at least a portion of the functions described herein. For example, security management operations and other functions, in conjunction with the following figures and other descriptions herein, can be implemented in a direct manner using software code executed by processor 222.

[0090] Therefore, a given memory in memory 226 can be considered as an example of what is more generally referred to herein as a computer program product, or more generally as a computer or processor-readable (non-transitory or storage) medium having executable program code embodied therein. Other examples of computer or processor-readable media may include magnetic disks or other types of magnetic or optical media, including any combination thereof. Illustrated embodiments may include articles of manufacture that include such computer program products or other computer or processor-readable media.

[0091] Furthermore, for example, memory 226 may more specifically include electronic random access memory (RAM), such as static RAM (SRAM), dynamic RAM (DRAM), or other types of volatile or non-volatile electronic memory. The latter may include, for example, non-volatile memory, such as flash memory, magnetic RAM (MRAM), phase-change RAM (PC-RAM), or ferroelectric RAM (FRAM). The term "memory" as used herein is intended to be interpreted broadly and may additionally or alternatively include, for example, read-only memory (ROM), disk-based memory, or other types of storage devices, and portions or combinations thereof.

[0092] Interface circuitry 220 schematically includes a transceiver or other communication hardware or firmware that allows associated system components to communicate with each other in the manner described herein.

[0093] from Figure 2 As can be clearly seen, multiple entities 202 are configured to communicate with each other as security management participants via their respective interface circuits 220. This communication involves each participant sending data to and / or receiving data from one or more other participants. The term "data" as used herein is intended to be interpreted broadly to cover any type of information that can be sent between participants, including but not limited to: identification data, key pairs, key indicators, tokens, secrets, security management messages, registration request / response messages and data, request / response messages, authorization and / or authentication request / response messages and data, metadata, control data, audio, video, multimedia, consent data, other messages, etc.

[0094] It should be understood that Figure 2 The specific arrangement of the components shown is merely an example, and many alternative configurations can be used in other embodiments. For example, any given entity 202 can be configured to incorporate additional or alternative components and support other communication protocols.

[0095] Additionally, entities such as third-party applications and network operators can participate in the methods described herein via computing devices configured to include components such as processors, memory, and network interfaces. These components and devices do not need to be implemented on separate, independent processing platforms, but can, for example, represent different functional parts of a single, general-purpose processing platform.

[0096] More generally, Figure 2This can be viewed as representing a processing device configured to provide corresponding security management functions and operably coupled to each other in a communication network environment. By way of example only, all or part of each of the multiple entities 202 (e.g., processors and memory) can be viewed as examples of components used to perform one or more operations, steps, functions, processes, etc., described herein. To manage the many APIs that may exist in a communication network environment (e.g., communication network environment 100), 3GPP defines the Common API Framework (CAPIF). See, for example, TS23.222, TS 33.122, and TS 29.222. More specifically, CAPIF includes in its northbound interface the logic and processes used to manage APIs exposed by 3GPP networks (e.g., networks 102-1, 102-2, 102-3, ..., 102-N).

[0097] As mentioned above, it is useful to provide one or more methods for allowing applications to access third-party services, such as quantum computing (QC) services available via API open functionality.

[0098] The following aims to address one or more of the issues mentioned above.

[0099] Specifically, the following describes one or more methods for allowing the CAPIF framework to be used to access one or more services that can be accessed via API open functionality.

[0100] More specifically, and using the terminology mentioned above with reference to the CAPIF framework, this includes details of the API caller's device being configured to obtain, via the CCF, details of one or more services available via one or more API providers. One or more API providers may be accessible via one or more AEFs, but it should be understood that the CCF can provide information about services available via one or more 3GPP network entities (e.g., services available without going through one or more AEFs).

[0101] The device may output information related to one or more services via its output (e.g., via a display screen and / or via audio output). This information may indicate one or more permissions, terms, or conditions to be agreed to before the service is provided. For example, the information may indicate one or more data that will be shared by the device with one or more API providers when the service is provided. The device may receive input via its input (e.g., via a display screen, keyboard, or audio input). This input may indicate whether the user of the device agrees to one or more permissions, terms, or conditions.

[0102] When input indicates that the user of the device has agreed to one or more permissions, terms, or conditions, the device may pre-authorize the device and / or the user to receive one or more services via CCF through one or more API providers. This pre-authorization may be referred to herein as a "subscription". The subscription may provide the device with one or more security credentials (e.g., referred to below as a client identifier and secret) for accessing one or more subscribed services.

[0103] The device can then determine whether a service to be provided to an application deployed on it is accessible via one or more AEFs. This can be determined by the device's operating system and / or by the device's middleware. Middleware is software that acts as a layer between the application and the operating system to facilitate communication and data management between them. Based on this determination, the middleware routes requests for the service to one or more AEFs. Requests for the service may include authorization information (e.g., one or more access tokens). An AEF (or another function configured to perform one or more authorization and / or authentication methods) can use the authorization information to determine whether the device and / or user are permitted to authorize the requested service. When the device and / or user are permitted to authorize the requested service, the requested service is provided. When the device and / or user are not permitted to authorize the requested service, the AEF signals the device an indication of service denial.

[0104] At least one of these methods will be described below with reference to one or more implementation examples.

[0105] The following considers one or more examples in the context of quantum computing (QC) services. However, it should be understood that the term is used interchangeably with non-QC services, such as those described above, and the methods described herein are not limited to QC services. For example, the methods described herein can also be applied with reference to services based on artificial intelligence (AI) and / or machine learning (ML).

[0106] In one example, a QC service producer (qServiceProducer) is described, which publishes the availability of one or more QC service (qService) APIs that can be provided by the CAPIF Core Functionality (CCF). Subsequently, a middleware component of the UE, acting as a QC service consumer (qServiceConsumer), can discover the corresponding qServiceProducer(s) and obtain authorization information (e.g., one or more access tokens) for accessing one or more qServices via the one or more qService APIs.

[0107] Multiple processes and / or applications in client devices (such as UEs) can benefit from the exchange / communication between quantum networks and mobile networks, where a quantum network can be viewed as a set of quantum nodes connected via quantum communication channels and auxiliary classical channels for stabilization, timing, and / or routing. The number of such applications is increasing. QC infrastructure can be available to high-end companies, and its services can be leased to low-capability devices (e.g., UEs). For example, RNGs using quantum computing are a service relevant to various applications because RNGs generated by quantum computers are more unpredictable than those generated by conventional computing infrastructure. Additionally, hard optimization problems performed on the UE side (e.g., for resource allocation or channel estimation) can leverage QC capabilities present elsewhere in the network.

[0108] Figure 5 The illustration shows an example of how an application requests a QC service (e.g., random number generation).

[0109] Figure 5 The illustration shows signaling that can be executed between an application 501 located on the UE 500 and a computing service provider (CSP) domain 510. The CSP domain may include a CAPIF provider domain 511 and a quantum computing domain 513, wherein the CAPIF provider domain 511 includes a CCF 512 and the quantum computing domain 513 includes a random number generator 514.

[0110] QC infrastructure may include at least one of the following: • (Multiple) quantum switches; • (Multiple) quantum repeaters; • (Multiple) modular quantum processors; • (Multiple) quantum frequency converters; • (Multiple) authorization servers / functions; and • (Multiple) API gateways, configured as entry points for the QC infrastructure (verifying access credentials and enforcing security rules within the QC domain), and scheduling tasks to the quantum computer.

[0111] QC infrastructure can be deployed on at least one of the following: • Centralized private cloud; • Edge (Quantum-based edge computing); • Public Land Mobile Network (PLMN) domain (e.g., network functionality as a QC input gateway); or • Non-public network (NPN).

[0112] Middleware components may include (multiple) software components on top of the UE operating system (e.g., iOS, Android), and may be at least one of the following: • Self-service mini-program managed / provided by CSP; • Enable clients (typically standardized in 3GPP SA6); or • A TS.43 client standardized in the GSMA TS.43 specification.

[0113] exist Figure 5 In the example, application 501 can determine that a random number should be generated. This determination can be performed based on receiving one or more inputs from the input device to the UE500, such as a keypad, screen pressure, audio signals, etc. This determination can also be performed based on determining that one or more services will be provided by application 501.

[0114] Subsequently, application 501 signals middleware component 502 of UE 500. This middleware component can determine that a random number can be generated via quantum computing domain 513. This determination can be performed by exchanging signaling CCF 512. Based on this determination, middleware component 502 can signal random number generator 514 to obtain random number generation services. Therefore, middleware component 503 can be considered as the entity that oversees where the service requests output by the application are forwarded.

[0115] As an alternative to obtaining a random number generation service via middleware component 502, the UE may have its own random number generation service, which is supported by the operating system 503 deployed on the UE.

[0116] exist Figure 5 In the example, the quantum network can be viewed as an API provider domain, where qServices are consumed via API calls using the HTTP REST protocol, and access to QC capabilities is provided via an API gateway (e.g., providing an entry point).

[0117] Furthermore, applications on the UE can be considered as third-party applications acting as API callers, or as applications on the UE supporting several other third-party applications deployed on the UE. Although not shown, applications acting as API callers can be deployed in the network rather than on the UE.

[0118] In addition, CCF 512 can provide at least qService access control and can also perform one or more additional CCF methods to support at least one of logging, auditing and billing for qService.

[0119] Figure 6 The illustrations show example signaling and actions that can be executed according to one or more methods described in this document.

[0120] Figure 6The illustration depicts at least one method that can be executed among user 601, user agent (e.g., resource owner function) 602, third-party application 603, middleware component 604, CCF 605, authorization function 606, and QC gateway 607. User agent 602, third-party application 603, and middleware component 604 can all be deployed on a device (e.g., UE). Authorization function 606 and QC gateway 607 can be considered as part of a QC infrastructure domain.

[0121] QC Gateway 607 can be viewed as responsible for routing qService API calls to API Exposure Functions (AEFs) within the QC infrastructure domain. It should be understood that the QC Gateway can also be configured to execute one or more methods of the AEF itself as an entry point for qService API calls.

[0122] Furthermore, although QC Gateway 607 and Authorization Function 606 have been described as two distinct functions within the QC infrastructure domain, they can be provided by a single, identical entity within the same domain.

[0123] During 6001, information indicating the availability of the qService API is provided by the API Publication Function (APF). Figure 6 (Not shown in the image) is published to the CCF. The publication process can be as described in 3GPP TS 23.222. The available qService API is available via QC Gateway 607.

[0124] During 6002, middleware component 604 signals to CCF 605. This signaling may include a request for information regarding available qServices provided by the QC domain. This signaling may be executed on at least one of the CAPIF-1 or CAPIF-1e interfaces. The requested information may be high-level information (e.g., information that a user can understand from the device's output). The signaling of 6002 may be executed via a service API directory request. The signaling of 6002 may include the device's identifier, such as the Mobile Station International Subscriber Directory Number (MSISDN). During 6002, middleware component 604 may be considered an API caller. The user 602's identifier (e.g., a General Public Subscription Identifier (GPSI)) may also be included in the signaling of 6002.

[0125] It should be understood that since both middleware components 604 and CCF 605 are controlled by the same CSP, no sensitive information will leave the operator's domain as part of the 6002 signaling.

[0126] CCF 605 can perform authentication steps based on the information received in the signaling of 6002. Upon successful authentication, during 6003, CCF 605 signals the user agent 602. This signaling may include the requested information describing the available services (e.g., a description of available qServices), and any corresponding terms and conditions (T&Cs) and privacy conditions (if any) associated with using each of these services. The signaling of 6003 can be provided via CAPIF-8. In this example, the resource owner function (e.g., the user agent) acts as an end-user-facing function and may also be configured to deliver retrieved directory information, suggest subscribing to one or more services relative to other services in the directory, obtain service subscriptions (as described in more detail below), and process user consent to terms and conditions and / or data sharing for privacy reasons.

[0127] During 6004, the end user 601 and the user agent 602 interact (e.g., via user input to the user device and / or via the display of the user device) to instruct the end user 605 to agree to one or more T&Cs and / or privacy conditions for using one or more services among those indicated in the signaling of 6003.

[0128] For example, user agent 605 may output directory information and / or conditional information to end users (e.g., via push notifications to the operator's self-service application or via network redirection to the operator's portal).

[0129] If the presented service is a QC service, the end user can be presented with information about the available QC capabilities (e.g., RNG, QC-licensed ML training, etc.), as well as T&Cs and any privacy requirements (e.g., user consent must be provided when case-sensitive information for the service needs to be shared).

[0130] End users may also be presented with (e.g., via the user's device display and / or audio output) a list of the benefits of accessing QC capabilities to help end users determine whether they agree to the conditions for using the service.

[0131] End users may accept T&Cs, any supplies provided in the catalog information of Custom 6003, and / or provide user consent (if local regulatory authorities require processing of personal information when consuming QC capabilities). These actions by the end user can be communicated by the user agent 602 via input from the UE.

[0132] Based on the information input to the UE during period 6004, user agent 602 can signal to CCF 605 during period 6005. This signaling in period 6005 can register user equipment and / or users to subscribe to some available qService API.

[0133] In other words, during period 6005, user agent 605 signals a subscription request to CCF 605, which includes information about the following: the user's identifier (e.g., MSISDN), the subset of qService APIs the user wants to subscribe to, and any consent-related information (e.g., validity period, permission granted / rejected consent) given and / or entered by the end user during period 6004.

[0134] It should be understood that the term "subscription" is used in this document based on the TeleManagement™ Forum's understanding (e.g., subscription products, i.e., service APIs), rather than a subscription / notification delivery method.

[0135] During 6006, CCF 605 forwards the subscription request of 6005 to the authorization function 606.

[0136] Assuming that authorization function 606 successfully authorizes the end user to subscribe to the service requested in 6006, then during 6007, authorization function 606 sends a subscription response to the CCF. The subscription response may include security information and / or credential information, which serves as (or is used to derive) authorization credentials when accessing the requested services(s) of the subscription request. The security information and / or credential information may include a client identifier and a secret. Signaling in 6007 may also include a list of services already subscribed to by the user based on the request in 6006.

[0137] It should be understood that when the CCF obtains information about the subscribed qService API through application layer interaction, the delivery of security information can be carried out as described in this article.

[0138] During 6008, CCF 605 forwards the subscription response to middleware component 604.

[0139] During 6009, middleware component 604 (acting as an API caller) performs the access procedure with CCF 605. This can be done as described in 3GPP TS 23.222.

[0140] During 6010, middleware component 604 (acting as the API caller) performs the authentication process with CCF 605. This can be done as described in 3GPP TS 23.222.

[0141] During 6011, the middleware component performs an API discovery process (e.g., qService API discovery). This API discovery process can be performed as described in 3GPP TS 23.222. This API discovery process can provide the middleware component with more detailed information about the qService API (compared to the information retrieved from the catalog in 6003). Details of the endpoint used to access a specific service (e.g., qService) can be obtained during 6011.

[0142] although Figure 6 Not shown, but it should be understood that middleware components (API callers) can be notified (e.g., by the CCF) of new QC services available in the QC domain, and these notifications can then be forwarded to end users, for example, via push notifications in the operator's self-service application (if available) or via enhanced ROF interaction (CAPIF-8). End users can then agree or disagree to renew any existing subscriptions to one or more QC services. The CCF can be configured to limit the number of notifications provided to end users within a predetermined time frame to minimize the frequency of input requests from end users.

[0143] During 6012, the end user interacts with an application residing on the UE (e.g., via user input). This end-user interaction may trigger middleware component 604 to determine during 6013 that one or more tasks can be offloaded to a subscribed service (e.g., in the QC computing domain). The determination in 6013 may be performed based on confirmation of available (and subscribed) services received in 6008.

[0144] During 6014, the middleware component interacts with the authorization function 606 to obtain authorization information (e.g., an access token) for receiving the subscribed service. Since end-user consent has already been provided, no further interaction with the end-user is required (considering the OAuth authorization codestream in RFC 6749 and TS 33.122). The process for obtaining the authorization information can be performed as described in TS 33.122. The signaling of 6014 may include the middleware component, which provides the authorization function with information derived using the aforementioned security information. At the end of 6014, the middleware component includes the access token.

[0145] Although not shown, it should be understood that an end user can withdraw any previously given consent. For example, based on input provided to the UE by end user 601, the device can remove any previously stored security information about the service, where the input indicates that the user's consent to the service has been withdrawn.

[0146] During step 6015, middleware component 604 signals an API call request (e.g., as described in TS23.222) to QC gateway 607. The API call request may be about a QC service that the UE user has subscribed to. The API call request may include the access token of 6014.

[0147] When the QC gateway receives an access token during 6015, the QC gateway may perform at least one of 6016 or 6017 to 6018.

[0148] During 6016, QC Gateway 607 locally verifies the received access token. This can be performed when the access token is self-contained (e.g., a JSON Web Token). As another example, this can be achieved by verifying the token's signature and claims, namely, iss (issuer), aud (audience), and exp (expiration time).

[0149] Between 6017 and 6018, QC gateway 607 uses another function (such as authorization function 606 in this example) to verify the received access token. This can help explain situations where the access token has been revoked between the time it was issued and the time the service was requested.

[0150] During 6017, QC gateway 607 signals authorization function 606. This signaling requests authorization function 606 to verify the access token received during 6015.

[0151] During 6018, the authorization function 606 signals the QC gateway within the indication of whether the access token has been verified by the authorization function at the current time.

[0152] When access tokens are valid as indicated by 6018 and / or 6016, QC gateway 607 enables the UE to access the requested service during 6019. Based on this, a service response, including the service requested by the UE during 6015, is provided to middleware component 605.

[0153] During 6020, the middleware component provides a 601 response to the end user and / or a 6019 response to the requesting application. The information included in this response satisfies the requested service.

[0154] The middleware component can be provided as an ML-based entity. In this case, the middleware component can acquire and / or determine the end user's computing habits (e.g., cycles per second) and / or information about the UE's energy consumption throughout the day. The middleware component can be configured to automatically and / or autonomously recommend network-hosted QC services to the end user when the end user considers which QC services to subscribe to during the 6004 period.

[0155] Furthermore, as mentioned above, while this example considers QC services, it should be understood that the techniques described herein can also be applied to other types of services available via AEF. For example, AI / ML services provided by non-QC domains can be subscribed to as described herein.

[0156] At least one of the above methods is referred to below. Figures 7 to 9 Explained.

[0157] Figure 7 The illustration depicts a method that can be performed by a device. The device may include a UE and / or be included within a UE. The device may be as described in reference... Figure 1 and Figure 10 As described in any of the accompanying figures.

[0158] During 701, the device sends a request to the Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device to subscribe to the device in order to receive the first service identified in the request via the API Open Function (AEF). It should be understood that the request to subscribe to the device may include requests from users subscribing to the device, and / or requests to subscribe to the device itself.

[0159] During period 702, the device receives a security credential from the CCF device, which authorizes the device to access the CCF to receive the first service.

[0160] Access can be viewed as the process of integrating a new API caller into CAPIF. For example, this could include sending an access request that includes the API caller's identifier (e.g., a client identifier acquired during the subscription period), credentials, and a secret. For instance, performing access with CCF could be viewed as including registering the device with CCF as an API caller.

[0161] In other words, during 702, the device receives a security credential from the CCF, which enables the device to register with the CCF to receive the first service.

[0162] When requesting the first service later, the device may send authorization information to the AEF based on (for example, using) security credentials. For example, when performing access with the CCF, the device may use these security credentials (e.g., the aforementioned client identifier and secret) to obtain more detailed information about the requested service. The authorization information may include at least one access token.

[0163] The device can: when an application residing on the device outputs a request for a first service, determine at the middleware component of the device that the device has authorization information (e.g., an access token) for authorizing the device to receive the first service, wherein the authorization information is sent to the AEF when the first service is requested based on a request output by the application.

[0164] As mentioned above, in some examples, user consent can be obtained by referring to accessing the first service. For example, the first service can only be subscribed to if the user has already consented to use it.

[0165] For example, the device can acquire information, for each of a plurality of services, indicating a description of the service and at least one first condition for the device to use the service. The plurality of services may include the first service. The device can output a description of the first service and at least one first condition for the device to use the first service via a user display of the device. The device can receive input via user input indicating whether the user of the device agrees to at least one first condition being met, wherein sending a request for authorization is performed based on the input indicating that the user of the device agrees to at least one condition being met. The at least one condition may include at least one term, at least one condition, and / or at least one privacy condition (e.g., whether the user agrees to share identifiers and / or personal information).

[0166] The authorization request may include an indication that the user device has given user consent to at least one first condition that has been met.

[0167] Obtaining information may include: sending a request to the CCF device for information indicating which services are available to the device; and receiving information from the CCF device, for each of a plurality of services, indicating a description of the service and at least one condition for the device to use the service. This may be in the form of a catalog, as described above.

[0168] Sending a request for information indicating which services are available for the device can be performed by middleware configured on the device. Receiving information can be performed by a resource owner function configured on the device, which, for each of a plurality of services, indicates a description of the service and at least one condition for the device to use the service. The description may be a general description of the service (e.g., in a form that the user can understand when output via the user display of the device).

[0169] The device can receive an indication that the user of the device has withdrawn their consent to at least one first condition being met. This can be received via an application and / or via user input on the device. The device can delete authorization information (e.g., access tokens) and / or security credentials based on the received indication that the user of the device has withdrawn their consent to at least one first condition being met.

[0170] Figure 8 The illustration depicts one or more methods that can be performed by a device. The device may include network functionality. For example, the device may include and / or be included within a CCF device.

[0171] During 801, the device receives a request from the user equipment to subscribe to the user equipment for receiving the first service identified in the request via the API Open Function (AEF). The user equipment may correspond to... Figure 7 The device. This device can be used as described in reference... Figure 1 and Figure 10 Described.

[0172] During 802, the device sends a request to the authorization function to subscribe to the user device. The authorization function is delegated to generate security credentials that enable the device to be authorized to receive services via the AEF. The authorization function can correspond to... Figure 9 The device.

[0173] During 803, the device receives from the authorization function a security credential that enables the user equipment to receive the first service.

[0174] During 804, the device sends security credentials to the user equipment.

[0175] The device can receive requests for information from a user equipment, for each of a plurality of services, the information indicating a description of the service and at least one condition for the user equipment to use the service, wherein the plurality of services includes a first service. The device can provide the requested information to the user equipment, for each of the plurality of services, the information indicating a description of the service and at least one condition for the device to use the service, wherein the plurality of services includes a first service.

[0176] The subscription request may include an indication that at least one condition associated with the user device's user consent and receipt of the first service has been met.

[0177] After sending security credentials to the user equipment Figure 8 The device can perform user equipment access based on security credentials.

[0178] After the access is executed, Figure 8The device can interface between the user equipment and the authorization function to obtain authorization information for authorizing the user equipment to access one or more services subscribed to by the UE.

[0179] Figure 9 The illustration depicts one or more methods that can be performed by a device. The device may include... Figure 8 CCF and / or Figure 7 The UE is a device located in a different management domain, or is included in it. Figure 9 The device may include authorization functionality. This authorization functionality may be for third-party applications deployed on the user's device. The device may be as described in reference... Figure 1 and Figure 10 Described.

[0180] During 901, the device was derived from the Universal Application Programming Interface Framework (CAPIF) Core Functions (CCF) device (e.g., Figure 8 The CCF receives requests to subscribe to and / or authorize user devices for receiving the first service identified in the request via the API Open Function (AEF).

[0181] During 902, the device determines that the user equipment is authorized to receive the first service.

[0182] During 903, the device provides the CCF device with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.

[0183] The device can receive a request from the AEF to verify whether the authorization information is still valid; and can provide the AEF with an indication that the authorization information is still valid. Based on the above example, any reference to authorization information herein may include a reference to the access token.

[0184] The device can receive requests from the AEF to verify whether the authorization information is still valid; and can provide the AEF with an indication that the authorization information is invalid.

[0185] The device can determine that a user of a user equipment has withdrawn their consent to meet one or more conditions for using the first service; or determine that the validity period associated with the authorization information has expired. An indication that the authorization information is invalid can be executed based on at least one of the preceding two determinations.

[0186] Requests for subscription and / or authorization may include an indication that at least one condition associated with the user's consent to receive the first service has been met.

[0187] exist Figures 7 to 9In all the examples above, the first service can be provided by at least one of the following: quantum computing-based application capabilities, artificial intelligence and / or machine learning-based application capabilities. The first service can be provided as a service-as-a-service. For example, the first service can be provided as AI as a service, where AI as a service involves providing AI capabilities and services through a cloud-based platform. Similarly, the first service can be provided as backend as a service, where backend as a service can involve a cloud service model that provides developers with the tools and infrastructure for building and managing application backends.

[0188] While examples may be referred to as "an," "a," or "some" in this disclosure, this does not necessarily mean that the same example is referenced each time, nor does it necessarily mean that a particular feature applies only to a single example. Individual features of different examples may also be combined to provide other examples. Furthermore, when a particular feature, structure, or property is described in conjunction with an example, applying such a feature, structure, or property in conjunction with other examples (whether explicitly described or not) is within the knowledge of those skilled in the art.

[0189] It should be understood that although the terms "first," "second," etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0190] It should be understood that the references to various network functions (e.g., AMF, SMF, etc.) above can be implemented by means of devices performing at least some of the functions associated with these network functions. Furthermore, means configured to implement network functions can also be configured as virtual network function instances implementing those network functions. This means can be a virtual machine provided by the infrastructure of a cloud computing system (e.g., hypervisor, processor, and / or memory). This means can be part of a distributed computing system having multiple computing devices (e.g., servers) communicating with each other via a data network. Any part or all of the operation of a network function can be performed by the same means or different means, such as one or more computing devices in a distributed computing system.

[0191] It should be understood that these devices may include or be coupled to other units or modules, such as radio components or radio heads used in transmission and / or reception, or used for transmission and / or reception. Although these devices have been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0192] It should be noted that while some examples have been described with reference to 5G networks, similar examples can also be applied to other networks and communication systems. Therefore, although some examples have been described above in a non-limiting and illustrative manner, referring to certain example architectures for wireless networks, technologies, and standards, other examples can be applied to any other suitable form of communication system besides those shown and described herein.

[0193] It should also be noted in this document that there are several variations and modifications that can be made to the various examples described herein without departing from the scope of this disclosure.

[0194] As used herein, the phrases “at least one of A or B,” “at least one of A and B,” and “A and / or B” mean (A), (B), or (A and B). For the purposes of this disclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). As used herein, the terms “at least one” and “one or more” mean “any one of at least one” or “any one of one or more,” respectively.

[0195] As used herein, the term “or” means non-exclusive “or” unless otherwise stated (e.g., “otherwise” or “or in alternatives”).

[0196] As used herein, unless explicitly stated otherwise, “perform a step in response to A” does not indicate that the step is performed immediately after “A” occurs, and one or more intermediate steps may be included. Similarly, “perform a step or function based on A” does not indicate that the step or function is performed solely based on “A”, as one or more additional conditions may be included.

[0197] Figure 10 A block diagram of apparatus 10 is shown by way of example. For example, apparatus 10 includes at least one processor 12 and at least one memory 14 storing instructions 15, which, when executed by the at least one processor, can cause apparatus 10 to perform at least one or more methods (or corresponding portions thereof) disclosed herein. In one example, at least one memory and instructions (e.g., computer program code, software) are configured, together with at least one processor, to cause apparatus 10 to perform one or more methods (or corresponding portions thereof) disclosed herein.

[0198] The processor 12 may include, or be configured as, one or more circuit systems configured to perform various stages of the methods described herein.

[0199] As used herein, the term “circuit system” may refer to one or more or all of the following: (a) a hardware circuit implementation (such as an implementation in an analog, digital and / or quantum circuit system); and (b) a combination of (multiple) hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog, digital and / or quantum hardware circuits with software / firmware; and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) and (multiple) memories having software, which work together to enable a device (such as a mobile device, user device, computing device, or server) to perform various functions; and (c) any or all portions of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors and / or (multiple) quantum processors, which require software (e.g., firmware) to operate, but may be absent when operation does not require software.

[0200] This definition of circuit system applies to all uses of the term in this disclosure, including in any claim. As another example, as used in this disclosure, the term circuit system also covers only hardware circuitry or a processor (or processors), or a portion of hardware circuitry or a processor and its accompanying software and / or firmware implementation. The term circuit system also covers (e.g., and if applicable to a particular claim) baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0201] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. The memory 14 may be at least partially located outside the device 10, but may be accessible by the device 10.

[0202] Instruction 15 may be included in a computer-readable medium or a non-transitory computer-readable medium. As used herein, the term “non-transitory” refers to a limitation on the medium itself (i.e., tangible, not tactile) rather than a limitation on the persistence of data storage (e.g., random access memory (RAM) and read-only memory (ROM).

[0203] For example, device 10 can be implemented as a terminal device, such as the UE previously described. As another example, the device can be included in such a terminal device, for example, as a chipset configured to control the terminal device. Device 10 can be made or configured to perform at least one or more of the methods (or portions thereof) of the examples described herein.

[0204] As another example, device 10 can be implemented as a network node, such as the network node previously described. In another example, the device can be included in such a network node, for example, as a chipset configured to control a network node. Device 10 can be made or configured to perform at least the methods of any one or more examples (or portions thereof) of the examples described herein.

[0205] The device may include one or more entities of any protocol layer, such as a MAC entity, RRC entity, RLC entity, PDCP entity, or PHY entity. In some examples, the entity may be configured to perform at least one or more methods of any of the examples described.

[0206] Device 10 may include a radio interface 16. Radio interface 16 may provide communication capabilities to device 10. Radio interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. Radio interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. Receivers may include more than one receiver. Transmitters may include more than one transmitter. Radio interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. Transceivers may include more than one transceiver.

[0207] Device 10 may include an interface (e.g., a user interface) 18, which includes at least one of, for example, a keypad, a microphone, a touch display, a monitor, a speaker, etc. Interface 18 can be used to control the device (e.g., by a user). Interface 18 may be external to device 10. For example, device 10 may be connected to another device, such as a computer, via a wireless or wired connection, and device 10 may be controlled via the computer (e.g., by a user).

[0208] In some examples, at least some of the processes described herein can be performed by means including components for performing at least some of the described processes. Components for performing the method steps disclosed herein may include software and / or hardware components of means 10. For example, at least one processor 12, memory 14, and computer program code form components for performing one or more methods disclosed herein, and any example thereof. As used herein, the term “component” shall be interpreted in the singular, i.e., referring to a single element; or in the plural, i.e., referring to a combination of single elements. Thus, the term “component for [performing A, B, C]” shall be interpreted to encompass means in which only one component for performing A, B, and C exists, or means in which separate components for performing A, B, and C exist, or means in which components for performing A, B, and C partially or completely overlap. Furthermore, the terms "component for performing A, component for performing B, component for performing C" should be interpreted as covering an apparatus in which only one component for performing A, B, and C exists, or an apparatus in which separate components for performing A, B, and C exist, or an apparatus in which components for performing A, B, and C partially or completely overlap.

[0209] The scope of protection sought by the various examples of this disclosure is set forth in the independent claims. Examples described in this disclosure that do not fall within the scope of the independent claims, and their features (if any), shall be interpreted as examples that aid in understanding the various examples of this disclosure.

[0210] Although various examples have been described above with reference to the accompanying drawings, it will be apparent to those skilled in the art that these examples are not limited thereto and can be modified in many different ways. Therefore, all words and expressions should be interpreted broadly, and are intended to illustrate rather than limit these examples. As technology advances, it will be apparent to those skilled in the art how certain examples can be implemented and / or modified in various ways. Furthermore, it will be clear to those skilled in the art that the examples (or portions thereof) described herein can, but need not, be combined in various ways with any other examples (or portions thereof) described herein.

Claims

1. A device for communication, comprising: At least one processor; as well as At least one memory, the at least one memory including code, which, when executed by the at least one processor, causes the device to perform: Send a request to the Common Application Programming Interface Framework (CAPIF) Core Function (CCF) device to subscribe to the device for receiving the first service identified in the request via the Application Programming Interface Open Function (AEF). as well as The device receives a security credential, which authorizes the device to access the CCF to receive the first service.

2. The apparatus of claim 1, wherein the apparatus is further caused to perform: When an application residing on the device outputs a request for the first service, the middleware component of the device determines that the device has authorization information for authorizing the device to receive the first service, wherein the authorization information is sent to the AEF when the first service is requested based on the request output by the application.

3. The apparatus according to any of the preceding claims, wherein the apparatus is further caused to perform: For each of a plurality of services, information indicating the service and at least one condition for the device to use the service is obtained, wherein the plurality of services includes the first service; The description of the first service and at least one first condition for the device to use the first service are output via the user display of the device. Input is received via user input of the device, the input indicating whether the user of the device agrees that at least one first condition is met, wherein the sending of the request for authorization is performed based on the input, the input indicating that the user of the device agrees that at least one first condition is met.

4. The apparatus of claim 3, wherein the request for subscription includes an indication from the user device that the user agrees that at least one first condition has been met.

5. The apparatus according to any one of claims 3 to 4, wherein acquiring the information comprises: Send a request to the CCF device for information indicating which services are available to the device; as well as The information is received from the CCF device, and for each of the plurality of services, the information indicates the description of the service and at least one condition for the device to use the service.

6. The apparatus of claim 5, wherein the request to send information indicating which services are available to the apparatus is performed by middleware configured on the apparatus, and wherein receiving the information is performed by a resource owner function configured on the apparatus, wherein for each of the plurality of services, the information indicates the description of the service and at least one condition for the apparatus to use the service.

7. The apparatus according to any one of claims 2 to 6, wherein the apparatus is further caused to perform: The user receiving the device has withdrawn their instruction that the at least one first condition has been met; and Based on the fact that the user of the device has withdrawn the received instruction to consent to the at least one first condition being met, at least one of the security credentials or authorization information is deleted.

8. A device for communication, comprising: At least one processor; as well as At least one memory, the at least one memory including code, which, when executed by the at least one processor, causes the device to perform: Receive a request from the user equipment to subscribe to the user equipment for receiving the first service identified in the request via the Application Programming Interface Exposure Function (AEF); The authorization function sends a request to subscribe to the user device, and the authorization function is delegated to generate security credentials so that the device can be authorized to receive services via the AEF. Receive the security credentials from the authorization function to enable the user equipment to receive the first service; as well as Send the security credentials to the user equipment.

9. The apparatus of claim 8, wherein the apparatus is further caused to perform: Receive from the user equipment a request for information, for each of a plurality of services, the information indicating a description of the service and at least one condition for the user equipment to use the service, wherein the plurality of services includes the first service; and The requested information is provided to the user equipment, and for each of the plurality of services, the information indicates the description of the service and at least one condition for the device to use the service, wherein the plurality of services includes the first service.

10. The apparatus of claim 9, wherein the request for subscription includes an indication that at least one condition associated with the user device's consent to receive the first service has been met.

11. A device for communication, comprising: At least one processor; as well as At least one memory, the at least one memory including code, which, when executed by the at least one processor, causes the device to perform: Receive requests from the core functionality CCF device of the Universal Application Programming Interface Framework (CAPIF) for subscribing to and / or authorizing user devices, in order to receive the first service identified in the request through the Application Programming Interface Open Function (AEF). It is determined that the user equipment is authorized to receive the first service; as well as Provide the CCF device with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.

12. The apparatus of claim 11, wherein the apparatus is further caused to perform: Receive a request from the AEF to verify whether the authorization information is still valid; and Provide the AEF with an indication that the authorization information is still valid.

13. The apparatus of claim 11, wherein the apparatus is further caused to perform: Receive a request from the AEF to verify whether the authorization information is still valid; and Provide the AEF with an indication that the authorization information is invalid.

14. The apparatus of claim 13, wherein the apparatus is further configured to perform at least one of the following: Determine that the user of the user equipment has withdrawn their consent to meet one or more conditions for using the first service; or It has been determined that the validity period associated with the authorization information has expired. The instruction that the authorization information is invalid is based on at least one of the previous two determinations being executed.

15. The apparatus of any one of claims 11 to 14, wherein the request for subscription and / or authorization includes an indication that at least one condition associated with the user device's consent to receive the first service has been met.

16. The apparatus according to any of the preceding claims, wherein the first service is provided by at least one of the following: quantum computing-based application functionality, artificial intelligence and / or machine learning-based application functionality, or as-a-service provision.

17. A method for an apparatus, the method comprising: Send a request to the Common Application Programming Interface Framework (CAPIF) Core Function (CCF) device to subscribe to the device for receiving the first service identified in the request via the Application Programming Interface Open Function (AEF). as well as The device receives a security credential, which authorizes the device to access the CCF to receive the first service.

18. A method for an apparatus, the method comprising: Receive a request from the user equipment to subscribe to the user equipment for receiving the first service identified in the request via the Application Programming Interface Exposure Function (AEF); The authorization function sends a request to subscribe to the user device, and the authorization function is delegated to generate security credentials so that the device can be authorized to receive services via the AEF. Receive the security credentials from the authorization function to enable the user equipment to receive the first service; as well as Send the security credentials to the user equipment.

19. A method for an apparatus, the method comprising: Receive requests from the core functionality CCF device of the Universal Application Programming Interface Framework (CAPIF) for subscribing to and / or authorizing user devices, in order to receive the first service identified in the request through the Application Programming Interface Open Function (AEF). It is determined that the user equipment is authorized to receive the first service; as well as Provide the CCF device with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.

20. A computer program product comprising instructions that, when the program is executed by a computer of a device, cause the device to perform: Send a request to the Common Application Programming Interface Framework (CAPIF) Core Functionality (CCF) device to subscribe to the device for receiving the first service identified in the request via the Application Programming Interface Open Function (AEF); and The device receives a security credential, which authorizes the device to access the CCF to receive the first service.

21. A computer program product comprising instructions that, when the program is executed by a computer of a device, cause the device to perform: Receive a request from the user equipment to subscribe to the user equipment for receiving the first service identified in the request via the Application Programming Interface Exposure Function (AEF); The authorization function sends a request to subscribe to the user device, and the authorization function is delegated to generate security credentials so that the device can be authorized to receive services via the AEF. Receive the security credentials from the authorization function to enable the user equipment to receive the first service; as well as Send the security credentials to the user equipment.

22. A computer program product comprising instructions that, when the program is executed by a computer of a device, cause the device to perform: Receive requests from the core functionality CCF device of the Universal Application Programming Interface Framework (CAPIF) for subscribing to and / or authorizing user devices, in order to receive the first service identified in the request through the Application Programming Interface Open Function (AEF). It is determined that the user equipment is authorized to receive the first service; as well as Provide the CCF device with at least one of a security credential or authorization information for authorizing the user equipment to receive the first service.