Network node and approval method

Abstract

This network node comprises: a control unit that gives approval for a service application programming interface (API) to an API call source; and a reception unit that receives, from a resource owner function, an API call source approval cancellation request related to the service API of the API call source, wherein the control unit further has a transmission unit that, on the basis of the API call source approval cancellation request, invalidates the approval for the service API of the API call source, and transmits, to the resource owner function, an API call source approval cancellation response to the API call source approval cancellation request, and, when cancellation of the approval for the service API of the API call source is successful, the transmission unit notifies an API provision function of the cancellation of the approval for the service API of the API call source.

Description

Network node and authorization method

[0001] The present invention relates to a network node and an authorization method in a communication system.

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. Various wireless technologies are being studied for 5G to meet the requirements of achieving a throughput of 10 Gbps or more while keeping latency in wireless sections to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE, is being considered (for example, Non-Patent Document 1 and Non-Patent Document 2).

[0004] Also, for example, an architecture is being considered in which a northbound interface between a network exposure function (NEF) and an application function (AF) in a 5G system is configured using the common API framework (CAPIF) (for example, Non-Patent Document 3 and Non-Patent Document 4). Resource owner-aware northbound API access (RNAA) is an authorization option in CAPIF.

[0005] 3GPP TS 23.501 V18.4.0 (2023-12)3GPP TS 23.502 V18.4.0 (2023-12)3GPP TS 29.522 V18.4.0 (2023-12)3GPP TS 23.222 V18.4.0 (2024-03)Internet Engineering Task Force Request for Comments: 6749, October 2012Internet Engineering Task Force Request for Comments: 7009, August 20133GPP TS 33.501 V18.4.0 (2023-12)

[0006] In the existing RNAA, the function of token revocation (see Non-Patent Document 6) in OAuth (see Non-Patent Document 5) is not specified, and there is no function to revoke an access token from the resource owner function.

[0007] The present invention has been made in view of the above points, and has as its object to revoke authorization for a service API (Application Programming Interface).

[0008] According to the disclosed technology, a network node is provided which includes a control unit that grants authorization to an API caller for an API caller's service API (Application Programming Interface), and a receiving unit that receives an API caller authorization revocation request related to the service API of the API caller from a resource owner function, wherein the control unit invalidates the API caller's authorization for the service API based on the API caller authorization revocation request, and transmits an API caller authorization revocation response that is a response to the API caller authorization revocation request to the resource owner function, and wherein the transmitting unit, if successful in revoking the API caller's authorization for the service API, notifies an API providing function of the revocation of the API caller's authorization for the service API.

[0009] According to the disclosed technology, authorization for a service API (Application Programming Interface) can be revoked.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a diagram for explaining an example of a CAPIF in an embodiment of the present invention. FIG. 4 is a sequence diagram for explaining an example of an API in an embodiment of the present invention. FIG. 5 is a diagram for explaining an example of the functional configuration of a base station 10 in an embodiment of the present invention. FIG. 6 is a diagram for explaining an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 7 is a diagram for explaining an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. FIG. 8 is a diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, and systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0013] Furthermore, in the embodiments of the present invention, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0015] The RAN (Radio Access Network) is a network node 30 having a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices may be configured.

[0016] The AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0017] The SMF is a network node 30 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.

[0018] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0019] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0020] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0021] The SMF is a network node 30 having functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a function of discovering NF instances that provide services. The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in FIG. 2 is a SEPP in the visited network, and the hSEPP is a SEPP in the home network.

[0022] As shown in Figure 2, a UE is in a roaming environment connected to a RAN and an AMF in a Visited PLMN (VPLMN). The VPLMN and a Home PLMN (HPLMN) are connected via a vSEPP and an hSEPP. The UE can communicate with a UDM in the HPLMN via the AMF in the VPLMN, for example.

[0023] FIG. 3 is a diagram illustrating an example of CAPIF in an embodiment of the present invention. Resource owner-aware northbound API access (RNAA) is an authorization option in the Common API Framework (CAPIF) (see Non-Patent Document 4). As shown in FIG. 3, the PLMN trust domain includes a CAPIF core function (CCF), a resource owner, an API invoker such as a terminal 20, an API exposing function (AEF), an API publishing function (APF), and an API management function (AMF). These functions may be configured by one or more network nodes 30. Furthermore, the API invoker may be located outside the PLMN trust domain.

[0024] An API caller may be connected to the CAPIF core function via interface CAPIF-1. An API caller located outside the PLMN trust domain may be connected to the CAPIF core function via interface CAPIF-1e. An API caller may also be connected to the API provider function via interface CAPIF-2. An API caller located outside the PLMN trust domain may be connected to the API provider function via interface CAPIF-2e.

