Diameter Routing Agent Session Deletion in Roaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods fail to effectively delete session information in the Diameter Routing Agent (DRA) when terminating a Diameter session, particularly in the roaming scenario, leading to incomplete or inaccurate session termination.
Innovation Solution
A method is proposed that involves sending a request message to both the visited and home Diameter Routing Agents (DRAs) to mark the Diameter session as terminated, using session identifiers to ensure accurate deletion of session information, regardless of the DRA modes (Redirect or Proxy) employed by the visited and home DRAs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the DRA saves session information to enable correct association of PCEF, BBERF and AF with PCRF, then the DRA can select the same PCRF for all IP-CAN sessions of a UE, but when the DRA needs to delete session information upon Diameter session termination, the existing mechanism fails to ensure complete deletion across both visited and home DRAs in roaming scenarios
Solution Approach 1:
The patent segments the session information deletion process into two independent parts: visited DRA deletion and home DRA deletion. Each DRA independently processes deletion requests for the sessions it manages, rather than relying on a single centralized deletion mechanism. This segmentation ensures that both DRAs can reliably delete their respective session information without complex coordination overhead.
Solution Approach 2:
The patent applies preliminary action by having the visited DRA mark sessions as terminated before the home DRA processes deletion. The visited DRA proactively notifies the home DRA about session termination, allowing the home DRA to prepare for and execute deletion of its session information. This preliminary notification ensures complete deletion across both DRAs.
2Measurement precision
If the DRA maintains detailed session information including NAI, IP address, and APN to uniquely identify IP-CAN sessions, then accurate session identification is achieved, but the deletion process becomes complex when multiple DRAs (visited and home) need to coordinate deletion in roaming scenarios
Solution Approach 1:
The patent extracts the essential session identification information (session identifier) from the complete session context and uses it as the key for deletion operations. Instead of transmitting or comparing complete session information including NAI, IP address, and APN between DRAs, the system extracts and uses only the session identifier for the deletion process. This simplifies the deletion coordination while maintaining accurate session identification.
Solution Approach 2:
Instead of having the home DRA query the visited DRA for session information to determine what to delete, the patent inverts the approach: the visited DRA actively notifies the home DRA about session termination. This inversion simplifies the deletion process by eliminating the need for complex information exchange and matching, as the home DRA receives direct deletion notifications from the visited DRA.
3Adaptability or versatility
If the system uses Redirect mode or Proxy mode for DRA operation, then flexibility in session management is improved, but the deletion mechanism must handle both modes uniformly, increasing the complexity of ensuring complete session information deletion
Solution Approach 1:
The patent creates a universal deletion mechanism that functions identically regardless of whether the DRA operates in Redirect mode or Proxy mode. The deletion process uses the same notification and marking procedures for both modes, eliminating the need for mode-specific deletion logic. This universal approach maintains adaptability while reducing complexity by treating both modes uniformly.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention discloses a method for deleting session information in Diameter Routing Agent, this method comprises: sending a request message for deleting the Diameter session to a visited Diameter Routing Agent DRA and a visited policy and charging rules function PCRF by a policy and charging control client; after the visited DRA receives the request message, the visited DRA marking the Diameter session as termination in the visited DRA; after the visited PCRF receives the request message, the visited PCRF sending a message requesting to delete the Diameter session information to a home DRA, the home DRA marking the Diameter session in the home DRA as termination. In the present invention, the session information in the DRA may be effectively deleted when the BBERF entity, the PCEF entity or the AF entity terminates the Diameter session between the local and the PCRF entities.