Traffic Engineering Database Update for RSVP LSP Bandwidth Accuracy

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In computer networks, the coexistence of resource reservation protocol (RSVP) and non-resource reservation protocol Label Switched Paths (LSPs) within the same domain leads to inaccuracies in Traffic Engineering Database (TED) used by path computation elements, as they do not account for non-RSVP LSP bandwidth utilization, affecting the computation of RSVP paths.

Innovation Solution

A mechanism is introduced to automatically update TED information by collecting and comparing traffic flow statistics of non-RSVP LSPs to a pre-defined threshold, adjusting the reservable bandwidth for RSVP LSP reservations, ensuring accurate path computation without modifying existing computation logic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If non-resource reservation protocol LSPs are provisioned in the same domain as resource reservation protocol LSPs, then network flexibility and bandwidth sharing are improved, but inaccuracies are introduced in the TED used by path computation elements

Engineering Contradiction:

Improvenetwork flexibilityVSAvoidTED accuracy

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The system implements feedback mechanisms where traffic flow statistics from non-RSVP LSPs are continuously collected and used to update TED information. This feedback loop ensures that path computation elements receive accurate bandwidth utilization information, resolving the inaccuracy issue while maintaining network flexibility

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

An intermediary mechanism is introduced between non-RSVP LSP traffic and RSVP path computation. The system collects traffic flow statistics as intermediary data and uses this information to update TED entries, enabling accurate resource allocation without modifying the core RSVP computation logic

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If path computation elements do not account for non-RSVP LSP bandwidth utilization, then computation logic remains simple, but resource allocation becomes inaccurate

Engineering Contradiction:

Improvecomputation logic complexityVSAvoidresource allocation accuracy

Core Design Contradiction:

Device complexityVSManufacturing precision

Solution Approach 1:

The system performs preliminary actions by collecting traffic flow statistics and updating TED information before path computation occurs. This advance preparation ensures that path computation elements work with accurate, up-to-date bandwidth information without adding complexity to the computation logic itself

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The TED update mechanism operates autonomously by automatically collecting traffic flow statistics and updating itself without requiring changes to path computation elements. This self-service approach maintains computation logic simplicity while improving resource allocation accuracy

Inventive Principle:

Principle #25Self-service

3Measurement precision

If traffic flow statistics are collected and TED is automatically updated, then path computation accuracy is improved, but system complexity increases

Engineering Contradiction:

Improvebandwidth utilization accuracyVSAvoidsystem complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system leverages existing multi-functional components to perform TED updates. Traffic flow collection and processing mechanisms already present in the network infrastructure are utilized, avoiding the need for dedicated complex systems while achieving accurate bandwidth utilization tracking

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10291531B2Bandwidth management for resource reservation protocol LSPS and non-resource reservation protocol LSPS

Publication Date: 2019.05.14 JUNIPER NETWORKS INC

AI summary

In general, techniques described are for bandwidth sharing between resource reservation protocol label switched paths (LSPs) and non-resource reservation protocol LSPs. For example, in networks where resource reservation protocol LSPs and non-resource reservation protocol LSPs co-exist within the same domain, resource reservation protocol LSPs and non-resource reservation protocol LSPs may share link bandwidth. However, when non-resource reservation protocol LSPs are provisioned, resource reservation protocol path computation elements computing resource reservation protocol paths may not account for non-resource reservation protocol LSP bandwidth utilization. The techniques described herein provide a mechanism for automatically updating traffic engineering database (TED) information about resource reservation protocol LSPs in a way that accounts for non-resource reservation protocol LSP traffic flow statistics, such as bandwidth utilization. Path computation elements may thus rely on an accurate TED for LSP path computation.