# US 2025/0193295 A1 · Technologies for dynamic accelerator selection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0193295 A1
- Document ID: US20250193295A1
- Status: Published application
- Kind: A1
- Application number: 19/060,359
- Filed: 2025-02-21
- Published: 2025-06-12
- Earliest claimed: 2017-08-30
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Francesc Guim Bernat
- Web page: https://patentgrep.com/patent/US20250193295A1

## CPC

- H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0629: {Configuration or reconfiguration of storage systems}
- G06F 3/0631: {by allocating resources to storage systems}
- G06F 3/0665: {at area level, e.g. provisioning of virtual or logical volumes}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 9/28: Enhancement of operational speed, e.g. by using several microcontrol devices operating in parallel
- G06F 9/5022: {Mechanisms to release resources}
- G06F 9/505: {considering the load}
- G06F 9/5088: {involving task migration}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3409: {for performance assessment}
- G06F 11/3442: {for planning or managing the needed capacity}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- G06F 30/34: for reconfigurable circuits, e.g. field programmable gate arrays [FPGA] or programmable logic devices [PLD]
- G11C 29/36: Data generation devices, e.g. data inverters
- G11C 29/38: Response verification devices
- H04L 9/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 41/0213: Standardised network management protocols, e.g. simple network management protocol [SNMP]
- H04L 41/0668: by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
- H04L 41/0677: Localisation of faults
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/0893: Assignment of logical groups to network elements
- H04L 41/0896: Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76)
- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 43/065: related to network devices
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 45/28: using route fault recovery
- H04L 45/7453: using hashing
- H04L 47/11: Identifying congestion
- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 47/781: {Centralised allocation of resources}
- H04L 47/83: based on usage prediction
- H04L 49/30: {Peripheral units, e.g. input or output ports}
- H04L 49/351: for local area network [LAN], e.g. Ethernet switches
- H04L 49/9005: using dynamic buffer space allocation
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 69/12: Protocol engines
- H04L 69/22: Parsing or analysis of headers
- H04L 69/32: Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H05K 7/1489: {characterized by the mounting of blades therein, e.g. brackets, rails, trays (H05K7/1491 takes precedence)}
- H05K 7/18: Construction of rack or frame
- H05K 7/20209: {Thermal management, e.g. fan control}
- H05K 7/20736: {within cabinets for removing heat from server blades}
- G06F 9/44: Arrangements for executing specific programs
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/4856: {resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence)}
- G06F 9/5044: {considering hardware capabilities}
- G06F 9/5055: {considering software capabilities, i.e. software resources associated or available to the machine}
- G06F 9/5061: {Partitioning or combining of resources}
- G06F 12/1054: {the data cache being concurrently physically addressed}
- G06F 12/1063: {the data cache being concurrently virtually addressed}
- G06F 13/4022: {using switching circuits, e.g. switching matrix, connection or expansion network (G06F13/4009 takes precedence)}
- G06F 15/1735: {Network adapters, e.g. SCI, Myrinet (protocol engines H04L69/12)}
- G06F 21/105: {Arrangements for software license management or administration, e.g. for managing licenses at corporate level}
- G06F 2200/201: Cooling arrangements using cooling fluid
- G06F 2201/85: Active fault masking without idle spares
- G06F 2201/86: Event-based monitoring
- G06F 2201/885: Monitoring specific for caches
- G06F 2209/5019: Workload prediction
- G06F 2209/509: Offload
- G06F 2212/1044: Space efficiency improvement
- G06F 2213/0064: Latency reduction in handling transfers
- G06N 3/063: using electronic means
- G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations
- H04L 41/044: comprising hierarchical management structures
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/142: using statistical or mathematical methods
- H04L 41/149: for prediction of maintenance
- H04L 41/16: using machine learning or artificial intelligence
- H04L 41/34: Signalling channels for network management communication
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5019: Ensuring fulfilment of SLA
- H04L 43/16: Threshold monitoring
- H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
- H04L 69/321: Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
- H05K 7/1498: {Resource management, Optimisation arrangements, e.g. configuration, identification, tracking, physical location (thermal management H05K7/20836)}
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)
- H05K: PRINTED CIRCUITS; CASINGS OR CONSTRUCTIONAL DETAILS OF ELECTRIC APPARATUS; MANUFACTURE OF ASSEMBLAGES OF ELECTRICAL COMPONENTS
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Technologies for dynamic accelerator selection include a compute sled. The compute sled includes a network interface controller to communicate with a remote accelerator of an accelerator sled over a network, where the network interface controller includes a local accelerator and a compute engine. The compute engine is to obtain network telemetry data indicative of a level of bandwidth saturation of the network. The compute engine is also to determine whether to accelerate a function managed by the compute sled. The compute engine is further to determine, in response to a determination to accelerate the function, whether to offload the function to the remote accelerator of the accelerator sled based on the telemetry data. Also the compute engine is to assign, in response a determination not to offload the function to the remote accelerator, the function to the local accelerator of the network interface controller.

## Claims

### Claim 1

