ENUM Request Augmentation for Intelligent Telecommunication Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

ENUM requests lack sufficient information for carriers to make network routing and class-of-service decisions, limiting the flexibility and intelligence in managing telephone calls through packet-based networks.

Innovation Solution

Augmenting ENUM requests with additional information such as logical trunk-group and gateway data, which can be associated through IP addresses or domain names, to enable intelligent routing and service decisions, including digit manipulation, dial plan management, and class-of-service policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If ENUM requests are kept simple for basic number mapping, then implementation ease is improved, but routing decision capability deteriorates

Engineering Contradiction:

Improveimplementation easeVSAvoidrouting decision capability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by pre-associating trunk-group and gateway information with ENUM requests before routing decisions are needed. This allows the basic ENUM protocol to remain simple while carrying additional routing information that has been prepared in advance, enabling both easy implementation and informed routing decisions.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses an intermediary approach by introducing additional data fields and association mechanisms that bridge the simple ENUM protocol with complex routing requirements. These intermediaries (extended data structures, association rules) allow the core ENUM function to remain unchanged while enabling enhanced routing capabilities through layered information addition.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If additional information is added to ENUM requests for intelligent routing, then routing capability is improved, but data packet complexity deteriorates

Engineering Contradiction:

Improverouting capabilityVSAvoiddata packet complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the additional information into distinct, organized components (trunk-group identifiers, gateway information, class-of-service data). This segmented structure allows routing capabilities to be enhanced through modular information addition rather than monolithic complexity, making the data packet manageable and processable.

Inventive Principle:

Principle #1Segmentation

3Speed

If ENUM requests include only basic mapping information, then processing speed is improved, but service management flexibility deteriorates

Engineering Contradiction:

Improveprocessing speedVSAvoidservice management flexibility

Core Design Contradiction:

SpeedVSAdaptability or versatility

Solution Approach 1:

The patent uses preliminary action to associate routing and service information with ENUM requests before processing occurs. This pre-preparation of data allows fast processing to continue while the necessary information for flexible service management is already in place, eliminating the need for additional lookup or processing steps.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9253142B2Providing telecommunication services based on an E.164 number mapping (ENUM) request

Publication Date: 2016.02.02 RIBBON COMMUNICATIONS OPERATING CO INC

AI summary

Data associated with an E.164 number mapping (ENUM) request can be received from an element of a telecommunications network. Logical trunk-group information and gateway information can be associated with the ENUM request. A call is managed by the computing element through a packet-based network based at least in part on the logical trunk-group information and the gateway information.