US 9,485,265 B1Grant
Malicious activity detection system capable of efficiently processing data accessed from databases and generating alerts for display in interactive user interfaces
Issue Date:2016-11-01
•16 Claims
•26 Drawing Sheets
Abstract
Various systems and methods are provided that retrieve raw data from issuers, reorganize the raw data, analyze the reorganized data to determine whether the risky or malicious activity is occurring, and generate alerts to notify users of possible malicious activity. For example, the raw data is included in a plurality of tables. The system joins one or more tables to reorganize the data using several filtering techniques to reduce the processor load required to perform the join operation. Once the data is reorganized, the system executes one or more rules to analyze the reorganized data. Each rule is associated with a malicious activity. If any of the rules indicate that malicious activity is occurring, the system generates an alert for display to a user in an interactive user interface.
Metadata
Assignee
- Palantir Technologies Inc.
Inventors
- Craig Saperstein
- Eric Schwartz
- Hongjai Cho
Application Information
Application Number:US 15/017,324
Filing Date:2016-02-05
Priority Date:2015-08-28
Art Unit:2433
Classifications
IPC:
H04L29/00H04L29/06
Field of Search:
H04L 63/1416H04L 29/06911H04L 29/06925H04L 29/06931H04L 29/06938G06F 21/55
Patent Drawings (26 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Application No. 62/211,520, entitled “FRAUD DETECTION SYSTEM CAPABLE OF EFFICIENTLY PROCESSING DATA ACCESSED FROM DATABASES AND GENERATING ALERTS FOR DISPLAY IN INTERACTIVE USER INTERFACES” and filed on Aug. 28, 2015, which is hereby incorporated by reference in its entirety.
TECHNICAL FIELD
[0002] The present disclosure relates to systems and techniques for data integration, analysis, and visualization.
BACKGROUND
[0003] Prepaid cards or cash cards are cards in which a user may load money for later withdrawal. For example, a user may load money onto a prepaid card and then later use the prepaid card to make a purchase. By law, the prepaid cards are generally regulated like regular bank accounts. The issuers of the prepaid cards are in charge of making sure transactions associated with the prepaid cards comply with the relevant regulations.
[0004] If transactions associated with a prepaid card do not meet the relevant regulations, the issuer of the prepaid card must submit a report. For example, the issuer may be required to submit a report if the transactions indicate that fraud could be taking place. The prepaid cards are often linked to the user via some identifier that uniquely identifies the user, so the report may include such information to assist the issuer and/or a federal agency in taking further action, if necessary.
SUMMARY
[0005] The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.
[0006] Issuers often store transaction data from prepaid cards in a plurality of databases. For example, one database may include transaction data that identifies an amount that was deposited or withdrawn on a card and a time and location where the transaction occurred, another database may include a description of the transaction and an identifier that identifies the user of the prepaid card, and so on. In some cases, to determine whether transactions comply with the relevant regulations, data from multiple databases may need to be analyzed. Typically, each individual database includes a large amount of uncompressed data (e.g., on the order of hundreds of gigabytes), so it is nearly impossible for a human fraud analyst to find all data that may be relevant to a particular regulation and/or to identify patterns that may indicate a regulation has been violated. The analysis could instead be automated. To perform the analysis, the data from the different databases would have to be combined into a single database, such as via a join table operation. However, because each individual database may include a large amount of uncompressed data, join operations typically implemented by traditional databases may be difficult to run. Furthermore, once the analysis is performed, a mechanism may need to be implemented so that detected inconsistencies between the transaction data and regulations can be brought to the fraud analyst's attention.
[0007] Accordingly, embodiments of the present disclosure relate to a system that retrieves raw transaction data from issuers, reorganizes the raw transaction data, analyzes the reorganized data to determine whether the relevant regulations have been complied with, and generates alerts to notify fraud analysts of possible regulation violations or the occurrence of possible risky or malicious behavior. For example, the raw transaction data may be included in a plurality of tables. The system may join one or more tables to reorganize the transaction data using several filtering techniques to reduce the amount of data being joined and the processor load required to perform the join operation. Once the transaction data is reorganized using the join operation, the system may run one or more rules to analyze the reorganized transaction data. Each rule may be associated with a regulation that governs the use of prepaid cards or a general category of risky or malicious behavior (e.g., behavior not associated with a specific regulation, but that nonetheless may indicate that fraud or other malicious activity is taking place). The rules may be generated such that duplicate violations are ignored and/or machine learning techniques are used to improve the function of the rule over time. If any of the rules indicate that a regulation may be violated or that risky behavior is occurring, the system may generate an alert for display to a fraud analyst in an interactive user interface. The interactive user interface may allow the fraud analyst to view additional details regarding alerts, organize alerts, filter alerts, and/or take further actions related to the alerts. Thus, the system may be able to efficiently allow prepaid card issuers to identify regulation violations or risky behavior and take appropriate action.
[0008] Additionally, it has been noted that design of computer user interfaces “that are useable and easily learned by humans is a non-trivial problem for software developers.” (Dillon, A. (2003) User Interface Design. MacMillan Encyclopedia of Cognitive Science, Vol. 4, London: MacMillan, 453-458.) The various embodiments of interactive and dynamic user interfaces of the present disclosure are the result of significant research, development, improvement, iteration, and testing. This non-trivial development has resulted in the user interfaces described herein which may provide significant cognitive and ergonomic efficiencies and advantages over previous systems. The interactive and dynamic user interfaces include improved human-computer interactions that may provide reduced mental workloads, improved decision-making, reduced work stress, and/or the like, for a fraud analyst user.
[0009] Further, the interactive and dynamic user interfaces described herein are enabled by innovations in efficient interactions between the user interfaces and underlying systems and components. For example, disclosed herein are improved methods of merging data stored in different tables and/or databases, automatic and dynamic execution of complex rules in response to the successful data merges, automatic interaction among various components and processes of the system, and/or automatic and dynamic updating of the user interfaces. The interactions and presentation of data via the interactive user interfaces described herein may accordingly provide cognitive and ergonomic efficiencies and advantages over previous systems.
[0010] Advantageously, according to various embodiments, the disclosed techniques provide a more effective starting point and user interface for an investigation of potentially fraudulent activity. A fraud analyst may be able to start an investigation by viewing a group of identified alerts organized by user, country of origin, violated regulation, identified risky behavior, and/or the like instead of by parsing through a large amount of data (e.g., on the order of hundreds of gigabtyes) to identify a transaction or sequence of transactions that may indicate a regulation is violated or that risky behavior is occurring, which may reduce the amount of time and effort required to perform the investigation. The disclosed techniques may also, according to various embodiments, provide a prioritization of alerts (e.g., based on which violations require immediate attention and which violations do not require immediate attention). For example, the fraud analyst may also be able to start the investigation from a high priority group of alerts, which may allow the fraud analyst to focus on the most important investigations, and may quickly evaluate that group of alerts based on the efficient user interface generated by the system. In each case, the processing and memory requirements of such an investigation may be significantly reduced due to the efficient merging of data, the running of various rules and the generation of alerts and related data.
[0011] One aspect of the disclosure provides a computing system configured to process a large amount of dynamically updating data. The computing system comprises a database storing a first table and a second table, wherein the first table comprises a first column header, a second column header, and first data corresponding to the first column header or the second column header, and wherein the second table comprises the first column header, a third column header, and second data corresponding to the first column header or the third column header; a computer processor; and a computer readable storage medium storing program instructions configured for execution by the computer processor in order to cause the computing system to: retrieve the first table and the second table from the database, identify that the first column header is included in the first table and the second table, execute a join operation to generate a third table using the first column header as a join key, wherein the third table comprises the first column header, the second column header, the third column header, the first data, and the second data, select a first rule from a plurality of rules, wherein the first rule is associated with a behavior, run the first rule on the third table to determine whether the behavior regulation is risky, generate an alert in response to a determination that the behavior is risky, and transmit the alert for display in an interactive user interface.
[0012] The computing system of the preceding paragraph can have any sub-combination of the following features: where the second table further comprises a fourth column header, and wherein the program instructions are further configured to cause the computing system to: determine that the first rule does not use data associated with the fourth column header to determine whether the behavior is risky, and remove the fourth column from the second table prior to executing the join operation; where the first data comprises a first subset of data and a second subset of data, and where the program instructions are further configured to cause the computing system to: determine that the first rule does not use the second subset of data to determine whether the behavior is risky, and remove the second subset of data from the first data prior to executing the join operation; where the first table comprises a first row that includes a first subset of the first data and a second row that includes a second subset of the first data, and wherein the program instructions are further configured to cause the computing system to: determine that the first subset of the first data is the same as the second subset of the first data, and remove the second row from the first table prior to executing the join operation; where the interactive user interface comprises a button that allows a user to take an action associated with the displayed alert; where the program instructions are further configured to cause the computing system to: receive, from the user, a selection of the button, update the interactive user interface to display a plurality of actions in response to receiving the selection, receive, from the user, a second selection of a first action in the plurality of actions, and generate a report in response to receiving the second selection; where the program instructions are further configured to cause the computing system to: use a clustering process to separate the first data and the second data into a plurality of clusters, identify a subset of the first data or the second data that fall outside of a first cluster in the plurality of clusters by at least a threshold value, and generate an alert for each of the items in the subset of the first data or the second data; where the program instructions are further configured to cause the computing system to update the clustering process based on actions taken by a user with regard to the generated alerts for each of the items in the subset of the first data or the second data; where the first rule is a cash out rule; where the program instructions are further configured to cause the computing system to: identify, based on an analysis of the first data and the second data, that a first user withdrew no money on a first day, no money on a second day, a first amount of money on a third day, no money on a fourth day, and no money on a fourth day, no money on a wherein a withdrawal of the first amount of money causes the computing system to determine that the behavior is risky, and generate the alert such that the alert corresponds with the first day, the second day, and the third day, does not correspond with the second day, the third day, and the fourth day, and does not correspond with the third day, the fourth day, and the fifth day; where the database further stores historical data, and wherein the program instructions are further configured to cause the computing system to: retrieve the historical data from the database, wherein running the first rule on the historical data causes the computing system to determine that the behavior is risky, merging the first data and the historical data, running the first rule on the merged first data and historical data, determining whether the behavior is risky, and determining that the first data is valid in response to a determination that the behavior is risky; where the database receives data from an issuer database in periodic intervals, and wherein the program instructions are further configured to cause the computing system to: select the first table, where a first subset of the first data is expected to be received at a first time and a second subset of the first data is expected to be received at a second time, determine that the second subset of the first data was not received at the second time, and generate a notification for display in the interactive user interface, wherein the notification instructs a user to retrieve the second subset of the first data; where the first rule is one of a cash out rule, a cash in rule, a sustained cash rule, a behavior outlier rule, a cross-border cash rule, a foreign cash out rule, a high risk countries rule, an external funding rule, a tax refund rule, a card-to-card transfer rule, a watch list rule, or a manual trigger rule; where the alert comprises information identifying a user associated with a prepaid card that caused the computing system to determine that the behavior is risky; where the program instructions are further configured to cause the computing system to determine that the behavior is risky in response to a determination that a first regulation is violated; and where the program instructions are further configured to cause the computing system to transmit the alert via one of an email, a push notification, or a text message.
[0013] Additional embodiments of the disclosure are described below in reference to the appended claims, which may serve as an additional summary of the disclosure.
[0014] In various embodiments, computer systems are disclosed that comprise one or more hardware computer processors in communication with one or more non-transitory computer readable storage devices, wherein the one or more hardware computer processors are configured to execute the plurality of computer executable instructions in order to cause the computer system to operations comprising one or more aspects of the above-described embodiments (including one or more aspects of the appended claims).
[0015] In various embodiments, computer-implemented methods are disclosed in which, under control of one or more hardware computing devices configured with specific computer executable instructions, one or more aspects of the above-described embodiments (including one or more aspects of the appended claims) are implemented and/or performed.
[0016] In various embodiments, non-transitory computer-readable storage mediums storing software instructions are disclosed, wherein, in response to execution by a computing system having one or more hardware processors, the software instructions configure the computing system to perform operations comprising one or more aspects of the above-described embodiments (including one or more aspects of the appended claims).
[0017] Further, as described herein, various embodiments of the system may be configured and/or designed to generate user interface data useable for rendering the various interactive user interfaces described. The user interface data may be used by the system, and/or another computer system, device, and/or software program (for example, a browser program), to render the interactive user interfaces. The interactive user interfaces may be displayed on, for example, electronic displays (including, for example, touch-enabled displays).
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG. 1 illustrates a block diagram of a system for collecting, organizing, and analyzing transaction data.
[0019] FIG. 2 illustrates a user interface displaying a table of raw transaction data collected by an issuer of FIG. 1 .
[0020] FIG. 3 illustrates a user interface displaying a table depicting the results of the validation performed by the transaction data server of FIG. 1 .
[0021] FIG. 4 illustrates another user interface displaying a table of raw transaction data collected by an issuer of FIG. 1 .
[0022] FIG. 5 illustrates a user interface displaying a join table formed from a join operation performed on the table of FIG. 2 and the table of FIG. 4 .
[0023] FIGS. 6A-6M illustrate a user interface displaying generated alerts.
[0024] FIG. 7 illustrates a user interface displaying a table view of generated alerts.
[0025] FIGS. 8A-8D illustrate a user interface depicting a triage reporting of all generated alerts.
[0026] FIG. 9 is a flowchart depicting an illustrative operation of displaying claims adjustments.
[0027] FIG. 10 illustrates a computer system with which certain methods discussed herein may be implemented.
DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS
Overview
[0028] As described above, transactions associated with a prepaid card may not meet regulations, such as regulations put in place to identify and/or prevent fraudulent activity. Such regulations can include U.S. federal regulations and/or statutes (e.g., the CARD Act, the Dodd-Frank Act, Electronic Funds Transfer Act, Federal Reserve regulations, etc.), individual state regulations and/or statutes, internal banking regulations, regulations or rules issued by executive agencies, and/or other similar rules or laws. In particular, prepaid cards have been used as a vehicle to store funds received via deceptive or fraudulent schemes and transactions associated with a prepaid card that do not meet the relevant regulations may indicate such activity. For example, scammers have intimidated consumers (e.g., by posing as Internal Revenue Service agents, utility companies, etc.), demanding that victims wire unpaid funds to a prepaid card or risk being arrested, losing service, and/or the like. As another example, scammers have filed false tax returns that result in a tax refund, and set the refund to be wired to a prepaid card rather than an account owned by the actual taxpayer. Thus, prepaid cards can be used to deprive consumers and/or businesses of millions to billions of dollars.
[0029] In an effort to combat such malicious activity, issuers (e.g., entities that issue prepaid cards) are required to submit a report, such as a currency transaction report (CTR) or a suspicious activity report (SAR), if the transactions associated with a prepaid card indicate that fraud (e.g., money laundering, tax fraud, etc.) could be taking place. Transactions associated with a prepaid card may indicate that fraud could be taking place if the transactions (or even a single transaction) violate one or more regulations that govern the use of prepaid cards.
[0030] Issuers often store transaction data from prepaid cards in a plurality of databases. For example, one database may include transaction data that identifies an amount that was deposited or withdrawn on a card and a time and location where the transaction occurred, another database may include a description of the transaction and an identifier that identifies the user of the prepaid card, and so on. In some cases, to determine whether transactions comply with the relevant regulations, data from multiple databases or data from multiple tables within one or more databases may need to be analyzed. Typically, each individual database includes a large amount of uncompressed data (e.g., on the order of hundreds of gigabytes), so it is nearly impossible for a human fraud analyst to find all data that may be relevant to a particular regulation and/or to identify patterns that may indicate that risky behavior is occurring (e.g., a regulation has been violated). Thus, relying on a human to perform the fraud analysis may not be adequate to identify and/or prevent the harm occurring to consumers and/or businesses.
[0031] The analysis could instead be automated. To perform the analysis, the data from the different databases would have to be combined into a single database, such as via a join or merge table operation. However, because each individual database may include a large amount of uncompressed data, join or merge operations typically implemented by traditional databases may be difficult to run because the join operations cannot process such a large amount of information. Furthermore, once the analysis is performed, a mechanism may need to be implemented so that detected inconsistencies between the transaction data and regulations can be brought to the fraud analyst's attention for further action.
[0032] Accordingly, embodiments of the present disclosure relate to a system that retrieves raw transaction data from issuers, reorganizes the raw transaction data, analyzes the reorganized data to determine whether the relevant regulations have been complied with and/or whether risky or malicious behavior is occurring (which can include the violation of one or more regulations), and generates alerts to notify fraud analysts of possible regulation violations and/or the occurrence of possible risky or malicious behavior. For example, the raw transaction data may be included in a plurality of tables stored within one or more databases. The system may join one or more tables to reorganize the transaction data using several filtering techniques to reduce the processor load required to perform the join operation. Once the transaction data is reorganized using the join operation, the system may run one or more rules to analyze the reorganized transaction data. Each rule may be associated with a regulation that governs the use of prepaid cards or a general category of risky or malicious behavior (e.g., behavior not associated with a specific regulation, but that nonetheless may indicate that fraud or other malicious activity is taking place). The rules may be generated such that duplicate violations are ignored and/or machine learning techniques are used to improve the function of the rule over time. If any of the rules indicate that a regulation may be violated or that risky behavior is occurring, the system may generate an alert for display to a fraud analyst in an interactive user interface. The interactive user interface may allow the fraud analyst to view additional details regarding alerts, organize alerts, filter alerts, and/or take further actions related to the alerts. Thus, the system may be able to efficiently allow prepaid card issuers to identify regulation violations or risky behavior and take appropriate action. The system is described in greater detail below with respect to FIGS. 1-9 .
Transaction Data Collection and Analysis System Overview
[0033] FIG. 1 illustrates a block diagram of a system 100 for collecting, organizing, and analyzing transaction data. The system 100 comprises one or more issuers 110, a transaction data analysis device 130, a transaction data server 140, and a network 120.
[0034] In the embodiment illustrated in FIG. 1 , the one or more issuers 110 (e.g., banks, credit card companies, etc.), which may be implemented by one or more first physical computing devices, are communicatively connected to the transaction data server 140, which may be implemented by one or more second physical computing devices, over the network 120. Similarly, the transaction data analysis device 130 (e.g., operated by a fraud analyst at an entity, such as the issuer or a third party) may be implemented by one or more third physical computing devices and may be communicatively connected to the transaction data server 140 over the network 120. The transaction data server 140 can be operated by the issuer or can be operated by a third party (e.g., a company that contracts with an issuer). In some embodiments, each such physical computing device may be implemented as a computer system including some or all of the components illustrated in the example computing system 1000 of FIG. 10 . For example, the one or more issuers 110, the transaction data analysis device 130, and/or the transaction data server 140 may be implemented in a computer system as a set of program instructions recorded on a machine-readable storage medium.
[0035] The one or more issuers 110 represent devices operated by prepaid card issuers (e.g., banks, credit card companies, etc.). Users may obtain prepaid cards from these prepaid card issuers and load money onto the cards for later use. Each time a transaction (e.g., a deposit, a withdrawal, a purchase, a fee, etc.) takes place using a prepaid card, the transaction is tracked by the issuer 110 associated with the prepaid card. Details of the transaction may be stored in one or more tables and the tables may be stored in one or more databases associated with the issuer 110 (not shown). At preset times or at the request of a fraud analyst, the issuers 110A-N transmit the tables to the transaction data server 140 for processing and analysis.
[0036] The transaction data analysis device 130 represents a device operated by an issuer or third party that allows a fraud analyst to analyze transaction data for a plurality of prepaid cards and view alerts generated by the transaction data server 140. For example, the transaction data analysis device 130 has a display that shows an interactive graphical user interface (GUI), where the interactive GUI allows the fraud analyst to view additional details regarding alerts, organize alerts, filter alerts, and/or take further actions related to the alerts. In an embodiment, the transaction data analysis device 130 includes GUI logic. The GUI logic may be a set of program instructions configured for execution by one or more computer processors of the transaction data analysis device 130, which are operable to receive user input and to display a graphical representation of transaction data and/or alerts using the approaches described herein. The GUI logic may be operable to receive user input from, and display a graphical representation of the claims, in a GUI that is provided on a display (not shown) of the transaction data analysis device 130 and/or another computing device that is in communication with the transaction data analysis device 130.
[0037] The transaction data server 140 may be implemented as a special-purpose computer system having logical elements. In an embodiment, the logical elements may comprise program instructions recorded on one or more machine-readable storage media. Alternatively, the logical elements may be implemented in hardware, firmware, or a combination thereof.
[0038] When executed by one or more processors of the computer system, logic in the transaction data server 140 is operable to receive, store, reorganize, validate, and/or analyze transaction data according to the techniques described herein. The logic in the transaction data server 140 is also operable to run rules on the transaction data to generate alerts for viewing by the fraud analyst according to the techniques described herein. In one embodiment, the transaction data analysis device 130 and/or the transaction data server 140 may be implemented in a Java Virtual Machine (JVM) that is executing in a distributed or non-distributed computer system. In other embodiments, the transaction data analysis device 130 and/or the transaction data server 140 may be implemented as a combination of programming instructions written in any programming language (e.g. C++ or Visual Basic) and hardware components (e.g., memory, CPU time) that have been allocated for executing the program instructions.
[0039] In an embodiment, the network 120 includes any communications network, such as the Internet. The network 120 may be a wired network, a wireless network, or a combination of the two. For example, network 120 may be a local area network (LAN) and/or a wireless area network (WAN).
Transaction Data Tables and Join Operations
[0040] FIG. 2 illustrates a user interface 200 displaying a table 212 of raw transaction data collected by an issuer 110A-N. For example, the raw transaction data may include raw transaction data collected by the issuer 110A-N from one or more prepaid cards managed by the issuer 110A-N. The raw transaction data and/or a schema related to the raw transaction data may be transmitted to the transaction data server 140. Using the schema, the transaction data server 140 may generate various columns, associate the raw transaction data with one or more of the generated columns, and store such information (e.g., in a Hadoop Distributed File System (HDFS)) to generate the table 212 (and/or other tables). For example, the transaction data server 140 may receive the information from the issuers 110A-N and use the schema and the raw transaction data to generate the headers of the columns using the data pipeline system described in U.S. patent application Ser. No. 14/533,433, titled “HISTORY PRESERVING DATA PIPELINE SYSTEM AND METHOD” and filed on Nov. 5, 2014, which is hereby incorporated herein by reference in its entirety.
[0041] As illustrated in FIG. 2 , the interface 200 includes a window 210 that includes the table 212. The table 212 includes the various columns and rows of transaction data. For example, the columns may include a transaction identifier (TransID) column, an account identifier (AccountID) column (e.g., an identifier that uniquely identifies a user), a transaction type identifier (TranstypeID) column, a description column, a transaction postdate (PostDate) column, a transaction amount (TransAmt) column, a transaction requirement identifier (TransReqID), and a time the transaction occurred (LastUpdate) column. While specific columns are depicted in the table 212, this is not meant to be limiting. The table 212 may include any number or type of column related to a transaction.
[0042] The user interface 200 may be displayed on the transaction data analysis device 130, which is in communication with the transaction data server 140. Within the user interface 200, the fraud analyst may be able to download the table 212 locally to the transaction data analysis device 130 by selecting download button 215. The fraud analyst may also be to sort the transaction data by column or by another means using sort button 220.
[0043] Before, after, and/or during the generation of the table 212 (and other tables), the transaction data server 140 may validate the raw transaction data. For example, the transaction data server 140 may expect to receive raw transaction data from the issuers 110A-N in regular intervals (e.g., every minute, every 15 minutes, every hour, etc.). The transaction data server 140 may parse the received raw transaction data and determine which data, if any, is missing or corrupted.
[0044] FIG. 3 illustrates a user interface 300 displaying a table 312 depicting the results of the validation performed by the transaction data server 140. As illustrated in FIG. 3 , a window 310 includes the table 312. The table 312 includes a validation day column, a missing blocks column, a total missing time column, and an isValid column. The validation day column may indicate a day that a validation test was run by the transaction data server 140. The missing blocks column may identify specific times on the corresponding validation day in which raw transaction data is missing. For example, the fourth row in the table 312 indicates that there are 5 times in which raw transaction data is missing. The times may be represented as an absolute time (e.g., GMT time) or a number of seconds from a set time (e.g., a number of minutes since midnight of the validation day). The total missing time column may indicate the number of missing blocks on a given validation day. The isValid column may indicate whether any transaction data corresponding to the validation day is corrupted (e.g., with “true” meaning that no transaction data is corrupted).
[0045] If any transaction data is missing or corrupted, the user interface 300 may generate a notification to alert the fraud analyst of the error. The fraud analyst may then be able to request the missing transaction data or a replacement for the corrupted transaction data.
[0046] In further embodiments, prior to performing the join operations described herein, the transaction data server 140 performs a pre-processing step to further validate the transaction data. For example, the transaction data server 140 may store historical transaction data that has been validated at a previous time. The historical transaction data may be merged with a portion of the received raw transaction data and the transaction data server 140 may run one or more rules (described below) on the merged transaction data to ensure that the results are as expected (e.g., a known alert is generated). The pre-processing step may be run at regular intervals (e.g., daily) to ensure the transaction data is validated. If the transaction data is not validated, the transaction data server 140 can provide a notification to the fraud analyst and/or automatically correct an identified error. The pre-processing step may catch errors, such as off-by-1 errors, that are caused by a change in the format or schema of the raw transaction data (e.g., by the issuers 110A-N).
[0047] FIG. 4 illustrates another user interface 400 displaying a table 412 of raw transaction data collected by an issuer 110A-N. As described herein, the transaction data server 140 may perform join operations to merge data from one or more tables. As illustrated in FIG. 4 , the table 412 includes different columns (and thus different transaction data) than found in the table 212. For example, the table 412 includes an aggregation identifier (AggregationID) column that indicates another identifier that uniquely identifies a user (e.g., via a social security number). In some cases, data found in table 212 (and not in table 412) and data found in table 412 (and not in table 212) may be joined such that the transaction data server 140 can properly run one or more of the rules. Likewise, the transaction data server 140 may join data from other tables (not shown) into a single table or multiple tables such that some or all of the rules can be run.
[0048] FIG. 5 illustrates a user interface 500 displaying a join table 512 formed from a join operation performed on the table 212 and the table 414. The join table 512 may be a new table or a modification of the table 212 or the table 414. The transaction data server 140 may further identify other columns or transaction data in other tables previously generated by the transaction data server 140 (not shown) and join these columns and/or transaction data with the information in the join table 512. For example, the transaction data server 140 may identify other columns or transaction data based on any additional data that may be necessary to run some or all of the rules. Alternatively or in addition, the transaction data server 140 may separately join transaction data from other tables (not shown) to form one or more other join tables. The other join tables may include different data than is present in the join table 512, and thus the transaction data server 140 may run separate rules on the data in the join table 512 and on the data in the other join tables.
[0049] The transaction data server 140 may use several techniques not typically performed during join operations to improve the speed and efficiency of the join operation and to ensure the join operation can be performed even when a large amount of transaction data (e.g., on the order of hundreds of gigabytes) is involved in the join operation (by, for example, reducing the amount of transaction data that is actually joined). For example, in some embodiments the transaction data server 140 identifies a column that is present in each of the tables involved in the join operation (e.g., such as the TransID column in the table 212 and the table 412) and uses the column as the join key. Some columns in the tables involved in the join operation may not be necessary, however. For example, the TransReqID information may not be necessary in order to properly run the rules. Thus, before performing the join operation, the data transaction server 140 may drop columns (and the transaction data corresponding to the dropped columns) from the tables such that the dropped columns are not included in the join table 512. Likewise, certain transactions may not be relevant to any of the rules. For example, withdrawal transactional data may be important to determine whether one or more regulations have been satisfied, but deposit transactional data may not be important to these determinations. Thus, before performing the join operation, the data transaction server 140 can parse each of the tables involved in the join operation and remove entries related to such irrelevant transactions. Furthermore, before performing the join operation, the data transaction server 140 can run a deduplication operation on each table involved in the join operation to remove any duplicate entries in such tables. In an embodiment, the TransID, which is a unique identifier for each transaction, may be used by the data transaction server 140 to determine whether each of the transactions in a table are unique or whether there are duplicates in the table. These techniques may help reduce the size of the raw transaction data, thereby reducing the processor load of the transaction data server 140 when performing the join operation(s).
Rules
[0050] As described above, the transaction data server 140 may run one or more rules on the join table 512 and/or other generated join tables to assess whether the relevant regulations have been complied with, whether generally risky behavior is occurring, and/or to determine whether further action may be necessary. If a rule is triggered, the transaction data server 140 may generate an alert. As an example, the rules may include a cash out rule, a cash in rule, a sustained cash rule, a behavior outlier rule, a cross-border cash rule, a foreign cash out rule, a high risk countries rule, an external funding rule, a tax refund rule, a card-to-card transfer rule, a watch list rule, and/or a manual trigger rule.
[0051] The cash out rule may monitor for one or more cash withdrawal transactions over a single-day or multi-day period (e.g., a one-day period, a three-day period, etc.) that collectively exceed a threshold value (e.g., a monetary value). In an embodiment, the transaction data server 140 groups transaction data from the join table(s) by the AggregationID (e.g., social security number) such that transactions associated with a single user can be analyzed separately from transactions associated with another user. If the AggregationID is unavailable, the transaction data server 140 may group transaction data by the AccountID. Transactions that may include a cash out event include automated teller machine (ATM) withdrawals, point of sale withdrawals, bank teller withdrawals, and/or quasi-cash channels (e.g., casinos). The transaction data server 140 may run the cash out rule on a regular basis (e.g., weekly). Because the cash out rule is triggered when total withdrawals over a multi-day period exceed a threshold value, the cash out rule could be triggered multiple times for the same cash out event (e.g., if on day one, $10,000 is withdrawn, the cash out rule would identify both day two and day three as exceeding the threshold value because the total withdrawals for day zero, day one, and day two would be $10,000 and the total withdrawals for day one, day two, and day three would also be $10,000). Thus, the transaction data server 140 may implement the cash out rule such that the cash out rule is triggered and an alert is generated if the total withdrawals over the multi-day period exceed the threshold value and a withdrawal occurred on the last day of the multi-day period. If no withdrawal occurs on the last day of the multi-day period, then the cash out rule is not triggered, thereby eliminating duplicative alerts.
[0052] The cash in rule may monitor for one or more cash deposits over a single-day or multi-day period (e.g., a one-day period, a three-day period, etc.) that collectively exceed a threshold value (e.g., a monetary value). In an embodiment, the transaction data server 140 groups transaction data from the join table(s) by the AggregationID or the AccountID (e.g., if the AggregationID is unavailable) such that transactions associated with a single user can be analyzed separately from transactions associated with another user. The transaction data server 140 may run the cash in rule on a regular basis (e.g., weekly). The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0053] The sustained cash rule may monitor for accounts that load a minimum amount of cash per month for at least a threshold period of time through cash channels, such as point of sale locations and/or money network sites. If alerts are generated based on the rule being triggered, the transaction data server 140 may rank the alerts based on the amount of churn (e.g., the sum of the cash loads and absolute value of the cash withdrawals over the threshold period of time). The transaction data server 140 may run the sustained cash rule on a regular basis (e.g., monthly). The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0054] The behavior outlier rule may monitor for outliers within certain behavioral clusters over a period of time (e.g., a month). The transaction data server 140 may consider statistical measures, such as the one-month means, standard deviations, and/or transaction counts of cash-in and/or cash-out activity. For example, the behavior outlier rule may be used to identify prepaid cards that are suspicious because such cards are outliers when compared to other cards of the same program. However, if there are a large number of programs (e.g., 10,000 programs) and each program has one prepaid card that is an outlier, then 10,000 alerts may be generated. To reduce the number of alerts to a meaningful number that can be investigated by the fraud analyst, the transaction data server 140 may organize the data using any known clustering technique, where the clustering is based on different features, such as cash-in data, cash-out data, the mean, the mode, the standard deviation, and/or the like, instead of the program names. The transaction data server 140 may initially validate the clustering by using historical transaction data to, for example, prevent overfitting (e.g., by using the historical transaction data to ensure that too many clusters are not created). Initially, the transaction data server 140 may use the behavior outlier rule to identify the top X (e.g., 10) outliers from each of the clusters based on a distance from a center of the cluster (or the outliers that are outside the cluster by at least a threshold value) and generate an alert for each of these outliers. The transaction data server 140 may then monitor subsequent actions (e.g., closed the alert, took an action, etc.) taken by the fraud analyst with respect to these generated alerts. A goal, for example, may be to identify a number of outliers from each of the clusters that are actioned a threshold percentage of the time (e.g., X percent of the time). If a percentage of the outliers from a cluster other than the threshold percentage of the outliers from a cluster are actioned (e.g., Y percent), the transaction data server 140 may use machine learning techniques to adjust the number of outliers that are identified from that cluster such that the threshold percentage is eventually achieved. The transaction data server 140 may run the behavior outlier rule on a regular basis (e.g., periodically). The same cluster definitions may be used each time the behavior outlier rule is run to achieve consistency. The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0055] The cross-border cash rule may monitor for funds that are deposited and/or withdrawn in different countries. The transaction data server 140 may run the cross-border cash rule on a regular basis (e.g., periodically).
[0056] The foreign cash out rule may monitor the withdrawal of cash greater than a threshold value (e.g., a monetary value) within a period of time outside of the first country. The transaction data server 140 may run the foreign cash out rule on a regular basis (e.g., monthly). The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0057] The high risk countries rule may monitor for any deposit and withdrawal that occur in a “high risk” country. Some or all transactions may be geo-tagged such that the high risk countries rule functions properly. The transaction data server 140 may run the high risk countries rule on a regular basis (e.g., periodically). The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0058] The external funding rule may monitor for multiple prepaid card accounts funding the same external source. The transaction data server 140 may generate an alert if more than a threshold number of prepaid cards initiate transfers to the same external source. The transaction data server 140 may run the external funding rule on a regular basis (e.g., periodically). The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0059] The tax refund rule may monitor and identify accounts that receive more than a threshold number of tax refunds. The transaction data server 140 may run the tax refund rule on a regular basis (e.g., periodically). The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0060] The card-to-card transfer rule may identify accounts that transfer more than a threshold amount between them within a period of time. The transaction data server 140 may run the card-to-card rule on a regular basis (e.g., periodically). The transaction data server 140 may run the card-to-card transfer rule in conjunction with the cash in and/or cash out rules. The transaction data server 140 may implement the same deduplication techniques as described above with respect to the cash out rule to eliminate duplicative alerts.
[0061] In an embodiment, a fraud analyst or another user may provide a list of accounts, account identifiers, names, social security numbers, and/or the like that are to be monitored on a regular basis (e.g., weekly). The transaction data server 140 may run a watch list rule, which causes each of the rules described above to be run on the data associated with the listed entities. Each time the watch list rule is run (e.g., weekly), the transaction data server 140 may generate a report indicating that no suspicious activity was detected and/or some suspicious activity was detected (e.g., identifying those rules that were triggered).
[0062] Similarly, a fraud analyst or another user may provide a list of accounts, account identifiers, names, social security numbers, and/or the like that are to be monitored once. The transaction data server 140 may run a manual trigger rule, which causes each of the rules described above (except the watch list rule) to be run on the data associated with the listed entities. When the manual trigger rule is run (just once), the transaction data server 140 may generate a report indicating that no suspicious activity was detected and/or some suspicious activity was detected (e.g., identifying those rules that were triggered).
[0063] Additional rules run by the transaction data server 140 may include a payroll rule and a maximum account rule. The payroll rule may be used by the transaction data server 140 to identify transactions that are illegitimate payroll transactions. The transaction data server 140 may use clustering and the machine learning techniques as described above to find outliers within these transactions, and generate alerts based on the identified outliers. The maximum account rule may identify the maximum number of accounts that can be associated with an address and/or name (and be triggered if the maximum number is exceeded).
Alerts
[0064] If a rule is triggered, the transaction data server 140 may generate the appropriate alert. FIGS. 6A-6M illustrate a user interface 600 displaying generated alerts. The user interface 600 may be displayed in the display of the transaction data analysis device 130. As illustrated in FIG. 6A , the user interface 600 includes a filter window 610 and an alert window 620. The alert window 620 may display one or more alert summaries that each summarize an alert generated by the transaction data server 140. The alert summaries may indicate which alerts are critical and which alerts are not critical. An alert may be critical based on the rule that triggered the generation of the alert and/or a number of rules that have been triggered by a given user or account. The alert summaries may be organized by AggregationID, as indicated by the selection of Aggregation ID button 630. The alert summaries that are displayed may be filtered using any of the filters in the filter window 610.
[0065] The alert summaries may also be organized by source (e.g., rule that triggered the alert) via the selection of source button 640, as illustrated in FIG. 6B . Each of the alert summaries are selectable to view more information about the alert(s). For example, the fraud analyst, using cursor 650, may trigger the cash out alert summary. Selection of the cash out alert summary causes the alert window 620 to display a graph 655 and a list of cash out alerts, as illustrated in FIG. 6C . The graph 655 may indicate a date that an alert was generated and how many alerts were generated on specific days. Each alert in the list of cash out alerts provides a more detail information associated with the alert. For example, alert 658 in the list of cash out alerts identifies the type of rule that triggered the alert (e.g., cash out), an identifier linked to the user of the prepaid card (e.g., the AggregationID, which includes the user's social security number), a date range associated with the alert 658, a date that the alert 658 was generated, an action label 659, and conclusions or results associated with the alert 658. The action label 659 may identify which action has been taken by the fraud analyst in response to the alert 658 and/or may identify that no action has been taken. Conclusions may include the funding percentage (e.g., what percentage of a prepaid card is funded by non-suspicious activity) over various months, a flagged amount, an Account ID, an Aggregation ID, an issuer of the prepaid card, a program name from which the prepaid card was issued, a city of residence for the user of the card, and/or other metadata.
[0066] Selection of the alert 658 may cause the alert window 620 to display even more information associated with the alert 658, as illustrated in FIG. 6D . The alert window 620 may display the same conclusions as discussed above with respect to FIG. 6C . The alert window 620 may also display a name of a person assigned to the alert 658 and a name of a person watching the alert 658. The alert window 620 may also include three tabs: account info tab 672, personal info tab 674, and notes tab 676. The account info tab 672 may display the Account ID, the Account Number, the Card Number, the Program Name, and the Issuer Name associated with the prepaid card that triggered the cash out alert.
[0067] The alert window 620 also includes a take action button 665 and an export button 670. Selection of the export button 670 may allow the fraud analyst to export details of the alert 658 to a file (e.g., a spreadsheet file or an image file). Selection of the take action button 665, using for example the cursor 650, may cause a plurality of options to appear, as illustrated in FIG. 6E .
[0068] Possible action options include closing the alert 658, opening details associated with the alert 658, reviewing the alert 658 (to, for example, generate a report), reassigning the alert 658 to another user, unassigning the alert 658, setting another user as the user watching the alert 658, or removing a user from watching the alert 658.
[0069] If, for example, the close option is selected using the cursor 650, window 678 may appear, as illustrated in FIG. 6F . The window 678 may request the fraud analyst to select a reason why the alert 658 is being closed and provide an option to include additional notes.
[0070] The personal info tab 674 may display the name, Account ID, username, social security number, electronic mail address, phone number, address, and date of birth associated with the prepaid card that triggered the cash out alert, as illustrated in FIG. 6G . The personal info tab 674 may also include a show logs button 680. The show logs button 680, when selected, may show the transaction details for the prepaid card that triggered the alert 658 and a period of time for which transaction details are provided, as illustrated in FIG. 6H .
[0071] The notes tab 676 may include a text box that allows the fraud analyst to enter any notes or comments associated with the alert 658, as illustrated in FIG. 6I . The notes tab 676 further lists the notes or comments that have been previously entered and a time that the notes or comments were entered, as illustrated in FIG. 6J .
[0072] The alert summaries may also be organized by flags (e.g., a list of all alerts organized by type of rule that triggered the alert) via the selection of flags list button 682, as illustrated in FIG. 6K . The fraud analyst may select more button 684 to organize the alert summaries in other ways. For example, the alert summaries can further be organized by issuer, transaction country, and/or by those with a remote account (e.g., an account based in a foreign country), as illustrated in FIG. 6L . Selection of the transaction country option may cause the alert window 620 to organize the alert summaries by the countries from which transactions originated to cause a rule to be triggered, as illustrated in FIG. 6M .
[0073] FIG. 7 illustrates a user interface 700 displaying a table view of generated alerts. The user interface 700 may be displayed in the display of the transaction data analysis device 130. As illustrated in FIG. 7 , the user interface 700 may include a window 710 that includes a table that lists details for various alerts that have been generated, such as AggregationID, flagged month (e.g., the month the alerted was generated), flag date (e.g., date range associated with the alert), conclusions, priority, rule that triggered the alert, and/or a rule ID (e.g., identifies the rule that triggered the alert, the AggregationID, and the flag date). The table can be downloaded using download button 215 or sorted using sort button 220.
[0074] FIGS. 8A-8D illustrate a user interface 800 depicting a triage reporting of all generated alerts. The user interface 800 may be displayed in the display of the transaction data analysis device 130. As illustrated in FIG. 8A , the user interface 800 includes a window 810 that provides a selectable calendar 815 to specify a date range and an alerts tab 820. Within the alerts tab 820, a number of open alerts is indicated, organized by time that the alert has been open (e.g., more than 30 days, 21 to 30 days, 11 to 20 days, 10 or fewer days, etc.), and alert details are provided. The alert details include a total number of alerts, a total number of alerts that have been closed, a percentage of closed alerts for which a report has been approved to be filed, and a number of alerts that have not been closed and that have been open for longer than 30 days.
[0075] The window 810 further includes a rules tab 830 that, when selected, provides additional rules details and a graph 835 indicating reasons why various alerts were closed and a number of alerts that have been closed based on a specific reason, as illustrated in FIG. 8B . The rule details may include a graph 836, such as a bar graph, that indicates a percentage of alerts that have been actioned (e.g., a report was generated) or closed. The rule details further include an indication of a total number of alerts, a total number of alerts that have been closed, a percentage of closed alerts for which a report has been approved to be filed, and a number of alerts that have not been closed and that have been open for longer than 30 days.
[0076] The rule details further include a dropdown menu 838. The dropdown menu 838, when selected using the cursor 650, provides the fraud analyst with the option to view rule details for a specific rule (rather than all the rules together), as illustrated in FIG. 8C . Selection of the cash out rule in the dropdown menu 838, for example, causes the rule details (e.g., the graph 836 and the rule statistics) and the rule closed reasons (e.g., the graph 835) to update to reflect just the statistics for the cash out rule, as illustrated in FIG. 8D .
[0077] In some cases, the user associated with a prepaid card may not be readily apparent or it may be difficult to determine whether two separate accounts are actually for the same user (because, for example, the address of the two accounts is the same). In such a situation, the transaction data server 140 may link perform entity resolution. For example, the transaction data server 140 may generate a graph in which each element of the graph corresponds to an account. A link may be created between elements if the elements share the same property (e.g., the same address, the same AggregationID, the same name, etc.). Once all possible links have been established, the transaction data server 140 may associate all linked elements with a single user or entity and the rules may be run using such information. In some embodiments, the linked elements can be hashed (e.g., one or more properties that cause the linkage could be hashed) to create a unique ID for the single user or entity.
[0078] In some embodiments, the alerts are automatically transmitted by the transaction data server 140 to the transaction data analysis device 130 and/or another user device (e.g., a mobile device operated by a user). The alerts can be transmitted at the time that the alerts are individually generated or at some determined time after generation of the alerts (e.g., as a push notification). When received by the transaction data analysis device 130, one or more of the alerts can cause the device to display the alerts via the activation of an application on the transaction data analysis device 130 (e.g., a browser, a mobile application, etc.). For example, receipt of an alert may automatically activate an application on the transaction data analysis device 130, such as a messaging application (e.g., SMS or MMS messaging application), a standalone application (e.g., a malicious activity monitoring application), or a browser, for example, and display information included in the alert. If the transaction data analysis device 130 is offline when the alert is transmitted, the application may be automatically activated when the transaction data analysis device 130 is online such that the alert is displayed. As another example, receipt of an alert may cause a browser to open and be redirected to a login page generated by the transaction data server 140 so that a user can log in to the transaction data server 140 and view the alert. Alternatively, the alert may include a URL of a webpage (or other online information) associated with the alert, such that when the transaction data analysis device 130 (e.g., a mobile device) receives the alert, a browser (or other application) is automatically activated and the URL included in the alert is accessed via the Internet.
[0079] One or more alerts can be transmitted by being packaged into an electronic message, such as an email, an instant message, a text message, a push notification, a network packet, and/or the like. For example, the electronic message can be an email and the complete alert can be included within the body of the email or a portion of the alert can be included within the subject line or body of the email with a link (e.g., URL) that can be accessed to view the complete alert. The electronic message can be transmitted by the transaction data server 140 to another system (not shown), such as an email server, accessible by the transaction data analysis device 130 or the transaction data analysis device 130 itself. Contents of the electronic message can be displayed within an interactive user interface (e.g., one of the user interfaces 600, 700, and/or 800) generated by the email server and/or the transaction data analysis device 130 such that the user can view the alert or a portion thereof.
Example Process Flow
[0080] FIG. 9 is a flowchart 900 depicting an illustrative operation of reorganizing and analyzing transaction data to generate alerts. Depending on the embodiment, the method of FIG. 9 may be performed by various computing devices, such as by the transaction data analysis device 130 and/or the transaction data server 140. For ease of discussion, the method is discussed herein with reference to the transaction data server 140. Depending on the embodiment, the method of FIG. 9 may include fewer and/or additional blocks and the blocks may be performed in an order different than illustrated.
[0081] In block 902, a first table and a second table are retrieved. The first table may include a first column header, a second column header, and first data corresponding to the first column header or the second column header. The second table may include the first column header, a third column header, and second data corresponding to the first column header or the third column header.
[0082] In block 904, it is identified that the first column header is included in the first table and the second table. For example, the first column header may be the Aggregation ID.
[0083] In block 906, a join operation to generate a third table using the first column header as a join key is executed. The third table may include the first column header, the second column header, the third column header, and the first and second data.
[0084] In block 908, a first rule from a plurality of rules is selected. The first rule may be associated with a first regulation that governs the use of prepaid cards.
[0085] In block 910, the first rule is run on the third table to determine whether the first regulation is violated. The first rule may be run on a periodic basis.
[0086] In block 912, an alert is generated in response to a determination that the first regulation is violated. The alert may include information identifying a user associated with the prepaid card that triggered the generation of the alert and the violation of the first regulation.
[0087] In block 914, the alert is displayed in an interactive user interface. For example, the alert may be displayed as depicted in FIGS. 6A-6M . The interactive user interface may also display a summary of generated alerts, as depicted in FIGS. 8A-8D .
Implementation Mechanisms
[0088] According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.
[0089] Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.
[0090] For example, FIG. 10 is a block diagram that illustrates a computer system 1000 upon which an embodiment may be implemented. For example, any of the computing devices discussed herein, such as the transaction data analysis device 130, the transaction data server 140, and the issuers 110 may include some or all of the components and/or functionality of the computer system 1000.
[0091] Computer system 1000 includes a bus 1002 or other communication mechanism for communicating information, and a hardware processor, or multiple processors, 1004 coupled with bus 1002 for processing information. Hardware processor(s) 1004 may be, for example, one or more general purpose microprocessors.
[0092] Computer system 1000 also includes a main memory 1006, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 1002 for storing information and instructions to be executed by processor 1004. Main memory 1006 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1004. Such instructions, when stored in storage media accessible to processor 1004, render computer system 1000 into a special-purpose machine that is customized to perform the operations specified in the instructions.
[0093] Computer system 1000 further includes a read only memory (ROM) 1008 or other static storage device coupled to bus 1002 for storing static information and instructions for processor 1004. A storage device 1010, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 1002 for storing information and instructions.
[0094] Computer system 1000 may be coupled via bus 1002 to a display 1012, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. An input device 1014, including alphanumeric and other keys, is coupled to bus 1002 for communicating information and command selections to processor 1004. Another type of user input device is cursor control 1016, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 804 and for controlling cursor movement on display 1012. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.
[0095] Computing system 1000 may include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
[0096] In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage
[0097] Computer system 1000 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 1000 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 1000 in response to processor(s) 1004 executing one or more sequences of one or more instructions contained in main memory 1006. Such instructions may be read into main memory 1006 from another storage medium, such as storage device 1010. Execution of the sequences of instructions contained in main memory 1006 causes processor(s) 1004 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
[0098] The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 1010. Volatile media includes dynamic memory, such as main memory 1006. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.
[0099] Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between nontransitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 802. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
[0100] Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 804 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 1000 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 1002. Bus 1002 carries the data to main memory 1006, from which processor 1004 retrieves and executes the instructions. The instructions received by main memory 1006 may retrieve and execute the instructions. The instructions received by main memory 1006 may optionally be stored on storage device 1010 either before or after execution by processor 1004.
[0101] Computer system 1000 also includes a communication interface 1018 coupled to bus 1002. Communication interface 1018 provides a two-way data communication coupling to a network link 1020 that is connected to a local network 1022. For example, communication interface 1018 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 1018 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 1018 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0102] Network link 1020 typically provides data communication through one or more networks to other data devices. For example, network link 1020 may provide a connection through local network 1022 to a host computer 1024 or to data equipment operated by an Internet Service Provider (ISP) 1026. ISP 1026 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 1028. Local network 1022 and Internet 1028 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 1020 and through communication interface 1018, which carry the digital data to and from computer system 1000, are example forms of transmission media.
[0103] Computer system 1000 can send messages and receive data, including program code, through the network(s), network link 1020 and communication interface 1018. In the Internet example, a server 1030 might transmit a requested code for an application program through Internet 1028, ISP 1026, local network 1022 and communication interface 1018.
[0104] The received code may be executed by processor 1004 as it is received, and/or stored in storage device 1010, or other non-volatile storage for later execution.
TERMINOLOGY
[0105] Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry.
[0106] The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
[0107] Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
[0108] The term “comprising” as used herein should be given an inclusive rather than exclusive interpretation. For example, a general purpose computer comprising one or more processors should not be interpreted as excluding other computer components, and may possibly include such components as memory, input/output devices, and/or network interfaces, among others.
[0109] Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
[0110] It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
Claims
What is claimed is:
1. A computing system configured to process a large amount of dynamically updating data, the computing system comprising:
a database storing a first table and a second table associated with transaction data received from one or more accounts, wherein the first table comprises a first column header, a second column header, and first data corresponding to the first column header or the second column header, and wherein the second table comprises the first column header, a third column header, a fourth column header, and second data corresponding to the first column header or the third column header;
a computer processor; and
a computer readable storage medium storing program instructions configured for execution by the computer processor in order to cause the computing system to:
select a first rule from a plurality of rules, wherein the first rule is associated with a behavior associated with the one or more accounts;
retrieve the first table and the second table from the database;
identify that the first column header is included in the first table and the second table;
determine that the first rule does not use data associated with the fourth column header to determine whether the behavior is risky;
remove the fourth column header from the second table in response to the determination that the first rule does not use data associated with the fourth column header to determine whether the behavior is risky;
execute a join operation to generate a third table using the first column header as a join key, wherein the third table comprises the first column header, the second column header, the third column header, the first data, and the second data and does not comprise the fourth column header;
run the first rule on the third table to determine whether the behavior is risky;
generate an alert in response to a determination that the behavior is risky; and
transmit the alert for display in an interactive user interface.
2. The computing system of claim 1, wherein the program instructions are further configured to cause the computing system to
remove the fourth column from the second table prior to executing the join operation.
3. The computing system of claim 1, wherein the first data comprises a first subset of data and a second subset of data, and wherein the program instructions are further configured to cause the computing system to:
determine that the first rule does not use the second subset of data to determine whether the behavior is risky; and
remove the second subset of data from the first data prior to executing the join operation.
4. The computing system of claim 1, wherein the first table comprises a first row that includes a first subset of the first data and a second row that includes a second subset of the first data, and wherein the program instructions are further configured to cause the computing system to:
determine that the first subset of the first data is the same as the second subset of the first data; and
remove the second row from the first table prior to executing the join operation.
5. The computing system of claim 1, wherein the interactive user interface comprises a button that allows a user to take an action associated with the displayed alert.
6. The computing system of claim 1, wherein the program instructions are further configured to cause the computing system to:
use a clustering process to separate the first data and the second data into a plurality of clusters;
identify a subset of the first data or the second data that fall outside of a first cluster in the plurality of clusters by at least a threshold value; and
generate an alert for each of the items in the subset of the first data or the second data.
7. The computing system of claim 1, wherein the first rule is a cash out rule.
8. The computing system of claim 1, wherein the database further stores historical data, and wherein the program instructions are further configured to cause the computing system to:
retrieve the historical data from the database, wherein running the first rule on the historical data causes the computing system to determine that the behavior is risky;
merging the first data and the historical data;
running the first rule on the merged first data and historical data;
determining whether the behavior is risky; and
determining that the first data is valid in response to a determination that the behavior is risky.
9. The computing system of claim 1, wherein the database receives data from an issuer database in periodic intervals, and wherein the program instructions are further configured to cause the computing system to:
select the first table, wherein a first subset of the first data is expected to be received at a first time and a second subset of the first data is expected to be received at a second time;
determine that the second subset of the first data was not received at the second time; and
generate a notification for display in the interactive user interface, wherein the notification instructs a user to retrieve the second subset of the first data.
10. The computing system of claim 1, wherein the first rule is one of a cash out rule, a cash in rule, a sustained cash rule, a behavior outlier rule, a cross-border cash rule, a foreign cash out rule, a high risk countries rule, an external funding rule, a tax refund rule, a card-to-card transfer rule, a watch list rule, or a manual trigger rule.
11. The computing system of claim 1, wherein the alert comprises information identifying a user associated with a prepaid card that caused the computing system to determine that the behavior is risky.
12. The computing system of claim 1, wherein the program instructions are further configured to cause the computing system to determine that the behavior is risky in response to a determination that a first regulation is violated.
13. The computing system of claim 1, wherein the program instructions are further configured to cause the computing system to transmit the alert via one of an email, a push notification, or a text message.
14. The computing system of claim 5, wherein the program instructions are further configured to cause the computing system to:
receive, from the user, a selection of the button;
update the interactive user interface to display a plurality of actions in response to receiving the selection;
receive, from the user, a second selection of a first action in the plurality of actions; and
generate a report in response to receiving the second selection.
15. The computing system of claim 6, wherein the program instructions are further configured to cause the computing system to update the clustering process based on actions taken by a user with regard to the generated alerts for each of the items in the subset of the first data or the second data.
16. The computing system of claim 7, wherein the program instructions are further configured to cause the computing system to:
identify, based on an analysis of the first data and the second data, that a first user withdrew no money on a first day, no money on a second day, a first amount of money on a third day, no money on a fourth day, and no money on a fifth day, wherein a withdrawal of the first amount of money causes the computing system to determine that the behavior is risky; and
generate the alert such that the alert corresponds with the first day, the second day, and the third day, does not correspond with the second day, the third day, and the fourth day, and does not correspond with the third day, the fourth day, and the fifth day.
Patent Citations (225)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5892900(A) | 1999-04-01 | Ginter et al. | Applicant |
| US6094643(A) | 2000-07-01 | Anderson et al. | Applicant |
| US6430305(B1) | 2002-08-01 | Decker | Applicant |
| US6820135(B1) | 2004-11-01 | Dingman | Applicant |
| US6978419(B1) | 2005-12-01 | Kantrowitz | Applicant |
| US6980984(B1) | 2005-12-01 | Huffman et al. | Applicant |
| US7168039(B2) | 2007-01-01 | Bertram | Applicant |
| US7617232(B2) | 2009-11-01 | Gabbert et al. | Applicant |
| US7756843(B1) | 2010-07-01 | Palmer | Applicant |
| US7899796(B1) | 2011-03-01 | Borthwick et al. | Applicant |
| US7917376(B2) | 2011-03-01 | Bellin et al. | Applicant |
| US7941321(B2) | 2011-05-01 | Greenstein et al. | Applicant |
| US7971150(B2) | 2011-06-01 | Raskutti et al. | Applicant |
| US8036971(B2) | 2011-10-01 | Aymeloglu et al. | Applicant |
| US8046283(B2) | 2011-10-01 | Burns | Applicant |
| US8054756(B2) | 2011-11-01 | Chand et al. | Applicant |
| US8214490(B1) | 2012-07-01 | Vos et al. | Applicant |
| US8229902(B2) | 2012-07-01 | Vishniac et al. | Applicant |
| US8290838(B1) | 2012-10-01 | Thakur et al. | Applicant |
| US8302855(B2) | 2012-11-01 | Ma et al. | Applicant |
| US8386377(B1) | 2013-02-01 | Xiong | Applicant |
| US8473454(B2) | 2013-06-01 | Evanitsky et al. | Applicant |
| US8484115(B2) | 2013-07-01 | Aymeloglu et al. | Applicant |
| US8554709(B2) | 2013-10-01 | Goodson et al. | Applicant |
| US8589273(B2) | 2013-11-01 | Creeden et al. | Applicant |
| US8595234(B2) | 2013-11-01 | Siripurapu et al. | Applicant |
| US8600872(B1) | 2013-12-01 | Yan | Applicant |
| US8666861(B2) | 2014-03-01 | Li et al. | Applicant |
| US8688573(B1) | 2014-04-01 | Rukonic et al. | Applicant |
| US8744890(B1) | 2014-06-01 | Bernier | Applicant |
| US8787939(B2) | 2014-07-01 | Papakipos et al. | Applicant |
| US8812960(B1) | 2014-08-01 | Sun et al. | Applicant |
| US8924388(B2) | 2014-12-01 | Elliot et al. | Applicant |
| US8924389(B2) | 2014-12-01 | Elliot et al. | Applicant |
| US8938686(B1) | 2015-01-01 | Erenrich et al. | Applicant |
| US8949164(B1) | 2015-02-01 | Mohler | Applicant |
| US9100428(B1) | 2015-08-01 | Visbal | Applicant |
| US9129219(B1) | 2015-09-01 | Robertson et al. | Applicant |
| US2001/0021936(A1) | 2001-09-01 | Bertram | Applicant |
| US2001/0027424(A1) | 2001-10-01 | Torigoe | Applicant |
| US2002/0065708(A1) | 2002-05-01 | Senay et al. | Applicant |
| US2002/0095360(A1) | 2002-07-01 | Joao | Applicant |
| US2002/0095658(A1) | 2002-07-01 | Shulman | Applicant |
| US2002/0103705(A1) | 2002-08-01 | Brady | Applicant |
| US2002/0147805(A1) | 2002-10-01 | Leshem et al. | Applicant |
| US2003/0126102(A1) | 2003-07-01 | Borthwick | Applicant |
| US2004/0034570(A1) | 2004-02-01 | Davis | Applicant |
| US2004/0111480(A1) | 2004-06-01 | Yue | Applicant |
| US2004/0153418(A1) | 2004-08-01 | Hanweck | Applicant |
| US2004/0236688(A1) | 2004-11-01 | Bozeman | Applicant |
| US2005/0010472(A1) | 2005-01-01 | Quatse et al. | Applicant |
| US2005/0086207(A1) | 2005-04-01 | Heuer et al. | Applicant |
| US2005/0133588(A1) | 2005-06-01 | Williams | Applicant |
| US2005/0149455(A1) | 2005-07-01 | Bruesewitz et al. | Applicant |
| US2005/0154628(A1) | 2005-07-01 | Eckart et al. | Applicant |
| US2005/0154769(A1) | 2005-07-01 | Eckart et al. | Applicant |
| US2006/0026120(A1) | 2006-02-01 | Carolan et al. | Applicant |
| US2006/0080283(A1) | 2006-04-01 | Shipman | Applicant |
| US2006/0143034(A1) | 2006-06-01 | Rothermel | Applicant |
| US2006/0143075(A1) | 2006-06-01 | Carr et al. | Applicant |
| US2006/0143079(A1) | 2006-06-01 | Basak et al. | Applicant |
| US2006/0242040(A1) | 2006-10-01 | Rader | Applicant |
| US2007/0000999(A1) | 2007-01-01 | Kubo et al. | Applicant |
| US2007/0011304(A1) | 2007-01-01 | Error | Applicant |
| US2007/0038646(A1) | 2007-02-01 | Thota | Applicant |
| US2007/0150369(A1) | 2007-06-01 | Zivin | Applicant |
| US2007/0150801(A1) | 2007-06-01 | Chidlovskii et al. | Applicant |
| US2007/0156673(A1) | 2007-07-01 | Maga | Applicant |
| US2007/0162454(A1) | 2007-07-01 | D'Albora et al. | Applicant |
| US2007/0185867(A1) | 2007-08-01 | Maga | Applicant |
| US2007/0192122(A1) | 2007-08-01 | Routson | Applicant |
| US2007/0208736(A1) | 2007-09-01 | Tanigawa et al. | Applicant |
| US2007/0284433(A1) | 2007-12-01 | Domenica et al. | Applicant |
| US2008/0103996(A1) | 2008-05-01 | Forman et al. | Applicant |
| US2008/0208735(A1) | 2008-08-01 | Balet | Applicant |
| US2008/0222295(A1) | 2008-09-01 | Robinson et al. | Applicant |
| US2008/0255973(A1) | 2008-10-01 | El Wade et al. | Applicant |
| US2008/0313132(A1) | 2008-12-01 | Hao et al. | Applicant |
| US2009/0055251(A1) | 2009-02-01 | Shah et al. | Applicant |
| US2009/0094270(A1) | 2009-04-01 | Alirez | Applicant |
| US2009/0106178(A1) | 2009-04-01 | Chu | Applicant |
| US2009/0112745(A1) | 2009-04-01 | Stefanescu | Applicant |
| US2009/0125359(A1) | 2009-05-01 | Knapic | Applicant |
| US2009/0125459(A1) | 2009-05-01 | Norton et al. | Applicant |
| US2009/0157732(A1) | 2009-06-01 | Hao | Applicant |
| US2009/0187546(A1) | 2009-07-01 | Whyte et al. | Applicant |
| US2009/0187548(A1) | 2009-07-01 | Ji et al. | Applicant |
| US2009/0249244(A1) | 2009-10-01 | Robinson et al. | Applicant |
| US2009/0271343(A1) | 2009-10-01 | Vaiciulis et al. | Applicant |
| US2009/0307049(A1) | 2009-12-01 | Elliott et al. | Applicant |
| US2009/0313463(A1) | 2009-12-01 | Pang et al. | Applicant |
| US2009/0319418(A1) | 2009-12-01 | Herz | Applicant |
| US2009/0319891(A1) | 2009-12-01 | MacKinlay | Applicant |
| US2010/0030722(A1) | 2010-02-01 | Goodson et al. | Applicant |
| US2010/0031141(A1) | 2010-02-01 | Summers et al. | Applicant |
| US2010/0042922(A1) | 2010-02-01 | Bradateanu et al. | Applicant |
| US2010/0057622(A1) | 2010-03-01 | Faith et al. | Applicant |
| US2010/0070842(A1) | 2010-03-01 | Aymeloglu et al. | Applicant |
| US2010/0094765(A1) | 2010-04-01 | Nandy | Examiner |
| US2010/0098318(A1) | 2010-04-01 | Anderson | Applicant |
| US2010/0114887(A1) | 2010-05-01 | Conway et al. | Applicant |
| US2010/0131502(A1) | 2010-05-01 | Fordham | Applicant |
| US2010/0161735(A1) | 2010-06-01 | Sharma | Applicant |
| US2010/0191563(A1) | 2010-07-01 | Schlaifer et al. | Applicant |
| US2010/0228812(A1) | 2010-09-01 | Uomini | Applicant |
| US2010/0235915(A1) | 2010-09-01 | Memon et al. | Applicant |
| US2010/0262688(A1) | 2010-10-01 | Hussain et al. | Applicant |
| US2010/0312837(A1) | 2010-12-01 | Bodapati et al. | Applicant |
| US2011/0029526(A1) | 2011-02-01 | Knight et al. | Applicant |
| US2011/0061013(A1) | 2011-03-01 | Bilicki et al. | Applicant |
| US2011/0078055(A1) | 2011-03-01 | Faribault et al. | Applicant |
| US2011/0078173(A1) | 2011-03-01 | Seligmann et al. | Applicant |
| US2011/0093327(A1) | 2011-04-01 | Fordyce et al. | Applicant |
| US2011/0099133(A1) | 2011-04-01 | Chang et al. | Applicant |
| US2011/0153384(A1) | 2011-06-01 | Horne et al. | Applicant |
| US2011/0173093(A1) | 2011-07-01 | Psota et al. | Applicant |
| US2011/0208565(A1) | 2011-08-01 | Ross et al. | Applicant |
| US2011/0213655(A1) | 2011-09-01 | Henkin | Applicant |
| US2011/0218955(A1) | 2011-09-01 | Tang | Applicant |
| US2011/0270604(A1) | 2011-11-01 | Qi et al. | Applicant |
| US2011/0270834(A1) | 2011-11-01 | Sokolan et al. | Applicant |
| US2011/0289397(A1) | 2011-11-01 | Eastmond et al. | Applicant |
| US2011/0289420(A1) | 2011-11-01 | Morioka et al. | Applicant |
| US2011/0295649(A1) | 2011-12-01 | Fine | Applicant |
| US2011/0307382(A1) | 2011-12-01 | Siegel et al. | Applicant |
| US2011/0314007(A1) | 2011-12-01 | Dassa et al. | Applicant |
| US2011/0314024(A1) | 2011-12-01 | Chang et al. | Applicant |
| US2012/0011238(A1) | 2012-01-01 | Rathod | Applicant |
| US2012/0011245(A1) | 2012-01-01 | Gillette et al. | Applicant |
| US2012/0022945(A1) | 2012-01-01 | Falkenborg et al. | Applicant |
| US2012/0054284(A1) | 2012-03-01 | Rakshit | Applicant |
| US2012/0059853(A1) | 2012-03-01 | Jagota | Applicant |
| US2012/0066166(A1) | 2012-03-01 | Curbera et al. | Applicant |
| US2012/0079363(A1) | 2012-03-01 | Folting et al. | Applicant |
| US2012/0084117(A1) | 2012-04-01 | Tavares et al. | Applicant |
| US2012/0084287(A1) | 2012-04-01 | Lakshminarayan et al. | Applicant |
| US2012/0117082(A1) | 2012-05-01 | Koperda et al. | Applicant |
| US2012/0131512(A1) | 2012-05-01 | Takeuchi et al. | Applicant |
| US2012/0159362(A1) | 2012-06-01 | Brown et al. | Applicant |
| US2012/0173381(A1) | 2012-07-01 | Smith | Applicant |
| US2012/0203708(A1) | 2012-08-01 | Psota et al. | Applicant |
| US2012/0215784(A1) | 2012-08-01 | King et al. | Applicant |
| US2012/0221553(A1) | 2012-08-01 | Wittmer et al. | Applicant |
| US2012/0226523(A1) | 2012-09-01 | Weiss | Applicant |
| US2012/0245976(A1) | 2012-09-01 | Kumar et al. | Applicant |
| US2012/0296907(A1) | 2012-11-01 | Long et al. | Applicant |
| US2012/0323888(A1) | 2012-12-01 | Osann, Jr. | Applicant |
| US2013/0016106(A1) | 2013-01-01 | Yip et al. | Applicant |
| US2013/0054306(A1) | 2013-02-01 | Bhalla | Applicant |
| US2013/0057551(A1) | 2013-03-01 | Ebert et al. | Applicant |
| US2013/0073454(A1) | 2013-03-01 | Busch | Applicant |
| US2013/0096988(A1) | 2013-04-01 | Grossman et al. | Applicant |
| US2013/0110746(A1) | 2013-05-01 | Ahn | Applicant |
| US2013/0110822(A1) | 2013-05-01 | Ikeda et al. | Applicant |
| US2013/0151148(A1) | 2013-06-01 | Parundekar et al. | Applicant |
| US2013/0151453(A1) | 2013-06-01 | Bhanot et al. | Applicant |
| US2013/0166348(A1) | 2013-06-01 | Scotto | Applicant |
| US2013/0166480(A1) | 2013-06-01 | Popescu et al. | Applicant |
| US2013/0185245(A1) | 2013-07-01 | Anderson | Applicant |
| US2013/0185307(A1) | 2013-07-01 | El-Yaniv et al. | Applicant |
| US2013/0208565(A1) | 2013-08-01 | Castellanos et al. | Applicant |
| US2013/0226318(A1) | 2013-08-01 | Procyk | Applicant |
| US2013/0238616(A1) | 2013-09-01 | Rose et al. | Applicant |
| US2013/0246170(A1) | 2013-09-01 | Gross et al. | Applicant |
| US2013/0246537(A1) | 2013-09-01 | Gaddala | Applicant |
| US2013/0246597(A1) | 2013-09-01 | Iizawa et al. | Applicant |
| US2013/0263019(A1) | 2013-10-01 | Castellanos et al. | Applicant |
| US2013/0267207(A1) | 2013-10-01 | Hao et al. | Applicant |
| US2013/0282696(A1) | 2013-10-01 | John et al. | Applicant |
| US2013/0290825(A1) | 2013-10-01 | Arndt et al. | Applicant |
| US2013/0297619(A1) | 2013-11-01 | Chandrasekaran et al. | Applicant |
| US2013/0304770(A1) | 2013-11-01 | Boero et al. | Applicant |
| US2014/0012796(A1) | 2014-01-01 | Petersen et al. | Applicant |
| US2014/0040371(A1) | 2014-02-01 | Gurevich et al. | Applicant |
| US2014/0058914(A1) | 2014-02-01 | Song et al. | Applicant |
| US2014/0067611(A1) | 2014-03-01 | Adachi et al. | Applicant |
| US2014/0068487(A1) | 2014-03-01 | Steiger et al. | Applicant |
| US2014/0095273(A1) | 2014-04-01 | Tang et al. | Applicant |
| US2014/0095509(A1) | 2014-04-01 | Patton | Applicant |
| US2014/0108068(A1) | 2014-04-01 | Williams | Applicant |
| US2014/0108380(A1) | 2014-04-01 | Gotz et al. | Applicant |
| US2014/0108985(A1) | 2014-04-01 | Scott et al. | Applicant |
| US2014/0123279(A1) | 2014-05-01 | Bishop et al. | Applicant |
| US2014/0136285(A1) | 2014-05-01 | Carvalho | Applicant |
| US2014/0143009(A1) | 2014-05-01 | Brice et al. | Applicant |
| US2014/0156527(A1) | 2014-06-01 | Grigg et al. | Applicant |
| US2014/0157172(A1) | 2014-06-01 | Peery et al. | Applicant |
| US2014/0164502(A1) | 2014-06-01 | Khodorenko et al. | Applicant |
| US2014/0189536(A1) | 2014-07-01 | Lange et al. | Applicant |
| US2014/0195515(A1) | 2014-07-01 | Baker et al. | Applicant |
| US2014/0222521(A1) | 2014-08-01 | Chait | Applicant |
| US2014/0222752(A1) | 2014-08-01 | Isman | Examiner |
| US2014/0222793(A1) | 2014-08-01 | Sadkin et al. | Applicant |
| US2014/0229554(A1) | 2014-08-01 | Grunin et al. | Applicant |
| US2014/0310266(A1) | 2014-10-01 | Greenfield | Applicant |
| US2014/0316911(A1) | 2014-10-01 | Gross | Applicant |
| US2014/0330845(A1) | 2014-11-01 | Feldschuh | Applicant |
| US2014/0344230(A1) | 2014-11-01 | Krause et al. | Applicant |
| US2014/0358829(A1) | 2014-12-01 | Hurwitz | Applicant |
| US2014/0366132(A1) | 2014-12-01 | Stiansen et al. | Applicant |
| US2015/0073929(A1) | 2015-03-01 | Psota et al. | Applicant |
| US2015/0073954(A1) | 2015-03-01 | Braff | Applicant |
| US2015/0095773(A1) | 2015-04-01 | Gonsalves et al. | Applicant |
| US2015/0100897(A1) | 2015-04-01 | Sun et al. | Applicant |
| US2015/0106379(A1) | 2015-04-01 | Elliot et al. | Applicant |
| US2015/0134512(A1) | 2015-05-01 | Mueller | Examiner |
| US2015/0134666(A1) | 2015-05-01 | Gattiker et al. | Applicant |
| US2015/0135256(A1) | 2015-05-01 | Hoy et al. | Applicant |
| US2015/0188872(A1) | 2015-07-01 | White | Applicant |
| US2015/0338233(A1) | 2015-11-01 | Cervelli et al. | Applicant |
| US2015/0379413(A1) | 2015-12-01 | Robertson et al. | Applicant |
| US2016/0004764(A1) | 2016-01-01 | Chakerian et al. | Applicant |
| CN102546446 | 2012-07-01 | Applicant | |
| CN103167093 | 2013-06-01 | Applicant | |
| CN102054015 | 2014-05-01 | Applicant | |
| DE102014204827 | 2014-09-01 | Applicant | |
| DE102014204830 | 2014-09-01 | Applicant | |
| DE102014204834 | 2014-09-01 | Applicant | |
| EP2487610 | 2012-08-01 | Applicant | |
| EP2858018 | 2015-04-01 | Applicant | |
| EP2869211 | 2015-05-01 | Applicant | |
| EP2889814 | 2015-07-01 | Applicant | |
| EP2892197 | 2015-07-01 | Applicant | |
| EP2963595 | 2016-01-01 | Applicant | |
| WO2005/116851 | 2005-12-01 | Applicant |
Non-Patent Literature (125)
- Amnet, “5 Great Tools for Visualizing Your Twitter Followers,” posted Aug. 4, 2010, http://www.amnetblog.com/component/content/article/115-5-grate-tools-for-visualizing-your-twitter-followers.html.Applicant
- Appacts, “Smart Thinking for Super Apps,” http://www.appacts.com Printed Jul. 18, 2013 in 4 pages.Applicant
- Apsalar, “Data Powered Mobile Advertising,” “Free Mobile App Analytics” and various analytics related screen shots http://apsalar.com Printed Jul. 18, 2013 in 8 pages.Applicant
- Capptain—Pilot Your Apps, http://www.capptain.com Printed Jul. 18, 2013 in 6 pages.Applicant
- Celik, Tantek, “CSS Basic User Interface Module Level 3 (CSS3 UI),” Section 8 Resizing and Overflow, Jan. 17, 2012, retrieved from internet http://www.w3.org/TR/2012/WO-css3-ui-20120117/#resizing-amp-overflow retrieved on May 18, 2015.Applicant
- Chaudhuri et al., “An Overview of Business Intelligence Technology,” Communications of the ACM, Aug. 2011, vol. 54, No. 8.Applicant
- Cohn et al., “Semi-supervised Clustering with User Feedback,” Constrained Clustering: Advances in Algorithms, Theory, and Applications 4.1, 2003, pp. 17-32.Applicant
- Countly Mobile Analytics, http://count.ly/ Printed Jul. 18, 2013 in 9 pages.Applicant
- DISTIMO—App Analytics, http://www.distimo.com/app-analytics Printed Jul. 18, 2013 in 5 pages.Applicant
- Flurry Analytics, http://www.flurry.com/ Printed Jul. 18, 2013 in 14 pages.Applicant
- Google Analytics Official Website—Web Analytics & Reporting, http://www.google.com/analytics.index.html Printed Jul. 18, 2013 in 22 pages.Applicant
- Gorr et al., “Crime Hot Spot Forecasting: Modeling and Comparative Evaluation,” Grant 98-IJ-CX-K005, May 6, 2002, 37 pages.Applicant
- Gu et al., “Record Linkage: Current Practice and Future Directions,” Jan. 15, 2004, pp. 32.Applicant
- Hansen et al. “Analyzing Social Media Networks with NodeXL: Insights from a Connected World”, Chapter 4, pp. 53-67 and Chapter 10, pp. 143-164, published Sep. 2010.Applicant
- Hua et al., “A Multi-attribute Data Structure with Parallel Bloom Filters for Network Services” HiPC 2006, LNCS 4297, pp. 277-288, 2006.Applicant
- “HunchLab: Heat Map and Kernel Density Calculation for Crime Analysis,” Azavea Journal, printed from www.azavea.com/blogs/newsletter/v414/kernel-density-capabilities-added-to-hunchlab/ on Sep. 9, 2014, 2 pages.Applicant
- Keylines.com, “An Introduction to KeyLines and Network Visualization,” Mar. 2014, http://keylines.com/wp-content/uploads/2014/03/KeyLines-White-Paper.pdf downloaded May 12, 2014 in 8 pages.Applicant
- Keylines.com, “KeyLines Datasheet,” Mar. 2014, http://keylines.com/wp-content/uploads/2014/03/KeyLines-datasheet.pdf downloaded May 12, 2014 in 2 pages.Applicant
- Keylines.com, “Visualizing Threats: Improved Cyber Security Through Network Visualization,” Apr. 2014, http://keylines.com/wp-content/uploads/2014/04/Visualizing-Threats1.pdf downloaded May 12, 2014 in 10 pages.Applicant
- Kontagent Mobile Analytics, http://www.kontagent.com/ Printed Jul. 18, 2013 in 9 pages.Applicant
- Localytics—Mobile App Marketing & Analytics, http://www.localytics.com/ Printed Jul. 18, 2013 in 12 pages.Applicant
- Manno et al., “Introducing Collaboration in Single-user Applications through the Centralized Control Architecture,” 2010, pp. 10.Applicant
- Mixpanel—Mobile Analytics, https://mixpanel.com/ Printed Jul. 18, 2013 in 13 pages.Applicant
- Open Web Analytics (OWA), http://www.openwebanalytics.com/ Printed Jul. 19, 2013 in 5 pages.Applicant
- Piwik—Free Web Analytics Software. http://piwik.org/ Printed Jul. 19, 2013 in18 pages.Applicant
- “Refresh CSS Ellipsis When Resizing Container—Stack Overflow,” Jul. 31, 2013, retrieved from internet http://stackoverflow.com/questions/17964681/refresh-css-ellipsis-when-resizing-container, retrieved on May 18, 2015.Applicant
- Sigrist et al., “PROSITE, a Protein Domain Database for Functional Characterization and Annotation,” Nucleic Acids Research 38.Suppl 1, 2010, pp. D161-D166.Applicant
- StatCounter—Free Invisible Web Tracker, Hit Counter and Web Stats, http://statcounter.com/ Printed Jul. 19, 2013 in 17 pages.Applicant
- TestFlight—Beta Testing on the Fly, http://testflightapp.com/ Printed Jul. 18, 2013 in 3 pages.Applicant
- trak.io, http://trak.io/ printed Jul. 18, 2013 in 3 pages.Applicant
- UserMetrix, http://usermetrix.com/android-analytics printed Jul. 18, 2013 in 3 pages.Applicant
- Valentini et al., “Ensembles of Learning Machines,” M. Marinaro and R. Tagliaferri (Eds.): Wirn Vietri 2002, LNCS 2486, pp. 3-20.Applicant
- Vose et al., “Help File for ModelRisk Version 5,” 2007, Vose Software, pp. 349-353.Applicant
- Wang et al., “Research on a Clustering Data De-Duplication Mechanism Based on Bloom Filter,” IEEE 2010, 5 pages.Applicant
- Wikipedia, “Multimap,” Jan. 1, 2013, https://en.wikipedia.org/w/index.php?title=Multimap&oldid=530800748.Applicant
- Notice of Allowance for U.S. Appl. No. 14/225,084 dated May 4, 2015.Applicant
- Notice of Allowance for U.S. Appl. No. 14/319,161 dated May 4, 2015.Applicant
- Notice of Allowance for U.S. Appl. No. 14/323,935 dated Oct. 1, 2015.Applicant
- Notice of Allowance for U.S. Appl. No. 14/451,221 dated Aug. 4, 2015.Applicant
- Notice of Allowance for U.S. Appl. No. 14/479,863 dated Mar. 31, 2015.Applicant
- Notice of Allowance for U.S. Appl. No. 14/552,336 dated Nov. 3, 2015.Applicant
- Notice of Allowance for U.S. Appl. No. 14/676,621 dated Feb. 10, 2016.Applicant
- Notice of Allowance for U.S. Appl. No. 14/746,671 dated Jan. 21, 2016.Applicant
- Official Communication for European Patent Application No. 14187996.5 dated Feb. 12, 2015.Applicant
- Official Communication for European Patent Application No. 14191540.5 dated May 27, 2015.Applicant
- Official Communication for European Patent Application No. 14200246.8 dated May 29, 2015.Applicant
- Official Communication for European Patent Application No. 14200298.9 dated May 13, 2015.Applicant
- Official Communication for European Patent Application No. 15181419.1 dated Sep. 29, 2015.Applicant
- Official Communication for European Patent Application No. 15184764.7 dated Dec. 14, 2015.Applicant
- Official Communication for Great Britain Patent Application No. 1404486.1 dated May 21, 2015.Applicant
- Official Communication for Great Britain Patent Application No. 1404486.1 dated Aug. 27, 2014.Applicant
- Official Communication for Great Britain Patent Application No. 1404489.5 dated May 21, 2015.Applicant
- Official Communication for Great Britain Patent Application No. 1404489.5 dated Aug. 27, 2014.Applicant
- Official Communication for Great Britain Patent Application No. 1404499.4 dated Jun. 11, 2015.Applicant
- Official Communication for Great Britain Patent Application No. 1404499.4 dated Aug. 20, 2014.Applicant
- Official Communication for Netherlands Patent Application No. 2012417 dated Sep. 18, 2015.Applicant
- Official Communication for Netherlands Patent Application No. 2012421 dated Sep. 18, 2015.Applicant
- Official Communication for Netherlands Patent Application No. 2012438 dated Sep. 21, 2015.Applicant
- Official Communication for New Zealand Patent Application No. 622473 dated Jun. 19, 2014.Applicant
- Official Communication for New Zealand Patent Application No. 622473 dated Mar. 27, 2014.Applicant
- Official Communication for New Zealand Patent Application No. 622513 dated Apr. 3, 2014.Applicant
- Official Communication for New Zealand Patent Application No. 628161 dated Aug. 25, 2014.Applicant
- Official Communication for U.S. Appl. No. 13/827,491 dated Dec. 1, 2014.Applicant
- Official Communication for U.S. Appl. No. 13/827,491 dated Jun. 22, 2015.Applicant
- Official Communication for U.S. Appl. No. 13/827,491 dated Oct. 9, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/141,252 dated Oct. 8, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,006 dated Sep. 10, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/225,006 dated Sep. 2, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,006 dated Dec. 21, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,006 dated Feb. 27, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,084 dated Sep. 11, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,084 dated Sep. 2, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/225,084 dated Feb. 20, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,084 dated Feb. 26, 2016.Applicant
- Official Communication for U.S. Appl. No. 14/225,084 dated Jan. 4, 2016.Applicant
- Official Communication for U.S. Appl. No. 14/225,160 dated Feb. 11, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,160 dated Aug. 12, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,160 dated May 20, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/225,160 dated Oct. 22, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/225,160 dated Jul. 29, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/306,138 dated Sep. 14, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,138 dated Feb. 18, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,138 dated Sep. 23, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/306,138 dated Dec. 24, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,138 dated May 26, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,138 dated Dec. 3, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,147 dated Feb. 19, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,147 dated Dec. 24, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,147 dated Aug. 7, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/306,147 dated Sep. 9, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/319,161 dated Jan. 23, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/323,935 dated Jun. 22, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/323,935 dated Nov. 28, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/323,935 dated Mar. 31, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/451,221 dated Oct. 21, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/451,221 dated Apr. 6, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/463,615 dated Sep. 10, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/463,615 dated Nov. 13, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/463,615 dated May 21, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/463,615 dated Jan. 28, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/463,615 dated Dec. 9, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/479,863 dated Dec. 26, 2014.Applicant
- Official Communication for U.S. Appl. No. 14/483,527 dated Jun. 22, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/483,527 dated Jan. 28, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/483,527 dated Oct. 28, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/552,336 dated Jul. 20, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/562,524 dated Nov. 10, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/562,524 dated Sep. 14, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/562,524 dated Feb. 18, 2016.Applicant
- Official Communication for U.S. Appl. No. 14/571,098 dated Nov. 10, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/571,098 dated Mar. 11, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/571,098 dated Feb. 23, 2016.Applicant
- Official Communication for U.S. Appl. No. 14/571,098 dated Aug. 24, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/571,098 dated Aug. 5, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/631,633 dated Sep. 10, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/631,633 dated Feb. 3, 2016.Applicant
- Official Communication for U.S. Appl. No. 14/676,621 dated Oct. 29, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/676,621 dated Jul. 30, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/746,671 dated Nov. 12, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/746,671 dated Sep. 28, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/800,447 dated Dec. 10, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/800,447 dated Mar. 3, 2016.Applicant
- Official Communication for U.S. Appl. No. 14/813,749 dated Sep. 28, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/842,734 dated Nov. 19, 2015.Applicant
- Official Communication for U.S. Appl. No. 14/923,374 dated Feb. 9, 2016.Applicant