VPN Hub Resource Allocation via Priority Messages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In VPN Hub-and-Spoke architectures, there is no mechanism to differentiate between critical and less critical branch devices for resource allocation, leading to inefficient resource management and potential service disruptions during outages, as all branches attempt to re-establish tunnels simultaneously, overwhelming the hub device's CPU resources.
Innovation Solution
Implementing a priority message system using connection establishment protocols like IKE, where branch devices convey their priority levels to the hub device, allowing it to allocate resources and manage tunnel setups and rekeying based on these priorities, ensuring preferential treatment for critical branches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all branches are treated equally for resource allocation, then simplicity and ease of operation are maintained, but resource management efficiency deteriorates and CPU overload occurs during outages
Solution Approach 1:
The patent applies local quality by assigning different priority levels to different branch devices based on their criticality. The hub device maintains a priority table that associates each branch with a specific priority value, enabling differentiated resource allocation. Critical branches receive higher priority for CPU resources during tunnel re-establishment, while less critical branches receive lower priority, thus improving resource management efficiency without requiring complete system redesign.
2Reliability
If priority differentiation is implemented, then resource allocation efficiency improves, but system complexity increases due to priority messages and allocation logic
Solution Approach 1:
The patent implements preliminary action by having branch devices include their priority information in the initial IKE connection establishment messages (such as IKE_SA_INIT or IKE_AUTH). The hub device receives and stores these priorities in advance in a priority table before any outage occurs. This pre-configured priority information is then automatically used during tunnel re-establishment after outages, ensuring service reliability for critical branches without requiring complex real-time priority negotiation or additional protocol complexity during critical events.
3Productivity
If simultaneous tunnel re-establishment is allowed for all branches, then ease of operation is maintained, but CPU resource overload occurs during outages
Solution Approach 1:
The patent applies periodic action by implementing a rate-limiting mechanism that controls the timing and frequency of tunnel re-establishment attempts based on branch priority. Critical branches are permitted to re-establish tunnels with higher frequency and lower delay, while less critical branches experience rate-limiting that spreads their re-establishment attempts over time. This priority-based rate limiting prevents CPU overload during outages while maintaining automatic failover capability, as all branches ultimately recover but at different rates determined by their priority levels.
Data Source
AI summary
In one embodiment, a first network device receives a priority message from a second network device, wherein the priority message conforms to a connection establishment protocol and indicates a priority associated with the second network device. The first network device obtains the priority from the priority message and stores the priority. The first network device allocates resources for at least one of control or data plane processing to the second network device in accordance with the priority.


