Call Routing Registry for Direct Device Identifier Path

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional call routing between devices is costly due to multiple termination points, inefficient number porting, time delays, poor voice quality, and incompatibility between different signaling protocols.

Innovation Solution

A method and system for routing calls between ingress and egress points using a registry of stored identifiers, where calls are initiated with an identifier associated with the egress point, determining a delivery route through a network component that connects various points and selects either a primary or secondary path based on availability, and transmits the call accordingly, while also considering signaling protocol compatibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If conventional call routing through PSTN and LEC termination points is used, then calls can be delivered to end users, but the cost increases due to multiple termination points

Engineering Contradiction:
Improvecall routing costVSAvoidrouting structure complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent extracts and removes intermediate termination points (PSTN and LEC) from the call routing path. By using a registry to store device identifiers and their associated routing information, the system enables direct routing from ingress to egress points, eliminating the need for multiple intermediary termination points and reducing associated costs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The registry serves multiple functions: storing device identifiers, maintaining routing information, enabling direct routing decisions, and supporting number portability. This multi-functional component replaces the need for separate systems that would otherwise be required for each function, simplifying the overall routing structure.

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

2Loss of time

If multiple termination points are used in call routing, then calls can be routed through the network, but time delay increases

Engineering Contradiction:
Improvecall routing time delayVSAvoidcall delivery reliability
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The registry is pre-populated with device identifiers and their associated routing information before calls are routed. This preliminary action allows the routing system to make immediate direct routing decisions without needing to query multiple termination points during call setup, thereby reducing time delay while maintaining reliable call delivery.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If number porting is required when switching service providers, then users can change providers, but user convenience decreases

Engineering Contradiction:
Improveservice provider switching convenienceVSAvoidnumber porting process complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The registry stores device identifiers independently of service provider information, allowing the same identifier to route to different service providers. This universal storage mechanism enables users to switch providers without changing their identifiers, eliminating the need for number porting procedures and greatly improving user convenience.

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

4Speed

If direct routing path is used, then call delivery speed increases, but path availability decreases

Engineering Contradiction:
Improvecall delivery speedVSAvoidrouting path availability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The routing system dynamically selects between direct paths and alternative paths based on real-time availability. The registry stores multiple routing options for each device identifier, allowing the system to adaptively choose the most appropriate path at the time of call routing, thereby maintaining both speed and path availability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8064354B1Optimized path call routing with device identifier
Publication Date: 2011.11.22 INTELEPEER CLOUD COMM LLC
  • US8064354B1 patent drawing
  • US8064354B1 patent drawing
  • US8064354B1 patent drawing

AI summary

A process for routing a call between an ingress point and an egress point is based on an identifier, such as a number, assigned to the egress point and a registry in which identifiers are stored. A routing component receives the call from the ingress point and consults the registry to determine if an entry with the identifier of the egress point being called is stored therein. If a corresponding entry exists, a delivery route for routing the call to the egress point is determined. The delivery route may be a first path to the egress point if available. If the first path is not available, one or more secondary paths are determined, where one is utilized for sending the call to the egress point. The utilized secondary path may be the most optimal path for the call based upon established preferences and call features.