Cross-Domain Pseudowire Configuration via Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current pseudowire configurations across multiple autonomous systems in computer networks require complex routing protocols like BGP, burdening service providers with advanced software and configuration requirements, especially for customer-side ingress and egress devices.
Innovation Solution
The techniques enable dynamic configuration of cross-domain pseudowires without necessitating the use of BGP or other layer three routing protocols on customer-side devices, allowing intermediate devices to handle protocol transformations, thereby simplifying the configuration process and reducing administrative burdens.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If BGP or other layer three routing protocols are used for dynamic configuration of cross-domain pseudowires, then dynamic configuration capability is improved, but device complexity and administrative burden increase
Solution Approach 1:
The patent segments the protocol handling responsibilities by introducing intermediate devices that perform protocol translation between LDP and BGP. Customer-side ingress and egress devices are separated from the complex BGP protocol requirements, which are instead implemented on intermediate network devices. This segmentation allows dynamic configuration capability while reducing the complexity burden on customer devices.
Solution Approach 2:
The patent introduces intermediate devices as mediators between customer devices and the BGP routing infrastructure. These intermediate devices translate LDP messages from customer devices into BGP routing protocol messages, enabling cross-domain pseudowire dynamic configuration without requiring customer devices to implement complex routing protocols. The intermediary handles the protocol transformation and complexity.
2Reliability
If BGP peering sessions are established between ingress and egress devices for MS-PW information exchange, then cross-domain pseudowire establishment is improved, but ease of operation deteriorates
Solution Approach 1:
The patent extracts the BGP peering session requirement from customer-side ingress and egress devices and relocates it to intermediate network devices. The LDP-based configuration process on customer devices remains simple and unchanged, while intermediate devices handle the complex BGP peering and information exchange necessary for reliable cross-domain pseudowire establishment.
3Device complexity
If protocol transformation is performed by intermediate devices, then customer device complexity is reduced, but intermediate device processing requirements increase
Solution Approach 1:
The intermediate devices perform self-service by automatically translating LDP messages into BGP routing protocol messages without requiring manual configuration or intervention. The translation process is handled autonomously by the intermediate device's protocol translation mechanism, reducing the administrative burden while managing the processing requirements through automated operations.
Data Source
AI summary
In general, techniques are described for dynamically configuring cross-domain pseudowires (PWs). A network device positioned between a first domain and a second domain of a computer network may implement the techniques. The intermediate network device comprises at least one interface and an LDP module, a transformation module and a routing protocol module. The interface receives a label distribution protocol (LDP) message that includes data for configuring a cross-domain PW from a first provider edge (PE) device of the first domain. The LDP module parses the received LDP message to extract the cross-domain PW configuration data. The translation module transforms the extracted data to conform to routing protocol extensions for advertising the cross-domain PW configuration data. The routing protocol module forms a routing protocol message that includes the transformed data. The interface outputs the routing protocol message to the second intermediate device of the second domain to establish the cross-domain PW.