BACKGROUND OF THE INVENTION [0002] The invention relates to vehicle fleet management, and more particularly, to a passive system for manipulating travel route condition information.

BRIEF SUMMARY OF THE INVENTION [0003] 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.

[0004] Further in accordance with the invention, a server for providing alerts to a 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.

[0005] 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.

[0006] 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.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS [0007] 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.

[0008] FIG. 1 is a schematic illustration of the use of the invention with a trucking fleet; [0009] FIG. 2, is a block diagram of a system using a weather broker in accordance with the invention ; and [0010] FIG. 3, is a block diagram of a system using a traffic broker in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION [0011] FIG. 1 schematically shows a trucking fleet consisting of a plurality of trucks 100 which are in communication with a remote server 120 via a cellular network represented by antenna 130. Cellular network would normally have multiple components, including other antennas, satellites and associated links, and so forth, which are omitted herein for simplicity. It is also contemplated that modes of wireless communication between trucks 100 and server 120 other than a cellular network may be implemented.

[0012] 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 Attorney Docket Number 033367-007 entitled"METHOD AND APPARATUS FOR PROVIDING INFORMATION PERTAINING TO VEHICLES LOCATED ALONG A PREDETERMINED TRAVEL ROUTE, "filed November 27,2002, and incorporated herein by reference in its entirety.

[0013] 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.

[0014] FIG. 2 is an architectural diagram of a passive alert system showing a vehicle processing system 210, which may be one of multiple such systems associated with respective vehicles of a fleet, all of which are in wireless communication with a server 220.. The systems 210 and the server 220 may be the same devices, respectively, as the systems 110 and server 120 shown in FIG.

1, but suitably configured to conduct the passive alert functions of the invention as described in greater detail below. Alternatively, they may be completely different devices used in conjunction with devices 110 and 120, depending on the particular application.

[0015] 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.

[0016] 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 GeoWavew 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 GeoWavew 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.

[0017] 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 WeatherBankw, 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.

[0018] 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 GeoWavew 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 GeoWåvew procedures performed in accordance with the aforementioned application.

[0019] 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.

[0020] 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 WeatherBankw, 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: http ://itxt. weatherbank. com: 8080/ ? Mobilaria: 42. 2.-112. 0 [0021] WeatherBankw responds to such a call with an XML response, which is reproduced as Appendix A. The XML response from WeatherBankl, 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 <weatherwxcode> contentforthe <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 WeatheBank.

Table A ' 0 .., r y . ri 0 1 Hail 34 Fog 2 Severe Thunderstorm 35 Haze 3 Freezing Rain 36 Sky Obscured 4 Freezing Drizzle 37 Thin Obscured, #1 5 Snow Shower 38 Obscured 6 Heavy Snow 39 Thin Obscured, #2 7 Rain and Snow 40 Overcast 8 Showers 41 Thin Overcast 9 Light Snow 42 Mostly Cloudy 10 Moderate Snow 43 Partly Cloudy, #1 11 Snow Pellets 44 Partly Cloudy, #2 12 Snow Grains 45 Mostly Clear, #1 13 Ice Pellets 46 Fair, #1 14 Heavy Thundershower 47 Clear, #1 15 Light Thundershower 48 Fair, #2 16 Moderate Thundershower 49 Fair, #3 17 Heavy Rain 50 High Overcast 18 Light Rain 51 High Thin Overcast 19 Moderate Rain 52 High Clouds 20 Heavy Drizzle 53 High Thin Clouds 21 Light Drizzle 54 Few High Clouds 22 Drizzle 55 Mostly Clear, #2 23 Blowing Snow 56 Fair, #4 24 Blowing Sand 57 Clear, #2 25 Blowing Dust 58 Fair, #5 26 Dust 59 Clear, #3 27 Ground Fog 60 Funnel Cloud, Tornado 28 Ice Crystals 61 Sandstorm 29 Ice Fog 62 Duststorm 30 Thick Fog 63 Patchy Fog 31 Thunder 64 Mist 32 Smog 65 Volcanic Ash [0022] 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.

