Diameter Protocol Rate Adaptation via Window Size Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Diameter Base Protocol lacks effective rate control mechanisms, leading to communication congestion and potential buffer overflow in scenarios with high signaling loads, particularly in 'super' applications like 3GPP Gx and Gy, where millions of concurrent sessions can result in connection issues and dropped requests, especially during peak times.
Innovation Solution
Implementing a communication window size mechanism where each AAA node announces and updates its maximum outstanding request capacity to peers, allowing for end-to-end rate control and priority scheduling to manage congestion and ensure reliable signaling, especially for emergency and priority services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If the Diameter Base Protocol is used for AAA applications with high signaling loads, then the protocol supports millions of concurrent sessions, but communication congestion and buffer overflow occur
Solution Approach 1:
The patent applies preliminary action by having communication nodes proactively announce their communication window sizes (maximum outstanding request capacities) to peers before congestion occurs. This allows peers to pre-adjust their request rates and avoid sending requests that would cause buffer overflow, thereby maintaining communication reliability while supporting high session volumes.
Solution Approach 2:
The patent implements feedback mechanisms where communication nodes continuously monitor their buffer states and dynamically update their window sizes. These window size announcements are fed back to peers, enabling real-time rate adaptation. This feedback loop allows the system to maintain reliable communication under high load by automatically adjusting request rates based on current buffer conditions.
2Reliability
If rate control mechanisms are added to the Diameter Base Protocol, then communication congestion is reduced, but the protocol complexity increases
Solution Approach 1:
The patent achieves rate control using existing Diameter protocol message types and structures, making the rate control mechanism universal across all Diameter applications. The window size announcements are carried within standard Diameter messages, avoiding the need for separate complex control protocols and maintaining compatibility with the existing Diameter infrastructure.
Solution Approach 2:
The patent introduces rate control by adding window size parameters to existing Diameter messages rather than creating entirely new message types. This parameter-based approach allows rate control functionality to be integrated into the existing protocol framework with minimal complexity increase, as nodes can implement rate adaptation by processing and generating these parameter fields within standard message exchanges.
3Ease of operation
If the default Peer watchdog timer is set to 30 seconds as recommended, then the protocol is simple to operate, but connection problems are not detected quickly in high-frequency signaling scenarios
Solution Approach 1:
The patent applies dynamics by allowing communication nodes to adaptively adjust their watchdog timer values based on the signaling frequency and load conditions. In high-frequency signaling scenarios, nodes can dynamically reduce the watchdog timer interval to detect connection problems faster, while in normal conditions the longer 30-second interval can be used to maintain simplicity. This dynamic adjustment resolves the contradiction between ease of operation and timely connection detection.
Data Source
AI summary
The present solution relates a method in a first communication node (301) for rate adaptation of communication between the first communication node (301) and at least one second communication node (302). The first communication node (301) and the at least one second communication node (302) being comprised in a communication network (300). The first communication node (301) receives a message from the second communication node (302). The message comprises a communication window size of the second communication node (302). The communication window size of the second communication node (302) is stored. Then, the first communication node (301) obtains the communication window size of the first communication node (301), i.e. its own communication window size. The first communication node (301) transmits a message to the second communication node (302). The message comprises the obtained communication window size of the first communication node (301).