Network node, resource owner device, system, and communication method

Abstract

Provided is a network node including a reception unit that receives an update request for updating API authorization information from a resource owner device and a control unit that updates retained API authorization information according to the update request and determines whether to permit an API call request from an external application according to the updated API authorization information.

Description

[Technical Field]

[0001] The present invention relates to API calls from external applications. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter referred to as "5G" or "NR") in order to achieve even larger system capacity, even faster data transmission speeds, and even 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 is being considered that includes 5GC (5G Core Network), which corresponds 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), which corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE (e.g., Non-Patent Document 1).

[0004] Furthermore, 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). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 23.501 V17.2.0(2021-09) [Non-patent document 2] 3GPP TS 29.522 V17.3.0(2021-09) [Non-patent document 3] 3GPP TS 23.222 V17.5.0(2021-06) Summary of the Invention [Problem to be solved by the invention]

[0006] The 3GPP core network opens up its API (Application Programming Interface) to external applications, allowing third-party applications to call the API.

[0007] In addition, a mechanism is being considered in which, when an external application makes an API call to a network node, the network node obtains information from the resource owner indicating whether the API can be used (called API authorization information), and determines whether the API can be used based on that API authorization information.

[0008] However, conventional technologies do not have a mechanism for changing API authorization information once it has been obtained, and are therefore unable to respond to requests such as denying the use of an API that has already been permitted for use at a later date.

[0009] The present invention has been made in view of the above points, and aims to provide a technique that enables API authorization information in a network node to be changed. [Means for solving the problem]

[0010] According to the disclosed technology, a receiving unit that receives an update request for API authorization information from a resource owner device; a control unit that updates the API authorization information held in accordance with the update request, and determines whether to permit an API call request from an external application in accordance with the updated API authorization information. a network node, The update request includes identification information of an API caller and identification information of an API whose callability is to be updated, and the control unit updates entries corresponding to the API caller and the API to be updated in a table indicating the API authorization information. A network node is provided. [Effects of the Invention]

[0011] The disclosed technology can provide a technology that enables API authorization information in a network node to be changed. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a communication system. [Figure 2] FIG. 1 is a diagram illustrating an example of a communication system in a roaming environment. [Figure 3] FIG. 10 is a diagram illustrating an example of an API call. [Figure 4] FIG. 10 is a diagram illustrating an example of an API call. [Figure 5] FIG. 10 is a diagram illustrating an example of an update process of API authorization information. [Figure 6] FIG. 10 is a diagram illustrating an example of an API call. [Figure 7] FIG. 10 is a diagram illustrating an example of a table showing API authorization information. [Figure 8] FIG. 10 is a diagram illustrating an example of an update process of API authorization information. [Figure 9] FIG. 10 is a diagram illustrating an example of a table showing API authorization information. [Figure 10] 10 is a sequence chart of processing for updating API authorization information. [Figure 11] FIG. 1 is a diagram illustrating an example of a system including a UE and an AF according to an embodiment of the present invention. [Figure 12] FIG. 1 is a diagram illustrating an example of a system including a UE according to an embodiment of the present invention. [Figure 13]1 is a diagram illustrating an example of a functional configuration of a base station 10 (and a network node 30 and a resource owner 40) according to an embodiment of the present invention. [Figure 14] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 (and a resource owner 40) according to an embodiment of the present invention. [Figure 15] 1 is a diagram illustrating an example of a hardware configuration of a base station 10 and a terminal 20 according to an embodiment of the present invention. [Figure 16] 1 is a diagram showing an example of a configuration of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

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

[0014] In operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. The existing technology is, for example, existing LTE or existing NR (5G), but is not limited to existing LTE or existing NR.

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

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

[0017] 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), and performing 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 are constructed.

[0018] 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 interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0019] The SMF is a network node 30 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 30 that has a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 that has functions such as selecting a network slice to which a UE connects, determining allowed NSSAIs (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 30 that has a function of controlling network policies. The AF is a network node 30 that has a function of controlling application servers. The NRF is a network node 30 that has 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.

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

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

[0022] 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 their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0023] 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 an NSSAI to be configured, 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 Figure 2 is the SEPP in the visited network, and the hSEPP is the SEPP in the home network.

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

[0025] The operation of this embodiment may be performed in either the configuration shown in Fig. 1 or 2. Furthermore, the operation of this embodiment may be performed in a configuration other than the configurations shown in Fig. 1 and 2.

