Network node and control method

Abstract

This network node comprises: a transmission unit that transmits a first message requesting information relating to quality of service; a reception unit that receives the information relating to the quality of service requested by the first message; and a control unit that associates and stores the information relating to the quality of service and an access token corresponding to the information relating to the quality of service. The control unit acquires the information relating to the quality of service associated with the access token when a notification related to the access token has been received, the transmission unit transmits a second message requesting restoration of the quality of service associated with the access token, and the reception unit receives a response to the second message.

Description

Network node and control method

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

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

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

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

[0005] 3GPP TS 23.501 V18.1.0 (2023-03) 3GPP TS 29.522 V17.8.0 (2022-12) 3GPP TS 23.222 V18.0.0 (2022-12) 3GPP TS 23.502 V18.0.0 (2022-12)

[0006] The 3GPP core network exposes APIs (Application Program Interfaces) to external applications, allowing third-party applications to call the APIs. Furthermore, CAPIF is being considered to allow resource owners to authorize API calls to the core network. Resource owners register in advance with an API exposing function or an authorization function, and can access the resource holder from the API exposing function or authorization function whenever necessary to inquire about the availability of API calls.

[0007] For example, an API invoker can request an API provider to change the Quality of Service (QoS) using an access token indicating that the QoS upgrade is permitted. After the QoS has been upgraded, if the resource holder wishes to revoke the QoS upgrade permission, the access token becomes invalid, and the API invoker will no longer be able to change the QoS. Furthermore, the resource holder will not be able to change the QoS even if the access token is invalidated.

[0008] The present invention has been made in view of the above points, and has as its object to restore a changed resource when a resource holder revokes authorization for a resource change.

[0009] According to the disclosed technology, a network node is provided that has: a transmitter that transmits a first message requesting information on quality of service; a receiver that receives the information on the quality of service requested by the first message; and a controller that associates the information on the quality of service with an access token corresponding to the information on the quality of service and stores the associated information on the quality of service in a quality of service list, wherein, upon receiving a notification on the access token, the controller obtains the information on the quality of service associated with the access token from the quality of service list; the transmitter transmits a second message requesting restoration of the quality of service associated with the access token; and the receiver receives a response to the second message.

[0010] According to the disclosed technology, when a resource holder revokes authorization for a resource change, the changed resource can be restored.

[0011] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram for explaining an example of an API call. FIG. 3 is a diagram for explaining example (1) of a QoS change. FIG. 4 is a diagram for explaining example (2) of a QoS change. FIG. 5 is a diagram for explaining an example of a QoS change in an embodiment of the present invention. A sequence diagram for explaining an example of saving QoS information in an embodiment of the present invention. A diagram for explaining an example of a QoS information list in an embodiment of the present invention. A sequence diagram for explaining an example of QoS restoration in an embodiment of the present invention. A diagram for explaining an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. A diagram for explaining an example of the functional configuration of a terminal 20 in an embodiment of the present invention. A diagram for explaining an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention. A diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

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

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

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

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

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

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

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

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

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

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

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

[0024] In the 3GPP core network, an API (Application Program Interface) is open to external applications, and the API can be called from a third-party application.

[0025] FIG. 3 is a diagram illustrating an example of an API call. As shown in FIG. 3, an authorization function 30E in a CAPIF core function 30A receives application pre-registration sent from an API invoker 20A and authenticates and authorizes third-party applications. An API exposing function 30B receives core network API calls sent from the API invoker and opens the API to authenticated and authorized external applications. Note that the authorization function 30E may be external to the CAPIF core function 30A.

[0026] A resource owner client 20B can authorize an API call made by the core network via a CAPIF core function 30A and an authorization function 30E. In addition, an API providing function 30B can access the authorization function 30E to check whether an API call is permitted.

[0027] The API caller 20A may be, for example, an application on a terminal or on a network node such as an application server, and may have the ability to support authentication by providing an identifier for the API caller, the ability to support mutual authentication with the CAPIF core function 30A, the ability to obtain authentication when accessing a service API, the ability to discover information related to the service API, and the ability to call the service API.

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

[0029] The API providing function 30B is a provider that provides a service API, and may have the ability to authenticate the API caller 20A based on information provided from the CAPIF core function 30A, the ability to verify the authentication provided from the CAPIF core function 30A, and the ability to record logs of service API calls in the CAPIF core function 30A.

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

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

