Load Balancer User Identification for Dedicated Node Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional load balancing systems in secure networks inefficiently distribute processing threads as they lack user identification information, leading to suboptimal utilization of processing nodes.

Innovation Solution

A method where a load balancer identifies the user and transfers threads to either dedicated or non-dedicated processing nodes based on the existence of a dedicated node for the user, optimizing resource allocation by ensuring efficient processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If conventional load balancer distributes threads without user identification, then thread distribution can be performed quickly, but processing efficiency and resource utilization deteriorate

Engineering Contradiction:
Improvethread distribution speedVSAvoidprocessing efficiency
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The system performs user identification and authentication before thread distribution. The load balancer authenticates the user and determines whether a dedicated processing node exists prior to distributing the thread, enabling optimized resource allocation based on user identity while maintaining efficient thread distribution processes.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If threads are distributed to any available processing node, then load balancing can be simplified, but resource utilization and processing efficiency deteriorate

Engineering Contradiction:
Improveload balancing complexityVSAvoidresource utilization
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system implements different thread distribution strategies based on user characteristics. For authenticated users with dedicated processing nodes, threads are routed to dedicated nodes for optimized processing. For other cases, conventional load balancing applies. This localized differentiation improves resource utilization without requiring complete system redesign.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The load balancer acts as an intermediary that performs user authentication and determines the appropriate destination processing node before thread distribution. This intermediary function enables the system to leverage user identification information for optimized resource allocation while maintaining the simplicity of the overall load balancing architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If user identification is performed before thread distribution, then processing efficiency can be optimized, but authentication time and processing delay increase

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidauthentication time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

User authentication is performed as a preliminary action before thread distribution. The load balancer authenticates the user and determines dedicated node assignment in advance, so that when threads arrive, the processing node selection is already optimized, reducing overall processing time despite the initial authentication step.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9058222B1System and method for distributed login with secure transfer to processor node based on one or more identifiers
Publication Date: 2015.06.16 IQNAVIGATOR INC
  • US9058222B1 patent drawing
  • US9058222B1 patent drawing
  • US9058222B1 patent drawing

AI summary

A distributed networked computer system is provided. The distributed networked computer system receives processing threads from a plurality of workstations and distributes the processing threads to selected processing nodes through a load balancer. The load balancer is configured to recognize certain enterprise users and transfer the processing threads from the certain enterprise users to dedicated processing nodes dedicated to processing the threads of those certain users.