Patent classifications
H04L47/78
System for automated cross-network monitoring of computing hardware and software resources
A system is provided for automated cross-network monitoring of computing hardware and software status. In particular, the system may track the status of various computing resources using process automation-based operations to simulate calls made by users to the various resources that the users are authorized to access. Based on said operations, the system may assess whether the authorized pathways to the resources and/or their respective components are properly functioning by capturing information regarding the resource, its associated components, and the current status of the resource. The results of these operations may be aggregated to provide an overview of which resources and/or systems are functioning and which are not. In this way, the system may provide a detailed view of the statuses of the individual resources and components within an entity's complex computing network.
Cluster capacity management for hyper converged infrastructure updates
Disclosed are various implementations of cluster capacity management for infrastructure updates. In some examples, cluster hosts for a cluster can be scheduled for an update. A component of a datacenter level resource scheduler can analyze cluster specific resource usage data to identify a cluster scaling decision for the cluster. The datacenter level resource scheduler transmits an indication that the resource scheduler is successfully invoked. Cluster hosts can then be updated.
Redirection mechanism to support network sharing/slicing with CU-DU split
Systems and methods for redirecting Radio Resource Control (RRC) messages in a wireless system that uses Central Unit (CU)/Distributed Unit (DU) splitting and either network sharing or network slicing are disclosed. In some embodiments, a method performed by a shared Distributed Unit (DU) comprises receiving a RRC message from a User Equipment (UE) and sending a first DU-to-Central Unit (CU) message to a first CU, where the first DU-to-CU message comprises the RRC message. The method further comprises either obtaining an indication that the first CU is a wrong CU for the RRC message or determining that the first CU is a wrong CU for the RRC message. The method further comprises sending another DU-to-CU message to a second CU, where the other DU-to-CU message comprises the RRC message or a RRC message related to the RRC message.
Grouping resource metadata tags
A system for applying metadata tags based on metadata tag groups is described. The system includes a plurality of compute nodes configured to provide a plurality of computing resources for clients of a provider network and a resource tag manager for the provider network. The resource tag manager is configured to receive, from a first client of an account of the provider network, a creation request to establish a resource attribute group comprising a plurality of resource keys and a plurality of resource values, wherein respective metadata keys correspond to respective resource values. The resource tag manager may receive, from a second client of the account, an application request to apply the resource attribute group to a computing resource and apply the plurality of resource keys and the plurality of resource values to metadata maintained for the computing resource.
Dynamic endpoint resources discovery in Kubernetes clusters via stable URI locator for workflow services
A method of performing resource discovery includes receiving, by a processing device, a resource identifier describing a resource of a computing cluster to be accessed by a workflow application. The method also includes sending the resource identifier to a container orchestration API to determine whether an endpoint exists for the resource. The method also includes, in response to an indication from the container orchestration API that the endpoint exists, receiving, from the container orchestration API, endpoint details used to access the resource, identifying an endpoint address based on the endpoint details, and binding the endpoint address to the resource in a runtime version of the workflow application to enable the workflow application to access the resource.
Systems and methods for bandwidth part selection initiated by a user equipment
A user equipment transmits user equipment information, associated with a communication of the user equipment, to permit a base station to select a first bandwidth part, a second bandwidth part, or a third bandwidth part. The user equipment is configured to communicate by the first bandwidth part, the second bandwidth part, and the third bandwidth part. The user equipment receives, from the base station, an instruction to monitor the first bandwidth part, the second bandwidth part, or the third bandwidth part. The instruction is selected based on the user equipment information. The user equipment monitors, based on the instruction, the first bandwidth part, the second bandwidth part, or the third bandwidth part.
Methods and apparatus to execute a workload in an edge environment
Methods and apparatus to execute a workload in an edge environment are disclosed. An example apparatus includes a node scheduler to accept a task from a workload scheduler, the task including a description of a workload and tokens, a workload executor to execute the workload, the node scheduler to access a result of execution of the workload and provide the result to the workload scheduler, and a controller to access the tokens and distribute at least one of the tokens to at least one provider, the provider to provide a resource to the apparatus to execute the workload.
Transaction-enabled systems and methods for resource acquisition for a fleet of machines
The present disclosure describes transaction-enabling systems and methods. A system can include a controller and a fleet of machines, each having at least one of a compute task requirement, a networking task requirement, and an energy consumption task requirement. The controller may include a resource requirement circuit to determine an amount of a resource for each of the machines to service the task requirement for each machine, a forward resource market circuit to access a forward resource market, and a resource distribution circuit to execute an aggregated transaction of the resource on the forward resource market.
PROCESSING QUEUE ASSIGNMENT BASED ON A FLAG IN A GENEVE HEADER
Described herein are systems, methods, and software to manage the identification of control packets in an encapsulation header. In one implementation, a computing system may receive a Geneve packet at a network interface and determine that the Geneve packet includes an Operations and Management (OAM) flag. Once the OAM flag is identified, the computing system can select a processing queue from a plurality of processing queues for a main processing system of the computing system based on the OAM flag and assign the Geneve packet to the processing queue.
PROCESSING QUEUE ASSIGNMENT BASED ON A FLAG IN A GENEVE HEADER
Described herein are systems, methods, and software to manage the identification of control packets in an encapsulation header. In one implementation, a computing system may receive a Geneve packet at a network interface and determine that the Geneve packet includes an Operations and Management (OAM) flag. Once the OAM flag is identified, the computing system can select a processing queue from a plurality of processing queues for a main processing system of the computing system based on the OAM flag and assign the Geneve packet to the processing queue.