WO2023187905A1 - Communication device, network node device, and authorization control method - Google Patents

Abstract

This communication device comprises: a control unit that determines whether an event that satisfies conditions for canceling authorization for API calls has occurred; and a transmission unit that, when it is determined that the event has occurred, transmits a request to cancel the authorization for API calls to a network node device.

Description

Communication device, network node device, and authorization control method

The present invention relates to API calls from external applications to network node devices.

In the 3GPP (3rd Generation Partnership Project), 5G or NR (New Radio) is being developed in order to further increase system capacity, further increase data transmission speed, and further reduce latency in wireless sections. Studies are progressing on a wireless communication system called ``5G'' (hereinafter referred to as ``5G'' or ``NR''). In 5G, various wireless technologies are being studied in order to meet the requirements of achieving a throughput of 10 Gbps or more while reducing the delay in the wireless section to 1 ms or less.

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

In addition, for example, an architecture in which a Northbound interface between NEF (Network Exposure Function) and AF (Application Function) in a 5G system is configured using CAPIF (Common API Framework) is being considered (for example, Non-Patent Document 2 and Non-Patent Document 3). ).

In the 3GPP core network, network node devices open APIs (Application Programming Interfaces) for external applications, and for example, a third-party application can call the API to the network node devices.

It is also possible to authorize API calls. That is, it is possible to permit only authorized API calls and reject unauthorized API calls.

However, in the conventional technology, there is no mechanism to revoke the authorization of an API call once authorized, so there is a possibility that unnecessary API calls are made and have an unexpected impact on the user.

The present invention has been made in view of the above points, and an object of the present invention is to provide a technology that makes it possible to revoke the authorization of an authorized API call.

According to the disclosed technology, a control unit that determines whether an event that satisfies conditions for canceling authorization for an API call has occurred;
A communication device is provided, comprising: a transmitting unit that transmits a request to cancel authorization for calling the API to a network node device when it is determined that the event has occurred.

According to the disclosed technology, a technology is provided that makes it possible to revoke the authorization of an authorized API call.

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 under a roaming environment. FIG. 3 is a diagram illustrating an example of an API call. FIG. 2 is a diagram for explaining a problem. FIG. 3 is a diagram for explaining an overview of a processing procedure in an embodiment of the present invention. FIG. 2 is a sequence diagram showing a specific example of a processing procedure in an embodiment of the present invention. FIG. 3 is a sequence diagram showing variations in processing procedures in an embodiment of the present invention. 1 is a diagram showing an example of a system in an embodiment of the present invention. 1 is a diagram showing an example of a system in an embodiment of the present invention. FIG. 2 is a diagram showing an example of a functional configuration of a base station 10 (and a network node device 30, an authorization server 35, and a resource holder client 40) in an embodiment of the present invention. It is a diagram showing an example of the functional configuration of a terminal 20 (and a resource holder client 40) in an embodiment of the present invention. 1 is a diagram showing an example of a hardware configuration of a device in an embodiment of the present invention. 1 is a diagram showing an example of the configuration of a vehicle in an embodiment of the present invention.

Embodiments of the present invention will be described below 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.

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

Furthermore, in the embodiment of the present invention, "configure" the wireless parameters etc. may mean pre-configuring predetermined values, or "pre-configuring" the wireless parameters etc. Alternatively, wireless parameters notified from the terminal 20 may be set.

FIG. 1 is a diagram for explaining an example of a communication system. As shown in FIG. 1, the communication system includes a UE, which is a terminal 20, and a plurality of network node devices 30. Hereinafter, it is assumed that one network node device 30 corresponds to each function, but one network node device 30 may realize multiple functions, or multiple network node devices 30 may realize one function. It's okay. Further, the "connection" described below may be a logical connection or a physical connection.

Furthermore, the base station 10, the terminal 20, and the network node device 30 may all be referred to as a "communication device."

RAN (Radio Access Network) is a network node device 30 having a radio access function, 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 device 30 having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node device 30 that has functions such as a PDU (Protocol Data Unit) session point for the outside that interconnects with a DN (Data Network), packet routing and forwarding, and user plane QoS (Quality of Service) handling. . The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, a plurality of network slices are constructed.

AMF includes 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), Connected to PCF (Policy Control Function) and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are interconnected through their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. This is a network node device 30.

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

FIG. 2 is a diagram for explaining an example of a communication system under a roaming environment. As shown in FIG. 2, the network includes a UE, which is a terminal 20, and a plurality of network node devices 30. Hereinafter, it is assumed that one network node device 30 corresponds to each function, but one network node device 30 may realize multiple functions, or multiple network node devices 30 may realize one function. It's okay. Further, the "connection" described below may be a logical connection or a physical connection.

