US 12,289,306 B2
System, method, and computer program product for authenticating a device based on an application profile
Navendu Misra, Austin, TX (US); Pratik Jayant Sanghvi, Austin, TX (US); and Vahini Mohan, Austin, TX (US)
Assigned to Visa International Service Association, San Francisco, CA (US)
Appl. No. 17/785,938
Filed by Visa International Service Association, San Francisco, CA (US)
PCT Filed Dec. 17, 2019, PCT No. PCT/US2019/066841
§ 371(c)(1), (2) Date Jun. 16, 2022,
PCT Pub. No. WO2021/126167, PCT Pub. Date Jun. 24, 2021.
Prior Publication US 2023/0027202 A1, Jan. 26, 2023
Int. Cl. H04L 9/40 (2022.01); G06Q 20/32 (2012.01); G06Q 20/40 (2012.01)
CPC H04L 63/0853 (2013.01) [G06Q 20/322 (2013.01); G06Q 20/40 (2013.01); H04L 63/1425 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method, comprising:
generating, with a mobile device application on a mobile device, a real-time mobile device application profile associated with the mobile device, wherein the real-time mobile device application profile comprises at least one of the following:
data associated with memory usage of one or more mobile device applications on the mobile device;
data associated with total usage of the one or more mobile device applications on the mobile device;
data associated with one or more times of a day that a user interacts with the one or more mobile device applications on the mobile device;
data associated with installation of the one or more mobile device applications on the mobile device; or
any combination thereof;
receiving, with at least one processor, the real-time mobile device application profile generated by the mobile device;
determining, with at least one processor, whether there is an anomaly between the real-time mobile device application profile and a historical mobile device application profile associated with the mobile device, wherein the historical mobile device application profile comprises at least one of the following:
historical data associated with memory usage of one or more mobile device applications on the mobile device;
historical data associated with total usage of the one or more mobile device applications on the mobile device;
historical data associated with one or more times of a day that a user interacts with the one or more mobile device applications on the mobile device;
historical data associated with installation of the one or more mobile device applications on the mobile device; or
any combination thereof;
wherein determining whether there is an anomaly comprises:
comparing the real-time mobile device application profile to the historical mobile device application profile; and
performing, with at least one processor, a remedial action associated with a transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile, wherein performing the remedial action associated with the transaction comprises:
transmitting one or more messages to one or more devices involved in the transaction, the one or more messages including data associated with an indication that an anomaly was detected, and
foregoing processing of the transaction based on determining that there is an anomaly between the real-time mobile device application profile and the historical mobile device application profile associated with the mobile device.