Token Bucket Shared Bandwidth Speed Limiting

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional firewall equipment cannot implement a shared speed limit for IP addresses at different network outlets in different regions, limiting network service providers' ability to manage bandwidth effectively across diverse locations.

Innovation Solution

A shared bandwidth speed-limiting method and device that utilize a token bucket algorithm, where customer premise equipment reports token surplus or deficiency to a central controller, allowing reallocation of tokens across distributed apparatuses with different network outlets, enabling flexible bandwidth subscription and improved resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional firewall equipment is used to implement speed limiting, then independent speed limit for single IP address can be achieved, but shared speed limit for multiple IP addresses at different network outlets cannot be implemented

Engineering Contradiction:

Improveshared bandwidth capabilityVSAvoidsystem architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system divides the speed limiting function into two independent parts: local token bucket implementation at each CPE for real-time bandwidth control, and central controller for token reallocation across multiple network outlets. This segmentation enables shared bandwidth capability while maintaining manageable system complexity through clear separation of concerns.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A central controller is introduced as an intermediary to coordinate token reallocation among multiple CPEs. The central controller receives statistical information reports from distributed CPEs and performs centralized token reallocation based on actual bandwidth usage patterns across different network outlets, enabling shared bandwidth without requiring complex peer-to-peer communication between CPEs.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If fixed bandwidth allocation is used for each network outlet, then simple implementation is achieved, but bandwidth resource utilization efficiency decreases

Engineering Contradiction:

Improvebandwidth resource utilizationVSAvoidbandwidth management

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The system implements dynamic bandwidth allocation through token reallocation based on actual usage patterns. The central controller continuously receives statistical information reports from CPEs and adjusts token distribution dynamically, allowing bandwidth to flow to network outlets with higher demand while maintaining overall resource efficiency. This dynamic approach replaces static fixed allocation with adaptive resource distribution.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system establishes a feedback loop where CPEs send statistical information reports to the central controller about their token bucket status and bandwidth usage. The central controller uses this feedback to make informed reallocation decisions, adjusting token distribution to optimize bandwidth utilization across the network while maintaining ease of operation through automated control.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If centralized token reallocation is implemented across distributed CPEs, then flexible bandwidth subscription is achieved, but communication overhead between CPEs and central controller increases

Engineering Contradiction:

Improveflexible bandwidth subscriptionVSAvoidcommunication data volume

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Instead of continuously exchanging detailed bandwidth usage data, the system uses periodic statistical information reports at preset time intervals. This partial action approach provides sufficient information for token reallocation decisions without the excessive communication overhead of continuous monitoring, achieving flexible bandwidth subscription with manageable data transmission volumes.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11784885B2Shared bandwidth speed limiting method, device, and storage medium

Publication Date: 2023.10.10 APPEX NETWORKS CORP

AI summary

The present disclosure relates to the field of communication technologies, in particular to a shared bandwidth speed-limiting method, device, and storage medium. The method for customer premise equipment comprises: adding a token into a token bucket of the customer premise equipment based on an initial bandwidth rate; and sending a statistical information report to a central controller every preset time interval, wherein the statistical information report represents a report reflecting a surplus or deficiency condition of tokens in the token bucket, and is configured to instruct the central controller to reallocate tokens of the customer premise equipment by a central token bucket. In embodiments, a token bucket algorithm is introduced to a distributed environment with a central controller, so that at least two pieces of customer premise equipment in distributed apparatuses can share a speed-limiting bandwidth, providing more flexible bandwidth subscription options and further improving the utilization of bandwidth resources.