The RAN is a network node device 30 having a wireless access function, and is connected to the UE, AMF, and UPF. The AMF is a network node device 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 device 30 that has functions such as a PDU session point for the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, a plurality of network slices are constructed.

AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are interconnected through their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf. This is a network node device 30.

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

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

The operation in this embodiment may be performed in either of the configurations shown in FIGS. 1 and 2. Further, the operation in this embodiment may be performed in a configuration other than the configuration shown in FIGS. 1 and 2.

In the above-mentioned NEF, it is possible to implement an API (Application Programming Interface) that can be called from the AF by applying the CAPIF (Common API Framework) architecture. The CAPIF architecture provides a mechanism to support service API operations, such as allowing an API caller to discover service APIs provided by an API provider and enable communication using those service APIs. do. The CAPIF architecture also has a mechanism to hide the topology of the PLMN trust domain from, for example, API callers accessing the service API from outside the PLMN trust domain.

Note that 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, or the API caller application 30A and AEF30C may be provided in the NEF. Each of them may be provided in any network node device 30. The base station 10 may be equipped with an AEF 30C. Further, the terminal 20 may be provided with an application 30A that calls the API.

Further, the resource holder client 40 (resource owner), which will be described later, may be the network node device 30, the terminal 20, the base station 10, or any other device. There may be.

FIG. 3 is a diagram showing an example of an API call. The 3GPP core network opens APIs to external applications, and third-party applications can call the APIs to the network node device 30. When calling an API, the calling application 30A (API invoker) is authenticated and/or authorized by the CAPIF core function (also referred to as CCF) in the core network, and which application calls the API. Manage what you can.

As shown in FIG. 3, the API caller application 30A is pre-registered in the CAPIF core function 30B using the CAPIF-API. The CAPIF core function 30B authenticates and authorizes the third party application 30A. Further, as shown in FIG. 3, the service API is opened by an API providing function (also referred to as AEF) 30C for the authenticated and authorized application 30A, and the application 30A that calls the API , by calling the API, the functions of the API can be used.

The APF (API Publishing Function) 30D has a function of publishing service API information of the API provider to the CAPIF core function 30B. The AMF (API Management Function) 30E has various management functions related to API calls.

Additionally, by extending CAPIF, the resource holder client 40 can authorize the API caller application 30A to make an API call via the authorization server 35. Note that the resource holder client 40 may also be called a network node device, a terminal, a resource holder client device, a resource owner, a communication device, or the like.

(About the assignment)
The resource holder client 40 can grant authorization to the API call request of the API caller application 30A (API invoker), but once the authorization is granted, the API caller will not be able to access the API unless the authorization is revoked. There is a possibility that an additional API call is requested from the application 30A. The challenges caused by the ability to make additional API calls unless authorization is revoked are discussed below.

For example, assume that the resource holder client 40 gives permission to call the QoS change API for temporary use of a competitive game. At this time, if the user forgets to cancel the authorization after the game ends, the API caller application 30A (API invoker) can continue to freely change the QoS of the resource holder client 40. It is undesirable that settings related to end user communication quality, such as QoS, be changed without the approval of the end user (resource holder).

In addition to operations related to end-user communication quality such as QoS changes, operations related to privacy such as obtaining location information, and operations related to billing such as the generation of usage fees for each API, the resource holder client 40 is appropriate. It is desirable to be able to revoke authorization at the appropriate timing.

FIG. 4 is a diagram for explaining the above situation. Note that the configuration of FIG. 4 itself shows the configuration of a communication system according to an embodiment of the present invention, and each device shown in the figure can perform data communication with other devices via a network.

In FIG. 4, the API caller application 30A is authorized to call a certain API. Specifically, for example, the authorization server 35 receives an access token for calling the API. The database 50 stores information regarding authorization.

By using the access token, the API calling application 30A can call the API to the AEF 30C within the validity period of the access token, unless the authorization is revoked. This causes the above-mentioned problem, and therefore, as shown in FIG. 4, it is necessary to cancel the authorization when it becomes unnecessary.

Hereinafter, an example of operation according to this embodiment for solving this problem will be described.

(Configuration and operation example according to embodiment)
In this embodiment, as shown in FIG. 5, the above-mentioned authorization can be canceled in a system configuration including an authorization server 35, a resource holder client 40, and a database 50.

The authorization server 35 is a type of network node device. The authorization server 35 may include the functions of the AEF 30C, may include the functions of the CAPIF core function 30B, may be a network node device that includes both the AEF 30C and the CAPIF core function 30B, or may include the functions of the AEF 30C and the CAPIF core function 30B. It may be a network node device that does not have any of the functions 30B.

