VPN Connection Status Detection via Handshake Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing VPN systems face challenges in efficiently managing VPN connections, leading to resource wastage as allocated IP addresses are not promptly reallocated when client devices become inactive, resulting in reduced availability for other devices.

Innovation Solution

Implementing a method for VPN connection status detection that involves selecting an IP address for client devices from a pool, providing access, receiving handshake notifications, determining a threshold time period of inactivity, disconnecting the client device, and adding the IP address back to the pool, ensuring resources are reallocated efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IP addresses are allocated to client devices for VPN access, then VPN connection availability is improved, but resource wastage occurs when client devices become inactive and IP addresses are not promptly reallocated

Engineering Contradiction:
ImproveVPN connection availabilityVSAvoidresource wastage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system implements a feedback mechanism by monitoring handshake notifications from client devices to detect inactive connections. When no handshake notification is received within a threshold time period, the system automatically disconnects the client device and reallocates the IP address, ensuring resources are not wasted on inactive connections while maintaining availability for active users.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by establishing a threshold time period for detecting inactive connections. This pre-defined parameter enables the system to proactively identify and clean up inactive VPN connections before they consume resources for extended periods, balancing resource availability with efficient utilization.

Inventive Principle:
Principle #10Preliminary action

2Stability of the object's composition

If IP addresses are held reserved for client devices, then connection stability is improved, but IP address availability for other devices is reduced

Engineering Contradiction:
Improveconnection stabilityVSAvoidIP address availability
Core Design Contradiction:
Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

The system dynamically manages IP address allocation by transitioning IP addresses between allocated and available states based on real-time connection status. IP addresses are held reserved during active connections to ensure stability, but are automatically released and made available to the pool when connections become inactive, creating a dynamic balance between connection stability and resource availability.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If manual IP address management is used, then system complexity is reduced, but resource reallocation efficiency is worsened

Engineering Contradiction:
Improvesystem complexityVSAvoidresource reallocation efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system implements self-service by automatically detecting inactive VPN connections through monitoring handshake notifications and autonomously performing disconnection and IP address reallocation without requiring manual intervention. This automated resource management significantly improves reallocation efficiency while maintaining manageable system complexity through straightforward monitoring and threshold-based decision logic.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12015674B2Virtual private network connection status detection
Publication Date: 2024.06.18 UAB 360 IT
  • US12015674B2 patent drawing
  • US12015674B2 patent drawing
  • US12015674B2 patent drawing

AI summary

Virtual private network (VPN) service provider infrastructure (SPI) receives a request to access a VPN from a client device. The VPN SPI selects an Internet Protocol (IP) address for access to the VPN by the client device from a pool of IP addresses. The VPN SPI provides access to the VPN for the client device via the IP address. The VPN SPI receives one or more handshake notifications from the client device. The VPN SPI determines that a threshold time period has passed since a latest-in-time handshake notification of the one or more handshake notifications. The VPN SPI disconnects the client device from the VPN in response to determining that the threshold time period has passed. The VPN SPI adds the IP address to the pool of IP addresses in response to disconnecting the client device from the VPN.