Apparatus, method and computer program

CN118945662APending Publication Date: 2024-11-12NOKIA TECHNOLOGIES OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410573170.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-10
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

During the service access authorization process of existing communication systems, the reuse of access tokens is limited, resulting in increased signaling, waste of resources, and the inability to effectively manage access permissions for multiple service scopes.

Method used

Introduce a new header 3gpp-Sbi-Additional-Access-Scopes, allowing service consumers to specify additional ranges when requesting access tokens. SCP can cache and reuse access tokens, reduce requests to authorized servers, and optimize access. Use of tokens.

Benefits of technology

By caching and reusing access tokens, the number of signaling is reduced, system efficiency is improved, resource consumption is reduced, and flexible permission management is achieved for multiple service scopes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945662A_ABST
    Figure CN118945662A_ABST
Patent Text Reader

Abstract

A method, apparatus and computer program are provided for causing a first network device to perform: signaling a request for an access token for a network function consumer to a second network device for authorizing the network function service consumer to access a first service from a network function service producer; receiving an access token from the second network device, wherein the received access token comprises: an indication of at least one second access permission that is not associated with accessing the first service; and causing the received access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Examples described herein relate generally to apparatus, methods and computer programs, and more particularly (but not exclusively) to apparatus, methods and computer programs for apparatus. Background Art

[0002] A communication system may be viewed as a facility that enables communication sessions between two or more entities (such as communication devices, base stations, and / or other nodes) by providing carrier waves between the various entities involved in the communication path.

[0003] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards such as those provided by 3GPP, satellite-based communication systems, and different wireless local networks such as wireless local area networks (WLANs). Wireless systems can typically be divided into cells and are therefore often referred to as cellular systems.

[0004] The communication system and associated equipment operate according to a given standard or set of specifications that specifies what the various entities associated with the system are allowed to do and how it will be achieved. The communication protocols and / or parameters that will be used for the connection are also typically defined. An example of a standard is the so-called 5G standard. Summary of the invention

[0005] According to a first aspect, a first network device is provided, the first network device comprising: a component for signaling a request for an access token of a network function consumer to a second network device for authorizing the network function service consumer to access a first service from a network function service producer; a component for receiving an access token from the second network device, wherein the received access token comprises: an indication of at least one second access right not associated with accessing the first service; and a component for causing the received access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0006] The first network device may further include means for receiving a service request for the first service from a network function service consumer prior to said signaling a request for an access token.

[0007] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0008] The first network device may further include: means for signaling a discovery request for discovering a network function service producer to the second network device; and means for receiving an indication of the network function service producer prior to said signaling a request for an access token.

[0009] The component for signaling a request for an access token may include: a component for signaling a request including at least one of the following items: an indication that at least one first access permission associated with access to a first service is being requested, an indication that at least one second access permission not associated with access to the first service is being requested, or an indication that all access permissions provided by a network function service producer are being requested.

[0010] The first network device may also include means for providing the received access token to the network function service consumer, the access token including an indication of at least one second access right not associated with accessing the first service.

[0011] The first network device may also include: a component for causing the received access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a second service to the network function service consumer, wherein the second service is associated with at least one of the at least one second access rights.

[0012] A component for causing a received access token to be provided to a network function service producer when the network function service producer is signaled with a request to provide a second service to a network function service consumer may include: a component for signaling the received access token to the network function service producer, and a request to provide a second service to the network function service consumer.

[0013] The first network device may further include means for receiving a request for a second service from the network function service consumer, the request for the second service including the received access token.

[0014] The first network device may also include means for determining not to request a new access token dependent on determining that the received access token authorizes access to the at least one second access right.

[0015] The first network device may also include: a component for determining that the first service is associated with a predetermined set of access permissions; a component for determining that the received access token granted by the second network device omits at least one access permission in the predetermined set of access permissions; and a component for retaining the received access token and / or providing the received access token to the network function service consumer without requesting the network function service producer to provide the first service to the network function service consumer.

[0016] A component for causing a received access token to be provided to a network function service producer when the network function service producer is signaled with a request to provide a service to a network function service consumer may include: a component for signaling the received access token to the network function service producer, and a request to provide a first service to the network function service consumer.

[0017] The components for causing the received access token to be provided to the network function service producer may include: components for determining that the first service is associated with a predetermined set of access permissions; components for determining that the received access token includes all access permissions in the predetermined set of access permissions; and components for providing the received access token to the network function service producer to request the first service.

[0018] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0019] According to a second aspect, a second network device is provided, the second network device comprising: a component for receiving a request for an access token for a network function consumer from a first network device, for authorizing the network function service consumer to access a first service from a network function service producer; a component for generating an access token, wherein the access token comprises: an indication of at least one second access right not associated with accessing the first service; and a component for signaling the generated access token to the first network device.

[0020] The second network device may also include: a component for receiving an indication of at least one of the following items from the network function service producer: at least one first access permission associated with accessing the first service, or at least one second access permission; and a component for storing the at least one first access permission and / or the at least one second access permission in a network configuration file of the network function service producer.

[0021] The means for generating may include means for obtaining an indication of at least one first access right and / or at least one second access right from a network configuration file of a network function service producer.

[0022] The request may include at least one of: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0023] The components for generating an access token may include: a component for determining that a first service is associated with a predetermined set of access permissions; a component for determining that the generated access token will omit at least one access permission in the predetermined set of access permissions; and a component for generating the generated access token to omit at least one access permission in the predetermined set of access permissions.

[0024] The components for generating an access token may include: a component for determining that the first service is associated with a predetermined set of access permissions; a component for determining that the access token being generated will include all access permissions in the predetermined set of access permissions; and a component for generating the generated access token to include all access permissions in the predetermined set of access permissions.

[0025] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0026] According to a third aspect, there is provided an apparatus for a network function service consumer, the apparatus comprising: a component for signaling a service request for accessing a first service from a network function service producer to a first network device; a component for receiving an access token from the first network device, wherein the access token comprises: an indication of at least one second access right not associated with accessing the first service; and a component for causing the access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0027] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0028] The apparatus may further include means for causing the received access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a second service to the network function service consumer, wherein the second service is associated with at least one of the at least one second access rights.

[0029] A component for causing a received access token to be provided to a network function service producer when the network function service producer is signaled with a request to provide a second service to a network function service consumer may include: a component for signaling the received access token to the network function service producer, and a request to provide a second service to the network function service consumer.

[0030] The apparatus may also include means for signaling a request for a second service to the first network device, the request for the second service including the access token.

[0031] Components for causing an access token to be provided to a network function service producer may include: components for determining that a second service is associated with a second predetermined set of access permissions; components for determining that the access token includes all access permissions in the predetermined set of access permissions; and components for providing the access token to the first network device when a request for access to the second service is signaled.

[0032] The apparatus may further include means for determining that the first service is associated with a first predetermined set of access rights; means for determining that the access token omits at least one access right in the first predetermined set of access rights; and means for retaining the access token.

[0033] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0034] According to a fourth aspect, a first network device is provided, which includes: at least one processor; and at least one memory, including code, which, when executed by the at least one processor, causes the first network device to execute: signaling a request for an access token of a network function consumer to a second network device for authorizing the network function service consumer to access a first service from a network function service producer; receiving an access token from the second network device, wherein the received access token includes: an indication of at least one second access right that is not associated with accessing the first service; and causing the received access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0035] The first network device may also be caused to perform: prior to said signaling a request for an access token, receiving a service request for the first service from a network function service consumer.

[0036] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0037] The first network device may also be caused to perform: signaling a discovery request for discovering a network function service producer to the second network device; and receiving an indication of the network function service producer before said signaling a request for an access token.

[0038] The signaling of a request for an access token may include signaling a request including at least one of: an indication that at least one first access permission associated with accessing a first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by a network function service producer are being requested.

[0039] The first network device may also be caused to perform: providing the received access token to the network function service consumer, the access token including: an indication of at least one second access right not associated with accessing the first service.

[0040] The first network device may also be caused to perform: when the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer, wherein the second service is associated with at least one of the at least one second access rights.

[0041] When the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer may include: signaling the received access token and the request to provide the second service to the network function service consumer to the network function service producer.

[0042] The first network device may also be caused to perform: receiving a request for a second service from the network function service consumer, the request for the second service including the received access token.

[0043] The first network device may also be caused to perform: determining not to request a new access token dependent on determining that the received access token authorizes access to the at least one second access right.

[0044] The first network device may also be caused to perform: determining that the first service is associated with a predetermined set of access permissions; determining that the received access token granted by the second network device omits at least one access permission in the predetermined set of access permissions; and retaining the received access token and / or providing the received access token to the network function service consumer without requesting the network function service producer to provide the first service to the network function service consumer.

[0045] Causing the received access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a service to a network function service consumer may include: signaling the received access token and the request to provide a first service to the network function service consumer to the network function service producer.

[0046] The method of causing the received access token to be provided to the network function service producer may include: determining that the first service is associated with a predetermined set of access permissions; determining that the received access token includes all access permissions in the predetermined set of access permissions; and providing the received access token to the network function service producer to request the first service.

[0047] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0048] According to a fifth aspect, a second network device is provided, comprising: at least one processor; and at least one memory, comprising code, which, when executed by the at least one processor, causes the second network device to perform: receiving a request for an access token of a network function consumer from a first network device for authorizing the network function service consumer to access a first service from a network function service producer; generating an access token, wherein the access token comprises: an indication of at least one second access right that is not associated with accessing the first service; and sending the generated access token to the first network device by signaling.

[0049] The second network device may also be caused to perform: receiving an indication of at least one of the items from the network function service producer: at least one first access right associated with accessing the first service, or at least one second access right; and storing the at least one first access right and / or the at least one second access right in a network configuration file of the network function service producer.

[0050] The generating may include: obtaining an indication of at least one first access right and / or at least one second access right from a network configuration file of the network function service producer.

[0051] The request may include at least one of: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0052] Generating an access token may include: determining that the first service is associated with a predetermined set of access permissions; determining that the generated access token will omit at least one access permission in the predetermined set of access permissions; and generating the generated access token to omit at least one access permission in the predetermined set of access permissions.

[0053] Generating the access token may include: determining that the first service is associated with a predetermined set of access rights; determining that the access token being generated will include all access rights in the predetermined set of access rights; and generating the generated access token to include all access rights in the predetermined set of access rights.

[0054] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0055] According to a sixth aspect, a device for a network function service consumer is provided, the device comprising: at least one processor; and at least one memory, comprising code, which, when executed by the at least one processor, causes the device to perform: signaling a service request for accessing a first service from a network function service producer to a first network device; receiving an access token from the first network device, wherein the access token comprises: an indication of at least one second access right that is not associated with accessing the first service; and causing the access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0056] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0057] The apparatus may also be caused to perform: when the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the access token to be provided to the network function service producer, wherein the second service is associated with at least one of the at least one second access rights.

[0058] Causing an access token to be provided to a network function service producer when the network function service producer is signaled with a request to provide a second service to a network function service consumer may include signaling the access token to the network function service producer and the request to provide the second service to the network function service consumer.

[0059] The apparatus may also be caused to perform signaling to the first network device a request for a second service, the request for the second service including the access token.

[0060] Causing an access token to be provided to a network function service producer may include: determining that a second service is associated with a second predetermined set of access permissions; determining that the access token includes all access permissions in the predetermined set of access permissions; and providing the access token to the first network device when a request for access to the second service is signaled.

[0061] The apparatus may also be caused to perform: determining that the first service is associated with a first predetermined set of access rights; determining that the access token omits at least one access right in the first predetermined set of access rights; and retaining the access token.

[0062] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0063] According to a seventh aspect, a method for a first network device is provided, the method comprising: signaling a request for an access token of a network function consumer to a second network device for authorizing the network function service consumer to access a first service from a network function service producer; receiving the access token from the second network device, wherein the received access token comprises: an indication of at least one second access right not associated with access to the first service; and causing the received access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0064] The method may further comprise, prior to said signalling a request for an access token, receiving a service request for a first service from a network function service consumer.

[0065] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0066] The method may further include: signaling a discovery request for discovering a network function service producer to the second network device; and receiving an indication of the network function service producer before signaling the request for the access token.

[0067] The signaling of a request for an access token may include signaling a request including at least one of: an indication that at least one first access permission associated with accessing a first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by a network function service producer are being requested.

[0068] The method may further include providing the received access token to the network function service consumer, the access token including an indication of at least one second access right not associated with accessing the first service.

[0069] The method may further include causing the received access token to be provided to the network function service producer when the network function service producer is signaled a request to provide a second service to the network function service consumer, wherein the second service is associated with at least one of the at least one second access rights.

[0070] When the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer may include: signaling the received access token and the request to provide the second service to the network function service consumer to the network function service producer.

[0071] The method may further include receiving, from the network function service consumer, a request for a second service, the request for the second service including the received access token.

[0072] The method may also include determining not to request a new access token dependent on determining that the received access token authorizes access to the at least one second access privilege.

