Indirect BGP Routing via Pointer Identification Lists
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software-defined networks (SDNs) with virtualized network functions, managing route targets (RTs) for multiple virtual routing and forwarding instances (VRFs) is complex, leading to scalability issues and the need for frequent updates across thousands of VRFs when new services are added, as each VRF must individually import and export unique RTs, limiting the number of services a single VRF can interact with.
Innovation Solution
A system using a pointer identification list that stores route targets associated with virtual routing and forwarding instances, allowing a provider edge router to direct routes to the appropriate VRFs based on the list, eliminating the need for individual updates of each VRF and enabling indirect BGP routing, thus simplifying the process and improving scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If each virtual routing and forwarding instance individually imports and exports unique route targets, then routing precision and service isolation are improved, but device complexity and management overhead increase significantly
Solution Approach 1:
The patent segments the route target management by introducing pointer identification lists that separate the routing logic from individual VRF instances. Each VRF maintains its own import/export route target configurations, but the actual route distribution is managed through centralized pointer lists that reference these configurations, reducing the complexity of direct one-to-one management between VRFs and routes.
Solution Approach 2:
The patent introduces pointer identification lists as intermediary structures between the BGP routing system and individual VRF instances. These pointer lists act as mediators that translate route target matching into VRF instance selections, simplifying the management overhead by providing an intermediate layer that handles the complexity of route-VRF mapping without requiring direct configuration changes in each VRF.
2Ease of operation
If a central pointer identification list is used to manage route targets, then ease of operation and scalability are improved, but the system requires additional data structures and processing logic
Solution Approach 1:
The patent implements pointer identification lists that essentially create copies or references to route target configurations rather than managing the actual route target data directly in each VRF. This copying approach allows centralized management through the pointer lists while maintaining the integrity and isolation of individual VRF route target definitions, reducing operational complexity.
Solution Approach 2:
The pointer identification lists serve multiple functions: they store route target mappings, control VRF instance selection, and enable scalable route management. This multi-functionality reduces the need for separate management mechanisms and simplifies operations by providing a universal structure that handles various routing management tasks.
3Reliability
If individual VRF updates are performed for each new service, then routing reliability is improved, but productivity and update speed decrease
Solution Approach 1:
The patent prepares route target configurations and pointer identification lists in advance, so that when new services are deployed, the routing infrastructure is already configured to handle them. This preliminary setup allows for faster service deployment while maintaining reliability, as the pointer lists are pre-configured to match route targets without requiring real-time configuration changes during service deployment.
Data Source
AI summary
A system for indirect border gateway routing may include a provider edge router, virtual routing and forwarding instance, a point identification list, and a virtual routing and forwarding import instance. The virtual routing and forwarding import instance may be adapted to receive a route from the provider edge router, in which the route may include a pointer identification directing the virtual routing and forwarding import instance to scan the pointer identification list for the route target associated with multiple virtual routing and forwarding instances. The virtual routing and forwarding import instance may be adapted to import the route to at least one virtual routing and forwarding instance having a route target on the pointer identification list.