Server Instance Allocation via Operational Parameter Eligibility Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing load balancing techniques in server computers often allocate server instances in a round robin manner, making it difficult to establish application instance sessions on selected server instances with specific hardware or firmware capabilities, leading to inefficient resource utilization.

Innovation Solution

A method for allocating server instances based on operational parameters, including unique identifiers, IP addresses, and MAC addresses, which analyzes eligibility for execution and queues requests if a server instance is overloaded, allowing for reevaluation during a timeout period and reallocating if capabilities change.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If round robin allocation is used for server instances, then allocation simplicity is improved, but resource utilization efficiency deteriorates

Engineering Contradiction:
Improveallocation simplicityVSAvoidresource utilization efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent changes the allocation parameter from simple sequential indexing (round robin) to a composite parameter that includes server instance capabilities, current load status, and application instance requirements. This allows the system to select server instances based on matching capabilities and available resources, thereby improving resource utilization efficiency while maintaining allocation simplicity through automated parameter-based selection.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If server instances are selected based on specific capabilities, then execution eligibility is improved, but allocation complexity deteriorates

Engineering Contradiction:
Improveexecution eligibilityVSAvoidallocation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-registering server instances with their capabilities and pre-defining application instance requirements. This allows the system to quickly match capabilities with requirements without complex real-time analysis, improving execution eligibility while keeping allocation complexity manageable through pre-established matching criteria.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary matching mechanism that mediates between server instance capabilities and application instance requirements. This intermediary layer simplifies the allocation process by handling the complexity of capability matching automatically, thereby improving execution eligibility without exposing the complexity to the allocation logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If server instances are overloaded, then request handling capacity is improved, but session establishment reliability deteriorates

Engineering Contradiction:
Improverequest handling capacityVSAvoidsession establishment reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements dynamic load monitoring and adaptive allocation where server instance load status is continuously tracked. When a server instance becomes overloaded, the system dynamically adjusts allocation decisions to avoid assigning new application instances, thereby maintaining session establishment reliability while allowing request handling capacity to scale with available resources.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12001888B2Server instance allocation for execution of application instances
Publication Date: 2024.06.04 HEWLETT PACKARD ENTERPRISE DEV LP
  • US12001888B2 patent drawing
  • US12001888B2 patent drawing
  • US12001888B2 patent drawing

AI summary

Example techniques for allocating a candidate server instance for execution of an application instance are described. In an example, a request for allocation of a candidate server instance from multiple server instances is received. The request for allocation of the candidate server instance comprises allocation parameters to uniquely identify the candidate server instance from the plurality of server instances. Subsequently, operational parameters of the candidate server instance are analyzed to determine eligibility of the candidate server instance for execution of the application instance. The candidate server instance is subsequently allocated for execution of the application instance based on the eligibility.