[0025] The CAPIF core function and the API providing function may be connected via an interface CAPIF-3. The CAPIF core function and the API publishing function may be connected via an interface CAPIF-4. The CAPIF core function and the API management function may be connected via an interface CAPIF-5. The CAPIF core function and the resource owner may be connected via an interface CAPIF-8.

[0026] The CAPIF core function receives application pre-registrations sent from API callers, such as the terminal 20, and authenticates and authorizes third-party applications. The API provision function receives core network API calls sent from API callers and opens service APIs for authenticated and authorized external applications.

[0027] In addition, the resource owner can authorize API calls made by the core network via an authorization function included in the CAPIF core functions. For example, the authorization function is registered with the API provider function. After registration, the API provider function can access the authorization function at the necessary timing to check whether the API can be called.

[0028] In addition, the API caller may be, for example, an application on a terminal, and may have the ability to support authentication by providing an identifier of the API caller, the ability to support mutual authentication with the CAPIF core functions, the ability to obtain authentication when accessing a service API, the ability to discover information related to the service API, and the ability to call the service API.

[0029] In addition, the CAPIF core functions may have, for example, the ability to support mutual authentication with the API caller 20A, the ability to authenticate the API caller when accessing the service API, the ability to publish and store information related to the service API, the ability to control access to the service API based on a policy set by the PLMN operator, the ability to record a service API call log and provide the service API call log to an approval authority, the ability to bill based on the service API call log, the ability to monitor service API calls, the ability to add and delete API callers, the ability to support access to logs for auditing to detect fraudulent use, and the ability to publish information related to the service API together with other CAPIF core functions through connections between CAPIFs.

[0030] The API providing function, the API publishing function, and the API management function may be functions or nodes that belong to a single API provider.

[0031] In addition, the API providing function is a provider that provides a service API, and may have the ability to authenticate the API caller based on information provided from the CAPIF core function, the ability to verify the authentication provided from the CAPIF core function 30F, and the ability to record a log of service API calls in the CAPIF core function.

[0032] The API disclosure function may have the ability to disclose information related to the service APIs owned by the API provider to the CAPIF core function.

[0033] The API management function is a function that allows the API provider to manage the service API, and may have the ability to audit the service API call log received from the CAPIF core function, the ability to monitor events reported from the CAPIF core function, the ability to set the API provider's policy in the CAPIF core function, the ability to monitor the status of the service API, the ability to add and delete API callers, and the ability to register and maintain the API provider's registration information in the CAPIF core function.

[0034] The CAPIF core function, the API providing function, the API publishing function, and the API management function may each be configured as a network node 30, or, for example, the API providing function, the API publishing function, and the API management function may be configured as one network node 30. Furthermore, the API caller and the resource owner may be, for example, a communication device such as a terminal or a server, or may be another communication device.

[0035] 3 also shows the structural model of RNAA in which a resource owner provides authorization to an API caller. The resource owner is an application client used by a resource owner of a service provider in an API provider domain. The resource owner interacts with the authentication function included in the CAPIF core functions via CAPIF-8. The resource owner communicates with the authentication function included in the CAPIF core functions to provide or revoke the resource owner's authorization.

[0036] For example, as defined in Non-Patent Document 7, API providing functions such as NEF and SCEF (Service Capability Exposure Function) operate as points that implement the consent of the resource owner, and interconnect with the authentication function included in the CAPIF core function via CAPIF-3. In addition, the API providing function can obtain parameters related to the consent of the resource owner from the authentication function. The API caller interconnects with the authentication function included in the CAPIF core function via CAPIF-1 or CAPIF-1e and operates.

[0037] In the existing RNAA, the function of token revocation (see Non-Patent Document 6) in OAuth (see Non-Patent Document 5) is not specified, and there is no function to revoke an access token from the resource owner function.

[0038] On the other hand, Non-Patent Document 4 specifies the revocation of authorization of an API caller by CAPIF, and includes an API providing function and a CAPIF core function for revoking an access token.

[0039] Therefore, token revocation from the resource owner function in RNAA may be realized by extending an existing API.

[0040] 4 is a sequence diagram illustrating an example of an API according to an embodiment of the present invention. Before the sequence diagram shown in FIG. 4 is executed, the following conditions 1) to 3) may be satisfied.

[0041] 1) The API caller is authenticated and authorized to use the service API. 2) The API provider function within CAPIF has an access policy set that applies to calls to the service API corresponding to the API caller and the service API. 3) The authorization details in the API provider function are available to the CAPIF core function.