The database 50 is a device that holds authorization information and is a type of network node device. The database 50 may be provided outside the authorization server 35 or may be provided inside the authorization server 35. The authorization information held by the database 50 is, for example, information that associates an access token (character string), an ID of an API, and information indicating whether calling of the API is authorized. These pieces of information are information registered in the database 50 by the authorization server 35.

An example of operation will be described with reference to FIG.

First, as a precondition, the resource holder client 40 has granted authorization for a specific API call to the API caller application 30A. Specifically, in this state, the database 50 stores an access token, the ID of the specific API, and information indicating that calling of the specific API is authorized, and the API caller Application 30A holds this access token.

As a preliminary preparation, conditions for canceling API call authorization are set in advance in the resource holder client 40.

As shown in FIG. 5, when the resource holder client 40 detects the occurrence of an event that satisfies the above conditions, it transmits an authorization cancellation request to the authorization server 35.

Upon receiving the authorization cancellation request, the authorization server 35 authenticates the resource holder client 40, and if the authentication (specifically, authentication information verification) is successful, the authorization server 35 invalidates the authorization for the given API call. do.

For example, the authorization server 35 deletes the access token of the corresponding entry in the database 50. That is, if the entry information is {access token, API ID, callable}, "{access token, API ID, callable}" is deleted.

Alternatively, the authorization server 35 may cancel the authorization by changing {access token, API ID, callable} to {access token, API ID, callable}. In other words, authorization may be revoked by making the access token unusable.

<Conditions for revocation of approval>
Examples of conditions that trigger the transmission of an authorization cancellation request include conditions (1) to (5) below. Note that the following conditions (1) to (5) are all examples, and the conditions that trigger the transmission of an authorization cancellation request are not limited to the following conditions (1) to (5).

(1) Application Status For example, the resource holder client 40 cancels the QoS change API call authorization using the termination of the competitive game application as a trigger. Thereafter, the QoS change API call may be authorized again using the start of the competitive game application as a trigger.

(2) Time/Time For example, the resource holder client 40 cancels the API call authorization when a preset time has elapsed from the time when the API call was authorized.

Also, for example, the resource holder client 40 may cancel API call authorization at a preset time.

(3) Location information For example, when the resource holder client 40 detects that it has moved to a preset location (eg, moved outside Tokyo), it cancels API call authorization.

The resource holder client 40 may determine whether it exists in a specific location using location information obtained by the GPS function or based on the cell ID of the cell in which it is located. However, the judgment may be made from an image obtained by a camera held by the person, from sound obtained by a microphone held by the person, or by other methods.

(4) Communication quality For example, the resource holder client 40 measures the communication delay to a specific server, and if it detects that the delay value has become larger than a preset reference value, the resource holder client 40 makes an API call. Revoke authorization.

Additionally, the resource holder client 40 and an external server may cooperate to detect an event (an event indicating that a condition is met).

For example, if the condition is that "the communication delay to a certain server exceeds a threshold", the resource holder client 40 sends a packet to a specific server, and the time required for the packet to return to the resource holder client 40 is It is possible to check whether the conditions are satisfied based on the round trip time.

(5) Wireless quality For example, when the resource holder client 40 detects that the strength of radio waves received from the base station has fallen below a preset reference value for a preset period of time, the resource holder client 40 requests API call authorization. cancel.

Note that in the examples (1) to (5) above, the resource holder client 40 itself holds the conditions for authorization cancellation and judges whether an event that satisfies the conditions has occurred, but this is just an example. be. Another entity (referred to as an external server 60) external to the resource holder client 40 may maintain conditions for authorization revocation and determine whether an event that satisfies the conditions has occurred.

When the external server 60 detects that an event that satisfies the conditions for authorization revocation has occurred, it notifies the resource holder client 40 that an event that satisfies the conditions for authorization revocation has occurred, for example. After that, the resource holder client 40 sends a cancellation request to the authorization server 35, similar to the process described above. Alternatively, when the external server 60 detects that an event that satisfies the conditions for authorization revocation has occurred, the external server 60 itself may transmit a revocation request to the authorization server 35.

<Multiple APIs>
If there are multiple authorized APIs, the resource holder client 40 maintains the conditions for each API, and when it detects that the conditions corresponding to a certain API are met, requests cancellation of authorization for that API. Send.

In this case, the resource holder client 40 holds information (table) in a format such as "(API_1, condition 1), (API_2, condition 2), ..., (API_n, condition n)" as a condition, for example. .

<About reauthorization>
Note that after canceling API call authorization as described above, it is also possible to authorize again. In that case, for example, the resource holder client 40 transmits an API call authorization request to the authorization server 35.

