Patent Application
20230385708
The present disclosure relates generally to computer networks, and, more particularly, to reconciling computing infrastructure and data in federated learning.
Machine learning is becoming increasingly ubiquitous in the field of computing. Indeed, machine learning is now used across a wide variety of use cases, from analyzing sensor data from sensor systems to performing future predictions for controlled systems. As machine learning techniques continue to mature, it is expected that the uses for machine learning will continue to grow.
The performance of a machine learning model is largely dependent on the quality of the data on which the model is trained. Complicating the collection of ‘good’ training data, though, are data privacy policies and regulations that place restrictions on the sharing of data that could be used to train a machine learning model. Federated learning presents a potential solution to these challenges, as it allows for training to be performed on-site, negating the need to export the data for model training.
Thus, to implement federated learning, learning tasks are deployed to compute nodes located at the various sites at which training is to be performed. Today, this is a largely manual process that is prone to errors and very difficult to scale. In a simple case, a learning task is configured on a compute node that also stores the training data used for the task. However, this is often not the case and the training data also needs to be moved to the on-site compute node, which also needs to be performed manually.
The embodiments herein may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identically or functionally similar elements, of which:
According to one or more embodiments of the disclosure, a controller for a federated learning system represents computing infrastructure for the federated learning system as a tree structure. The controller forms associations between datasets available to the federated learning system and nodes in the tree structure. The controller receives one or more instructions to perform model training in the federated learning system with datasets specified using their associations. The controller configures, in response to the one or more instructions, the federated learning system to perform the model training using the datasets specified by the one or more instructions using the tree structure.
A computer network is a geographically distributed collection of nodes interconnected by communication links and segments for transporting data between end nodes, such as personal computers and workstations, or other devices, such as sensors, etc. Many types of networks are available, with the types ranging from local area networks (LANs) to wide area networks (WANs). LANs typically connect the nodes over dedicated private communications links located in the same general physical location, such as a building or campus. WANs, on the other hand, typically connect geographically dispersed nodes over long-distance communications links, such as common carrier telephone lines, optical lightpaths, synchronous optical networks (SONET), or synchronous digital hierarchy (SDH) links, or Powerline Communications (PLC) such as IEEE 61334, IEEE P1901.2, and others. The Internet is an example of a WAN that connects disparate networks throughout the world, providing global communication between nodes on various networks. The nodes typically communicate over the network by exchanging discrete frames or packets of data according to predefined protocols, such as the Transmission Control Protocol/Internet Protocol (TCP/IP). In this context, a protocol consists of a set of rules defining how the nodes interact with each other. Computer networks may be further interconnected by an intermediate network node, such as a router, to extend the effective “size” of each network.
Smart object networks, such as sensor networks, in particular, are a specific type of network having spatially distributed autonomous devices such as sensors, actuators, etc., that cooperatively monitor physical or environmental conditions at different locations, such as, e.g., energy/power consumption, resource consumption (e.g., water/gas/etc. for advanced metering infrastructure or “AMI” applications) temperature, pressure, vibration, sound, radiation, motion, pollutants, etc. Other types of smart objects include actuators, e.g., responsible for turning on/off an engine or perform any other actions. Sensor networks, a type of smart object network, are typically shared-media networks, such as wireless or PLC networks. That is, in addition to one or more sensors, each sensor device (node) in a sensor network may generally be equipped with a radio transceiver or other communication port such as PLC, a microcontroller, and an energy source, such as a battery. Often, smart object networks are considered field area networks (FANs), neighborhood area networks (NANs), personal area networks (PANs), etc. Generally, size and cost constraints on smart object nodes (e.g., sensors) result in corresponding constraints on resources such as energy, memory, computational speed and bandwidth.
In some implementations, a router or a set of routers may be connected to a private network (e.g., dedicated leased lines, an optical network, etc.) or a virtual private network (VPN), such as an MPLS VPN thanks to a carrier network, via one or more links exhibiting very different network and service level agreement characteristics. For the sake of illustration, a given customer site may fall under any of the following categories:
Servers 152-154 may include, in various embodiments, a network management server (NMS), a dynamic host configuration protocol (DHCP) server, a constrained application protocol (CoAP) server, an outage management system (OMS), an application policy infrastructure controller (APIC), an application server, etc. As would be appreciated, network 100 may include any number of local networks, data centers, cloud environments, devices/nodes, servers, etc.
In some embodiments, the techniques herein may be applied to other network topologies and configurations. For example, the techniques herein may be applied to peering points with high-speed links, data centers, etc.
According to various embodiments, a software-defined WAN (SD-WAN) may be used in network 100 to connect local network 160, local network 162, and data center/cloud environment 150. In general, an SD-WAN uses a software defined networking (SDN)-based approach to instantiate tunnels on top of the physical network and control routing decisions, accordingly. For example, as noted above, one tunnel may connect router CE-2 at the edge of local network 160 to router CE-1 at the edge of data center/cloud environment 150 over an MPLS or Internet-based service provider network in backbone 130. Similarly, a second tunnel may also connect these routers over a 4G/5G/LTE cellular service provider network. SD-WAN techniques allow the WAN functions to be virtualized, essentially forming a virtual connection between local network 160 and data center/cloud environment 150 on top of the various underlying connections. Another feature of SD-WAN is centralized management by a supervisory service that can monitor and adjust the various connections, as needed.
The network interfaces 210 include the mechanical, electrical, and signaling circuitry for communicating data over physical links coupled to the network 100. The network interfaces may be configured to transmit and/or receive data using a variety of different communication protocols. Notably, a physical network interface 210 may also be used to implement one or more virtual network interfaces, such as for virtual private network (VPN) access, known to those skilled in the art.
The memory 240 comprises a plurality of storage locations that are addressable by the processor(s) 220 and the network interfaces 210 for storing software programs and data structures associated with the embodiments described herein. The processor 220 may comprise necessary elements or logic adapted to execute the software programs and manipulate the data structures 245. An operating system 242 (e.g., the Internetworking Operating System, or IOS®, of Cisco Systems, Inc., another operating system, etc.), portions of which are typically resident in memory 240 and executed by the processor(s), functionally organizes the node by, inter alia, invoking network operations in support of software processors and/or services executing on the device. These software processors and/or services may comprise federated learning control process 248, as described herein, any of which may alternatively be located within individual network interfaces.
It will be apparent to those skilled in the art that other processor and memory types, including various computer-readable media, may be used to store and execute program instructions pertaining to the techniques described herein. Also, while the description illustrates various processes, it is expressly contemplated that various processes may be embodied as modules configured to operate in accordance with the techniques herein (e.g., according to the functionality of a similar process). Further, while processes may be shown and/or described separately, those skilled in the art will appreciate that processes may be routines or modules within other processes.
In various embodiments, as detailed further below, federated learning control process 248 may also include computer executable instructions that, when executed by processor(s) 220, cause device 200 to perform the techniques described herein. To do so, in some embodiments, federated learning control process 248 may utilize machine learning. In general, machine learning is concerned with the design and the development of techniques that take as input empirical data (such as network statistics and performance indicators), and recognize complex patterns in these data. One very common pattern among machine learning techniques is the use of an underlying model M, whose parameters are optimized for minimizing the cost function associated to M, given the input data. For instance, in the context of classification, the model M may be a straight line that separates the data into two classes (e.g., labels) such that M=a*x+b*y+c and the cost function would be the number of misclassified points. The learning process then operates by adjusting the parameters a,b,c such that the number of misclassified points is minimal. After this optimization phase (or learning phase), the model M can be used very easily to classify new data points. Often, M is a statistical model, and the cost function is inversely proportional to the likelihood of M, given the input data.
In various embodiments, federated learning control process 248 may employ, or be responsible for the deployment of, one or more supervised, unsupervised, or semi-supervised machine learning models. Generally, supervised learning entails the use of a training set of data, as noted above, that is used to train the model to apply labels to the input data. For example, the training data may include sample image data that has been labeled as depicting a particular condition or object. On the other end of the spectrum are unsupervised techniques that do not require a training set of labels. Notably, while a supervised learning model may look for previously seen patterns that have been labeled as such, an unsupervised model may instead look to whether there are sudden changes or patterns in the behavior of the metrics. Semi-supervised learning models take a middle ground approach that uses a greatly reduced set of labeled training data.
Example machine learning techniques that federated learning control process 248 can employ, or be responsible for deploying, may include, but are not limited to, nearest neighbor (NN) techniques (e.g., k-NN models, replicator NN models, etc.), statistical techniques (e.g., Bayesian networks, etc.), clustering techniques (e.g., k-means, mean-shift, etc.), neural networks (e.g., reservoir networks, artificial neural networks, etc.), support vector machines (SVMs), logistic or other regression, Markov models or chains, principal component analysis (PCA) (e.g., for linear models), singular value decomposition (SVD), multi-layer perceptron (MLP) artificial neural networks (ANNs) (e.g., for non-linear models), replicating reservoir networks (e.g., for non-linear models, typically for time series), random forest classification, or the like.
Unfortunately, running a machine learning workload is a complex and cumbersome task, today. This is because expressing a machine learning workload is not only tightly coupled with infrastructure resource management, but also embedded into the machine learning library that supports the workload. Consequently, users responsible for machine learning workloads are often faced with time-consuming source code updates and error-prone configuration updates in an ad-hoc fashion for different types of machine learning workloads, which may be used to perform tasks such as aggregated model training, performing inferences on a certain dataset, or the like. However, defining a machine learning workload, especially across a distributed set of nodes/sites, can also be a very cumbersome and error-prone task.
To simplify the definition of a workload, the techniques herein propose decomposing machine learning workloads into primitives/building blocks and decoupling core building blocks (e.g., the AI/ML algorithm) of the workload from the infrastructure building blocks (e.g., network connectivity and communication topology). The infrastructure building blocks are abstracted so that the users can compose their workloads in a simple and declarative manner. In addition, scheduling the workloads is straightforward and foolproof, using the techniques herein.
In various embodiments, the techniques herein propose representing a machine learning workload using the following building block types:
Roles and channels may also have various properties associated with them, to control the provisioning of a machine learning workload. In some embodiments, these properties may be categorized as predefined ones and extended ones. Predefined properties may be essential to support the provisioning and set by default, whereas extended properties may be user-defined. In other words, to enrich the functionality of the roles and channels, the user engineer may opt to customize extended properties.
By way of example, a role may have either or both of the following pre-defined properties:
For a channel, there may be the following property:
Using the above building blocks and properties, the system can greatly simplify the process for defining a machine learning workload for a user.
As shown, workload design template 300 consists of three roles: machine learning (ML) model trainer 302, intermediate model aggregator 304, and global model aggregator 306. Connecting them in template 300 may be three types of channels: trainer channel 308, parameter channel 310, and aggregation channel 312.
Trainer channels allows communication between peer trainer nodes at runtime. For instance, assume that the group by property is set to group trainer nodes into separate groups located in the western U.S. and the UK. In such a case, trainer channels may be provisioned between these nodes. Similarly, a parameter channel may enable communications between intermediate model aggregators, such as intermediate model aggregator 304 and trainer nodes in the various groups, such as model trainer 302. Finally, an aggregation channel may connect the intermediate model aggregator to global model aggregator 306.
To provision the machine learning workload across the different hospitals, a user may convey, via a user interface, definition data for the workload. For instance, the user may specify the type of model to be trained, values for the replica property, the number of datasets to use, tags for the group by property, any values for the load balancing property, combinations thereof, or the like.
Based on the definition data, the system may identify that the needed training datasets are located at nodes 402a-402e (e.g., the different hospitals). Note that the user does not need to know where the data is located during the design phase for machine learning workload 400, as the system may automatically identify nodes 402a-402e, automatically, using an index of their available data. In turn, the system may designate each of nodes 402a-402e as having training roles, meaning that each one is to train a machine learning model in accordance with the definition data and using its own local training dataset. In other words, once the system has identified nodes 402a-402e as each having training datasets matching the requisite type of data for the training, the system may provision and configure each of these nodes with a trainer role.
Assume now that the group by property has been set to group nodes 402a-402e by their geographic locations. Consequently, nodes 402a-402c may be grouped into a first group of trainer/training nodes, based on these hospitals all being located in the western US, by being tagged with a “us_west” tag. Similarly, nodes 402d-402e may be grouped into a second group of training nodes, based on these hospitals being located in the UK, by being tagged with a “uk tag.
For purposes of simplifying this example, also assume that the replica property is set to 1, by default, meaning that there is only one trainer role instance to be configured at each of nodes 402a-402e.
To connect the different sites/nodes 402a-402e in each group, the system may also provision and configure trainer channels between the nodes in each group. For instance, the system may configure trainer channels 408a between nodes 402a-402c within the first geographic group of nodes, as well as a trainer channel 408b between nodes 402d-402e in the second geographic group of nodes.
Once the system has identified nodes 402a-402e, it may also identify intermediate model aggregator nodes 404a-404b, to support the groups of nodes 402a-402c and 402d-402e, respectively. In turn, the system may configure model aggregator nodes 404a-404b with intermediate model aggregation roles. In addition, the system may configure parameter channels 410a-410b to connect the groups of nodes 402a-402c and 402d-402e with intermediate model aggregator nodes 404a-404b, respectively. These parameter channels 410a-410b, like their respective groups of nodes 402, may be tagged with the ‘us_west’ and ‘uk’ tags, respectively. In some instances, intermediate model aggregator nodes 404a-404b may be selected based on their distances or proximities to their assigned nodes among nodes 402a-402e. For instance, intermediate model aggregator node 404b may be cloud-based and selected based on it being in the same geographic region as nodes 402d-402e, Indeed, intermediate model aggregator node 404a may be provisioned in the Google cloud (gcp) in the western US, while intermediate model aggregator node 404b may be provisioned in the Amazon cloud (AWS) in the UK region.
During execution, each trainer node 402a-402e may train a machine learning model using its own local training dataset. In turn, nodes 402a-402e may send the parameters of these trained models to their respective intermediate model aggregator nodes 404a-404b via parameter channels 410a-410b. Using these parameters, each of intermediate model aggregator nodes 404a-404b may form an aggregate machine learning model. More specifically, intermediate model aggregator node 404a may aggregate the models trained by nodes 402a-402c into a first intermediate model and intermediate model aggregator node 404h may aggregate the models trained by nodes 402d-402e into a second aggregate model.
Finally, the system may also provision machine learning workload 400 in part by selecting and configuring global model aggregator node 406. Here, the system may configure a global aggregation role to global model aggregator node 406 and configure aggregation channels 412 that connect it to intermediate model aggregator nodes 404a-404b. Note that these aggregation channels may not be tagged with a geographic tag, either.
Once configured and provisioned, intermediate model aggregator nodes 404a-404b may send the parameters for their respective intermediate models to global model aggregator node 406 via aggregation channels 412. In turn, global model aggregator node 406 may use these model parameters to form a global, aggregated machine learning model that can then be distributed for execution. As a result of the provisioning by the system, the resulting global model will be based on the disparate training datasets across nodes 402a-402e, and in a way that greatly simplifies the definition process of the machine learning workload used to train the model.
As noted above, configuring a learning node in a federated learning system to perform model training using a particular dataset is a largely manual process that is prone to errors and very difficult to scale. In a simple case, a learning task is configured on a compute node that also stores the training data used for the task. However, this is often not the case and the training data also needs to be moved to the on-site compute node, which also needs to be performed manually.
The techniques introduced herein allow for the storage of information about the various datasets and computing infrastructures available in a federated learning deployment. In some aspects, this is done in a hierarchical manner (e.g., using a tree structure) that also integrates location information, allowing for the automated provisioning of federated learning tasks in a manner that complies with the various data sovereignty and privacy rules applicable to the available datasets.
Illustratively, the techniques described herein may be performed by hardware, software, and/or firmware, such as in accordance with federated learning control process 248, which may include computer executable instructions executed by the processor 220 (or independent processor of interfaces 210) to perform functions relating to the techniques described herein.
Specifically, according to various embodiments, a controller for a federated learning system represents computing infrastructure for the federated learning system as a tree structure. The controller forms associations between datasets available to the is federated learning system and nodes in the tree structure. The controller receives one or more instructions to perform model training in the federated learning system with datasets specified using their associations. The controller configures, in response to the one or more instructions, the federated learning system to perform the model training using the datasets specified by the one or more instructions using the tree structure.
Operationally, the techniques herein propose a systematic way of reconciling computing infrastructure and available datasets in a federated learning system. In various embodiments, the techniques herein propose two primary components: 1.) an infrastructure registry that stores information about the computing infrastructure of the federated learning system that could be leveraged to perform a learning task and 2.) a metadata database that stores information about the various datasets available to the federated learning system.
As shown, the tree structure may include any or all of the following types of nodes that are interconnected with one another:
By representing the computing infrastructure in infrastructure registry 500 using a tree structure, this allows for the relationships between the computing infrastructure to be stored and represented, as well. For example, as shown in
In various embodiments, portions of the tree structure store in infrastructure registry 500 can be referenced in a manner similar to a file system. For instance, root node 502 may be represented by the character ‘/.’ Similarly, the path “/europe/uk/org3” may be used to reference the infrastructure of org3 located in the U.K. in Europe.
For example, metadata database 600 may comprise any number of entries 602, such as entries 602a-602d shown, each of which represents a different dataset. In some embodiments, each dataset may have a unique identifier stored in its respective entry 602 in metadata database 600. In addition, each entry 602 may store the URL or other address of the dataset, a name for the dataset, or other such information.
According to various embodiments, another concept introduced herein is referred to as a ‘realm,’ which may also be stored in a given entry 602 in metadata database 600 and represents the boundary for access to the corresponding dataset. In various embodiments, such a realm may take the form of an association to a point in the tree structure in infrastructure registry 500. For instance, the format of a realm may be: [<infrastructure ID>|<location path>], meaning that either an infrastructure ID (e.g., an identifier for an infrastructure node in the tree structure) or a location path (e.g., a branch in the tree structure) may be used to define the access boundary.
For instance, consider a dataset whose unique identifier is 12345 and is represented in metadata database 600 by entry 602a. The dataset has a realm specified as “org1,” which is an infrastructure ID. On the other hand, in entry 602b, the realm of the dataset having a unique identifier of 67890 is set to “/na/us,” which represents a location is path.
In case of entry 602a, the dataset is only accessible and processed within the computing infrastructure of org1. Usually, any access to an internal infrastructure and resources (e.g., data) in it is strictly controlled, such as via security policies and firewall rules. Hence, a dataset owner is only responsible for ensuring that dataset is accessible within the internal infrastructure.
In contrast, in entry 602c, because the realm of the dataset is a location path (i.e., “/na/us”), and not tied to a specific organization's infrastructure, the dataset may be a public one and can be accessed by any device in any infrastructure (e.g., public cloud) within the specified location path. Unlike private datasets whose realm is an infrastructure ID, enforcing this type of realm is weak, meaning that the system abides by the realm set by the location path (e.g., united states in this case), but it is still possible for the dataset to be accessed outside the U.S., since it has a public URL. In addition, the root (e.g., represented as simply “I”) may be specified as the realm for any public datasets that are globally accessible.
In various embodiments, the associations between the tree structure in infrastructure registry 500 and the various datasets represented in metadata database 600 allows for instructions for the federated learning system to be specified in a simplified manner. For example,
As shown in
In turn, the controller may configure the respective infrastructure of the federated learning system to perform the model training. Here, since the groupby instruction value, “/europe” contains the realm “/europe/fr/org2,” the trainer using this configuration will be grouped by the label “/europe.” Similarly, the groupby value “/na/us” contains the realm “/na/us/west/ca/org1,” so the corresponding trainer will be grouped by the label “/na/us.”
Note previously in
At step 915, as detailed above, the controller may form associations between datasets available to the federated learning system and nodes in the tree structure. In some embodiments, the associations restrict where the datasets available to the federated learning system may be used for model training. In one embodiment, the datasets available in the federated learning system include at least one public dataset whose association is with a root node of the tree structure. In addition, in some embodiments, the controller may also assign unique identifiers to the datasets available in the federated learning system.
At step 920, the controller may receive one or more instructions to perform model training in the federated learning system with datasets specified using their associations, is as described in greater detail above. In some embodiments, a particular instruction in the one or more instructions to perform the model training indicates that model training results from two or more of the datasets should be grouped. In one embodiment, the particular instruction specifies a location path in the tree structure.
At step 925, as detailed above, the controller may the federated learning system to perform the model training using the datasets specified by the one or more instructions using the tree structure, in response to the one or more instructions. In some embodiments, the controller may do so by configuring a particular device in the computing infrastructure to aggregate the model training results from those two or more of the datasets to be grouped. In various embodiments, the model training in the federated learning system using the datasets specified by the one or more instructions.
It should be noted that while certain steps within procedure 900 may be optional as described above, the steps shown in
The techniques described herein, therefore, allow for the simplified configuration of workloads in a federated learning system, such as model training tasks. By representing the computing infrastructure of the federated learning system as a tree structure, and forming associations between the available datasets and that tree structure, aggregation tasks can be configured in a simplified manner. In addition, these associations also allow for restrictions to be placed on the datasets in terms of where and how they may be used by the federated learning system.
While there have been shown and described illustrative embodiments that provide for reconciling computing infrastructure and data in federated learning, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the embodiments herein. For example, while certain embodiments are is described herein with respect to machine learning workloads directed towards model training, the techniques herein are not limited as such and may be used for other types of machine learning tasks, such as making inferences or predictions, in other embodiments. In addition, while certain protocols are shown, other suitable protocols may be used, accordingly.
The foregoing description has been directed to specific embodiments. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. For instance, it is expressly contemplated that the components and/or elements described herein can be implemented as software being stored on a tangible (non-transitory) computer-readable medium (e.g., disks/CDs/RAM/EEPROM/etc.) having program instructions executing on a computer, hardware, firmware, or a combination thereof. Accordingly, this description is to be taken only by way of example and not to otherwise limit the scope of the embodiments herein. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the embodiments herein.
