Communication device, network node, and communication method

Abstract

A communication device according to the present invention comprises: a transmission unit that transmits, to a network node, a first message requesting acquisition of authorization information related to utilization of a service API according to authorization based on single authentication information corresponding to a plurality of API calling sources; and a reception unit that receives, from the network node as a response to the first message, a second message including authorization information related to utilization of the service API authorized by a resource holder on the basis of the single authentication information.

Description

COMMUNICATION DEVICE, NETWORK NODE, AND COMMUNICATION METHOD

[0001] The present invention relates to a communication device, a network node, and a communication 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).

[0004] Also, for example, an architecture is being considered in which the 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 Documents 2 and 3).

[0005] 3GPP TS 23.501 V18.6.0 (2024-03) 3GPP TS 23.222 V18.4.0 (2024-03) 3GPP TS 38.122 V18.3.0 (2024-03) 3GPP TR 23.700-22 V0.2.0 (2024-04)

[0006] CAPIF specifies an authorization method based on OAuth 2.0 for an API (Application Programming Interface) caller to obtain authorization to use a service API. Meanwhile, RNAA (Resource Owner-Aware Northbound API Access), an authorization option in CAPIF, is considering a method for a resource owner to authorize multiple API callers to use a service API based on a single piece of authentication information (see Section 5.2 of Non-Patent Document 4). This method requires support for Single Sign-On (SSO), which allows a user to log in to multiple services using a single piece of authentication information (e.g., an ID and password).

[0007] The present invention has been made in view of the above points, and has as its object to enable a resource holder to execute authorization for the use of a service API for multiple API callers based on a single piece of authentication information.

[0008] According to the disclosed technology, a communication device is provided that has: a transmitter that transmits a first message to a network node requesting acquisition of authorization information for use of a service API through authorization based on single authentication information corresponding to multiple API callers; and a receiver that receives a second message from the network node in response to the first message, the second message including authorization information for use of the service API authorized by a resource holder based on the single authentication information.

[0009] According to the disclosed technology, in RNAA, a resource holder can execute authorization for the use of a service API for multiple API callers based on a single authentication information.

[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 CAPIF. FIG. 4 is a diagram for explaining an example of RNAA. FIG. 5 is a diagram for explaining an example of a sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram for explaining an example of the functional configuration of a network node 100 in an embodiment of the present invention. FIG. 7 is a diagram for explaining an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 8 is a diagram for explaining an example of the hardware configuration of a network node 100 and a terminal 20 in an embodiment of the present invention. FIG. 9 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 a network node or terminal 20 are set.

[0014] FIG. 1 is a diagram illustrating an example of a communication system. An RNAA, which will be described later, is provided, for example, within the telecommunications carrier network. As shown in FIG. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes. Hereinafter, it is assumed that one network node corresponds to each function, but multiple functions may be realized by one network node, or multiple network nodes 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 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 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registering management, connecting management, reachability management, and terminal mobility management. The UPF is a network node having functions related to processing user plane data, such as a PDU (Protocol Data Unit) session point to the outside that interconnects with the DN (Data Network), packet routing and forwarding, and user plane Quality of Service (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 configured. 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 interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0017] The SMF is a network node that has 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 that has the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node that has functions such as selecting a network slice to which a UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be configured, and determining the AMF set to which the UE connects. The PCF is a network node that has the function of controlling network policies. The AF is a network node that has the function of controlling application servers. The NRF is a network node that has the function of discovering NF instances that provide services. The UDM is a network node 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 for explaining 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. Hereinafter, it is assumed that one network node corresponds to each function, but multiple functions may be realized by one network node, or multiple network nodes 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 having a radio access function and is connected to the UE, the AMF, and the UPF. The AMF is a network node having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 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 interconnected via respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0021] The SMF is a network node 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 having a function of notifying other NFs of capabilities and events. The NSSF is a network node having functions such as selecting a network slice to which a UE connects, determining allowed NSSAIs, determining a configured NSSAI, and determining an AMF set to which a UE connects. The PCF is a network node having a function of controlling network policies. The AF is a network node having a function of controlling application servers. The NRF is a network node 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 a visited network, and the hSEPP is a SEPP in a 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] (About RNAA) As mentioned above, an architecture is being considered in which the northbound interface between the NEF and AF in the 5G system is configured using the Common API Framework (CAPIF). CAPIF is a framework that enables third-party operators to use the mobile network functions of telecommunications carriers. Figure 3 shows an example of the system configuration of CAPIF described as Figure.6.2.0-1 in Non-Patent Document 2 (3GPP TS23.222).

