Caller ID Authentication via Pre-Call Token Handshake
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Nuisance calls, where callers use deceptive caller ID identifiers to fool recipients, pose a challenge in telecommunications, as existing solutions like continuous monitoring and blocking of numbers are ineffective due to the ability of scammers to quickly change phone numbers.
Innovation Solution
A multi-factor authentication method is implemented using a pre-call authentication handshake via SMS/MMS, where a caller shares an authentication token and a chosen numerical identifier, which is validated by the recipient's device and stored in an authorized caller list, ensuring only trusted calls are completed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous monitoring and blocking of phone numbers is used to prevent nuisance calls, then call security is improved, but the system becomes ineffective because scammers can quickly change phone numbers
Solution Approach 1:
The system performs authentication before the call is completed. A call request message is sent containing an authentication token and identifier, which is validated before the actual telephone call is connected. This preliminary authentication prevents nuisance calls from being completed, addressing the issue of scammers changing numbers by verifying identity in advance.
Solution Approach 2:
The call establishment process is divided into separate stages: (1) sending a call request message with authentication token, (2) validating the token and identifier, (3) storing authorized caller records, and (4) completing the telephone call only if authentication succeeds. This segmentation allows authentication to occur independently before the actual call, preventing fraudulent calls while allowing legitimate ones to proceed.
2Measurement precision
If multi-factor authentication with authentication tokens is implemented, then caller identification accuracy is improved, but the complexity of the calling process increases
Solution Approach 1:
The authentication system uses self-service mechanisms where the caller's device automatically sends the call request message containing the authentication token and identifier without requiring manual intervention. The recipient's device automatically validates the token and manages the authorized caller list, reducing the perceived complexity for users while maintaining high identification accuracy.
Solution Approach 2:
The system changes the parameter of authentication from traditional continuous verification to a discrete token-based system with specific parameters: an authentication token and a numerical identifier. This parameter change simplifies the authentication process to exchanging and verifying specific data elements rather than continuous monitoring, improving identification accuracy while managing complexity through defined parameters.
3Reliability
If authentication tokens with predetermined time periods are used, then call authenticity is improved, but the duration for which calls can be made is limited
Solution Approach 1:
The authentication token is designed with a predetermined time period for validity. The system periodically refreshes or re-validates authentication through the call request message process. This periodic authentication mechanism ensures call authenticity within each time period while allowing multiple authentication cycles for ongoing communication needs, balancing reliability with operational duration.
Data Source
AI summary
Systems and methods for multi-factor authentication of a caller identification (ID) identifier are disclosed. In embodiments, a method includes: receiving, by a computing device of a call recipient, a call request message from a remote caller device of a caller, the call request message including an authentication token shared between the caller and the call recipient, and an identifier; authenticating the caller using the authentication token; saving an authorized caller record in an authorized caller list on the computing device, the authorized caller record including the identifier; receiving an incoming telephone call from the caller, the incoming call including a caller ID identifier; determining that the caller ID identifier matches the identifier in the authorized caller record; and initiating completion of the call based on the determining that the caller ID identifier matches the identifier in the authorized caller record.