[0042] In step S101, the resource owner function triggers the revocation of authorization for the API caller.

[0043] In step S102, the resource owner function sends an API caller authorization revocation request, which is a request to revoke the authorization of the API caller, to the CAPIF core function. The API caller authorization revocation request may include details of the API caller and the service API.

[0044] In step S103, upon receiving information for revoking the authorization of the API caller for the service API, which is included in the API caller authorization revocation request, the CAPIF core function invalidates the authorization of the API caller corresponding to the service API.

[0045] In step S104, the CAPIF core function sends an API caller authorization revocation response, which is a response to the request to revoke the authorization of the API caller, to the resource owner function.

[0046] In step S105, if the CAPIF core function has successfully revoked the authorization for the service API corresponding to the API caller, the CAPIF core function notifies the API providing function of the revocation of the authorization for the service API of the API caller. The API providing function revokes the authorization for the service API of the API caller.

[0047] In step S106, the CAPIF core function sends an API caller authorization revocation notification to the API caller, notifying the API caller that the authorization to access the corresponding service API has been revoked.

[0048] Note that the execution of steps S105 and S106 may be optional.

[0049] The API caller authorization revocation request sent from the resource owner function to the CAPIF core function may include the information elements shown in Table 1.

[0050]

[0051] As shown in Table 1, the API caller authorization revocation request may include an information element "API invoker identity information," which indicates the identifier of the API caller.

[0052] As shown in Table 1, the API caller authorization revocation request may include an information element "Service API identification," which identifies the service API for the resource owner consent revocation request.

[0053] As shown in Table 1, the API caller authorization revocation request may include the information element "Cause," which indicates the reason for revoking the resource owner consent.

[0054] The API caller authorization revocation response sent from the CAPIF core function to the resource owner function may include the information elements shown in Table 2.

[0055]

[0056] As shown in Table 2, the API caller authorization revocation response may include the information element "Result," which indicates the success or failure of the API caller authorization revocation request.

[0057] The API caller authorization revocation notification sent from the CAPIF core function to the API caller may include the information elements shown in Table 3.

[0058]

[0059] As shown in Table 3, the API caller authorization revocation notification may include an information element "API invoker identity information," which indicates the identifier of the API caller whose authorization has been revoked.

[0060] As shown in Table 3, the API caller authorization revocation notification may include an information element "Service API identification," which identifies the service API that the API caller authorization revocation targets.

[0061] As shown in Table 3, the API caller authorization revocation notification may include the information element "Cause," which indicates the reason for the resource owner consent revocation.

[0062] The above-described embodiment enables RNAA to realize a function for invalidating an access token from a resource owner function, thereby improving the convenience of RNAA.

[0063] That is, authorization for a service API (Application Programming Interface) can be revoked.

[0064] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0065] <Base Station 10 and Network Node 30> Fig. 5 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 5, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 5 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0066] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal.

[0067] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out the information from the storage device as needed. The content of the setting information includes, for example, settings related to API calling procedures.

[0068] As described in the embodiment, the control unit 140 performs processing related to the API call procedure in the network. The control unit 140 also performs processing related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0069] <Terminal 20> Fig. 6 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 6, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 6 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0070] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from the network node 30.

[0071] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information includes, for example, settings related to API calling procedures.

[0072] As described in the embodiments, the control unit 240 performs processing related to connection control to the network and the network slice. The control unit 240 also performs processing related to the API call procedure. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0073] (Hardware Configuration) The block diagrams (FIGS. 5 and 6) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0074] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0075] For example, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 7 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0076] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0077] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0078] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0079] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 5 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 6 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0080] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0081] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0082] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0083] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0084] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0085] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0086] Fig. 8 shows an example configuration of a vehicle 2001. As shown in Fig. 8, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0087] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0088] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0089] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0090] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0091] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0092] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0093] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0094] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0095] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0096] (Summary of embodiment) As described above, according to an embodiment of the present invention, a network node is provided which includes a control unit that grants authorization to an API caller for an API caller's service API (Application Programming Interface), and a receiving unit that receives an API caller authorization revocation request related to the service API of the API caller from a resource owner function, and the control unit further includes a transmitting unit that invalidates the API caller's authorization for the service API based on the API caller authorization revocation request, and transmits an API caller authorization revocation response that is a response to the API caller authorization revocation request to the resource owner function, and the transmitting unit notifies an API providing function of the revocation of the API caller's authorization for the service API when the revocation of the API caller's authorization for the service API is successful.

