Authorization Proxy for Load Balancer Traffic Segregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing authorization systems face bottlenecks due to limitations in load balancers, which require code updates for all clients simultaneously, fail to segregate traffic for specific clients, and lack validation and logging capabilities, leading to potential system-wide failures and inefficiencies.

Innovation Solution

A layer of proxies is introduced between the load balancer and authorization cells to perform preliminary request validation, modify requests and responses for protocol changes, direct traffic to specific authorization cells, and enhance logging, allowing for client prioritization and controlled code testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a load balancer is used to distribute authorization requests, then traffic distribution is achieved, but code updates must be applied to all clients simultaneously and traffic cannot be segregated for specific clients

Engineering Contradiction:
Improvetraffic distribution efficiencyVSAvoidclient traffic segregation capability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an authorization gateway as an intermediary component between the load balancer and authorization cells. This gateway acts as a mediator that can selectively route traffic from specific clients to specific authorization cells, enabling fine-grained control over traffic distribution while maintaining the benefits of load balancing. The gateway intercepts authorization requests, identifies the client, and directs traffic appropriately without requiring changes to client code.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If load balancer directly handles authorization requests, then simple architecture is maintained, but validation and logging capabilities are insufficient leading to system-wide failure risks

Engineering Contradiction:
Improvesystem architecture simplicityVSAvoidsystem failure risk
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the authorization system into distinct functional components: load balancer, authorization gateway, and authorization cells. The gateway is separated as a dedicated component with specialized functions for validation, logging, and traffic management. This segmentation allows each component to be optimized for its specific function while maintaining overall system reliability through distributed architecture, preventing single points of failure.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If protocol changes are made in authorization cells, then system adaptability is improved, but all clients are affected simultaneously requiring code updates

Engineering Contradiction:
Improveprotocol change capabilityVSAvoidclient code update requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The authorization gateway serves as a protocol translation intermediary between clients and authorization cells. When protocol changes are made in authorization cells, the gateway can translate between the new protocol and the legacy protocol that clients expect. This allows protocol evolution in the backend without requiring simultaneous client code updates, as the gateway absorbs the protocol change impact.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If multiple authorization cells are deployed, then system capacity is increased, but traffic cannot be directed to specific cells for prioritization or controlled testing

Engineering Contradiction:
Improveauthorization processing capacityVSAvoidtraffic routing control
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic traffic routing at the authorization gateway based on client identity, authorization cell status, and routing rules. This dynamic control enables flexible traffic distribution where specific clients can be directed to specific authorization cells for prioritization, testing, or load management. The routing configuration can be changed without system restart, allowing adaptive traffic management in response to changing system conditions.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11729167B2Authorization proxy
Publication Date: 2023.08.15 TARGET BRANDS INC
  • US11729167B2 patent drawing
  • US11729167B2 patent drawing
  • US11729167B2 patent drawing

AI summary

A computer-implemented method includes a proxy receiving an authorization message from a load balancer and the proxy selecting an authorization cell from a plurality of authorization cells designated for the proxy in response to receiving the authorization message. The proxy sending a second authorization message to the selected authorization cell and the proxy receiving a response message from the selected cell, wherein the response message corresponds to the second authorization message. The proxy then sending a second response message to the load balancer in response to receiving the response message.