Two-Level Directory System for Proximity-Based Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional communication routing systems in federated domains do not efficiently select a point of presence nearest the destination communication device, leading to inefficient routing of calls and communication links.

Innovation Solution

A two-level directory system is implemented, where a user directory provides location information for communication devices, which is then used to access a peer directory containing point of presence information, allowing for the selection of a point of presence based on proximity, cost, latency, or other factors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional DNS lookup is used to route calls in federated domains, then routing information can be obtained, but the point of presence selected is not necessarily the nearest one to the destination device

Engineering Contradiction:
Improverouting precisionVSAvoidrouting efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The directory system is segmented into two levels: a user directory containing location information for communication devices, and a peer directory containing point of presence information for enterprises. This segmentation allows the system to first resolve user location and then select the nearest point of presence, improving routing precision without sacrificing efficiency

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The federation broker acts as an intermediary that hosts both directories and performs the two-step lookup process. It mediates between the conventional DNS lookup and the point of presence selection, using location information from the user directory to efficiently select the nearest point of presence from the peer directory

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If a point of presence far from the destination device is selected, then routing can be simplified, but connection quality and latency are degraded

Engineering Contradiction:
Improverouting complexityVSAvoidconnection quality
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system applies local quality by selecting a point of presence that is locally optimal (nearest to the destination device) rather than using a uniform routing approach. The user directory stores location information that enables this localized selection, improving connection quality and reducing latency while maintaining routing simplicity through the automated two-level lookup process

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If location information is not integrated into the DNS lookup process, then the existing system structure is maintained, but routing efficiency is reduced

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidrouting time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The user directory pre-stores location information for communication devices, and the peer directory pre-stores point of presence information for enterprises. When a routing request is made, the federation broker performs a preliminary lookup in the user directory to obtain location information, then uses this information to efficiently select the nearest point of presence from the peer directory, reducing routing time while adapting the existing DNS lookup structure

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10277421B2Route lookup resolution
Publication Date: 2019.04.30 EXTREME NETWORKS INC
  • US10277421B2 patent drawing
  • US10277421B2 patent drawing
  • US10277421B2 patent drawing

AI summary

Methods and systems for routing connections between federated enterprises are provided. More particularly, user location information is stored as part of a first directory accessible to a federation broker. Location information obtained in association with a requested connection is used by the federation broker to access a second directory containing the locations of points of presence within the enterprise that includes the target communication device.