[0024] This embodiment targets CAPIF that supports RNAA (Resource owner-aware northbound API access). RNAA is an authorization option in CAPIF. Figure 4 shows an example of the system configuration of CAPIF that supports RNAA. Figure 4 is a diagram shown as Figure.6.2.3-1 in Non-Patent Document 2. Hereinafter, CAPIF that supports RNAA may be referred to as "RNAA."

[0025] The system configuration of RNAA will be described with reference to Fig. 4. As shown in Fig. 4, the PLMN trust domain includes a CAPIF core function 30, a resource owner function 50, an API invoker 25, an API exposing function 40 (AEF 40), an API publishing function, and an API management function. Each of these functions may be configured by one or more network nodes. Furthermore, the API invoker 25 may be located outside the PLMN trust domain.

[0026] The CAPIF core function 30, Resource owner function 50, API invoker 25, API exposing function 40 (AEF 40), API publishing function, and API management function may be referred to as the CAPIF core function 30, Resource owner function 50, API invoker 25, API providing function 40, API publishing function, and API management function, respectively.

[0027] The API invoker 25 located within the PLMN trust domain is connected to the CAPIF core function 30 via an interface CAPIF-1. The API invoker 25 located outside the PLMN trust domain is connected to the CAPIF core function 30 via an interface CAPIF-1e. Furthermore, the API invoker 25 located within the PLMN trust domain is connected to the API exposing function 40 via an interface CAPIF-2. The API invoker 25 located outside the PLMN trust domain is connected to the API exposing function 40 via an interface CAPIF-2e.

[0028] The CAPIF core function 30 and the API exposing function 40 are connected via an interface CAPIF-3. The CAPIF core function 30 and the API publishing function are connected via an interface CAPIF-4. The CAPIF core function 30 and the API management function are connected via an interface CAPIF-5. The CAPIF core function 30 and the Resource owner function 50 are connected via an interface CAPIF-8.

[0029] The CAPIF core function 30 receives application pre-registration sent from the API invoker 25 and authenticates and authorizes third-party applications. The API exposing function 40 receives core network API calls sent from the API invoker 25 and opens service APIs for authenticated and authorized external applications.

[0030] Furthermore, the resource owner function 50 communicates with an authorization function included in the CAPIF core function 30 via the interface CAPIF-8, and manages the consent / approval of the resource owner. Furthermore, for example, the authentication function is registered with the API exposing function 40. After registration, the API exposing function 40 can access the authentication function at the necessary timing to check whether or not the API can be called.

[0031] The API invoker 25 is, for example, an application on a terminal, and may have the ability to support authentication by providing an identifier of an API caller, the ability to support mutual authentication with the CAPIF core function 30, 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.

[0032] In addition, the CAPIF core function 30 may have, for example, the ability to support mutual authentication with the API invoker 25, the ability to authenticate the API invoker 25 when accessing a 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 service API call logs and provide the service API call logs to an approval agency, the ability to bill based on the service API call logs, the ability to monitor service API calls, the ability to add and delete API invokers 25, 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.

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

[0034] The API exposing function 40 is a provider that provides a service API, which is an interface that allows a system component to expose its service to API invokers.

[0035] The API exposing function 40 may have the ability to authenticate the API invoker 25 based on information provided by the CAPIF core function 30, the ability to verify the authentication provided by the CAPIF core function 30, and the ability to log service API calls to the CAPIF core function 30.

[0036] The API publishing function may have the ability to publish to the CAPIF core function 30 information related to the service APIs owned by the API provider.

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

