Dynamic Origination-Based Routing Key Registration in Diameter Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional DIAMETER networks lack a mechanism for automatic receipt and updating of origin-based routing information, leading to manual and error-prone processes for populating routing tables, whereas destination-based routing information can be automatically updated using DNS.

Innovation Solution

Implementing dynamic origination-based routing key registration through modified DIAMETER messages, such as the capabilities exchange message, to automatically generate and apply origin-based routing rules, allowing DIAMETER nodes to specify that traffic from specific sources should be routed to them, thereby automating the population and updating of routing tables.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual methods are used to populate routing tables with origin-based routing information, then routing table updates can be performed, but the process is slow and prone to error

Engineering Contradiction:

Improveaccuracy of routing table updatesVSAvoidspeed of routing table updates

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service by allowing DIAMETER nodes to automatically send notification messages to relay nodes, providing their own routing information without requiring manual data entry. The automated message generation and routing table population process eliminates human intervention, thereby improving both accuracy and speed simultaneously

Inventive Principle:

Principle #25Self-service

2Extent of automation

If no automatic mechanism exists for origin-based routing information, then manual updates can be performed, but automated notification and updating like destination-based routing is not available

Engineering Contradiction:

Improveautomation of routing information updatesVSAvoidsimplicity of routing information management

Core Design Contradiction:

Extent of automationVSEase of operation

Solution Approach 1:

The invention applies universality by creating a notification message mechanism that works for origin-based routing information in the same way DNS works for destination-based routing information. This multi-functional approach allows both origin-based and destination-based routing to be managed automatically through similar mechanisms, improving automation while maintaining operational simplicity

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Loss of time

If hub provider A manually gathers origin-based routing information, then routing tables can be updated, but the process requires human intervention and is time-consuming

Engineering Contradiction:

Improvetime required for routing table updatesVSAvoidcomplexity of routing information gathering process

Core Design Contradiction:

Loss of timeVSDevice complexity

Solution Approach 1:

The system implements preliminary action by having DIAMETER nodes pre-configure their routing information and automatically send notification messages when routing changes occur. This advance preparation and automated triggering eliminates the need for time-consuming manual data gathering while reducing process complexity through standardized message formats and automated workflows

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentEP2583415B1Method, diameter node, and computer readable medium for providing dynamic origination-based routing key registration in a diameter network

Publication Date: 2018.07.25 TEKELEC INC

Figure 1
Figure 2
Figure 3

AI summary

Methods, systems, and computer readable media for providing dynamic origination-based routing key registration in a DIAMETER network are disclosed. According to one method, origin-based routing information is received, at a first DIAMETER node, from a second DIAMETER node. The origin-based routing information specifies one or more sources such that traffic originating from one of the one or more sources should be routed to the second DIAMETER node. A routing rule is automatically generated, at he first DIAMETER node, based on the received origin-based routing information.