User-centric traffic enquiry and alert system

• US 9,135,624 B2
• Filed: 09/23/2011
• Issued: 09/15/2015
• Est. Priority Date: 09/23/2010
• Status: Active Grant

• Current Assignee: Appy Risk Technologies Limited (Trak Global Group Ltd.)
• Original Assignee: Intelligent Mechatronic Systems Inc. (Trak Global Group Ltd.)
• Inventors: Basir, Otman Adam
• Primary Examiner(s): Mehmood, Jennifer
• Assistant Examiner(s): Casillashernandez, Omar
• Application Number:
  US13/244,204
• Publication Number:
  US 20120075118A1
• Time in Patent Office: 1,453 Days
• Field of Search: 340/905, 340/988, 701/32.5
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/06 Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G08G 1/096741 where the source of the transmitted information selects which information to transmit to each vehicle
• CPC Class Codes: G08G 1/096775 where the origin of the information is a central station

Abstract

A method for notifying a user about traffic including the step of determining an origin of the user. A destination of the user is also determined. Traffic conditions between the origin and the destination are determined. The user is notified of the traffic conditions.

Claims

1. A method for notifying a user about traffic including the steps of:

a) determining a current location of the user with a gps receiver;

b) determining a destination of the user by comparing with a processor the user'"'"'s current direction of travel from the user'"'"'s current location to addresses in a set of electronically-stored contacts associated with the user;

c) determining traffic conditions between the origin and the destination; and

d) notifying the user of the traffic conditions based upon said step c).

2. The method of claim 1 wherein said step b) is performed by monitoring a history of destinations by the user and predicting the destination based upon the history of destinations.

3. The method of claim 2 wherein the step of monitoring the history of destinations by user includes monitoring destinations on days of the week and times of day.

4. The method of claim 3 further including the step of comparing the traffic conditions to a threshold set by the user and wherein said step d) includes only notifying the user based upon the comparison with the threshold.

5. The method of claim 4 wherein the threshold is a length of delay of calculated travel time relative to expected travel time under normal conditions.

6. The method of claim 1 wherein said step b) is performed based upon a calendar event associated with the user.

7. The method of claim 1 wherein said step d) is performed at a set time interval prior to the user leaving the origin.

8. The method of claim 1 wherein said step d) is performed at a time that is dependent upon the traffic conditions determined in said step c).

9. The method of claim 1 wherein said step d) is performed at a time that is based upon a latest time of arrival received from the user.

10. The method of claim 1 wherein at least some of said steps a)-d) are performed on a mobile device.

11. The method of claim 1 wherein at least some of said steps a)-d) are performed on a server remote from the user.