[0073] The method may also include: determining that the first service is associated with a predetermined set of access permissions; determining that the received access token granted by the second network device omits at least one access permission in the predetermined set of access permissions; and retaining the received access token and / or providing the received access token to the network function service consumer without requesting the network function service producer to provide the first service to the network function service consumer.

[0074] Causing the received access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a service to a network function service consumer may include: signaling the received access token and the request to provide a first service to the network function service consumer to the network function service producer.

[0075] The method of causing the received access token to be provided to the network function service producer may include: determining that the first service is associated with a predetermined set of access permissions; determining that the received access token includes all access permissions in the predetermined set of access permissions; and providing the received access token to the network function service producer to request the first service.

[0076] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0077] According to an eighth aspect, a method for a second network device is provided, the method comprising: receiving a request for an access token for a network function consumer from a first network device for authorizing the network function service consumer to access a first service from a network function service producer; generating an access token, wherein the access token comprises: an indication of at least one second access right that is not associated with accessing the first service; and sending the generated access token to the first network device using a signal.

[0078] The method may also include: receiving an indication of at least one of the following items from a network function service producer: at least one first access permission associated with accessing a first service, or at least one second access permission; and storing at least one first access permission and / or at least one second access permission in a network configuration file of the network function service producer.

[0079] The generating may include: obtaining an indication of at least one first access right and / or at least one second access right from a network configuration file of the network function service producer.

[0080] The request may include at least one of: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0081] Generating an access token may include: determining that the first service is associated with a predetermined set of access permissions; determining that the generated access token will omit at least one access permission in the predetermined set of access permissions; and generating the generated access token to omit at least one access permission in the predetermined set of access permissions.

[0082] Generating the access token may include: determining that the first service is associated with a predetermined set of access rights; determining that the access token being generated will include all access rights in the predetermined set of access rights; and generating the generated access token to include all access rights in the predetermined set of access rights.

[0083] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0084] According to a ninth aspect, a method for a device for a network function service consumer is provided, the method comprising: signaling a service request for accessing a first service from a network function service producer to a first network device; receiving an access token from the first network device, wherein the access token comprises: an indication of at least one second access right that is not associated with accessing the first service; and causing the access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0085] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0086] The method may further include causing the access token to be provided to the network function service producer when the network function service producer is signaled a request to provide a second service to the network function service consumer, wherein the second service is associated with at least one of the at least one second access rights.

[0087] Causing an access token to be provided to a network function service producer when the network function service producer is signaled with a request to provide a second service to a network function service consumer may include signaling the access token to the network function service producer and the request to provide the second service to the network function service consumer.

[0088] The method may also include signaling a request for a second service to the first network device, the request for the second service including the access token.

[0089] Causing an access token to be provided to a network function service producer may include: determining that a second service is associated with a second predetermined set of access permissions; determining that the access token includes all access permissions in the predetermined set of access permissions; and providing the access token to the first network device when a request for access to the second service is signaled.

[0090] The method may also include determining that the first service is associated with a first predetermined set of access rights; determining that the access token omits at least one access right in the first predetermined set of access rights; and retaining the access token.

[0091] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0092] According to the tenth aspect, a first network device is provided, which includes: a signal sending circuit system for sending a request for an access token of a network function consumer to a second network device by signaling, so as to authorize the network function service consumer to access a first service from a network function service producer; an access circuit system for receiving an access token from the second network device, wherein the received access token includes an indication of at least one second access right that is not associated with accessing the first service; and a causing circuit system for causing the received access token to be provided to the network function service producer when the network function service producer is sent a request by signaling to provide a service to the network function service consumer.

[0093] The first network device may further include receiving circuitry for receiving a service request for the first service from a network function service consumer prior to said signaling a request for an access token.

[0094] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0095] The first network device may further include: a signaling circuit system for signaling a discovery request for discovering a network function service producer to the second network device; and a receiving circuit system for receiving an indication of the network function service producer before said signaling a request for an access token.

[0096] The signaling circuit system for signaling a request for an access token may include: a signaling circuit system for signaling a request including at least one of: an indication that at least one first access permission associated with access to a first service is being requested, an indication that at least one second access permission not associated with access to the first service is being requested, or an indication that all access permissions provided by a network function service producer are being requested.

[0097] The first network device may also include circuitry for providing the received access token to the network function service consumer, the access token including an indication of at least one second access right not associated with accessing the first service.

[0098] The first network device may also include a circuit system that causes the received access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a second service to the network function service consumer, wherein the second service is associated with at least one of the at least one second access rights.

[0099] A circuit system for causing a received access token to be provided to a network function service producer when the network function service producer is signaled to send a request for providing a second service to a network function service consumer may include: a circuit system for signaling the received access token to the network function service producer, and a signaling circuit system for signaling a request for providing a second service to the network function service consumer.

[0100] The first network device may further include receiving circuitry for receiving a request for a second service from the network function service consumer, the request for the second service including the received access token.

[0101] The first network device may also include determining circuitry for determining not to request a new access token dependent on determining that the received access token authorizes access to the at least one second access privilege.

[0102] The first network device may also include: a determination circuit system for determining that the first service is associated with a predetermined set of access permissions; a determination circuit system for determining that the received access token granted by the second network device omits at least one access permission in the predetermined set of access permissions; and a reservation circuit system for retaining the received access token and / or providing the received access token to the network function service consumer without requesting the network function service producer to provide the first service to the network function service consumer.

[0103] A circuit system for causing a received access token to be provided to a network function service producer when the network function service producer is signaled to send a request to provide a service to a network function service consumer may include: a circuit system for signaling the received access token to the network function service producer, and a circuit system for signaling a request to provide a first service to the network function service consumer.

[0104] The causing circuit system for causing the received access token to be provided to the network function service producer may include: a determining circuit system for determining that the first service is associated with a predetermined set of access permissions; a determining circuit system for determining that the received access token includes all access permissions in the predetermined set of access permissions; and a providing circuit system for providing the received access token to the network function service producer to request the first service.

[0105] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0106] According to the eleventh aspect, a second network device is provided, which includes: a receiving circuit system for receiving a request for an access token of a network function consumer from a first network device, so as to authorize the network function service consumer to access a first service from a network function service producer; a generating circuit system for generating an access token, wherein the access token includes: an indication of at least one second access right that is not associated with accessing the first service; and a signal sending circuit system for sending the generated access token to the first network device by signal.

[0107] The second network device may also include: a receiving circuit system for receiving an indication of at least one of the following items from a network function service producer: at least one first access permission associated with accessing the first service, or at least one second access permission; and a storage circuit system for storing at least one first access permission and / or at least one second access permission in a network configuration file of the network function service producer.

[0108] The generating circuitry for generating may include an acquiring circuitry for acquiring an indication of at least one first access right and / or at least one second access right from a network configuration file of a network function service producer.

[0109] The request may include at least one of: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0110] A generation circuit system for generating an access token may include: a determination circuit system for determining that a first service is associated with a predetermined set of access permissions; a determination circuit system for determining that the generated access token will omit at least one access permission in the predetermined set of access permissions; and a generation circuit system for generating the generated access token to omit at least one access permission in the predetermined set of access permissions.

[0111] A generation circuit system for generating an access token may include: a determination circuit system for determining that a first service is associated with a predetermined set of access permissions; a determination circuit system for determining that the access token being generated will include all access permissions in the predetermined set of access permissions; and a generation circuit system for generating the generated access token to include all access permissions in the predetermined set of access permissions.

[0112] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0113] According to the twelfth aspect, a device for a network function service consumer is provided, the device comprising: a signal sending circuit system for sending a service request for accessing a first service from a network function service producer by signal to a first network device; a receiving circuit system for receiving an access token from the first network device, wherein the access token comprises: an indication of at least one second access right not associated with accessing the first service; and a causing circuit system for causing the access token to be provided to the network function service producer when the network function service producer is sent a request for providing a service to the network function service consumer by signal.

[0114] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0115] The apparatus may further include causing circuitry to cause an access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a second service to the network function service consumer, wherein the second service is associated with at least one of the at least one second access rights.

[0116] A circuit system for causing an access token to be provided to a network function service producer when the network function service producer is signaled to provide a request for providing a second service to a network function service consumer may include: a circuit system for signaling an access token to the network function service producer, and a circuit system for signaling a request for providing a second service to the network function service consumer.

[0117] The apparatus may also include signaling circuitry for signaling a request for a second service to the first network device, the request for the second service including an access token.

[0118] A causing circuit system for causing an access token to be provided to a network function service producer may include: a determining circuit system for determining that a second service is associated with a second predetermined set of access permissions; a determining circuit system for determining that the access token includes all access permissions in the predetermined set of access permissions; and a providing circuit system for providing the access token to the first network device when a request for access to the second service is signaled.

[0119] The apparatus may further include a determination circuit system for determining that the first service is associated with a first predetermined set of access permissions; a determination circuit system for determining that the access token omits at least one access permission in the first predetermined set of access permissions; and a retention circuit system for retaining the access token.

[0120] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0121] According to the thirteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing a first network device to execute: signaling a request for an access token for a network function consumer to a second network device for authorizing the network function service consumer to access a first service from a network function service producer; receiving an access token from the second network device, wherein the received access token comprises an indication of at least one second access right that is not associated with access to the first service; and causing the received access token to be provided to the network function service producer when the network function service producer is signaled a request to provide a service to the network function service consumer.

[0122] The first network device may also be caused to perform: prior to said signaling a request for an access token, receiving a service request for the first service from a network function service consumer.

[0123] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0124] The first network device may also be caused to perform: signaling a discovery request for discovering a network function service producer to the second network device; and receiving an indication of the network function service producer before said signaling a request for an access token.

[0125] The signaling of a request for an access token may include signaling a request including at least one of: an indication that at least one first access permission associated with accessing a first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by a network function service producer are being requested.

[0126] The first network device may also be caused to perform: providing the received access token to the network function service consumer, the access token including: an indication of at least one second access right not associated with accessing the first service.

[0127] The first network device may also be caused to perform: when the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer, wherein the second service is associated with at least one of the at least one second access rights.

[0128] When the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer may include: signaling the received access token and the request to provide the second service to the network function service consumer to the network function service producer.

[0129] The first network device may also be caused to perform: receiving a request for a second service from the network function service consumer, the request for the second service including the received access token.

[0130] The first network device may also be caused to perform: determining not to request a new access token dependent on determining that the received access token authorizes access to the at least one second access right.

[0131] The first network device may also be caused to perform: determining that the first service is associated with a predetermined set of access permissions; determining that the received access token granted by the second network device omits at least one access permission in the predetermined set of access permissions; and retaining the received access token and / or providing the received access token to the network function service consumer without requesting the network function service producer to provide the first service to the network function service consumer.

[0132] Causing the received access token to be provided to the network function service producer when the network function service producer is signaled with a request to provide a service to a network function service consumer may include: signaling the received access token and the request to provide a first service to the network function service consumer to the network function service producer.

[0133] The method of causing the received access token to be provided to the network function service producer may include: determining that the first service is associated with a predetermined set of access permissions; determining that the received access token includes all access permissions in the predetermined set of access permissions; and providing the received access token to the network function service producer to request the first service.

[0134] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0135] According to a fourteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing a second network device to execute: receiving a request for an access token for a network function consumer from a first network device for authorizing the network function service consumer to access a first service from a network function service producer; generating an access token, wherein the access token comprises: an indication of at least one second access right that is not associated with accessing the first service; and sending the generated access token to the first network device using a signal.

[0136] The second network device may also be caused to perform: receiving an indication of at least one of the following items from a network function service producer: at least one first access permission, or at least one second access permission associated with accessing a first service; and storing at least one first access permission and / or at least one second access permission in a network configuration file of the network function service producer.

[0137] The generating may include: obtaining an indication of at least one first access right and / or at least one second access right from a network configuration file of the network function service producer.

[0138] The request may include at least one of: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0139] Generating an access token may include: determining that the first service is associated with a predetermined set of access permissions; determining that the generated access token will omit at least one access permission in the predetermined set of access permissions; and generating the generated access token to omit at least one access permission in the predetermined set of access permissions.

[0140] Generating the access token may include: determining that the first service is associated with a predetermined set of access rights; determining that the access token being generated will include all access rights in the predetermined set of access rights; and generating the generated access token to include all access rights in the predetermined set of access rights.

[0141] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0142] According to the fifteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions for causing a device for a network function service consumer to execute: signaling a service request for accessing a first service from a network function service producer to a first network device; receiving an access token from the first network device, wherein the access token comprises: an indication of at least one second access right that is not associated with accessing the first service; and causing the access token to be provided to the network function service producer when the network function service producer is signaled a request for providing a service to the network function service consumer.

[0143] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0144] The apparatus may also be caused to perform: when the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the access token to be provided to the network function service producer, wherein the second service is associated with at least one of the at least one second access rights.

[0145] Causing an access token to be provided to a network function service producer when the network function service producer is signaled with a request to provide a second service to a network function service consumer may include: signaling an access token to the network function service producer and for providing the second service to the network function service consumer.

