1. Field of the Invention
The present invention relates to a system and method for providing current weather warnings and alerts to vehicle occupants. More particularly, the present invention is directed to a weather information system that collects, formats, and broadcasts weather data to vehicles.
2. Description of Related Art
Navigation systems for determining a route from a start point to a destination point are well known in the art. In addition, navigation systems having capabilities for determining the geographic position of a reference point are also well known in the art (e.g., a Global Positioning System (GPS) or a self-contained system having distance and bearing sensors). As an example, a commonly used navigation system allows a user (or driver) of a vehicle to enter a destination place into the navigation system. The navigation system then looks up an appropriate route from an original point (using geographic positioning capabilities) to the destination point in a road map database (e.g., the route may be a route having the shortest distance from the start point to the destination, one that would take the vehicle the least time, or some other route), and guides the user to the destination point along the searched route through a visual display or vocal guide.
Recently, navigation systems have been improved to provide and utilize vehicle-related or geographically-relevant, real time traffic information in guiding the user to his/her destination, described in further detail in U.S. patent application Ser. No. 11/093,919, filed Mar. 29, 2005, titled Display Method and System for a Vehicle Navigation System, the disclosure of which is incorporated in its entirety herein by reference. However, there remains a need for systems and methods for collecting, utilizing, and providing vehicle-related, real time weather information and alerts to the user. In addition, there is a need for a vehicle navigation system that receives, processes, and displays real time weather alerts and information to the user.
Navigations systems have also recently been improved to allow for the broadcasting of data such as traffic information to a vehicle via a broadcast network such as XM Satellite Radio, described in further detail in U.S. patent application Ser. No. 11/266,879, filed Nov. 4, 2005, titled Data Broadcast Method for Traffic Information, the disclosure of which is incorporated in its entirety herein by reference. However, bandwidth and data transfer capacity over the broadcast network is limited, making conservation of bandwidth in future applications a necessity of design.
Accordingly, it would be advantageous to provide a vehicle navigation system that receives and processes real time information (e.g., traffic, weather, and other geographically-relevant or vehicle-related information) in guiding the user to his/her destination while making efficient use of limited broadcast bandwidth resources.
The present invention provides a weather information system for collecting, formatting, filtering, and delivering timely weather alerts and information to a vehicle navigation system, which in turn processes and displays the weather information for the vehicle occupants.
In accordance with one aspect of the embodiments described herein, there is provided a method for providing weather data to a vehicle comprising the steps of: (a) receiving a broadcast signal containing weather data referenced to a plurality of cells arranged in a grid corresponding to a geographic map; (b) determining the present location, speed, and direction of the vehicle; (c) calculating a geographic region for which the weather data will affect the vehicle user based upon the current location, speed, and direction of the vehicle; (d) filtering the weather data to yield filtered data comprising at least one of the plurality of cells correlated to the previously calculated geographic region; and (e) formatting the filtered data for display to vehicle occupants.
In accordance with another aspect of the embodiments described herein, there is provided a system for providing weather data to a vehicle having a telematics unit and a navigation system. The telematics unit is equipped to receive weather data over a broadcast network such that the weather data is referenced to a plurality of cells arranged in a grid corresponding to a geographic map. The navigation system is in electrical communication with the telematics unit for reception of the weather data and further comprises a display equipped to present the weather data to a user, a Global Positioning System antenna equipped to determine the vehicle location, a speed sensor equipped to determine the vehicle speed, and a yaw-rate sensor equipped to determine the vehicle direction. The navigation system is adapted to calculate a geographic region for which the weather data will affect the vehicle user based upon the current location, speed, and direction of the vehicle. At least one of the telematics unit and the navigation system is adapted to filter the weather data prior to user display based upon at least one of the plurality of cells correlated to the previously calculated geographic region.
In accordance with yet another aspect of the embodiments described herein, there is provided a method for providing weather warnings to a vehicle comprising the steps of: (a) receiving a first broadcast signal containing weather warning mesh data and a second broadcast signal containing weather warning information; (b) determining whether a current location of the vehicle is in or near the area to which the received weather warning mesh data and weather warning information apply; and (c) displaying a warning to the vehicle user if the current vehicle location is in or near the area to which the received weather warning mesh data and weather warning information apply.
The present invention provides a system that collects and formats regionally relevant and current weather information that is broadcast to vehicle navigation systems, while making efficient use of the available broadcast bandwidth.
Referring first to
The telematics unit 28 receives the broadcasted weather data from the satellite 26, and preferably filters the data to remove duplicate data and/or data that is not relevant to the geographic regions in which the vehicle is currently or will be traveling to. The telematics unit 28 comprises a duplicate filter 32 to remove duplicate data, as well as an area filter 34 to filter geographically irrelevant data. The filtered weather data is sent from the telematics unit 28 to the navigation system 36, which in turn processes and displays the data on a display unit 38 for the vehicle occupants.
The duplicate filter 32 and area filter 34 are optional, but generally desirable to reduce the amount of data that is received and processed by the navigation system 36. The same weather data is broadcasted until the weather data gets updated. The receiver stores the Mesh longitude number and Cyclic Redundancy Check (CRC). If the weather data comprises the same longitude number and CRC as the previous mesh data packet, the receiving telematics unit 28 filters and discards the duplicate data, thereby saving the navigation system 36 from having to waste time processing the duplicate data. In one embodiment, the navigation system 36 initiates a request for weather information data from the telematics unit 28. The request can be for all U.S. data, specific longitudinal area data, etc., so that the telematics unit 28 relays weather data for the requested geographic area to navigation system 36. This reduces the number of tasks system 36 must perform, and also makes efficient use of the bandwidth available in the communication channel between the system 36 and the telematics unit 28.
In the present embodiment, the transmitter 24, the satellite 26, and the telematics unit 28 are part of a satellite radio broadcasting system (e.g., XM Satellite Radio). It will be understood that the weather data 22 from the weather content provider 20 can be broadcast via any suitable information broadcast system (e.g., FM radio, AM radio, or the like), and is not limited to the satellite radio broadcast system illustrated in
With reference to
The system for delivering weather alerts to a vehicle first figures out whether a given weather alert pertains to the vehicle location. Typically, the weather alerts are generated and specific to a defined geographic area. In one embodiment, wherein the area to which the weather alert pertains is a large geographic region—namely a county—the system 1 receives and/or converts such data as a longitude and latitude data for the county border and defines a corresponding area on the digital map. In another embodiment, shown in
In yet another embodiment, vehicle velocity vectors (speed and direction) v(Pn) from multiple points are used to determine whether a vehicle will enter an area of alert. For example, as shown in
V(Pn)=[v(Pn)+v(Pn−1)+v(Pn−2)+v(Pn−3)]/4.
The calculated velocity vector V(Pn) is used to determine whether the vehicle will cross the border into the area of alert within a predetermined amount of time (e.g., 30 minutes). In another approach, the calculated velocity vector V(Pn) is used to determine whether the vehicle will leave the area of alert within the predetermined amount of time.
In accordance with one aspect of the embodiments described herein, the weather data may be broadcasted as a multi-longitudinal data array. An advantage of using a longitudinal-based array is that it is shorter than a latitude-based array, and therefore may take less time to be broadcast to a vehicle. It should be appreciated that as the broadcast time increases, there is an increased possibility that the broadcasted data signal will be interrupted by physical impediments such as bridges, buildings, etc. Interrupted data signals result in broken data, which may be deemed useless and thrown away by receiver units.
The weather data can be referenced to a grid covering the United States of America. Some portions of the weather data can be delivered in columns that are equally spaced in longitude across the U.S., as shown in
In one embodiment, shown in
In one embodiment, shown in
In one embodiment, each mesh cell comprises one byte of data, thereby making efficient use of the available broadcast bandwidth. In another embodiment, each mesh cell comprises less than one byte of data. An advantage of mesh cells having small data sizes is that it may reduce the amount of power and/or memory the navigation system uses to handle the weather data. Basic weather condition data (e.g., rain, snow, etc.) can be encoded with less than a single byte of data.
Weather conditions are determined from any number of known suitable sources, such as Doppler radars, Geostationary Operational Environmental Satellite Program (GOES) weather satellites, surface observation sites, etc. In one embodiment, the mesh cells are transmitted in column major order, and a separate message is used for each column. A message header is preferably sent at the start of each column, wherein the header contains the column number. For example, the first cell in the data is for 50N, while the second is for 49.875N, and so on.
With reference to
The weather alert manager 112 can be configured to receive meteorological data via communication link interface 134, or alternatively, via manual entry through input device 126. The meteorological data may be provided by a variety of sources, but preferably comprises NexRad attribute data. NexRad is a weather service provided by the National Weather Service (NWS), which employs a system of high powered radars scattered throughout the country that collect data that is synthesized for distribution to subscribers. The NexRad attribute data is distributed by several providers that can communicate the data via a satellite downlink or over a communication network connection such as a telephone line. Several of the NexRad providers are: Alden Electronics, Westborough, Mass., USA; UNISYS, Philadelphia, Pa., USA; and Weather Services International (WSI) Corporation, Billerica, Mass., USA. The NexRad attributes data provides subscribers with detailed information concerning storms detected by the NexRad radar sites. The NexRad attribute data may include the information in
The meteorological data can comprise manually entered information regarding a storm. Preferably, this information is provided by the emergency management agency (EMA) or another similar entity such as a local 911 service charged with weather warnings. Examples of factors that may be considered in such circumstances include the terrain of the local area or the presence of high risk structures in the path of a storm, such as a school or shopping mall.
The meteorological data received by the weather alert manager 112 is processed by the site specific program 120. Particularly, the site specific program 120 performs storm tracking functions on the storms that are identified by the meteorological data, and that are within the geographic region of interest. Systems capable of performing storm tracking functions, such as those required in the present system, which are commercially available include the NexTrac system by Baron Services, Inc., Alabama, USA, or Storm Pro by Kavouras, Minnesota, USA.
There are several possible methods of performing storm tracking operations. A first exemplary method involves gathering historical data of a particular storm so that the direction and speed of the storm can be derived from the location of the storm at two discrete points in time that are recorded in the historical data. A direction of the storm can then be determined by a direction vector passing through the two locations of the storm. The speed of the storm can be determined from the distance between the two points and the time the storm took to travel between the two points. From the direction and speed, the location of the storm at some future point in time can be mapped out within an acceptable degree of accuracy. A second exemplary method includes retrieving the NexRad attributes FCST13 ANGLE and FCST13 MVMT, and then calculating the position of the storm after a predefined period of time based upon these attributes, as described in detail below.
Initially, the NexRad attributes RANGE and AZ are utilized to determine a current×coordinate range and a current y coordinate range for the storm with respect to the NexRad radar site that is tracking the storm. The x and y coordinate ranges can then be utilized with the latitude and longitude coordinates of the NexRad radar site to determine a true location of the storm in latitude and longitude measurements. The latitude and longitude of the storm can be combined with the NexRad attributes FCST_ANGLE (i.e., forecasted direction) and FCST_MVMT (i.e., forecasted speed) to derive a position of the storm after a predetermined period of time.
In addition to determining a future position of the storm, the storm tracking function includes tracking the width and fan-out of the storm. The width can be determined from the NexRad attributes as described above, and the fan-out is user defined. For purposes of the present disclosure, the fan-out of a storm is the rate at which the storm track widens from the base of the storm to the end of the track. The fan-out is an error factor that allows the future path of the storm to be determined with a greater tolerance. That is, the geographic area over which a storm may travel is more likely to be within a predicted path that accounts for a widening of the storm as it moves, such as in a range of around ten percent. The fan-out can be varied between two instances of the storm tracking operation for the same storm to create qualifiers that indicate the likelihood that the storm will affect a particular cell. These qualifiers are referred to hereafter as presence qualifiers. As an example, a storm tracking operation performed on a storm with about ten percent fan-out may result in ten cells that the storm will “probably” cross. If the storm tracking operation were performed a second time with a fan-out of about twenty percent, then the results may include twenty or more cells that the storm may “possibly” cross.
In one embodiment, the site specific program 120 combines the storm tracking information with a geographic grid to determine which location(s) within the geographic grid are affected by the storm. The geographic grid comprises a geographic region that is divided into a plurality of cells that are individually identified by a unique identification number. Each cell preferably comprises at least one latitude coordinate and one longitude coordinate, though the size of the cells can be defined by the user. By comparing the coordinates defining the predicted path of the storm to the geographic grid on a cell-by-cell basis, each cell within the grid that is affected by the storm can be identified. Furthermore, by running multiple instances of the storm tracking with different fan-out settings, presence qualifiers can be determined for the identified cells that the storm is currently crossing, probably approaching, or possibly approaching.
The site specific program 120 generates a storm profile for the storms identified in the meteorological data. The storm profiles generated by the site specific program 120 preferably include a storm type identifier, a severity indicator, and a list of cell numbers and associated presence qualifiers such as “in this cell,” “possibly approaching this cell,” or “probably approaching this cell.” The storm identifier is provided by the NexRad attribute ID, the severity indicator is either manually entered by the EMA or automatically generated from one or more of the NexRad attributes, and the cell numbers and presence qualifiers are determined as described above. A data structure comprising a storm profile may appear as shown in
The distribution network 114 is configured to deliver the storm profiles to the respective remote units 116. Because the storm profiles require so little bandwidth for transmission to the remote units, updated storm profiles information can be sent out to subscribers frequently to ensure the weather information is current and up-to-date.
Preferably, the storm profiles and storm-related messages are generically broadcast to the remote units 116. Upon receiving a broadcast storm-related message, the remote unit 116 in a vehicle determines whether the message is applicable to the vehicle (e.g., whether the storm is within a predetermined distance of the current location of the vehicle or route to a destination). In other words, vehicles within broadcast range of the distribution network 114 will receive the storm profile broadcasts. Each vehicle, rather than the server or distribution network 114, decides whether the broadcast is appropriate or applicable to the vehicle.
In an alternative embodiment, the storm profiles are distributed according to an address integrated in the protocol overhead or the storm profile itself such as in an address field so that the remote units only respond to storm profiles that particularly identify cells that are associated with that remote unit 116. This can be accomplished by maintaining an end user database at the weather alert manager 112 that associates each end user with one or more of the cells. Thus, by cross referencing the cell numbers in a profile to a list of end users with associated cells, the specific end users that should be sent a storm profile can be identified. By identifying the end user, the remote unit 116 associated with that end user may be identified. The profiles may then be sent to the end user directly in a point-to-point communication utilizing the address.
In yet another embodiment, if the remote units 116 are configured to be responsive to specific address(es), then the profiles may be broadcast to all the remote units 114. The addresses in this case may be merely the cell numbers, and thereby, eliminate the need to provide a special address field to the data structure comprising the storm profile. The end user database may also identify how the profile is to be sent to the subscriber (e.g., a cellular phone call with recorded message or a pager with an alpha numeric message).
The distribution network 114 can be implemented by a variety of different communication mediums such as, but not limited to, wireless, cable television, pager, land-line telephone, satellite, etc. This flexibility in the method by which the storm profiles are delivered by the distribution network is advantageous because the method enables the subscriber to choose the most convenient method of delivering the site specific weather information of the present invention. The communication medium chosen may be based upon pricing tariffs, Federal Communications Commission (FCC) regulations, available technology, or the configuration of the remote unit (as described below). An example of one configuration for the distribution network 114 is a wireless network that initiates a call based upon a number (i.e., address) that the weather alert manager 112 retrieved from a subscriber database. The wireless network then makes a call to the remote unit 116 associated with that wireless telephone number for sending a storm profile to the remote unit 116, which processes the information for presentation to the subscriber in real-time.
The remote unit 116 is configured to receive a storm profile and respond thereto by providing audio and/or visual indicators that convey relevant storm information such as the type of storm, the severity of the storm, and the relevance of the storm with regard to the location of the remote unit 116. The remote unit 116 can be located throughout the geographic region covered by the geographic grid utilized by the weather alert manager 112. The remote units 116 can be located in homes, a public facilities (e.g., shopping malls or golf courses), mobile vehicles (e.g., automobiles, buses, taxicabs, plane, etc.), or the like.
With reference to
In accordance with another aspect of the embodiments described herein, four types of weather warnings are processed, encoded, and delivered to a vehicle navigation system by the weather information system—namely, advisories, watches, warnings, and road closings. Advisories, watches, and warnings are typically derived from bulletins from the National Weather Service (NWS). At least four types or categories of weather warnings are possible. The first type of situation occurs when the vehicle is currently in the warning area. The second situation occurs when the destination is in the warning area. The third situation occurs when the planned travel route of the vehicle is located in or passes through at least one warning area. The fourth exemplary situation is when the vehicle is located close to at least one warning area.
In one embodiment, weather warnings are encoded according to the numeric codes in
Weather warnings are not typically contained in the mesh data, since weather warnings do not always exist or occur (i.e., bits of data in the mesh cell data is not allocated to weather warnings). This allows for more efficient utilization of the available broadcast bandwidth. However, when the weather warnings are broadcast, the warning location data is linked to the mesh location, allowing for the navigation system to process and display the weather warning on the display unit easier.
In accordance with another aspect of the embodiments described herein, there is provided a mesh data system for a vehicle navigation system that is not limited to current weather data, but supports weather forecast data. Weather forecast data for locations can be defined relative to mesh grids, thereby making possible the encoding and sending of weather forecast data, such as temperature, general conditions, and the probability of precipitation. In one embodiment, weather forecast conditions are encoded in a field that is 5 bits in size, according to the table provided in
In one application, the mesh data covers all of the U.S., except Hawaii and Alaska. Since the mesh data is linked to particular geographic regions or cells defined by the grid defined by the grid, as opposed to being linked to roads or cities, there is no need to update the data format when new roads appear, etc. The weather data encoding schemes described herein are exemplary and are not intended to limit the scope of the present invention. It will be understood that the weather data encoding, broadcasting, and/or filtering methods described herein can be modified to make efficient use of the bandwidth available for data transmission. For example, in one embodiment, shown in
In accordance with another aspect of the embodiments described herein, there is provided a real time information system that collects, encodes, and delivers regionally-relevant traffic and weather information to vehicles via an information broadcast system, such as satellite radio or the like. The system can optionally deliver other regionally-relevant information, such as points of interests, etc.
In one embodiment, weather information/data is encoded into a traffic data format and incorporated into a traffic data stream, thereby avoiding having to use two separate formats to broadcast weather and traffic data. Further detail regarding traffic data formats is provided in U.S. patent application Ser. No. 11/093,919, filed Mar. 29, 2005, titled Display Method and System for a Vehicle Navigation System, and also in U.S. patent application Ser. No. 11/100,868, filed Apr. 6, 2005, titled Method and System for Controlling the Exchange of Vehicle Related Messages, the disclosures of both of which are incorporated in their entireties herein by reference.
In accordance with yet another aspect of the embodiments described herein, there is provided a system and method for formatting the weather data that is broadcast to a receiver or vehicle telematics unit inside the vehicle, and then ultimately transmitted to the navigation system of the vehicle. Again, the weather data is preferably filtered by the telematics unit to remove duplicate or geographically irrelevant data. The weather data can be formatted in any of ways, such as in Mesh Weather format, Warning Message/Warning ID format, and Mesh Radar/Satellite format, as shown in
In accordance with yet another aspect of the embodiments described herein, there is provided a vehicle navigation system that detects the current location of the vehicle, and that receives weather alerts within a predetermined distance of the current location (or that occur within the same geographic zone in which the vehicle is located or is traveling to). The navigation system typically comprises a digital map display for displaying the current location, direction, and speed of the vehicle, as well as weather information, as shown in
In one embodiment, the navigation system receives encoded weather data, processes the received weather data, and displays the appropriate weather icons, thereby reducing the amount and pieces of information needed to convey weather conditions to the driver and vehicle occupants, and thereby avoiding crowded displays. A cluster of weather icons can further be coalesced into a smaller number of representative icons, preferably with some indication that the weather information has been condensed. The user can preferably select the representative icon(s) (e.g., by moving a cursor on the display unit of the navigation system) to obtain additional information regarding weather conditions summarized by the representative icon(s). In one embodiment, effects can be applied to the weather icons (e.g., flashing icons) to call the attention of the user to the particular weather conditions, as illustrated in
In one embodiment, shown in
In accordance with another aspect of the embodiments described herein, there is provided a system and method for efficiently sending weather-related information, warnings, and alerts to a vehicle over a limited broadcast bandwidth. As used herein, weather warning mesh refers to weather warning data, typically displayed on a map that is divided into and comprises a mesh pattern or matrix. The warning area mesh typically comprises a plurality of weather warning cells, wherein each cell is defined by longitudinal and latitudinal coordinates.
With reference to
In one embodiment, the weather warning mesh comprises weather data that is divided into a matrix by dividing a map every ⅛ (0.125) degree along the longitudinal and latitudinal axes, such that each cell spans ⅛ (0.125) degree. It will be understood that the map information can be divided at different intervals along the longitudinal and latitudinal axes (or other suitable spatial reference set) to generate the weather warning mesh. The intervals between divisions of the map into cells can be adjusted as needed depending on the application, geographic properties of the mapped region, etc.
As used herein, weather warning information refers to detailed weather-related information/data that is linked to certain cells of the weather warning mesh. Typically, a weather warning information packet or class is applicable to a plurality of cells. Rather than linking the detailed weather warning information to each cell via a detailed coordinate system that consumes a large amount of broadcast bandwidth resources, the embodiment described herein involves linking detailed weather warning information to the cells of the weather warning mesh by assigning a warning number to each cell. As used herein, warning number refers to an assigned number that serves as a link between a given weather warning cell and the detailed weather warning information for the particular class of the weather warning cell. The warning numbers function as a type of classification system for cells of the weather warning mesh. In one embodiment, cells having the same warning number receive the same weather warning information (e.g., a warning regarding a flood or thunderstorm watch until 9:00 pm).
With reference to
The weather warning information 220, 222 and the weather warning mesh 210 are periodically updated, so there may be multiple versions of the weather warning information and the weather warning mesh. As such, a matching number is assigned to both the weather warning information and the weather warning mesh to ensure that the weather warning information generated at one particular time matches up with the weather warning mesh generated at the same time. As used herein, matching number refers to the particular version or iteration of the weather warning information and/or the weather warning mesh. The matching numbers for the weather warning information and the weather warning mesh increase each time there is an update to the weather warning information and the weather warning mesh, respectively. In one embodiment, the broadcast warning data is updated at predetermined time intervals (e.g., every 5 minutes).
In an exemplary embodiment, the matching number range is from 0 to 255. After 255, the matching numbers return to 0 and go to 255 again, such that a particular matching number can be reused. The vehicle navigation system typically comprises a timer for keeping track of how long received warning data has been around. Old warning data (i.e., data that has been around longer than a predetermined amount of time) is preferably deleted. In one approach, old warning data is deleted if the next warning data is not received within a set time period (e.g., 15 or 30 minutes). As such, reusing the same matching number does not pose a problem because the previously used same matching number does not exist any longer in the vehicle navigation system.
With reference to
It will be understood that the present system and method for providing weather warnings and alerts are particularly suitable for implementation with a vehicle navigation system. With reference to
At step 264, the onboard computer determines whether the current location of the vehicle is in or near the area to which weather warning applies. If so, the onboard computer proceeds to step 266; otherwise, the onboard computer proceeds to step 268. At step 266, the onboard computer checks the warning numbers and matching numbers of (a) the weather warning information and (b) the weather warning mesh. At step 272, the onboard computer determines whether there are any mismatches between the respective warning numbers and matching numbers of (a) the weather warning information and (b) the weather warning mesh. If there are not any mismatches, the method proceeds to step 274; otherwise, the method proceeds to step 282 to generate a warning flag. At step 274, the onboard computer determines whether the warning flag field has been set to 0. If not (i.e., where the warning flag field is set to 1), the method ends at step 290; otherwise, the method proceeds to step 276, where the onboard computer determines whether the blink field is set to 1. If the blink field is set to 1, the onboard computer prompts the display unit to display a blinking icon at step 278. If the blink field is set to 0, the vehicle does not display a blinking icon (step 280). Next, the method proceeds to step 282, where the warning flag field is set to 1, and the method comes to an end at step 290.
Back at step 268, the onboard computer determines whether it is operating in route guidance mode (i.e., whether the vehicle navigation system is providing driving directions to a destination). If so, the computer proceeds to step 270; otherwise, the computer proceeds to step 290 where the method ends. At step 270, the computer determines whether the destination or the route-to-route to destination overlaps with the areas affected by the weather warning. If so, the computer proceeds to step 266; otherwise, the computer proceeds to step 284, where the computer determines if the warning flag field has been set to 1. If the warning flag field has been set to 1, the method proceeds to step 286 where no warning icon is displayed, and then to step 288 where the warning flag field is set to 0. If at step 284, the computer determines that the warning flag field has not been set to 1, the computer proceeds to step 290 where the method ends.
With reference to
At step 308, if the blink field is set to 1, the vehicle shows the weather warning by displaying a blinking icon on the vehicle display screen at step 310; otherwise, a non-blinking icon is provided on the vehicle display screen at step 312. Next, the warning flag field is set to 1 at step 314. Again, weather warnings/alerts are provided to vehicle occupants when the warning flag field is set to 1.
Next, at step 316 if the pop-up field is set to 1, the method proceeds to step 318; otherwise, the method proceeds to step 320 where the method ends. At step 318, the vehicle shows the weather warning by displaying a pop-up weather warning message on the vehicle display screen. Finally, the method proceeds to step 320 where the method ends.
While the present invention has been illustrated and described with particularity in terms of preferred embodiments, it should be understood that no limitation of the scope of the invention is intended thereby. Features of any of the foregoing systems and methods may be substituted or added into the others, as will be apparent to those of skill in the art. It should also be understood that variations of the particular embodiments described herein will occur to those of ordinary skill in the art and yet be within the scope of the present invention.
This application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application No. 60/711,606, filed Aug. 25, 2005, which application is specifically incorporated herein, in its entirety, by reference. Additionally, this application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application No. 60/739,622, filed Nov. 23, 2005, which application is specifically incorporated herein, in its entirety, by reference.
Number | Name | Date | Kind |
---|---|---|---|
3283297 | Pfenninghausen et al. | Nov 1966 | A |
4404639 | McGuire | Sep 1983 | A |
4989146 | Imajo | Jan 1991 | A |
5173691 | Sumner | Dec 1992 | A |
5182555 | Sumner | Jan 1993 | A |
5359529 | Snider | Oct 1994 | A |
5388045 | Kamiya et al. | Feb 1995 | A |
5420794 | James | May 1995 | A |
5442553 | Parrillo | Aug 1995 | A |
5445347 | Ng | Aug 1995 | A |
5506773 | Takaba et al. | Apr 1996 | A |
5508931 | Snider | Apr 1996 | A |
5546305 | Kondo | Aug 1996 | A |
5551064 | Nobbe et al. | Aug 1996 | A |
5563788 | Yoon | Oct 1996 | A |
5590040 | Abe et al. | Dec 1996 | A |
5635924 | Tran et al. | Jun 1997 | A |
5636245 | Ernst et al. | Jun 1997 | A |
5648768 | Bouve | Jul 1997 | A |
5649300 | Snyder et al. | Jul 1997 | A |
5661787 | Pocock | Aug 1997 | A |
5664948 | Dimitriadis et al. | Sep 1997 | A |
5671195 | Lee | Sep 1997 | A |
5682525 | Bouve et al. | Oct 1997 | A |
5696676 | Takaba | Dec 1997 | A |
5699056 | Yoshida | Dec 1997 | A |
5757645 | Schneider et al. | May 1998 | A |
5774827 | Smith et al. | Jun 1998 | A |
5802545 | Coverdill | Sep 1998 | A |
5862510 | Saga et al. | Jan 1999 | A |
5864305 | Rosenquist | Jan 1999 | A |
5878056 | Black et al. | Mar 1999 | A |
5892463 | Hikita et al. | Apr 1999 | A |
5926108 | Wicks et al. | Jul 1999 | A |
5931878 | Chapin, Jr. | Aug 1999 | A |
5959577 | Fan et al. | Sep 1999 | A |
5964811 | Ishii et al. | Oct 1999 | A |
5982298 | Lappenbusch et al. | Nov 1999 | A |
5999882 | Simpson et al. | Dec 1999 | A |
6018699 | Baron, Sr. et al. | Jan 2000 | A |
6032046 | Nakano | Feb 2000 | A |
6073007 | Doyle | Jun 2000 | A |
6078865 | Koyanagi | Jun 2000 | A |
6084510 | Lemelson et al. | Jul 2000 | A |
6085146 | Kuribayashi et al. | Jul 2000 | A |
6091956 | Hollenberg | Jul 2000 | A |
6111521 | Mulder et al. | Aug 2000 | A |
6169894 | McCormick et al. | Jan 2001 | B1 |
6195602 | Hazama et al. | Feb 2001 | B1 |
6208935 | Yamada et al. | Mar 2001 | B1 |
6212388 | Seo | Apr 2001 | B1 |
6236330 | Cohen | May 2001 | B1 |
6240364 | Kerner et al. | May 2001 | B1 |
6243647 | Berstis et al. | Jun 2001 | B1 |
6246320 | Monroe | Jun 2001 | B1 |
6266607 | Meis et al. | Jul 2001 | B1 |
6266608 | Pertz | Jul 2001 | B1 |
6275774 | Baron, Sr. et al. | Aug 2001 | B1 |
6292723 | Brogan et al. | Sep 2001 | B1 |
6297748 | Lappenbusch et al. | Oct 2001 | B1 |
6308120 | Good | Oct 2001 | B1 |
6314370 | Curtright | Nov 2001 | B1 |
6317686 | Ran | Nov 2001 | B1 |
6329925 | Skiver et al. | Dec 2001 | B1 |
6330499 | Chou et al. | Dec 2001 | B1 |
6335729 | Nunokawa et al. | Jan 2002 | B2 |
6339736 | Moskowitz et al. | Jan 2002 | B1 |
6351709 | King et al. | Feb 2002 | B2 |
6356822 | Diaz et al. | Mar 2002 | B1 |
6356839 | Monde et al. | Mar 2002 | B1 |
6362730 | Razavi et al. | Mar 2002 | B2 |
6370454 | Moore | Apr 2002 | B1 |
6373883 | Soerensen et al. | Apr 2002 | B1 |
6381533 | Crane et al. | Apr 2002 | B1 |
6381538 | Robinson et al. | Apr 2002 | B1 |
6389337 | Kolls | May 2002 | B1 |
6397067 | Tanaka et al. | May 2002 | B1 |
6408307 | Semple et al. | Jun 2002 | B1 |
6421593 | Kempen et al. | Jul 2002 | B1 |
6434455 | Snow et al. | Aug 2002 | B1 |
6438490 | Ohta | Aug 2002 | B2 |
6459961 | Obradovich et al. | Oct 2002 | B1 |
6477452 | Good | Nov 2002 | B2 |
6480105 | Edwards | Nov 2002 | B2 |
6480145 | Hasegawa | Nov 2002 | B1 |
6490525 | Baron, Sr. et al. | Dec 2002 | B2 |
6493633 | Baron, Sr. et al. | Dec 2002 | B2 |
6510317 | Marko et al. | Jan 2003 | B1 |
6522250 | Ernst et al. | Feb 2003 | B1 |
6526335 | Treyz et al. | Feb 2003 | B1 |
6529143 | Mikkola et al. | Mar 2003 | B2 |
6539269 | Jarrow et al. | Mar 2003 | B1 |
6539302 | Bender et al. | Mar 2003 | B1 |
6542794 | Obradovich et al. | Apr 2003 | B2 |
6542822 | Froeberg | Apr 2003 | B1 |
6549833 | Katagishi et al. | Apr 2003 | B2 |
6552682 | Fan | Apr 2003 | B1 |
6553290 | Pillar | Apr 2003 | B1 |
6553308 | Uhlmann et al. | Apr 2003 | B1 |
6553313 | Froeberg | Apr 2003 | B1 |
6577934 | Matsunaga et al. | Jun 2003 | B2 |
6583734 | Bates et al. | Jun 2003 | B2 |
6587759 | Obradovich et al. | Jul 2003 | B2 |
6587777 | St. Pierre | Jul 2003 | B1 |
6587787 | Yokota | Jul 2003 | B1 |
6590507 | Burns | Jul 2003 | B2 |
6594576 | Fan et al. | Jul 2003 | B2 |
6597904 | Neustein | Jul 2003 | B1 |
6603405 | Smith | Aug 2003 | B2 |
6604038 | Leseky et al. | Aug 2003 | B1 |
6608559 | Lemelson et al. | Aug 2003 | B1 |
6609004 | Morse et al. | Aug 2003 | B1 |
6611740 | Lowrey et al. | Aug 2003 | B2 |
6611753 | Millington | Aug 2003 | B1 |
6615130 | Myr | Sep 2003 | B2 |
6615133 | Moskowitz et al. | Sep 2003 | B2 |
6615186 | Kolls | Sep 2003 | B1 |
6618669 | Ota et al. | Sep 2003 | B2 |
6636721 | Threadgill et al. | Oct 2003 | B2 |
6647417 | Hunter et al. | Nov 2003 | B1 |
6654600 | Pollak et al. | Nov 2003 | B1 |
6657558 | Horita et al. | Dec 2003 | B2 |
6658485 | Baber et al. | Dec 2003 | B1 |
6662090 | Toyama et al. | Dec 2003 | B2 |
6662091 | Wilson et al. | Dec 2003 | B2 |
6664922 | Fan | Dec 2003 | B1 |
6668219 | Hwang et al. | Dec 2003 | B2 |
6677854 | Dix | Jan 2004 | B2 |
6680694 | Knockeart et al. | Jan 2004 | B1 |
6681120 | Kim | Jan 2004 | B1 |
6691025 | Reimer | Feb 2004 | B2 |
6697633 | Dogan et al. | Feb 2004 | B1 |
6701231 | Borugian | Mar 2004 | B1 |
6701232 | Yamaki | Mar 2004 | B2 |
6707421 | Drury et al. | Mar 2004 | B1 |
6708108 | Jones | Mar 2004 | B2 |
6711398 | Talaie et al. | Mar 2004 | B1 |
6714797 | Rautila | Mar 2004 | B1 |
6720920 | Breed et al. | Apr 2004 | B2 |
6721685 | Kodama | Apr 2004 | B2 |
6724827 | Patsiokas et al. | Apr 2004 | B1 |
6730940 | Steranka et al. | May 2004 | B1 |
6732031 | Lightner et al. | May 2004 | B1 |
6735416 | Marko et al. | May 2004 | B1 |
6735504 | Katagishi et al. | May 2004 | B2 |
6738697 | Breed | May 2004 | B2 |
6741188 | Miller et al. | May 2004 | B1 |
6741834 | Godwin | May 2004 | B1 |
6748317 | Maruyama et al. | Jun 2004 | B2 |
6754485 | Obradovich et al. | Jun 2004 | B1 |
6754570 | Iihoshi et al. | Jun 2004 | B2 |
6757712 | Bastian et al. | Jun 2004 | B1 |
6785551 | Richard | Aug 2004 | B1 |
6798358 | Joyce et al. | Sep 2004 | B2 |
6804589 | Foxford et al. | Oct 2004 | B2 |
6810323 | Bullock et al. | Oct 2004 | B1 |
6810328 | Yokota et al. | Oct 2004 | B2 |
6812860 | Schwarzwalder, Jr. | Nov 2004 | B1 |
6812888 | Drury et al. | Nov 2004 | B2 |
6813549 | Good | Nov 2004 | B2 |
6816778 | Diaz | Nov 2004 | B2 |
6819986 | Hong et al. | Nov 2004 | B2 |
6823169 | Marko et al. | Nov 2004 | B2 |
6823263 | Kelly et al. | Nov 2004 | B1 |
6836539 | Katou et al. | Dec 2004 | B2 |
6836667 | Smith, Jr. | Dec 2004 | B1 |
6847871 | Malik et al. | Jan 2005 | B2 |
6847872 | Bodin et al. | Jan 2005 | B2 |
6847889 | Park et al. | Jan 2005 | B2 |
6850823 | Eun et al. | Feb 2005 | B2 |
6859720 | Satoh et al. | Feb 2005 | B2 |
6870487 | Nuesser et al. | Mar 2005 | B2 |
6871067 | Clark et al. | Mar 2005 | B2 |
6901374 | Himes | May 2005 | B1 |
6911918 | Chen | Jun 2005 | B2 |
6920382 | Katagishi et al. | Jul 2005 | B2 |
6928423 | Yamanaka | Aug 2005 | B1 |
6944430 | Berstis | Sep 2005 | B2 |
6971070 | Obradovich et al. | Nov 2005 | B2 |
6978206 | Pu et al. | Dec 2005 | B1 |
6983200 | Bodin et al. | Jan 2006 | B2 |
6987964 | Obradovich et al. | Jan 2006 | B2 |
6988034 | Marlatt et al. | Jan 2006 | B1 |
7010297 | Yokota | Mar 2006 | B2 |
7024310 | Root et al. | Apr 2006 | B2 |
7053780 | Straub et al. | May 2006 | B1 |
7054612 | Patel | May 2006 | B2 |
7089116 | Smith | Aug 2006 | B2 |
7170390 | Quinones et al. | Jan 2007 | B2 |
7174171 | Jones | Feb 2007 | B2 |
7174301 | Florance et al. | Feb 2007 | B2 |
7177651 | Almassy | Feb 2007 | B1 |
7184866 | Squires et al. | Feb 2007 | B2 |
7210142 | Hilt et al. | Apr 2007 | B2 |
7216109 | Donner | May 2007 | B1 |
20010001848 | Oshizawa et al. | May 2001 | A1 |
20020002534 | Davis et al. | Jan 2002 | A1 |
20020008637 | Iemelson et al. | Jan 2002 | A1 |
20020016655 | Joao | Feb 2002 | A1 |
20020027511 | Horita et al. | Mar 2002 | A1 |
20020027512 | Horita et al. | Mar 2002 | A1 |
20020029339 | Rowe | Mar 2002 | A1 |
20020049531 | Tanaka et al. | Apr 2002 | A1 |
20020067289 | Smith | Jun 2002 | A1 |
20020077741 | Hanebrink | Jun 2002 | A1 |
20020082771 | Anderson | Jun 2002 | A1 |
20020103582 | Ohmura et al. | Aug 2002 | A1 |
20020128773 | Chowanic et al. | Sep 2002 | A1 |
20020152021 | Ota et al. | Oct 2002 | A1 |
20020152115 | Morita et al. | Oct 2002 | A1 |
20020161841 | Kinnunen | Oct 2002 | A1 |
20020198632 | Breed et al. | Dec 2002 | A1 |
20030069683 | Lapidot | Apr 2003 | A1 |
20030098782 | Eastman et al. | May 2003 | A1 |
20030117982 | Minnick | Jun 2003 | A1 |
20030120426 | Baron, Sr. et al. | Jun 2003 | A1 |
20030169182 | Wilhelm et al. | Sep 2003 | A1 |
20030195814 | Striemer | Oct 2003 | A1 |
20030212479 | Baghshomali et al. | Nov 2003 | A1 |
20030216859 | Martell et al. | Nov 2003 | A1 |
20030225516 | DeKock et al. | Dec 2003 | A1 |
20030236613 | Satoh et al. | Dec 2003 | A1 |
20040012501 | Mazzara et al. | Jan 2004 | A1 |
20040043760 | Rosenfeld et al. | Mar 2004 | A1 |
20040059781 | Yoakum et al. | Mar 2004 | A1 |
20040068364 | Zhao et al. | Apr 2004 | A1 |
20040073356 | Craine | Apr 2004 | A1 |
20040075774 | Chang et al. | Apr 2004 | A1 |
20040080430 | Videtich | Apr 2004 | A1 |
20040102898 | Yokota et al. | May 2004 | A1 |
20040104842 | Drury et al. | Jun 2004 | A1 |
20040110515 | Blumberg et al. | Jun 2004 | A1 |
20040148099 | Kim | Jul 2004 | A1 |
20040198217 | Lee et al. | Oct 2004 | A1 |
20040199326 | Jung et al. | Oct 2004 | A1 |
20040203919 | Ross et al. | Oct 2004 | A1 |
20040204821 | Tu | Oct 2004 | A1 |
20040225437 | Endo et al. | Nov 2004 | A1 |
20040233070 | Finnern | Nov 2004 | A1 |
20040233101 | Kim | Nov 2004 | A1 |
20040239526 | Nakajima | Dec 2004 | A1 |
20040239531 | Adamczyk | Dec 2004 | A1 |
20040252197 | Fraley et al. | Dec 2004 | A1 |
20040260786 | Barile | Dec 2004 | A1 |
20050015197 | Ohtsuji et al. | Jan 2005 | A1 |
20050015199 | Lokshin et al. | Jan 2005 | A1 |
20050024236 | Gosdin et al. | Feb 2005 | A1 |
20050027436 | Yoshikawa et al. | Feb 2005 | A1 |
20050027449 | Marsh | Feb 2005 | A1 |
20050038596 | Yang et al. | Feb 2005 | A1 |
20050043880 | Yamane et al. | Feb 2005 | A1 |
20050046594 | Taylor | Mar 2005 | A1 |
20050065678 | Smith et al. | Mar 2005 | A1 |
20050137790 | Yamada et al. | Jun 2005 | A1 |
20050187714 | Brulle-Drews | Aug 2005 | A1 |
20050197775 | Smith | Sep 2005 | A1 |
20050203698 | Lee | Sep 2005 | A1 |
20050221876 | Van Bosch et al. | Oct 2005 | A1 |
20050222760 | Cabral et al. | Oct 2005 | A1 |
20050222771 | Matsumoto | Oct 2005 | A1 |
20050259606 | Shutter et al. | Nov 2005 | A1 |
20050273218 | Breed et al. | Dec 2005 | A1 |
20050288856 | Uyeki et al. | Dec 2005 | A1 |
20060022846 | Tummala | Feb 2006 | A1 |
20060030298 | Burton et al. | Feb 2006 | A1 |
20060038674 | Sumcad et al. | Feb 2006 | A1 |
20060055565 | Kawamata et al. | Mar 2006 | A1 |
20060058950 | Kato et al. | Mar 2006 | A1 |
20060080032 | Cooper et al. | Apr 2006 | A1 |
20060258379 | Oesterling et al. | Nov 2006 | A1 |
20060287818 | Okude et al. | Dec 2006 | A1 |
20060293846 | Lippert | Dec 2006 | A1 |
20070010258 | Landschaft et al. | Jan 2007 | A1 |
20070042812 | Basir | Feb 2007 | A1 |
20070054702 | Rokusek et al. | Mar 2007 | A1 |
20070078595 | Song | Apr 2007 | A1 |
20070106454 | Nonaka | May 2007 | A1 |
20070168524 | Chao et al. | Jul 2007 | A1 |
20080088480 | Rozum et al. | Apr 2008 | A1 |
20080106436 | Breed | May 2008 | A1 |
Number | Date | Country |
---|---|---|
10047279 | Apr 2002 | DE |
20315556 | May 2004 | DE |
0973299 | Jan 2000 | EP |
2700047 | Jul 1994 | FR |
6201394 | Jul 1994 | JP |
10-150477 | Jun 1998 | JP |
10307042 | Nov 1998 | JP |
11002539 | Jan 1999 | JP |
2000121377 | Apr 2000 | JP |
2000193469 | Jul 2000 | JP |
2001099665 | Apr 2001 | JP |
2001-216555 | Aug 2001 | JP |
2002-032276 | Jan 2002 | JP |
2002-077295 | Mar 2002 | JP |
2002-084298 | Mar 2002 | JP |
2002-318844 | Oct 2002 | JP |
2003004465 | Jan 2003 | JP |
2003004474 | Jan 2003 | JP |
2003294470 | Oct 2003 | JP |
2003329472 | Nov 2003 | JP |
2005147708 | Jun 2005 | JP |
2006003272 | Jan 2006 | JP |
WO2005088255 | Sep 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20070049260 A1 | Mar 2007 | US |
Number | Date | Country | |
---|---|---|---|
60711606 | Aug 2005 | US | |
60739622 | Nov 2005 | US |