BGP Label Distribution for L3VPN Instance Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing OAM technology cannot effectively perform fault location and performance detection on L3VPN services due to the inability to identify the source end of the service.

Innovation Solution

A label distribution method and device that extend MP-BGP to allow routing devices to learn and identify VPN instances, allocate labels to these instances, and include VPN instance identifiers and route targets in BGP update messages to facilitate effective fault location and performance detection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional MPLS technology is used in IP RAN networks, then bandwidth and statistical multiplexing support are improved, but the ability to perform fault location and performance detection on L3VPN services deteriorates due to inability to identify service source ends

Engineering Contradiction:
Improvebandwidth and statistical multiplexing supportVSAvoidfault location and performance detection capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces VPN instance identifiers and route targets as intermediary elements that mediate between the L3VPN service and the underlying MPLS network. These identifiers act as mediators that enable the tail end to identify and locate the source end of the service, thereby restoring fault location and performance detection capabilities while maintaining the benefits of conventional MPLS technology.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If MPLS-TP technology is applied to simplify the data plane and reduce coupling between MPLS and IP, then ease of operation and maintenance are improved, but the complexity of identifying and managing VPN instances across multiple routing devices increases

Engineering Contradiction:
Improvedata plane simplification and reduced couplingVSAvoidVPN instance identification and management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a standardized mechanism using BGP update messages that can be universally applied across all routing devices in the MPLS-TP network. The VPN instance identifiers and route targets serve as universal keys that enable consistent identification and management of VPN instances across multiple devices, reducing the overall complexity despite the simplified data plane.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If BGP update messages are extended to include VPN instance identifiers and route targets, then fault location capability is improved, but the complexity of message processing and label distribution increases

Engineering Contradiction:
Improvefault location precisionVSAvoidmessage processing and label distribution complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-establishing the correspondence between VPN instance identifiers, route targets, and forwarding equivalence class labels through BGP update messages before actual service traffic flows. This preliminary label distribution and identifier establishment simplifies the subsequent fault location process, as the mapping relationships are already in place and do not require complex real-time processing when faults occur.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10554542B2Label distribution method and device
Publication Date: 2020.02.04 HUAWEI TECH CO LTD
  • US10554542B2 patent drawing
  • US10554542B2 patent drawing
  • US10554542B2 patent drawing

AI summary

A label distribution method and device are disclosed. In an embodiment the method includes: a first routing device sends a first BGP update message including a first VPN instance identifier and a first RT to a second routing device; the first routing device receives a second BGP update message including a second VPN instance identifier and a second RT; the first routing device allocates a first VPN instance label to a second VPN instance after the second routing device determines that the first RT is equal to the second RT; and the first routing device sends a third BGP update message including the first VPN instance label to the second routing device. Mutual learning on VPN instances is performed, and a label is allocated to a VPN instance, so that a service tail end node can identify a VPN instance from which an L3VPN service specifically comes.