Patent Grant
10614517
The invention relates generally to a system that transmits alerts to users in a computing network where the alerts may include icons and other information. The type of alert transmitted is related to an associated alert condition where the alert may be related to user experience. The alert including the icon is selected for specialized purposes to more efficiently transmit alerts to the user and to generate user responses.
The following presents a simplified summary of one or more embodiments of the invention in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments, nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.
In some embodiments an entity system comprises a network communication interface and a memory device storing an alert application. A processing device is operatively coupled to the memory device and is configured to execute computer-readable program code to: transmit alerts to a user device in response to alert conditions; monitor responses to the alert from the user device; and alter the visual appearance of the alerts at the user device based on the results of monitoring the responses.
The processing device may be configured to execute computer-readable program code to select from at least two different types of alerts. The two different types of alerts may comprise different icons having different visual appearances. The two different types of alerts may be associated with different alert conditions. The two different types of alerts may be based on the responsiveness of the user device. The two different types of alerts may be based on the urgency of the alert conditions. The entity system may be a financial entity system and the alert conditions relate to a user account information.
In some embodiments an entity system comprises a network communication interface and a memory device storing an alert application. A processing device is operatively coupled to the memory device and is configured to execute computer-readable program code to: transmit alerts to a plurality of user devices in response to alert conditions; monitor responses to the alert from the user devices; and alter the visual appearance of the alerts at the user devices based on the results of monitoring the responses.
The processing device may be configured to execute computer-readable program code to select from at least two different types of alerts based on the aggregate data from the plurality of user devices. The two different types of alerts may be matched to different alert conditions. The two different types of alerts may comprise different icons having different visual appearances. The two different types of alerts may be based on the aggregate responsiveness of the plurality of user devices. The two different types of alerts are based on the urgency of the alert conditions.
In some embodiments an entity system comprises a network communication interface and a memory device storing an alert application. A processing device is operatively coupled to the memory device, wherein the processing device is configured to execute computer-readable program code to: monitor a user account for a first alert condition and a second alert condition; determine to transmit a first alert for the first alert condition and a second alert to a second alert condition to a user device in response to monitoring the user account; and transmit a first type of alert for the first alert condition and a second type of alert for the second condition where the first alert and the second alert are different in visual appearance from one another.
The first alert and the second alert may be different in at least one of color and size. The first alert and the second alert may comprise different icons having different visual appearances. The network communication interface may transmit a message to the user device such that the first alert and the second alert are displayed on the user device without being displayed in-line with associated transaction information. The network communication interface may receive a message from the user device such that the network communication interface transmits a message to the user device disabling the first alert and the second alert such that the first alert and the second alert are not displayed. The first alert and the second alert may comprise different icons and alphanumeric characters having different visual appearances. The first alert and the second alert may be associated with two different alert conditions and the first alert and the second alert may be based on the responsiveness of the user device the urgency of the alert conditions.
The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, wherein:
Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to elements throughout. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein.
An “account” is the relationship that a user has with an entity, such as a financial institution. Examples of accounts include a deposit account, such as a transactional account (e.g., a banking account), a savings account, an investment account, a money market account, a time deposit, a demand deposit, a pre-paid account, a credit account, a non-monetary user profile that includes information associated with the user, or the like. The account is associated with and/or maintained by the entity. “Assets” include accounts of the user and/or other property owned by the user. The assets may be associated with accounts or may be property that is not associated with a specific account. Examples of assets associated with accounts may be accounts that have cash or cash equivalents, or accounts that are funded with or contain property, such as safety despots box account that jewelry, a trust account that is funded with property, or the like. Examples of assets that may not be associated with accounts may be antiques in a user's home, jewelry in a user's home, or the like. “Authentication information” is any information that can be used to identify of a user. For example, a system may prompt a user to enter authentication information such as a username, a password, a personal identification number (PIN), a passcode, biometric information (e.g., voice authentication, a fingerprint, and/or a retina scan), an answer to a security question, a unique intrinsic user activity, such as making a predefined motion with a user device. This authentication information may be used to authenticate the identity of the user (e.g., determine that the authentication information is associated with the account) and determine that the user has authority to access an account or system. An “entity” as used herein may be a financial institution. For the purposes of this invention, a “financial institution” may be defined as any organization, entity, or the like in the business of moving, investing, or lending money, dealing in financial instruments, or providing financial services. This may include commercial banks, thrifts, federal and state savings banks, savings and loan associations, credit unions, investment companies, insurance companies and the like. In some embodiments, the entity may allow a user to establish an account with the entity. A “financial event” or “life event” may be any immediate or future event that causes a change in a user's financial status. A financial event may be a charge, a transaction, and exchange, or the like that may cause the user to lose or gain money and/or assets. Examples of financial events or life events include a medical expense, buying a house, college tuition, rent, moving to a new city, receiving a raise or bonus in pay and the like. To “monitor” is to watch, observe, or check something for a special purpose over a period of time. The “monitoring” may occur periodically over the period of time, or the monitoring may occur continuously over the period of time. In some embodiments, a system may actively monitor a database, wherein the system reaches out to the database and watches, observes, or checks the database for changes, updates, and the like. In other embodiments, a system may passively monitor a database, wherein the database provides information to the system and the system then watches, observes, or checks the provided information. A “transaction” refers to any communication between a user and the financial institution or other entity monitoring the user's activities. A transaction may also refer to any communication between a user and a third party. For example, a transaction may refer to a purchase of goods or services, a return of goods or services, a payment transaction, a credit transaction, or other interaction involving a user's account. In the context of a financial institution or third party, a transaction may refer to one or more of: a sale of goods and/or services, initiating an automated teller machine (ATM) or online banking session, an account balance inquiry, a rewards transfer, an account money transfer or withdrawal, opening a bank application on a user's computer or mobile device, a user accessing their e-wallet, or any other interaction involving the user and/or the user's device that is detectable by the financial institution. A transaction may include one or more of the following: renting, selling, and/or leasing goods and/or services (e.g., groceries, stamps, tickets, DVDs, vending machine items, digital items and the like); making payments to creditors (e.g., paying monthly bills; paying federal, state, and/or local taxes; and the like); sending remittances; loading money onto stored value cards (SVCs) and/or prepaid cards; donating to charities; and/or the like. A “user” may be a financial institution customer (e.g., an account holder or a person who have an account (e.g., banking account, credit account, or the like)). In one aspect, a user may be any financial institution customer involved managing spending and accounts with the financial institution or any other affiliate entities associated with the financial institution. In some embodiments, the user may be an individual who may be interested in opening an account with the financial institution. In some embodiments, a “user” may be a financial institution employee (e.g., an underwriter, a project manager, an IT specialist, a manager, an administrator, an internal operations analyst, bank teller or the like) capable of operating the system described herein. For purposes of this invention, the term “user” and “customer” may be used interchangeably. A “user interface” is any device or software that allows a user to input information, such as commands or data, into a device, or that allows the device to output information to the user. For example, the user interface includes a graphical user interface (GUI) or an interface to input computer-executable instructions that direct a processing device to carry out specific functions. The user interface typically employs certain input and output devices to input data received from a user second user or output data to a user. These input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other user input/output device for communicating with one or more users.
Referring now to
The systems and devices communicate with one another over the network 130 and perform one or more of the various steps and/or methods according to embodiments of the disclosure discussed herein. The network 130 may include a local area network (LAN), a wide area network (WAN), and/or a global area network (GAN). The network 130 may provide for wireline, wireless, or a combination of wireline and wireless communication between devices in the network. In one embodiment, the network 130 includes the Internet.
The user device 111, the third party system 160, and the financial institution system 140 each includes a computer system, server, multiple computer systems and/or servers or the like. The financial institution system 140, in the embodiments shown has a communication device 142 communicably coupled with a processing device 144, which is also communicably coupled with a memory device 146. The processing device 144 is configured to control the communication device 142 such that the financial institution system 140 communicates across the network 130 with one or more other systems. The processing device 144 is also configured to access the memory device 146 in order to read the computer readable instructions 148, which in some embodiments includes one or more applications such as applications 150 and 151. At least one of the applications 150, 151 may be an alert application that includes the instructions for carrying out the invention as described herein. The memory device 146 also includes a datastore 154 or database for storing pieces of data that can be accessed by the processing device 144.
As used herein, a “processing device,” generally refers to a device or combination of devices having circuitry used for implementing the communication and/or logic functions of a particular system. For example, a processing device may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing devices according to their respective capabilities. The processing device 114, 144, or 164 may further include functionality to operate one or more software programs based on computer-executable program code thereof, which may be stored in a memory. As the phrase is used herein, a processing device 114, 144, or 164 may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function.
Furthermore, as used herein, a “memory device” generally refers to a device or combination of devices that store one or more forms of computer-readable media and/or computer-executable program code/instructions. Computer-readable media is defined in greater detail below. For example, in one embodiment, the memory device 146 includes any computer memory that provides an actual or virtual space to temporarily or permanently store data and/or commands provided to the processing device 144 when it carries out its functions described herein.
The user device 111 includes a communication device 112 communicably coupled with a processing device 114, which is also communicably coupled with a memory device 116. The processing device 114 is configured to control the communication device 112 such that the user device 111 communicates across the network 130 with one or more other systems. The processing device 114 is also configured to access the memory device 116 in order to read the computer readable instructions 118, which in some embodiments includes application 120 and online banking application 121. The memory device 116 also includes a datastore 122 or database for storing pieces of data that can be accessed by the processing device 114. The user device 111 may be a mobile device of the user 110, a bank teller device, a third party device, an automated teller machine, a video teller machine, or another device capable of capturing a check image.
The user device 111 further includes a user interface 131 that allows input from the user to the user device and output from the user device to be displayed to the user. As used herein, a “user interface” 130 generally includes a plurality of interface devices and/or software that allow a customer to input commands and data to direct the processing device to execute instructions. For example, the user interface 131 presented in
The third party system 160 includes a communication device 162 communicably coupled with a processing device 164, which is also communicably coupled with a memory device 166. The processing device 164 is configured to control the communication device 162 such that the third party system 160 communicates across the network 130 with one or more other systems. The processing device 164 is also configured to access the memory device 166 in order to read the computer readable instructions 168, which in some embodiments includes an application 170. The memory device 166 also includes a datastore 172 or database for storing pieces of data that can be accessed by the processing device 164.
In some embodiments, the application 120, the online banking application 121, and the application 170 interact with the application 150 or 151 to receive or provide financial data, analyze financial record data, and implement business strategies, transactions, and processes. The applications 150 and 151 may be a suite of applications for performing these functions.
In some embodiments, the application 120, the online banking application 121, and the application 170 interact with the applications 150 and 151 to utilize metadata to determine decisions for processing.
The applications 120, 121, 150, 151, and 170 are for instructing the processing devices 114, 144 and 164 to perform various steps of the methods discussed herein, and/or other steps and/or similar steps. In various embodiments, one or more of the applications 120, 121, 150, 151, and 170 are included in the computer readable instructions stored in a memory device of one or more systems or devices other than the systems 160 and 140 and the user device 111. For example, in some embodiments, the application 120 is stored and configured for being accessed by a processing device of one or more third party systems 192 connected to the network 130. In various embodiments, the applications 120, 121, 150, 151, and 170 stored and executed by different systems/devices are different. In some embodiments, the applications 120, 121, 150, 151, and 170 stored and executed by different systems may be similar and may be configured to communicate with one another, and in some embodiments, the applications 120, 121, 150, 151, and 170 may be considered to be working together as a singular application despite being stored and executed on different systems.
In various embodiments, one of the systems discussed above, such as the financial institution system 140, is more than one system and the various components of the system are not collocated, and in various embodiments, there are multiple components performing the functions indicated herein as a single device. For example, in one embodiment, multiple processing devices perform the functions of the processing device 144 of the financial institution system 140 described herein. In various embodiments, the financial institution system 140 includes one or more of the external systems 196 and/or any other system or component used in conjunction with or to perform any of the method steps discussed herein. For example, the financial institution system 140 may include a financial institution system, a credit agency system, and the like.
In various embodiments, the financial institution system 140, the third party system 160, and the user device 111 and/or other systems may perform all or part of a one or more method steps discussed above and/or other method steps in association with the method steps discussed above. Furthermore, some or all the systems/devices discussed here, in association with other systems or without association with other systems, in association with steps being performed manually or without steps being performed manually, may perform one or more of the steps of one or more of the method discussed herein, or other methods, processes or steps discussed herein or not discussed herein.
Referring now to
Referring now to
Referring now to
Referring now to
Alerts 204a, 204b, 204c are provided to bring the user's attention to special circumstances or situations related to the user's accounts, transactions or the like (referred to herein as “alert conditions”). The illustrated examples of alert conditions include double charges, duplicate subscriptions, and financial performance metrics. The alert conditions may include any activity or situation related to a user account or transaction including, but not limited to, direct deposit notifications, due dates of payments, balance information, credit card budget limits, security alerts and the like. The alerts are transmitted from the financial institution system 140 to the user device 111 such that the alerts may be displayed to the user by the user interface 131. In some embodiments the alerts are provided as a part of the transaction log as shown in
In some embodiments the in-line alerts may provide too much information to the user in one display such that the effectiveness of the alerts may be lost among the other information presented to the user such as the transaction information in a transaction log or the subscription information in a subscription log. In one embodiment the user device 111 may be provided with a user input 205 (
In some embodiments, the system may operate in an “alert mode” where only the alerts are displayed to the user on user device 111 such that the other transactions in the log are hidden. The menu may provide for the “alert mode” by a user input 211 (
In some embodiments, the alert messages may be modified in appearance such that different alert conditions are provided with alerts having different visual appearances. In this manner the user may quickly identify the type of alert by the visual appearance of the alert message without having to read or otherwise process the substance of the alert message. In some embodiments the alert message may comprise alphanumeric text where the different appearances of the different types of messages is accomplished by varying the appearance of the text. For example, as shown in
In one exemplary embodiment, the difference in appearance of the displayed alerts may be based on the importance and/or urgency of the alert condition where a more urgent alert condition may be provided in a larger font and in a first more prominent color and a second less urgent alert may be displayed in a smaller font and in a second less prominent color. For example, a more urgent alert may be used for the user being charged twice for the same purchase versus a less urgent alert being used if the user is spending too much in general. The appearance of the alert may be selected based on a user's reaction to the visual appearance of the alert. For example an alert for a high urgency alert condition may be displayed in red font and in all capital letters while an alert for a medium urgency level alert condition may be displayed in initial caps and in yellow font and an alert for a low urgency alert condition may be displayed in no caps and in a green font. In this manner the user may identify and sort through the alerts by quickly scanning the visual appearances of the alerts without having to read the substance of the alerts.
In some embodiments the alert may change automatically over time based on whether or not the user acts on the alert. For example, if the user hasn't acted on the alert for a predetermined period of time the visual appearance or presentation of the alert may change. For example, if the alert is not acted upon by the user after a predetermined period of time the alert message and/or icon may increase in size, change color, change font, move up or down on the alert list or otherwise change in appearance in order to encourage the user to act on the alert. For example, if an urgent alert is sent to the user and the user doesn't act on the alert after 24 hours, the size, color and location of the alert on the user display may change to encourage the user to notice and act on the alert. For example, the alert may increase in size, change from yellow to red and move to the top of the alert list. If the alert is not acted upon after another 24 hours the visual appearance of the alert may be altered again to change background colors, change icon, to flash or the like. For less urgent alert situations the time period may be longer than for more urgent alert situations and the changes to the visual appearance of the alerts may be less drastic. In such an embodiment the alert is transmitted to the user device from the financial institution system and the financial institution system monitors communications from the user to detect action on the alert by the user. If the user does not act on the alert within the predetermined period of time, the financial institution transmits a message to the user device to display a second modified alert having different visual appearance than the first alert. The system may monitor the communications from the user to detect action on the second alert by the user in a second period of time and may transmit a message to the user device to display a third modified alert having different visual appearance than the first and second alerts. The process may be repeated for multiple periods of times and the alerts may be varied from one visual appearance to a different visual appearance with each iteration of the process.
In some embodiments, the visual appearance of the alerts may be designated by the financial institution system 140 such that all users receive an alert having the same visual appearance for the same type of alert condition. In other embodiments, the user may have input into the visual appearance of the alert. For example, referring to
In addition to alphanumeric text the alerts may be provided with icons or symbols 221 that identify the message as an alert such that the user may quickly and easily identify alerts. The appearance of the icon associated with the alert condition may be selected based on the type of alert condition. As shown in
The use of alphanumeric text and icons, images or other visual indicators may be combined in a single alert. Moreover, the styles, types, colors, and shapes of the alerts may vary from those specifically described herein.
The visual appearance of the alert may also be selected by the financial institution system 140 based on the response of the user. For example in one embodiment, as illustrated in
In some embodiments, the visual appearance of the alert may also be determined by the financial institution system 140 based on the aggregated responses of selected users of the institution. The users selected for the sample may be all of the users or a subset of the users. The subset of users may be based on characteristics of the users such that the responses of similarly situated users may be aggregated for purposes of determining the type of alert to be used with a particular alert condition. The system operates in a manner similar to that describe with respect to
In some embodiments of the invention one or more of the systems described herein may be combined with each other, or otherwise perform the functions of the other systems described herein. In other embodiments of the invention one or more of the applications described herein may be combined with each other, or otherwise perform the functions of the other applications described herein. Furthermore, the applications may be any type of application, such as an application stored on a desktop, server, or other device, a mobile application stored on a mobile device, a cloud application, or other like application. As such, the applications described herein, or portions of the applications described herein may be stored and operated on any of the systems or devices described herein. For example, a portion of one or more applications may be stored on the user device, or may be included as a portion of financial institution applications, such as an online banking application, in order to achieve embodiments of the inventions described herein.
It should be understood, that the systems and devices described in
Moreover, it should be understood that the process flows described herein include transforming the information sent and/or received from the applications of the different systems (e.g., internally or externally) and/or the devices from one or more data formats into a data format associated with an application for display to the user on the user device. There are many ways in which information is converted within the system environment. This may be seamless, as in the case of upgrading to a newer version of a computer program. Alternatively, the conversion may require processing by the use of a special conversion program, or it may involve a complex process of going through intermediary stages, or involving complex “exporting” and “importing” procedures, which may converting to and from a tab-delimited or comma-separated text file. In some cases, a program may recognize several data file formats at the data input stage and then is also capable of storing the output data in a number of different formats. Such a program may be used to convert a file format. If the source format or target format is not recognized, then at times a third program may be available which permits the conversion to an intermediate format, which can then be reformatted.
As will be appreciated by one of skill in the art, the present invention may be embodied as a method (including, for example, a computer-implemented process, a business process, and/or any other process), apparatus (including, for example, a system, machine, device, computer program product, and/or the like), or a combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product on a computer-readable medium having computer-executable program code embodied in the medium.
Any suitable transitory or non-transitory computer readable medium may be utilized. The computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples of the computer readable medium include, but are not limited to, the following: an electrical connection having one or more wires; a tangible storage medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other optical or magnetic storage device.
In the context of this document, a computer readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, radio frequency (RF) signals, or other mediums.
Computer-executable program code for carrying out operations of embodiments of the present invention may be written in an object oriented, scripted or unscripted programming language such as Java, Perl, Smalltalk, C++, or the like. However, the computer program code for carrying out operations of embodiments of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages.
Embodiments of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and/or combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable program code portions. These computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the code portions, which execute via the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer-executable program code portions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the code portions stored in the computer readable memory produce an article of manufacture including instruction mechanisms which implement the function/act specified in the flowchart and/or block diagram block(s).
The computer-executable program code may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the code portions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block(s). Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the invention.
As the phrase is used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function.
Embodiments of the present invention are described above with reference to flowcharts and/or block diagrams. It will be understood that steps of the processes described herein may be performed in orders different than those illustrated in the flowcharts. In other words, the processes represented by the blocks of a flowchart may, in some embodiments, be in performed in an order other that the order illustrated, may be combined or divided, or may be performed simultaneously. It will also be understood that the blocks of the block diagrams illustrated, in some embodiments, merely conceptual delineations between systems and one or more of the systems illustrated by a block in the block diagrams may be combined or share hardware and/or software with another one or more of the systems illustrated by a block in the block diagrams. Likewise, a device, system, apparatus, and/or the like may be made up of one or more devices, systems, apparatuses, and/or the like. For example, where a processor is illustrated or described herein, the processor may be made up of a plurality of microprocessors or other processing devices which may or may not be coupled to one another. Likewise, where a memory is illustrated or described herein, the memory may be made up of a plurality of memory devices which may or may not be coupled to one another.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications:
| Number | Name | Date | Kind |
|---|---|---|---|
| 5864684 | Nielson | Jan 1999 | A |
| 5918217 | Maggioncalda et al. | Jun 1999 | A |
| 6012044 | Maggioncalda et al. | Jan 2000 | A |
| 6278993 | Kumar et al. | Aug 2001 | B1 |
| 6327578 | Linehan | Dec 2001 | B1 |
| 6629081 | Cornelius et al. | Sep 2003 | B1 |
| 6633910 | Rajan et al. | Oct 2003 | B1 |
| 6782374 | Nichols | Aug 2004 | B2 |
| 6829334 | Zirngibl et al. | Dec 2004 | B1 |
| 6892192 | Geddes et al. | May 2005 | B1 |
| 7085834 | Delany et al. | Aug 2006 | B2 |
| 7092992 | Yu | Aug 2006 | B1 |
| 7103556 | Del Rey et al. | Sep 2006 | B2 |
| 7165041 | Guheen et al. | Jan 2007 | B1 |
| 7296734 | Pliha | Nov 2007 | B2 |
| 7363339 | Delany et al. | Apr 2008 | B2 |
| 7364071 | Esplin et al. | Apr 2008 | B2 |
| 7406537 | Cullen | Jul 2008 | B2 |
| 7412534 | Tsang et al. | Aug 2008 | B2 |
| 7444304 | Mellinger et al. | Oct 2008 | B2 |
| 7486780 | Zirngibl et al. | Feb 2009 | B2 |
| 7624073 | Robinson et al. | Nov 2009 | B1 |
| 7672879 | Kumar et al. | Mar 2010 | B1 |
| 7698190 | Penkalski et al. | Apr 2010 | B2 |
| 7774257 | Maggioncalda et al. | Aug 2010 | B2 |
| 7788147 | Haggerty et al. | Aug 2010 | B2 |
| 7797267 | Horvitz | Sep 2010 | B2 |
| 7813989 | Jones et al. | Oct 2010 | B2 |
| 7860774 | Peterson et al. | Dec 2010 | B1 |
| 7912770 | Haggerty et al. | Mar 2011 | B2 |
| 8060423 | Rukonic et al. | Nov 2011 | B1 |
| 8073759 | Del Favero et al. | Dec 2011 | B1 |
| 8122123 | Bhattacharya et al. | Feb 2012 | B2 |
| 8135655 | Oaten et al. | Mar 2012 | B2 |
| 8260699 | Smith et al. | Sep 2012 | B2 |
| 8306894 | Newman et al. | Nov 2012 | B2 |
| 8346568 | Del Favero et al. | Jan 2013 | B1 |
| 8396791 | Cotton | Mar 2013 | B2 |
| 8407137 | Thomas | Mar 2013 | B2 |
| 8429038 | Harman et al. | Apr 2013 | B1 |
| 8458051 | Saltzman et al. | Jun 2013 | B1 |
| 8473380 | Thomas et al. | Jun 2013 | B2 |
| 8494936 | Brenner | Jul 2013 | B2 |
| 8515828 | Wolf et al. | Aug 2013 | B1 |
| 8594283 | Hogan et al. | Nov 2013 | B2 |
| 8639567 | Winters | Jan 2014 | B2 |
| 8639638 | Shae et al. | Jan 2014 | B2 |
| 8682793 | Carlson et al. | Mar 2014 | B2 |
| 8713090 | Sadovsky et al. | Apr 2014 | B2 |
| 8719132 | Diggdon et al. | May 2014 | B1 |
| 8732073 | Thomas | May 2014 | B2 |
| 8768736 | Chapman et al. | Jul 2014 | B1 |
| 8768800 | Milosavljevic et al. | Jul 2014 | B2 |
| 8768833 | Freishtat et al. | Jul 2014 | B2 |
| 8788661 | Raleigh | Jul 2014 | B2 |
| 8825759 | Jackson et al. | Sep 2014 | B1 |
| 8930217 | Feinschreiber et al. | Jan 2015 | B2 |
| 8935342 | Patel | Jan 2015 | B2 |
| 9098387 | Curtis et al. | Aug 2015 | B1 |
| 9256876 | Vasant Akole et al. | Feb 2016 | B2 |
| 9286637 | Keld et al. | Mar 2016 | B1 |
| 9411942 | Commons et al. | Aug 2016 | B2 |
| 9460443 | Curtis et al. | Oct 2016 | B1 |
| 20020174185 | Rawat et al. | Nov 2002 | A1 |
| 20020180786 | Tanner | Dec 2002 | A1 |
| 20030120593 | Bansal et al. | Jun 2003 | A1 |
| 20030139986 | Roberts, Jr. | Jul 2003 | A1 |
| 20030206554 | Dillon | Nov 2003 | A1 |
| 20040107125 | Guheen et al. | Jun 2004 | A1 |
| 20040138959 | Hlavac et al. | Jul 2004 | A1 |
| 20040153413 | Gross | Aug 2004 | A1 |
| 20040162773 | Del Rey et al. | Aug 2004 | A1 |
| 20040175680 | Hlavac et al. | Sep 2004 | A1 |
| 20040181591 | Yu et al. | Sep 2004 | A1 |
| 20040189702 | Hlavac et al. | Sep 2004 | A1 |
| 20050187862 | Dheer et al. | Aug 2005 | A1 |
| 20060014535 | Walker et al. | Jan 2006 | A1 |
| 20060224046 | Ramadas et al. | Oct 2006 | A1 |
| 20060265201 | Martin | Nov 2006 | A1 |
| 20060288023 | Szabo | Dec 2006 | A1 |
| 20070021200 | Fox et al. | Jan 2007 | A1 |
| 20070112906 | Liu et al. | May 2007 | A1 |
| 20070167689 | Ramadas et al. | Jul 2007 | A1 |
| 20070174448 | Ahuja et al. | Jul 2007 | A1 |
| 20070286099 | Stocklein et al. | Dec 2007 | A1 |
| 20080014908 | Vasant | Jan 2008 | A1 |
| 20080034045 | Bardsley | Feb 2008 | A1 |
| 20080086409 | Moorman et al. | Apr 2008 | A1 |
| 20080114677 | Keohane | May 2008 | A1 |
| 20080133734 | Jacobs et al. | Jun 2008 | A1 |
| 20090024984 | Maeda | Jan 2009 | A1 |
| 20090106171 | Hlavac et al. | Apr 2009 | A1 |
| 20090124349 | Dawson et al. | May 2009 | A1 |
| 20090132395 | Lam et al. | May 2009 | A1 |
| 20090276288 | Hlavac et al. | Nov 2009 | A1 |
| 20100017619 | Errico | Jan 2010 | A1 |
| 20100100470 | Buchanan et al. | Apr 2010 | A1 |
| 20100121808 | Kuhn | May 2010 | A1 |
| 20100257066 | Jones et al. | Oct 2010 | A1 |
| 20100299252 | Thomas | Nov 2010 | A1 |
| 20100306080 | Trandal et al. | Dec 2010 | A1 |
| 20100325047 | Carlson | Dec 2010 | A1 |
| 20100332373 | Crabtree et al. | Dec 2010 | A1 |
| 20100332583 | Szabo | Dec 2010 | A1 |
| 20110066505 | Hammad | Mar 2011 | A1 |
| 20110106775 | Arbo et al. | May 2011 | A1 |
| 20110131130 | Griffin et al. | Jun 2011 | A1 |
| 20110145056 | Sullivan et al. | Jun 2011 | A1 |
| 20110213686 | Ferris et al. | Sep 2011 | A1 |
| 20110275344 | Momtahan et al. | Nov 2011 | A1 |
| 20120010933 | Satyavolu et al. | Jan 2012 | A1 |
| 20120016858 | Rathod | Jan 2012 | A1 |
| 20120122570 | Baronoff | May 2012 | A1 |
| 20120155296 | Kashanian | Jun 2012 | A1 |
| 20120173700 | De Andrade Cajahyba et al. | Jul 2012 | A1 |
| 20120179564 | Soroca et al. | Jul 2012 | A1 |
| 20120185368 | Schloter et al. | Jul 2012 | A1 |
| 20120197794 | Grigg et al. | Aug 2012 | A1 |
| 20120215640 | Ramer et al. | Aug 2012 | A1 |
| 20120221446 | Grigg et al. | Aug 2012 | A1 |
| 20120330971 | Thomas et al. | Dec 2012 | A1 |
| 20130006883 | McKeown et al. | Jan 2013 | A1 |
| 20130024203 | Flores et al. | Jan 2013 | A1 |
| 20130041819 | Khasho | Feb 2013 | A1 |
| 20130054681 | Coyne | Feb 2013 | A1 |
| 20130080641 | Lui et al. | Mar 2013 | A1 |
| 20130110640 | Powell et al. | May 2013 | A1 |
| 20130176908 | Baniel et al. | Jul 2013 | A1 |
| 20130227027 | May et al. | Aug 2013 | A1 |
| 20130262312 | Carlson | Oct 2013 | A1 |
| 20130325598 | Shao et al. | Dec 2013 | A1 |
| 20130325681 | Somashekar et al. | Dec 2013 | A1 |
| 20140025491 | Nagarajan et al. | Jan 2014 | A1 |
| 20140136381 | Joseph et al. | May 2014 | A1 |
| 20140172560 | Satyavolu et al. | Jun 2014 | A1 |
| 20140207584 | Wicha et al. | Jul 2014 | A1 |
| 20140236846 | Melika et al. | Aug 2014 | A1 |
| 20140278755 | Eberl et al. | Sep 2014 | A1 |
| 20140279639 | Cooper et al. | Sep 2014 | A1 |
| 20140279800 | Anastasopoulos | Sep 2014 | A1 |
| 20140289154 | Cooper et al. | Sep 2014 | A1 |
| 20140289386 | Vatto et al. | Sep 2014 | A1 |
| 20140335819 | Jahr | Nov 2014 | A1 |
| 20140365354 | Shvarts | Dec 2014 | A1 |
| 20150026053 | Calman | Jan 2015 | A1 |
| 20150046307 | Calman et al. | Feb 2015 | A1 |
| 20150079929 | McNamee et al. | Mar 2015 | A1 |
| 20150082458 | Cooper et al. | Mar 2015 | A1 |
| 20150095132 | Van Heerden et al. | Apr 2015 | A1 |
| 20150161671 | Watkeys | Jun 2015 | A1 |
| 20150351075 | Korver et al. | Dec 2015 | A1 |
| 20150379582 | Jain et al. | Dec 2015 | A1 |
| 20160034588 | Hyatt et al. | Feb 2016 | A1 |
| 20160034834 | Snell et al. | Feb 2016 | A1 |
| 20160048698 | Sahu et al. | Feb 2016 | A1 |
| 20160198322 | Pitis | Jul 2016 | A1 |
| 20160267597 | Johansen et al. | Sep 2016 | A1 |
| 20160274744 | Neumann et al. | Sep 2016 | A1 |
| 20160275436 | Kurjanowicz et al. | Sep 2016 | A1 |
| 20160353237 | Shepherd et al. | Dec 2016 | A1 |
| 20160353386 | Sasidharan et al. | Dec 2016 | A1 |
| 20160379107 | Li et al. | Dec 2016 | A1 |
| 20170011398 | Narasimhan | Jan 2017 | A1 |
| 20170013440 | Ostling | Jan 2017 | A1 |
| 20170078861 | McNamee et al. | Mar 2017 | A1 |
| 20170236131 | Nathenson et al. | Aug 2017 | A1 |
| 20180018158 | Kalke et al. | Jan 2018 | A1 |
| 20180063018 | Bosch et al. | Mar 2018 | A1 |
| 20180225754 | Del Vecchio | Aug 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2626172 | Nov 2009 | CA |
| 2629653 | Nov 2009 | CA |
| 2634626 | Jan 2010 | CA |
| 103677488 | Mar 2014 | CN |
| 2004023451 | Mar 2004 | WO |
| 2006107799 | Oct 2006 | WO |
| 2007014201 | Feb 2007 | WO |
| 2008072255 | Jun 2008 | WO |
| 2008076997 | Jun 2008 | WO |
| 2011068791 | Jun 2011 | WO |
| 2014153128 | Sep 2014 | WO |
| 2014157891 | Oct 2014 | WO |
| 2014200692 | Dec 2014 | WO |
| 2010450059 | Aug 2017 | WO |
| Entry |
|---|
| Egele, Manuel, et al., “COMPA: Detecting Compromised Accounts on Social Networks”, NDSS 2013, San Diego, CA, Feb. 24-27, 3013, 17 pages. |
| Merriam Webster's Collegiate Dictionary, 10th Edition, Merriam-Webster, Incorporated, Springfield, MA, © 2000, p. 47. |
| Number | Date | Country | |
|---|---|---|---|
| 20180101901 A1 | Apr 2018 | US |
