Peer Revival Detection for VPN Session Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In systems using Dead Peer Detection (DPD) for VPNs, especially with mobile devices, the 'forced outage' issue occurs where a peer goes offline temporarily, leading to prolonged connection wait times and resource wastage due to incomplete DPD procedures, and allowing multiple sessions per IDi exacerbates resource consumption and security vulnerabilities.

Innovation Solution

Implementing a Peer Revival Detection mechanism that quickly determines the status of existing sessions using a boosted DPD procedure, allowing for faster session recovery and minimizing duplicate sessions by differentiating between revived peers and new connections, thus reducing 'forced outage' periods and optimizing resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Dead Peer Detection (DPD) procedures are implemented to detect dead peers, then connection reliability is improved, but forced outage periods are prolonged due to incomplete DPD procedures

Engineering Contradiction:
Improveconnection reliabilityVSAvoidforced outage period
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing a quick status check of existing sessions before initiating a full DPD procedure. When a peer reconnection request is detected, the system first checks whether the session exists and is in a dead state, allowing immediate session termination or revival without waiting for the complete DPD timeout period. This preliminary detection resolves the contradiction by reducing the forced outage period while maintaining connection reliability through accurate dead peer detection.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple sessions per IDi are allowed to support peer revival, then session continuity is improved, but resource consumption increases

Engineering Contradiction:
Improvesession continuityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies discarding and recovering by implementing a mechanism that detects and terminates dead sessions, then recovers the associated resources for new connections. When a peer reconnection request is received, the system checks for existing dead sessions, terminates them, and frees up the resources (memory, processing power, connection slots) for the revived peer. This resolves the contradiction by ensuring session continuity for legitimate peers while preventing resource exhaustion from accumulating dead sessions.

Inventive Principle:
Principle #34Discarding and recovering

Solution Approach 2:

The system applies self-service by automatically detecting dead peers and cleaning up their sessions without requiring manual intervention or prolonged timeout waiting. The peer revival detection mechanism autonomously identifies dead sessions, terminates them, and prepares resources for reconnection, enabling the system to self-manage its resources efficiently while maintaining session continuity for legitimate users.

Inventive Principle:
Principle #25Self-service

3Productivity

If Dead Peer Detection is implemented, then network resource management is improved, but system complexity increases

Engineering Contradiction:
Improvenetwork resource managementVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies partial action by implementing a simplified peer detection mechanism that performs only the necessary checks for reconnection requests rather than continuous full DPD procedures. The system checks whether a session exists and is dead only when a peer reconnection is detected, avoiding the overhead of continuous DPD while still achieving effective dead peer detection and resource management. This resolves the contradiction by improving network resource management through targeted detection while minimizing system complexity.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9736244B2Peer revival detection
Publication Date: 2017.08.15 NOKIA SOLUTIONS & NETWORKS OY
  • US9736244B2 patent drawing
  • US9736244B2 patent drawing
  • US9736244B2 patent drawing

AI summary

It is provided a method, comprising detecting a request for establishing a session between a peer and a network, wherein the request is received from the peer and comprises an identifier of a user of the network; checking, if the request is detected, whether a first session is established, wherein the first session is a session of the user which is established between the peer and the network; determining, if it is checked that the first session is established, whether the first session is dead or alive; flushing the first session if it is determined that the first session is dead; triggering an establishment of the requested session if it is determined that the first session is dead.