Proxy Server Network Architecture for Secure Data Communications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The network edge is vulnerable to unauthorized data transfers and intrusions between secure internal networks and unsecure external networks, particularly due to the lack of effective security measures against malware and unauthorized access, which poses a significant threat to confidential information such as credit card data.

Innovation Solution

A network architecture with a demarcation zone (DMZ) using multiple proxy servers and a management server to establish secure connections through SSL/TLS protocols, providing mutual authentication and encryption, and implementing load balancing to ensure high availability by configuring all proxy servers with identical configuration information, allowing seamless switching in case of server unavailability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single proxy server is used for data communications between external and internal networks, then device complexity is reduced, but reliability deteriorates due to single point of failure

Engineering Contradiction:
Improvehigh availabilityVSAvoidmultiple proxy servers
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system divides the proxy server function into multiple separate proxy servers (first proxy server, second proxy server, etc.) that can operate independently. Each proxy server handles data communications separately, allowing the system to segment the load and failover functionality across multiple components rather than relying on a single point of failure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements failover mechanisms where if one proxy server becomes unavailable, the load balancer automatically redirects traffic to other available proxy servers. This allows the system to discard the failed server's service temporarily and recover by utilizing remaining functional servers, maintaining continuous operation.

Inventive Principle:
Principle #34Discarding and recovering

2Reliability

If multiple proxy servers are deployed for load balancing, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvehigh availabilityVSAvoidmultiple proxy servers
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

All proxy servers in the system are configured with substantially identical configuration information, making them universal and interchangeable. This multi-functionality allows any proxy server to take over the role of any other proxy server in case of failure, simplifying the system's operational complexity despite having multiple components.

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

Solution Approach 2:

The proxy servers are designed with equal status and identical configurations, creating an equipotential system where no single server holds a privileged position. This equality ensures that all servers can perform the same functions and are equally capable of handling traffic, simplifying management and failover operations.

Inventive Principle:
Principle #12Equipotentiality

3Ease of operation

If proxy servers are configured with identical configuration information, then ease of operation is improved through seamless switching, but adaptability deteriorates

Engineering Contradiction:
Improveseamless switchingVSAvoidconfiguration flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic configuration where proxy servers can be added, removed, or updated without requiring changes to other servers' configurations. The load balancer dynamically adjusts traffic routing based on server availability and status, allowing the system to adapt to changing conditions while maintaining operational simplicity through consistent configuration templates.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2308196B1Network architecture for secure data communications
Publication Date: 2017.07.12 VISA USA INC
  • EP2308196B1 patent drawingFigure 1
  • EP2308196B1 patent drawingFigure 2
  • EP2308196B1 patent drawingFigure 3~4

AI summary

A network architecture includes a perimeter network connected between an internal network and an external network. The perimeter network includes one or more external edge nodes that are connected to the external network and a plurality of proxy servers that are each connected to one or more of the external edge nodes. One or more internal edge nodes are connected between the plurality of proxy servers and the internal network. The proxy servers are operable to establish a first secure connection between a destination through the external network and a second secure connection to a destination in the internal network. Each of the plurality of proxy servers provide a substantially identical identification for authentication when establishing the first and second secure connections.