WO2023067742A1 - Network node and communication method - Google Patents

Abstract

This network node determines whether to permit or reject calling of a new application programming interface (API), on the basis of the upper limit of the number of applications for which an API can be called, and registered applications, and notifies of the permission or rejection of calling of the API.

Description

Network node and communication method

The present disclosure relates to network nodes and communication methods.

In the 3GPP (3rd Generation Partnership Project), 5G or NR (New Radio) and NR (New Radio) are being used in order to further increase the system capacity, further increase the data transmission speed, and further reduce the delay in the wireless section. A wireless communication system called "5G" (hereinafter, the wireless communication system is referred to as "5G" or "NR") is under study. In 5G, various radio technologies are being studied in order to meet the requirements of realizing a throughput of 10 Gbps or more and keeping the delay in the radio section to 1 ms or less.

In NR, 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core) which is the core network in LTE (Long Term Evolution) network architecture and E-UTRAN (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 under consideration (see Non-Patent Document 1).

Also, for example, an architecture (hereinafter referred to as "CAPIF architecture") that configures the Northbound interface used between NEF (Network Exposure Function) and AF (Application Function) in 5G systems with CAPIF (Common API Framework) is under consideration. (See Non-Patent Documents 2, 3, and 4). CAPIF is defined as a framework that can be applied to all APIs (Application Programming Interfaces) provided by 3GPP.

　The 3GPP core network opens APIs for external applications, and CAPIF allows third-party applications to call the APIs.

　However, there is room for further investigation regarding CAPIF control when API calls are made consecutively from multiple applications.

One aspect of the present disclosure is a network that can prevent unintentional change of settings by an API called earlier by an API called later when API calls are made in succession from a plurality of applications. A node and communication method are provided.

A network node according to an aspect of the present disclosure controls to determine permission or rejection of a new API call based on the upper limit number of applications that can call an API (Application Programming Interface) and registered applications. and a transmission unit for notifying permission or refusal of calling the API.

In a communication method according to an aspect of the present disclosure, a network node permits or denies new API calls based on the upper limit number of applications that can call APIs (Application Programming Interface) and registered applications. is determined, and permission or refusal of calling the new API is notified.

1 is a diagram for explaining an example of a communication system; FIG. FIG. 4 is a diagram for explaining another example of a communication system under roaming environment; 1 is a diagram for explaining a CAPIF architecture; FIG. FIG. 4 is a diagram for explaining the first sequence of CAPIF; FIG. FIG. 4 is a diagram for explaining a second sequence of CAPIF; FIG. FIG. 4 is a diagram for explaining a second sequence of CAPIF; FIG. FIG. 10 is a diagram showing an example of an API invoker list; 1 is a diagram illustrating an example of a functional configuration of a terminal according to an embodiment of the present disclosure; FIG. It is a diagram showing an example of a functional configuration of a base station according to an embodiment of the present disclosure. 2 is a diagram illustrating an example of a functional configuration of NEF according to an embodiment of the present disclosure; FIG. 2 is a diagram illustrating an example of hardware configuration of a terminal, base station, data hub access support device, or other network node according to an embodiment of the present disclosure; FIG. It is a figure showing an example of composition of vehicles in an embodiment of the invention.

(Circumstances leading to the present invention)
An API invoker, such as an application in a smartphone, is registered (onboarded) in a CCF (CAPIF Core Function). The CCF authenticates/authorizes the API invoker based on the registration information. When the API invoker receives authorization to call an API from the CCF, it calls an API to an AEF (API exposing function) within an APD (API provider domain). The AEF performs processing corresponding to API calls, such as notifying the Core Network of API contents such as QoS.

When API calls are made continuously (within a predetermined time) from each of a plurality of API invokers, the AEF sequentially performs processing corresponding to each API call.

If API calls from multiple API invokers compete, for example, if API calls that apply to the same communication path and require different QoS properties are made in succession, the call will The API QoS performed is reflected (overwritten) in the Core Network communication path.

For example, application A calls an API requesting QoS that realizes high-speed, large-capacity communication for downloading a large amount of data in the background. Suppose that an API requesting QoS for achieving low-delay communication for comfortable playing is performed. In this case, the QoS for high-speed, large-capacity communication requested by application A is overwritten by the QoS for low-delay communication requested by application B on the communication path of the Core Network.

As a result, application A will not be able to continue high-speed, large-capacity communication in the background.

The inventor focused on this problem and came to the present invention.

Embodiments of the present disclosure will be described below with reference to the drawings. The embodiments described below are examples, and the embodiments to which the present disclosure is applied are not limited to the following embodiments.

For the operation of the wireless communication system according to the embodiment of the present disclosure, existing technology may be used as appropriate. The existing technology is, for example, existing LTE or existing 5G, but is not limited to existing LTE or existing 5G.

In addition, in the following description, the node names, signal names, etc. described in the 5G standard (or LTE standard) are currently used, but node names and signal names having the same functions as these are used. Names, etc. may be called by names different from these.

For example, in the embodiments of the present disclosure described below, SS (Synchronization Signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical Broadcast Channel), PRACH (Physical Random Access Channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel) and other terms may be used. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, and the like. However, even a signal used for NR is not necessarily specified as "NR-".

(System configuration example A)
FIG. 1 is a diagram for explaining an example of a communication system 1A. As shown in FIG. 1, the communication system 1A includes, for example, a UE 10A (User Equipment: may be called a (user) terminal or a (user) node), a plurality of network nodes 20A, 30A-1 to 30A-10 (which may be called NF (Network Function)) and 40A. Hereinafter, one network node corresponds to each function, but one network node may implement a plurality of functions, or a plurality of network nodes may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

The NG-RAN (Next Generation - Radio Access Network) 20A is a network node with radio access functionality, and may be, for example, a gNB (next generation Node B) (which may also be called a base station). NG-RAN 20A is connected to UE 10A, AMF (Access and Mobility Management Function) 30A-1 and UPF (User Plane Function) 40A.

AMF30A-1 is a network node having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. AMF 30A-1 includes UE 10A, NG-RAN 20A, SMF (Session Management function) 30A-2, NSSF (Network Slice Selection Function) 30A-3, NEF (Network Exposure Function) 30A-4, NRF (Network Repository Function) 30A- 5, UDM (Unified Data Management) 30A-6, AUSF (Authentication Server Function) 30A-7, PCF (Policy Control Function) 30A-8, AF (Application Function) 30A-9 and NWDAF (Network Data Analytics Function) 30A- 10. Note that the AMF 30A-1 may also be called an access mobility management device.

AMF30A-1, SMF30A-2, NSSF30A-3, NEF30A-4, NRF30A-5, UDM30A-6, AUSF30A-7, PCF30A-8, AF30A-9 and NWDAF30A-10 are interfaces Namf, Nsmf , Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf and Nnwdaf, respectively.

SMF30A-2 is a network node 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. Note that the SMF 30A-2 may be called a session management device.

NSSF 30A-3 is a network node that has functions such as selecting a network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. is.

The NEF 30A-4 is a network node that has the function of notifying other NFs of capabilities and events.

NRF 30A-5 is a network node that has the function of discovering NF instances that provide services.

The UDM 30A-6 is a network node that manages subscriber data and authentication data. UDM 30A-6 is connected to a UDR (User Data Repository) that holds the data.

AUSF 30A-7 is a network node that authenticates subscribers/UEs 10 against subscriber data held in UDR.

The PCF 30A-8 is a network node that has the function of performing network policy control.

AF30A-9 is a network node that has the function of controlling the application server.

NWDAF30A-10 is a network node that collects and analyzes data acquired by the network and provides analysis results.

UPF 40A is a network that has functions such as PDU (Protocol Data Unit) session point for the outside that interconnects with NG-RAN 20 and DN (Data Network) 50A, packet routing and forwarding, user plane QoS (Quality of Service) handling, etc. A node that transmits and receives user data. Note that the UPF 40A may also be called a user plane device.

For example, one UPF 40A and DN 50A may constitute a network slice. A plurality of network slices are constructed in the wireless communication network according to the embodiment of the present disclosure. One UPF 40A may operate one network slice, or one UPF 40A may operate a plurality of network slices.

Also, the UPF 40A is physically one or more computers (servers, etc.), and can be made by logically integrating and dividing the hardware resources (CPU, memory, hard disk, network interface, etc.) of the computer. A plurality of resources can be viewed as a resource pool and each resource can be used as a network slice for the resource pool. The UPF 40A operating the network slice means, for example, managing the correspondence between the network slice and the resource, starting/stopping the resource, monitoring the operation status of the resource, and the like.

(System configuration example B)
FIG. 2 is a diagram for explaining an example of the communication system 1B under the roaming environment. As shown in FIG. 2, the communication system 1B includes, for example, a UE 10B, which is a communication terminal (node) used by a user, and a plurality of network nodes 20B, 30B-1 to 30B-12, 40B.

The communication system 1B is a system included in the 5G network system, and is a system that provides network services to the UE 10B through data communication. Network services refer to services using network resources, such as communication services (dedicated line services, etc.) and application services (video distribution, services using sensor devices such as embedded devices).

Also, in FIG. 2, it is assumed that the UE 10B is in a roaming environment. The UE 10 is in a roaming environment, which is different from the HPLMN (Home Public Land Mobile Network) which is the network (home network) of the operator to which the user of the UE 10 has a contract. Indicates that the VPLMN (Visited Public Land Mobile Network) is being accessed for communication.

The VPLMN of the communication system 1B includes UE 10B, (R) AN ((Radio) Access Network) 20B, AMF (Access and Mobility Management Function) 30B-1, SMF (Session Management function) 30B-2, NSSF (Network Slice Selection Function ) 30B-3, NEF (Network Exposure Function) 30B-4, NRF (Network Repository Function) 30B-5, PCF (Policy Control Function) 30B-8, NSACF (Network Slice Admission Control Function) 30B-10, SEPP (Security Edge Protection Proxy) 30B-12 and UPF (User Plane Function) 40B.

The HPLMN of the communication system 1B includes SMF30B-2, NSSF30B-3, NEF30B-4, NRF30B-5, UDM (Unified Data Management) 30B-6, AUSF (Authentication Server Function) 30B-7, PCF30B-8, AF (Application Function) 30B-9, NSACF 30B-10, NSSAAF (Network Slice Specific Authentication and Authorization Function) 30B-11, SEPP 30B-12, and UPF 40B.

The (R)AN 20B is a network node with radio access functionality, and may be, for example, a gNB (next generation Node B) (which may also be called a base station).

AMF30B-1 is a network node having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management.

SMF30B-2 is a network node 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.

NSSF 30B-3 selects the network slice to which the UE connects, determines the allowed NSSAI (Network Slice Selection Assistance Information), determines the NSSAI to be set, determines the AMF set to which the UE connects, etc. A network node with functions such as is.

The NEF 30B-4 is a network node that has the function of notifying other NFs of capabilities and events.

　NRF30B-5 is a network node that has the function of discovering NF instances that provide services.

The UDM 30B-6 is a network node that manages subscriber data and authentication data. The UDM 30B-6 is connected to a UDR (User Data Repository) holding the data.

　AUSF 30B-7 is a network node that authenticates the subscriber/UE 10B against the subscriber data held in the UDR.

PCF 30B-8 is a network node that has the function of performing network policy control.

AF30B-9 is a network node that has the function of controlling the application server.

NSACF 30B-10B is a network node that has the function of controlling network slice approval.

NSSAAF 30B-11 is a network node that has the function of controlling network slice authentication and authorization.

SEPP 30B-12 is a network node with a proxy that controls message filtering and policy restrictions in inter-operator control plane exchanges. The SEPP30B-12 on the VPLMN side is described as vSEPP30B-12v, and the SEPP30B-12 on the HPLMN side is described as hSEPP30B-12h. vSEPP 30B-12v and hSEPP 30B-12h provide functions related to security and integrity of messages (HTTP Request, HTTP Response, etc.) sent and received between VPLMN and HPLMN.

The UPF 40B is a network node that has functions such as a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling.

　N1, N2, N3, N4, and N9 are reference points between network nodes. Also, N32 between vSEPP30B-12v and hSEPP30B-12h is a reference point at the connection point between VPLMN and HPLMN.

(R) AN 20B is connected to UE 10B, AMF 30B-1 and UPF 40B.

In the VPLMN, AMF 30B-1, SMF 30B-2, NSSF 30B-3, NEF 30B-4, NRF 30B-5, PCF 30B-8, NSACF 30B-10 have respective service-based interfaces Namf, Nsmf, Nnssf, Nnef, Nnrf, Npcf, are connected to each other via Nsacf respectively.

In the HPLMN, SMF30B-2, NSSF30B-3, NEF30B-4, NRF30B-5, UDM30B-6, AUSF30B-7, PCF30B-8, AF30B-9, NSACF30B-10, NSSAAF30B-11 are interfaces based on each service. are interconnected via Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf, Nsacf, and Nnssaaf, respectively.

vSEPP30B-12v connects with VPLMN's AMF30B-1, SMF30B-2, NSSF30B-3, NEF30B-4, NRF30B-5, PCF30B-8 and NSACF30B-10, and connects with hSEPP30B-12h via N32.

hSEPP30B-12h connects with HPLMN SMF30B-2, NSSF30B-3, NEF30B-4, NRF30B-5, UDM30B-6, AUSF30B-7, PCF30B-8, AF30B-9, NSACF30B-10 and NSSAAF30B-11. , N32 to vSEPP30B-12v.

The UPF 40B on the VPLMN side interconnects with (R)AN 20B, SMF 30B-2 and UPF 40B on the HPLMN side. UPF 40B of HPLMN interconnects with SMF 30B-2 and DN (Data Network) 50B.

(CAPIF architecture)
The NEF 30A-4 (30B-4) described above is under consideration to implement an API that can be called from the AF 30A-9 (30B-9) by applying the CAPIF architecture. The CAPIF architecture provides a mechanism to support service API operation, for example, allows an API invoker to discover a service API provided by an API provider and use the service API. enable communication. The CAPIF architecture also has mechanisms to hide the topology of the PLMN trust domain, eg, from API callers accessing the service API from outside the PLMN trust domain.

Next, the CAPIF architecture will be explained using FIG. As shown in FIG. 3, CAPIF is composed of API invoker 101, CCF 102, and APD 103. The API invoker 101 is an API caller application, and the CCF 102 and APD 103 are network nodes.

The APD 103 has each function (network node) of AEF 103-1, APF (API publishing function) 103-2, and AMF (API management function) 103-3. The APD 103 uses the AEF 103-1 to authenticate/authorize the access of the API invoker 101. Also, the APD 103 publishes the Service API on the CCF 102 using the APF 103-2. The APD 103 also uses the AMF 103-3 to audit logs of API calls received from the CCF 102 and to monitor the status of Service APIs.

A CAPIF can contain multiple API invokers 101. FIG. 3 shows an example in which the CAPIF includes two API invokers 101, API invoker 101A and API invoker 101B. For example, API invoker 101A is an application that performs high-speed, large-capacity communication to download a large amount of data in the background, and API invoker 101B is a low-delay application that allows you to play competitive games comfortably without time lag. It is an application that communicates. In the following, processing common to both the API invoker 101A and API invoker 101B will be simply described as processing of the API invoker 101. FIG.

(API invoker 101)
The API invoker 101 is connectable with the CCF 102 and the APD 103 and registered (onboarded) with the CCF 102 in advance. The API invoker 101 may be a third-party application, or may be an application operated by the same provider that provides the CCF 102 and APD 103 .

Also, a security method is agreed between the API invoker 101 and the CCF 102. For this security method, for example, the Client Credential method specified in OAuth 2.0 is used. In this method, API calls are authorized only by client (API invoker) authentication.

If the API invoker 101 is authenticated and authorized by the CCF 102, it will be able to call the API, that is, access the AEF (API exposing function) 103-1 in the APD 103.

When the API invoker 101 accesses the AEF 103-1 (API call), the API invoker 103-1 permits or rejects the API call (hereinafter also referred to as "permission"). is notified. When the API call is rejected, the API invoker 101 is also notified of a value indicating the reason for the rejection (cause value).

If the API invoker 101 rejects the API call, the API invoker 101 may perform a predetermined operation such as calling the API again after a certain period of time. Also, the API invoker 101 may determine subsequent operations based on the cause value. For example, if the cause value indicates that changing the QoS for an existing communication is unacceptable, the API invoker 101 may establish a new communication flow with the desired QoS instead of making the API call. .

(CCF102)
The CCF 102 manages applications capable of calling APIs, and upon receiving an API call authorization request from the API invoker 101 , verifies the authorization request and authenticates/authorizes the API invoker 101 . The CCF 102 statically manages this authentication/authorization of the API invoker 101 mainly by the ID (identifier) of the API invoker 101 and authentication information.

In addition, the CCF 102 is set with the upper limit number of API invokers that can call APIs that affect the service quality of a specific UE, and the IDs of the API invokers that have called APIs for the UE are listed together with the registration time. It is saved (see FIG. 7). This list is hereinafter referred to as an "API invoker list".

The CCF 102 dynamically manages whether or not to call an API according to the API invoker list, and when it receives an inquiry about whether or not to call a new API from the AEF 103-1, it checks the API invoker list and decides whether to call the API. Judge whether or not it is possible.

Specifically, when the ID of the API invoker 101 that newly invoked the API (hereinafter referred to as the "target API invoker") is saved in the API invoker list, or when the ID of the target API invoker 101 is stored in the API invoker list , the number of API invokers does not reach the upper limit, the CCF 102 permits API calls from the target API invoker 101 . If the ID of the target API invoker 101 is not saved in the API invoker list, the CCF 102 adds the ID of the target API invoker 101 to the API invoker list.

On the other hand, if the ID of the target API invoker 101 is not saved in the API invoker list and the number of API invokers has reached the upper limit, the CCF 102 rejects API calls from the target API invoker 101.

The CCF 102 notifies the AEF 103-1 of the judgment result after judging whether or not the new API can be called.

(Processing of AEF103-1)
When the AEF 103-1 receives an API call from the API invoker 101, the AEF 103-1 notifies the CCF 102 of the called API and the UE whose service quality is affected by the API, and inquires whether the API can be called.

When the AEF 103-1 receives the judgment result about whether or not the API call is permitted from the CCF 102, it notifies the API invoker 101 of whether or not the API call is permitted. When API calls are permitted, the AEF 103-1 performs processing for API calls, such as notifying the Core Network of API contents such as QoS.

(first sequence of CAPIF)
Next, the first sequence of CAPIF, that is, the sequence until the API invoker 101 calls the API will be described with reference to FIG. It is assumed that the API invoker 101 has been registered (onboarded) in the CCF 102 in advance, and that a security method has been agreed between the API invoker 101 and the CCF 102 .

First, in S101, the API invoker 101 transmits an API call authorization request to the CCF 102. At that time, the API invoker 101 also transmits authentication information to the CCF 102 .

In S102, the CCF 102 verifies the authorization request from the API invoker 101 and performs authentication processing for the API invoker 101.

When the authentication process is completed, the CCF 102 transmits API call authorization information, specifically an access token, in S103.

In S104, the API invoker 101 uses the authorization information (access token) to call the API and access the AEF 103-1.

(second sequence of CAPIF)
Next, the second sequence of CAPIF, that is, the sequence after the API invoker 101 calls the API will be described with reference to FIGS. 5 and 6. FIG. In the CCF 102, an upper limit number of API invokers capable of invoking APIs that affect the service quality of a specific UE is set in advance, and the ID of the API invoker that has invoked the API for the UE is included in the API invoker list. saved in the format In FIGS. 5 and 6, it is assumed that the upper limit number of API invokers is set to one. 5 is in the state (initial state) of FIG. 7A, and the API invoker list at the start of the sequence in FIG. 6 is in the state of FIG. 7B.

FIG. 5 shows the sequence when the API invoker 101A, in the initial state (FIG. 7A), calls an API requesting QoS that realizes high-speed, large-capacity communication for downloading a large amount of data in the background.

In S201, the API invoker 101A calls the AEF 103-1 for an API requesting QoS that realizes high-speed, large-capacity communication.

In S202, the AEF 103-1 notifies the CCF 102 of the called API and the UE whose service quality is affected by the API, and inquires whether the API can be called.

In S203, the CCF 102 checks the API invoker list and determines whether the API can be called. In the case of FIG. 5, since the number of API invokers in the API invoker list shown in FIG. 7A has not reached the upper limit number "1", the CCF 102 permits calling of the API. The CCF 102 also stores the ID [apiinvoker_a] of the API invoker 101A together with the registration time in the API invoker list (see FIG. 7B).

In S204, the CCF 102 notifies the AEF 103-1 of the confirmation result of the API invoker list, that is, the determination result of permitting the API call.

In S205, the AEF 103-1 notifies the API invoker 101A of permission to call the API. In addition, the AEF 103-1 performs processing for API calls, such as notifying the Core Network of API contents such as QoS.

Through this series of processing, the API invoker 101A can perform high-speed, large-capacity communication in the background.

FIG. 6 shows the state after the API invoker 101A calls the API (FIG. 7B), which realizes low-latency communication for comfortable play without time lag in competitive games, etc. This is the sequence when calling an API requesting QoS.

In S301, the API invoker 101B calls the API requesting QoS that realizes low-delay communication to the AEF 103-1.

In S302, the AEF 103-1 notifies the CCF 102 of the called API and the UE whose service quality is affected by the API, and inquires whether the API can be called.

In S303, the CCF 102 checks the API invoker list and determines whether the API can be called. In the case of FIG. 6, the number of API invokers in the API invoker list shown in FIG. reject the call.

In S304, the CCF 102 notifies the AEF 103-1 of the result of checking the API invoker list, that is, the result of the decision to refuse to call the API.

In S305, the AEF 103-1 notifies the API invoker 101B of its refusal to call the API.

This series of processes maintains the QoS of high-speed, large-capacity communication on the Core Network communication path, so the API invoker 101A can continue high-speed, large-capacity communication in the background.

The CCF 102 starts a timer when the ID of the API invoker 101A is added to the API invoker list (registration time), and when the timer counts a predetermined time (for example, 30 minutes), the ID of the API invoker 101A is added to the API invoker list. You can remove it from the list. Also, the CCF 102 may delete the ID of the API invoker 101A from the API invoker list based on instructions from the API invoker 101A. In this case, the API invoker list reverts to the state of Figure 7A.

The API invoker 101B may start a timer when it receives a notification to the effect that the API call is to be rejected, and call the API again when the timer counts a predetermined time (for example, 30 minutes). At that time, if the ID of the API invoker 101A has been deleted from the API invoker list, the API call is permitted.

As a result, the API invoker 101B will be able to perform low-delay communication in the background.

<effect>
Thus, in the present embodiment, the upper limit of the number of API invokers capable of calling an API for a specific UE is preset in the CCF, and the CCF calls the API for the UE. Save the ID of the API invoker. Then, when a new API is called, the CCF detects that the ID of the API invoker that called the API is not saved and the number of API invokers has reached the upper limit. reject the call to

As a result, when the quality of service of the UE changes due to an API call such as QoS change, it is possible to prevent the later-called API from unintentionally changing the settings of the previously called API.

In the above, an example in which the CCF manages the upper limit number of API invokers that can call an API for a specific UE has been described, but the present disclosure is not limited to this, and the AEF manages the upper limit number. You may In this case, the AEF does not make an inquiry to the CCF, judges whether the API call is permitted or not, and notifies the API invoker that called the API of the judgment result.

In the above description, the CCF stores the IDs of the API invokers that have called the API in a list format. IDs of invokers may be managed in a format other than a list.

(Device configuration)
Next, functional configuration examples of the terminal 10, the base station 20, and the NEF 30A-4 (30B-4) that execute the processes and operations described above will be described. Terminal 10, base station 20 and NEF 30A-4 (30B-4) include the functionality described in the above example. However, the terminal 10, base station 20 and NEF 30A-4 (30B-4) may include only some of the functions described in the above examples.

<Terminal 10>
FIG. 8 is a diagram illustrating an example of a functional configuration of terminal 10 according to an embodiment of the present disclosure. As shown in FIG. 8, the terminal 10 includes a transmitting section 510, a receiving section 520, a setting section 530, and a control section 540. The functional configuration shown in FIG. 8 is merely an example. As long as the operation according to the embodiment of the present disclosure can be executed, the functional division and the name of the functional unit may be anything.

The transmission unit 510 generates a transmission signal from transmission data and wirelessly transmits the generated transmission signal. The receiving unit 520 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiving unit 520 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals, etc. transmitted from the base station 20 . Further, for example, the transmitting unit 510, as D2D communication, to the other terminal 10, PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel) etc., and the receiving unit 520 receives PSCCH, PSSCH, PSDCH, PSBCH, etc. from other terminals 10 .