[0032] The API providing function 30B, the API publishing function 30C, and the API management function 30D may be functions or nodes belonging to a single API provider. Alternatively, the CAPIF core function 30A, the API providing function 30B, the API publishing function 30C, and the API management function 30D may each be configured as a network node 30. For example, the API providing function 30B, the API publishing function 30C, and the API management function 30D may be configured as a single network node 30. The API caller 20A, the resource holder client 20B, and the authorization function 30E may be, for example, a communication device such as a terminal or a server, or may be another communication device. CAPIF can also be extended to allow the resource holder client 20B to authorize an API call from the core network using Resource Owner-Aware Northbound API Access (RNAA).

[0033] 4 is a diagram illustrating an example (1) of a QoS change. As shown in FIG. 4, first, a resource owner client 20B permits a QoS (Quality of Service) upgrade. Next, an API invoker 20A requests an API exposing function 30B to change the QoS using an access token indicating that the QoS upgrade is permitted.

[0034] FIG. 5 is a diagram illustrating an example (2) of a QoS change. As shown in FIG. 5, after the QoS has been upgraded, if the resource owner client 20B wishes to stop the QoS upgrade, it can revoke permission for the upgrade. At this time, the access token indicating permission for the upgrade becomes invalid, and the API caller 20A can no longer change the QoS. Furthermore, although the resource owner client 20B can invalidate the access token, it cannot change the QoS (return the upgraded QoS to its previous state).

[0035] Example 1 Example 1 will be described as an embodiment of the present invention. In Example 1, an operation of restoring a changed resource (e.g., QoS) when a resource holder revokes authorization for a resource change (e.g., QoS upgrade permission) will be described. Here, QoS may also be referred to as quality of service or quality of service. FIG. 6 is a diagram for explaining an example of QoS change in an embodiment of the present invention. As shown in FIG. 6, a resource owner client 20B requests a CAPIF core function 30A to revoke a token. The CAPIF core function 30A notifies an API exposing function 30B that the token has expired. The API exposing function 30B restores the changed QoS to the QoS before the API was applied by transmitting information about the QoS corresponding to the expired token, which was stored before the API was applied, to a network node 30F in the 3GPP core network. Here, the network node 30F may be, for example, a PCF (Policy Control Function).

[0036] Next, the details of the operation in the first embodiment will be described. First, the operation of saving information about quality of service (QoS) will be described. Fig. 7 is a sequence diagram for explaining an example of saving QoS information in an embodiment of the present invention. The processing of each step in Fig. 7 will be described below.

[0037] Step S301: The resource owner client 20B permits the API invoker 20A to update (upgrade) the quality of service (QoS). The API invoker 20A requests the CAPIF core function 30A to authenticate and authorize the application related to the service, as well as an access token. The authorization function 30E in the CAPIF core function 30A performs application authentication and authorization in response to the request.

[0038] Step S302: The API caller 20A sends a message requesting the call of the service API to the API providing function 30B. The message includes the access token acquired in step S301 and information about the quality of service (QoS) to be updated (upgraded).

[0039] Step S303: In response to the request message received in step S302, the API providing function 30B transmits a message requesting acquisition of information about the current quality of service (QoS) to the network node 30F in the 3GPP core network.

[0040] Step S304: In response to the request message received in step S303, the network node 30F transmits information about the current quality of service (QoS) to the API providing function 30B. Here, the network node 30F is, for example, a PCF (Policy Control Function). The information about the quality of service (QoS) may also include, for example, a quality of service identifier (for example, 5QI (5G QoS Identifier), see Non-Patent Document 1).

