Dynamic Sessional Proxy Server Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional proxy servers require restarts to update configurations, limiting their ability to dynamically route requests based on request content and session context, and they cannot differentiate between multiple sessions.

Innovation Solution

A dynamic inferred sessional proxy server system with an application programming interface (API) that allows reconfiguration without restarts, using an inference engine to determine session-dependent rules for routing requests based on content and context, and maintaining a reconfigurable rules table for dynamic updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proxy server configuration is updated by restarting the service, then configuration changes are applied, but service interruption occurs and requests cannot be routed dynamically

Engineering Contradiction:
Improveconfiguration update capabilityVSAvoidservice availability
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The proxy server implements dynamic configuration updates by loading new routing rules from files or databases without requiring service restart. The configuration system transitions from static to dynamic, allowing the proxy to adapt routing behavior in real-time while maintaining service continuity and request forwarding capability.

Inventive Principle:
Principle #15Dynamics

2Reliability

If proxy server uses fixed routing instructions, then routing is simple and reliable, but the proxy cannot differentiate between multiple sessions or route based on request content

Engineering Contradiction:
Improverouting stabilityVSAvoidsession differentiation capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The proxy server implements session-dependent routing rules that allow different routing instructions for different sessions or request types. Each session can have customized routing behavior based on request content, source, or other criteria, while maintaining the overall reliability of the routing system through structured rule management.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The proxy server changes routing parameters dynamically based on session context and request content. Routing decisions are made by evaluating multiple parameters including session ID, request method, URL patterns, and source IP, allowing flexible differentiation between sessions while maintaining reliable routing through consistent parameter evaluation.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If proxy server operates with static routing rules, then device complexity is low, but the system cannot perform intelligent routing based on request context

Engineering Contradiction:
Improverouting rule structureVSAvoidintelligent routing capability
Core Design Contradiction:
Device complexityVSExtent of automation

Solution Approach 1:

The proxy server performs intelligent routing autonomously by evaluating session-dependent rules and request content without requiring external intervention. The system automatically differentiates between sessions, selects appropriate routing instructions, and forwards requests accordingly, reducing the need for manual configuration while maintaining manageable system complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11394734B2Dynamic inferred sessional proxy server system
Publication Date: 2022.07.19 SONY INTERACTIVE ENTERTAINMENT LLC
  • US11394734B2 patent drawing
  • US11394734B2 patent drawing
  • US11394734B2 patent drawing

AI summary

A method for redirecting data traffic includes receiving a first request from a client device addressed to a first server and sending the first request from the client device to the first server, and determining rerouting rules. A response may be received addressed to client device from the first server the response is sent to the client device. Metadata from client device may be received wherein the metadata provides information about a second request from the client device and a second request from the client device is received addressed to the first server, the information about the second request in the metadata is compared to the rerouting rules and the second request is sent according the rerouting rules.