H04L41/042

Mesh network system comprising a plurality of interconnected individual mesh networks
11324074 · 2022-05-03 · ·

A mesh network system comprising at least a first mesh network controlled by a first central controlling unit CU and at least a second mesh network controlled by a second central controlling unit CU is disclosed. The at least first central controlling unit and the at least second central controlling unit is configured to communicate via an external network. Respective central controlling units CU are configured to facilitate interoperations between devices located in different mesh networks.

Methods for backing up virtual-machines
11323531 · 2022-05-03 · ·

A comprehensive approach to streaming backups for virtual machines (“VMs”) in a storage management system comprises improvements to the assignment of data agent proxies for VM secondary copy operations. New considerations in performing a VM streaming backup job include without limitation: determining and enforcing a system-wide per-proxy limit of concurrent data streams; generating an ordered priority list of the VMs to be backed up as a basis for choosing which proxies will back up the respective VM, though the illustrative system may not strictly adhere to the priority list based on further considerations; identifying a next available proxy based on data stream utilization at the proxy; and dynamically re-generating the priority list and re-evaluating considerations if some VMs become “stranded” due to a failure to be backed up. Secondary copy operations are distributed to proxies in ways that improve the chances of successfully completing VM streaming backups.

Methods for backing up virtual-machines
11323531 · 2022-05-03 · ·

A comprehensive approach to streaming backups for virtual machines (“VMs”) in a storage management system comprises improvements to the assignment of data agent proxies for VM secondary copy operations. New considerations in performing a VM streaming backup job include without limitation: determining and enforcing a system-wide per-proxy limit of concurrent data streams; generating an ordered priority list of the VMs to be backed up as a basis for choosing which proxies will back up the respective VM, though the illustrative system may not strictly adhere to the priority list based on further considerations; identifying a next available proxy based on data stream utilization at the proxy; and dynamically re-generating the priority list and re-evaluating considerations if some VMs become “stranded” due to a failure to be backed up. Secondary copy operations are distributed to proxies in ways that improve the chances of successfully completing VM streaming backups.

AUTOMATIC AND DYNAMIC ADAPTATION OF GROUPING IN A DATA PROCESSING SYSTEM

A system and method to adapt the grouping between a plurality of nodes in a data processing system. In one embodiment, a first leader node (320) in a data processing system (300) is configured to determine (815) a cost map within a first group of nodes (310), calculate (820) costs between the first leader node (320) and first member nodes (330) based on the cost map, determine (830) a candidate member node (330A) from the first member nodes (330), query (840) other leader nodes (350, 380) to accept a transfer of the candidate member node (330A), receive (850) a first transfer response from a second leader node (350) to accept the transfer to a second group of nodes (340), initiate (860) a transfer of and receive (865) an acknowledgement for the transfer of the candidate member node (330A) to the second group of nodes (340).

Configuration management for co-management

Various examples for discovering policy bindings between group policy rules in a legacy management framework and unified endpoint management rules that are utilized in a modern mobile device management (MDM) device management framework. A configuration state view can allow an administrator to understand inconsistencies or conflicts between group policy rules and UEM rules.

SERVER-MANAGEMENT MICROSERVICE STOREHOUSE FOR BASEBOARD MANAGEMENT CONTROLLERS

Techniques to facilitate the provision of server-management microservices for baseboard management controllers from a storehouse of such microservices are described herein. A technique described herein includes a server-management microservice storehouse obtaining a request for a server-management microservice for a baseboard management controller (BMC) of a server of a communications network. Further, the storehouse delivers the microservice to the BMC over the communication network. The server-management microservice is a modularized application that interacts with the operating system of the BMC while the microservice executes on the BMC, and the server-management microservice cause management of operations of the server or monitoring of the status of the server.

SYSTEM AND METHOD FOR DISTRIBUTED HOME AUTOMATION CONTROL
20210367838 · 2021-11-25 · ·

A distributed home automation system and method for control of devices located in rooms of a home that is divided into regions includes plural devices located in the rooms, with a first device located in a first room, and a second device located in a second room. The system includes a network of regional controllers in communication with each device and with each regional controller in the network. Each regional controller is configured to control only a preselected number of devices that is less than all of the devices. The system includes plural regional controllers configured to control less than all of the devices in all of the rooms. The network is also configured to allow the regional controllers automatically to configure or reconfigure each other, automatically and remotely.

Self-optimizing fabric architecture and self-assembling network

A controller associated with a domain includes a network interface; one or more processors communicatively coupled to the network interface; and memory storing instructions that, when executed, cause the one or more processors to communicate with one or more additional controllers via the network interface, wherein each of the one or more additional controllers is in one or more additional domains, and wherein each domain provides different characteristics, utilize at least part of a control pattern to obtain requirements for a service, and cause, utilizing any of a peer relationship and a hierarchical relationship with the one or more additional controllers, at least part of implementation of a composition of resources to meet the requirements for the service, wherein the composition defines the resources provided in each domain for the service, and wherein the composition is based on the requirements and the different characteristics in each domain.

Control network planning

Example implementations described herein generate plans for the deployment of functions involving the distribution function and the allocation of network resources based on the requirements of the distributed functions on the control system and the network information constituting the control system. Example implementations involve gathering requirements of the distributed functions constituting the distributed control system, information of the network, and information of the plurality of communication devices, and generating a plan for deployment of the distributed functions to corresponding ones of the plurality of communications devices and allocation of network resources to the corresponding ones of the plurality of communication devices based on the gathered requirements and the information of the network.

Multi-Domain Orchestration

A first orchestrator (20-1) for a first domain (10-1) is configured for multi-domain orchestration. The first orchestrator (20-1) receives an inbound orchestration request (22) that requests orchestration of one or more inbound targets (24) and that includes one or more records (26). The one or more records (26) either indicate an ancestry of each of the one or more inbound targets (24) or indicate an ancestry of the inbound orchestration request (22). The first orchestrator (20-1), based on the one or more records (26) included in the inbound orchestration request (22), evaluating whether or not to send from the first domain (10-1) to a second domain (10-2) an outbound orchestration request (28) that requests orchestration of an outbound target (30). The outbound target (30) is one of, or is a descendant of at least one of, the one or more inbound targets (24). The first orchestrator (20-1) then sends or does not send the outbound orchestration request (28) from the first domain (10-1) to the second domain (10-2) depending on the evaluation.