Dynamic Context Router for Signalling Traffic Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of wireless and cellular networks has increased due to expanding user demand for services, making efficient routing and management of signalling traffic a challenging task, particularly in telecommunications systems where existing solutions lack dynamic and intelligent management capabilities.

Innovation Solution

The implementation of a dynamic context router that operates as a protocol-agnostic, application-level router and load balancer, capable of making routing and load-balancing decisions based on message context and content, and able to interact with external systems for additional information to optimize routing and load balancing operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If traditional routing methods are used in expanding telecommunications networks, then network coverage and user capacity increase, but routing efficiency and management complexity deteriorate

Engineering Contradiction:
Improvenetwork capacityVSAvoidrouting management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments the telecommunications network into multiple distributed routing instances that operate independently but coordinate through a standardized interface. Each routing instance handles a specific subset of traffic, allowing the network to scale horizontally without proportionally increasing central routing management complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal routing interface that can handle multiple protocols and traffic types through a single standardized mechanism. This multi-functional approach allows the routing system to manage diverse traffic flows without requiring separate complex management systems for each protocol

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If more routing instances are deployed to handle increased traffic, then network capacity and availability improve, but coordination complexity and resource overhead increase

Engineering Contradiction:
Improvenetwork availabilityVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the coordination parameter from complex stateful communication to simple key-based hashing. Each routing instance uses a hash of the message key to determine data repository location, transforming coordination from a complex multi-variable problem into a simple deterministic function that scales linearly with the number of instances

Inventive Principle:
Principle #35Parameter changes

3Productivity

If dynamic context-based routing is implemented, then routing intelligence and efficiency improve, but processing complexity and computational overhead increase

Engineering Contradiction:
Improverouting efficiencyVSAvoidprocessing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the complex routing logic from the message forwarding path and places it in a separate data repository lookup mechanism. The router only needs to extract the message key, hash it to find the repository, and forward the message - separating the intelligent routing decision from the simple forwarding action to reduce processing complexity in the critical path

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8725820B2Methods, systems and devices for horizontally scalable high-availability dynamic context-based routing
Publication Date: 2014.05.13 OPENET TELECOM LTD
  • US8725820B2 patent drawing
  • US8725820B2 patent drawing
  • US8725820B2 patent drawing

AI summary

Methods, servers and systems for communicating information in networks enable efficient expansion while maintaining high-availability. A first message associated with an entity may be received on a first server. An operation may be performed on certain information included in the first message associated with the entity to identify a first data repository in which information associated with the first message or the entity is to be stored. Information extracted from the first message may be stored in the identified first data repository. When a second message associated with the entity is received, the same operation may be performed on the same certain information included in the second message to identify the first data repository in which information associated with the first message or the entity is stored. The information related to the first message or the entity from the first data repository may then be used.