Table B &6d6VM-u6*'""D A wcode Value"fi Descn'', [ [/tion Y. w'. y, # rx=, . Iert 5ver 1 2 Severe Thunderstorm 1 Freezing 4 Freezing Drizzle 1 5 Thunder Snow Shower 1 6 Heavy Snow 1 7 1 8 Snow Showers 1 9 Light Snow 3 10 Moderate Snow 2 11 Snow Pellets 1 12 Snow Grains 2 13 Ice Pellets 1 14 Heavy Thundershower 15 Light Thundershower 2 16 Moderate Thundershower 1 17 Heavy Rain 1 19 Moderate Rain 3 23 Blowing Snow 1 24 Blowing Sand 1 25 Blowing Dust 1 27 Ground 28 Ice Crystals 2 29 Ice Fog 2 30 Thick 1 33 Light 3 34 Fog 2 60 Cloud, Tornado 1 e61 Sandstorm 1 62 Duststorm 1 63 Patchy Fog 2 64 Mist 2 65 Volcanic Ash 1 Table C f .. C., 1. .-. ; xcodea . ASeven AA AB. Scattered Snow Showers 2 AC Partly Cloudy, Snow Showers 2 AC AD Snow AF Partly Cloudy ; Snow Showers 2 W Partly Cloudy ; Widely Scattered Snow Showers 2 X Mostly Cloudy ; Widely Scattered Snow Showers 2 Y Overcast ; Widely Scattered Snow Showers 2 Partly Scattered Snow Showers [0023] 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).

[0024] 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.

[0025] 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 WeatherBankw, 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 > informationand 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).

[0026] 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.

[0027] 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.

[0028] 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 expedents can also be employd, depending on the application.

[0029] While in the above example the invention s described in terms of weather-related conditions, it will be appreciated that other conditions can be monitored and conveyed to the vehicle operator FIG. 3 is an example directed to traffic conditions, and depicts a traffic broker 322 operating as the condition information broker in server 320. Traffic broker 322 can replace weather broker 222, and the system can be used exclusively to provide traffic information, in a process further described below. Alternatively, traffic broker 322 can operate in conjunction with weather broker 222, and both traffic and weather information can be provided. Further, weather traffic broker 322 and weather broker 222 can be combined into a single broker (not shown) capable of performing the functions of both devices. The particular configuration depends on the application and falls within the purview of the invention.

[0030] With reference to FIG. 3, traffic broker 322 operates in conjunction with GeoWave generator 22S, searching the data matrix containing geographical points based on the determined travel route to select the point-Last Point Reached-closest to the current position of the vehicle. Once determined, an ETA 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 prospective points is determined. The prospective point represents a point along the travel route at which the vehicle is expected to be during a particular time window in the future. For traffic information, a single prospective point, about fifteen minutes into the future, may suffice.

[0031] Traffic broker 322 is in contact with a traffic service provider, such as TelevigationN (360), via an HTTP/XML interface. TelevigationN is configured to provide information by market, by area, or by route. Using the preferred by-route approach, a request is sent to TelevigationN, 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 TelevigationN, 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: IncID: 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.

< Impact > : This information pertains to the severity of the incident.

< Diversion > : This information provides an indication as to whether an alternate route should be found and taken.

< TravelDirection > : This information pertains to the direction of travel affected by the incident.

< MainRoad > : This information pertains to the current roadway or a landmark.

< CrossRoadl >: This information indicates the intersection at which the traffic incident occurred.

< UpdateTime >: This information pertains to the time of the update.

< ExpectedEndTime >: This information pertains to the expected end time of the update.

< Ramp > : This information indicates the type of highway ramp (Soutbound, Eastbound, etc. ) on which the incident occurred.

< IncidentDescr >: This information contains a verbal description of the traffic incident.

[0032] 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 TelevigationTU, 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.

[0033] 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.

[0034] 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.