The setting unit 530 stores various setting information received from the base station 20 by the receiving unit 520 in a storage device (storage unit), and reads the setting information from the storage device as necessary. The setting unit 530 also stores preset information that is set in advance in the storage device. The contents of the configuration information and the preconfiguration information may include, for example, information related to PDU sessions. Note that the setting unit 530 may be included in the control unit 540 .

The control unit 540 controls the terminal 10 as a whole. In particular, the control unit 540 performs control related to communication by a PDU session or the like, as described in the above examples. A functional unit related to signal transmission in control unit 540 may be included in transmitting unit 510 , and a functional unit related to signal reception in control unit 540 may be included in receiving unit 520 .

<Base station 20>
FIG. 9 is a diagram illustrating an example of a functional configuration of base station 20 according to an embodiment of the present disclosure. As shown in FIG. 9, the base station 20 includes a transmitting section 610, a receiving section 620, a setting section 630, and a control section 640. The functional configuration shown in FIG. 9 is merely an example. As long as the operation according to the embodiment of the present disclosure can be executed, the functional division and the name of the functional unit may be anything.

The transmission unit 610 includes a function of generating a signal to be transmitted to the terminal 10 and wirelessly transmitting the generated signal. The transmitter 610 also transmits inter-network node messages to other network nodes. Moreover, the transmission unit 610 transmits the user data transmitted from the terminal 10 to the DH 50 as necessary. The receiving unit 620 includes a function of receiving various signals transmitted from the terminal 10 and acquiring, for example, higher layer information from the received signals. Also, the transmitting unit 610 has a function of transmitting NRPSS, NR-SSS, NR-PBCH, DL/UL control signals, etc. to the terminal 10 . The receiver 620 also receives inter-network node messages from other network nodes.

