Cloud Container Node Selection for Resource Waste and Attack Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud container orchestration leads to resource fragmentation and decreased utilization, and cloud resources are vulnerable to attacks like spoofing, tampering, and denial of service, posing security threats.

Innovation Solution

A computing platform uses deep reinforcement learning to optimize node selection and threat detection for cloud container deployment, employing a node selection model trained with historical performance and application parameters, and a threat detection model to identify and mitigate attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud container orchestration is used to manage and schedule resources, then application deployment is enabled, but resource fragmentation and decreased resource utilization occur

Engineering Contradiction:
Improveresource utilizationVSAvoidresource waste
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by pre-training node selection models with historical performance data and pre-configuring threat detection models before actual deployment occurs. This allows the system to make optimized node selection decisions in advance, reducing resource fragmentation and improving utilization efficiency during actual application deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring node performance metrics (CPU usage, memory usage, network bandwidth, disk capacity) and using this information to retrain and update node selection models. This feedback loop enables the system to learn from actual performance data and improve resource allocation decisions, reducing fragmentation and waste over time.

Inventive Principle:
Principle #23Feedback

2Reliability

If cloud resources are deployed to support applications, then service availability is improved, but vulnerability to attacks such as spoofing, tampering, and denial of service increases

Engineering Contradiction:
Improveservice availabilityVSAvoidsecurity threats
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary security actions by pre-training threat detection models with historical threat data before attacks occur. The models are configured to detect various attack types (spoofing, tampering, denial of service) in advance, enabling the system to prepare defense mechanisms before actual threats materialize, thus maintaining service availability while countering security risks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms for security by continuously monitoring node performance and threat indicators, then using this information to retrain threat detection models. This feedback loop enables the system to adapt to evolving attack patterns and improve its detection accuracy over time, maintaining service reliability while responding to security threats.

Inventive Principle:
Principle #23Feedback

3Productivity

If a node selection model is trained using historical performance information, then deployment optimization is achieved, but system complexity increases

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidmodel training complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system achieves multi-functionality by using a single node selection model framework that handles multiple purposes: optimizing resource allocation, predicting node performance, and guiding deployment decisions. The model processes various input types (CPU, memory, network, disk metrics) and produces comprehensive deployment recommendations, reducing the need for separate specialized models and simplifying overall system architecture.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system manages complexity by dynamically adjusting model parameters and training data based on actual deployment needs. The model can adapt its complexity level by selecting relevant historical performance parameters (CPU usage, memory usage, network bandwidth, disk capacity) that are most pertinent to current deployment scenarios, thereby optimizing deployment efficiency without consistently maintaining maximum complexity.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If threat detection models are trained using historical threat information, then security detection capability is improved, but computational resources and time requirements increase

Engineering Contradiction:
Improvethreat detection accuracyVSAvoidtraining time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary training of threat detection models using historical threat data before actual threat detection is needed. By pre-training the models in advance and storing the trained parameters, the system can quickly deploy security monitoring without requiring time-consuming training during actual threat detection operations, thus improving detection accuracy while minimizing time loss during active security monitoring.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system manages training time by dynamically adjusting the scope and complexity of threat detection model training based on available historical data and computational resources. The model can adapt to train on specific threat patterns or time periods most relevant to current operational needs, thereby improving detection accuracy for critical threats while reducing unnecessary training time on less relevant historical data.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12563065B2Monitoring and preventing spoofing, tampering, and denial of service attacks on cloud containers
Publication Date: 2026.02.24 BANK OF AMERICA CORP
  • US12563065B2 patent drawing
  • US12563065B2 patent drawing
  • US12563065B2 patent drawing

AI summary

A computing platform may train, using historical node performance information and historical application parameter information, a node selection model, which may configure the model to select nodes for application cloud deployment. The computing platform may receive a request to deploy an application to a cloud network. The computing platform may select a node, of the plurality of nodes of the cloud network, to which the application should be deployed. The computing platform may queue, along with other applications scheduled for deployment to the plurality of nodes, the application for deployment to the node. After identifying that the application is first in the queue, the computing platform may deploy the application to the node of the cloud network, which may create, at the node, a container corresponding to the application.