Upon receiving the authorization request, the authorization server 35 authenticates the resource holder client 40, and if the authentication (specifically, verification of the authentication information) is successful, the authorization server 35 validates the authorization for the API call. For example, the authorization server 35 changes the corresponding entry {access token, API ID, callable} in the database 50 to {access token, API ID, callable}. Further, if the entry has been deleted, a new entry, that is, {access token, API ID, callable} is generated, and the access token is paid out to the API calling application 30A.

When performing reauthorization, the resource holder client 40 sends a message to the authorization server 35 in the same manner as the above-mentioned cancellation, using the detection of the occurrence of an event that satisfies preset conditions as reauthorization conditions as a trigger. , an API call authorization request may be sent.

(Sequence example)
Next, a more detailed example of operation in this embodiment will be described with reference to the sequence diagram of FIG. 6. As a premise for the following operations, it is assumed that calls to a certain API are authorized. Additionally, the resource holder client 40 holds conditions for requesting cancellation of authorization.

Note that there are access tokens and refresh tokens as tokens, which will be collectively referred to as "tokens" below. The token may also be called "access permission information."

As shown in S101, the API caller application 30A holds tokens, and the database 50 stores information regarding the tokens. The information regarding the token is, for example, the information {token, API ID, callable}.

At S102, the resource holder client 40 detects an event that satisfies preset conditions.

In S103, the resource holder client 40 transmits an authorization cancellation request to the authorization server 35. This request message includes, for example, the ID of the target API and information indicating that it is a cancellation request.

In S104, the authorization server 35 authenticates the resource holder client 40. Any authentication method may be used; for example, the authorization server 35 requests the resource holder client 40 for an ID/password, and the resource holder client 40 sends the ID/password to the authorization server 35. Authentication may be performed by Here, it is assumed that the authentication was successful.

In S105, the authorization server 35 transmits a token deletion request to the database 50. This request message includes, for example, the ID of the target API. In S106, the database 50 deletes the token corresponding to the target API. Alternatively, as described above, the token may be managed as "uncallable" without being deleted.

In S107, the database 50 returns a deletion response to the authorization server 35. In S108, the authorization server 35 returns a response to the resource holder client 40 indicating that the call authorization for the target API has been revoked.

After that, in S109, the API calling application 30A uses the old token (the token that has been deleted or is disabled to call) to send a request to call the target API to the AEF 30C. The AEF 30C accesses the database 50 and tries to refer to the information regarding the token, but fails to refer to the information regarding the token. Alternatively, check the information regarding the token and understand that it is "uncallable." In S111, the AEF 30C transmits an API call rejection message to the API caller application 30A.

<Sequence variations>
As described above, the external server 60 may detect events that satisfy the cancellation conditions. FIG. 7 shows an example of a sequence when the external server 60 detects an event that satisfies the cancellation conditions. In the following, description of the same parts as those in FIG. 6 will be omitted or simplified.

As shown in FIG. 7, communication is possible between the resource holder client 40 and the external server 60, and the external server 60 transmits information necessary for detecting an event that satisfies the cancellation condition to the resource holder client at any time. It can be obtained from 40. Note that if it is possible to detect an event that satisfies the cancellation conditions without using information from the resource holder client 40, it is not necessary to acquire the information from the resource holder client 40.

In S102, the external server 60 detects an event that satisfies preset conditions.

In S103, the external server 60 transmits an authorization cancellation request to the authorization server 35. This request message includes, for example, information indicating the resource holder client 40 (IP address, etc.), the ID of the target API, and information indicating that it is a cancellation request. In S104, the authorization server 35 authenticates the resource holder client 40.

After S105 to S107, in S108, the authorization server 35 returns a response to the external server 60 indicating that the call authorization for the target API has been revoked. After S108, the external server may notify the API calling application 30A of information indicating that the authorization to call the target API has been revoked.

(Specific system configuration example)
FIG. 8 shows a specific configuration example of a system according to this embodiment, assuming a 5G system. FIG. 8 shows, as an example, a case where the UE (terminal) 20 is the resource holder client 40 and the CCF 30B is the authorization server 35. The database 50 may also be included in the CCF 30B.

In the example of FIG. 8, the trusted domain PLMN (PLMN Trust domain) includes CCF 30B including CAPIF-API, AEF 30C including service API, APF (API Publishing Function) 30D, AMF (API Management Function) 30E, and UE 20. (eg, resource holder client 40), core network, and access network. On the other hand, an API caller application 30A (for example, a game server) exists outside the PLMN.

As shown in FIG. 8, the UE 20 may be connected to the API calling application 30A, AEF 30C, and CCF 30B via an access network and a core network.

