Per-Peer Timeout Configuration for DIAMETER Routing Agents
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Diameter Routing Agents (DRAs) lack the ability to flexibly define and extend message processing behaviors, leading to inefficient handling of request messages in DIAMETER protocol networks due to lack of customizable timeout settings, resulting in potential network failures and unresponsive scenarios.
Innovation Solution
Implementing a method for DRAs to associate specific timeout values on a per-peer basis, allowing for customizable timeout settings for request messages, which includes initiating a timeout timer, forwarding the message, and taking preselected actions upon timer expiration, such as resending the message or sending an unable_to_deliver response.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If DRAs use fixed timeout handling for all peers, then device complexity is reduced, but adaptability to different peer response characteristics deteriorates
Solution Approach 1:
The patent implements per-peer timeout configuration where each peer can have its own customized timeout value stored in a configuration database. This allows different parts of the system (different peers) to have different timeout characteristics based on their specific response characteristics, resolving the contradiction between simplified fixed handling and adaptive peer-specific handling.
2Adaptability or versatility
If DRAs implement per-peer timeout configuration, then adaptability to different peers is improved, but device complexity increases
Solution Approach 1:
The system automatically retrieves the appropriate timeout value for each peer from the configuration database based on peer identification, and automatically manages the timeout timer without requiring manual intervention. This self-service approach reduces operational complexity while maintaining per-peer adaptability.
Solution Approach 2:
The timeout configuration mechanism serves multiple functions: it stores peer-specific timeout values, retrieves appropriate values during message processing, manages timers, and handles timeout events. This multi-functional approach consolidates complexity into a unified system rather than requiring separate mechanisms for each function.
3Ease of operation
If DRAs use standardized message processing, then ease of operation is improved, but ability to handle unresponsive peers deteriorates
Solution Approach 1:
The system pre-configures timeout values for each peer before actual message processing occurs. When a message is sent, the appropriate timeout value is already available from the configuration database, allowing immediate timer initiation without delay. This preliminary configuration enables reliable timeout handling while maintaining simple standardized processing procedures.
Data Source
AI summary
A method for per-peer request delivery timeouts includes receiving a DIAMETER message at a DIAMETER Routing Agent, testing if the DIAMETER message is a request message destined for an associated peer, and if said test is affirmative, then retrieving a preset timeout associated with that peer; initiating a timeout timer with said preset timeout; and forwarding the DIAMETER request message to said peer. The disclosure provides additional steps with respect to stopping the timer in the event that a response message is received prior to the timer expiring; or alternatively, either resending the request or providing an unable_to_deliver response in the event the timer does expire. The method for per-peer request delivery timeouts provides for fine tuning timeout periods according to the networks to which the DIAMETER peers are connected. The method is particularly useful for reducing the amount of time waiting for response messages which will not be forthcoming.