[0026] The NEF is being considered for implementation by applying the Common API Framework (CAPIF) architecture to an API (Application Programming Interface) that can be called from an AF. The CAPIF architecture provides a mechanism to support service API operations, for example, allowing an API invoker to discover service APIs provided by an API provider and enabling communication using the service APIs. The CAPIF architecture also has a mechanism to hide the topology of the PLMN trust domain from an API invoker that accesses a service API from outside the PLMN trust domain.

[0027] The API caller application 30A described below may be provided in the above-mentioned AF, and the API providing function (AEF) 30C may be provided in the NEF, but this is not limitative, and the API caller application 30A and the AEF 30C may each be provided in any network node 30. The AEF 30C may be provided in the base station 10. Furthermore, the API caller application 30A may be provided in the terminal 20.

[0028] Furthermore, a resource owner 40 (resource owner device) described later may be a network node 30, a terminal 20, a base station 10, or a device other than these.

[0029] 3 is a diagram showing an example of an API call. The 3GPP core network opens APIs to external applications, allowing third-party applications to call the APIs from the network node 30. When an API is called, a CAPIF Core Function (also referred to as CCF) in the core network authenticates and / or authorizes the calling application (API invoker) and manages which applications can call the APIs.

[0030] As shown in Figure 3, an application 30A that makes an API call is pre-registered with a CAPIF core function 30B using the CAPIF-API. The CAPIF core function 30B authenticates and / or authorizes the third-party application 30A. Also, as shown in Figure 3, when the application 30A that makes an API call calls an API of the core network, an API exposing function (also referred to as an AEF) 30C opens a service API for the authenticated and / or authorized external application.

[0031] CAPIF can also be extended to allow the resource owner 40 to authorize API calls to the core network. However, existing technology only allows for a method in which authorization is obtained from the resource owner 40 when an API call is made.

[0032] The resource owner 40 is, for example, an entity that is affected by the call (execution) of the target API. For example, the resource owner 40 may be the user's terminal 20 that allows / denies the application 30A that is the API call source to use the API provided by the AEF 30C to acquire location information of the user's terminal 20.

[0033] The resource owner 40 may also be called a network node, a terminal, a resource owner device, a communication device, an authorization information providing device, an authorization information updating device, or the like.

[0034] Authorization once given by the resource owner 40 for API usage is held in the AEF 30C, but the conventional technology has a problem in that the procedure for changing the authorization information (for example, when wanting to revoke authorization once given) is not clear. Below, an example of operation according to this embodiment for solving this problem will be described.

[0035] (Example of operation according to the embodiment) Here, the API call from the API caller 30A to the AEF 30C holds the API authorization information, and then updates the API authorization information from the resource owner 40, and references it during subsequent API calls. However, this is just an example, and it is also possible that the resource owner 40 first sends the API authorization information to the AEF 30C and causes the AEF 30C to hold the authorization information.

[0036] <Holding of API Authorization Information> First, referring to FIG. 4, the operations until the AEF 30C holds the API authorization information will be described.

[0037] In S1, the API caller 30A makes an API call by sending a service API invocation request to the AEF 30C. The service API invocation request may include information (such as ID, address, etc.) for identifying the resource owner 40.

[0038] Upon receiving the service API invocation request, the API caller 30A accesses the resource owner 40 in S2, for example, based on the information (e.g., name of the API, ID of the resource owner) included in the service API invocation request, and obtains the API authorization information (information indicating whether the API call is permitted) related to the service API invocation request from the resource owner 40, and holds the API authorization information in S3.

[0039] When the above API authorization information is information that permits API usage, the API execution process is performed. When the above API authorization information is information that rejects API usage, for example, information indicating that API usage is rejected is returned to the API caller 30A, and the API execution process is not performed.

[0040] <Update of API Authorization Information> For example, if the resource owner 40 wants to make an API that was previously available unavailable (or make an API that was previously unavailable available), in S1 of FIG. 5, the resource owner 40 sends a notification (update request) to the AEF30C regarding whether or not the API can be called for updating.

[0041] In S2, the AEF 30C updates the API authorization information that it holds based on the notification received in S1.

[0042] (Example) A more specific example of operation will be described below as an embodiment.

[0043] In the example shown in Fig. 6, it is assumed that the AEF 30C holds the illustrated table (also called a list) as API authorization information. Each entry in this table includes a resource owner ID, a target API, and whether or not it can be called. For example, it indicates that the SessionWithQoS API, which is the target API for resource owner ID = 123456789, is available for use. This information is, for example, information obtained using the procedure shown in Fig. 4 or information updated using the procedure shown in Fig. 5.

[0044] 6, for example, it is assumed that the API caller 30A sends a call request for the "SessionWithQoS API" to the AEF 30C. The AEF 30C references the table it holds and finds that the "SessionWithQoS API" is available, and therefore executes the "SessionWithQoS API."