[0097] With the above configuration, the RNAA can realize a function to invalidate an access token from the resource owner function, thereby improving the convenience of the RNAA. That is, it is possible to revoke the authorization of a service API (Application Programming Interface).

[0098] The transmission unit may transmit to the API caller an API caller authorization revocation notice, which is a notice of revocation of authorization for the service API of the API caller. With this configuration, in the RNAA, a function of invalidating an access token from a resource owner function can be realized, thereby improving the convenience of the RNAA.

[0099] The control unit may determine the identifier of the API caller, the identifier of the service API, and the reason for revocation based on the API caller authorization revocation request. With this configuration, in the RNAA, a function for revoking an access token from a resource owner function is realized, thereby improving the convenience of the RNAA.

[0100] The control unit may include, in the API caller authorization revocation response, information indicating whether the revocation of the authorization for the service API of the API caller was successful. With this configuration, in the RNAA, a function for invalidating an access token from a resource owner function is realized, thereby improving the convenience of the RNAA.

[0101] The control unit may include an identifier of the API caller, an identifier of the service API, and a reason for revocation in the API caller authorization revocation notification. With this configuration, in the RNAA, a function for revoking an access token from a resource owner function is realized, thereby improving the convenience of the RNAA.

[0102] Furthermore, according to an embodiment of the present invention, there is provided an authorization method in which a network node executes the following steps: granting authorization to an API caller for a service API (Application Programming Interface); receiving an API caller authorization revocation request related to the service API of the API caller from a resource owner function; invalidating the API caller's authorization for the service API based on the API caller authorization revocation request; sending an API caller authorization revocation response that is a response to the API caller authorization revocation request to the resource owner function; and, if the revocation of the API caller's authorization for the service API is successful, notifying an API providing function of the revocation of the API caller's authorization for the service API.

[0103] With the above configuration, the RNAA can realize a function to invalidate an access token from the resource owner function, thereby improving the convenience of the RNAA. That is, it is possible to revoke the authorization of a service API (Application Programming Interface).

[0104] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention. Two or more items may be used in combination as needed, and items described in one item may apply to items described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to physical component boundaries. The operations of multiple functional units may be physically performed by a single component, or the operations of a single functional unit may be physically performed by multiple components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 30 and the terminal 20 have been described using functional block diagrams. However, such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the network node 30 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in any suitable storage medium, such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or the like.

[0105] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0106] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0107] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0108] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0109] In this specification, a specific operation that is described as being performed by the network node 30 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes including the network node 30, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the network node 30 and another network node other than the network node 30 (for example, an MME or an S-GW, etc., are possible, but are not limited to these). Although the above example illustrates a case where there is one other network node other than the network node 30, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0110] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0111] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0112] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0113] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0114] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0115] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0116] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0117] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0118] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0119] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0120] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0121] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0122] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0123] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0124] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0125] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the above-described network node 30. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0126] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0127] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0128] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0129] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0130] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0131] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0132] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0133] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0134] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0135] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0136] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0137] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0138] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A network node comprising: a control unit that grants authorization to an API caller for an API caller's service API (Application Programming Interface); and a receiving unit that receives an API caller authorization revocation request related to the service API of the API caller from a resource owner function, wherein the control unit invalidates the API caller's authorization for the service API based on the API caller authorization revocation request; and further comprises a transmitting unit that transmits an API caller authorization revocation response to the API caller authorization revocation request to the resource owner function, wherein the transmitting unit notifies an API providing function of the revocation of the API caller's authorization for the service API if the revocation of the API caller's authorization for the service API is successful.

2. The network node according to claim 1, wherein the transmission unit transmits to the API caller an API caller authorization revocation notice, which is a notice of revocation of authorization for the service API of the API caller.

3. The network node according to claim 1, wherein the control unit determines an identifier of the API caller, an identifier of the service API, and a reason for revocation based on the API caller authorization revocation request.

4. The network node according to claim 1, wherein the control unit includes in the API caller authorization revocation response information indicating whether the revocation of the authorization of the API caller for the service API was successful.

5. The network node according to claim 2, wherein the control unit includes in the API caller authorization revocation notice an identifier of the API caller, an identifier of the service API, and a reason for revocation.

6. An authorization method in which a network node executes the following steps: granting authorization to an API caller for a service API (Application Programming Interface); receiving an API caller authorization revocation request related to the service API from the API caller from a resource owner function; invalidating the API caller's authorization for the service API based on the API caller authorization revocation request; sending an API caller authorization revocation response that is a response to the API caller authorization revocation request to the resource owner function; and, if the API caller's authorization for the service API is successfully revoked, notifying an API providing function of the revocation of the API caller's authorization for the service API.

Images