[0146] The apparatus may also be caused to perform signaling a request for a second service to the first network device, the request for the second service including the access token.

[0147] Causing an access token to be provided to a network function service producer may include: determining that a second service is associated with a second predetermined set of access permissions; determining that the access token includes all access permissions in the predetermined set of access permissions; and providing the access token to the first network device when a request for access to the second service is signaled.

[0148] The apparatus may also be caused to perform: determining that the first service is associated with a first predetermined set of access rights; determining that the access token omits at least one access right in the first predetermined set of access rights; and retaining the access token.

[0149] The access rights for accessing a service may correspond to the scope of an authorized access token.

[0150] According to a sixteenth aspect, there is provided a computer program product stored on a medium, which can cause an apparatus to perform any of the methods described herein.

[0151] According to a seventeenth aspect, there is provided an electronic device which may comprise an apparatus as described herein.

[0152] According to an eighteenth aspect, there is provided a chipset which may include an apparatus as described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0153] Some examples will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0154] Figure 1A and Figure 1B A schematic representation of a 5G system is shown;

[0155] Figure 2 A schematic representation of a network device is shown;

[0156] Figure 3 A schematic representation of a user equipment is shown;

[0157] Figure 4a , Figure 4b and Figure 5 The signaling is shown;

[0158] Figures 6 to 9illustrates example signaling; and

[0159] Figures 10 to 12 Example operations that may be performed by the apparatus described herein are illustrated. DETAILED DESCRIPTION

[0160] The following describes operations that may be performed when obtaining an access token that may be used to allow a network function service consumer to receive services from a network function service producer.

[0161] Specifically, a mechanism is described below in which an access token for allowing a network function service consumer to receive such a service is associated with more access rights (also referred to herein as "scopes") than are required to receive the service. In other words, where a service is associated with multiple scopes that will be used to provide the service, the network function service consumer is provided with an access token that includes at least one additional scope that is not included in the multiple scopes.

[0162] The access token may subsequently be used to request other services for the network function service consumer, wherein the other services utilize at least one additional scope.

[0163] Since the access token may be reused for subsequent service requests associated with a different scope from the initial service request, the entire system may save signaling and processing resources since a new access token is neither requested nor obtained.

[0164] In the following description of examples, certain aspects are explained with reference to devices that are generally capable of communicating via wireless cellular systems, and mobile communication systems that serve such mobile communication devices. For the sake of brevity and clarity, these aspects are described below with reference to 5G wireless communication systems. However, it should be understood that such aspects are not limited to 5G wireless communication systems, and can, for example, be applied to other wireless communication systems (e.g., current 6G proposals, IEEE 802.11, etc.).

[0165] Before describing the examples in detail, refer to Figure 1A and Figure 1B Briefly explain some general principles of 5G wireless communication systems.

[0166] 3GPP standards define a service-based architecture in 5G, which is expected to be leveraged in 6G and beyond.

[0167] In a service-based architecture, a modular framework is used where common applications can be deployed using components from different sources and / or providers.

[0168] Figure 1AA schematic representation of a 5G system (5GS) 100 is shown. The 5GS may include a user equipment (UE) 102 (which may also be referred to as a communication device or terminal), a 5G access network (AN) (which may be a 5G radio access network (RAN), or any other type of 5G AN, such as a non-3GPP interworking function for non-trusted / trusted non-3GPP access (N3IWF) / a trusted non-3GPP gateway function for non-trusted / trusted non-3GPP access (TNGF) or a wired access gateway function for wired access (W-AGF)) 104, a 5G core (5GC) 106, one or more application functions (AF) 108, and one or more data networks (DN) 110.

[0169] A 5G RAN may include one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) unit functions. A RAN may include one or more access nodes.

[0170] 5GC 106 may include one or more access and mobility management functions (AMF) 112, one or more session management functions (SMF) 114, one or more authentication server functions (AUSF) 116, one or more unified data management 118, one or more user plane functions (UPF) 120, one or more unified data repository (UDR) functions 122, one or more network repository functions (NRF) 128, and / or one or more network open functions (NEF) 124. The role of NEF is to provide a secure opening of network services (e.g., voice, data connectivity, billing, subscriber data, etc.) to third parties. Although NRF 128 is not shown with its interface, it should be understood that this is for clarity and that NRF 128 may have multiple interfaces with other network functions.

[0171] 5GC 106 also includes a network data analysis function (NWDAF) 126. NWDAF is responsible for providing network analysis information based on requests from one or more network functions or devices within the network. Network functions can also subscribe to NWDAF 126 to receive information from it. Therefore, NWDAF 126 is also configured to receive and store network information from one or more network functions or devices within the network. Data collection by NWDAF 126 can be performed based on at least one subscription to events provided by at least one network function.

[0172] The network may also include a management data analysis service (MDAS) producer or an MDAS management service (MnS) producer. The MDAS MnS producer may provide data analysis in the management plane taking into account parameters including, for example, load level and / or resource utilization. For example, an MDAS MnS producer for a network function (NF) may collect load-related performance data of the NF, such as the resource usage status of the NF. Analysis of the collected data may provide a prediction of resource usage information in a predefined future time window. The analysis may also recommend appropriate actions, such as resource expansion, admission control, load balancing of traffic, and the like.

[0173] Figure 1B An alternative view of a 5GC is shown in FIG. It should be understood that the architecture is intended to illustrate potential components that may be included in a core network, and the principles currently described are not limited to a core network that includes only the described components.

[0174] Figure 1B A 5GC 106' is shown, which includes a UPF 120' connected to an SMF 114' via an N4 interface. The SMF 114' is connected to each of the UDM 122', NEF 124', NWDAF 126', AF 108', policy control function (PCF) 130', AMF 112', and charging function 132' via an interconnect medium that interconnects these network functions. The 5G core 106' also includes a network repository function (NRF) 133' and a network function 134' connected to the interconnect medium.

[0175] exist Figure 1A and Figure 1B In the example of , the control plane functions and common data repository of the 5G network are delivered via a collection of interconnected network functions with access to each other's services. For example, a service-based architecture may include network functions such as NEF, NRF, UDM, PCF and AMF, SMF, etc. These network functions may provide services to another entity as NF "instances".

[0176] A network function that requests a service from another network function is called a service consumer (eg, network function service consumer, NFc), and the other network function is called a service producer (eg, network function service producer, NFp).

[0177] NFc and NFp can communicate with each other directly and / or indirectly via a service communication proxy (SCP). Whether the NF uses direct communication or indirect communication via SCP is based on the configuration of the NF. Indirect communication can be performed with or without delegated discovery (these are referred to as Model D and Model C, respectively), where delegated discovery refers to the use of SCP to discover NFp.

[0178] The NRF may save a record of available NF instances and the services they support as (multiple) NF profiles. For example, a NFp may register its NF profile in the NRF. The NF profile may include NF level specific information, and a list of NF service instances supported by the NFp and their associated attributes.

[0179] Examples of information elements that may be included in an NF profile are described below with reference to Table 1. Some features of these information elements are described later in this specification, including "scope," which refers to a value indicating the degree of access (e.g., "scope") associated with a service. A service to be provided may be associated with one or more "scopes," which define the minimum access level required (e.g., requested) for the service to be provided.

[0180]

[0181]

[0182] Table 1 Information elements in the NF configuration file at NRF

[0183] The NRF may provide information from the NF profile to at least one NF instance via a subscription operation and / or via a discovery operation.

[0184] Under the subscription operation, other NF instances signal a subscription request to the NRF to subscribe to registration notifications at the NRF of NF instances that are notified of a predetermined type (subscribed according to the type included in the subscription request).

[0185] Under the discovery operation, the NRF receives a discovery request from a NF instance requesting information of NF instances of a predetermined type (predetermined according to the type included in the discovery request), and responds to the discovery request with detailed information on which NF instances support at least one service specified in the discovery request.

[0186] NFc and / or Service Communication Agent (SCP) can perform NF discovery process to NRF to discover NFp by using query parameters describing the services or attributes of the NFp they wish to discover. NRF returns NF profiles of candidate NFp matching the query parameters in the response. In Model D, the discovery and selection of NFp is delegated to SCP, while in Model C, NFc discovers and selects NFp.

[0187] In a network where Oauth2-based service access authorization is deployed, NFc or SCP may request an Oauth2 access token from an OAuth 2.0 Authorization Server (NRF), which grants NFc permission to invoke NFp services and / or specific service operations of NFp services. Then, NFc or SCP may include the Oauth2 access token in a service request sent to NFp. If the access token grants NFc the permission required to access the service, NFp may provide the requested service.

[0188] The above attributes of Table 1 may be used to determine whether a given resource and / or operation level scope will be granted to a NF service consumer requesting an Oauth2 access token with a specific scope.

[0189] For example, when the attribute "allowedOperationsPerNfInstanceOverrides" does not exist or is set to false, the NRF grants such a scope in the access token only if the scope exists in "allowedOperationsPerNfType" (specific NF type for NF service consumer) or "allowedOperationsPerNfInstance" (specific NF instance ID for NF service consumer).

[0190] When the attribute "allowedOperationsPerNfInstanceOverrides" exists and is set to true, the NRF shall grant such scope in the Access Token when the scope is included in the "allowedOperationsPerNfInstance" attribute of the NF Instance ID of the NF Service Consumer. When the attribute "allowedOperationPerNfInstanceOverrides" exists and is set to true, but the NF Instance ID of the NF Service Consumer is not included in the attribute "allowedOperationPerNfInstance", the NRF shall grant such scope when the scope is in the "allowedOperationsPerNfType" of the specific NF Type for the NF Service Consumer.

[0191] When the NF service instance only supports (or is configured to use only) service level scopes for all NF service consumers that are allowed to access the service, these attributes are not necessarily registered. When both attributes are not present, the NRF can only grant access tokens for service level scopes. When at least one of these information elements is present, these information elements will indicate all NF types or NF instances that are allowed to access the NF service instance, and all corresponding scopes (e.g., service level scopes and resource / operation specific scopes) that are allowed for each NF type or NF instance, for example, any NF type or NF instance not listed in these information elements is not allowed to access the NF service instance.

[0192] Figure 2 An example of a control device for a communication system is shown, which is coupled to and / or used to control a station of an access system, such as a RAN node, such as a base station, a gNB, a central unit of a cloud architecture or a node of a core network (such as an MME or S-GW), a scheduling entity (such as a spectrum management entity), or a server or host, such as a device hosting an NRF, NWDAF, AMF, SMF, UDM / UDR, etc. The control device may be integrated with a node or module of the core network or RAN, or external to it. In some examples, the base station includes a separate control device unit or module. In other examples, the control device may be another network element, such as a radio network controller or a spectrum controller. The control device 200 may be arranged to provide control of communications in a service area of ​​the system. The device 200 includes at least one memory 201, at least one data processing unit 202, 203, and an input / output interface 204. Via the interface, the control device may be coupled to a receiver and a transmitter of the device. The receiver and / or the transmitter may be implemented as a radio front end or a remote radio head. For example, the control device 200 or the processor 201 may be configured to execute appropriate software code to provide control functionality. References herein to "code" are understood to refer to software code and vice versa.

[0193] Stations accessing the system can be classified into two different types: distributed units (DU) and centralized units (CU).

[0194] The DU provides access node support for lower layers of the protocol stack (such as radio link control (RLC), medium access control (MAC), and / or physical layer protocol layers, as examples). Each DU can support one or more cells, and each cell can support one or more beams.

[0195] The CU can support multiple DUs and provide access node support for higher layers of the protocol stack within the access node (such as Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), and / or Radio Resource Control (RRC) protocol layers as examples). The interface between the CU and the DU is labeled as the F1 interface. There is a single CU per gNB, and CUs belonging to multiple gNBs can be implemented using a shared hardware platform.

[0196] Possible wireless communication devices will now refer to Figure 3 is described in more detail, Figure 3 A schematic partial cross-sectional view of a communication device 300 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. Suitable mobile communication devices can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or mobile device, such as a mobile phone or so-called "smart phone", a computer provided with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA), or a tablet computer provided with wireless communication capabilities, or any combination of these, etc. The mobile communication device can provide, for example, data communication for carrying communications (such as voice, e-mail (email), text messages, multimedia, etc.). Therefore, users can be supplied and provided with a variety of services via their communication devices. Non-limiting examples of these services include two-way or multi-way calls, data communications or multimedia services, or simply access to a data communication network system (such as the Internet). Users can also be provided with broadcast or multicast data. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms and other information.

[0197] A wireless communication device may be, for example, a mobile device (i.e., a device that is not fixed to a particular location), or it may be a fixed device. A wireless device may or may not require human interaction to communicate. As described herein, the term UE or "user" is used to refer to any type of wireless communication device.

[0198] The wireless device 300 may receive signals over the air or radio interface 307 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 3 In the wireless device, the transceiver arrangement is schematically designated by block 306. The transceiver arrangement 306 may be provided, for example, by a radio part and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the wireless device.

