Encapsulated Test Packets for Network Node Status Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for testing network connections in centrally-controlled networks are inefficient, as they often reroute traffic without determining whether a disrupted node is transiently or permanently non-functional, leading to unnecessary burdens on other nodes.

Innovation Solution

A computer network testing process that constructs and sends encapsulated test packets through a reachable node to determine if an unreachable node is still functional on the data-plane network, using OpenFlow and tunneling protocols to confirm operational status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current methods reroute traffic around an unreachable node, then network control is maintained, but other network nodes are burdened with increased traffic and unnecessary reconfiguration

Engineering Contradiction:
Improvenetwork controlVSAvoidunnecessary traffic burden on other nodes
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system performs preliminary testing by sending encapsulated test packets through reachable nodes to the unreachable node before committing to traffic rerouting. This preliminary action determines whether the unreachable node is truly non-functional or merely experiencing transient control-plane issues, preventing premature rerouting that would burden other nodes with unnecessary traffic.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses reachable nodes as intermediaries to forward encapsulated test packets to the unreachable node. These intermediary nodes help test data-plane connectivity without requiring direct controller-to-node communication, allowing the system to distinguish between control-plane disruptions and complete node failures before initiating traffic rerouting.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-generated harmful factors

If the controller waits longer to reroute traffic, then other nodes avoid unnecessary burden, but the controller cannot respond beyond a predetermined waiting period

Engineering Contradiction:
Improvetraffic burden on other nodesVSAvoidresponse time for rerouting
Core Design Contradiction:
Object-generated harmful factorsVSLoss of time

Solution Approach 1:

The system performs preliminary testing with encapsulated packets before the predetermined waiting period expires. By conducting this test early and using the response (or lack thereof) to make informed decisions, the system can extend the effective waiting period safely or proceed with rerouting only when necessary, optimizing both response time and avoidance of unnecessary traffic burden.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from the encapsulated test packet responses to dynamically adjust the rerouting decision timeline. If test packets elicit responses indicating the unreachable node is still functional on the data plane, the controller extends the waiting period. If no response is received, the controller proceeds with rerouting within the predetermined period, optimizing response time based on actual node status.

Inventive Principle:
Principle #23Feedback

3Productivity

If the controller assumes an unreachable node is non-functional, then traffic can be rerouted quickly, but the node may still be forwarding data successfully

Engineering Contradiction:
Improvetraffic rerouting speedVSAvoidnode functionality assessment
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system uses reachable nodes as intermediaries to send encapsulated test packets through the data plane to the unreachable node. This intermediary approach allows testing of data-plane connectivity independent of control-plane status, providing reliable evidence of node functionality before making rerouting decisions, thus avoiding premature assumptions about node failure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary data-plane connectivity testing using encapsulated packets before assuming the unreachable node is non-functional. This preliminary verification ensures that rerouting is only initiated when the node is truly unreachable through the data plane, not merely when control-plane communication is disrupted, maintaining both productivity and reliability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9654375B1Systems and methods for testing network connections of a centrally-controlled network
Publication Date: 2017.05.16 GOOGLE LLC
  • US9654375B1 patent drawing
  • US9654375B1 patent drawing
  • US9654375B1 patent drawing

AI summary

A computer network testing process to determine whether, given a network node that is unreachable by communication attempts from a controller on a control-plane network, the network node is still functioning to forward data packets on a data-plane network, or if the network node is fully non-functional on both the control-plane network and data-plane network. In order to make this determination, the testing process identifies a network node that is still reachable by the controller on the control-plane network, identifies a route between the controller and unreachable node, passing through the reachable node, and constructs an encapsulated test packet that is sent along this route. In response to sending the encapsulated test packet, the controller may, upon receipt of a confirmation packet, determine that the unreachable node is still functional on the data-plane network, or if no confirmation packet is received, mark the unreachable node as fully non-functional.