[0045] Also, for example, suppose that API caller 30A sends a call request for "TrafficInfluence" to AEF 30C. AEF 30C refers to the table it holds and finds that "TrafficInfluence" is unavailable, and therefore does not execute "TrafficInfluence."

[0046] When the AEF 30C receives a request to call an API that is not in the table (list), it inquires of the resource owner 40 whether the call is permitted, according to the procedure shown in FIG. 4, and adds the result of the inquiry to the table.

[0047] The table of API authorization information held by the AEF 30C may include an API caller ID, as shown in Fig. 7. In the example of Fig. 7, for example, when API caller A (ID = API caller A) transmits a call request for API1 including the ID to the AEF 30C, the AEF 30C refers to the table and determines that the call of API1 from API caller A is permitted, and executes API1 for API caller A.

[0048] Also, in the example of Figure 7, for example, if API caller B (ID = API caller B) sends a call request for API1 including the ID to AEF30C, AEF30C will determine by referring to the table that API caller B cannot call API1, and will not execute API1 for API caller B.

[0049] Fig. 8 shows an example of updating the table (API authorization information) shown in Fig. 6. In the example shown in Fig. 8, the resource owner 40 with ID=123456789 wants to change the invocation of the "SessionWithQoS API" from "allowed" to "not allowed," and in S1 transmits an API invocation permission / denial notice (which may also be called an update notice) indicating that the invocation of the "SessionWithQoS API" is "not allowed" to the AEF 30C. Upon receiving the API invocation permission / denial notice, the AEF 30C changes the invocation permission / denial in the entry for "SessionWithQoS API" in the table to "not allowed," as shown in Fig. 8.

[0050] After the above change, it is assumed that API caller 30A sends a call request for the "SessionWithQoS API" to AEF 30C. AEF 30C refers to the table it holds and finds that the "SessionWithQoS API" is unavailable, and therefore does not execute the "SessionWithQoS API."

[0051] As shown in the example of Figure 7, a list including the API caller ID can also be updated in the same way.

[0052] For example, if it is determined that the resource owner 40 with ID=10 has denied the request to call API1 from API caller A, the resource owner 40 transmits to the AEF 30C an API call possibility notification (update notification) indicating that the call to API1 from API caller A is "denied." Upon receiving the API call possibility notification, the AEF 30C changes the call possibility in the entries for "API caller A" and "API1" in the table to "denied," as shown in FIG.

[0053] <Sequence example> 10, an example of a sequence related to updating API authorization information is shown. In S101, the resource owner 40 transmits a request to update API authorization information to the AEF 30C. This update request includes, for example, the resource owner ID and information indicating the API to be updated (such as the name of the API).

[0054] In S102, the AEF 30C verifies the update request. As an example, the ID of each authenticated resource owner is registered in the AEF 30C, and in S102, the AEF 30C performs verification by checking whether the ID of the resource owner 40 included in the update request is the registered ID.

[0055] In S103, the AEF 30C updates the authorization information table, for example, as shown in Fig. 8. In S104, the AEF 30C transmits an authorization information update response indicating that the update has been performed to the resource owner 40 that has made the update request. The resource owner 40 that has received the authorization information update response can confirm that the update has been performed successfully.

[0056] In the above example, we have shown a case where information already existing in the table is updated, but the process of adding new information that is not in the table is basically the same as the process explained so far, and can be performed according to the sequence in Figure 10. The process of adding new information that is not in the table may also be called "updating."

[0057] <System configuration example> 11 shows a specific configuration example of a system according to the present embodiment, assuming a 5G system. In FIG. 11, a case where a UE (terminal) 20 is a resource owner 40 is shown as an example.

[0058] 11, a CCF 30B including a CAPIF-API, an AEF 30C including a service API, an APF (API Publishing Function) 30D, an AMF (API Management Function) 30E, a core network, and an access network belong to a PLMN (PLMN Trust domain), which is a trusted domain. On the other hand, an API caller 30A (e.g., a game server) and a UE 20 (e.g., a resource owner) exist outside the PLMN.

[0059] 11, the API caller 30A may be connected to the AEF 30C via a core network. The UE 20 may be connected to the API caller 30A and the AEF 30C via an access network and a core network.

[0060] Fig. 12 is a diagram showing another example of a system configuration. As shown in Fig. 12, the CCF 30B including the CAPIF-API, the AEF 30C including the service API, the APF 30D, the AMF 30E, the core network, and the access network belong to the PLMN, which is a trusted domain. On the other hand, UE 20-1 and UE 20-2 exist outside the PLMN. UE 20-1 includes, for example, an application that has issued an API call request. UE 20-2 is, for example, a resource owner 40. Note that the application and resource owner functions may be provided in the same device (terminal, etc.).

