Mobile Caller Authentication via Cloud Token Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Authenticating callers in contact centers is imprecise and resource-intensive, especially with mobile devices, as security questions can be compromised, and Automatic Number Identification can be spoofed, failing to verify the correct user.
Innovation Solution
A system where mobile devices send authentication factors to a cloud authentication service, generating a token validated by the contact center, ensuring the user and device are authentic before establishing a call, using usage characteristics and biometrics for verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If security questions are used for authentication, then callers can be verified, but security information may be compromised allowing unauthorized access
Solution Approach 1:
The authentication process is segmented into multiple independent factors: device-based authentication (separate from user credentials), voice biometrics, and transactional verification. This segmentation ensures that compromise of one factor does not necessarily compromise the entire authentication system.
Solution Approach 2:
A cloud-based authentication service acts as an intermediary between the contact center and the caller's mobile device. This intermediary handles the complex authentication logic, token generation, and verification, protecting the contact center from direct exposure to authentication vulnerabilities while maintaining high security standards.
2Measurement precision
If ANI is used for caller identification, then the calling party's identity is tied to a location or device, but the ANI may be spoofed and does not ensure the correct individual is using the phone
Solution Approach 1:
The mobile device performs preliminary authentication actions before the call is routed to the contact center. The device generates authentication tokens and verifies voice biometrics in advance, ensuring that only authenticated users can initiate contact center calls. This preliminary verification prevents spoofing attempts at the source.
Solution Approach 2:
The system changes the authentication parameters from static ANI-based identification to dynamic multi-factor authentication including voice biometrics and device-specific tokens. This parameter transformation makes spoofing significantly more difficult as it would require replicating multiple dynamic factors simultaneously.
3Reliability
If active/passive voice biometrics are used for authentication, then high certainty of correct party is achieved, but the technology is very resource intensive for each call
Solution Approach 1:
The system implements partial voice biometric analysis by extracting only critical authentication features from the voice signal rather than performing complete forensic analysis. This partial action approach maintains high authentication certainty while significantly reducing computational resources required per call.
Solution Approach 2:
Voice biometric templates are established during a preliminary enrollment phase, storing only essential authentication characteristics. During actual calls, the system performs rapid comparison against these pre-established templates rather than creating new biometric profiles in real-time, reducing resource intensity while maintaining high certainty.
4Ease of operation
If traditional authentication methods are used, then the process is simple, but the authentication is imprecise and onerous
Solution Approach 1:
The authentication system operates autonomously without requiring contact center agent intervention. The mobile device and cloud authentication service handle verification automatically through token validation and biometric comparison, maintaining simplicity for the user while achieving high precision through automated multi-factor verification.
Data Source
AI summary
A call request is received, from a mobile device, to establish a communication with a contact center. For example, the call request may be to establish a voice call with the contact center. In response to the call request, the mobile device sends authentication factors to a cloud authentication service that the user/mobile device has previously registered with. For example, the authentication factors may include usage factors of the mobile device, such as a call history of the user on the mobile device. If the authentication factors are validated, a token is generated. The token is sent to the contact center along with the call request. The token is validated at the contact center. At this point, the contact center knows that the user/mobile device are authentic. A call is then established between the user and the contact center.