BGP Extensions for RIP Routing in MPLS VPNs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing BGP/MPLS standard for VPN management fails to include necessary parameters for correct routing of data using the RIP protocol, leading to information loss and perpetual loops due to compatibility issues between RIP and BGP, requiring administrators to use different protocols and causing administrative challenges.
Innovation Solution
Extending the BGP protocol with new extensions to store information about data passage points, creating a BGP_RIP protocol that integrates RIP-specific data and uses MPLS for secure and reliable data transmission, ensuring data integrity and preventing perpetual loops.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the BGP/MPLS standard is used for VPN management, then data transmission between client networks is enabled, but information loss occurs and perpetual loops are created due to missing RIP routing parameters
Solution Approach 1:
The patent embeds RIP routing information within BGP protocol structures by nesting RIP parameters inside BGP UPDATE messages. Specifically, RIP routing parameters are placed in the MP_REACH_NLRI and MP_WITHDRAWN_LSA attributes of BGP messages, allowing RIP routing data to be transported through the BGP/MPLS infrastructure without loss, thereby preventing perpetual loops while maintaining end-to-end RIP protocol operation.
Solution Approach 2:
The patent introduces an intermediary translation mechanism at the provider edge routers that converts RIP routing information into a format suitable for BGP transport. This intermediary process involves encapsulating RIP parameters within BGP attributes, enabling seamless information transfer between the RIP-based client networks and the BGP-based provider network without information loss.
2Adaptability or versatility
If different protocols (RIP and BGP) are used in client and provider networks, then interconnection is achieved, but administrative complexity increases and protocol compatibility issues arise
Solution Approach 1:
The patent makes the BGP protocol multi-functional by enabling it to transport both its native routing information and RIP routing parameters simultaneously. Through the use of MP_REACH_NLRI and MP_WITHDRAWN_LSA attributes, BGP serves as a universal transport mechanism that can carry client-specific RIP routing data, allowing provider networks to support multiple client network protocols without requiring separate infrastructure for each protocol type.
Solution Approach 2:
The patent changes the parameter structure of BGP messages to include RIP-specific parameters. By modifying BGP UPDATE messages to contain RIP routing parameters within standardized attributes (MP_REACH_NLRI, MP_WITHDRAWN_LSA), the system maintains BGP's external routing protocol function while incorporating internal RIP routing capabilities, thereby reducing administrative complexity through parameter standardization.
3Ease of operation
If the provider network remains transparent to client networks, then seamless communication is achieved, but the provider network cannot enforce security policies or monitor traffic flow
Solution Approach 1:
The patent performs preliminary action by embedding routing information and policy parameters into BGP messages before traffic forwarding occurs. The provider edge routers use the MP_REACH_NLRI and MP_WITHDRAWN_LSA attributes to pre-configure routing paths and policy enforcement points, enabling security policies to be enforced at the provider network edge while maintaining transparency for end-user applications. This preliminary configuration allows the provider network to control traffic flow without disrupting client network operations.
Data Source
AI summary
This invention concerns a method of managing a telecommunication network (232), referred to as the provider network (232), used to transmit data between at least two telecommunication client networks (204, 222) in order to create a virtual private network (200) between the client networks (204, 222), each of these client networks (204, 222) using an internal communication protocol, referred to as the internal client protocol, and each of the client networks (204, 222) having at least one client interconnection device (206, 220, 221) communicating with at least one provider interconnection device (208, 215) of the provider network (232).According to this invention, the provider network (232) uses a communication protocol, referred to as the provider protocol, comprising extensions for the storage of information relating to the points of passage of the data in the client networks (204, 222).