ENUM Payload Merging for Nuisance Call Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional call routing systems are limited in managing nuisance calls, as they only route calls based on the called party's number and do not consider the preferences or identifiers of the calling party, leading to inefficiencies in handling unwanted calls such as scams or telemarketers.
Innovation Solution
The system modifies the ENUM payload to include both the calling party and called party numbers, allowing for preference-based call routing by querying an ENUM database to determine if the calling party is unwanted, and applying alternate routing dispositions such as blocking or redirecting calls based on spam scores and user feedback.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional call routing is used based only on called party number, then routing simplicity is maintained, but ability to manage nuisance calls is insufficient
Solution Approach 1:
The patent combines the calling party number and called party number into a single ENUM lookup key. This merging allows the system to query caller preferences and routing dispositions without requiring separate complexity for caller identification and routing logic, thus improving nuisance call management while maintaining routing simplicity.
Solution Approach 2:
The ENUM database is enhanced to store multiple types of information including caller preferences, spam scores, and routing dispositions for different calling scenarios. This multi-functional database serves both traditional call routing and advanced nuisance call management, eliminating the need for separate specialized systems.
2Measurement precision
If enhanced information query including both calling and called party numbers is implemented, then caller identification accuracy is improved, but information processing requirements increase
Solution Approach 1:
By merging both calling and called party numbers into a single ENUM lookup operation, the system retrieves comprehensive caller information in one query rather than requiring multiple separate lookups. This reduces information processing load while maintaining high caller identification accuracy.
3Reliability
If preference-based routing is implemented using ENUM database, then call handling effectiveness is improved, but system complexity increases
Solution Approach 1:
The system performs preliminary ENUM database lookups before call establishment to determine caller preferences and routing dispositions. By pre-fetching routing information based on caller ID, the system can make immediate routing decisions without adding complex real-time analysis during call handling, thus improving effectiveness while controlling complexity.
4Object-affected harmful factors
If traditional DNS routing is used, then network resource consumption is low, but nuisance call filtering capability is insufficient
Solution Approach 1:
The system performs preliminary ENUM database queries during call setup to identify and filter nuisance calls before they consume significant network resources. By pre-screening callers using their identifiers and stored preferences, the system blocks unwanted calls early in the process, reducing overall network resource consumption while improving nuisance call filtering.
Data Source
AI summary
A system may include one or more of a called device, a calling device, configured to call the called device, and a network module. The network module is configured to process incoming call information of a call placed to the called device and configured to route the call to a destination based on preferences of the called device.