Centralized Address Pool Management via RPC Interface
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for allocating IPv4 addresses to provider edge devices are inefficient, leading to delays in customer session setup due to slow address allocation, which consumes computing and networking resources and results in lost traffic and stalled transmissions.
Innovation Solution
A network device interface that supports centralized address pool management using an RPC-based interface for sub-second provisioning of address pool prefixes, allowing smaller prefix sizes and reducing resource consumption by optimizing address allocation processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If traditional address allocation methods are used, then address pools are established, but address allocation is slow causing delays in customer session setup
Solution Approach 1:
The system performs preliminary actions by pre-establishing address pools and synchronizing domain and address pool information between the first device and second device before actual address allocation is needed. This includes exchanging sync domains RPC requests and sync pools RPC requests to prepare the allocation infrastructure in advance, enabling rapid address assignment when customers connect.
2Productivity
If address pools are pre-established, then address allocation can proceed, but computing and networking resources are consumed
Solution Approach 1:
The system implements self-service mechanisms where the first device automatically monitors address pool thresholds and triggers synchronization operations only when needed. The RPC-based interface enables automated domain and address pool synchronization without manual intervention, reducing unnecessary resource consumption while maintaining allocation efficiency.
3Productivity
If centralized address pool management is implemented, then address allocation is optimized, but system complexity increases
Solution Approach 1:
The system employs a universal RPC-based interface that handles multiple functions including connection establishment, domain synchronization, address pool synchronization, and threshold monitoring through a unified communication protocol. This multi-functional interface reduces the need for separate specialized components, managing system complexity while enabling centralized address pool management.
Data Source
AI summary
A first device may establish a connection with a second device, and may provide a connection check RPC message to the second device. The first device may receive a verification RPC message from the second device, and may provide, to the second device, a sync domains RPC request that includes a first list of active domains with associated address pools. The first device may receive, from the second device, a sync domains RPC response that includes threshold values for the active domains included in the first list of active domains, and may provide, to the second device, a sync pools RPC request that includes a first list of address pools associated with the active domains. The first device may receive, from the second device, a sync pools RPC response that includes confirmation of the first list of address pools, and may allocate addresses of an address pool to a CPE.