US 12,204,641 B2
Systems and methods for detecting resources responsible for events
Chris Moradi, San Francisco, CA (US); Jacob Sisk, Orinda, CA (US); Evan Bloom, Oakland, CA (US); Craig Gimby, Lakewood, CO (US); and Xin Sun, Pleasanton, CA (US)
Assigned to Capital One Services, LLC, McLean, VA (US)
Filed by Capital One Services, LLC, McLean, VA (US)
Filed on Oct. 9, 2023, as Appl. No. 18/483,233.
Application 18/483,233 is a continuation of application No. 16/924,004, filed on Jul. 8, 2020, granted, now 11,783,028.
Application 16/924,004 is a continuation of application No. 16/271,619, filed on Feb. 8, 2019, granted, now 10,742,671, issued on Aug. 11, 2020.
Application 16/271,619 is a continuation of application No. 15/856,614, filed on Dec. 28, 2017, granted, now 10,284,581, issued on May 7, 2019.
Application 15/856,614 is a continuation of application No. 15/854,030, filed on Dec. 26, 2017, granted, now 10,356,110, issued on Jul. 16, 2019.
Claims priority of provisional application 62/440,949, filed on Dec. 30, 2016.
Prior Publication US 2024/0037225 A1, Feb. 1, 2024
Int. Cl. G06F 21/55 (2013.01); G06F 16/2457 (2019.01); G06F 16/9038 (2019.01); G06F 21/60 (2013.01); G06N 7/01 (2023.01); G06Q 10/0635 (2023.01); G06Q 20/40 (2012.01); H04L 9/40 (2022.01); H04W 12/12 (2021.01); H04W 12/122 (2021.01); H04W 12/126 (2021.01)
CPC G06F 21/552 (2013.01) [G06F 16/24578 (2019.01); G06F 16/9038 (2019.01); G06F 21/60 (2013.01); G06N 7/01 (2023.01); G06Q 10/0635 (2013.01); G06Q 20/4016 (2013.01); H04L 63/1408 (2013.01); H04L 63/1416 (2013.01); H04L 63/1475 (2013.01); H04W 12/12 (2013.01); H04W 12/122 (2021.01); H04W 12/126 (2021.01)] 20 Claims
OG exemplary drawing
 
1. A system comprising:
one or more processors and memory comprising instructions that, when executed by the one or more processors, cause operations comprising:
identifying first actors that have accessed a resource and affected actors that have been affected by an event after accessing the resource by identifying the affected actors based on actors identified in event data associated with the event;
determining an access likelihood value based on the event data and an identifier of the resource by accessing a probabilistic data structure stored in an in-memory database wherein the access likelihood value indicates a likelihood that one or more of the first actors accessed the resource;
determining an event score based on the likelihood;
determining whether the resource is a cause for the event based on the event score; and
in response to determining that the resource is a cause for the event, generating, via a graphical user interface, a prompt to decline an incoming transaction by an additional actor that has accessed the resource determined to be a cause for the event.