Artificial intelligence (ai) powered data integration in multi-controller environments

Abstract

This disclosure describes techniques and mechanisms for a system to integrate data from multiple controllers such that a user may manage and/or have visibility to the multiple controllers from a single management platform and/or dashboard. For example, each of the multiple controllers may be associated with a large language model (LLM) that may be trained on a functionality associated with the controller, as well as the structure of the user interface associated with the controller. Using data associated with the secondary controller and output by the LLM of the secondary controller, the data may be used by the primary controller and the LLM of the primary controller such that data of the secondary controller (e.g., command data and/or user interface data) may be integrated with data of the primary controller (e.g., command data and/or user interface data) at a single controller management system and/or dashboard.

What is claimed is: 
     
         1 . A system comprising:
 one or more processors; and   one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:   receiving, at a multi-controller management platform, user input selecting a first controller and a second controller, wherein the first controller is associated with a first large language model (LLM) and the second controller is associated with a second LLM;   receiving, from the second LLM, a first indication of a first workflow associated with the first controller, wherein the first indication is based at least in part on the first workflow and second UI attributes of the second controller;   generating, at the multi-controller management platform, a representation including the first indication and a second indication of a second workflow associated with the second controller; and   causing display of the representation at a user interface associated with the second controller.   
     
     
         2 . The system of  claim 1 , wherein the user input is first user input, the operations further comprising:
 receiving second user input selecting the second controller and a third controller, wherein the third controller is associated with a third LLM;   receiving, from the second LLM, a third indication of a third workflow associated with the third controller, wherein the third indication is based at least in part on the second workflow and the second UI attributes of the second controller;   generating, at the multi-controller management platform, a representation including the first indication, the second indication, and the third indication; and   causing display of the representation at the user interface associated with the second controller.   
     
     
         3 . The system of  claim 1 , wherein:
 the first LLM is trained to determine workflows associated with the first controller based at least in part on attributes associated with the first controller; and   the second LLM is trained to determine workflows associated with the second controller based at least in part on attributes associated with the second controller.   
     
     
         4 . The system of  claim 3 , wherein the second LLM is trained to determine conflicts between workflows associated with the first controller and workflows associated with the second controller, the operations further comprising:
 determining, by the second LLM, a conflict between the first workflow and the second workflow; and   retraining the second LLM to determine the workflows associated with the second controller based at least in part on the conflict.   
     
     
         5 . The system of  claim 3 , wherein the attributes associated with the first controller and attributes associated with the second controller include at least one of:
 a functionality associated with the first controller;   a functionality associated with the second controller;   UI semantic data associated with the first controller; or   UI semantic data associated with the second controller.   
     
     
         6 . The system of  claim 1 , wherein the first workflow further includes at least one of:
 access rights associated with a user of the first controller; or   application programming interface (API) commands associated with the first controller.   
     
     
         7 . The system of  claim 6 , wherein the user input is first user input, the operations further comprising:
 receiving, at the user interface associated with the second controller, second user input selecting a command associated with a functionality of the first controller;   sending, by the second controller and to the first controller, and based at least in part on the access rights and the API commands associated with the first controller, command data indicating the command;   receiving, at the second controller and from the first controller, output data responsive to the command data; and   based at least in part on the output data, updating the representation.   
     
     
         8 . A method for multi-controller management, the method comprising:
 receiving, at a multi-controller management platform, user input selecting a first controller and a second controller, wherein the first controller is associated with a first large language model (LLM) and the second controller is associated with a second LLM;   receiving, from the first LLM, workflow data including a first workflow of the first controller and first user interface (UI) attributes of the first workflow, wherein the first UI attributes are associated with the first controller;   receiving, from the second LLM, a first indication of the first workflow, wherein the first indication is based at least in part on the workflow data and second UI attributes of the second controller;   generating, at the multi-controller management platform, a representation including the first indication and a second indication of a second workflow associated with the second controller; and   causing display of the representation at a user interface associated with the second controller.   
     
     
         9 . The method of  claim 8 , wherein the user input is first user input, the workflow data is first workflow data, the method further comprising:
 receiving second user input selecting the second controller and a third controller, wherein the third controller is associated with a third LLM;   receiving, from the third LLM, second workflow data indicating a third workflow of the third controller and third UI attributes of the third workflow, wherein the third UI attributes are associated with the third controller;   receiving, from the second LLM, a third indication of the third workflow, wherein the third indication is based at least in part on the second workflow data and the second UI attributes of the second controller;   generating, at the multi-controller management platform, a representation including the first indication, the second indication, and the third indication; and   causing display of the representation at the user interface associated with the second controller.   
     
     
         10 . The method of  claim 8 , wherein:
 the first LLM is trained to determine workflows associated with the first controller based at least in part on attributes associated with the first controller; and   the second LLM is trained to determine workflows associated with the second controller based at least in part on attributes associated with the second controller.   
     
     
         11 . The method of  claim 10 , wherein the second LLM is trained to determine conflicts between workflows associated with the first controller and workflows associated with the second controller, the method further comprising:
 determining, by the second LLM, a conflict between the first workflow and the second workflow; and   retraining the second LLM to determine the workflows associated with the second controller based at least in part on the conflict.   
     
     
         12 . The method of  claim 10 , wherein the attributes associated with the first controller and attributes associated with the second controller include at least one of:
 a functionality associated with the first controller;   a functionality associated with the second controller;   UI semantic data associated with the first controller; or   UI semantic data associated with the second controller.   
     
     
         13 . The method of  claim 8 , wherein the workflow data further includes at least one of:
 access rights associated with a user of the first controller; or   application programming interface (API) commands associated with the first controller.   
     
     
         14 . The method of  claim 13 , wherein the user input is first user input, the method further comprising:
 receiving, at the user interface associated with the second controller, second user input selecting a command associated with a functionality of the first controller;   sending, by the second controller and to the first controller, and based at least in part on the access rights and the API commands associated with the first controller, command data indicating the command;   receiving, at the second controller and from the first controller, output data responsive to the command data; and   based at least in part on the output data, updating the representation.   
     
     
         15 . One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
 receiving, at a multi-controller management platform, user input selecting a first controller and a second controller, wherein the first controller is associated with a first large language model (LLM) and the second controller is associated with a second LLM;   receiving, from the first LLM, workflow data including a first workflow of the first controller and first user interface (UI) attributes of the first workflow, wherein the first UI attributes are associated with the first controller;   receiving, from the second LLM, a first indication of the first workflow, wherein the first indication is based at least in part on the workflow data and second UI attributes of the second controller;   generating, at the multi-controller management platform, a representation including the first indication and a second indication of a second workflow associated with the second controller; and   causing display of the representation at a user interface associated with the second controller.   
     
     
         16 . The one or more non-transitory computer-readable media of  claim 15 , wherein the user input is first user input, the workflow data is first workflow data, the operations further comprising:
 receiving second user input selecting the second controller and a third controller, wherein the third controller is associated with a third LLM;   receiving, from the third LLM, second workflow data indicating a third workflow of the third controller and third UI attributes of the third workflow, wherein the third UI attributes are associated with the third controller;   receiving, from the second LLM, a third indication of the third workflow, wherein the third indication is based at least in part on the second workflow data and the second UI attributes of the second controller;   generating, at the multi-controller management platform, a representation including the first indication, the second indication, and the third indication; and   causing display of the representation at the user interface associated with the second controller.   
     
     
         17 . The one or more non-transitory computer-readable media of  claim 15 , wherein:
 the first LLM is trained to determine workflows associated with the first controller based at least in part on attributes associated with the first controller; and   the second LLM is trained to determine workflows associated with the second controller based at least in part on attributes associated with the second controller.   
     
     
         18 . The one or more non-transitory computer-readable media of  claim 17 , wherein the second LLM is trained to determine conflicts between workflows associated with the first controller and workflows associated with the second controller, the operations further comprising:
 determining, by the second LLM, a conflict between the first workflow and the second workflow; and   retraining the second LLM to determine the workflows associated with the second controller based at least in part on the conflict.   
     
     
         19 . The one or more non-transitory computer-readable media of  claim 17 , wherein the attributes associated with the first controller and attributes associated with the second controller include at least one of:
 a functionality associated with the first controller;   a functionality associated with the second controller;   UI semantic data associated with the first controller; or   UI semantic data associated with the second controller.   
     
     
         20 . The one or more non-transitory computer-readable media of  claim 15 , wherein the user input is first user input, the operations further comprising:
 receiving, at the user interface associated with the second controller, second user input selecting a command associated with a functionality of the first controller;   sending, by the second controller and to the first controller, and based at least in part on access rights associated with a user of the first controller and application programming interface (API) commands associated with the first controller, command data indicating the command;   receiving, at the second controller and from the first controller, output data responsive to the command data; and   based at least in part on the output data, updating the representation.