[0038] The CAPIF core function 30, the API exposing function 40, the API publishing function, and the API management function may each be configured as a network node, or, for example, the API exposing function 40, the API publishing function, and the API management function may be configured as a single network node. Also, the API invoker 25 and the resource owner function 50 may each be, for example, a communication device such as a terminal or a server, or may be another communication device.

[0039] In this embodiment, it is assumed that the API invoker 25 is a function (specifically, an application) provided in a terminal (an example of a communication device), but this is not limiting, and the API invoker 25 may be provided in any communication device (including a server).

[0040] Figure 4 shows the system architecture and an architectural model of RNAA in which a resource owner function 50 provides authentication to the API invoker 25. The resource owner function 50 is responsible for interaction with the resource owner of the service provider in the API provider domain. The resource owner function 50 interacts with the authentication function included in the CAPIF core function 30 via CAPIF-8.

[0041] Furthermore, an API exposing function 40, such as an NEF or SCEF (Service Capability Exposure Function), operates as a point for implementing consent from a resource holder, and interconnects with an authentication function included in the CAPIF core function 30 via CAPIF-3. The API exposing function 40 can also obtain parameters related to consent from a resource holder from the authentication function. The API invoker 25 interconnects with an authentication function included in the CAPIF core function 30 via CAPIF-1 or CAPIF-1e and operates. Hereinafter, the CAPIF core function 30 will be referred to as CCF 30.

[0042] (Processing Sequence) In RNAA, a resource holder executes authorization for the use of a service API for multiple API callers based on a single authentication information, as described below with reference to a sequence diagram. FIG. 5 shows an example of a sequence diagram according to an embodiment of the present invention. The processing of this sequence is premised on the assumption that the CCF 30, API invoker 25, and resource owner (RO) support Single Sign-On (SSO). Messages exchanged between the CCF 30, API invoker 25, and resource owner (RO) may include information about the SSO user (session information, token, etc.). Furthermore, it is assumed that the API invoker 25 requires authorization from the resource holder to use (access) the service API. The processing of each step is described below.

[0043] S101: The API invoker 25 sends a message to the CCF 30 requesting acquisition of authorization information related to the use of the service API by authorization based on single authentication information used for multiple API callers (API invokers).

[0044] S102: The CCF 30 sends the Resource owner function 50 a request message (authorization confirmation request) for confirming whether or not to grant authorization related to the authorization information requested in S101.

[0045] S103: The resource owner function 50 executes the confirmation requested in S102 with the RO. For example, the resource owner function 50 may execute the confirmation regarding authorization by having the RO input whether or not to grant authorization. The RO may determine whether or not to grant authorization to the user of the SSO corresponding to the API invoker 25. Alternatively, the CCF 30 may include authentication information (such as login information) corresponding to the API invoker 25 that has been registered in advance in the CCF 30 in the request message of S102, and the authorization by the RO may be granted if the resource owner function 50 confirms the validity of the authentication information (if it matches the authentication information held by the resource owner function 50's own device).

[0046] S104: The resource owner function 50 sends to the CCF 30 a message including information indicating the result of the check made in S103.

[0047] S105: If the confirmation result received in S104 indicates that authorization has been obtained from the RO, the CCF 30 issues authorization information (assertion). The authorization information is signed by the CCF 30. For example, the CCF 30 generates signature information by signing the authorization information using a private key held by the CCF 30. The signature information may be included in the authorization information, or the authorization information and the signature information may be separate information. Furthermore, the information included in the authorization information may include, for example, an identifier (ID) for identifying the authorization information, the issuer of the authorization information, conditions to be considered when evaluating the validity of the authorization information, and information related to the authorization (e.g., the time when the authorization was executed, the authorization method, etc.).

[0048] S106: The CCF 30 transmits a response message to the request message received in S101 to the API invoker 25. The response message includes the authorization information (Assertion) issued in S105 and a signature (signature information) for the authorization information by the CCF 30.

[0049] Similarly, by using the above procedure, multiple other API callers (API invokers) can obtain authorization information using the single authentication information in the SSO used in the above procedure. That is, by using the above embodiment, in RNAA, a resource holder can execute authorization for the use of service APIs for multiple API callers based on a single authentication information. Furthermore, the API callers can use the authorization information issued based on the SSO when invoking (invoking) the service API.

[0050] (Device Configuration) Next, a description will be given of an example of the functional configuration of the CAPIF core function 30, the AEF 40, the communication device, and the terminal 20, which perform the processing and operations described above. Hereinafter, network nodes such as the CAPIF core function 30, the AEF 40, and the communication device other than the terminal 20 will be collectively referred to as the "network node 100."

[0051] <Network Node 100> FIG. 6 is a diagram illustrating an example of the functional configuration of the network node 100. As shown in FIG.

[0052] As shown in Fig. 6, the network node 100 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 6 is merely an example. The names of the functional divisions and functional units may be any names as long as they can perform the operations according to the embodiment of the present invention.

[0053] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 or another network node and transmitting the signal via a wired or wireless connection. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 or another network node and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0054] The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed. The control unit 140 controls the network node 100. 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. The transmitting unit 110 and the receiving unit 120 may be called a transmitter and a receiver, respectively.

