Traffic Scheduling with Nested User and Port-Level Queues
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current HQoS strategies in network communication devices fail to simultaneously perform user-level and port-level scheduling and flow limiting due to independent configurations on sub-interfaces or ports, limiting their ability to manage complex multi-service scenarios effectively.
Innovation Solution
Implement a two-stage scheduling process where service traffic is first scheduled at a user-level based on sub-interfaces and then at a port-level, using pre-configured mapping relationships and ACL tables to identify and prioritize queues for simultaneous user-level and port-level scheduling and flow limiting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If HQoS strategy is configured on sub-interface, then user-level scheduling and flow limiting can be performed, but port-level scheduling and flow limiting cannot be performed simultaneously
Solution Approach 1:
The patent divides the scheduling system into two independent modules: a first scheduling module configured on sub-interfaces for user-level scheduling, and a second scheduling module configured on ports for port-level scheduling. This segmentation allows each module to operate independently without conflict, enabling both user-level and port-level scheduling to function simultaneously.
Solution Approach 2:
The patent implements a nested scheduling structure where the first scheduling module (user-level) and second scheduling module (port-level) are hierarchically organized. The sub-interface scheduling operates within the broader port-level scheduling framework, creating a nested relationship that enables multi-level traffic management without interference.
2Ease of operation
If HQoS policy is configured on port, then port-level scheduling and flow limiting can be performed, but user-level scheduling and flow limiting cannot be performed simultaneously
Solution Approach 1:
The patent separates the scheduling functions into distinct modules: the first scheduling module handles port-level scheduling when configured on ports, while the second scheduling module handles user-level scheduling when configured on sub-interfaces. This segmentation enables the system to adapt to different configuration scenarios and perform both types of scheduling simultaneously.
Solution Approach 2:
The patent creates a dynamic scheduling system where the scheduling behavior can adapt based on configuration. The system can dynamically switch between or combine port-level and user-level scheduling depending on where the HQoS policy is applied, providing flexibility and versatility in traffic management.
3Device complexity
If single-level scheduling is implemented, then device complexity is reduced, but ability to manage complex multi-service scenarios is limited
Solution Approach 1:
The patent divides the complex scheduling task into two manageable segments: first scheduling module for one level of scheduling and second scheduling module for another level. This segmentation reduces the complexity of each individual module while collectively providing comprehensive multi-service scenario management capability.
Solution Approach 2:
The patent adds an additional dimension to the scheduling system by implementing two-level scheduling with different configuration levels (sub-interface and port). This dimensional expansion enables the system to handle complex multi-service scenarios without proportionally increasing overall system complexity, as each dimension operates semi-independently.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The embodiments of the present application relate to the technical field of communications. Disclosed are a traffic scheduling method, an electronic device and a storage medium. In the present application, the method includes: acquiring service traffic received at a data receiving port; performing a first scheduling on the service traffic according to a preset first scheduling strategy, where the first scheduling strategy is a user-level scheduling strategy; forwarding the service traffic on which the first scheduling is performed to the data receiving port; performing a second scheduling on the service traffic according to a preset second scheduling strategy, where the second scheduling strategy is a port-level scheduling strategy; and sending the service traffic on which the second scheduling is performed through a data sending port.