A cloud service provider system for use in providing at least one service in association with at least one node via at least one network, the cloud service provider system comprising:
resources that are configurable to comprise accelerator circuitry comprised in multiple accelerators in the at least one network, the multiple accelerators comprising one or more certain accelerators that are remote from the at least one node; and
server circuitry configurable to dynamically assign and/or reassign, based upon (1) physical location information associated, at least in part, with the multiple accelerators, (2) current resource usage data, (3) resource utilization trend data, and (4) predicted future resource utilization data, at least one workload to and/or from at least one portion of the resources;
wherein:
the at least one workload is associated with the providing of the at least one service;
execution of the at least one workload is to be associated with at least one container and/or virtual machine; and
the current resource usage data, the resource utilization trend data, and the predicted future resource utilization data are to be generated based, at least in part, upon telemetry data associated with the at least one portion of the resources.

### Claim 2 (depends on 1)

The cloud service provider system of claim 1, wherein:
the server circuitry is to determine accelerator failure based upon the telemetry data.

### Claim 3 (depends on 2)

The cloud service provider system of claim 2, wherein:
the at least one workload is associated with machine learning; and
the accelerator circuitry comprises graphics processing unit hardware.

### Claim 4

A method implemented using a cloud service provider system, the cloud service provider system to be used in providing at least one service in association with at least one node via at least one network, the cloud service provider system comprising resources and server circuitry, the resources being configurable to comprise accelerator circuitry comprised in multiple accelerators in the at least one network, the multiple accelerators comprising one or more certain accelerators that are remote from the at least one node, the method comprising:
dynamically assigning and/or reassigning, by the server circuitry, based upon (1) physical location information associated, at least in part, with the multiple accelerators, (2) current resource usage data, (3) resource utilization trend data, and (4) predicted future resource utilization data, at least one workload to and/or from at least one portion of the resources;
wherein:
the at least one workload is associated with the providing of the at least one service;
execution of the at least one workload is to be associated with at least one container and/or virtual machine; and
the current resource usage data, the resource utilization trend data, and the predicted future resource utilization data are to be generated based, at least in part, upon telemetry data associated with the at least one portion of the resources.

### Claim 5 (depends on 4)

The method of claim 4, wherein:
the server circuitry is to determine accelerator failure based upon the telemetry data.

### Claim 6 (depends on 5)

The method of claim 5, wherein:
the at least one workload is associated with machine learning; and
the accelerator circuitry comprises graphics processing unit hardware.

### Claim 7

At least one non-transitory machine-readable storage medium storing instructions to be executed by at least one machine that is to be associated with a cloud service provider system, the cloud service provider system to be used in providing at least one service in association with at least one node via at least one network, the cloud service provider system comprising resources and server circuitry, the resources being configurable to comprise accelerator circuitry comprised in multiple accelerators in the at least one network, the multiple accelerators comprising one or more certain accelerators that are remote from the at least one node, the instructions, when executed by the at least one machine, resulting in the cloud service provider system being configured to enable performance of operations comprising:
dynamically assigning and/or reassigning, by the server circuitry, based upon (1) physical location information associated, at least in part, with the multiple accelerators, (2) current resource usage data, (3) resource utilization trend data, and (4) predicted future resource utilization data, at least one workload to and/or from at least one portion of the resources;
wherein:
the at least one workload is associated with the providing of the at least one service;
execution of the at least one workload is to be associated with at least one container and/or virtual machine; and
the current resource usage data, the resource utilization trend data, and the predicted future resource utilization data are to be generated based, at least in part, upon telemetry data associated with the at least one portion of the resources.

### Claim 8 (depends on 7)

The at least one non-transitory machine-readable storage medium of claim 7, wherein:
the server circuitry is to determine accelerator failure based upon the telemetry data.

### Claim 9 (depends on 8)

The at least one non-transitory machine-readable storage medium of claim 8, wherein:
the at least one workload is associated with machine learning; and
the accelerator circuitry comprises graphics processing unit hardware.

### Claim 10

At least one data center for use in association with at least one node, the at least one data center to be used in association with a cloud service provider system, the cloud service provider system to be used in providing at least one service, the at least one data center comprising:
at least one network;
multiple server nodes; and
resources configurable to comprise multiple accelerator nodes to be communicatively coupled to the multiple server nodes via the at least one network, the multiple accelerator nodes comprising respective accelerator circuitry, one or more of the multiple accelerator nodes being remote from the at least one node, the multiple server nodes comprising server circuitry, the server circuitry being configurable to dynamically assign and/or reassign, at least in part, based upon (1) physical location information of the multiple accelerator nodes, (2) current resource usage data, (3) resource utilization trend data, and (4) predicted future resource utilization data, at least one workload to and/or from at least one portion of the resources;
wherein:
the at least one workload is associated with the providing of the at least one service;
execution of the at least one workload is to be associated with at least one container and/or virtual machine; and
the current resource usage data, the resource utilization trend data, and the predicted future resource utilization data are to be generated based, at least in part, upon telemetry data associated with the at least one portion of the resources.

### Claim 11 (depends on 10)

The at least one data center of claim 10, wherein:
the server circuitry is to determine accelerator failure based upon the telemetry data.

### Claim 12 (depends on 11)

The at least one data center of claim 11, wherein:
the at least one workload is associated with machine learning; and
the respective accelerator circuitry comprises graphics processing unit hardware.

### Claim 13 (depends on 12)

The at least one data center of claim 12, wherein:
the at least one data center comprises multiple data centers.
