NOTIFICATION SERVICES WITH ANOMALY DETECTION

• US 20130291099A1
• Filed: 04/25/2012
• Published: 10/31/2013
• Est. Priority Date: 04/25/2012
• Status: Abandoned Application

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: DONFRIED, Paul A., TIPPETT, Peter S., RAMACHANDRAN, Vidhyaprakash, KERN, Scott N.
• Application Number:
  US13/455,680
• Publication Number:
  US 20130291099A1
• Time in Patent Office: Days
• US Class Current: 726/22
• CPC Class Codes: G06Q 30/0637 Approvals

Abstract

A system is configure to monitor financial and/or identification inquiries for anomalous behavior; identify anomalous behavior by comparing the financial and/or identification inquiries to historical financial transactions and/or identification information; send a notification to a mobile device when anomalous behavior is identified for a user of the mobile device; and receive a signal from the mobile device approving, denying, or requesting more information about the anomalous behavior.

Claims

1. A method comprising:

identifying, by one or more server devices, a notification threshold level;

identifying, by the one or more server devices, an anomalous transaction involving an enterprise;

comparing, by the one or more server devices, the anomalous transaction with the identified notification threshold level;

sending, by the one or more server devices via a network, a notification when the anomalous transaction exceeds the identified notification threshold level;

receiving, by the one or more server devices, a selection to approve, deny, or request more information about the anomalous transaction; and

sending, by the one or more server devices to the enterprise via the network, the selection to approve, deny, or request more information about the anomalous transaction.

2. The method of claim 1, where identifying the notification threshold level comprises:

receiving input from a user identifying the notification threshold level;

or

predetermining a first notification threshold level, and allowing a user to change the first notification threshold level to set a second notification threshold level as the notification threshold level.

3. The method of claim 1, where identifying the anomalous transaction comprises:

building an identity profile for a user by gathering user identity information data and/or user tracking information data;

gathering transaction data;

comparing the identity profile with the transaction data; and

determining that the transaction is an anomalous transaction when the transaction data deviates by a predetermined amount from data from the identity profile.

4. The method of claim 1, where identifying the anomalous transaction comprises:

gathering transaction data;

gathering historical malicious behavior data;

comparing the transaction data with the historical malicious behavior data; and

determining that the transaction is an anomalous transaction when the transaction data deviates by a predetermined amount from the historical malicious behavior data.

5. The method of claim 1, where identifying the anomalous transaction comprises:

building a pattern based upon a plurality of transaction data and/or identity data from a user;

receiving transaction information on a transaction;

comparing the transaction information to the pattern; and

determining that the transaction is an anomalous transaction when the transaction information deviates by a predetermined amount from the pattern.

6. The method of claim 1, where identifying the anomalous transaction comprises:

building a pattern based upon a plurality of transaction data from multiple users;

receiving transaction information on a transaction;

comparing the transaction information to the pattern; and

determining that the transaction is an anomalous transaction when the transaction information deviates by a predetermined amount from the pattern.

7. The method of claim 1, further comprising:

converting the identified notification threshold level to a value on a notification threshold level scale;

receiving anomalous transaction data; and

converting the anomalous transaction data to a value on the notification threshold level scale, where comparing the anomalous transaction with the identified notification threshold level comprises;

comparing the anomalous transaction data value to the identified notification threshold level value.

8. The method of claim 1, further comprising:

preparing, when the notification exceeds the identified notification threshold level, an alert associated with the notification; and

presenting a visual alert via a display associated with a mobile device, or presenting an audible alert via a speaker associated with the mobile device.

9. The method of claim 1, where identifying the anomalous transaction comprises:

receiving transaction information;

receiving comparative information from the one or more server devices;

comparing the transaction information with the comparative information; and

identifying anomalies based upon inconsistencies between the transaction information and the comparative information from the one or more server devices.

10. The method of claim 9, where receiving the comparative information from the one or more server devices comprises receiving login information, billing information, address information, previous purchase history, a listing of transactions, information identifying a location of a mobile device, and/or information identifying previous locations of the mobile device.

11. The method of claim 9, where receiving the comparative information from the one or more server devices comprises receiving comparative information from the tracking server, where the comparative information includes information identifying a location of the device, a list of previous locations of the device, and/or information identifying movements of the device.

12. The method of claim 9, where receiving the comparative information the one or more server devices comprises receiving information on enterprises, devices, and/or systems associated with malicious activity.

13. The method of claim 1, further comprising:

preparing a first map icon based upon a location of the anomalous transaction;

preparing a second map icon based upon a location of a device; and

providing a user interface that includes a map illustrating the first map icon on the map, and the second map icon on the map.

14. The method of claim 13, further comprising:

providing anomalous transaction information with the first map icon, the anomalous transaction information including a name and a location of an enterprise providing the anomalous transaction,

where receiving the selection to approve, deny, or request more information about the anomalous transaction is received through interaction with the user interface that includes the map.

15. A device, comprising:

at least one processor to;

present a first user interface displaying a plurality of threshold levels for selection;

receive a selection of a threshold level from the plurality of threshold levels;

receive, via a network, a notification of anomalous behavior when an anomalous behavior risk level, that is based upon information about a transaction, exceeds the selected threshold level;

present a second user interface displaying the notification of anomalous behavior;

receive, via the second user interface, options to approve, deny, or request more information about the transaction; and

send, via the network, a selection of one of the options to approve, deny, or request more information about the transaction.

16. The device of claim 15, where the least one processor is to further:

generate an alert based on the notification of anomalous behavior; and

provide the alert on the device.

17. The device of claim 16, where, when providing the alert, the at least one processor is to:

present a visual notification via a display associated with the device, or present an audible notification via a speaker associated with the device.

18. A system, comprising:

one or more server devices with one or more processors to;

monitor financial and/or identification inquiries for anomalous behavior;

identify anomalous behavior by comparing the financial and/or identification inquiries to historical financial transactions and/or identification information;

send a notification to a mobile device when anomalous behavior is identified for a user of the mobile device; and

receive a signal from the mobile device approving, denying, or requesting more information about the anomalous behavior.

19. The system of claim 18, where the one or more server devices are to identify anomalous behavior by comparing the financial and/or identification transactions to identification information, which includes login information, billing information, address information, previous purchase history, a listing of transactions, information identifying a location of the mobile device, and/or information identifying previous locations of the mobile device.

20. A method comprising:

selecting, by a mobile device, a plurality of notification threshold levels;

sending, by the mobile device via a network, the plurality of notification threshold levels;

receiving, by the mobile device via the network, a notification when an anomalous transaction exceeds at least one of the plurality of notification threshold levels;

providing, by the mobile device, a first audible and/or visual alert when the anomalous transaction exceeds a first of the plurality of notification threshold levels; and

providing, by the mobile device, a second audible and/or visual alert when the anomalous transaction exceeds a second of the plurality of notification threshold levels.

21. The method of claim 20, where the selecting the plurality of notification threshold levels includes selecting the first and the second notification threshold levels and selecting a type of audible and/or visual alert associated with each of the first and the second notification threshold levels, respectively,

where providing the first audible and/or visual alert comprises providing an audible alert via a speaker associated with the mobile device and/or a visual alert via a display associated with the mobile device when the anomalous transaction exceeds the first of the plurality of notification threshold levels, and

where providing the second audible and/or visual alert comprises providing an audible alert via the speaker associated with the mobile device and/or a visual alert via the display associated with the mobile device when the anomalous transaction exceeds the second of the plurality of notification threshold levels.