The setting unit 630 stores preset information set in advance and various kinds of setting information to be transmitted to the terminal 10 in a storage device (storage unit), and reads preset information and setting information from the storage device as needed. . The contents of the preset information and the configuration information may include, for example, node connection information, information related to PDU sessions, and the like. Note that the setting unit 630 may be included in the control unit 640 .

The control unit 640 controls the base station 20 as a whole. In particular, as described in the above example, the control unit 640 controls communication by a PDU session or the like (in particular, transmission of user data transmitted from the terminal 10 to the DH 50 based on a notification from another network node). I do. Also, the control unit 640 controls communication with the terminal 10 based on the terminal capability report regarding the radio parameters received from the terminal 10 . A functional unit related to signal transmission in control unit 640 may be included in transmitting unit 610 , and a functional unit related to signal reception in control unit 640 may be included in receiving unit 620 .

<Configuration of NEF>
FIG. 10 is a diagram showing an example of a functional configuration of NEF 30A-4 (30B-4) according to an embodiment of the present disclosure. As shown in FIG. 10, the NEF 30A-4 (30B-4) comprises a transmitting section 710, a receiving section 720, a setting section 730, and a control section 740. The functional configuration shown in FIG. 10 is merely an example. As long as the operation according to the embodiment of the present disclosure can be executed, the functional division and the name of the functional unit may be anything.

