# US 2018/0026912 A1 · Methods and apparatus for composite node malleability for disaggregated architectures

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

- Number: US 2018/0026912 A1
- Document ID: US20180026912A1
- Status: Published application
- Kind: A1
- Application number: 15/655,855
- Filed: 2017-07-20
- Published: 2018-01-25
- Earliest claimed: 2016-07-22
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: FRANCESC GUIM BERNAT; SUSANNE M. BALLE; DANIEL RIVAS BARRAGAN; JOHN CHUN KWOK LEUNG; SURAJ PRABHAKARAN; MURUGASAMY K. NACHIMUTHU; SLAWOMIR PUTYRSKI
- Web page: https://patentgrep.com/patent/US20180026912A1

## CPC

- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- 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/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 43/16: Threshold monitoring
- H04L 47/803: {Application aware}
- H04L 47/83: based on usage prediction
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/1031: Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04Q 9/00: Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
- H04L 41/16: using machine learning or artificial intelligence
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 43/0858: {One way delays}
- H04L 43/0894: Packet rate
- H04L 47/722: at the destination endpoint, e.g. reservation of terminal resources or buffer space
- H04L 47/805: {QOS or priority aware}
- H04Q 2209/20: using a distributed architecture
- 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)
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)

## Abstract

Techniques for increasing malleability in software-defined infrastructures are described. A compute node, including one or more processor circuits, may be configured to access one or more remote resources via a fabric, the compute node may be configured to monitor utilization of the one or more remote resources. The compute node may be further configured to identify based on one or more criteria that one or more remote resources may be released and initiate release of identified one or more remote resources. The compute node may be configured to generate a notification to a software stack indicating that the identified one or more remote resources has been released. Other embodiments are described and claimed.

## Claims

### Claim 1

A software-defined infrastructure system, comprising:
a compute node, including one or more processor circuits, arranged to access one or more remote resources via a fabric, the compute node configured to:
monitor utilization of the one or more remote resources;
identify based on one or more criteria that one or more remote resources may be released;
initiate release of identified one or more remote resources; and
generate a notification to a software stack indicating that the identified one or more remote resources has been released.

### Claim 2 (depends on 1)

The system of claim 1, wherein the notification includes a system interrupt to initiate a resource remapping.

### Claim 3 (depends on 1)

The system of claim 1, wherein the one or more criteria include underutilization for a predetermined period of time.

### Claim 4 (depends on 1)

The system of claim 1, wherein the one or more criteria are determined using a machine learning component.

### Claim 5 (depends on 1)

The system of claim 1, wherein the monitoring is initialized based upon a detected need for additional resources.

### Claim 6 (depends on 1)

The system of claim 1, wherein the one or more criteria are based on a dynamic limits table stored within a telemetry component.

### Claim 7 (depends on 6)

The system of claim 6, wherein the dynamic limits table is stored within a machine learning node recomposer of the telemetry component.

### Claim 8 (depends on 6)

The system of claim 6, wherein the dynamics limits table includes upper and lower limits for each of a plurality of resource types.

### Claim 9 (depends on 1)

The system of claim 1, wherein the one or more remote resources are exposed to the software stack as local resources.

### Claim 10 (depends on 1)

The system of claim 1, wherein the monitoring is performed by a composite node recomposer component within the compute node.

### Claim 11

A computer-implemented method, comprising:
monitoring utilization of one or more remote resources connected via a fabric to a compute node including one or more processor circuits;
identifying based on one or more criteria that one or more remote resources may be released;
initiating release of identified one or more remote resources; and
generating a notification to a software stack indicating that the identified one or more remote resources has been released.

### Claim 12 (depends on 11)

The method of claim 11, wherein the notification includes a system interrupt to initiate a resource remapping.

### Claim 13 (depends on 11)

The method of claim 11, wherein the one or more criteria include underutilization for a predetermined period of time.

### Claim 14 (depends on 11)

The method of claim 11, wherein the one or more criteria are determined using a machine learning component.

### Claim 15 (depends on 11)

The method of claim 11, wherein the monitoring is initialized based upon a detected need for additional resources.

### Claim 16 (depends on 11)

The method of claim 11, wherein the one or more criteria are based on a dynamic limits table stored within a telemetry component.

### Claim 17 (depends on 16)

The method of claim 16, wherein the dynamic limits table is stored within a machine learning node recomposer of the telemetry component.

### Claim 18 (depends on 16)

The method of claim 16, wherein the dynamics limits table includes upper and lower limits for each of a plurality of resource types.

### Claim 19 (depends on 11)

The method of claim 11, wherein the one or more remote resources are exposed to the software stack as local resources.

### Claim 20 (depends on 11)

The method of claim 11, wherein the monitoring is performed by a composite node recomposer component within the compute node.

### Claim 21

An article comprising a non-transitory computer-readable storage medium that stores instructions for execution by processing circuitry of a compute node of a software-defined infrastructure system, the instructions to cause the compute node to:
monitor utilization of one or more remote resources connected via a fabric to the compute node;
identify based on one or more criteria that one or more remote resources may be released;
initiate release of identified one or more remote resources; and
generate a notification to a software stack indicating that the identified one or more remote resources has been released.

### Claim 22 (depends on 21)

The article of claim 21, wherein the notification includes a system interrupt to initiate a resource remapping.

### Claim 23 (depends on 21)

The article of claim 21, wherein the one or more criteria include underutilization for a predetermined period of time.

### Claim 24 (depends on 21)

The article of claim 21, wherein the one or more criteria are determined using a machine learning component.

### Claim 25 (depends on 21)

The article of claim 21, wherein the monitoring is initialized based upon a detected need for additional resources.