[0055] <Terminal 20> Fig. 7 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 7, 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. 7 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.

[0056] The transmitter 210 creates a transmission signal from 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. In particular, in the communication UE 21, the receiver 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from a network node. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0057] The setting unit 230 stores various setting information received from the network node by the receiving unit 220 in a storage device, and reads it out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

[0058] The control unit 240 controls the terminal 20. The functional unit in the control unit 240 related to signal transmission may be included in the transmitting unit 210, and the functional unit in the control unit 240 related to signal reception may be included in the receiving unit 220. The transmitting unit 210 and the receiving unit 220 may be called a transmitter and a receiver, respectively.

[0059] (Hardware Configuration) The block diagrams (FIGS. 6 and 7) 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 connected directly or indirectly (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.

[0060] 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.

[0061] For example, the network node 100 and the terminal 20 according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 8 is a diagram illustrating an example of the hardware configuration of the network node 100 and the terminal 20 according to an embodiment of the present disclosure. The network node 100 and the terminal 20 described above 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.

[0062] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the network node 100 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.

[0063] Each function in the network node 100 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 via 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.

[0064] 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.

[0065] The processor 1001 also 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 network node 100 shown in FIG. 6 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 7 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives 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).

[0070] 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.

[0071] Furthermore, the network node 100 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.

[0072] 9 shows an example configuration of a vehicle 2001. As shown in FIG. 9 , 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. For example, the network node 100 or the terminal 20 may be included in the communication module 2013.

[0073] 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.

[0074] 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).

[0075] 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 rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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 terminal, a network node, or the like.

[0080] The communication module 2013 may transmit, via wireless communication, to an external device at least one of signals from the 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. 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.

[0081] 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.

[0082] Furthermore, when the communication module 2013 includes the network node 100 (or the terminal 20), the communication module 2013 can perform the operations of the network node 100 (or the terminal 20) described above.

[0083] This specification discloses at least the configurations described in the appendices below.

[0084] <Additional Notes> (Additional Item 1) A communications device comprising: a transmitter that transmits to a network node a first message requesting acquisition of authorization information related to use of a service API through authorization based on single authentication information corresponding to multiple API callers, and a receiver that receives from the network node a second message in response to the first message, the second message including authorization information related to use of the service API authorized by a resource holder based on the single authentication information. (Additional Item 2) The communications device according to Additional Item 1, wherein the receiver receives the second message including signature information generated by the network node signing the authorization information. (Supplementary Item 3) A network node comprising: a receiver that receives, from an API caller in a communication device, a first message requesting acquisition of authorization information for use of a service API with authorization based on single authentication information corresponding to multiple API callers; and a transmitter that transmits, to another network node, a second message requesting confirmation of whether authorization related to the authorization information is permitted, wherein the receiver receives from the other network node a third message that is a response to the second message, and further comprises a controller that issues the authorization information if the third message indicates that authorization related to the authorization information is permitted, and the transmitter transmits, in response to the first message, a fourth message including the authorization information to the API caller in the communication device. (Supplementary Item 4) The network node according to Supplementary Item 3, wherein the controller executes a signature on the authorization information to generate signature information, and the transmitter transmits the signature information included in the fourth message. (Supplementary Item 5) A network node including: a receiving unit that receives, from another network node, a first message requesting confirmation of whether to grant authorization for use of a service API; a control unit that performs confirmation of whether to grant the authorization based on single authentication information corresponding to multiple API callers; and a transmitting unit that transmits, in response to the first message, a second message to the other network node that includes information indicating the result of the confirmation.(Supplementary clause 6) A communication method executed by a communication device, comprising: a step of sending a first message to a network node requesting acquisition of authorization information for use of a service API with authorization based on single authentication information corresponding to multiple API callers; and a step of receiving a second message from the network node in response to the first message, the second message including authorization information for use of the service API authorized by a resource holder based on the single authentication information.