FIG. 9 is a diagram showing another example of the system configuration. As shown in FIG. 9, the CCF 30B including the CAPIF-API, the AEF 30C including the service API, the APF 30D, the AMF 30E, the UE 20-1, the UE 20-2, the core network, and the access network belong to the PLMN, which is a trusted domain. The UE 20-1 includes, for example, an application that is an API call request source. The UE 20-2 is, for example, the resource holder client 40. Note that the functions of the application and the resource holder client may be provided in the same device (such as a terminal).

As shown in FIG. 9, the UE 20-1 may be connected to the CCF 30B and AEF 30C via an access network and a core network. Further, the UE 20-2 may be connected to the CCF 30B and the AEF 30C via an access network and a core network.

Note that FIGS. 8 and 9 show an example of the system configuration, and the system configuration is not limited thereto. For example, AEF 30C, APF 30D, and AMF 30E may be outside the trusted PLMN domain.

(Effects of embodiment)
Using the technology described above, by setting conditions for revoking authorization in advance for the resource holder client 40 (terminal held by the resource holder), it is possible to prevent API calls from being inadvertently allowed. It can be prevented.

In the existing OAuth 2.0 specification, the token itself can have an expiration date, but the technology according to this embodiment goes beyond that by providing dynamic information such as device location information, application status, and real-time communication quality. This makes it possible to more flexibly control authorization revocation based on relevant information.

This allows the terminal user to automatically allow API calls only under certain conditions and cancel them otherwise.

(Device configuration)
Next, an example of the functional configuration of the base station 10, network node device 30, resource holder client 40, database 50, and terminal 20 that implement the processes and operations described above will be described. Note that the authorization server 35, database 50, and external server 60 are all types of network node device 30. Note that the database 50 may be provided inside the authorization server 35.

Note that the base station 10, network node device 30, resource holder client 40, database 50, external server 60, and terminal 20 may all be referred to as "communication devices."

<Base station 10 and network node device 30>
FIG. 10 is a diagram showing an example of the functional configuration of the base station 10. As shown in FIG. As shown in FIG. 10, base station 10 includes a transmitting section 110, a receiving section 120, a setting section 130, and a control section 140. The functional configuration shown in FIG. 10 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names.

Note that the network node device 30 (for example, the network node device 30 having the function of the AEF 30C, the authorization server 35, the database 50, the external server 60, etc.) may have the same functional configuration as the base station 10 shown in FIG. . Further, the network node device 30 having a plurality of different functions in the system architecture may be configured from a plurality of network node devices 30 separated for each function. Further, the network node device 30 is not limited to a network node device existing in a core network or an access network, but may correspond to a network node device belonging to a PLMN domain. Further, the resource holder client 40 may also have the functional configuration shown in FIG.

The transmitting unit 110 includes a function of generating a signal to be transmitted to the terminal 20 or other network node device 30, and transmitting the signal by wire or wirelessly. The receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 or other network node devices 30 and acquiring, for example, information of a higher layer from the received signals.

The setting unit 130 stores various setting information in a storage device, and reads it from the storage device as necessary.

The control unit 140 controls the entire device. 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.

<Terminal 20>
FIG. 11 is a diagram showing an example of the functional configuration of the terminal 20. As shown in FIG. 11, the terminal 20 includes a transmitting section 210, a receiving section 220, a setting section 230, and a control section 240. The functional configuration shown in FIG. 11 is only an example. As long as the operations according to the embodiments of the present invention can be carried out, the functional divisions and functional parts may have any names. The terminal 20 may function as a resource holder client 40.

The transmitter 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 220 wirelessly receives various signals and obtains higher layer signals from the received physical layer signals. Further, the receiving unit 220 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 device 30.

The setting unit 230 stores various setting information received from the base station 10 or network node device 30 by the receiving unit 220 in a storage device, and reads it from the storage device as necessary. The storage device also stores conditions for authorization cancellation.

The control unit 240 performs, for example, processing related to connection control to networks and network slices. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220. When the terminal 20 functions as the resource holder client 40, the terminal 20 may be equipped with a display capable of inputting and outputting, similar to a smartphone or the like.