The transmission unit 710 includes a function of generating a signal to be transmitted and transmitting the generated signal to the network. The receiving unit 720 includes a function of receiving various signals and acquiring, for example, higher layer information from the received signals.

The setting unit 730 stores preset information and setting information set in advance in a storage device (storage unit), and reads preset information and setting information from the storage device as needed. Note that the setting unit 730 may be included in the control unit 740 .

The control unit 740 controls the entire NEF 30A-4 (30B-4). A functional unit related to signal transmission in control unit 740 may be included in transmitting unit 710 , and a functional unit related to signal reception in control unit 740 may be included in receiving unit 720 .

(Hardware configuration)
It should be noted that the block diagrams used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a terminal, 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. 11 is a diagram illustrating an example of hardware configurations of a terminal, base station, data hub access support, and other network nodes according to an embodiment of the present disclosure; The terminal 10, base station 20 and NEF 30A-4 (30B-4) described above physically include a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. It may be configured as a computer device.

In the following explanation, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of the terminal 10, base station 20 and NEF 30A-4 (30B-4) may be configured to include one or more of each device shown in the figure, or may be configured to include some devices without may be configured.

Each function in terminal 10, base station 20 and NEF 30A-4 (30B-4) is performed by processor 1001 by loading predetermined software (program) onto hardware such as processor 1001 and memory 1002, It is realized by controlling communication by the communication device 1004 and controlling at least one of data reading and writing in the memory 1002 and the storage 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, the control unit 540 , the control unit 640 , the control unit 740 and the like described above may be realized by the processor 1001 .

