Looping Engine for Multi-Gateway Network Call Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing telecommunications networks face delays and resource wastage due to looping conditions, where calls are repeatedly routed without reaching their destination, as existing solutions require updating routing tables to terminate such loops.

Innovation Solution

A system that uses a looping engine within the switching infrastructure to detect looping conditions in real-time by querying call identification data and releasing calls for alternate routing without pre-emptive blocking, utilizing a fixed or sliding window to identify occurrences within a predetermined time frame.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If routing tables are updated to block looping calls, then looping conditions are terminated, but call delays and resource consumption occur before blocking is established

Engineering Contradiction:

Improvelooping condition terminationVSAvoidcall delay

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary detection of looping conditions by tracking call routing paths before the loop completes. The looping detection mechanism monitors call offers and identifies potential loops in advance, allowing the system to terminate the call immediately upon detection rather than waiting for the loop to fully execute and then updating routing tables.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback monitoring of call routing paths through the peering grid. By tracking call identification data and routing history, the system detects looping conditions in real-time and provides immediate feedback to terminate the call, eliminating the delay associated with post-detection routing table updates.

Inventive Principle:

Principle #23Feedback

2Reliability

If routing tables are updated to prevent future loops, then looping is prevented, but system complexity and processing overhead increase

Engineering Contradiction:

Improveloop preventionVSAvoidrouting table management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The looping detection functionality is extracted from the core routing logic into a separate, dedicated mechanism. This allows the routing tables to remain simple and efficient while the extraction of loop detection into a specialized subsystem handles the complexity of path tracking and loop identification without burdening the general routing infrastructure.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

An intermediary looping detection mechanism is introduced between the call offering system and the routing tables. This intermediary layer tracks call paths and identifies loops without requiring complex modifications to the routing tables themselves, maintaining their simplicity while adding loop prevention capability through the mediating detection layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Measurement precision

If calls are tracked through database recording, then looping conditions can be detected, but resource consumption increases

Engineering Contradiction:

Improveloop detection accuracyVSAvoidsystem resource consumption

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system applies partial tracking by monitoring only the necessary call identification data required for loop detection rather than recording complete call details. By tracking only essential routing path information through a streamlined mechanism, the system achieves sufficient detection accuracy while minimizing resource consumption compared to comprehensive call recording.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS8325891B2Anti-looping for a multigateway multi-carrier network

Publication Date: 2012.12.04 INTELEPEER CLOUD COMM LLC

AI summary

The present invention relates to systems and methods for detecting and terminating a looping condition occurring in a telecommunications network comprising receiving a call offer comprising receiving call identification data associated with the call offer at a switching component, querying a looping engine using the call identification data to detect a looping condition, identifying a number of occurrences of the call identification data within a predetermined time frame, comparing the number of occurrences against a predetermined count, and returning a message to the switching component based on the comparison, the message indicating whether a looping condition exists in the telecommunications network.