Destination-Based Bandwidth Control for Enterprise VPN Switches
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional VPN service networks lack the ability to dynamically control bandwidth based on the final destination of user traffic, leading to high communication costs for enterprises promoting resource centralization to a data center, as all local branch sites must be assigned broad bandwidth, regardless of traffic destination.
Innovation Solution
A communication network system with separate bandwidth controllers for local-branch-site-line and data-center-site-line network switches, allowing for pre-selected bandwidths to be assigned for communications between local-branch-site-line switches, data-center-site-line switches, and the carrier network, enabling flexible bandwidth allocation based on traffic destinations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all local branch sites are assigned broad common bandwidth in conventional VPN service networks, then communication reliability between data center and local branch sites is improved, but communication costs increase significantly
Solution Approach 1:
The patent implements destination-based bandwidth control where different bandwidth allocations are applied to different traffic destinations. Specifically, traffic destined for the data center receives broader bandwidth allocation, while traffic between local branch sites receives narrower bandwidth allocation. This local quality differentiation resolves the contradiction by providing high reliability only where needed (data center communications) rather than uniformly across all communications, thereby reducing overall communication costs.
Solution Approach 2:
The patent dynamically changes bandwidth parameters based on traffic destination identification. The system identifies whether packets are destined for the data center or other local branch sites, and then applies different bandwidth control parameters accordingly. This parameter change strategy allows the system to maintain communication reliability for critical data center traffic while reducing bandwidth allocation (and costs) for less critical inter-branch traffic.
2Loss of energy
If separate bandwidth control based on final destination is implemented, then communication cost efficiency is improved, but device complexity increases due to additional bandwidth controllers and identification mechanisms
Solution Approach 1:
The patent segments the bandwidth control function into separate dedicated controllers: a first bandwidth controller for limiting bandwidth of packets destined for local branch sites, and a second bandwidth controller for limiting bandwidth of packets destined for the data center. This segmentation allows each controller to be optimized for its specific function and simplifies the overall control logic compared to a single complex controller that would need to handle all destinations. The segmentation also enables independent configuration and management of bandwidth parameters for different traffic types.
Solution Approach 2:
The patent introduces destination identification mechanisms as intermediary components that sit between packet reception and bandwidth control application. These intermediaries (destination identification sections in network switches) analyze packet destinations and route packets to the appropriate bandwidth controller based on whether the destination is a local branch site or the data center. This intermediary layer abstracts the complexity of destination-based routing from the bandwidth control logic itself, making the system more manageable and maintainable.
3Productivity
If broader bandwidth is assigned for data center communications, then resource centralization efficiency is improved, but bandwidth allocation flexibility is reduced when local branch site communications are considered
Solution Approach 1:
The patent implements dynamic bandwidth allocation that adapts to traffic patterns and destination requirements. Rather than assigning fixed bandwidth to all connections, the system dynamically adjusts bandwidth allocation based on real-time destination identification. Traffic to the data center receives broader bandwidth allocation to support resource centralization operations, while traffic between local branch sites receives narrower allocation. This dynamic approach allows the system to be flexible and adaptive to different communication scenarios while still prioritizing data center communications for resource centralization efficiency.
Data Source
AI summary
A communication network system is disclosed in which local-branch-site-line network switches accommodating local-branch-site lines, and at least one data-center-site-line network switch accommodating at least one data-center-site line, are interconnected via a carrier network. This system include: a first bandwidth controller, disposed at each local-branch-site-line network switch, configured to limit a bandwidth of each of inbound packets and/or outbound packets to a pre-selected bandwidth α, wherein the inbound packets flow from the instant local-branch-site-line network switch or other local-branch-site-line network switches, and the outbound packets flow to the instant local-branch-site-line network switch or other local-branch-site-line network switches; and a second bandwidth controller, disposed at each local-branch-site-line network switch, configured to limit a bandwidth of each of inbound packets and/or outbound packets to a pre-selected bandwidth β broader than the bandwidth α, wherein the inbound packets flow from the data-center-site-line network switch, and the outbound packets flow to the data-center-site-line network switch.