[0041] Step S305: The API providing function 30B stores information about the current quality of service (QoS) received in step S304 and the access token corresponding to the quality of service information in a QoS information list. FIG. 8 is a diagram illustrating an example of a QoS information list according to an embodiment of the present invention. As shown in FIG. 8, the QoS information list includes information about the access token and information about the QoS. The information about the access token includes a value such as a number or identifier for identifying the access token (e.g., #aaa), or a value obtained by hashing the access token value. The QoS information includes, for example, information about normal quality of service (Normal QoS information) required for QoS reconfiguration, such as the UE (IP or MAC) address, the application session context identifier, and QoS information (see Section 5.2.5.3.2 of Non-Patent Document 4). Returning to FIG. 7, the following explanation will be given.

[0042] Step S306: In response to the request message received in step S302, the API providing function 30B sends a message to the network node 30F requesting a QoS update. The message includes information identifying the user or terminal and information about the quality of service (QoS) to be updated (upgraded). The information about the quality of service (QoS) may include a quality of service identifier (such as 5QI). The information identifying the user is, for example, a Subscription Permanent Identifier (SUPI). The information identifying the terminal is, for example, the IP address or MAC address of the terminal.

[0043] Step S307: The network node 30F executes a QoS update process in response to the request message received in step S306.

[0044] Step S308: The network node 30F transmits a response to the request message received in step S306 to the API providing function 30B.

[0045] Step S309: The API providing function 30B sends a token event subscription request to the CAPIF core function 30A to receive notifications of events related to the access token received in step S302.

[0046] Step S310: The CAPIF core function 30A transmits a response to the request received in step S309 to the API providing function 30B.

[0047] Next, the operation of restoring QoS will be described. Fig. 9 is a sequence diagram for explaining an example of restoring QoS in an embodiment of the present invention. The processing of each step in Fig. 9 will be described below.

[0048] Step S401: The resource holder client 20B sends a message to the CAPIF core function 30A requesting cancellation of the access token acquired in step S301 of FIG.

[0049] Step S402: The CAPIF core function 30A cancels the token in response to the received request.

[0050] Step S403: The CAPIF core function 30A sends to the API providing function 30B a token event notification indicating that the access token acquired in step S301 of Fig. 7 has been revoked and has expired. The notification includes information about the expired access token.

[0051] Step S404: The API providing function 30B detects the need to restore QoS by confirming that the information regarding the access token contained in the notification received in step S403 is included in the QoS information list saved in step S305 of Figure 7.

[0052] Step S405: The API providing function 30B checks the QoS information list for information on the QoS corresponding to the access token included in the notification received in step S403 (information on normal QoS).

[0053] Step S406: The API providing function 30B sends a request message to the network node 30F to restore the upgraded QoS to the normal QoS. The message includes information for identifying the user or terminal and information about the normal QoS (Normal QoS information).

[0054] Step S407: In response to the request message received in step S406, the network node 30F executes a restoration process to restore the updated (upgraded) QoS to the normal QoS.

[0055] Step S408: The network node 30F transmits a response to the request message received in step S406 to the API providing function 30B. The response may include information indicating that the QoS restoration process was successful.

[0056] Step S409: The API providing function 30B sends a response corresponding to the notification received in step S403 to the CAPIF core function 30A. The response may include information indicating that the requested token has been successfully revoked and information indicating that the QoS restoration process has been successful.

[0057] Step S410: The CAPIF core function 30A sends a response to the request received in step S401 to the resource holder client 20B. The response may include information indicating that the requested token has been successfully revoked and information indicating that the QoS restoration process has been successful.

[0058] (Modification) A modification will be described as an embodiment of the present invention. In this modification, instead of using the information on the quality of service stored in the QoS information list shown in FIG. 8 in the first embodiment, information on a predetermined quality of service is used. That is, as shown in step S302 of FIG. 7, the API providing function 30B receives an access token and a message requesting updating of the quality of service corresponding to the access token. Furthermore, as shown in step S403 of FIG. 8, after receiving a notification regarding the expiration of the access token, the API providing function 30B transmits a message to the network node 30F requesting restoration of the quality of service (QoS) associated with the access token to a predetermined quality of service (QoS). The message may include information indicating updating to the predetermined quality of service, or updating to the predetermined quality of service may be preset or may be defined by a standard.

[0059] According to the above-described embodiment, when a user (resource holder) revokes authorization for a resource change (e.g., QoS upgrade permission), it is possible to restore the changed resource (e.g., QoS). That is, when a resource holder revokes authorization for a resource change, it is possible to restore the changed resource. Furthermore, even if a user (resource holder) revokes authorization and invalidates a token, the original resource state can be restored without relying on a third-party API invoker. This makes it possible to prevent a high-quality QoS from being set against the user's intention after the user (resource holder) invalidates a token. That is, it is possible to prevent unintended high usage fees from being charged due to the use of a high-quality service.

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

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

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

[0063] The setting unit 130 stores in a storage device preset setting information and various setting information to be transmitted to the terminal 20, and reads out the setting information from the storage device as needed. The content of the setting information is, for example, information related to service APIs in the network.

[0064] As described in the embodiment, the control unit 140 performs processing related to setting of a service API in the network. The control unit 140 also performs processing related to communication with the terminal 20. 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.

[0065] <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 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 11 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, a communication device that becomes a resource holder 20 may have the same functional configuration as the terminal 20.

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

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

[0068] As described in the embodiment, the control unit 240 performs processing related to setting of a service API in a network. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] Fig. 13 shows an example configuration of a 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, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

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

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

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

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

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

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

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

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