[0061] 12, the UE 20-1 may be connected to the CCF 30B and the AEF 30C via the access network and the core network, and the UE 20-2 may be connected to the AEF 30C via the access network and the core network.

[0062] 11 and 12 show examples of system configurations, and the present invention is not limited to these. For example, the AEF 30C, the APF 30D, and the AMF 30E may be outside the trusted PLMN domain.

[0063] (Effects of the embodiment) The technology described above allows the resource owner 40 to notify the AEF 30C of permission or denial of any API at any time. Furthermore, by receiving permission or denial in advance, the AEF 30C does not need to inquire of the resource owner 40 whether the call is permitted or not each time an API is called, thereby reducing the amount of signaling.

[0064] Furthermore, the resource owner 40 can update the previously notified permission / denial of API calls to prevent future API calls from being unintentionally permitted / denied.

[0065] (Device configuration) Next, examples of functional configurations of the base station 10, network node 30, resource owner 40, and terminal 20 that perform the processes and operations described above will be described. The base station 10, network node 30, resource owner 40, 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.

[0066] <Base Station 10 and Network Node 30> Fig. 13 is a diagram showing an example of the functional configuration of base station 10. As shown in Fig. 13, 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. 13 is merely an example. The functional divisions and names of the functional units may be any names as long as they can perform the operations according to the embodiment of the present invention.

[0067] The network node 30 (for example, a network node 30 having the function of the AEF 30C) may have the same functional configuration as the base station 10 shown in FIG. 13. Furthermore, a network node 30 having a plurality of different functions in the system architecture may be composed of a plurality of network nodes 30 separated by function. Furthermore, the network node 30 is not limited to a network node existing in a core network or an access network, but may correspond to a network node belonging to a PLMN domain. Furthermore, the resource owner 40 may also have the functional configuration shown in FIG. 13.

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

[0069] The setting unit 130 stores various setting information in a storage device and reads it out from the storage device as needed. The setting information may be, for example, a table of API authorization information.

[0070] The control unit 140 performs, for example, a rejection decision for an API call, an update process for a table of API authorization information, etc. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0071] <Terminal 20> Fig. 14 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 14, 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. 14 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. The terminal 20 may function as a resource owner 40.

[0072] The transmitter 210 generates 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 base station 10 or the network node 30.

[0073] The setting unit 230 stores various setting information received from the base station 10 or the network node 30 by the receiving unit 220 in a storage device, and reads it out from the storage device as required.

[0074] The control unit 240 performs, for example, processing related to connection control to the network and network slices. The functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0075] <Additional Notes> This embodiment provides at least the network node, resource owner device, system, and communication method shown in the following items 1 to 5. (Section 1) a receiving unit that receives an update request for API authorization information from the resource owner device; a control unit that updates the API authorization information it holds in accordance with the update request, and determines whether to permit an API call request from an external application in accordance with the updated API authorization information; A network node comprising: (Section 2) The update request includes identification information of the API whose callability is to be updated, and the control unit updates the entry of the API in the table indicating the API authorization information. 2. The network node of claim 1. (Section 3) a transmitter that transmits an update request for API authorization information to a network node; a receiving unit in the network node that receives an update response from the network node after the API authorization information held therein is updated based on the update request; A resource owner device comprising: (Section 4) a receiving unit that receives an update request for API authorization information from the resource owner device; a control unit that updates the API authorization information it holds in accordance with the update request, and determines whether to permit an API call request from an external application in accordance with the updated API authorization information; a network node comprising: a transmitter for transmitting the update request to the network node; a receiving unit in the network node that receives an update response from the network node after the API authorization information held therein is updated based on the update request; the resource owner device comprising: A system comprising: (Section 5) receiving a request to update API authorization information from the resource owner device; updating the API authorization information held in accordance with the update request, and determining whether to permit an API call request from an external application in accordance with the updated API authorization information; A communication method executed by a network node, comprising:

[0076] Any of the above items 1 to 5 provides a technique that enables changing API authorization information in a network node. In particular, the above item 2 enables changing API authorization information by updating table entries, thereby ensuring reliable updates.

[0077] (Hardware configuration) The block diagrams (FIGS. 13 and 14) 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, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0078] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, 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.

[0079] 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. 15 is a diagram illustrating an example of the hardware configuration of the base station 10, the terminal 20, the network node 30, the resource owner 40, etc. according to an embodiment of the present disclosure. Each of the above-mentioned devices 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.

