Resource authorization during federated learning process in 5g core
Patent Information
- Application Number
- PCT/IB2024/054681
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2024-05-14
- Publication Date
- 2024-11-21
Smart Images

Figure IB2024054681_21112024_PF_FP_ABST
Abstract
Description
RESOURCE AUTHORIZATION DURING FEDERATED LEARNING PROCESS IN 5G COREFIELD OF THE DISCLOSURE
[0001] Various exemplary embodiments disclosed herein relate to resource authorization during federated learning process in 5G core.BACKGROUND
[0002] In 5G networks federated learning (FL) may be used among network data analytics functions (NWDAF). Federated learning is a machine learning technique that trains an algorithm across multiple decentralized edge devices or servers holding local data samples, without exchanging the local data. This approach stands in contrast to traditional centralized machine learning techniques where all the local datasets are uploaded to one server, as well as to more classical decentralized approaches which often assume that local data samples are identically distributed. Federated learning enables multiple actors to build a common, robust machine learning model without sharing data, thus allowing to address critical issues such as data privacy, data security, data access rights, and access to heterogeneous data.SUMMARY
[0003] A summary of various exemplary embodiments is presented below.
[0004] Various embodiments relate to an authorization server apparatus configured to implement a resource authorization mechanism for a federated learning (FL) training process, including: at least one processor; and at least one memory storing instructions, that when executed by the at least one processor, cause the apparatus at least to: receive from a first network device FL registration information including FL utilization information; receive an access token request from a second network device for the first network device that is a potential FL client including request utilization information; determine if the second network device is authorized for the first network device based upon the FL utilization information and the request utilization information; and send an access token for the first network device to the second network device when the access token request for the first network device is authorized.
[0005] Various embodiments are described, wherein the utilization information includes maximum resource utilization information.
[0006] Various embodiments are described, wherein the maximum resource utilization information includes processor throughput, memory, and storage space.
[0007] Various embodiments are described, wherein the utilization information includes maximum resource utilization information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
[0008] Various embodiments are described, wherein the utilization information includes at least one of a geographical area of the second network device, the maximum number of second network device instances from the same vendor allowed to use the FL client, the maximum number of FL client instances from the same vendor used by one or more second network devices from the same vendor, and geographical area restrictions per analytics ID.
[0009] Various embodiments are described, wherein the utilization information includes maximum FL process execution time information.
[0010] Various embodiments are described, wherein the utilization information includes maximum FL process execution time information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
[0011] Various embodiments are described, wherein the access token request includes at least one of a FL process execution time required per analytics ID, a maximum resource consumption, and a geographical area of the second network device.
[0012] Various embodiments are described, wherein the access token includes at least one of total FL process execution time and geographical area of the second network device.
[0013] Various embodiments are described, wherein the authorization server is a network repository function (NRF), and the first and second network devices are a network data analytics function (NWDAF).
[0014] Further various embodiments relate to a federated learning (FL) client apparatus configured to implement a resource authorization mechanism for a FL training process, including: at least one processor; and at least one memory storing instructions, that when executed by the at least one processor, cause the apparatus at least to: send to an authorization server FL registration information including utilization information; receive a FL service request including an analytics ID, FL model parameters, and an access token from a second network device including utilization information; verifying the access token; and sending asuccess response indicating that the FL client will use its analytics data to train and update a FL machine learning model.
[0015] Various embodiments are described, wherein the at least one memory stores instructions, that when executed by the at least one processor, cause the apparatus to: train the FL machine learning model using analytics data associated with the analytics ID to update FL machine learning model parameters; and send updated FL machine learning model parameters to the second network device.
[0016] Various embodiments are described, wherein the utilization information includes maximum resource utilization information.
[0017] Various embodiments are described, wherein the maximum resource utilization information includes processor throughput, memory, and storage space.
[0018] Various embodiments are described, wherein the utilization information includes maximum resource utilization information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
[0019] Various embodiments are described, wherein the utilization information includes at least one of a geographical area of the second network device, the maximum number of second network device instances from the same vendor allowed to use a FL client, the maximum number of FL client instances from the same vendor used by one or more second network devices from the same vendor, and geographical area restrictions per analytics ID.
[0020] Various embodiments are described, wherein the utilization information includes maximum FL process execution information.
[0021] Various embodiments are described, wherein the utilization information includes maximum FL process execution time information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
[0022] Various embodiments are described, wherein the FL client is a network data analytics function (NWDAF).
[0023] Further various embodiments relate to a federated learning (FL) server apparatus configured to implement an authorization mechanism for a FL training process, including: at least one processor; at least one data storage; and at least one memory storing instructions, that when executed by the at least one processor, cause the apparatus at least to; send a discovery request to an authorization server; receive from the authorization server information regardinga potential FL client; send an access token request to the authorization server for the potential FL client including request utilization information; receive an access token for the FL client from the authorization server when access token request for the FL client is authorized; and sending a FL service request access token to the FL client including utilization information.
[0024] Various embodiments are described, wherein the utilization information includes maximum resource utilization information.
[0025] Various embodiments are described, wherein the maximum resource utilization information includes processor throughput, memory, and storage space.
[0026] Various embodiments are described, wherein the utilization information includes maximum resource utilization information based on at least one of analytics identification (ID), interoperability ID, vender ID of the FL server, regulatory constraints, number of FL servers already served, and a network function instance ID of the FL server.
[0027] Various embodiments are described, wherein the utilization information includes at least one of a geographical area of the FL server, the maximum number of FL server instances from the same vendor allowed to use a FL client, the maximum number of FL client instances from the same vendor used by one or more FL servers from the same vendor, and geographical area restrictions per analytics ID.
[0028] Various embodiments are described, wherein the utilization information includes maximum FL process execution time information.
[0029] Various embodiments are described, wherein the utilization information includes maximum FL process execution time information based on at least one of analytics identification (ID), interoperability ID, vender ID of the FL server, regulatory constraints, number of FL servers already served, and a network function instance ID of the FL server.
[0030] Various embodiments are described, wherein the FL server is a network data analytics function (NWDAF).
[0031] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description whenconsidered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.BRIEF DESCRIPTION OF DRAWINGS
[0032] So that the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.
[0033] FIG. 1 illustrates a portion of the 5G core network that provides network data analytics services.
[0034] FIG. 2 illustrates an implementation of a resource authorization mechanism in the 5G core.
[0035] FIG. 3 illustrates an exemplary hardware diagram for implementing the authorization mechanism.DETAILED DESCRIPTION
[0036] Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or combined with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
[0037] Several aspects of federated learning in 5G systems will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and / or the like (collectively referred to as “elements”). These elements may be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0038] It should be noted that while aspects may be described herein using terminology commonly associated with 5G mobile network technologies, aspects of the present disclosure can be applied in other generation-based mobile network systems, such as 6G and later.
[0039] Federated learning (FL) may be used among network data analytics functions (NWDAF) in 5G networks to develop machine learning (ML) models trained using various data analytics from the NWDAFs. FL uses a FL server that collects and consumes data from FL clients. The FL server is able to develop a machine learning model based upon the data analytics from various NWDAFs. The application of FL to data analytics in the 5G core leads to a better machine learning model. It also allows for the analytics data at the various NWDAFs to remain private and secure. In order to implement FL in the 5G core, various mechanisms that enable authorization of NWDAFs to operate as FL servers and FL clients have been defined. An authorization framework for 5G core using OAuth 2.0 is currently defined in TS 33.501, Clause 13. Tdoc S2-2306099(https: / / www.3gpp.org / ftp / tsg_sa / WG2_Arch / TSGS2_156E_Electronic_2023-04 / Docs / S2- 2306099.zip) defines the procedure and services for ML Model Training, which are part of and enable the federated learning process in the 5G core. Currently there is an issue with respect to the FL authorization in that client NWDAF (Model Training Logical Function (MTLF)) resources may be used up by being included into many federated learning groups. The currently proposed solutions do not address this threat. Currently, the FL server can send a request to FL client(s) and consume their resources on a first come first served basis. There is no mechanism defined currently to define the resource authorization and limitations for a given FL server when sending a FL process request to the relevant FL clients. Embodiments will be described herein that define the resource authorization and limitations for a given FL server when sending a FL process request to the relevant FL clients. Further, these embodiments describe an authorization scheme that governs how FL servers from one vendor use computing resources of FL clients from another vendor.
[0040] For this purpose, the embodiments described herein implement an authorization mechanism in which the FL client may explicitly indicate the resource utilization (for example, in terms of central processing unit (CPU), graphics processing unit (GPU), Memory consumption, maximum allowed usage time, maximum number or NF instances, the number of epochs needed, the FL rounds etc.) for a given FL server and analytics identifier (ID).
[0041] As described above, there may be situations when multiple FL servers are requesting FL processes on FL clients, therefore only the FL servers authorized to consume the resources of the FL process should be allowed and serviced. Further, there may also be situations where a few analytics ID(s) have higher priority as compared to others, and therefore there is no mechanism to set priorities when FL process requests are received for a variety of different analytics ID(s).
[0042] FIG. 1 illustrates a portion of the 5G core network that provides network data analytics services. The 5G network is implemented using a Service-Based Architecture (SBA) where various software services may be implemented in a cloud computing environment. The SBA provides a modular framework from which common applications can be deployed using components of varying sources and suppliers. The 3GPP defines a SBA, whereby the control plane functionality and common data repositories of a 5G network are delivered by way of a set of interconnected Network Functions (NFs), each with authorization to access each other’s services. Assuming the role of either service consumer or service producer, NFs are self- contained, independent and reusable. Each NF service exposes its functionality through a Service Based Interface (SBI).
[0043] In FIG. 1 , the network is divided into a visited public land mobile network (VPLMN) and a home public land mobile network (HPLMN). The VPLMN includes Application Function (AF) 102, visited Security Edge Protection Proxy (vSEPP) 110, and other NFs 114. The AF 102 may act as the FL server as will be described further below. The Security Edge Protection Proxy (SEPP) enables secure interconnect between 5G networks. The SEPP ensures end-to-end confidentiality and / or integrity between source and destination network for all 5G interconnect roaming messages. The VPLMN may include other NFs 114 that perform various functions.
[0044] The HPLMN includes network repository function (NRF) 104, NWADF 106, unified data management (UDM) 108, home SEPP (hSEPP) 112, and other NFs 116. The SBA employs a centralized discovery framework that leverages the NRF 104. The NRF 104 is an authorization server that maintains a record of available NF instances and their supported services. It allows other NF instances to subscribe and be notified of registrations from NFinstances of a given type. The NRF 104 supports service discovery, by receipt of Discovery Requests from NF instances and details which NF instances support specific services.
[0045] The NWDAF 106 is a network function that collects data from 5G Core network functions, performs network analytics, and provides insights with closed loop automation to authorized data consumers. These include external users taking advantage of open application programming interfaces (APIs) to help generate greater insight into network performance. The NWDAF makes analytics available where needed to meet the varying latency requirements of 5G use cases. This approach to collecting, analyze, and expose data allows service providers to manage, automate, and optimize their 5G network operations much more efficiently. The NWDAF architecture is a cloud-native, multi-vendor capable, and probeless solution, making it easy to collect and analyze data from networks and services. The data collected and provided by the NWDAFs 106 may be used to train machine learning models using FL to model various aspects of the 5G network.
[0046] The UDM 108 is a converged repository of subscriber information used to service a number of NFs. The HPLMN may include other NFs 116 that perform various functions. The hSEPP 112 is a home SEPP. In FIG. 1 labelled dashed lines illustrate the various steps of an embodiment of an authorization mechanism that will be further described below.
[0047] FIG. 2 illustrates an implementation of a resource authorization mechanism in the 5G core. The 5G core may include a NWDAF FL server 202, NRF 204 (which may be an authorization server), and NWDAF MTLF FL clients 206. The NWDAF FL server 202 develops a machine learning model to model network analytics. The machine learning model at NWDAF FL server 202 is trained at the NWDAF MTLF FL clients 206 using analytics data available at the NWDAF MTLF FL clients 206.
[0048] The various steps carried out by the NWDAF FL server 202, NRF 204, and NWDAF MTLF FL clients 206 that implement the resource authorization mechanism 200 will now be described.
[0049] The resource authorization mechanism 200 begins with the NWDAF MTLF FL clients 206 registering their Network Function (NF) profile 208 including registration information. This registration information may include utilization information such as a maximum resource utilization (e.g., CPU, memory, and disk storage) to run FL process requests. These external resource utilization values may be specified per analytics ID, interoperability ID, vendor ID of the FL server, NF instance ID of the FL Server, regulatory constraints, number of FL servers already served, etc. That is maximum resource utilization limits may be placed per these different parameters. The analytics ID may identify a specific analytic or set of analytics thatare of interest. The interoperability ID may indicate that interoperability is generally allowed or may be a list of vendors where interoperability is allowed. The vender ID of the FL server identifies the vender of a specific FL server and may also include model and version information as well. As the NWDAF FL server 202 may carry out different network functions, each of these differently defined network functions may have a NF instance ID. The regulatory constraints may mean, for example, that an FL client in one jurisdiction cannot interact with a FL server in a second specific jurisdiction.
[0050] The registration information may also include execution time information that includes the maximum time to run the FL process requests or the availability time required to run the FL process. It is noted that a FL process may include several rounds of client / server interactions. Accordingly, the maximum and / or availability time to run the FL process requests could be for each specific interaction or for an aggregate of the first interaction until a process termination happens. These maximum and / or availability time to run the FL process requests may be specified per analytics ID, interoperability ID, vendor ID of the FL server, NF Instance ID of the FL Server, regulatory constraints, number of FL servers already served, etc.
[0051] The NWDAF MTLF FL clients 206 may also specify a total maximum time to run all FL processes and maximum resource utilization by all FL processes per analytics ID, vendor ID, NF Instance ID of the FL server, etc.
[0052] The utilization information may also include the geographical area of the NWDAF FL server 202. That is the geographic area that is served by the NWDAF FL server 202. Further, the utilization information may also include the maximum number of FL server instances from the same vendor allowed to use the FL client. This may prevent one vendor from taking all of the resources of the NWDAF MTLF FL clients 206. The utilization information may also include the maximum number of FL client instances from the same vendor used by one or more FL servers from the same vendor. Finally, the utilization information may include geographical area restrictions per analytics ID (i.e., for every given analytics ID that the NWDAF FL server 202 wishes to run the FL processes for, the geographical area of that FL server). Note various other information may also be used as utilization information.
[0053] Next, the NWDAF FL server 202 may initiate a discovery request 210 for potential NWDAF MTLF FL clients 206 to the NRF 204. For example, this request may request analytics data associated with specific analytics IDs. Then the NWDAF FL server 202 after discovering the relevant NWDAF MTLF FL clients 206 that may process requests sends an access token request to the NRF 212. The access token request also includes request utilization information such as the FL process running time required per analytics ID, max resourceconsumption, geographical area of NWDAF MTLF FL clients, etc. This request utilization information can then be matched to the capabilities of the different NWDAF MTLF FL clients 206 to see if they can handle the request.
[0054] Next, the NRF 204 authorizes the request of the NWDAF FL server 214 based upon the information registered in the NF profile in step 208 and the information provided in the access token request in step 212. This step can prevent requests from the NWDAF FL server 202 that would exceed the resource and run time limits of the NWDAF MTLF FL clients 206 and allows the NRF 204 to authorize requests that fit within the resource and run time limits of the NWDAF MTLF FL clients 206. Further, if the analytics IDs have associated priorities, then these priorities may be used to determine if requests should be authorized.
[0055] Once authorized the NRF 204 provides an access token with enhanced claims for resources 216. These enhanced claims for resources may include the total time for FL process, vendor ID, geographical area of NWDAF FL server, analytics ID, etc. If the NRF 204 is unable to authorize the request, the NRF 204 rejects the token request 218.
[0056] Next, the NWDAF FL server 202 sends the service request to NWDAF MTLF FL clients 206 with the access token(s) received earlier 220. This service request now also includes the total FL processing time and the maximum resource utilization in addition to FL model parameters, FL model ID, access token and analytics ID.
[0057] Finally, the NWDAF MTLF FL clients 206 verifies the access token(s), when the token is successfully verified the FL process is initialized 222. Also the NWDAF MTLF FL clients 206 may send back a response that the token has been successfully authorized.
[0058] In the resource authorization mechanism 200 the NWDAF MTLF FL clients 206 register the maximum resource utilization and time to run the FL process according to various parameters. The NRF 204 then uses this registration information to accept or reject FL requests from the NWDAF FL server 202. This resource authorization mechanism 200 thus can manage and limit the utilization of the NWDAF MTLF FL clients 206 to prevent overloading or exclusive use of the NWDAF MTLF FL clients 206.
[0059] FIG. 3 illustrates an exemplary hardware diagram 300 for implementing the authorization mechanism. The exemplary hardware 300 may correspond to NWDAF FL server 202, NRF 204, and / or NWDAF MTLF FL clients 206 of FIG. 2. As shown, the device 300 includes a processor 320, memory 330, user interface 340, network interface 350, and storage 360 interconnected via one or more system buses 310. It will be understood that FIG. 3 constitutes, in some respects, an abstraction and that the actual organization of the components of the device 300 may be more complex than illustrated.
[0060] The processor 320 may be any hardware device capable of executing instructions stored in memory 330 or storage 360 or otherwise processing data. As such, the processor may include a microprocessor, microcontroller, graphics processing unit (GPU), neural network processor, field programmable gate array (FPGA), application-specific integrated circuit (ASIC), or other similar devices.
[0061] The memory 330 may include various memories such as, for example LI, L2, or L3 cache or system memory. As such, the memory 330 may include static random-access memory (SRAM), dynamic RAM (DRAM), flash memory, read only memory (ROM), or other similar memory devices.
[0062] The user interface 340 may include one or more devices for enabling communication with a user such as an administrator. For example, the user interface 340 may include a display, a touch interface, a mouse, and / or a keyboard for receiving user commands. In some embodiments, the user interface 340 may include a command line interface or graphical user interface that may be presented to a remote terminal via the network interface 350.
[0063] The network interface 350 may include one or more devices for enabling communication with other hardware devices. For example, the network interface 350 may include a network interface card (NIC) configured to communicate according to the Ethernet protocol or other communications protocols, including wireless protocols. Additionally, the network interface 350 may implement a transmission control protocol / internet protocol (TCP / IP) stack for communication according to the TCP / IP protocols. Various alternative or additional hardware or configurations for the network interface 350 will be apparent.
[0064] The storage 360 may include one or more machine -readable storage media such as readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, or similar storage media. In various embodiments, the storage 360 may store instructions for execution by the processor 320 or data upon with the processor 320 may operate. For example, the storage 360 may store a base operating system 361 for controlling various basic operations of the hardware 300. Storage 362 may include instructions for implementing the resource authorization mechanism described herein.
[0065] It will be apparent that various information described as stored in the storage 360 may be additionally or alternatively stored in the memory 330. In this respect, the memory 330 may also be considered to constitute a “storage device” and the storage 360 may be considered a “memory.” Various other arrangements will be apparent. Further, the memory 330 and storage 360 may both be considered to be “non-transitory machine-readable media.” As used herein,the term “non-transitory” will be understood to exclude transitory signals but to include all forms of storage, including both volatile and non-volatile memories.
[0066] The system bus 310 allows communication between the processor 320, memory 330, user interface 340, storage 360, and network interface 350.
[0067] While the host device 300 is shown as including one of each described component, the various components may be duplicated in various embodiments. For example, the processor 320 may include multiple microprocessors that are configured to independently execute the methods described herein or are configured to perform steps or subroutines of the methods described herein such that the multiple processors cooperate to achieve the functionality described herein. Further, where the device 300 is implemented in a cloud computing system, the various hardware components may belong to separate physical systems. For example, the processor 320 may include a first processor in a first server and a second processor in a second server. Further, the authorization mechanism may be implemented using cloud computing to carry out the various functions described above.
[0068] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.
[0069] As used herein, the term “component” is intended to be broadly construed as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.
[0070] As used herein, satisfying a threshold may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and / or the like. It will be apparent that systems and / or methods described herein may be implemented in different forms of hardware, firmware, and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it being understood that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.
[0071] As used herein, the term “non-transitory machine -readable storage medium” will be understood to exclude a transitory propagation signal but to include all forms of volatile and non-volatile memory. When software is implemented on a processor, the combination of software and processor becomes a specific dedicated machine.
[0072] Because the data processing implementing the embodiments described herein is, for the most part, composed of electronic components and circuits known to those skilled in the art, circuit details will not be explained in any greater extent than that considered necessary as illustrated above, for the understanding and appreciation of the underlying concepts of the aspects described herein and in order not to obfuscate or distract from the teachings of the aspects described herein.
[0073] Unless stated otherwise, terms such as “first” and “second” are used to arbitrarily distinguish between the elements such terms describe. Thus, these terms are not necessarily intended to indicate temporal or other prioritization of such elements.
[0074] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative hardware embodying the principles of the aspects.
[0075] While each of the embodiments are described above in terms of their structural arrangements, it should be appreciated that the aspects also cover the associated methods of using the embodiments described above.
[0076] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. A phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a- b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
[0077] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two more more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0078] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and / or the like), and may be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and / or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
Claims
Claims:
1. An authorization server apparatus configured to implement a resource authorization mechanism for a federated learning (FL) training process, comprising: at least one processor; and at least one memory storing instructions, that when executed by the at least one processor, cause the apparatus at least to: receive from a first network device FL registration information including FL utilization information; receive an access token request from a second network device for the first network device that is a potential FL client including request utilization information; determine if the second network device is authorized for the first network device based upon the FL utilization information and the request utilization information; and send an access token for the first network device to the second network device when the access token request for the first network device is authorized.
2. The authorization server apparatus of claim 1, wherein the utilization information includes maximum resource utilization information.
3. The authorization server apparatus of claim 2, wherein the maximum resource utilization information includes processor throughput, memory, and storage space.
4. The authorization server apparatus of claim 1, wherein the utilization information includes maximum resource utilization information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
5. The authorization server apparatus of claim 1, wherein the utilization information includes at least one of a geographical area of the second network device, the maximum number of second network device instances from the same vendor allowed to use the FL client, the maximum number of FL client instances from the same vendor used by one or more second network devices from the same vendor, and geographical area restrictions per analytics ID.
6. The authorization server apparatus of claim 1, wherein the utilization information includes maximum FL process execution time information.
7. The authorization server apparatus of claim 1, wherein the utilization information includes maximum FL process execution time information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
8. The authorization server apparatus of claim 1, wherein the access token request includes at least one of a FL process execution time required per analytics ID, a maximum resource consumption, and a geographical area of the second network device.
9. The authorization server apparatus of claim 1, wherein the access token includes at least one of total FL process execution time and geographical area of the second network device.
10. The apparatus according to any of claims 1 to 9, wherein the authorization server is a network repository function (NRF), and the first and second network devices are a network data analytics function (NWDAF).
11. A federated learning (FL) client apparatus configured to implement a resource authorization mechanism for a FL training process, comprising: at least one processor; and at least one memory storing instructions, that when executed by the at least one processor, cause the apparatus at least to: send to an authorization server FL registration information including utilization information; receive a FL service request including an analytics ID, FL model parameters, and an access token from a second network device including utilization information; verifying the access token; and sending a success response indicating that the FL client will use its analytics data to train and update a FL machine learning model.
12. The FL client apparatus of claim 11, wherein the at least one memory stores instructions, that when executed by the at least one processor, cause the apparatus to: train the FL machine learning model using analytics data associated with the analytics ID to update FL machine learning model parameters; and send updated FL machine learning model parameters to the second network device.
13. The FL client apparatus of claim 11 wherein the utilization information includes maximum resource utilization information.
14. The FL client apparatus of claim 13, wherein the maximum resource utilization information includes processor throughput, memory, and storage space.
15. The FL client apparatus of claim 11, wherein the utilization information includes maximum resource utilization information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
16. The FL client apparatus of claim 11, wherein the utilization information includes at least one of a geographical area of the second network device, the maximum number of second network device instances from the same vendor allowed to use a FL client, the maximum number of FL client instances from the same vendor used by one or more second network devices from the same vendor, and geographical area restrictions per analytics ID.
17. The FL client apparatus of claim 11, wherein the utilization information includes maximum FL process execution information.
18. The FL client apparatus of claim 11, wherein the utilization information includes maximum FL process execution time information based on at least one of analytics identification (ID), interoperability ID, vender ID of the second network device, regulatory constraints, number of FL servers already served, and a network function instance ID of the second network device.
19. The apparatus according to any of claims 11 to 18, wherein the FL client is a network data analytics function (NWDAF).
20. A federated learning (FL) server apparatus configured to implement an authorization mechanism for a FL training process, comprising: at least one processor; at least one data storage; and at least one memory storing instructions, that when executed by the at least one processor, cause the apparatus at least to; send a discovery request to an authorization server; receive from the authorization server information regarding a potential FL client; send an access token request to the authorization server for the potential FL client including request utilization information; receive an access token for the FL client from the authorization server when access token request for the FL client is authorized; and sending a FL service request access token to the FL client including utilization information.
21. The FL server apparatus of claim 20, wherein the utilization information includes maximum resource utilization information.
22. The FL server apparatus of claim 21, wherein the maximum resource utilization information includes processor throughput, memory, and storage space.
23. The FL server apparatus of claim 20, wherein the utilization information includes maximum resource utilization information based on at least one of analytics identification (ID), interoperability ID, vender ID of the FL server, regulatory constraints, number of FL servers already served, and a network function instance ID of the FL server.
24. The FL server apparatus of claim 20, wherein the utilization information includes at least one of a geographical area of the FL server, the maximum number of FL server instances fromthe same vendor allowed to use a FL client, the maximum number of FL client instances from the same vendor used by one or more FL servers from the same vendor, and geographical area restrictions per analytics ID.
25. The FL server apparatus of claim 20, wherein the utilization information includes maximum FL process execution time information.
26. The FL server apparatus of claim 20, wherein the utilization information includes maximum FL process execution time information based on at least one of analytics identification (ID), interoperability ID, vender ID of the FL server, regulatory constraints, number of FL servers already served, and a network function instance ID of the FL server.
27. The apparatus according to any of claims 20 to 26, wherein the FL server is a network data analytics function (NWDAF).