[0092] (Summary of embodiment) As described above, according to an embodiment of the present invention, there is provided a network node having: a transmitter that transmits a first message requesting information on quality of service; a receiver that receives the information on the quality of service requested by the first message; and a controller that associates the information on the quality of service with an access token corresponding to the information on the quality of service and stores the information on the quality of service in a quality of service list, wherein, upon receiving a notification on the access token, the controller obtains the information on the quality of service associated with the access token from the quality of service list, the transmitter transmits a second message requesting restoration of the quality of service associated with the access token, and the receiver receives a response to the second message.

[0093] With the above configuration, when the resource holder revokes authorization for resource modification, the modified resource can be restored.

[0094] The service quality list may include at least one of an IP address of a terminal, a MAC address of a terminal, an application session context identifier, and a service quality identifier as information related to the service quality. With this configuration, when a resource holder revokes authorization for a resource change, the changed resource can be restored.

[0095] The notification may be a notification regarding the expiration of the access token. This configuration allows the modified resource to be restored when a resource holder revokes authorization for modifying the resource.

[0096] The transmitting unit may transmit a response to the notification indicating that the quality of service corresponding to the access token has been successfully restored. With this configuration, when a resource holder revokes authorization for a resource change, the changed resource can be restored.

[0097] According to an embodiment of the present invention, there is also provided a network node having: a receiving unit that receives an access token and a first message requesting an update of the quality of service corresponding to the access token; and a sending unit that, upon receiving a notification related to the access token, sends a second message requesting that the quality of service associated with the access token be restored to a predetermined quality of service.

[0098] With the above configuration, when the resource holder revokes authorization for resource modification, the modified resource can be restored.

[0099] The notification may be a notification regarding the expiration of the access token. This configuration allows the modified resource to be restored when a resource holder revokes authorization for modifying the resource.

[0100] The transmitting unit may transmit a response to the notification indicating that the quality of service corresponding to the access token has been successfully restored. With this configuration, when a resource holder revokes authorization for a resource change, the changed resource can be restored.

[0101] Further, according to an embodiment of the present invention, there is provided a control method executed by a network node, the control method comprising: a sending step of sending a first message requesting information on quality of service; a receiving step of receiving information on the quality of service requested by the first message; and a control step of associating the information on the quality of service with an access token corresponding to the information on the quality of service and storing the information on the quality of service in a quality of service list, wherein the control step, upon receiving a notification on the access token, obtains information on the quality of service associated with the access token from the quality of service list; the sending step sends a second message requesting restoration of the quality of service associated with the access token; and the receiving step receives a response to the second message.

[0102] With the above configuration, when the resource holder revokes authorization for resource modification, the modified resource can be restored.

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

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

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

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

[0107] In this specification, a specific operation described as being 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 having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0108] For example, the authorization function may be combined with a network node having a function other than authorization (for example, an edge application server or an edge enabler server having an edge computing function).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0124] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0138] REFERENCE SIGNS LIST 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Controller 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Controller 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A network node having: a transmitting unit that transmits a first message requesting information on quality of service; a receiving unit that receives the information on the quality of service requested by the first message; and a control unit that associates the information on the quality of service with an access token corresponding to the information on the quality of service and stores them in a quality of service list, wherein when the control unit receives a notification regarding the access token, it obtains the information on the quality of service associated with the access token from the quality of service list; the transmitting unit transmits a second message requesting restoration of the quality of service associated with the access token; and the receiving unit receives a response to the second message.

2. The network node according to claim 1, wherein the service quality list includes at least one of a terminal's IP address, a terminal's MAC address, an application session context identifier, and a service quality identifier as information relating to the service quality.

3. A network node having: a receiving unit that receives an access token and a first message requesting an update of the quality of service corresponding to the access token; and a transmitting unit that, upon receiving a notification regarding the access token, transmits a second message requesting that the quality of service associated with the access token be restored to a predetermined quality of service.

4. A network node as described in claim 1 or claim 3, wherein the notification is a notification regarding the expiration of the access token.

5. A network node as described in claim 1 or claim 3, wherein the transmission unit transmits a response to the notification indicating that the restoration of the quality of service corresponding to the access token has been successful.

6. A control method executed by a network node, comprising: a sending step of sending a first message requesting information on service quality; a receiving step of receiving information on the service quality requested by the first message; and a control step of associating the information on the service quality with an access token corresponding to the information on the service quality and storing them in a service quality list, wherein the control step obtains information on the service quality associated with the access token from the service quality list upon receiving a notification regarding the access token; the sending step sends a second message requesting restoration of the service quality associated with the access token; and the receiving step receives a response to the second message.

Images