[0080] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10, the terminal 20, the network node 30, the resource owner 40, etc. 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.

[0081] Each function in the base station 10, terminal 20, network node 30, resource owner 40, etc. is realized by loading specified software (programs) onto hardware such as the processor 1001, 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 auxiliary memory device 1003.

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

[0083] The processor 1001 also loads 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 shown in FIG. 13 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 shown in FIG. 14 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.

[0084] 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 ROM (EPROM), an electrically erasable programmable ROM (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.

[0085] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0086] 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, or a communication module. 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.

[0087] The input device 1005 is an input device (for example, 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 (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

[0089] Furthermore, the base station 10, the terminal 20, the network node 30, the resource owner 40, etc. 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), a field programmable gate array (FPGA), etc., 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.

[0090] Furthermore, the terminal 20, the base station 10, the network node 30, and the resource owner 40 may each be provided in a vehicle 2001, or any one or more of them may be provided in a vehicle 2001. FIG. 16 shows a configuration example of a vehicle 2001. As shown in FIG. 16, 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 in the vehicle 2001, and may be applied to the communication module 2013, for example. All or any of the functions of the terminal 20, the base station 10, the network node 30, and the resource owner 40 may be mounted in the communication module 2013.

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

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

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

[0094] 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 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 obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001.

[0095] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

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

[0098] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, which are input to the electronic control unit 2010.

[0099] The communication module 2013 receives various information (traffic information, traffic signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the 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, axle 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0100] (Supplementary explanation of the embodiment) 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 combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical 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 base station 10, terminal 20, network node 30, resource owner 40, etc. have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. Software operating on a processor in a base station 10, a terminal 20, a network node 30, a resource owner 40, etc. 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.

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

[0102] 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-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended 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.

[0103] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed 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.

[0104] In this specification, a specific operation that is described as being performed by the base station 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 (such as an MME and an S-GW).

[0105] The information or signals 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.

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

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

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

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

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

[0111] Note that terms explained 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.

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

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

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

[0115] In this disclosure, terms such as "base station (BS)," "radio base station," "base station," "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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0116] 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 divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

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

[0119] At least one of the base station and the mobile station may be called 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, or the mobile body itself. 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.

[0120] Furthermore, a base station in the present disclosure may be read as a 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 terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). 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 communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0121] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.

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

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

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

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

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

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

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

[0129] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0130] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0131] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0132] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0133] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0134] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, or the like instead of a subframe. Furthermore, one slot may be called a unit time. The unit time may differ for each cell depending on the numerology.

[0135] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0136] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0137] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0138] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0139] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0140] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0141] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0142] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0143] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0144] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0145] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0146] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0147] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

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

[0150] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0151] 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. [Explanation of symbols]

[0152] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 30 network nodes 40 Resource Owner 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM 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 Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. a receiving unit that receives an update request for API authorization information from the resource owner device; a control unit that updates the API authorization information held therein in accordance with the update request, and determines whether to permit an API call request from an external application in accordance with the updated API authorization information, The update request includes identification information of an API caller and identification information of an API whose callability is to be updated, and the control unit updates entries corresponding to the API caller and the API to be updated in a table indicating the API authorization information. Network node.

2. a transmitter that transmits an update request for API authorization information to a network node; a receiving unit configured to receive an update response from the network node after the API authorization information held therein is updated based on the update request, The update request includes identification information of an API caller and identification information of an API whose callability is to be updated, and in the network node, entries corresponding to the API caller and the API to be updated in a table indicating the API authorization information are updated. Resource owner device.

3. a receiving unit that receives an update request for API authorization information from the resource owner device; a control unit that updates the API authorization information held therein in accordance with the update request, and determines whether to permit an API call request from an external application in accordance with the updated API authorization information, The update request includes identification information of an API caller and identification information of an API whose callability is to be updated, and the control unit updates entries corresponding to the API caller and the API to be updated in a table indicating the API authorization information. a network node; a transmitter for transmitting the update request to the network node; a receiving unit in the network node that receives an update response from the network node after the API authorization information held therein is updated based on the update request; the resource owner device comprising: A system comprising:

4. receiving a request to update API authorization information from a resource owner device; a control step of updating the API authorization information held in accordance with the update request, and determining whether to permit an API call request from an external application in accordance with the updated API authorization information, The update request includes identification information of an API caller and identification information of an API whose callability is to be updated, and in the control step, the network node updates entries corresponding to the API caller and the API to be updated in a table indicating the API authorization information. Communication method.

Images