<Additional notes>
The present embodiment provides at least the communication device, network node device, and authorization control method shown in Additional Notes 1 to 6 below.
(Additional note 1)
a control unit that determines whether an event that satisfies conditions for canceling authorization for calling the API has occurred;
a transmission unit that transmits a request to cancel authorization for calling the API to a network node device when it is determined that the event has occurred.
(Additional note 2)
The condition is any one of a plurality of conditions including at least a condition related to an application state, a condition related to time, a condition related to location, a condition related to communication quality, and a condition related to wireless quality. Communication device.
(Additional note 3)
a receiving unit that receives a request to cancel authorization for calling the API from a communication device that has detected an event that satisfies conditions for canceling authorization for calling the API;
and a control unit that executes a process of canceling authorization for calling the API based on the request.
(Additional note 4)
The network node device according to appendix 3, wherein the control unit deletes the access permission information used for calling the API from the database or makes the access permission information unusable.
(Additional note 5)
Determine whether an event that satisfies the conditions for revoking the authorization of the API call has occurred;
If it is determined that the event has occurred, transmitting a request to cancel authorization for calling the API to the network node device;
An authorization control method executed by a communication device.
(Additional note 6)
receiving a request to revoke authorization for calling the API from a communication device that has detected an event that satisfies conditions for revoking authorization for calling the API;
Based on the request, perform processing to revoke authorization for calling the API;
An authorization control method executed by a network node device.

Any of Supplementary Notes 1 to 6 provides a technology that makes it possible to revoke authorization for an API call once authorized. According to Additional Note 2, judgments can be made based on various conditions. According to Additional Note 4, the process of canceling API call permission can be appropriately executed.

(Hardware configuration)
The block diagrams (FIGS. 10 and 11) used to explain the above embodiments show blocks in functional units. 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 one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, These include, but are not limited to, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. I can't do it. For example, a functional block (configuration unit) that performs transmission is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, the network node device 30, terminal 20, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 12 is a diagram illustrating an example of the hardware configuration of the base station 10, terminal 20, network node device 30, authorization server 35, resource holder client 40, external server 60, etc. according to an embodiment of the present disclosure. . Each of the above 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, and the like.

Note that in the following description, the word "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10, terminal 20, network node device 30, authorization server 35, resource holder client 40, etc. may be configured to include one or more of each device shown in the figure, or may be configured to include one or more of each device shown in the figure. It may also be configured without including any other device.

Each function in the base station 10, terminal 20, network node device 30, authorization server 35, resource holder client 40, external server 60, etc. is implemented by predetermined software (program) on hardware such as the processor 1001, storage device 1002, etc. This is achieved by causing the processor 1001 to perform calculations and controlling communication by the communication device 1004 and/or controlling at least one of data reading and writing in the storage device 1002 and the auxiliary storage device 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, the above-described control unit 140, control unit 240, etc. may be implemented by the processor 1001.

Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 140 shown in FIG. 10 may be realized by a control program stored in the storage device 1002 and operated on the processor 1001. Further, for example, the control unit 240 shown in FIG. 11 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001. Although the various processes described above have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunications line.

The storage device 1002 is a computer-readable recording medium, such as at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. may be configured. The storage device 1002 may be called a register, cache, main memory, or the like. The storage device 1002 can store executable programs (program codes), software modules, and the like to implement a communication method according to an embodiment of the present disclosure.

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

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 a network device, network controller, network card, communication module, etc., for example. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of. For example, a transmitting/receiving antenna, an amplifier section, a transmitting/receiving section, a transmission line interface, etc. may be realized by the communication device 1004. The transmitting and receiving unit may be physically or logically separated into a transmitting unit and a receiving unit.

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts 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 have an integrated configuration (for example, a touch panel).

Further, 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 for each device.

In addition, the base station 10, terminal 20, network node device 30, authorization server 35, resource holder client 40, external server 35, etc. are equipped with a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), etc. ), PLD (Programmable Logic Device), FPGA (Field Programmable Gate Array), etc., and a part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

Further, the vehicle 2001 may be provided with each of the terminal 20, the base station 10, the network node device 30, the authorization server 35, the resource holder client 40, and the external server 60, or any one or more of these. . FIG. 13 shows an example of the configuration of vehicle 2001. As shown in FIG. 13, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, a front wheel 2007, a rear wheel 2008, an axle 2009, an electronic control unit 2010, and various sensors 2021 to 2029. , an information service section 2012 and a communication module 2013. Each aspect/embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, may be applied to communication module 2013. All or any functions of the terminal 20, base station 10, network node device 30, authorization server 35, and resource holder client 40 may be installed in the communication module 2013.

The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel), 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.

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

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

The information service department 2012 includes various devices such as car navigation systems, audio systems, speakers, televisions, and radios for providing various information such as driving information, traffic information, and entertainment information, as well as one or more devices that control these devices. It consists of an ECU. The information service unit 2012 provides various multimedia information and multimedia services to the occupants of the vehicle 2001 using information acquired from an external device via the communication module 2013 and the like.

The driving support system unit 2030 includes a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (for example, GNSS, etc.), map information (for example, a high-definition (HD) map, an autonomous vehicle (AV) map, etc.) ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors that prevent accidents and reduce the driver's driving burden. The system is comprised of various devices that provide functions for the purpose and one or more ECUs that control these devices. Further, the driving support system unit 2030 transmits and receives various information via the communication module 2013, and realizes a driving support function or an automatic driving function.

