Call Routing Facility Using Service Provider Type Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telephony systems face challenges in routing calls originating from other service providers, as relying solely on call type is insufficient for determining the correct routing destination.

Innovation Solution

A method and system that involve receiving a call session from another service provider, determining the service provider type and origination number type, and using this information to determine routing details, which are then used to route the call session to its destination, utilizing a call routing facility with components like a session border controller, jurisdictional analyzer, route proxy, and routing database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If routing decisions are based solely on call type, then routing simplicity is maintained, but routing accuracy for calls from other service providers deteriorates

Engineering Contradiction:
Improverouting decision complexityVSAvoidrouting accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The routing decision process is segmented into multiple evaluation dimensions: call type identification, service provider type determination, and origination number type classification. Each dimension contributes to the final routing decision, allowing the system to handle different service provider calls appropriately while maintaining manageable complexity through modular decision components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The routing system transitions from a single-dimension approach (call type only) to a multi-dimensional approach by incorporating service provider type and origination number type as additional routing dimensions. This dimensional expansion enables accurate routing for calls from other service providers without overwhelming system complexity, as each dimension is processed by dedicated routing components.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Device complexity

If a shared routing database is used for all users, then system simplicity is maintained, but user data privacy and scalability deteriorate

Engineering Contradiction:
Improvedatabase structure complexityVSAvoiduser data privacy
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The routing database is segmented into multiple partitioned databases, with each partition dedicated to a specific user or service provider. This segmentation isolates user data, ensuring that routing information for one user cannot be accessed by another, thereby maintaining data privacy and security while allowing the overall system to scale by adding new partitions as needed.

Inventive Principle:
Principle #1Segmentation

3Device complexity

If the system handles only domestic calls, then routing complexity is reduced, but service versatility deteriorates

Engineering Contradiction:
Improverouting logic complexityVSAvoidservice coverage
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The routing system is designed with universal components that can handle multiple types of calls (domestic, international, toll, long-distance) through a unified routing framework. The system determines service provider type and call type dynamically, allowing the same routing infrastructure to serve diverse calling scenarios without requiring separate routing logic for each call type, thus maintaining versatility while controlling complexity.

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

Data Source

PatentEP2945355B1Data and call routing and forwarding
Publication Date: 2019.05.01 COMCAST CABLE COMM LLC
  • EP2945355B1 patent drawingFigure 1A
  • EP2945355B1 patent drawingFigure 1B
  • EP2945355B1 patent drawingFigure 2

AI summary

One or more aspects of the disclosure relate to various functions and processes related to routing of calls originating from other service providers. For example, a method includes receiving a request to route a call or a call session, such as a session initiation request, from a second service provider and proceeding to route the requested call or session through a call routing facility of the first service provider to a requested destination of the call. Routing the call through the call routing facility may include determining a service provider type and/or an origination number type for the call, determining routing information for the call using the type information, and causing routing of the call to a destination of the call based on the routing information. Further aspects of the disclosure relate to various functions and processes related to accessing routing data and/or information from a routing database.