|Publication number||US7065445 B2|
|Application number||US 10/395,841|
|Publication date||Jun 20, 2006|
|Filing date||Mar 24, 2003|
|Priority date||Nov 27, 2002|
|Also published as||US20040102895, WO2004086076A2, WO2004086076A3|
|Publication number||10395841, 395841, US 7065445 B2, US 7065445B2, US-B2-7065445, US7065445 B2, US7065445B2|
|Inventors||Peter A. Thayer, Victor Shao, Subramanian Mahesh|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (24), Referenced by (16), Classifications (15), Legal Events (12)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation-in-part of U.S. patent application Ser. No. 10/306,679 entitled “METHOD AND APPARATUS FOR PROVIDING INFORMATION PERTAINING TO VEHICLES LOCATED ALONG A PREDETERMINED TRAVEL ROUTE,” filed Nov. 27, 2002, and incorporated herein by reference in its entirety.
The invention relates to vehicle fleet management, and more particularly, to a passive system for manipulating travel route condition information.
In accordance with the invention, a passive alert system for a vehicle adapted to travel along a predetermined travel route is provided, and includes a vehicle processing system disposed onboard the vehicle and a server which is remote from the vehicle. The server acquires condition information relating to one or more prospective points along the travel route, generates one or more alerts based on the acquired condition information, and transmits the one or more alerts wirelessly to the vehicle processing system.
Further in accordance with the invention, a server for providing alerts to remote processing systems onboard a vehicle which is adapted to travel along a predetermined travel route is provided. The server includes a vehicle location monitoring system for providing vehicle location information, and a condition information broker adapted to communicate with a service provider and acquire therefrom condition information along one or more prospective points along the travel route, the prospective points being based a closest known position of the vehicle as indicated by the vehicle location information. The server also includes an alert generator for generating one or more alerts based on the condition information acquired from the service provider, and a communication manager for establishing a communication link with the remote processing system through which the one or more alerts are sent.
Further in accordance with the invention, a method for communicating passive alerts from a server to a vehicle having a vehicle processing system and traveling along a predetermined travel route is disclosed. The method includes determining a closest known position of the vehicle, acquiring condition information relating to one or more prospective points along the travel route, generating one or more alerts based on the acquired condition information, and transmitting the one or more alerts wirelessly to the vehicle processing system.
Further in accordance with the invention, a computer-readable media containing one or more programs which execute the following procedure for communicating passive alerts from a server to a vehicle having a vehicle processing system and traveling along a predetermined travel route is provided, and includes determining a closest known position of the vehicle, acquiring condition information relating to one or more prospective points along the travel route, generating one or more alerts based on the acquired condition information, and transmitting the one or more alerts wirelessly to the vehicle processing system.
Many advantages of the present invention will be apparent to those skilled in the art with a reading of this specification in conjunction with the attached drawings, wherein like reference numerals are applied to like elements.
Each truck 100 is provided with a vehicle processing system 110 which determines and monitors truck status information, including for example location, and relays this information to server 120 as appropriate. Location information is determined via GPS (Global Positioning System), preferably in accordance with the GeoWave™ algorithms disclosed in copending U.S. patent application No. 10/306,679 entitled “METHOD AND APPARATUS FOR PROVIDING INFORMATION PERTAINING TO VEHICLES LOCATED ALONG A PREDETERMINED TRAVEL ROUTE,” filed Nov. 27, 2002, and incorporated herein by reference in its entirety.
In the aformentioned copending application, a server such as server 120 determines an optimal travel route for a vehicle such as a truck 100 based on the start and end points. The travel route is divided into one or more segments, each of which is associated with a corridor having prescribed dimensions and encompassing the associated segment. During the time that the vehicle is traveling along the travel route, expectancy zones having prescribed dimensions are representationally propagated through the corridors, at prescribed speeds corresponding to the speed of the vehicle in that corridor. The expectancy zones correspond to a region in which the vehicle is expected to be at a particular moment in time. Deviation from the expectancy zones, as determined by GPS readings, triggers alerts which can be used to invoke remedial action, such as communications to the driver, notification of local authorities, or remote vehicle disablement.
Other devices with which server 220 communicates, either wirelessly or through a network such as the Internet, WAN (Wide Area Network), LAN (Local Area Network), and so forth, include a fleet server 250, and a weather service provider such as WeatherBank™ (260), the function of which is described in greater detail below. Multiple fleet servers 250 (only one is shown) are contemplated, each associated with a fleet of vehicles, operating to provide services relating to said fleet in accordance with the aforementioned copending application. Thus it can be seen that server 220 may be used in conjunction with multiple fleets of vehicles, each containing one or more vehicles. It will also be appreciated that one or more fleet servers 250 may be physically integral with server 220—that is, they may simply be separate processes running on server 220.
Server 220 includes a condition information broker, in the form of weather broker 222, along with an alert generator 224, a connection manager 226, and a vehicle location monitoring system such as GeoWave™ generator 228. As discussed above, the GeoWave™ generator 228 may be part of a separate device, such as a server 120, or it may be integral with server 220. GeoWave™ generator 228 provides position information, in the form of GPS latitude and longitude coordinates, to weather broker 222. The position information of GeoWave™ generator 228 corresponds to the travel route information as described in the aforementioned application, and includes, for travel routes determined to be active: the latitude and longitude coordinates of the start and end points of the travel route; start and end points of the one or more corridors associated with the travel route; and other points, such as waypoints, along the travel route. A travel route is determined to be active if it relates to a vehicle in the system which is currently traveling along the travel route.
The weather broker 222 performs several functions. Among these is compiling a list of geographical points whose weather conditions and forecasts are to be determined; coordinating the communication with the weather information provider, such as WeatherBank™, to obtain the weather conditions and forecasts and further populate the compiled list with this information; examining the list for alertable items; and sending out alerts to the appropriate vehicle processing systems 210.
The process of compiling the list of geographical points whose weather conditions and forecasts are to be determined, as performed by weather broker 222, is implemented with reference to information from GeoWave™ generator 228, which generates a data matrix containing geographical points based on the determined travel route in the manner disclosed in the aforementioned copending application. Weather broker 222 uses points from each data matrix associated with a travel route it determines to be active. It searches the data matrix and selects the point—Last Point Reached—closest to the current position of the vehicle. This information is known for example from the GeoWave™ procedures performed in accordance with the aforementioned application.
An example of how the Last Point Reached can be determined is to search a Route Vector Table and find the last point having a Point Reached flag set to “yes.” Once determined, an ETA (Estimated Arrival Time) associated with the Last Point Reached is compared to system time, and an offset is calculated from the difference. Then, based on the ETA of the Last Point Reached and corresponding offset, a set of one or more short-term prospective points is formulated, the set preferably consisting of four such points. The set of short-term prospective points represents points along the travel route at which the vehicle is expected to be during a particular time window in the future. For example, during the four hour time window following the time the Last Point Reached was reached, taking the offset into account, a set of 1 to 4 geographical points through which the vehicle is expected to pass is formulated, making reference to the data matrix as necessary.
In addition to the set of short-term prospective points, a set of long-term prospective points is also formulated, the latter set preferably consisting of two points along the travel route whose ETAs are, respectively, one and two days into the future. More days into the future are also possible. The short- and long-term prospective points provide the basis for obtaining weather and forecast information by weather broker 222. Using these prospective points, weather broker 222, which is contact with a weather information provider, such as WeatherBank™, via an HTTP/XML interface, makes an HTTP call to WeatherBank™. The prospective points are identified by their latitude and longitude coordinates, and this information is included in the call to WeatherBank™ (whose URL is WeatherBank.com). An example of a call for a particular prospective point is as follows:
WeatherBank™ responds to such a call with an XML response, which is reproduced as Appendix A. The XML response from WeatherBank™, includes current conditions for the particular point, as well as the five-day forecast (period-1, period-2, period-3, period-4, and period-5), for that point. Not all of the information provided in the response needs to be used, and the particular selection of the information used will depend on the specific application. Exemplarily, only the <weather wxcode> content for the <current>, <period-1> and <period-2> are used. In other words, for the prospective point selected, only the current weather conditions of that point, and the forecast conditions one day and two days forward at that point, are selected. Table A is a list of all the possible wxcode information which can be provided in the XML response from WeatherBank™.
Thunder Snow Shower
Rain and Snow
Thin Obscured, #1
Thin Obscured, #2
Partly Cloudy, #1
Partly Cloudy, #2
Mostly Clear, #1
High Thin Overcast
High Thin Clouds
Few High Clouds
Mostly Clear, #2
Funnel Cloud, Tornado
Weather broker 222 examines the <weather wxcode> information for the three time periods—that is, the <current>, <period-1> and <period-2>—for each prospective point. Based on the examination, conditions requiring further action are determined. Table B provides a list of the <current> conditions which are deemed to require further attention, while Table C provides a list of <period-1> and <period-2> conditions deemed to require further attention.
Thunder Snow Shower
Rain and Snow
Funnel Cloud, Tornado
Cloudy, Scattered Snow Showers
Overcast, Scattered Snow Showers
Partly Cloudy, Snow Showers
Partly Cloudy; Snow Showers
Partly Cloudy; Widely Scattered Snow Showers
Mostly Cloudy; Widely Scattered Snow Showers
Overcast; Widely Scattered Snow Showers
Partly Cloudy; Scattered Snow Showers
Tables B and C are subsets of the total possible conditions which may be indicated in the XML response from WeatherBank™ (that is, they are subsets of Table A), and are selected for their relevance to the exemplary application disclosed herein. It will be appreciated that other subsets may be selected, depending on the application, without departure from the spirit and scope of the invention. It will further be appreciated that Tables B and C are different from one another (although this will not necessarily always be the case), because conditions which are a few hours away (that is, conditions relating to the <current> information) may require different treatment than conditions which may be a day or two days into the future (conditions relating to the <period-1> and <period-2> information).
Tables B and C also provide severity assignments for the different conditions listed therein. These assignments are exemplary, and may be different depending on the application.
The entries in Tables B and C is herein referred to altertable conditions, because it comprises information which should be conveyed to the driver of the vehicle involved, or otherwise acted upon. Thus when any of the conditions listed in Table B are indicated in the <current> tag in the XML response from WeatherBank™, or any of the conditions listed in Table C are indicated in the <period-1> and <period-2> tag, weather broker 222 directs alert manager 230 to generate an alert signal—which signal includes the nature of and severity of the alert, along with its location, which may be identified by a weather station location from which the report issued, and the date of the conditions for the <period-1> and <period-2> information—and to send alert signal, via communication manager 232, to the associated vehicle processing system 110, for example through the cellular network described above (FIG. 1).
It may be desirable under some circumstances to limit the number of alerts sent from server 220 to vehicle processing system 210. Thus if more than one alertable condition is encountered, weather broker 222 may prioritize the alertable conditions, selecting for instance the condition with the highest severity rating as the one to base the alert upon. In this manner, communications resources may be conserved.
Communication between server 220 and vehicle processing system is facilitated by connection managers 226 and 212. The alert from server 220 is forwarded to client process manager 214 and then to application user interface 216 and output manager (TOM) 218.
Application user interface 216 is a process which responds differently depending on the situation. For instance, if the parking brake of the vehicle is disengaged, indicating that the vehicle is en route, then the alerts can be provided to the vehicle operator in auditory form. Specifically, a TTS (text-to-speech) conversion device 219 can be used to announce the alert verbally, in order to reduce distractions to the operator. Alternatively, if the parking brake is engaged, the alerts can be provided in visual form, using a dash-mounted component (not shown) having a display screen suitable for the purpose. A combination of the two expedients can also be employed, depending on the application.
While in the above example the invention is described in terms of weather-related conditions, it will be appreciated that other conditions can be monitored and conveyed to the vehicle operator.
With reference to
Traffic broker 322 is in contact with a traffic service provider, such as Televigation™ (360), via an HTTP/XML interface. Televigation™ is configured to provide information by market, by area, or by route. Using the preferred by-route approach, a request is sent to Televigation™, via an XML post, for information pertaining to the portion of the travel route between the Last Point Reach and the prospective point, taking the determined offset into account. The points are identified by their latitude and longitude coordinates. The XML response from Televigation™, an example of which is reproduced in Appendix B, provides a comprehensive data set of traffic incidents along the associated travel route portion. The data set includes the following information:
This information is the incident identification,
and is unique to an incident, or to an incident
update. Thus an update of the same incident would
have a new IncID.
This information pertains to the severity of
This information provides an indication as to whether an
alternate route should be found and taken.
This information pertains to the direction of travel
affected by the incident.
This information pertains to the current
roadway or a landmark.
This information indicates the intersection
at which the traffic incident occurred.
This information pertains to the time of the
This information pertains to the expected end
time of the update.
This information indicates the type of highway
ramp (Southbound, Eastbound, etc.) on which the
This information contains a verbal description of
the traffic incident.
Traffic broker 322 stores the incident identification information and sets it to automatically expire within a set period of time, preferably about one hour. When a traffic incident is retrieved from Televigation™, the IncID is checked against this stored information, and if it already exists, then an alert pertaining to this incident has already been sent and is not resent. If it does not already exist, then an alert is sent to the vehicle processing system 210, subject to additional filtering. This additional filtering could include, for example, only sending alerts whose impact—that is, severity—is above a predetermined threshold, such that minor traffic incidents are not alerted.
The alert is generated in alert generator 324, and sent wirelessly, via connection manager 326, in the manner described above with respect to the weather-related information. The traffic alert includes some or all of the above-listed information from Televigation™. Once received by vehicle processing system 210, the alert can be presented to the operator visually and/or audibly, depending on the situation—for instance, in accordance to whether the parking brake is engaged or disengaged.
The above are exemplary modes of carrying out the invention and are not intended to be limiting. It will be apparent to those of ordinary skill in the art that modifications thereto can be made without departure from the spirit and scope of the invention as set forth in the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US3875379||Aug 13, 1973||Apr 1, 1975||Carl W Vietor||Terminal airways traffic control system|
|US3947809||Jan 13, 1975||Mar 30, 1976||Sundstrand Data Control, Inc.||Below glide slope advisory warning system for aircraft|
|US4792906||Aug 29, 1986||Dec 20, 1988||The Boeing Company||Navigational apparatus and methods for displaying aircraft position with respect to a selected vertical flight path profile|
|US5526000||Mar 10, 1988||Jun 11, 1996||Electronique Serge Dassault||Procedure and automatic control device for an airborne vehicle in low altitude overflight|
|US5648768 *||Dec 30, 1994||Jul 15, 1997||Mapsys, Inc.||System and method for identifying, tabulating and presenting information of interest along a travel route|
|US5825283||Jul 3, 1996||Oct 20, 1998||Camhi; Elie||System for the security and auditing of persons and property|
|US5867804||Sep 6, 1995||Feb 2, 1999||Harold R. Pilley||Method and system for the control and management of a three dimensional space envelope|
|US5922040||Aug 30, 1996||Jul 13, 1999||Mobile Information System, Inc.||Method and apparatus for fleet management|
|US5949345 *||May 27, 1997||Sep 7, 1999||Microsoft Corporation||Displaying computer information to a driver of a vehicle|
|US5999882 *||Jun 4, 1997||Dec 7, 1999||Sterling Software, Inc.||Method and system of providing weather information along a travel route|
|US6031455 *||Feb 9, 1998||Feb 29, 2000||Motorola, Inc.||Method and apparatus for monitoring environmental conditions in a communication system|
|US6073075 *||Oct 29, 1996||Jun 6, 2000||Hitachi, Ltd.||Method and system for providing information for a mobile terminal|
|US6209026 *||Mar 7, 1997||Mar 27, 2001||Bin Ran||Central processing and combined central and local processing of personalized real-time traveler information over internet/intranet|
|US6304816 *||Jan 28, 1999||Oct 16, 2001||International Business Machines Corporation||Method and apparatus for automatic traffic conditions data collection using a distributed automotive computing system|
|US6317686 *||Jul 21, 2000||Nov 13, 2001||Bin Ran||Method of providing travel time|
|US6339745||Oct 12, 1999||Jan 15, 2002||Integrated Systems Research Corporation||System and method for fleet tracking|
|US6347263||Oct 15, 1999||Feb 12, 2002||Alliedsignal Inc.||Aircraft terrain information system|
|US6353398 *||Oct 22, 1999||Mar 5, 2002||Himanshu S. Amin||System for dynamically pushing information to a user utilizing global positioning system|
|US6654689 *||Nov 6, 2000||Nov 25, 2003||Weather Central, Inc.||System and method for providing personalized storm warnings|
|US20010020213 *||Mar 5, 2001||Sep 6, 2001||Ichiro Hatano||Navigation system, navigation information providing server, and navigation server|
|US20020067289 *||Dec 5, 2000||Jun 6, 2002||Michael Smith||Vehicle-centric weather prediction system and method|
|US20020121989 *||Mar 5, 2001||Sep 5, 2002||Ronnie Burns||Method and system for providing personalized traffic alerts|
|US20020143461||May 28, 2002||Oct 3, 2002||Burns Ray L.||Permission system for controlling interaction between autonomous vehicles in mining operation|
|GB2227389A||Title not available|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7746794 *||Aug 17, 2006||Jun 29, 2010||Federal Signal Corporation||Integrated municipal management console|
|US7905640||Jan 8, 2009||Mar 15, 2011||Federal Signal Corporation||Light bar and method for making|
|US8209113||Apr 21, 2008||Jun 26, 2012||Visteon Global Technologies, Inc.||Programmable route specific dynamic traffic warning system with segmentation identifiers|
|US8636395||Mar 4, 2011||Jan 28, 2014||Federal Signal Corporation||Light bar and method for making|
|US9002313||Oct 10, 2006||Apr 7, 2015||Federal Signal Corporation||Fully integrated light bar|
|US9316737||May 21, 2013||Apr 19, 2016||Spireon, Inc.||Container verification through an electrical receptacle and plug associated with a container and a transport vehicle of an intermodal freight transport system|
|US9346397||Jan 13, 2012||May 24, 2016||Federal Signal Corporation||Self-powered light bar|
|US9550453||Jan 14, 2014||Jan 24, 2017||Federal Signal Corporation||Light bar and method of making|
|US9551788||Mar 24, 2015||Jan 24, 2017||Jim Epler||Fleet pan to provide measurement and location of a stored transport item while maximizing space in an interior cavity of a trailer|
|US9779379||Dec 8, 2014||Oct 3, 2017||Spireon, Inc.||Container verification through an electrical receptacle and plug associated with a container and a transport vehicle of an intermodal freight transport system|
|US9779449||Aug 30, 2013||Oct 3, 2017||Spireon, Inc.||Veracity determination through comparison of a geospatial location of a vehicle with a provided data|
|US20070195706 *||Aug 17, 2006||Aug 23, 2007||Federal Signal Corporation||Integrated municipal management console|
|US20070195939 *||Oct 10, 2006||Aug 23, 2007||Federal Signal Corporation||Fully Integrated Light Bar|
|US20080201065 *||Apr 21, 2008||Aug 21, 2008||Zerod Richard D||Programmable route specific dynamic traffic warning system with segmentation identifiers|
|US20090079555 *||May 16, 2008||Mar 26, 2009||Giadha Aguirre De Carcer||Systems and methods for remotely configuring vehicle alerts and/or controls|
|US20110156589 *||Mar 4, 2011||Jun 30, 2011||Federal Signal Corporation||Light bar and method for making|
|U.S. Classification||701/522, 340/993, 340/995.13, 340/989, 340/992, 340/988, 340/995.24, 701/515, 701/537|
|International Classification||G08G5/04, G08G1/123, G08G1/09, G01W1/00|
|Apr 23, 2004||AS||Assignment|
Owner name: MOBILEARIA, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:THAYER, PETER A.;SHAO, VICTOR;MAHESH, SUBRAMANIAN;REEL/FRAME:014557/0319
Effective date: 20040402
|May 29, 2007||AS||Assignment|
Owner name: WIRELESS MATRIX USA, INC., VIRGINIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOBILEARIA, INC.;REEL/FRAME:019341/0768
Effective date: 20060720
|Jan 25, 2010||REMI||Maintenance fee reminder mailed|
|Jun 20, 2010||LAPS||Lapse for failure to pay maintenance fees|
|Apr 27, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Apr 27, 2011||SULP||Surcharge for late payment|
|Apr 27, 2011||FEPP|
Free format text: PETITION RELATED TO MAINTENANCE FEES GRANTED (ORIGINAL EVENT CODE: PMFG)
Free format text: PETITION RELATED TO MAINTENANCE FEES FILED (ORIGINAL EVENT CODE: PMFP)
|Aug 13, 2013||AS||Assignment|
Owner name: SQUARE 1 BANK, NORTH CAROLINA
Free format text: SECURITY AGREEMENT;ASSIGNOR:CALAMP WIRELESS DATA SYSTEMS, INC.;REEL/FRAME:031004/0675
Effective date: 20130716
|Dec 4, 2013||FPAY||Fee payment|
Year of fee payment: 8
|Mar 31, 2014||AS||Assignment|
Owner name: CALAMP WIRELESS DATA SYSTEMS, INC., CALIFORNIA
Free format text: CHANGE OF NAME;ASSIGNOR:WIRELESS MATRIX USA INC.;REEL/FRAME:032564/0423
Effective date: 20130604
|Nov 5, 2014||AS||Assignment|
Owner name: CALAMP WIRELESS NETWORKS CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CALAMP WIRELESS DATA SYSTEMS;REEL/FRAME:034111/0946
Effective date: 20141104
|Oct 26, 2017||MAFP|
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553)
Year of fee payment: 12