Communication module 2013 can communicate with microprocessor 2031 and components of vehicle 2001 via a communication port. For example, the communication module 2013 communicates with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, electronic Data is transmitted and received between the microprocessor 2031, memory (ROM, RAM) 2032, and sensors 2021 to 29 in the control unit 2010.

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 external devices. For example, various information is transmitted and received with an 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.

The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. In addition, the communication module 2013 also receives the front wheel and rear wheel rotational speed signals inputted to the electronic control unit 2010 and acquired by the rotational speed sensor 2022, the front wheel and rear wheel air pressure signals acquired by the air pressure sensor 2023, and the vehicle speed sensor. 2024, an acceleration signal obtained by acceleration sensor 2025, an accelerator pedal depression amount signal obtained by accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by brake pedal sensor 2026, and a shift lever. A shift lever operation signal acquired by the sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028 are also transmitted to the external device via wireless communication.

The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 2012 provided in the vehicle 2001. Communication module 2013 also stores various information received from external devices into memory 2032 that can be used by microprocessor 2031 . Based on the information stored in the memory 2032, the microprocessor 2031 controls the drive section 2002, steering section 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheel 2007, rear wheel 2008, and axle 2009 provided in the vehicle 2001. , sensors 2021 to 2029, etc. may be controlled.

(Supplementary information on 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, modifications, alternatives, replacements, etc. Probably. Although the invention has been explained using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The classification of items in the above explanation is not essential to the present invention, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be used in another item. may be applied to the matters described in (unless inconsistent). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. The operations of a plurality of functional sections may be physically performed by one component, or the operations of one functional section may be physically performed by a plurality of components. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as there is no contradiction. For convenience of processing explanation, the base station 10, terminal 20, network node device 30, authorization server 35, resource holder client 40, etc. have been explained using a functional block diagram, but such devices are hardware, It may be implemented in software or a combination thereof. According to the embodiment of the present invention, the software operated by the processors of the base station 10, terminal 20, network node device 30, authorization server 35, resource holder client 40, etc. includes random access memory (RAM), flash memory, read memory, etc. The information may be stored in a dedicated memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

Each aspect/embodiment described in this disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). 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), and other appropriate systems and systems expanded based on these. It may be applied to at least one next generation system. Furthermore, a combination of a plurality of systems may be applied (for example, a combination of at least one of LTE and LTE-A and 5G).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this specification may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.

In this specification, specific operations performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes including a base station 10, various operations performed for communication with a terminal 20 are performed by the base station 10 and other network nodes other than the base station 10. It is clear that this can be done by at least one of the following: for example, MME or S-GW (possible, but not limited to). Although the case where there is one network node other than the base station 10 is illustrated above, the other network node may be a combination of multiple other network nodes (for example, MME and S-GW). .

The information, signals, etc. described in this disclosure can be output from an upper layer (or lower layer) to a lower layer (or upper layer). It may be input/output via multiple network nodes.

The input/output information may be stored in a specific location (for example, memory) or may be managed using a management table. Information etc. to be input/output may be overwritten, updated, or additionally written. The output information etc. may be deleted. The input information etc. may be transmitted to other devices.

The determination in the present disclosure may be performed based on a value represented by 1 bit (0 or 1), a truth value (Boolean: true or false), or a comparison of numerical values (e.g. , comparison with a predetermined value).

Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create a website, When transmitted from a server or other remote source, these wired and/or wireless technologies are included within the definition of transmission medium.

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., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of

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 the channel and the symbol may be a signal. Also, the signal may be a message. Further, a component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

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

In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by an index.

The names used for the parameters mentioned above are not restrictive in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (e.g. PUCCH, PDCCH, etc.) and information elements may be identified by any suitable designation, the various names assigned to these various channels and information elements are in no way exclusive designations. isn't it.

In this disclosure, "Base Station (BS)," "wireless base station," "base station," "fixed station," "NodeB," "eNodeB (eNB)," and "gNodeB ( gNB)”, “access point”, “transmission point”, “reception point”, “transmission/reception point”, “cell”, “sector”, Terms such as "cell group," "carrier," "component carrier," and the like may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells. If 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 is divided into multiple subsystems (e.g., small indoor base stations (RRHs)). Communication services can also be provided by Remote Radio Head). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.

In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

A mobile station is defined by a person 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 It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving object may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving object (for example, a drone, a self-driving car, etc.), or a robot (manned or unmanned). ). Note that at least one of the base station and the mobile station includes 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.