[0199] The wireless device is typically provided with at least one data processing entity 301, at least one memory 302 and other possible components 303 for use in software code and hardware assistance to perform the tasks it is designed to perform, including control of access and communication to access systems and other communication devices. Data processing, storage and other related control means may be provided in appropriate circuit boards and / or chipsets. This feature is represented by reference numeral 304. The user can control the operation of the wireless device through appropriate user access (such as a keypad 305, voice commands, touch screen or pad, combinations thereof, etc.). A display 308, speakers and microphones may also be provided. In addition, the wireless communication device may include appropriate connectors (wired or wireless) to other devices and / or for connecting external accessories (such as hands-free devices) to it.

[0200] 3GPP has released multiple versions (Rel) for defining operational communication protocols related to communication networks. Currently, goals and work related to Release 19 (Rel. 19) are being developed.

[0201] The following describes a scenario where the NF service consumer (NFc) delegates the discovery and selection of NF service producers to the service communication proxy (SCP). In this scenario, the SCP issues queries for service discovery and / or service subscription to the NRF on behalf of the NFc.

[0202] As mentioned above, for some service requests, some additional authorizations are used to check whether the NFc is allowed to actually request the service from the NF Service Producer (NFp).

[0203] 3GPP TS 33.500, clause 6.7.3 deals with authorization of NF service access. As discussed therein, two alternative authorization mechanisms are defined in 3GPP 33.501:

[0204] Static authorization, which is based on the local authorization policy of the NRF and NF Service Producer (see 3GPP TS 33.501, clause 13.3.0);

[0205] Token-based authorization, when the NRF acts as an authorization server and provides access (see 3GPP TS 33.501, clause 13.3.1).

[0206] The following focuses on the example of requesting an "access token" from an authorization server (e.g., NRF), which can be used to represent the access rights of NFc to receive services from NFp. Then, when requesting services from NFp, the access token is forwarded to NFp together with the service request. NFp will check the validity of the access token to determine whether to provide the requested service to NFc. As mentioned above, the access token can include an OAuth2 access token.

[0207] The requested (and received) access token may be stored by the NFc for inclusion in subsequent service requests signaled to at least one NFp. Then, if the same access token is used for some subsequent access request (e.g. because the same access rights will be used), no further contact with the authorization server will be performed and the signaling may be saved. On the other hand, it has also been specified in the standards that "scopes" may be provided for the authentication process, which scopes may be used to check whether the requested access can / will be granted within this specific scope. Currently, only a few of these "scopes" are defined. These are explained below.

[0208] As mentioned above, NFc and NFp can communicate directly or indirectly via SCP. These are described for 3GPP TS 23.501 and TS 23.502 (for indirect communication) and 3GPP TS 33.501 and TS 29.500 (for service access authorization). These are shown in the following figure.

[0209] FIG. 4A illustrates example signaling in which NFc obtains an access token before NF services are requested from NFp.

[0210] Figure 4A illustrates signaling that may be performed between a NFc 401' and an authorization server 402'. The authorization server may be, for example, an NRF.

[0211] During 4001', NFc 401' sends signaling to authorization server 402'. The signaling may include a request for an access token for at least one service. For example, the signaling may include at least one NF service name, at least one NF type, NF type of NFc 401' and / or client identifier. The signaling may include a Nnrf_AccessToken_GetRequest service operation.

