Token Bucket Traffic Limiting Shared Timestamp Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Token bucket-based traffic limiting methods in data communication networks lead to over-occupation of storage resources and high hardware costs due to the need for each token bucket to store its own timestamp, resulting in inefficient memory usage and increased costs.
Innovation Solution
A token bucket-based traffic limiting method where a shared timestamp is used across multiple token buckets, allowing the number of tokens filled in each bucket to be determined based on the arrival time of packets and a preset token filling rate, thereby reducing the need for individual timestamps and optimizing storage and hardware usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each token bucket stores its own timestamp, then traffic limiting accuracy is maintained, but storage resources are over-occupied and hardware cost increases
Solution Approach 1:
Multiple token buckets share a common timestamp storage resource instead of each bucket having its own timestamp. The timestamp is updated when any token bucket in the set is filled, and all buckets use this shared timestamp for their token calculations, thereby reducing storage overhead while maintaining traffic limiting accuracy.
Solution Approach 2:
The shared timestamp serves multiple token buckets simultaneously, performing the time-tracking function for all buckets in the set. This universal timestamp resource replaces multiple individual timestamp resources, achieving the same functional purpose with reduced storage requirements.
2Ease of operation
If each token bucket stores its own timestamp, then individual bucket tracking is simplified, but hardware cost increases
Solution Approach 1:
The patent merges the timestamp storage function across multiple token buckets into a single shared timestamp resource. This reduces hardware cost by eliminating redundant timestamp storage while the system maintains ease of operation through centralized timestamp management that automatically serves all buckets in the set.
Data Source
AI summary
The embodiments of the present invention disclose a token bucket-based traffic limiting method, including: when a packet is received, triggering a filling operation of filling each token bucket in a token bucket set under a scheduling node corresponding to the packet, where the token bucket set includes at least two token buckets; determining the number of tokens filled in each token bucket in the token bucket set according to a moment when the packet is received and a timestamp shared by the token bucket set; and if the number of tokens in a token bucket corresponding to the packet exceeds a length of the packet, allowing the packet to pass through the scheduling node and removing the number of tokens, corresponding to the length of the packet, from the token bucket corresponding to the packet.