APPENDIX A < ? ? > - - <copyrighbCopyrightWeatherBank i<positionjongitude>-112. 01 c/posiffon_longitude cposition_latitude>42. KStation_name current <Cmestamp : 01 PM</timestamp> ctimestamp_day>Wednesdayc/bmestamp <tmestampdate>09/18/02</timestampdate> <name>Now</name> weather wxcode='40'>Overcast</weather> <temperature unit='Fahrenheit°>48</temperature> <temperatureunit=''Cetsius'>9. <dewpoint unit'Fahrenheit'>43</dewpoinb <dewpoint unit='Celsius">6. 0</dewpoint> <relative_humidity pressure unit='inches mercury'>Missing</pressure> cwindspeed unit="mileshou¢>8c/windspeed> <windfrom>North</windfrom> cfeels-like_temperature <visibility </current> - - cbmestamp_day>Wednesdayc/timestamp_day <timestampdate>09/18/02<timestampdate> weather wxcode="B>Fairc/weather> <hightemperature unit="Fahrenheit">61c/high_temperature> <high 1 </hightemperature> clow-temperature owtemperature> <low <sunrise>7 : 14 AM</sunrise> <sunset>7 : 32 PM</sunset> </period <period-2> <tmestampjay>Thursday</bmestamp-Oay> <Umestampiate>09/19/02<ttimestamp-Oate> weather wxcode="B">Fairc/weather> <hightemperature unit='Fahrenheit'>66</hightemperature> <high <low_temperature <low_temperature <sunrise>7 : 15 AM</sunrise> <sunset>7 : 30 PM</sunset> <Iperiod-2> cperiod-3> ctimestamp_day>Fridayc/timestarnp_ciay> <timestamp_date>09/20/02dtimestamp_date> weather wxcode="B">Fairclweather> chigh_temperature <high_temperature dow_temperature <low_temperature <sunrise>7 : 16 AM</sunrise> <sunset>7 : 28 PM</sunset> </period-3> <period-4> <timestampday>Saturday</timestampday> <timestamp_date>09/21/02dtimestamp_date> weather wxcode=nB">Fairc/weather> <high chigh_temperature <IowJemperature unit="Fahrenheir>37cAiow_temperature <low_temperature <sunrise>7 : 18 <sunset>7 : 26 PM</sunset> </period-4> - <timestampday>Sunday</timestampday> <timestampdate>09/22/02<timestampdate> cweather <high <high clow_temperature unit='Fahrenheit'>35<Ilow_temperature> <low_temperature csunrise>7 : 19 <sunset>7 : 24 PM</sunset> </period-5> </forecast> </weather> </data> APPENDIX B < ? xml version="1. 0" ? > - -<TNXResponseHeader> <TNXTRANSID/> </TNXResponseHeader> - <TrafficStatus - Distance UNIT="Km">146. - reaRef="0"Direction="3"Locationld="l0233"NextID="10234"OneMa y-''Yes" PrevID="10232"SecondDir="0"SegmentlD="311"TypeCode="2"> <Market Code="SAC"/> <Name>I-80</Name> <Name2>I-80 EB</Name2> <XStreet>GREENBACK LANE</XStreet> <XStreet2>GREENEACK <Alias/> <Alias2/ <Area>CITRUS HEIGHTS</Area> <Area2>CITRUS HEIGHTS</Area2> <Lat>38. 68273e/Lat <Lon>-121. 33528</Lon> <Vid>14644</Vid> <GeoKey>SMF511423000</GeoKey> <ExitNO/> <LocationTag>91</LocationTag> <CrossRoadlAlias/> </Location> - <Lat>0. <Lon>0. 0</Lon> <BackupRoad/> </Backup> - <month>9</month> <dayofmonth>9</dayofmonth> <year>2001</year> <dayofweek>3</dayofweek> <hours>18</hours> <minutes>14</minutes> <seconds>10</seconds> <epoch>1002676450000</epoch> </UpdateTime> - <month>9</month> <dayofmonth>13</dayofmonth> <year>2001</year> <dayofweek>7</dayofweek> <hours>5</hours> <minutes>15</minutes> <seconds>0</seconds> cepochlO02975300000c/epoch </ExpectedEndtime> -<ReportTime> emontho9c/monthz cdayofmonth>8</dayoftonthz <year>2001</year> <dayofweek>2</dayofweek> chours>5</hours> <minutes>10</minutes> <seconds>23</seconds> <epoch>1002543023000</epoch> </ReportTime> MainRoadzI-80c/MainRoado <CrossRoadl>GREENBACK LANE</CrossRoadl> <CrossRoadlAlias/> <CrossRoad2/> <Ramp Affected="O"/> <Lat>38. 682643</Lat> <Lon>-121. 336348</Lon> <ReportedBy/> <Impact Type="2"/> <IncidentDescr>ALTERNATING RAMP CLOSURES ARE SCHEDULED EACH NIGHT THROUGH FRIDAY NIGHT 8 PM TO AM</IncidentDescr> <RegionName>CITRUS HEIGHTS</RegionName> <Duration>4</Duration> <TravelDirection>E</TravelDirection> <LocQualifier Code=nOn/> <ItisMsg Description="Road construction during the night"Type="817"/> <Extent Direction="l"Value="l"/> Diversion Recommended="on/> <Priority Code="0"/> <Region Code="0"/> template Code="0"/> <Rwa Code=". <News Code="0"/> <Market Code="SAC"/> <Timezone>0</Timezone> <Delay>O</Delay> <Textl/> <Text2/> </TrafficIncident> </TNXResponseBody> </TNXResponse>