[0212] 3GPP TS 33.501 further discusses this signaling of 4001'. The document also discloses that the NF service consumer 401' uses the Nnrf_AccessToken_Get request operation to request an access token from the NRF associated with the same management domain as the NF service consumer (e.g., the same Public Land Mobile Network (PLMN)). The message includes the NF instance Id of the (multiple) NF service consumer, the requested "scope" (which may include (multiple) expected NF service names and optional "additional scope" information (e.g., requested resources and requested actions on the resources (service operations)), the expected NF producer instance, and the NF type of the NF consumer. The service consumer may also include a list of slice identifiers (e.g., Network Slice Selection Assistance Information (NSSAI) and / or a list of Network Slice Instance (NSI) identifiers for the expected NF producer instance). The message of 4001' may also include the NF set ID of the desired NF service producer instance.

[0213] As specified in 3GPP TS29.500, the requested access scope may correspond to an access scope level for accessing a given resource. The access scope may be based on the local configuration of the NF service producer (e.g., at least one of the following: the service name of the NF service (the scope associated therewith may grant generic access to a given application program interface (API), for resource operations that do not require specific authorization, or both), the service name of the NF service and a string that uniquely represents the type of operation (e.g., create / modify / read), resource, and service (these two scopes together may grant access to those operations of the resource using specific authorization).

[0214] TS 29.500 also defines the information elements included in the access token request in clause 6.3.5.2.2. Table 2 (below) reproduces at least some of these definitions.

[0215]

[0216] Table 2 Information elements included in the access header

[0217] During 4002', the authorization server 402' authorizes the NFc 401' and generates an access token for representing and / or determining at least one access right of the NFc.

[0218] During 4003', the authorization server 402' sends signaling to the NFc 401'. The signaling may include the access token generated during 4002'. The signaling may include an indication of when the access token included in the signaling will expire (e.g., become no longer valid). The signaling may include an Nnrf_AccessToken_GetResponse service operation.

[0219] FIG. 4B shows example signaling in which NFc uses the access token obtained during FIG. 4A to request NF services from NFp.

[0220] FIG. 4B shows signaling that may be performed between NFc 401″ and NFp 402″.

[0221] During 4001', NFc 401' sends signaling to NFp 402'. The signaling may include the access token received during 4003'. The signaling may include a NF service request (eg, a request for NFc 401' to be provided with NF services from NFp 402').

[0222] During 4002", the NFp 402" verifies the integrity of the access token and assertions in the access token. When successfully verified, the NFp 402" determines to perform the service requested during 4001".

[0223] During 4003", NFp 402" sends signaling to NFc 401". The signaling may include a response to the 4001" signaling. When the verification of 4002" is successful, the signaling may indicate that NFc 401" has been granted the requested service. When the verification of 4002" is unsuccessful, the signaling may indicate that NFc 401" has not yet been granted the requested service.

[0224] When indirect communication with delegated discovery is used, NFc delegates the discovery and selection of NFp to SCP. SCP may also be responsible for requesting an access token on behalf of NFc from an OAuth2 authorization server (this type of authorization is used).

[0225] As specified in clause 13.4.1 of 3GPP TS 33.501, OAuth 2.0 (see IETF RFC 6749) can be used for authorization of NF service access. All NFs and NRFs can support the OAuth 2.0 authorization framework with the "Client Credentials" grant type as specified in clause 4.4 of IETF RFC 6749, but without the "Authorization" HTTP request header in the access token request.

[0226] The NRF can act as an authorization server, providing a "bearer" access token (IETF RFC 6750) to the NF service consumer to access the services provided by the NF service provider.

[0227] When an NF service (e.g., an API) receives an OAuth 2.0 access token in the "Authorization" Hypertext Transfer Protocol (HTTP) request header field, the NF service can verify the access token, its expiration time, and its access scope before allowing access to the requested resource, as specified in IETF RFC 6749 Clause 7.

[0228] The access scope used to access a given resource may be based on the local configuration of the NF service producer, such as at least one of the following:

[0229] The service name of the NF service; for those operations on resources that do not require specific authorization, this scope grants generic access to the given API, or

[0230] The service name of the NF service and the type of operation that uniquely represents it (e.g. create / modify /

[0231] read), resource, and service; these two scopes together grant access to operations on resources that require specific authorization.

[0232] The NF service consumer may include any specific discovery and selection parameters to be satisfied by the NFp to allow the SCP to find a suitable producer that satisfies these discovery and selection parameters in its service request to the SCP. The SCP may use the request address in the request message, as well as the discovery and selection parameters, to route the service request to the selected producer instance. In addition, the NFc may provide a header in the service request sent to the SCP, which includes (multiple) access scopes to be used to authorize the service request. For example, the header may be a 3gpp-Sbi-Access-Scope header. For example, the header may be a header including a value corresponding to the service level scope (of the 5GC API / service of the service request), and if any additional scope API is defined for the specific resource / operation of the service request in the corresponding 5GC API, a header also including a value of the resource / operation level scope. This enables the SCP to know for which scopes the SCP will request access tokens from the NRF (assuming that no access tokens matching these scopes are available). The SCP may return the obtained access token to the NFc in the service response for possible reuse of the access token in subsequent service requests.

[0233] The current form of the access scope described in 3GPP TS29.500 is provided below. However, it should be understood that the form of the access scope may change as the standard develops, and the access scope of NFc can generally be understood as including parameters indicating the scope (or degree) of the access authority of NFc.

[0234] 3GPP TS29.500 clause 5.2.3.2.16 defines the header "3gpp-Sbi-Access-Scope", which is used in service requests for indirect communication to indicate the access scope of the service request for NF service access authorization (further reference clauses 6.7.3 and 6.10.11). Currently, the encoding of this header follows the Augmented Backus-Naur Form (ABNF) defined in IETF RFC 7230.

[0235] The header may include a Scope-Token, which is defined as:

[0236] Scope-Token=1*NQCHAR

[0237] The Scope-Token may include a list of space-delimited, case-sensitive strings containing the NF Service Name of the NF Service Producer corresponding to the service request, and additional resource / operation level scopes if defined for the specific resource / operation in the corresponding API.

[0238] NQCHAR is defined in Annex A (A.4) of IETF RFC 6749. NQCHAR corresponds to the "scope" syntax defined for OAuth in clauses 3.3 and A.4 of IETF RFC 6749, and also corresponds to the syntax of the "scope" parameter in AccessTokenReq in 3GPP TS29.510. The use of NQCHAR enables the SCP to set the scope parameter in the Nnrf_GetAccessToken request to the value of the 3gpp-Sbi-Access-Scope header received in the incoming Service Request, or to a list of scopes that is the intersection of the scopes indicated in the 3gpp-Sbi-Access-Scope header and the scopes expected by the NF Service Producer (as registered in the NF Profile of the NFp of the NRF).

[0239] For indirect communication with delegated discovery (see clause TS 33.50, clause 6.10.11.2), the NF Service Consumer does not know and does not need to know whether the NF Service Producer is configured to require resource / operation level scopes for the specific resource / operation for which the API defines resource / operation level scopes. The setting of the 3gpp-Sbi-Access-Scope header can be the same regardless of whether the NF Service Producer is configured to require resource / operation level scopes.

[0240] 3GPP TS 33.500, clause 6.10.11.2 describes authorization for indirect communication using delegated discovery. According to this clause, when the NF service consumer is configured to use delegated service discovery, the requirements in clause 13.4.1.3.2 of 3GPP TS 33.501 apply with the following additions.

[0241] When the NF service consumer receives an access token in a previous service response that is valid for a new service request, the NF service consumer may include the access token in the authorization header in the service request. The access token received in the previous service response is valid for the new service request if:

[0242] The access token has matching scopes, or the access token has only matching service-level scopes (e.g., the new service request also uses resource / operation-level scopes that were not present in the scope of the access token received in the previous service response);

[0243] The access token has a matching audience (e.g., matching producer’s NF type or NF instance ID);

[0244] the access token has matching producer NF set ID, S-NSSAI, NSI and PLMN identifiers when the access token includes the producer NF set ID, S-NSSAI, NSI and PLMN ID respectively; and

[0245] The access token has not expired.

[0246] When a NF Service Consumer has multiple cached access tokens valid for a service request, it is left to the implementation to select the access token to be included in the request. An access token with a matching scope (if any) will be used in preference to an access token with only a matching service level scope.

[0247] Including an access token with only a matching service level scope but not a matching resource / operation level scope enables reuse of the access token when the NF service producer is not configured to require the resource / operation level scope.

[0248] When the NF Service Consumer does not include an access token in the service request, or when an access token is included but the access token only has a matching service level scope and no matching resource / operation level scope, or when an access token is included but the access token is NF instance specific and reselection of a different producer instance may be applied at the SCP (e.g., the Route Binding header or the Discovery header provides the NF Set ID of the producer), the NF Service Consumer may include in the service request:

[0249] NF service discovery factors used by SCP for service access authorization process, such as 3GPP TS

[0250] 33.500, § 6.10.3.2; and

[0251] The 3gpp-Sbi-Access-Scope header indicates the access scope of the service request for access authorization, as defined in the corresponding API for a specific resource / operation (see 3GPP TS

[0252] 33.500, clause 5.2.3.2.16).

[0253] The NF Service Consumer may also include its Client Credentials Assertion in the Service Request as described in 3GPP TS 33.500 clause 6.7.5.

[0254] The SCP may use the access scope information received in the 3gpp-Sbi-Access-Scope header to determine the access scope required for access authorization for the incoming service request. The SCP may also make this determination using the scopes used by the NF Service Producer (as registered in the NF Profile of the NFp of the NRF), and if a new access token is required, request an access token from the NRF for a list of scopes that is the intersection of the scopes indicated in the 3gpp-Sbi-Access-Scope header and the scopes desired by the NF Service Producer.

[0255] When the NF Service Consumer has included an access token in a service request without a 3gpp-Sbi-Access-Scope header, or when the SCP has a cached granted access token that matches the service request, the SCP may reuse the available access token. When the NF Service Consumer includes an access token in a service request and a 3gpp-Sbi-Access-Scope header, the 3gpp-Sbi-Access-Scope header includes multiple scopes, and the access token has matching scopes for only a subset of the scopes present in the 3gpp-Sbi-Access-Scope header, the SCP shall consider the access token to have valid scopes for the service request if the NF Service Producer has not used any scopes that are not granted in the access token (as determined by its NF profile); otherwise, the SCP may request a new access token for the service request.

[0256] When the 3gpp-Sbi-Access-Scope header includes both service level scope and resource / operation level scope, this process may enable the SCP to consider that the access token has a valid scope, the access token has a scope that matches only the service level scope, and the NF service producer is not configured to require resource / operation specific scopes.

[0257] When the NRF receives a request to obtain an access token for a list of scopes, but the NF Service Producer's profile does not allow granting of tokens for all requested scopes, the NRF may grant an access token, but limited to the allowed scopes, unless the request cannot be authorized for other reasons. This process may enable the NRF to grant an access token for a service level scope in response to an access token request for a list of scopes that includes both a service level scope and a resource / operation level scope, when the NF Service Producer's profile is not configured to require resource / operation level scopes.

[0258] When the SCP requests an access token for a service request, the SCP may include the access token obtained from the NRF in the service response forwarded to the NF service consumer by including a 3gpp-Sbi-Access-Token header for possible reuse by the NF service consumer in subsequent service requests. The NF service consumer stores the access token received in the service response and uses it in subsequent service requests in a similar manner as described above.

[0259] Indirect communication with SCP targets Figure 5 is shown, Figure 5 The signaling described in 3GPP TS 33.501 is shown. The process may involve authorization and service invocation procedures for indirect communication with delegated discovery.

[0260] Figure 5 Signaling that may be performed between NFc 501, SCP 502, NRF 503, and NFp 504 is shown.

[0261] During 5001, NFc 501 sends signaling to SCP 502. The signaling may include a service request. The service request may include a Client Credential Assertion (CAA) of NFc 501 (as defined in clause 13.3.8 of TS 33.501). If the NF Service Consumer has received an access token in the service request, it may include the access token in the service request. If the previously received access token has expired, the NF Service Consumer may include discovery parameters in the service request to enable SCP to discover NFp (e.g., as specified in clause 5.2.3.2.7 of TS29.500). If a CCA is included, the NF Type of the intended audience in the CCA may include parameters and / or values ​​specifying "NRF" and "NF Service Producer".

[0262] 5002 to 5005 involve SCP 502 performing a discovery process to identify NFp 504 as an NF instance that can provide the service requested in the service request of 5001 to NFc 501, and to obtain an access token for indicating whether NFc 501 is allowed to access the NFp. It should be understood that these steps do not necessarily have to be performed. For example, when the NF service consumer has included an access token in the signaling of 5001, and / or when SCP 502 has a cached granted access token that can be used for NFc 501, then SCP 502 can reuse any of these access tokens and continue to 5006 instead of performing 5002 to 5005.

[0263] During 5002, SCP 502 exchanges signaling with NRF 503. The signaling may involve service discovery for discovering at least one NFp that can provide the requested service during 5001.

[0264] During 5003, SCP 502 sends signaling to NRF 503. The signaling may include a request for an access token. For example, SCP 502 may send an access token request (Nnrf_AccessToken_Get request) to NRF during 5003. The access token request may include parameters as defined in clause 13.4.1.1 of 3GPP TS 33.501. When the signaling of 5003 is received during 5001, the signaling of 5003 may include the CCA of NFc.

[0265] During 5004, the NRF 503 authenticates the NFc 501. The authentication may be performed, for example, using one of the methods described in TS 33.501 clause 13.3.1.2. For example, when CCA is provided during 5003, the authentication / verification may be performed using CCA. When the NFc authentication succeeds and the NFc is authorized based on the NRF policy, the NRF issues an access token. For example, the access token may be issued as described in 3GPP TS 33.501 clause 13.4.1.1. The NRF may use the NF service consumer instance identifier as the subject of the access token.

[0266] During 5005, the NRF 503 sends signaling to the SCP 502. The signaling may include the access token generated during 5004. The signaling may include an access token response (e.g., a Nnrf_AccessToken_Get response signaling operation).

[0267] During 5006, the SCP sends signaling to the NFp 504. The signaling may include a service request. The service request may include an access token (e.g., the access token received during 5001 and / or during 5005). When a CCA is received during 5001, the service request may include a CCA of the NFc.

[0268] During 5007, NFp 504 may authenticate NFc 501. This may be performed in any of a number of different ways (e.g., by at least one of the methods described in 3GPP TS 33.501 clause 13.3.2.2). When NFc 501 is successfully authenticated by NFp 504, NFp 504 verifies the access token received during 5006. This may be performed in any of a number of different ways (e.g., by at least one of the methods described in 3GPP TS 33.501 clause 13.4.1.1). When the verification of the access token is successful, NFp 504 proceeds to 5008.

[0269] During 5008, NFp 504 sends signaling to SCP 502. The signaling may include a service response. The signaling may be a response to 5006 signaling.

[0270] During 5009, SCP 502 sends signaling to NFc 501. The signaling may forward the service response received during 5008 to NFc 501. SCP may include an access token in the service response to NFc for possible reuse in subsequent service requests.

[0271] With delegated discovery, the task of SCP is to request access tokens on behalf of NFc. In other words, since SCP receives 3gpp-Access-Scope from NFc, SCP only knows which scopes are needed to serve the service. Therefore, SCP only requests these scopes received in 3gpp-Access-Scope from NRF. If any of these requested scopes are not granted, SCP rejects the service request.

[0272] The Global System for Mobile Communications Association (GSMA) has recently called for the introduction of many new types of the above-mentioned "scopes" for the authentication process in order to organize the authentication process with a higher granularity.

[0273] Relatedly, in 3GPP, contributions have just been approved to add many of these newly defined "scopes". For example, based on a GSMA request, 3GPP is defining finer-grained OAuth2 scopes in 3GPP Rel-18 to strengthen the security of 5GC, such as by defining additional resource and / or operation level scopes. According to recent submissions, it is up to the operator to decide whether to use OAuth2, and if so, which scopes to use.

[0274] As another example, more than 30 new additional scopes have been proposed to enable operators to provide fine-grained authorization to access specific resources / operations of the Unified Data Management Subscriber Data Management (UDM SDM) API (additional functionality of the UDM SDM API is provided in 3GPP TS 29.503).

[0275] The existing service access authorization process defined for indirect communication with delegated discovery does not allow requesting and obtaining an access token with additional resource / operation level scopes in addition to the specific resource / operation level scope of the service request. More specifically, the 3gpp-Sbi-Access-Scope header may include the scopes that will be used to authorize a specific service request (e.g., a service level scope, and if the 5GC API defines a resource / operation specific scope for the service operation called in the service request, the resource / operation specific scope). For example, as described above, the SCP may use the access scope information received in the 3gpp-Sbi-Access-Scope header to determine the access scope required for access authorization for an incoming service request.

[0276] When the SCP cannot obtain an access token with all scopes indicated in the 3gpp-Sbi-Access-Scope header, the SCP denies the service request.

[0277] Therefore, the access token obtained by the SCP and passed back in the service response to the NFc can only be reused for subsequent service requests that do not require a different resource / operation level scope than that of the initial service request that requested the access token. This causes a lot of signaling from the SCP to the NRF to obtain new access tokens for service requests that require different scopes of the same API.

[0278] In other words, the requested (and received) access tokens will only be valid for further requests with these "scopes". This means that storing the token for further service requests will no longer work most of the time, since the "scopes" may be different (although the "actual core of the request" remains the same). This will cause an increase in signaling, since currently the SCP will more often need to request a new access token, where a previously received access token could simply be reused.

[0279] To address at least one of the above issues, the following proposes to extend the delegated discovery process so that the SCP can be enabled to request (and then forward to the NFc) access tokens not only for the "scope" specified in the service request from the NFc, but also for other additional "scopes".

[0280] Furthermore, NFc may use a newly designated header (labeled herein as "3gpp-Sbi-Additional-Access-Scopes" header) to directly indicate in the service request to SCP that, in addition to the actual "scope" used for the current service request, NFc is interested in obtaining access tokens for scopes for future potential service requests.

[0281] An option is also introduced to add new "wildcard scope" information to the service request to request (and receive) at least one access token for all "scopes". A "wildcard scope" request may include a request to receive all possible scopes provided by NFp that NFc allows (e.g., that NFc is allowed to provide).

[0282] For example, in indirect communication with delegated discovery, after receiving an incoming service request at the SCP, when no access token is available to enable authorization of the service request at the NFp, the SCP may request an access token for the NFc from the NRF. The request may request multiple scopes, including scope(s) specifically for authorization of the incoming service request, and additional scopes not related to authorization of the incoming service request (e.g., which may be useful for authorization of subsequent service requests issued by the NFc). The SCP, when forwarding a service response to the NFc, may cache and / or return the access token obtained from the NRF to the NFc. The NFc may cache at least one access token received in the service response. The NFc and / or the SCP may reuse the cached access token(s) to authorize subsequent service requests associated with at least one of the additional scope(s) granted in the access token.

[0283] Although the previous paragraph relates to an example where the NRF grants at least one access token associated with a scope specified in an access token request, it should be understood that this is not limiting. For example, the NRF may be configured to grant in the access token all scopes as registered in the NFp profile that the NFp allows the NFc to register in the NFp profile, regardless of the scope requested to be granted in the access token request.

[0284] When receiving the access token response with access token from NRF, SCP checks whether the access token grants all scopes to be used to authorize the incoming service request. When the access token grants all scopes to be used, SCP forwards the service request with the access token obtained from NRF to NFc.

[0285] Failure to obtain an access token for additional scopes that are not used to authorize a service request will not cause the SCP to reject the request. On the contrary, if the access token is granted for all scopes used by the service request, the SCP can continue to submit service requests to the NFp using the obtained access token.

[0286] Otherwise, when the NRF does not authorize all scopes required for the service request but authorizes at least one additional scope indicated in 3gpp-Sbi-Additional-Access-Scopes, the SCP may reject the service request to the NFc but still include the access token obtained from the NRF in the service rejection response to the NFc to enable the NFc to cache the actually granted access token.

[0287] The SCP may determine the list of scopes required to authorize the incoming service request as at least one of the scopes received in the 3gpp-Sbi-Access-Scope header in the service request received from NFc, or the intersection of the scopes received in the 3gpp-Sbi-Access-Scope header in the service request received from NFc and the scopes allowed by NFc (as registered in the NFp profile discovered by the SCP from the NRF).

[0288] The SCP may determine the additional scopes not to be used for authorizing incoming service requests as at least one of the following: the scope(s) received in the new 3gpp-Sbi-Additional-Access-Scopes header in the received service request, the scope(s) to which the NFp allows the NFc to access (as registered in the NFp document discovered by the SCP from the NRF), in addition to the scopes listed in the 3gpp-Sbi-Access-Scope header, or any intersection of the above lists.

[0289] The SCP may be configured by the operator to request from the NRF at least one access token with new "wildcard scope" information indicating a request for all possible scopes supported by the NFp.

[0290] In order to enable at least one of the above features to be implemented, a new 3GPP custom HTTP header (referred to herein as "3gpp-Sbi-Additional-Access-Scopes") is provided. This new header enables the NFc to indicate in its service request to the SCP the additional access scopes that are expected to be obtained using the access tokens in addition to the scopes indicated in the 3gpp-Sbi-Access-Scope when requesting access tokens from the NRF, but these access tokens are not used for the service request itself.

[0291] New "Wildcard Scope" information is also defined, which may be provided in any of the following items: "Access Token Request", "Access Token Response", "Access Token", and / or "3gpp-Sbi-Additional-Access-Scopes". This may be defined as a new information element in the Access Token Request, or as a new wildcard scope for each 5GC API that grants authorization for all service operations for the access API. The latter scope may be labeled "<Service Name>-Wildcard", where <Service Name> represents the associated 5GC API for the scope.

[0292] The semantics and processing of the existing 3gpp-Sbi-Access-Scope and the new 3gpp-Sbi-Additional-Access-Scopes headers by SCP may be different. In other words, 3gpp-Sbi-Additional-Access-Scopes may not only be an extension of the existing 3gpp-Sbi-Access-Scope header.

[0293] To illustrate the above features, several examples are provided below showing example signaling between the entities described herein. It should be understood that unless otherwise mentioned, the same references as in FIGS. Figure 5 Features of these examples labeled in the same manner include similar features.

[0294] Figure 6 Example signaling between NFc 601, SCP 602, NRF 603 and NFp 604 is illustrated. Figure 6 This example shows an example enhanced service access authorization using a new custom header (e.g., 3gpp-Sbi-Additional-Access-Scopes).

[0295] During 6001, NFp 604 sends signaling to NRF 603. The signaling may include a request to register attributes and / or parameters of NFp 604 in a configuration file saved by NRF 603 for NFp 604. For example, in this example, the configuration file may include an indication of at least one scope that a NF service producer can provide to a NF service consumer. For example, NFp 604 may register with NRF 603 that NFp 604 can provide scopes S, W, X, and Y to NF service consumers.

[0296] During 6002, NFc 601 sends signaling to SCP 602. The signaling may include a service request (e.g., a request to be provided a service to a service producer). The signaling may not include an access token.

[0297] The signaling may include a first header portion that specifies at least one scope associated with the requested service (e.g., hereinafter labeled as scopes S and W). For example, the at least one scope may include a service level scope (S) and / or a resource / operation scope (W). The first header portion may include, for example, a 3GPP-Sbi-Access-Scope portion.

[0298] The signaling may include a second header part specifying at least one additional scope, eg, labeled hereinafter as X, Y, and Z. The second header part may include, for example, a 3GPP-Sbi-Additional-Access-Scopes part.

[0299] During 6003, SCP 602 sends signaling to NRF 603. The signaling may include an NF discovery request for identifying at least one NF service producer that can provide the service requested in the service request of 6002.

[0300] During 6004, NRF 603 sends signaling to SCP 602. The signaling may include a NF discovery response. For example, the signaling may include at least a portion of a NF profile for NFp, which indicates the operations allowed for each NF type and / or each NF instance. For example, the signaling may indicate that NFp is able to provide ranges S, W, X, and Y to NF service consumers.

[0301] During 6005, SCP 602 sends signaling to NRF 603. The signaling may include an access token request. The signaling may include a request for an access token for ranges S, W, X, Y, and Z. The signaling may include at least one indication of which of these ranges will be used for the actual service requested (e.g., S and W), and which of these ranges will not be used for the actual service requested (e.g., X, Y, and Z).

[0302] During 6006, NRF 603 sends signaling to SCP 602. The signaling may include an access token response. The signaling may include an access token. The access token may include tokens for scopes S, W, X, and Y (e.g., the scopes that NFp 604 is registered as being able to provide to NF service consumers in the configuration file of NFp at NRF, which overlap with the requested (multiple) scopes of 6005). The signaling may include an indication of which scopes are available via the access token.

[0303] During 6007, SCP 602 sends signaling to NFp 604. The signaling may include a service request on behalf of NFc 601. The signaling may include the access token received during 6006.

[0304] During 6008, NFp 604 sends signaling to SCP 602. The signaling may include an indication that the service request 6007 was successful.

[0305] During 6009, SCP 602 sends signaling to NFc 601. The signaling may include an indication that the service request has been successful. The signaling may include the access token of 6006. The signaling may include an indication of which ranges are available via the access token. For example, the signaling may include a 3gpp-Sbi-Access-Token and indicate that the access token is valid for ranges S, W, X, and Y. NFc 601 may cache the access token. After this successful establishment, NFc 601 may receive services with ranges S and W from NFp 604.

[0306] During 6010, NFc 601 determines that a new service is requested that utilizes resources and / or operations defined with additional scope Y.

[0307] During 6011, NFc 601 sends signaling to SCP 602. The signaling may include a service request. The service request may include a service request for scope Y. For example, the signaling may include a service request for service level scope S with resource and / or operation scope Y. The signaling may include 3gpp-Sbi-Access-Scope. The signaling may include an explicit indication of scope S and scope Y.

[0308] For all examples discussed herein, the NFc may determine when to include additional scope requests (e.g., for scopes S and Y) in any of a number of different ways. For example, the NFc may include additional scopes in its service request in situations where the SCP may need to request a new access token, such as when no valid access token is available at the NFc (and therefore no access token may be included in the service request sent to the SCP), such as in situations where the NFc delegates any request retransmissions to the SCP (e.g., when the NFp to which the request is directed is unavailable). These scenarios involve similar conditions to the insertion of the existing 3gpp-Sbi-Access-Scope (defined in 3GPP TS 29.500) by the NFc.

[0309] For example, according to 3GPP TS29.500, when the NF service consumer does not include an access token in the service request, or when the NF service consumer does include an access token but the access token only has a matching service level scope (but not a matching resource / operation level scope), or if the access token is specific to an NF instance and reselection of a different producer instance may be applied at the SCP (e.g., the Route Binding header or the Discovery header provides the producer's NF set identifier), the NF service consumer may include in the service request to the SCP: the NF service discovery factor to be used by the SCP for the service access authorization process (as specified in clause 6.10.3.2 of 3GPP TS 29.500); and the 3gpp-Sbi-Access-Scope header indicating the access scope of the service request for access authorization, as defined in the corresponding API for a specific resource / operation (see clause 5.2.3.2.16 of 3GPP TS29.500).

[0310] During 6012, SCP 602 determines that SCP 602 does not need to signal a discovery and / or access token request because the access token received during 6006 can be used for the service requested during 6011. SCP 602 may make this determination based on previous caching of access tokens received at SCP 602 during 6006. SCP 602 may make this determination based on receipt of the access token in the service request of 6011.

[0311] Following this determination, during 6013 SCP 602 signals NFp 604 a service request for ranges S and Y.

[0312] During 6014, NFp 604 sends signaling to SCP 602. The signaling may indicate that the service request of 6013 is successful. The indication of the success of the service request may be forwarded (not shown) to NFc 601. After the successful establishment, NFc 601 may receive services with scopes S and Y from NFp 604.

[0313] Figure 7 An example of SCP determining the scope of a request wildcard is illustrated.

[0314] Figure 7 Example signaling between NFc 701, SCP 702, NRF 703 and NFp 704 is illustrated. Figure 7 This example illustrates an example of enhanced service access authorization, where the SCP is configured to request an access token or a wildcard scope of all scopes allowed by the NFp from the NF service consumer.

[0315] During 7001, NFp 704 sends signaling to NRF 703. The signaling may include a request to register attributes and / or parameters of NFp 704 in a configuration file maintained by NRF 703 for NFp 704. For example, in this example, the configuration file may include an indication of at least one scope that a NF service producer can provide to a NF service consumer. For example, NFp 704 may register with NRF 703 that NFp 704 can provide scopes S, W, X, and Y to NF service consumers.

[0316] During 7002, NFc 701 sends signaling to SCP 702. The signaling may include a service request (e.g., a request to be provided a service to a service producer). The signaling may not include an access token.

[0317] The signaling may include a first header portion that specifies at least one scope associated with the requested service (e.g., hereinafter labeled as scopes S and W). For example, the at least one scope may include a service level scope (S) and / or a resource / operation scope (W). The first header portion may include, for example, a 3GPP-Sbi-Access-Scope portion.

[0318] During 7003, SCP 702 sends signaling to NRF 703. The signaling may include an NF discovery request for identifying at least one NF service producer that can provide the service requested in the service request of 7002.

[0319] During 7004, NRF 703 sends signaling to SCP 702. The signaling may include a NF discovery response. For example, the signaling may include at least a portion of a NF profile for NFp, which indicates the operations allowed for each NF type and / or each NF instance. For example, the signaling may indicate that NFp is able to provide ranges S, W, X, and Y to NF service consumers.

[0320] During 7005, SCP 702 sends signaling to NRF 703. The signaling may include an access token request. The signaling may include a request for an access token for ranges S, W, X, Y, and Z, or a request for a wildcard range (e.g., a request for all ranges registered as provided by NFp and allowed to be received by NFc). When an indication of a specific range is included in the signaling of 7005, the signaling may include at least one indication indicating which of these ranges will be used for the actual service requested (e.g., S and W), and / or which of these ranges will not be used for the actual service requested (e.g., X, Y, and Z).

[0321] During 7006, NRF 703 sends signaling to SCP 702. The signaling may include an access token response. The signaling may include an access token. The access token may include tokens for scopes S, W, X, and Y (e.g., NFp 704 is registered as being able to be provided to NF service consumers in the NFp profile at the NRF and is allowed to be provided to NFc 701). The signaling may include an indication of which scopes are available via the access token. In other words, the signaling may include an identification of which scopes are available via the access token.

[0322] During 7007, SCP 702 sends signaling to NFp 704. The signaling may include a service request on behalf of NFc 701. The signaling may include the access token received during 7006. The access token may indicate at least ranges S, W, X, and Y.

[0323] During 7008, NFp 704 sends signaling to SCP 702. The signaling may include an indication that the service request 7007 was successful.

[0324] During 7009, SCP 702 sends signaling to NFc 701. The signaling may include an indication that the service request has been successful. The signaling may include the access token of 7006. The signaling may include an indication of which ranges are available via the access token. For example, the signaling may include a 3gpp-Sbi-Access-Token and indicate that the access token is valid for ranges S, W, X, and Y. NFc 701 may cache the access token. After this successful establishment, NFc 701 may receive services with ranges S and W from NFp 704.

[0325] During 7010, NFc 701 determines that a new service is requested that utilizes resources and / or operations defined with additional scope Y.

[0326] During 7011, NFc 701 sends signaling to SCP 702. The signaling may include a service request. The service request may include a service request for scope Y. For example, the signaling may include a service request for service level scope S with resource and / or operation scope Y. The signaling may include 3gpp-Sbi-Access-Scope. The signaling may include an explicit indication of scope S and scope Y.

[0327] During 7012, SCP 702 determines that SCP 702 does not need to signal a discovery and / or access token request because the access token received during 7006 can be used for the service requested during 7011. SCP 702 may make this determination based on previous caching of access tokens received at SCP 702 during 7006. SCP 702 may make this determination based on receipt of the access token in the service request at 7011.

[0328] After this determination, during 7013, SCP 702 signals to NFp 704 a service request for ranges S and Y.

[0329] During 7014, NFp 704 sends signaling to SCP 702. The signaling may indicate that the service request of 7013 is successful. The indication of the success of the service request may be forwarded (not shown) to NFc 701. After the successful establishment, NFc 701 may receive services with scopes S and Y from NFp 704.

[0330] Figure 8 Example signaling between NFc 801, SCP 802, NRF 803 and NFp 804 is illustrated. Figure 8 This example illustrates an example enhanced service access authorization in which, regardless of which scopes are requested as part of an access token request signaled by an SCP, an authorization server (e.g., NRF) provides an access token that covers greater scopes than requested in the access token request.

[0331] During 8001, NFp 804 sends signaling to NRF 803. The signaling may include a request to register attributes and / or parameters of NFp 804 in a configuration file saved by NRF 803 for NFp 804. For example, in this example, the configuration file may include an indication of at least one scope that a NF service producer can provide to a NF service consumer. For example, NFp 804 may register with NRF 803 that NFp 804 can provide scopes S, W, X, and Y to NF service consumers.

[0332] During 8002, NFc 801 sends signaling to SCP 802. The signaling may include a service request (e.g., a request to be provided a service to a service producer). The signaling may not include an access token.

[0333] The signaling may include a first header portion that specifies at least one scope associated with the requested service (e.g., hereinafter labeled as scopes S and W). For example, the at least one scope may include a service level scope (S) and / or a resource / operation scope (W). The first header portion may include, for example, a 3GPP-Sbi-Access-Scope portion.

[0334] During 8003, SCP 802 sends signaling to NRF 803. The signaling may include an NF discovery request for identifying at least one NF service producer that can provide the service requested in the service request of 8002.

[0335] During 8004, NRF 803 sends signaling to SCP 802. The signaling may include an NF discovery response. For example, the signaling may include at least a portion of an NF profile for NFp, which indicates the operations allowed for each NF type and / or each NF instance. For example, the signaling may indicate that NFp is able to provide scopes S, W, X, and Y to NF service consumers.

[0336] During 8005, SCP 802 sends signaling to NRF 803. The signaling may include an access token request. The signaling may include a request for an access token for scopes associated with the requested server (e.g., scopes S and W). The signaling may include at least one indication which of these scopes will be used for the actual service requested (e.g., S and W). The signaling may not indicate any other scopes other than those explicitly indicated as being used for the requested service. In other words, the access token request may only indicate those scopes that will be used as part of the requested service.

[0337] During 8006, NRF 803 sends signaling to SCP 802. The signaling may include an access token response. The signaling may include an access token. The access token may include tokens for scopes S, W, X, and Y (e.g., for more than requested scopes, such as all scopes that NFp 804 is registered as being able to provide to NF service consumers in the NFp profile at the NRF, which overlap with the requested scope(s) of 8005). The signaling may include an indication of which scopes are available via the access token (e.g., an indication that explicitly identifies which scopes are available via the access token).

[0338] During 8007, SCP 802 sends signaling to NFp 804. The signaling may include a service request on behalf of NFc 801. The signaling may include the access token received during 8006.

[0339] During 8008, NFp 804 sends signaling to SCP 802. The signaling may include an indication that the service request 8007 was successful.

[0340] During 8009, SCP 802 sends signaling to NFc 801. The signaling may include an indication that the service request has been successful. The signaling may include the access token of 8006. The signaling may include an indication of which ranges are available via the access token. For example, the signaling may include a 3gpp-Sbi-Access-Token and indicate that the access token is valid for ranges S, W, X, and Y. NFc 801 may cache the access token. After this successful establishment, NFc 801 may receive services with ranges S and W from NFp 804.

[0341] During 8010, NFc 801 determines that a new service is requested that utilizes resources and / or operations defined with additional scope Y.

[0342] During 8011, NFc 801 sends signaling to SCP 802. The signaling may include a service request. The service request may include a service request for scope Y. For example, the signaling may include a service request for service level scope S with resource and / or operation scope Y. The signaling may include 3gpp-Sbi-Access-Scope. The signaling may include an explicit indication of scope S and scope Y.

[0343] During 8012, SCP 802 determines that SCP 802 does not need to signal a discovery and / or access token request because the access token received during 8006 can be used for the service requested during 8011. SCP 802 may make this determination based on previous caching of access tokens received at SCP 802 during 8006. SCP 802 may make this determination based on receipt of the access token in the service request at 8011.

[0344] After this determination, during 8013, SCP 802 signals to NFp 804 a service request for ranges S and Y.

[0345] During 8014, NFp 804 sends signaling to SCP 802. The signaling may indicate that the service request of 8013 is successful. The indication of the success of the service request may be forwarded (not shown) to NFc 801. After the successful establishment, NFc 801 may receive services with scopes S and Y from NFp 804.

[0346] Fig. 9 An example is illustrated where the NF producer does not provide all scopes associated with the requested service.

[0347] Fig. 9 Example signaling between NFc 901, SCP 902, NRF 903 and NFp 904 is shown. Fig. 9 This example shows an example enhanced service access authorization using a new custom header (e.g., 3gpp-Sbi-Additional-Access-Scopes).

[0348] During 9001, NFp 904 sends signaling to NRF 903. The signaling may include a request to register attributes and / or parameters of NFp 904 in a configuration file saved by NRF 903 for NFp 904. For example, in this example, the configuration file may include an indication of at least one scope that a NF service producer can provide to a NF service consumer. For example, NFp 904 may register with NRF 903 that NFp 904 can provide scopes S, X, and Y to NF service consumers.

[0349] During 9002, NFc 901 sends signaling to SCP 902. The signaling may include a service request (e.g., a request to provide a service from a service producer). The signaling may not include an access token.

[0350] The signaling may include a first header portion that specifies at least one scope associated with the requested service (e.g., hereinafter labeled as scopes S and W). For example, the at least one scope may include a service level scope (S) and / or a resource / operation scope (W). The first header portion may include, for example, a 3GPP-Sbi-Access-Scope portion.

[0351] The signaling may include a second header part specifying at least one additional scope, eg, labeled hereinafter as X, Y, and Z. The second header part may include, for example, a 3GPP-Sbi-Additional-Access-Scopes part.

[0352] During 9003, SCP 902 sends signaling to NRF 903. The signaling may include an NF discovery request for identifying at least one NF service producer that can provide the service requested in the service request of 9002.

[0353] During 9004, NRF 903 sends signaling to SCP 902. The signaling may include an NF discovery response. For example, the signaling may include at least a portion of an NF profile for NFp, which indicates the operations allowed for each NF type and / or each NF instance.

[0354] During 9005, SCP 902 sends signaling to NRF 903. The signaling may include a request for an access token. The signaling may include a request for access tokens for ranges S, W, X, Y, and Z. The signaling may include at least one indication of which of these ranges are to be used for the actual service requested (e.g., S and W), and which of these ranges are not to be used for the actual service requested (e.g., X, Y, and Z).

[0355] As previously discussed, throughout the examples provided herein, the SCP may determine the set of scopes for authorizing incoming service requests as: the scopes received in the 3gpp-Sbi-Access-Scope header in the service request received from the NFc; or the intersection of the scopes received in the 3gpp-Sbi-Access-Scope header in the service request received from the NFc and the scopes that the NFc is allowed to access as registered by the NFp in the NFp profile discovered by the SCP from the NRF.

[0356] Furthermore, the SCP may determine the additional scopes not to be used for authorizing incoming service requests as: the scopes received in a new 3gpp-Sbi-Additional-Access-Scopes header in the service request received from NFc; or the scopes allowed by NFp to NFc as registered in the NFp profile discovered by SCP from NRF, in addition to those listed in the 3gpp-Sbi-Access-Scope header; or any intersection of the above lists.

[0357] During 9006, NRF 903 sends signaling to SCP 902. The signaling may include an access token response. The signaling may include an access token. The access token may include tokens for scopes S, X, and Y (e.g., NFp 904 is registered as being able to provide scopes to NF service consumers in the configuration file of NFp at NRF, which overlap with the requested (multiple) scopes of 9005). Therefore, the access token cannot be used to access services that utilize scope W. The signaling may include an explicit indication of which scopes are available via the access token.

[0358] During 9007, SCP 902 sends signaling to NFc 901. The signaling may include an indication that the service request has been unsuccessful. The signaling may include an access token of 9006. The signaling may include an indication of which ranges are available via the access token. For example, the signaling may include a 3gpp-Sbi-Access-Token and indicate that the access token is valid for ranges S, X, and Y. NFc 901 may cache the access token. After this successful establishment, NFc 901 may not receive services with ranges S and W from NFp 904. The signaling may be performed without SCP 902 signaling an access token to NFp 904.

[0359] During 9008, NFc 901 determines that a new service is requested that utilizes resources and / or operations defined with additional scope Y.

[0360] During 9009, NFc 901 sends signaling to SCP 902. The signaling may include a service request. The service request may include a service request for scope Y. For example, the signaling may include a service request for service level scope S with resource and / or operation scope Y. The signaling may include 3gpp-Sbi-Access-Scope. The signaling may include an explicit indication of scope S and scope Y.

[0361] During 9010, SCP 902 determines that SCP 902 does not need to signal a discovery and / or access token request because the access token received during 9006 can be used for the service requested during 9009. At SCP 902, SCP 902 may make this determination based on previous caching of the access token received during 9006. SCP 902 may make this determination based on receipt of the access token in the service request at 9009.

[0362] After this determination, during 9011, SCP 902 signals to NFp 904 a service request for ranges S and Y.

[0363] During 9012, NFp 904 sends signaling to SCP 902. The signaling may indicate that the service request of 9011 is successful. The indication of the success of the service request may be forwarded (not shown) to NFc 901. After the successful establishment, NFc 901 may receive services with scopes S and Y from NFp 904.

[0364] Fig. 9This example relates to a scenario in which the SCP requests an access token using a list of scopes indicated to the SCP in a 3gpp-Sbi-Access-Scope header part and a 3gpp-Sbi-Additional-Access-Scopes header part received from the NFc in a service request, and the NRF provides an access token for the list of scopes that does not include at least one of the scopes of the 3gpp-Sbi-Access-Scope. The NRF may include the access token obtained in a service rejection response to the NFc. This allows the NFc to reuse an access token that may have been granted for a later service request (e.g., for a new service request that includes at least one of the scopes indicated in the 3gpp-Sbi-Additional-Access-Scopes).

[0365] As Figures 6 to 9 As a variation of the above example, NFc may encode a wildcard scope in the 3gpp-Sbi-Additional-Access-Scopes header. This wildcard scope may indicate that NFc prefers that the access token be valid for any scope defined in the 5GC API (of the service request), if possible.

[0366] As an example, consider when NFc is an AMF and NFp is an SDM. An AMF that wants to access specific resources and / or operations of the SDM API may indicate a preference to obtain an access token valid for any resources and / or operations of the SDM API that the AMF may need to access later. Thus, as an example, when sending a service request for "read access and mobility subscription data", the enhancements specified herein may allow the SCP and AMF to obtain an access token that authorizes all of the following service operations / access to any of the following UDM SDM resources listed in Table 3.

[0367]

[0368] Table 3 Requested access and potential tags

[0369] Figures 10 to 12 The diagrams illustrate operations that may be performed by the apparatus described herein. These diagrams illustrate features of the above examples, so correspondence can be found between these features and elements of the following operations.

[0370] Fig.10 The diagram illustrates operations that may be performed by the first network device. The first network device may include a proxy function. For example, the first network device may include an SCP.

[0371] During 1001 , a first network device signals to a second network device a request for an access token of a network function consumer for authorizing the network function service consumer to access a first service from a network function service producer.

[0372] The second network device may include a device for retaining information about the network function service producer. For example, the second network device may include a device for enabling an access token to be provided to a network function service consumer for accessing services from the network function service producer. The second network function may include a network repository function.

[0373] During 1002, the first network device receives an access token from the second network device, wherein the access token includes: an indication of at least one second access right not associated with accessing the first service. The access token of 1002 is denoted herein as the received access token. The access token of 1002 may correspond to the access token requested in 1001, or may not correspond to the access token requested in 1001 (e.g., when the requested access right / scope of the generated access token is different from the access right / scope of the requested access token).

[0374] During 1003 , when the network function service producer is signaled a request to provide a service to the network function service consumer, the first network device may cause the received access token to be provided to the network function service producer.

[0375] When the received access token includes an indication of all access rights (eg, scopes) associated with providing the first service, the request to provide the service to the network function service consumer may include a request to provide the first service.

[0376] In other words, the first network device may: determine that the first service is associated with a predetermined set of access permissions; determine that the received access token includes all access permissions in the predetermined set of access permissions; and provide the received access token to the network function service producer to request the first service.

[0377] When the received access token omits an indication of at least one of the access rights (e.g., scopes) associated with providing the first service, the request to provide the service to the network function service consumer may not include a request to provide the first service. Regardless, the first network device may retain the received access token and / or provide the received access token to the network function service consumer for requesting a second service (a different service).

[0378] In other words, the first network device may: determine that the first service is associated with a predetermined set of access permissions; determine that the received access token granted by the second network device omits at least one access permission in the predetermined set of access permissions; and retain the received access token and / or provide the received access token to the network function service consumer without requesting the network function service producer to provide the first service to the network function service consumer.

[0379] When the received access token includes an indication of all access rights associated with providing the second service, the request for providing the service to the network function service consumer may include a request for providing the second service, wherein at least one of the access rights associated with providing the second service is at least one of the second access rights.

[0380] For example, when the network function service producer is signaled a request to provide a second service to the network function service consumer, the first network device may cause the received access token to be provided to the network function service producer, wherein the second service is associated with at least one of the at least one second access rights.

[0381] When the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer may include: signaling the received access token and the request to provide the second service to the network function service consumer to the network function service producer.

[0382] The first network device may receive a request for a second service from the network function service consumer, the request for the second service including the received access token.

[0383] The first network device may determine not to request a new access token dependent on determining that the received access token authorizes access to the at least one second access right.

[0384] The first network device may receive a service request for the first service from a network function service consumer prior to said signaling a request for an access token.

[0385] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0386] The first network device may signal a discovery request to discover a network function service producer to the second network device, and receive an indication of the network function service producer prior to signaling the request for an access token.

[0387] Signaling a request for an access token may include signaling a request including at least one of: an indication that at least one first access permission associated with accessing a first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by a network function service producer are being requested.

[0388] The first network device may provide, to the network function service consumer, a component of the received access token, the access token comprising an indication of at least one second access right not associated with accessing the first service.

[0389] When the network function service producer is signaled with a request to provide a second service to the network function service consumer, causing the received access token to be provided to the network function service producer may include: signaling the received access token and the request to provide the second service to the network function service consumer to the network function service producer.

[0390] Fig.11 The diagram illustrates operations that can be performed by the second network device. The second network device can be combined with Fig.10 As described.

[0391] For example, the second network device may include a device for retaining information about the network function service provider. For example, the second network device may include a device that enables an access token to be provided to a network function service consumer for accessing services from a network function service producer. The second network function may include a network repository function.

[0392] The first network device mentioned in this article may correspond to Fig.10 For example, the first network device may include an SCP.

[0393] During 1101 , a second network device may receive a request for an access token of a network function consumer from a first network device for authorizing the network function service consumer to access a first service from a network function service producer.

[0394] During 1102, the second network device may generate an access token, wherein the access token includes an indication of at least one second access right that is not associated with accessing the first service. The access token of 1102 is labeled herein as a generated access token. The access token of 1102 may correspond to the access token requested in 1101, or may not correspond to the access token requested in 1101 (e.g., when the requested access right / scope of the generated access token is different from the access right / scope of the requested access token).

[0395] During 1103 , the second network device may signal the generated access token to the first network device.

[0396] The second network device may: receive an indication of at least one of the following items from the network function service producer: at least one first access permission associated with accessing the first service, or at least one second access permission; and store the at least one first access permission and / or the at least one second access permission in a network configuration file of the network function service producer.

[0397] The generating may include: obtaining, from the network configuration file, an indication of at least one first access right and / or at least one second access right in the network configuration file of the network function service producer.

[0398] The request may include at least one of: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0399] The second network device may: determine that the first service is associated with a predetermined set of access permissions; determine that the generated access token omits at least one access permission in the predetermined set of access permissions; and provide the generated access token to the first network device.

[0400] The second network device may: determine that the first service is associated with a predetermined set of access permissions; determine that the generated access token includes all access permissions in the predetermined set of access permissions; and provide the generated access token to the first network device.

[0401] Fig.12 The diagram illustrates operations that may be performed by an apparatus for a network function service consumer. The network function service consumer may include Fig.10 and / or Fig.11 network functions to serve consumers.

[0402] During 1201, a network function service consumer signals a service request for accessing a first service from a network function service producer to a first network device. The first network device may include Fig.10 and / or Fig.11 The first network device.

[0403] During 1202 , a network function service consumer receives an access token from a first network device, wherein the access token includes an indication of at least one second access right not associated with accessing a first service.

[0404] During 1203 , when the network function service producer is signaled a request to provide a service to the network function service consumer, the network function service consumer causes an access token to be provided to the network function service producer.

[0405] The service request may include at least one of the following items: an indication that at least one first access permission associated with accessing the first service is being requested, an indication that at least one second access permission not associated with accessing the first service is being requested, or an indication that all access permissions provided by the network function service producer are being requested.

[0406] When the network function service producer is signaled with a request to provide a second service to the network function service consumer, the device may cause the access token to be provided to the network function service producer, wherein the second service is associated with at least one of the at least one second access rights. In this case, when the network function service producer is signaled with a request to provide the second service to the network function service consumer, causing the access token to be provided to the network function service producer may include: signaling (e.g., via the first network device / SCP) the access token to the network function service producer, and the request to provide the second service to the network function service consumer.

[0407] The device may signal a request for a second service to the first network device, the request for the second service including the access token.

[0408] The device may determine that the second service is associated with a second predetermined set of access rights; determine that the access token includes all access rights in the predetermined set of access rights and provide the access token to the first network device when signaling a request to access the second service.

[0409] The apparatus may determine that a first service is associated with a first predetermined set of access permissions; determine that an access token omits at least one access permission in the first predetermined set of access permissions; and retain the access token. This may be useful in the case where a later requested service (e.g., a second service) has access permissions (e.g., a scope) that are fully covered by the access token.

[0410] In all of the above examples, the access rights for accessing the service may correspond to the scope of the authorized access token.

[0411] Furthermore, in all of the above examples, when the access right will be used (e.g., required) to access the service, the access right can be referred to as being "associated" with the service. In other words, when the access right is not used (e.g., not required) to access the service, the access right can be referred to as being "not associated" with the service.

[0412] The presently described examples may significantly reduce the number of access token requests that need to be requested by the SCP to the NRF compared to current schemes due to more extensive reuse of access tokens for different service operations for the same API.

[0413] The foregoing description has provided a complete and informative description of some examples by way of non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description when read in conjunction with the accompanying drawings and claims. However, all such and similar modifications of the present teachings will still fall within the scope of the claims.

[0414] In the above, different examples are described using radio access architectures based on Long Term Evolution Advanced (LTE Advanced, LTE-A) or New Radio (NR, 5G) as examples of access architectures to which the described techniques may be applied, however, the examples are not limited to such architectures. These examples may also be applied to other types of communication networks with suitable components by appropriately adjusting parameters and procedures. Some examples of other options for suitable systems are Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Network (WLAN or Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using Ultra-Wideband (UWB) technology, sensor networks, mobile ad hoc networks (MANETs), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0415] As provided herein, various aspects are described in the specific embodiments and claims of the examples. In general, some examples can be implemented in hardware or dedicated circuits, software code, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software code that can be executed by a controller, microprocessor, or other computing device, but the examples are not limited thereto. Although various examples can be illustrated and described as block diagrams, flow charts, or using some other graphical representations, it is well understood that, as non-limiting examples, these boxes, devices, systems, techniques, or methods described herein can be implemented in hardware, software code, firmware code, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0416] These examples may be implemented by a computer software code stored in a memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software code and hardware.