Also, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them. 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 540 of the terminal 10, the control unit 640 of the base station 20, and the control unit 740 of the NEF 30A-4 (30B-4) are stored in the memory 1002 and may be implemented by a control program that runs on the processor 1001. , other functional blocks may be similarly implemented. Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

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

The storage 1003 is a computer-readable recording medium, for example, 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), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like. Storage 1003 may also be called an auxiliary storage device. The storage medium described above may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003 .

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, frequency division duplex (FDD) and time division duplex (TDD). may consist of For example, the transmitting unit 510 , the receiving unit 520 , the transmitting unit 610 , the receiving unit 620 , the transmitting unit 710 , the receiving unit 720 and the like described above may be implemented by the communication device 1004 .

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (eg, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Each device such as the processor 1001 and the memory 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 devices.

In addition, the terminal 10, the base station 20 and the NEF 30A-4 (30B-4) include a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA ( Field Programmable Gate Array) may be included, and 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 pieces of hardware.

An example configuration of the vehicle 2001 is shown in FIG. As shown in FIG. 12, a 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, and various sensors 2021-2029. , an information service unit 2012 and a communication module 2013 . Each aspect/embodiment described in the present disclosure may be applied to a communication device mounted on vehicle 2001, and may be applied to communication module 2013, for example.

The driving unit 2002 is configured by, for example, an engine, a motor, or a hybrid of the engine and the motor. The steering unit 2003 includes at least a steering wheel (also referred to as 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 , a memory (ROM, RAM) 2032 and a 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).

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

The information service unit 2012 includes various devices such as car navigation systems, audio systems, speakers, televisions, and radios for providing various types of information such as driving information, traffic information, and entertainment information, and one or more devices for controlling these devices. ECU. The information service unit 2012 uses information acquired from an external device via the communication module 2013 or the like to provide passengers of the vehicle 2001 with various multimedia information and multimedia services.

Driving support system unit 2030 includes millimeter wave radar, LiDAR (Light Detection and Ranging), camera, positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, automatic driving vehicle (AV) map, etc. ), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, AI processors, etc., to prevent accidents and reduce the driver's driving load. and one or more ECUs for controlling these devices. In addition, 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.

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

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 an external device via wireless communication. Communication module 2013 may be internal or external to 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 receives the rotation speed signal of the front and rear wheels obtained by the rotation speed sensor 2022, the air pressure signal of the front and rear wheels obtained by the air pressure sensor 2023, and the 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, and a shift lever. A shift lever operation signal obtained by the sensor 2027 and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028 are also transmitted to an external device via wireless communication.

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

