Mobile Device Cryptogram Authentication for Fraud Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current service provider applications on mobile devices lack a reliable method to confirm the authenticity of both the user and the device when accessing third-party services, leading to potential fraudulent activities.
Innovation Solution
Implementing a secure authentication system where the mobile device generates a cryptogram using user identification, timestamp, device ID, service provider application ID, and service provider device ID, which is then verified by the service provider computer, ensuring the authenticity of both the user and the device without additional login steps.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional login methods are used for service provider applications, then ease of operation is maintained, but reliability of authentication is insufficient
Solution Approach 1:
The system performs preliminary binding between user credentials and device identifiers before the authentication process. The mobile device stores binding information that links the user's login credentials with the device's unique identifiers (IMSI, IMEI, MAC address) in advance, so that during authentication, the system can automatically verify both user identity and device authenticity without requiring additional login steps from the user.
2Reliability
If additional authentication steps are added to verify device authenticity, then reliability of authentication is improved, but ease of operation deteriorates
Solution Approach 1:
The mobile device automatically performs device authentication by presenting its stored binding information and current device identifiers to the server. The device itself verifies whether its current state matches the bound credentials, eliminating the need for user intervention in the device verification process. The user simply needs to log in normally, while the system handles device authenticity verification in the background.
3Reliability
If multiple data elements are required for cryptogram generation, then reliability of fraud prevention is improved, but device complexity increases
Solution Approach 1:
The mobile device's existing authentication framework is extended to serve multiple functions: it not only handles traditional user login authentication but also performs device authenticity verification, generates cryptograms for fraud prevention, and manages binding information storage. By making the authentication system multi-functional, the patent avoids adding separate dedicated components for each security function, thereby limiting the increase in device complexity while improving fraud prevention capabilities.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An authentication method is disclosed. To authenticate a user, a mobile device may request identification and verification from the user. Upon receiving a positive identification and verification response from the user, the mobile device may generate a cryptogram using a user identification (ID) associated with the user, a timestamp, a device ID associated with the mobile device, a service provider application ID associated with the service provider application, and a service provider device ID. The mobile device may transmit the generated cryptogram, the user ID, the timestamp, the device ID, the service provider application ID, and the service provider device ID, to a service provider computer associated with the service provider application. The service provider computer may decrypt the cryptogram and compare the decrypted data elements to the received data elements to validate and authenticate the user.