[0417] The memories mentioned herein may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[0418] The (data) processor referred to in this document may be of any type suitable for the local technical environment, and may include, by way of non-limiting example, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0419] Furthermore, in this regard, it should be noted that e.g. Fig.10 , and / or Fig.11 and / or Fig.12 , and / or any of the processes described in other ways above may represent the operation of a computer program deployed by at least one processor included in the device (where the computer program includes instructions for causing the device to perform at least one action, which instructions are represented as software code stored on at least one memory), or interconnected logic circuits, boxes and functions, or a combination of the operation of a computer program deployed by at least one processor included in the device and logic circuits, boxes and functions. The software code may be stored on a memory, such as a physical medium as a memory chip, or a memory block implemented within a processor, a magnetic medium (such as a hard disk or floppy disk), and an optical medium (such as a DVD and its data variant CD, as an example).

[0420] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a gate-level circuit, and a processor based on a multi-core processor architecture.

[0421] Additionally or alternatively, some examples may be implemented using a circuit system. The circuit system may be configured to perform one or more of the previously described functions and / or method steps. The circuit system may be provided in a base station and / or in a communication device and / or in a core network entity.

[0422] As used in this application, the term "circuitry" or "component" may refer to one or more or all of the following:

[0423] (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry);

[0424] (b) a combination of hardware circuitry and software such as (where applicable):

