Central Connectivity Engine for Remote Network Tunnel Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Establishing and maintaining accurate network configurations for remote connections is challenging and prone to errors, especially in cloud computing environments accelerated by the shift to remote work.
Innovation Solution
A central connectivity engine manages network data to create a tunnel proxy, establishing separate tunnels between remote networks and forming a logical link for data flow, allowing customers to initiate and manage connectivity without manual intervention from support providers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual network configuration is used for remote connections, then connectivity can be established, but the process is demanding and prone to error
Solution Approach 1:
The system enables customer networks to autonomously manage their own connectivity by collecting and storing their own network data (addresses, URLs, hostnames) and initiating connection requests without requiring manual intervention from support providers. The central engine automatically processes these requests and establishes connections based on the provided configuration data.
Solution Approach 2:
A central engine acts as an intermediary between customer networks and support provider networks. It collects network data from customers, manages the connection establishment process, and coordinates tunnel creation and logical link formation, thereby simplifying the overall configuration process and reducing errors.
2Extent of automation
If support providers manually manage connectivity, then connections can be established, but it requires manual intervention and reduces customer autonomy
Solution Approach 1:
Customer networks pre-collect and store their own network configuration data (addresses, URLs, hostnames) in advance. When a connection is needed, the system can quickly retrieve and use this pre-prepared data to establish connections rapidly without requiring manual data collection or support provider intervention.
Solution Approach 2:
The system empowers customer networks to independently initiate connection requests and manage their own connectivity. The central engine automatically processes these self-service requests, establishing connections without requiring support provider involvement, thereby increasing automation and reducing connection establishment time.
3Productivity
If network configurations are maintained manually, then connections can be updated, but it is demanding and error-prone
Solution Approach 1:
The central engine continuously monitors connection status and automatically updates configurations based on current network data. When connections need to be modified or terminated, the system automatically processes these changes and notifies relevant parties, ensuring configurations remain accurate without manual intervention.
Solution Approach 2:
Customer networks can autonomously initiate connection changes by submitting updated network data or connection requests to the central engine. The system automatically processes these requests, updates configurations, and establishes or terminates connections as needed, improving both efficiency and accuracy.
4Reliability
If tunnel proxies are created for each connection, then secure connectivity is established, but system complexity increases
Solution Approach 1:
The central engine serves multiple functions: it collects network data, creates tunnel proxies, establishes tunnels, forms logical links, and manages connection lifecycle. This multi-functional approach consolidates complexity into a single centralized system rather than distributing it across multiple components, making the system easier to manage while maintaining security.
Solution Approach 2:
The tunnel proxy acts as an intermediary component that the central engine creates to secure connections between customer and support provider networks. By centralizing the creation and management of these proxies through the central engine, the system maintains security while managing complexity centrally rather than distributing it across network endpoints.
Data Source
AI summary
Connectivity between remote networks is managed by a central engine that collects and stores network data such as network addresses, URLs, hostnames, and/or other information. The engine creates a tunnel proxy, as well as separate respective tunnels with the remote networks. Based upon network data, the engine references the tunnel proxy to create a logical link joining the respective tunnels. Data can then flow between the remote networks through the logical link. The logical link may exist for only a limited time, e.g., as determined by a timer. Certain embodiments may be particularly suited to empower a customer network to manage connectivity with the remote network of a support provider. The customer can initiate connectivity changes without the manual involvement of the support provider. The customer can also authorize the support provider to manage connectivity and initiate changes under prescribed conditions.