(notification of information, signaling)
Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

(Applicable system)
Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other suitable systems and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

(Processing procedure, etc.)
The processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

(Base station operation)
Certain operations that are described in this disclosure as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes with a base station, various operations performed for communication with a terminal may be performed by the base station and other network nodes other than the base station (e.g. MME or S-GW, etc. (including but not limited to). Although the case where there is one network node other than the base station is exemplified above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).

(input/output direction)
Information and the like (*see the item “information, signal”) can be output from the upper layer (or lower layer) to the lower layer (or higher layer). It may be input and output via multiple network nodes.

(Handling of input/output information, etc.)
Input/output information and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

(Determination method)
The determination may be made by a value represented by one bit (0 or 1), by a true/false value (Boolean: true or false), or by numerical comparison (for example, a predetermined value).

(software)
Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

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

(information, signal)
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 refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

The 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, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

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

(parameter, channel name)
In addition, 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. may be represented. For example, radio resources may be indexed.

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

(Base station (wireless base station))
In the present disclosure, "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", ""accesspoint","transmissionpoint","receptionpoint","transmission/receptionpoint","cell","sector","cellgroup", Terms such as "carrier" and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: Communication services can also be provided by Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.

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

A mobile station is defined 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 It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

(base station/mobile station)
At least one of a base station and a mobile station may be called a transmitter, a receiver, a communication device, and the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, 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.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the terminal 10 may have the functions of the base station 20 described above. Also, 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 read as side channels.