[0425] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0426] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software code, software and memory(s) that work together to enable an apparatus (such as a communication device or base station) to perform the various functions previously described; and

[0427] (c) Hardware circuits and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) to operate, but where the software is not required for operation, the software may not be present.

[0428] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware code. The term circuitry also covers, for example, an integrated device.

[0429] Implementations of the present disclosure may be practiced in various components, such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available to convert logic-level designs into semiconductor circuit designs that are ready to be etched and formed on semiconductor substrates.

[0430] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions (wherein a list of two or more elements is connected by “and” or “or”) mean at least any one element, or at least any two or more elements, or at least all elements.

[0431] As used herein, the term "non-transitory" is a restriction to the medium itself (ie, tangible, not a signal), not to data storage persistence (eg, RAM vs. ROM).

[0432] The scope of protection sought by various examples of the present disclosure is set out by the independent claims. Examples and features described in this specification that do not fall within the scope of the independent claims, if any, should be construed as examples that help understand the present disclosure.

[0433] The foregoing description has provided a complete and informative description of example implementations of the present disclosure by way of non-limiting examples. However, when read in conjunction with the accompanying drawings and the appended claims, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description. However, all such and similar modifications of the teachings of the present disclosure will still fall within the scope of the present invention as defined in the appended claims. In fact, there are other implementations, including combinations of one or more implementations with any other implementations previously discussed.

