ENUM DNS Packet Priority Control via Destination-Based Flagging

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing ENUM/DNS system lacks a mechanism to prioritize emergency calls during congestion, as it relies on origin terminal information and does not adhere to ENUM standards, failing to identify packet priority based on destination terminal information.

Innovation Solution

An ENUM/DNS packet priority control system where a call control server determines connection requests for priority processing based on predetermined logic and generates ENUM/DNS packets with a priority flag, allowing the ENUM/DNS server to identify and prioritize packets without relying on origin terminal information, using call destination information to differentiate between priority and normal packets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the ENUM/DNS system processes all queries equally without priority differentiation, then the system maintains simplicity and adheres to standard protocols, but emergency calls and high-priority connections experience delays or failures during congestion

Engineering Contradiction:

Improveemergency call connectivityVSAvoidpacket priority control mechanism

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the parameter of packet identification from origin-based (caller ID) to destination-based (called number) priority marking. The call control server modifies ENUM/DNS packets by setting a priority flag based on the called number, allowing the ENUM/DNS server to differentiate and prioritize emergency calls during congestion without fundamentally altering the protocol structure

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The call control server acts as an intermediary between the terminal and ENUM/DNS server, inserting priority information into ENUM/DNS packets based on called number analysis. This intermediary function enables priority control while maintaining compatibility with existing ENUM/DNS protocols and infrastructure

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the system uses origin terminal information to determine packet priority, then priority control can be implemented, but it fails to identify priority packets based on call destination information and does not comply with ENUM standards

Engineering Contradiction:

Improvepriority packet identificationVSAvoidENUM standard compliance

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent inverts the traditional approach by determining packet priority based on the called number (destination) rather than the caller ID (origin). The call control server analyzes the called number in connection requests and sets priority flags accordingly, ensuring both emergency call prioritization and ENUM standard compliance

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The patent changes the parameter of priority determination from origin terminal identity to destination terminal (called number) characteristics. By analyzing called numbers and setting priority flags based on destination information, the system achieves both reliable priority identification and adherence to ENUM protocols

Inventive Principle:

Principle #35Parameter changes

3Productivity

If the ENUM/DNS server processes all queries with equal priority, then the system operates simply without complex priority logic, but connection delays occur during high-volume congestion scenarios

Engineering Contradiction:

Improvequery processing speedVSAvoidpriority processing logic

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The call control server performs preliminary action by setting priority flags in ENUM/DNS packets before they reach the ENUM/DNS server. This advance marking allows the ENUM/DNS server to quickly identify and prioritize emergency calls without complex real-time analysis, improving processing speed during congestion

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces a priority flag parameter in ENUM/DNS packets that enables the ENUM/DNS server to differentiate between normal and emergency queries. This simple binary parameter allows efficient priority processing without requiring complex processing logic at the ENUM/DNS server

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS11757783B2ENUM/DNS packet priority control system and ENUM/DNS packet priority control method

Publication Date: 2023.09.12 NIPPON TELEGRAPH & TELEPHONE CORP

AI summary

When congestion occurs, the ENUM/DNS server can identify a priority packet without relaying on origin terminal information. An ENUM/DNS packet priority control system 100 includes a call control server 10 that, upon receiving a connection request from a terminal, determines whether or not the connection request is to be subjected to priority processing based on predetermined determination logic, and generates an ENUM/DNS packet that has a priority flag upon determining that the connection request is to be subjected to priority processing. The ENUM/DNS packet priority control system 100 also includes an ENUM/DNS server 20 that, upon receiving an ENUM/DNS packet that has the priority flag, determines that the packet is to be subjected to priority processing, and transmits, to the call control server 10, connection destination information that corresponds to the call destination terminal.