Similarly, a terminal in the present disclosure may be read as a base station. In this case, the base station 20 may have the functions of the terminal 10 described above.

(Term meaning and interpretation)
As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Judgement", "determining" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as "judged" or "determined", and the like. Also, "judgment" and "decision" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that something has been "determined" or "decided". In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" may include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected," "coupled," or any variation thereof mean any direct or indirect connection or connection between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are defined using at least one of one or more wires, cables, and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

(reference signal)
The reference signal may be abbreviated as RS (Reference Signal), or may be referred to as Pilot according to the applicable standard.

(meaning "based on")
As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

("first", "second")
Any reference to elements using the "first,""second," etc. designations used in this disclosure 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, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

(means)
The "unit" in the configuration of each device described above may be replaced with "means", "circuit", "device", or the like.

(open format)
Where "include,""including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

(Time unit such as TTI, frequency unit such as RB, radio frame configuration)
A radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

A numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, transmission and reception specific filtering operations performed by the receiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, and/or the like.

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

A slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist 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. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.

For example, one subframe may be called a Transmission Time Interval (TTI), a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. may That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum scheduling time unit 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 user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

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

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 scheduling time unit. Also, the number of slots (the number of mini-slots) constituting 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, or the like. A TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve. The number of subcarriers included in an RB may be determined based on neumerology.