Claims

1. A first network device, include: at least one processor; as well as at least one memory including software code, which, when executed by the at least one processor, causes the first network device to perform: Receiving a service request for accessing a service from a network function service consumer, the service request for accessing the service comprising: at least one first scope associated with accessing the service, and at least one second scope not associated with accessing the service; signaling a request for an access token for the network function service consumer to authorize the network function service consumer to access the service from the network function service producer to the second network device, the request for the access token comprising: the at least one first range associated with accessing the service, and the at least one second range not associated with accessing the service; receiving the access token from the second network device, wherein the received access token is associated with the at least one first scope and the at least one second scope, the at least one first scope being associated with accessing the service and the at least one second scope being not associated with accessing the service; and A service request for providing the service to the network function service consumer is signaled to the network function service producer, the service request for providing the service including the received access token.

2. The first network device of claim 1 , wherein the software code, when executed by the at least one processor, further causes the first network device to perform: signaling a discovery request to the second network device for discovering the network function service producer; and Prior to said signaling said request for said access token, receiving an indication of said network function service producer.

3. The first network device of any preceding claim, wherein the software code, when executed by the at least one processor, further causes the first network device to perform: The received access token is provided to the network function service consumer.

4. The first network device of any preceding claim, wherein the software code, when executed by the at least one processor, further causes the first network device to perform: Signaling a service request to the network function service producer for providing other services to the network function service consumer, the service request for providing the other services comprising the received access token, wherein the other services are associated with at least one of the at least one second scope.

5. The first network device according to any preceding claim, wherein the service request for providing the service to the network function service consumer is signaled to the network function service producer. include: determining that the service is associated with a predetermined set of scopes; as well as It is determined that the received access token is associated with all scopes in a predetermined set of scopes.

6. The first network device of any preceding claim, wherein the access token corresponds to an authorization access token, and the at least one first scope and the at least one second scope correspond to respective scopes of the authorization access token.

7. A second network device, include: at least one processor; as well as at least one memory including software code, which, when executed by the at least one processor, causes the second network device to perform: receiving, from a first network device, a request for an access token for a network function service consumer for authorizing the network function service consumer to access a service from a network function service producer, the request for the access token comprising: at least one first scope associated with accessing the service, and at least one second scope not associated with accessing the service; generating the access token, wherein the access token is associated with the at least one first scope and the at least one second scope, the at least one first scope being associated with accessing the service, and the at least one second scope being not associated with accessing the service; and The generated access token is signaled to the first network device.

8. The second network device of claim 7, wherein the software code, when executed by the at least one processor, further causes the second network device to perform: receiving, from the network function service producer, at least one of the at least one first range or the at least one second range, the at least one first range being associated with accessing the service and the at least one second range being not associated with accessing the service; and The at least one of the at least one first range or the at least one second range is stored in a network configuration file of the network function service producer.

9. The second network device according to claim 8, wherein the generating include: At least one of the at least one first range or the at least one second range is obtained from the network configuration file of the network function service producer.

10. The second network device according to any one of claims 7 to 9, wherein the access token corresponds to an authorization access token, and the at least one first scope and the at least one second scope correspond to respective scopes of the authorization access token.

11. A device for a network function service consumer, the device include: at least one processor; as well as at least one memory including software code, which, when executed by the at least one processor, causes the second network device to perform: A service request for accessing a service is signaled to a first network device, the service request comprising an indication of at least one first range associated with accessing the service and at least one second range not associated with accessing the service.

12. A method for communication, include: Receiving a service request for accessing a service from a network function service consumer, the service request for accessing the service comprising: at least one first scope associated with accessing the service, and at least one second scope not associated with accessing the service; signaling to a second network device a request for an access token for the network function service consumer for authorizing the network function service consumer to access the service from the network function service producer, the request for the access token comprising: the at least one first scope associated with accessing the service, and the at least one second scope not associated with accessing the service; receiving the access token from the second network device, wherein the received access token is associated with the at least one first scope and the at least one second scope, the at least one first scope being associated with accessing the service and the at least one second scope being not associated with accessing the service; and A service request for providing the service to the network function service consumer is signaled to the network function service producer, the service request for providing the service including the received access token.

13. The method according to claim 12, further comprising: include: signaling, to the second network device, a discovery request for discovering the network function service producer; as well as Prior to said signaling said request for said access token, receiving an indication of said network function service producer.

14. The method according to claim 12 or 13, further comprising: include: The received access token is provided to the network function service consumer.

15. The method according to any one of claims 12 to 14, further comprising: include: Signaling a service request to the network function service producer for providing other services to the network function service consumer, the service request for providing the other services comprising the received access token, wherein the other services are associated with at least one of the at least one second scope.

16. The method according to any one of claims 12 to 15, wherein the service request for providing the service to the network function service consumer is signaled to the network function service producer. include: determining that the service is associated with a predetermined set of scopes; as well as It is determined that the received access token is associated with all scopes in a predetermined set of scopes.

17. The method according to any one of claims 12 to 16, wherein the access token corresponds to an authorization access token, and the at least one first scope and the at least one second scope correspond to respective scopes of the authorization access token.

18. A method for communication, include: receiving, from a first network device, a request for an access token for a network function service consumer for authorizing the network function service consumer to access a service from a network function service producer, the request for the access token comprising: at least one first scope associated with accessing the service, and at least one second scope not associated with accessing the service; generating the access token, wherein the access token is associated with the at least one first scope and the at least one second scope, the at least one first scope being associated with accessing the service, and the at least one second scope being not associated with accessing the service; and The generated access token is signaled to the first network device.

19. The method according to claim 18, further comprising: include: receiving, from the network function service producer, at least one of the at least one first range or the at least one second range, the at least one first range being associated with accessing the service and the at least one second range being not associated with accessing the service; as well as The at least one of the at least one first range or the at least one second range is stored in a network configuration file of the network function service producer.

20. The method according to claim 19, wherein said generating include: At least one of the at least one first range or the at least one second range is obtained from the network configuration file of the network function service producer.

21. The method according to any one of claims 18 to 20, wherein the access token corresponds to an authorization access token, and the at least one first scope and the at least one second scope correspond to respective scopes of the authorization access token.

22. A method for communication, include: A service request for accessing a service is signaled to a first network device, the service request comprising an indication of at least one first range associated with accessing the service and at least one second range not associated with accessing the service.