Service Status Notification via LLDP TLV Data

Solution Overview

Problem

In virtual private networks (VPNs), when a failure occurs in one service, it often leads to unnecessary disruption and traffic loss for other services due to the shutdown of physical links between provider edge (PE) and customer edge (CE) devices, and the process of rerouting traffic through alternate paths is time-consuming and disruptive.

Innovation Solution

PE devices determine the status of each service and generate type-length-value (TLV) data indicating this status, which is added to Link Layer Discovery Protocol (LLDP) packets and sent to CE devices, allowing traffic from services without errors to continue uninterrupted and routing errors to be redirected through alternate paths.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If physical links between PE and CE devices are shutdown when a service failure occurs, then service isolation is improved, but traffic continuity deteriorates

Engineering Contradiction:
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the service status monitoring at the PE device level, allowing each PE device to independently determine the status of services it hosts. This enables selective notification to CE devices about specific service failures without requiring shutdown of entire physical links, thus maintaining traffic continuity for unaffected services while achieving service isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism using LLDP packets with TLV data as a mediator between PE devices and CE devices. This intermediary allows the CE device to receive detailed service status information and make intelligent routing decisions, replacing the need for physical link shutdowns while maintaining service isolation through software-based service status tracking.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If physical links are shutdown to isolate service failures, then service failure containment is improved, but traffic loss increases

Engineering Contradiction:
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent implements preliminary action by having PE devices proactively monitor and determine service status, then pre-notify CE devices of service failures before they affect traffic. This allows CE devices to preemptively reroute traffic through alternate paths, containing service failures without causing traffic loss that would result from reactive physical link shutdowns.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent establishes a feedback mechanism where PE devices continuously report service status to CE devices via LLDP packets. This feedback loop enables CE devices to maintain real-time awareness of service health and dynamically adjust traffic routing, containing failures at the service level rather than requiring physical link disruption.

Inventive Principle:
Principle #23Feedback

3Reliability

If traffic rerouting is performed after service failure detection, then service recovery is improved, but downtime increases

Engineering Contradiction:
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by enabling CE devices to receive service status notifications and prepare alternate routing paths before actual service disruption occurs. This proactive approach minimizes downtime by allowing traffic to be switched to backup paths almost immediately upon receiving the LLDP notification, rather than waiting for failure detection and manual intervention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements self-service through automated service status monitoring at PE devices and automated routing decision-making at CE devices. When service failures are detected, the system automatically notifies affected CE devices, which then autonomously reroute traffic without human intervention, significantly reducing recovery time compared to manual processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11570073B1Service status notification
Publication Date: 2023.01.31
  • US11570073B1 patent drawing
  • US11570073B1 patent drawing
  • US11570073B1 patent drawing

AI summary

A provider edge (PE) device may receive traffic associated with one or more services, wherein the traffic includes a plurality of packets, and may determine, based on the plurality of packets, one or more packets respectively associated with each service of the one or more services. The PE device may determine, based on the one or more packets respectively associated with each service of the one or more services, a respective status of each of the one or more services. The PE device may generate type-length-value (TLV) data that indicates the respective status of each of the one or more services and may cause the TLV data to be added to a link layer discovery protocol (LLDP) packet. The PE device may send the LLDP packet that includes the added TLV data to a customer edge (CE) device.