Also, the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long. One TTI, one subframe, etc. may each consist of one or more resource blocks.

One or more RBs are physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc. may be called.

Also, a resource block may be composed of one or more resource elements (RE: Resource Element). 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 bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a certain numerology in a certain carrier. good. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

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 "cell", "carrier", etc. in the present disclosure may be read as "BWP".

The structures such as radio frames, subframes, slots, minislots and symbols described above are only examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. can be varied.

In this disclosure, if articles are added by translation, such as a, an, and the in English, the 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." The term may also mean that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

(Variation of mode, etc.)
Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching according to execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

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 in the present disclosure. The present disclosure can be practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

One aspect of the present disclosure is useful for mobile communication systems.

10 UE (terminal)
20 gNB (base station)
30A-4, 30B-4 NEF (Network Exposure Function)
101 API invokers
102 CCF (CAPIF Core Function)
103 APDs (API provider domains)
103-1 AEF (API exposing function)
103-2 APF (API publishing function)
103-3 AMF (API management functions)
510, 610, 710 transmitter 520, 620, 720 receiver 530, 630, 730 setter 540, 640, 740 controller

Claims (5)

1. a control unit that determines whether to permit or reject a new API call based on the upper limit of the number of applications that can call an API (Application Programming Interface) and the registered applications;
   a transmitting unit that notifies permission or refusal of calling the API;
   A network node comprising:
2. The control unit permits the API call when the application that has called the new API is already registered, or when the number of registered applications does not reach the upper limit. ,
   A network node according to claim 1.
3. The control unit rejects the API call when the application that has called the new API is not registered and the number of registered applications has reached the upper limit.
   3. A network node according to claim 1 or 2.
4. The control unit stores identifiers of applications that have called the API within a predetermined period of time in the past in a list, and based on the list, determines whether the application that has called the new API has already been registered. , and determining whether the number of registered applications has reached the upper limit;
   A network node according to any one of claims 1 to 3.
5. network node
   Based on the upper limit number of applications that can call APIs (Application Programming Interface) and registered applications, determine whether to permit or reject new API calls,
   Notifying the permission or refusal of calling the new API;
   Communication method.

Images