[0085] Any of Supplementary Items 1 to 6 allows a resource holder in RNAA to execute authorization for the use of a service API for multiple API callers based on a single authentication information.

[0086] (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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters 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 boundaries between physical components. The operations of multiple functional units may be performed physically by a single component, or the operations of a single functional unit may be performed physically by multiple components. The order of processing procedures described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 100 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 EES 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 random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0087] 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), 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), 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.

[0088] 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).

[0089] 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.

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

[0091] 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.

[0092] 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 transmitted to another device.

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

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

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

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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 small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0103] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0105] 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.

[0106] At least one of the network node 100 and the terminal 20 may be referred to as a transmitting device, a receiving device, a communication device, or the like. At least one of the network node 100 and the terminal 20 may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that travels autonomously based on operational commands. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the network node 100 and the terminal 20 may 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.

[0107] 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 base station 10 described above. 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.

[0108] 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.

[0109] 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.

[0110] 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.

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

[0112] 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."

[0113] 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.

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

[0115] 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.

[0116] 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.

[0117] 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."

[0118] 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).

[0119] 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.

[0120] 10 Base station ((R)AN) 20 Terminal (UE) 30 CAPIF core function 40 API exposing function 50 Resource owner function 55 Resource owner 100 Network node 110 Transmitter 120 Receiver 130 Setting unit 140 Controller 210 Transmitter 220 Receiver 230 Setting unit 240 Controller 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 Revolution speed sensor 2023 Air 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 communications device having: a transmitter that transmits a first message to a network node requesting acquisition of authorization information for use of a service API with authorization based on a single authentication information corresponding to multiple API callers; and a receiver that receives a second message from the network node in response to the first message, the second message including authorization information for use of the service API authorized by a resource holder based on the single authentication information.

2. The communication device according to claim 1, wherein the receiving unit receives the second message including signature information generated by the network node signing the authorization information.

3. A network node comprising: a receiver that receives a first message from an API caller in a communications device, the first message requesting the acquisition of authorization information for use of a service API through authorization based on single authentication information corresponding to multiple API callers; and a transmitter that transmits a second message to another network node, the second message requesting confirmation of whether authorization related to the authorization information is to be granted; wherein the receiver receives a third message from the other network node as a response to the second message; and when the third message indicates that authorization related to the authorization information is to be granted, the receiver further comprises a control unit that issues the authorization information; and the transmitter transmits a fourth message including the authorization information to the API caller in the communications device in response to the first message.

4. The network node according to claim 3, wherein the control unit generates signature information by executing a signature on the authorization information, and the transmission unit includes the signature information in the fourth message and transmits the fourth message.

5. A network node including: a receiving unit that receives, from another network node, a first message requesting confirmation of whether to grant authorization for use of a service API; a control unit that performs confirmation of whether to grant the authorization based on single authentication information corresponding to multiple API callers; and a transmitting unit that transmits, in response to the first message, a second message to the other network node that includes information indicating the result of the confirmation.

6. A communication method executed by a communication device, comprising: a step of sending a first message to a network node requesting acquisition of authorization information for use of a service API with authorization based on single authentication information corresponding to multiple API callers; and a step of receiving a second message from the network node in response to the first message, the second message including authorization information for use of the service API authorized by a resource holder based on the single authentication information.

Images