Additionally, the base station in the present disclosure may be replaced by a terminal. For example, a configuration in which communication between a base station and a terminal is replaced with communication between a plurality of terminals 20 (for example, it may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) Each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 20 may have the functions that the base station 10 described above has. Further, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be replaced with side channels.

Similarly, a terminal in the present disclosure may be replaced by a base station. In this case, a configuration may be adopted in which the base station has the functions that the above-described terminal has.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of operations. "Judgment" and "decision" include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, and inquiry. (e.g., searching in a table, database, or other data structure), and regarding an ascertaining as a "judgment" or "decision." In addition, "judgment" and "decision" refer to receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and access. (accessing) (e.g., accessing data in memory) may include considering something as a "judgment" or "decision." In addition, "judgment" and "decision" refer to resolving, selecting, choosing, establishing, comparing, etc. as "judgment" and "decision". may be included. In other words, "judgment" and "decision" may include regarding some action as having been "judged" or "determined." Further, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

The terms "connected", "coupled", or any variations thereof, refer to any connection or coupling, direct or indirect, between two or more elements and to each other. It may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled." The bonds or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access." As used in this disclosure, two elements may include one or more electrical wires, cables, and/or printed electrical connections, as well as in the radio frequency domain, as some non-limiting and non-inclusive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and non-visible) ranges.

The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applied standard.

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

As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.

"Means" in the configurations of each of the above devices may be replaced with "unit", "circuit", "device", etc.

Where "include", "including" and variations thereof are used in this disclosure, these terms, like the term "comprising," are inclusive. It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.

A radio frame may be composed of one or more frames in the time domain. Each frame or frames in the time domain may be called a subframe. A subframe may also be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

The numerology may be a communication parameter applied to the transmission and/or reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, and transmitter/receiver. It may also indicate at least one of a specific filtering process performed in the frequency domain, a specific windowing process performed by the transceiver in the time domain, and the like.

A slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. A slot may be a unit of time based on numerology.

A slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (or PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol.

For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. It's okay. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe. Furthermore, one slot may be called a unit time. The unit time may be different for each cell depending on the numerology.

Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each terminal 20) to each terminal 20 on a TTI basis. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.

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

Additionally, the time domain of an RB may include one or more symbols, and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

Note that one or more RBs include physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. May be called.

Additionally, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A bandwidth part (BWP) (which may also be called a partial bandwidth or the like) may represent a subset of consecutive common resource blocks (RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

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 of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

The structures of radio frames, subframes, slots, minislots, symbols, etc. described above 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 symbols included in an RB, Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

In this disclosure, when articles are added by translation, such as a, an, and the in English, the present disclosure may include that the nouns following these articles are plural.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."

Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. In addition, notification of prescribed information (for example, notification of "X") is not limited to being done explicitly, but may also be done implicitly (for example, not notifying the prescribed information). Good too.

Although the present disclosure has been described in detail above, it is clear for those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as determined by the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and is not intended to have any limiting meaning on the present disclosure.

10 base station 110 transmitting section 120 receiving section 130 setting section 140 control section 20 terminal 210 transmitting section 220 receiving section 230 setting section 240 control section 30 network node 35 authorization server 40 resource holder client 50 database 60 external server 1001 processor 1002 storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive section 2003 Steering section 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control section 2012 Information service section 2013 Communication module 2021 current Sensor 2022 Rotational 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 support system section 2031 Microprocessor 2032 Memory (ROM, RAM)
2033 Communication port (IO port)

Claims (6)

1. a control unit that determines whether an event that satisfies conditions for canceling authorization for calling the API has occurred;
   a transmission unit that transmits a request to cancel authorization for calling the API to a network node device when it is determined that the event has occurred.
2. The condition is any one of a plurality of conditions including at least a condition related to an application state, a condition related to time, a condition related to location, a condition related to communication quality, and a condition related to wireless quality. Communication device.
3. a receiving unit that receives a request to cancel authorization for calling the API from a communication device that has detected an event that satisfies conditions for canceling authorization for calling the API;
   and a control unit that executes a process of canceling authorization for calling the API based on the request.
4. The network node device according to claim 3, wherein the control unit deletes the access permission information used for calling the API from the database or makes the access permission information unusable.
5. Determine whether an event that satisfies the conditions for revoking the authorization of the API call has occurred;
   If it is determined that the event has occurred, transmitting a request to cancel authorization for calling the API to the network node device;
   An authorization control method executed by a communication device.
6. receiving a request to revoke authorization for calling the API from a communication device that has detected an event that satisfies conditions for revoking authorization for calling the API;
   Based on the request, perform processing to revoke authorization for calling the API;
   An authorization control method executed by a network node device.

Images