Service-Based Route Target Allocation for MPLS VPN Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and troubleshooting Multi-Protocol Label Switching (MPLS) Virtual Private Networks (VPNs) is challenging due to the complexity of route target management in centralized systems, making it difficult to identify and address issues without intensive computation and holistic knowledge.

Innovation Solution

A network management system that allocates and provisions service-based route targets, using a service-based route target allocator to generate unique identifiers for service providers and services, and converts data for meaningful display, facilitating easier management and troubleshooting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized management system is used to manage VPNs, then route targets can be provisioned and displayed, but managing and troubleshooting becomes difficult without intensive computation and holistic knowledge

Engineering Contradiction:
ImproveVPN management easeVSAvoidmanagement system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the route target management by introducing service identifiers that divide the complex routing information into manageable service-based units. Each service identifier represents a specific service instance, allowing administrators to manage VPNs by service rather than by individual route targets, thereby reducing the cognitive load and simplifying troubleshooting while maintaining comprehensive control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces service identifiers as intermediary elements between the administrative view and the actual route target configuration. These service identifiers act as mediators that translate complex routing policies into service-level abstractions, making the management system more user-friendly while preserving the underlying complexity for automated processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If route targets are managed as a list without service context, then comprehensive control is maintained, but identification and troubleshooting of specific VPN issues becomes difficult

Engineering Contradiction:
ImproveVPN issue identification precisionVSAvoidservice context information
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent applies local quality by attaching service-specific identifiers and attributes to each route target entry. Instead of treating all route targets uniformly, the system adds localized service context (such as service type, service provider, and service instance) to each entry, enabling precise identification and troubleshooting of specific VPN issues while maintaining the overall list structure for comprehensive control.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8072991B2Allocation of route targets based on service offered
Publication Date: 2011.12.06 CISCO TECHNOLOGY INC
  • US8072991B2 patent drawing
  • US8072991B2 patent drawing
  • US8072991B2 patent drawing

AI summary

A network controller to allocate route targets for communication services provided on one or more corresponding virtual private networks, the route targets identifying service providers associated with the virtual private networks and the communication services provided by the corresponding virtual private networks.