Priority-Based Message Traffic Shaping for Network Congestion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current message traffic shaping solutions fail to consider non-compliant operating behavior and are inefficient due to lack of scalability and restriction to single network elements, often arbitrarily discarding messages based on quantity rather than traffic classifications.
Innovation Solution
A system and method for priority and compliance-based message traffic shaping, where an egress function aggregates traffic, provides dynamic update data to ingress functions, and adjusts outgoing message traffic rates based on message processing capacity thresholds and client compliance, allowing for strategic discarding or rerouting of non-compliant traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic shaping solutions arbitrarily discard messages based on quantity or volume, then network resources are protected from congestion, but traffic-related classifications and metrics such as non-compliant operating behavior are not considered
Solution Approach 1:
The patent applies local quality by treating different message traffic differently based on its characteristics. Ingress functions classify messages from different source IP addresses and apply different shaping policies to each source, rather than applying a uniform discard policy to all traffic. This allows the system to protect network resources while considering traffic-specific metrics like compliance behavior.
Solution Approach 2:
The system dynamically changes the parameter of message discard rate for each ingress function based on aggregated traffic metrics. The egress function monitors the aggregate message rate and adjusts individual source discard rates proportionally, transforming the static arbitrary discard approach into a dynamic parameter-adjusted system that considers traffic classifications.
2Ease of manufacture
If traffic shaping solutions are implemented at a single network element or device, then implementation is simplified, but scalability is limited
Solution Approach 1:
The patent implements a multi-functional traffic shaping system where egress functions can serve multiple ingress functions from different source IP addresses. The egress function aggregates traffic metrics and provides dynamic update data to multiple ingress functions, allowing a single egress function to perform traffic shaping for multiple sources, thereby improving scalability without significantly increasing implementation complexity.
Solution Approach 2:
The system segments traffic shaping functionality into distinct ingress functions and egress functions. Each ingress function handles traffic from a specific source IP address, while the egress function aggregates and coordinates shaping across multiple sources. This segmentation allows the system to scale to multiple network elements while maintaining manageable complexity through clear functional separation.
3Productivity
If dynamic update data is sent to multiple ingress functions, then traffic rates can be adjusted based on server capacity, but network communication overhead increases
Solution Approach 1:
The egress function sends dynamic update data containing aggregate traffic metrics to multiple ingress functions. Rather than each ingress function independently monitoring and reporting traffic, the egress function performs the aggregation and distributes the results, reducing redundant communication and optimizing the balance between coordination overhead and traffic optimization benefits.
Data Source
AI summary
According to one aspect, the disclosed subject matter describes herein a method that includes aggregating, by an egress function, message traffic directed to a target server entity from each of a plurality of ingress functions and procuring, by the egress function, dynamic update data that includes a message processing capacity threshold value associated with the target server entity and an aggregated message traffic rate corresponding to the message traffic received from the plurality of ingress functions. The method further includes sending the dynamic update data to each of the plurality of ingress functions and adjusting, by each of the ingress functions, an outgoing message traffic rate directed to the target server entity in accordance with the dynamic update data.