Time Weighted Queuing Scheduler for M2M Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Machine-to-machine (M2M) communication networks face challenges in managing unpredictable and varied traffic flows, leading to over- or under-dimensioning of networks and difficulties in prioritizing data according to different quality of service requirements across various applications.
Innovation Solution
Implementing a gateway that manages M2M traffic by assigning priority levels and determining holding times and outgoing traffic rates based on the type of traffic, ensuring that high-priority traffic is transmitted before low-priority traffic, thereby stabilizing network resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If M2M traffic is managed without priority levels, then network simplicity is maintained, but quality of service requirements cannot be met for different applications
Solution Approach 1:
The patent segments M2M traffic into different priority levels (high, medium, low) and assigns them to separate queues. This segmentation enables differentiated quality of service treatment while maintaining a relatively simple overall structure by using standard queuing mechanisms rather than complex custom scheduling algorithms.
Solution Approach 2:
The patent applies local quality by treating different traffic types differently based on their priority levels. Each queue has its own holding time and transmission characteristics, allowing high-priority traffic to receive preferential treatment while low-priority traffic waits longer, thus meeting diverse QoS requirements without requiring complete system redesign.
2Reliability
If network is over-dimensioned to handle peak traffic, then reliability during peak loads improves, but network resources are wasted during low traffic periods
Solution Approach 1:
The patent implements dynamic traffic management by adjusting holding times and transmission rates based on current traffic conditions and priority levels. The system can adaptively manage network resources rather than maintaining fixed over-capacity infrastructure, reducing waste during low traffic periods while ensuring reliability when needed through priority-based queuing.
3Loss of time
If all M2M traffic is treated equally, then device complexity is minimized, but critical applications cannot receive timely data transmission
Solution Approach 1:
The patent segments traffic into priority-based queues, allowing critical high-priority applications to be transmitted with lower latency while non-critical traffic waits in lower-priority queues. This segmentation achieves differentiated latency treatment using well-understood queuing mechanisms rather than complex adaptive scheduling algorithms.
Data Source
AI summary
A device may receive machine-to-machine (M2M) traffic associated with two or more M2M applications. The M2M traffic may include information that identifies two or more priority levels associated with the M2M traffic. The device may determine parameters associated with managing the M2M traffic. The device may determine a traffic rate, an overall holding time, and an outgoing traffic rate associated with the M2M traffic. The device may determine a normalization factor based on the overall holding time and the parameters. The device may determine a set of priority level holding times based on the normalization factor, the overall holding time, and the parameters. Each priority level holding time may be associated with a priority level of the two or more priority levels. The device may manage the M2M traffic based on the set of priority level holding times and the outgoing traffic rate.