Diameter Routing Agent Context Objects for Dynamic Message Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Diameter Routing Agents (DRAs) lack the ability for users to easily and flexibly define complex message processing behaviors, relying on hard coding or scripting for basic functionalities.

Innovation Solution

Implementing a method and system that allows users to define and extend DRA message processing behavior through context artifacts, which include context objects and rules, enabling the creation of computational contexts for routing decisions and subscriber records, and using a rule engine to evaluate these rules for message processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hard coding or scripting is used for basic DRA functionalities, then the system structure is simple, but the adaptability and ease of defining complex message processing behaviors deteriorates

Engineering Contradiction:
Improveability to define complex message processing behaviorsVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the DRA system into distinct modular components: context artifacts (defining context object types), context objects (instances with attributes and actions), rule storage (containing processing logic), and a rule engine (evaluation mechanism). This segmentation allows each component to be independently configured and modified, enabling complex message processing behaviors without requiring complete system redesign.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic configurability where context artifacts and rules can be added, modified, or removed at runtime without reconfiguring the entire DRA system. The rule engine dynamically evaluates rules against context objects during message processing, allowing the system to adapt to changing requirements while maintaining a stable core architecture.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If context artifacts and rule engine are implemented, then the ease of operation and adaptability improve, but the device complexity increases

Engineering Contradiction:
Improveease of defining message processing behaviorsVSAvoidnumber of system components
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent enables self-service operation where users can directly define message processing behaviors using context artifacts and rules without requiring deep knowledge of the underlying system architecture. The rule engine automatically evaluates these user-defined rules against incoming messages, and the system self-manages the complexity of coordinating multiple components through standardized interfaces.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The rule engine acts as an intermediary layer between user-defined context artifacts/rules and the actual message processing operations. This intermediary abstracts the complexity of coordinating multiple system components, presenting a simplified interface to users while managing the intricate interactions between context objects, attributes, actions, and message routing internally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9204285B2Subscriber record context objects
Publication Date: 2015.12.01 ALCATEL LUCENT SA
  • US9204285B2 patent drawing
  • US9204285B2 patent drawing
  • US9204285B2 patent drawing

AI summary

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device, wherein the Diameter message is associated with a subscriber; establishing a subscriber record context object in response to receiving the Diameter message, wherein the subscriber record context object is associated with a subscriber record of the subscriber; evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the subscriber record context object based on the context object reference; and transmitting a message based on the evaluation of the rule.