Hybrid Session Diameter Routing via Binding Repository
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Diameter-based network service node assignment methods face challenges in identifying and correlating subsequent signaling messages with the initial transaction, leading to incorrect routing of Diameter signaling messages in telecommunications networks.
Innovation Solution
Implementing a hybrid session-based Diameter routing system that uses a Diameter signaling router (DSR) with a binding repository (HE-SBR) to store exception binding records, allowing for dynamic node selection and routing of messages through load balancing hashing functions, minimizing the need for maintaining state or binding records for each session.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional Diameter routing methods are used to assign network service nodes, then routing decisions can be made based on available information, but subsequent signaling messages cannot be correctly correlated with the initial transaction, leading to incorrect routing
Solution Approach 1:
The solution segments the routing information into two parts: a centralized binding repository that stores session correlation information (binding records) and distributed Diameter routing nodes that make routing decisions. This segmentation allows the binding repository to maintain session state information while routing nodes remain relatively stateless, solving the problem of correlating subsequent messages with initial transactions.
Solution Approach 2:
The binding repository acts as an intermediary between the Diameter signaling router and the network service nodes. It receives binding information from the signaling router, stores it, and provides routing decisions back to the router. This intermediary maintains the session correlation information that would otherwise be lost, enabling accurate routing of subsequent messages.
2Reliability
If binding records are maintained for each session to ensure correct routing, then message correlation is improved, but memory resource usage increases significantly
Solution Approach 1:
The solution merges the binding record storage function into a centralized binding repository that is shared across multiple Diameter routing nodes. Instead of each routing node maintaining separate binding records (multiplying memory usage), they share a single centralized repository, reducing total memory resource usage while maintaining message correlation capability.
Solution Approach 2:
The binding repository serves multiple functions: it stores binding information for session correlation, provides routing decisions to multiple routing nodes, and maintains a global view of session state. This multi-functionality eliminates the need for redundant binding records at each routing node, optimizing memory usage.
3Reliability
If a centralized binding repository is implemented to maintain session state, then correct routing is achieved, but system complexity increases
Solution Approach 1:
The solution extracts the session state management function from the Diameter routing nodes and places it in a separate binding repository. This extraction simplifies the routing nodes (making them relatively stateless) while concentrating the complexity in a dedicated repository designed for state management, thereby organizing system complexity rather than simply increasing it.
Solution Approach 2:
The solution introduces a new architectural dimension by separating the control plane (binding repository for state management) from the data plane (routing nodes for message forwarding). This dimensional separation allows each component to be optimized independently, managing system complexity through functional decomposition across different architectural layers.
4Productivity
If load balancing hashing functions are used for node selection, then distribution of traffic is improved, but ensuring messages reach the correct node for existing sessions becomes difficult
Solution Approach 1:
The solution performs preliminary action by establishing binding records in the centralized repository before routing subsequent messages. The initial Diameter message triggers the creation of a binding record that associates the session with a specific network service node. This preliminary binding ensures that all subsequent messages for that session are routed to the same node, maintaining session affinity while allowing load balancing for new sessions.
Solution Approach 2:
The system implements feedback by using the centralized binding repository to provide routing decisions back to the Diameter signaling router. When a message arrives, the router queries the binding repository, which returns the appropriate network service node based on stored binding information. This feedback mechanism ensures consistent routing decisions while allowing the load balancing hashing function to distribute new sessions across available nodes.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods, systems, and computer readable media for hybrid session based Diameter routing are disclosed. According to one method, the method comprises receiving, at a first Diameter signaling router (DSR), a first Diameter message for processing by a Diameter server. The method also includes selecting, using a Diameter node selection algorithm that operates on at least one parameter in the first Diameter message without requiring use of stored Diameter binding information, a first Diameter server to which the first Diameter message is to be routed. The method further includes determining whether the first Diameter server is available. The method also includes, in response to determining that the first Diameter server is not available, selecting a second Diameter server to which the first Diameter message is to be routed and creating an exception binding record that associates the second Diameter server and information in the first Diameter message.