1. Field of the Invention
The present invention relates to a method and system for communicating information to vehicles from a remote location, and more particularly, to a method and system for filtering and buffering user searchable event program information and broadcasting the event program information to the vehicles.
2. Description of Related Art
Navigation systems for determining a route from a starting 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, such as 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 into the navigation system. The navigation system then looks up an appropriate route from an original point (using its 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 point, one which would take the vehicle the least time, or some other route), and guides the user to the destination 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 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. There also currently existing systems and methods of providing other types of location-based event program information to vehicle users. More specifically, event program information can comprise such time sensitive event program information as movies, sports events, plays, operas, concerts, etc. Location-based event program information is event program information that is scheduled to take place at venues within a predefined distance from a vehicle's current location or within a geographic zone (such as a postal zip code). The drawback of such existing systems and methods is that the vehicle navigation system does not maintain the needed data in system memory, on a hard disk drive, or a DVD disc. Thus when a user desires to view such information, it must first be received by the system via a broadcast or cellular network. The downloading of such a large volume of data requires a significant amount of data bandwidth, as well as long wait times for the user before the desired information can be displayed.
Thus, there remains a need for systems and methods for collecting, utilizing, and providing vehicle location-based event program information that is frequently updated and searchable by the user, wherein a vehicle navigation system receives, processes, and buffers event program information in memory while the navigation system is initializing, so that location-based event program information is quickly available to display to the user. A system that automatically updates itself daily in the background would reduce the bandwidth of broadcast data required to provide the user with selectable filtered event program information on her vehicle's navigation system when the user utilizes the system. Such a system would reduce the time needed for the vehicle navigation system to filter and process the event program data, as well as reducing the demands on the broadcasting network, so that less costly and sophisticated broadcast network systems are required to transmit location-based event program data to vehicle navigation systems. Additionally, it would be desirable 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 an event program she has viewed and selected from her vehicle's navigation system.
Moreover, there remains a need for a method and system for providing location-based event program information that is available for display to the user soon after the navigation system is initialized, thereby minimizing the delays needed for the system to retrieve and filter the data based on the vehicle's current location. Moreover, it is desired that the navigation system be provided with enough information to properly determine efficient routes to venues the user selects from the event program information displayed without being inundated with low priority, redundant, or superfluous traffic information. Thus, there is a need for providing event program information to a user in a useful, efficient manner that is easy to select by location with minimal wait time.
Accordingly, it would be desirable to provide a vehicle navigation method and system that overcomes the above-described shortcoming of the prior art while retaining their advantages.
The present invention addresses the shortcomings of the prior art systems and methods. In particular, the present invention is directed to a system and method for providing location-based event program information to a user in a useful, efficient manner that is easy to select by user selected criteria, such as venue, with minimal wait time required.
In accordance with one aspect of the embodiments described herein, there is provided a system for communicating event program information to at least one vehicle from a remote location that is filtered by a vehicle's current location. The system can comprise one or more antennas, a broadcast receiver unit having a data filter, and a navigational device and that displays to a user event program information by venue within a set distance from the vehicle's current location, with multi-leveled sub-menus that provide the user with a variety of event program information. In one embodiment, event program information comprises movie related information such as screening times, cast listings, movie reviews, movie trailers, etc The event program information can be broadcast by a plurality of methods such as satellite radio, digital FM radio broadcast, or a cellular telephone network. The system further comprises a memory buffer unit in the receiver unit that stores the vehicle's last reported location data and cross-referenced databases of movie program information with periodic updates so as to minimize bandwidth requirements of the system. The receiver unit can process and filter event program data while the navigational unit is initializing, using data stored in the memory buffer. The results can be stored in the memory buffer until the navigational unit is ready to receive, process, and display the data, thereby significantly reducing the wait time for the navigational unit to display the event program information to the unit.
In order to overcome the physical limitations of available memory space for data storage, the system can use a First-in, First-Out (“FIFO”) approach; wherein the oldest stored event program information is deleted first to make room for newer updates to the databases and the old database identifiers or fields are reassigned to new information received by the receiver unit.
In another embodiment of the invention, the user can filter the event program information by movie titles, wherein movie titles are displayed to the user by the navigational unit that are within a set distance from the vehicle's current location. The user can then determine which venues are screening the movies she is interested in attending. Once the user has mad a choice of venues to travel to, there is provided a method for generating maps and driving directions to guide the user to the event venue she desires. The method further comprises a voice synthesizer that emits a voice to guide the user along the travel route to the desired venue. In one approach, real time estimates of travel time to the event venue are provided to the user by the navigational unit.
In accordance with another aspect of the embodiments described herein, there is provided a method for providing event information to a user of a vehicle, comprising determining a geographic position of the vehicle, storing position data regarding the determined geographic position in a memory prior to a vehicle reactivation, retrieving the position data from the memory after the vehicle reactivation, and receiving event information from a remote location. The method further comprising filtering the received event information to discard information regarding events occurring farther than a predetermined distance from the determined geographic position of the vehicle. In a variation of this embodiment, this method further comprises generating the updated event information from the filtered event program updates, and displaying the updated event information to the user.
In accordance with yet another aspect of the embodiments described herein, there is provided a system for providing updated event information to a user of a vehicle, comprising a navigation unit for determining a geographic position of the vehicle, a receiver for receiving event program updates from a remote location, a memory unit, and a processor. The processor unit is operatively coupled to the navigation, receiver, and memory units, wherein the processor unit is programmed to store position data regarding the determined geographic position in the memory unit prior to a vehicle deactivation, and to retrieve the position data from the memory unit after the vehicle reactivation. The processor is further programmed to filter the received event program updates, to discard updates regarding events occurring farther than a predetermined distance from the determined geographic position of the vehicle, and to generate the updated event information from the filtered event program updates.
In accordance with yet another aspect of the embodiments described herein, there is provided a system for providing event information to a user of a vehicle, comprising a navigation unit for determining a geographic position of the vehicle, a receiver for receiving the event information, a memory unit, a processor unit operatively coupled to the navigation, receiver, and memory units. The processor unit stores position data regarding the determined geographic position in the memory unit prior to a vehicle deactivation, and retrieves the position data from the memory unit after the vehicle reactivation. The processor unit then filters the received event information to discard information regarding events occurring farther than a predetermined distance from the determined geographic position of the vehicle.
A more complete understanding of the a system and method for providing location-based event program information to a user will be afforded to those of skill in the art, as well as a realization of additional advantages and objectives thereof, by a consideration of the following detailed description of a preferred embodiment. Reference will be made to the appended sheets of drawings which will first be described briefly.
a is a schematic diagram of a first embodiment of a system pursuant to aspects of the invention;
b is a schematic diagram of a broadcast communication network;
c is a schematic diagram of a navigation device in communication with a mobile unit;
a is a data table showing an example of entries in a Facility ID database for the venues that can be cross-referenced to other event program information;
b is a data table showing an example of entries in an Event ID database for event titles that can be cross-referenced to other event program information;
a is a data table showing an example of show time data entries in database for Event ID#s that are cross-referenced to Facility ID#s;
b is a data table showing an example of show time data entries in database for Event ID#s, wherein multiple Event-ID#s are cross-referenced to a single Facility ID#;
a is a schematic diagram of an conventional method of broadcasting the entire event program information to the vehicle navigation system when the user accesses the system;
b is a schematic diagram of an improved method of broadcasting event program information in segments at different times periodically to the vehicle navigation system and storing the information in the system memory for quicker user access times;
a is a block diagram of an embodiment of a single-packet broadcast data message with header and cyclic redundancy codes;
b is a block diagram of a multi-packet message partitioned into multiple parts with header and cyclic redundancy codes;
a is a flowchart of a method that stores vehicle location data periodically in a memory buffer unit.
b is a flowchart of an improved method that displays filtered event program information to a user of the vehicle navigation system in an expedited manner, after the vehicle ignition is turned on;
The present invention generally relates to systems and methods for providing location-based event program information or event information or point of interest information to a vehicle navigation system. Event program information is regularly updated while the vehicle's ignition is turned to the “On” or “Accessory” position (i.e., while the vehicle is driven). The data received is preferably stored in a memory buffer for quick retrieval the next time the vehicle navigation system is initialized. In the detailed description that follows, like element numerals are used to describe like elements illustrated in one or more of the figures.
With reference to
The receiver unit 22 receives information from the remote location 10 and, in one embodiment, is in communication with the remote location by way of a one-to-many communication system. One-to-many communication systems include systems that can send information from one source to a plurality of receivers, such as a broadcast network 31. Broadcast networks include television, radio, and satellite networks. Referring now to
Referring now to
The position detection unit 24 may include a GPS receiver that communicates with a plurality of GPS satellites to determine the position of the vehicle 12 (shown in
Returning now to the embodiment shown in
In one embodiment, the information received from and transmitted to the remote location 10 by way of the mobile unit 18 is accessed by the user through the navigation device 14, which is in communication with the mobile unit 18. The mobile unit 18 may be embedded in the vehicle 12 and be in communication with the navigation device 14 by, for example, a cable (not shown).
In another embodiment, the navigation device 14 and mobile unit 18 are in communication with one another by way of RF transceiver units 54 and 52. Both the navigation device 14 and the mobile unit 18 include RF transceiver units 52, 54, which, in one embodiment, comply with the Bluetooth® wireless data communication standard and protocol established by Bluetooth SIG, Inc. or the like. The RF transceiver units 52, 54 allow the navigation device 14 and the mobile unit 18 to communicate with one another. In other embodiments (not shown), the receiver 32 and transmitter 14 of the mobile unit 18 and the receiver unit 20 of the navigation device 14 allow the navigation device 14 and mobile unit 18 to communicate with one another. In yet other embodiments, there may be an RF transceiver that is separate from the navigation device 14 and the mobile unit 18 and that allows the navigation device 14 and mobile unit 18 to communicate with one another.
In the alternate embodiment shown in
Note that in the alternate embodiment of
The remote locations 10, 110 include remote servers 44, 144, remote transmitters 56, 156, receivers 58, 158, and remote memory 60, 160, that are in communication with one another. As provided above, in the first embodiment, the remote transmitter 56 and receiver 58 communicate with the navigation device 14 and mobile unit 18 by way of the broadcast 31 and wireless 46 communication networks, respectively. In the alternate embodiment, the remote transmitter 156 and receiver 158 communicate with the navigation device 114, including the RF transceiver 152, by way of the broadcast communication network 131 and a network 162. The remote locations 10, 110 are also in communication with suppliers of traffic 48, 148 and/or other information 50, 150, such as government traffic information suppliers, private traffic information suppliers, and users of other vehicles, by way of the networks 62, 162.
In both the first and alternate embodiments shown in
As provided in greater detail below, the information suppliers 48, 50, 148, 150 may transmit updated user profiles and traffic-related information as well as point of interest information to the remote locations 10, 110. A plurality of user profiles are in a user profile database, which, along with traffic-related information, are stored in the remote memory 60, 160. The updated user profiles and new traffic-related information are transmitted from the remote locations 10, 110 to the navigation devices 14, 114 by way of the broadcast networks 31, 131. In other embodiments, the new traffic-related information, point of interest information, and updated user profiles may be transmitted to the vehicles 12, 112 by way of the wireless network 46 or the network 162. At the vehicle, the user profile stored in the memory 30 of the navigation device 14 is updated, and the vehicle-related information is made accessible to the user by way of the output unit 21 of the navigation device 14. In other embodiments, the information providers may communicate directly with the mobile unit 18 or RF transceiver 152 by way of the wireless communication network 46 or the network 162.
At step 314, the Navi queries the user with the option of filtering movie program information by venue. If the user has elected to filter movie program information by venue, then at step 318, the system filters movie program information by the vehicle's current location, so that at step 322, only movie titles and accompanying movie information will be displayed by the venues that are located within a given distance from the vehicle's current location. The criteria for filtering venues for display from the vehicle's current location can be pre-set or pre-defined as a user preference. In a variation of the embodiment, the filtering at step 318 is such that only venues within the same geographical zone or postal code as the vehicle's current location will be displayed to the user by the Navi at step 322. The filtering step of 318 can also filter the information displayed to venues that are within a particular number of zones away from the vehicle's current location as has been pre-set or per-defined as a user preference. In another variation of this embodiment (not shown), the Navi offers the user the option of filtering the movie information presented a second time, wherein the movie information filtered by venue is now filtered by movie title so that the user is able to view movie information sorted by title for only the theater venues located within the given distance of the vehicle, as discussed above.
If the user has not elected to filter movie program information by venue at step 314, then at step 316, the Navi queries the user with the option of filtering movie program information by movie title. If the user has elected to filter movie program information by title, then at step 320, the system filters movie program information by title, so that at step 324, only the movie titles and accompanying movie information are displayed for movie titles that are screening at movie venues within a given distance from the vehicle's current location. The criteria for filtering venues for display from the vehicle's current location can be pre-set or pre-defined as a user preference. As described above, in a variation of the embodiment, the filtering at step 320 is such that only venues within the same geographical zone or postal code as the vehicle's current location will be displayed to the user by the Navi at step 324. The filtering step of 318 can also filter the information displayed to venues that are within a particular number of zones away from the vehicle's current location as has been pre-set or per-defined as a user preference. In another variation of this embodiment, the Navi presents the user with the option of starting the filtering process over again by venue at step 314. Finally, if the user has not elected to filter movie program information by title at step 316, the method ends.
a is a data table or database showing an example of entries in a Facility ID database for the venues that can be cross-referenced to other event program information such as the entries in the Event ID database (see
b is a data table or database showing an example of entries in an Event ID database for event titles that can be cross-referenced to other event program information. Column 404 contains the Event Identification Number or E-ID# that has a code for each currently playing movie title. Columns 510-514 contain database entries that are associated with a particular E-ID# of column 404. Specifically, Column 510 contains the movie title, Column 512 contains the movie description, and column 514 contains the list of actors or cast members. It should be appreciated that other columns can be added to the data table for other types of related movie information, such as movie reviews and movie promotional icon image files.
The entries in the exemplary database of
a is a data table or database showing an example of show time data entries in a database for Event ID#s that are cross-referenced to Facility ID#s. Column 402 contains the Facility Identification Number or F-ID # and is associated with a particular E-ID# in column 404. Column 406 contains the event program data. The entry shown in
b is a data table or database showing an example of show time data entries in a database for Event ID#s, wherein multiple Event-ID#s are cross-referenced to a single Facility ID#. This data table is essentially the same as the data table of
a is a schematic diagram of an conventional method of broadcasting the entire event program information to the vehicle navigation system when the user accesses the system. Items 602-606 are representations of the database information that is needed for the Navi to display the event program information for the movie facilities in the United States. With the conventional method of providing event program information to vehicle users, the vehicle navigation system does not maintain the needed data in system memory, on a hard disk drive, or a DVD disc. Thus when a user desires to view such information, it is received via broadcast or cellular network. The downloading of such a large volume of data requires a significant amount of data bandwidth, as well as long wait times for the user.
b is a schematic diagram of an improved method of broadcasting event program information in segments at different times periodically to the vehicle navigation system and storing the information in the system memory (e.g., hard drive or DVD disc) for quicker user access times. The information displayed on the example display 600 is comprised of various lists or databases with database entries 610-620 (see database columns 502, 510, and 406 in
There are approximately 50,000 movie theaters in the United States. Movie industry analysts estimate that 95% of the potential movie viewing audience is interested in viewing the top 20 popular movies at any given point in time. Thus, the data bandwidth necessary to maintain a database of movie program information can be reduced by broadcasting this information for only the top 20 popular movies for all 50,000 theater facilities. Further, in delivering movie database content or data via a multicast broadcast to vehicle navigational devices, the use of a digital fountain protocol to encode the broadcast data minimizes the needed time and bandwidth to deliver the movie database data substantially error free. The required data bandwidth can be further reduced by the use of known data compression methods. As discussed above, by updates to the database entries 610-620 and database 608 may be sent at different times in the background when the vehicle's ignition switch is on, such as when the vehicle is being driven by the user. These bandwidth reduction methods together with the method of storing the Facility ID database described herein, greatly reduce the waiting time of the user that wishes to utilize the Navi to obtain movie program information.
The navigational system illustrated in the embodiment of
Looking closer now at the Navi 712, the microprocessor 722 processes user commands entered on the display unit 726 or other input device (not shown), as well as the location data received via the GPS antenna 708 and filtered database information from the microprocessor/data filter 716. The memory unit 724 can include at least a portion of a user profile and in some embodiments may include the entire user profile that stores user preferences such as favorite movie theater venues and/or distances from the vehicle's current location that the user is interested in using as a filtering criteria. The memory unit 724 includes a road map database portion, an event venue information or Facility ID database and, in some embodiments, includes a DVD unit for reading road map information not built into the navigation device. A plurality of other database information and database updates, such as movie titles, show times, cast listings, and movie reviews, are received from the data receiver unit 710 and are stored in the memory unit 724. Further, filtered data such as event program information and movie titles sent by the data receiver unit 710 are also stored in the memory unit 724.
The speed sensor 728 and the yaw rate sensor 730 are in electrical communication with the Navi 712 and are used to determine estimates of times to arrive at event program venues, such as movie theaters where a desired movie is playing, from the vehicle's current location. The speed sensor 728 and the yaw rate sensor 730 can also be used to determine the most efficient travel routes to the desired event program venue. In one embodiment, the estimated times to travel to a plurality of the event program venues are displayed to assist the user in deciding which event venue she would like to choose or receive further information about from the Navi 712.
The audio unit 732 is in electrical communication with the data receiver unit 710, the Navi 712, and the speaker 734. The audio unit 732 comprises an audio processor (not shown), an amplifier (not shown), and a speech synthesizer (not shown). The audio unit can provide verbal warnings and announcements to the user, as well as driving directions by the coupling of the audio unit 732 to the speaker 734. The audio unit 732 also provides audio for movie trailers and preview videos. Variations of this embodiment include the use of confirming tones or beeps that can be produced when a user selects a command or menu on the display unit 726. Another variation utilizes a human voice synthesis of the text portion displayed on the display unit 726 such as the names of movies, theaters and movie descriptions. The speaker 734 can be the same device used by the user to listen to radio, CD-ROM, DVD and other audio sources accessed in the vehicle by the user.
The display unit 726 is in electrical communication with the Navi 712 and displays a variety of types of information to the user, such as digital maps and routes that guide the user to an event venue location, as well as event program information with a variety of submenus. The display can show text, images and video clips such as movie trailers and promotional poster image icons for movies. The display unit 726 can be a touch display that shows icons that are activated when a user touches them with her finger.
Looking closer now at the data receiver unit 710, the microprocessor/data filter or filter 716 processes a plurality of types of data received by the radio data module 714 and updates data stored in the hard disk drive 720 and memory unit 724. A key function of the filter 714 is that it filters the large volume of data received by the data module 716 so that only information relevant to a user is sent to the Navi 712 for processing and ultimately display by the display unit 726.
As discussed further below with respect to
The mobile unit 18 (shown in
The payload section, which is between the header and the CRC code, includes the filter section and the broadcast data. The CRC code may be generated using any suitable algorithm, such as, but not limited to, the following polynomial function:
G(X)=X16+X15+X2+1
It should be appreciated that when the same message data is broadcast to plural vehicles of a common group, and when there are large numbers of target vehicles in the target group, the overall data amount is small (i.e., the broadcast efficiency is high). The payload section may include one set of broadcast data or multiple sets of broadcast data. That is, depending on the length of the message body, the broadcast message may be a single packet or multiple packets in length. For a single packet message, a header and CRC code is created and added to the Source Data to produce the Broadcast Data Packet. Alternatively, for a multiple packet message, the message body is partitioned into sections and each section has a header and CRC code added thereto. Separate Broadcast Data Packets are produced from each section, as shown in
b is a block diagram of a multi-packet message partitioned into multiple parts. When the source data of a broadcast data message is long, it may be divided into multiple parts for broadcast. In
It should be appreciated that the use of the source data CRC can ensure reliability of reconstruction of the multiple partitioned source data. But, the source data CRC also takes up data space that reduces the broadcast efficiency of the message. Accordingly, the source data CRC could be used selectively for instances in which high reliability is necessary or large data files are being broadcasted.
It will be noted that in some embodiments the movie program information has been previously sent to the receiver unit and has been stored in either semiconductor memory and/or a hard disk drive located within the receiver unit, so that the receiver unit is only updating the database with the data received from the broadcasted data. Because the receiver unit generally has a finite amount of memory, a First-in, First-Out method can be used to maintain the database. That is, when the available memory becomes full, the oldest entries are deleted from the database first and the new data received is stored in those memory locations. In another approach, older entries are deleted and new entries are added to the database at defined time intervals (predetermined or otherwise). At step 868, the receiver unit receives broadcast movie program data and waits for location data to be sent to the receiver unit from the Navi. At step 870, the Navi is ready to receive filtered movie program data from the receiver unit, but the Navi must first receive multiple GPS satellite signals (generally four or more) and compute the vehicle's current location. At step 872, the Navi sends the current location data to the receiver unit and at step 876 waits to receive filtered movie program data to be sent by the receiver unit.
At step 874, the receiver unit receives the current location data from the Navi and filters the movie program data utilizing an internal data filter unit. The filtered data is then sent to the Navi. At step 878, the Navi receives the filtered movie program data and at step 880, the Navi initialization is complete. Finally, at step 882, the Navi displays the filtered movie program data to the user with a series of icons and sub menus and the method ends.
a is a flowchart of a method that stores vehicle location data periodically in a memory buffer unit. At step 830, the navigation section or navigation unit or Navi periodically sends the vehicle's current location data to the receiver section or receiver unit. At step 832, the location data sent by the Navi is received and stored in a buffer memory unit located within the receiver section. At step 834, the ignition is switched off (or the ignition key is removed from the ignition switch) and the current navi cycle ends. This can occur when a user parks her car and leaves her vehicle. It will be understood that other ways of signaling to the Navi to power down are within the spirit and scope of the present invention. The method then ends and the end of a Navi cycle has been reached.
b is a flowchart of an improved method that displays filtered event program information to a user of the vehicle navigation system in an expedited manner, after the vehicle ignition is turned on. In the embodiment illustrated, event program data comprises movie program data; however, as discussed above, event program data can also comprise other types of event program data such as sports event data, play event data, opera event data, concert event data, etc. At step 840, a new Navi cycle commences when the vehicle's ignition is turned on (i.e., set to the “On,” “Accessory” or similar position). It will also be understood that other methods of signaling to the Navi to power on are within the spirit and scope of the present invention. At step 842, the broadcast receiver unit starts the initialization process. At step 844, the Navi starts the initialization process, which with many existing vehicle navigation systems, takes significantly longer to complete than the receiver unit does (as discussed above with respect to
At step 846, the receiver unit starts processing location data that has been stored in step 832. As discussed with respect to
In some embodiments, the movie program information has been previously sent to the receiver unit and has been stored in either semiconductor memory and/or a hard disk drive located within the receiver unit, so that the receiver unit is only updating the databases with the data received from the broadcasted data, thus utilizing significantly less data bandwidth. Because the receiver unit generally has only a finite amount of memory, a FIFO method is used to maintain the databases. That is, when the available memory becomes full, the oldest entries are deleted first and new data received is stored in those memory locations, as discussed above previously.
Next, at step 854 the updated data from step 852 is filtered and integrated with the movie program data stored in the receiver unit's semiconductor memory and/or hard drive. At step 862, the integrated data is stored in the memory buffer unit. Periodic location data updates received from the Navi section at step 860 (discussed further below) are also stored in the memory buffer at step 862. Next, at step 850, the Navi sends a “Ready to Receive” signal to the receiver section. Upon receiving this signal from the Navi section,
At step 864 the receiver section waits for the Navi section to send a “Ready to Receive” signal that is generated at step 850. When the “Ready to Receive” signal is received by the receiver section at step 864, the receiver section then sends the filtered movie data to the Navi section and the first portion of the method (concerning the receiver section) ends.
After the Navi section has progressed sufficiently in the initialization process at step 844, the Navi section sends a “Ready to Receive” signal to the receiver section at step 850. At step 856, the Navi section is ready to receive data and the Navi section receives the filtered movie program data sent by the receiver section at step 864. Next, at step 858, the Navi section competes the initialization procedure. At step 859, the Navi section processes and displays the filtered movie program data to the user with a series of icons and sub menus. Finally, at step 860, the Navi section periodically sends the vehicle's current location data to the receiver section and the data is stored in the receiver section's memory buffer at step 862, as discussed above and the second portion of the method (concerning the Navi section) ends. By the use of the memory data buffer in the method of
At time 0, the receiver unit and the Navi start-up initialization sequences. Bar 900 illustrates that from time 0 to time A, the receiver unit is starting-up and bar 908 shows that the Navi is starting-up from time 0 to time X. Until Bar 900 reaches time A, the receiver unit cannot receive, send, or process data. Similarly, until time B, the Navi can not receive, send or process data or commands. Starting at time A, Bar 902 indicates that the receiver unit can now receive, process and filter data. In the provided embodiment, the data the receiver unit receives is the broadcast data that comprises a set of periodic data bursts of data packets that are broadcast by satellite radio, digital FM radio broadcast, cellular network, etc. Bar 910 shows that the Navi unit is able to receive filtered data sent by the receiver unit starting at time B, but as discussed in further detail below, there is not yet any filtered event program data being sent from the receiver.
At time X, a data packet 918 is broadcast. As shown by bar 902, the receiver unit can receive, process, and filter the data packet 918 at time X, but the receiver unit is waiting for the Navi unit to send the vehicle's current location data so that the receiver unit can filter the data packet 918 by location. In a variation of this embodiment, some of the event program data is stored in the receiver unit or Navi unit, but in such a case, the receiver unit must still wait to receive the current location data from the Navi unit before the event program information can be filtered.
With continued reference to the embodiment shown in
At time 0, the receiver unit starts an initialization sequence and simultaneously, but at a different rate, the Navi unit starts an initialization sequence as well. Bar 900 illustrates that from time 0 to time A, the receiver unit is starting-up and bar 908 indicates that the Navi is starting-up from time 0 to time X. Until Bar 900 reaches time A, the receiver unit can not receive, send, or process data. Similarly, until time B, the Navi unit can not receive, send or process data or commands. Starting at time A, Bar 902 indicates that the receiver unit can now receive, process and filter data. In the embodiment, the data the receiver unit receives is the data broadcast, that comprises a set of periodic data bursts of data packets that are broadcast by satellite radio, digital FM radio broadcast, cellular network, etc. Bar 910 shows that the Navi unit is able to receive filtered data sent by the receiver unit starting at time B. Unlike the embodiment of
At time X, a data packet 918 is broadcast. As shown by bar 902, the receiver unit can receive, process, and filter the data packet 918 at time X using the location data stored in the memory buffer. In this embodiment, the event program data is also stored in the memory buffer unit, so that the receiver unit starts to process and filter the event program information at time A, as shown by bar 922. Because the Navi unit is not yet ready to receive any filtered data from the receiver unit until time B, the receiver unit stores the processed and filtered event program data in the same memory buffer as the location data until time B. At time B, the receiver unit sends the event program data to the receiver, as shown by bar 926. At time X, the data packet 918 is received by the receiver unit, as shown by bar 902; however, in this embodiment, the data packet 918 is used to update the event program data already stored in the memory buffer unit.
At time B, the Navi unit is ready to receive the processed and filtered event program data from the receiver section, as shown by bar 910. In this embodiment, the receiver unit is not sitting idle waiting for the location data to be sent, as was the case in
It will be noted that the improved methods and systems outlined in the figures herein described are merely exemplary embodiments of the present invention. In other embodiments, subsets, different combinations, and variations of the steps described with respect to the figures can be used to filter and buffer user searchable event program information and broadcast the event program information to a vehicle. Features of any of the foregoing methods and systems may be substituted or added into others, as will be apparent to one of skill in the art.
Having thus described a preferred embodiment of a method and system for providing location-based event program information to a user, it should be apparent to those skilled in the art that certain advantages of the within system have been achieved. It should also be appreciated that various modifications, adaptations, and alternative embodiments thereof may be made within the scope and spirit of the present invention. For example, the use of the memory buffer to allow the receiver section of the navigational system to begin processing and filtering event program data while the navigational section is initializing so that the navigational section is ready to display filtered information quicker than previously disclosed methods has been illustrated, but it should be apparent that many of the inventive concepts described above would be equally applicable to use with other non-broadcast communication networks.
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 |
5303401 | Duckeck et al. | Apr 1994 | A |
5359529 | Snider | Oct 1994 | A |
5388045 | Kamiya et al. | Feb 1995 | A |
5406490 | Braegas | Apr 1995 | A |
5420794 | James | May 1995 | A |
5442553 | Parrillo | Aug 1995 | A |
5445347 | Ng | Aug 1995 | A |
5465088 | Braegas | Nov 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 |
5608635 | Tamai | Mar 1997 | 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 |
5842146 | Shishido | Nov 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 |
5898680 | Johnstone et al. | Apr 1999 | A |
5911773 | Mutsuga et al. | Jun 1999 | A |
5926108 | Wicks et al. | Jul 1999 | A |
5928307 | Oshizawa 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 |
6032046 | Nakano | Feb 2000 | A |
6073007 | Doyle | Jun 2000 | A |
6078865 | Koyanagi | Jun 2000 | A |
6085146 | Kuribayashi et al. | Jul 2000 | A |
6111521 | Mulder et al. | Aug 2000 | A |
6163751 | Van Roekel | Dec 2000 | A |
6169894 | McCormick et al. | Jan 2001 | B1 |
6178378 | Leibold | Jan 2001 | B1 |
6195602 | Hazama et al. | Feb 2001 | B1 |
6204778 | Bergan et al. | Mar 2001 | B1 |
6208932 | Ohmura et al. | Mar 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 |
6253146 | Hanson et al. | Jun 2001 | B1 |
6255963 | Heimann et al. | Jul 2001 | B1 |
6266607 | Meis et al. | Jul 2001 | B1 |
6266608 | Pertz | Jul 2001 | B1 |
6292723 | Brogan et al. | Sep 2001 | B1 |
6297748 | Lappenbusch et al. | Oct 2001 | B1 |
6298302 | Walgers et al. | Oct 2001 | B2 |
6308120 | Good | Oct 2001 | B1 |
6317685 | Kozak et al. | Nov 2001 | B1 |
6317686 | Ran | Nov 2001 | B1 |
6321158 | DeLome et al. | Nov 2001 | B1 |
6329925 | Skiver et al. | Dec 2001 | B1 |
6330499 | Chou et al. | Dec 2001 | B1 |
6339736 | Moskowitz et al. | Jan 2002 | B1 |
6349211 | Koshima et al. | Feb 2002 | B2 |
6349261 | Ohnishi et al. | Feb 2002 | B1 |
6351709 | King et al. | Feb 2002 | B2 |
6356822 | Diaz et al. | Mar 2002 | B1 |
6362730 | Razavi et al. | Mar 2002 | B2 |
6370454 | Moore | Apr 2002 | B1 |
6373883 | Sorensen et al. | Apr 2002 | B1 |
6374177 | Lee et al. | Apr 2002 | B1 |
6381533 | Crane 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 |
6453230 | Geurts | Sep 2002 | B1 |
6456234 | Johnson | Sep 2002 | B1 |
6459961 | Obradovich et al. | Oct 2002 | B1 |
6477452 | Good | Nov 2002 | B2 |
6480105 | Edwards | Nov 2002 | B2 |
6480145 | Hasegawa | Nov 2002 | B1 |
6480783 | Myr | Nov 2002 | B1 |
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 |
6546333 | Tanaka et al. | Apr 2003 | B2 |
6549833 | Katagishi et al. | Apr 2003 | B2 |
6552682 | Fan | Apr 2003 | B1 |
6553289 | Maki et al. | Apr 2003 | B2 |
6553290 | Pillar | Apr 2003 | B1 |
6553308 | Uhlmann et al. | Apr 2003 | B1 |
6553309 | Uchida et al. | Apr 2003 | B2 |
6553313 | Froeberg | Apr 2003 | B1 |
6577934 | Matsunaga et al. | Jun 2003 | B2 |
6583734 | Bates et al. | Jun 2003 | B2 |
6584401 | Kirshenbaum et al. | Jun 2003 | B2 |
6587759 | Obradovich et al. | Jul 2003 | B2 |
6587777 | St. Pierre | Jul 2003 | B1 |
6587785 | Jijina et al. | Jul 2003 | B2 |
6587787 | Yokota | Jul 2003 | B1 |
6590507 | Burns | Jul 2003 | B2 |
6591188 | Ohler | Jul 2003 | B1 |
6594576 | Fan et al. | Jul 2003 | B2 |
6597904 | Neustein | Jul 2003 | B1 |
6603405 | Smith | Aug 2003 | B2 |
6604038 | Lesesky 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 | Boies et al. | Sep 2003 | B2 |
6615186 | Kolls | Sep 2003 | B1 |
6618669 | Ota et al. | Sep 2003 | B2 |
6622083 | Knockeart et al. | Sep 2003 | B1 |
6622087 | Anderson | Sep 2003 | B2 |
6633238 | Lemelson et al. | Oct 2003 | B2 |
6636721 | Threadgill et al. | Oct 2003 | B2 |
6647417 | Hunter et al. | Nov 2003 | B1 |
6650948 | Atkinson 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 |
6680674 | Park | Jan 2004 | B1 |
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 |
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 |
6760661 | Klein et al. | Jul 2004 | B2 |
6785551 | Richard | Aug 2004 | B1 |
6785606 | DeKock et al. | Aug 2004 | B2 |
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 |
6819268 | Wakamatsu et al. | 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 |
6850842 | Park | Feb 2005 | B2 |
6859720 | Satoh et al. | Feb 2005 | B2 |
6859726 | Choi | Feb 2005 | B2 |
6859728 | Sakamoto et al. | Feb 2005 | B2 |
6862524 | Nagda et al. | Mar 2005 | B1 |
6868331 | Hanebrink | Mar 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 |
6920328 | Wollrab | Jul 2005 | B2 |
6920382 | Katagishi et al. | Jul 2005 | B2 |
6928423 | Yamanaka | Aug 2005 | B1 |
6944430 | Berstis | Sep 2005 | B2 |
6961758 | Krishnan | Nov 2005 | B2 |
6971070 | Obradovich et al. | Nov 2005 | B2 |
6973384 | Zhao et al. | Dec 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 |
6995686 | Gosdin et al. | Feb 2006 | B2 |
7006903 | Smith et al. | Feb 2006 | B2 |
7010297 | Yokota | Mar 2006 | B2 |
7026958 | Wainfan et al. | Apr 2006 | B2 |
7050818 | Tendler | May 2006 | B2 |
7054740 | Chinomi et al. | May 2006 | B2 |
7096115 | Groth et al. | Aug 2006 | B1 |
7155376 | Yang et al. | Dec 2006 | B2 |
7170390 | Quinones et al. | Jan 2007 | B2 |
7174301 | Florance et al. | Feb 2007 | B2 |
7184866 | Squires et al. | Feb 2007 | B2 |
7210142 | Hilt et al. | Apr 2007 | B2 |
7216109 | Donner | May 2007 | B1 |
7307513 | Shutter et al. | Dec 2007 | B2 |
20010001848 | Oshizawa et al. | May 2001 | A1 |
20010012004 | Nunokawa et al. | Aug 2001 | A1 |
20010029425 | Myr | Oct 2001 | A1 |
20020002534 | Davis et al. | Jan 2002 | A1 |
20020003495 | Johnstone et al. | Jan 2002 | A1 |
20020016655 | Joao | Feb 2002 | A1 |
20020029339 | Rowe | Mar 2002 | A1 |
20020032507 | Diaz et al. | Mar 2002 | A1 |
20020044049 | Saito et al. | Apr 2002 | A1 |
20020049531 | Tanaka et al. | Apr 2002 | A1 |
20020062236 | Murashita | May 2002 | A1 |
20020067289 | Smith | Jun 2002 | A1 |
20020072378 | Gaal | Jun 2002 | A1 |
20020077741 | Hanebrink | Jun 2002 | A1 |
20020080022 | Edwards | Jun 2002 | A1 |
20020087237 | Ol et al. | Jul 2002 | A1 |
20020103582 | Ohmura et al. | Aug 2002 | A1 |
20020103583 | Ohmura et al. | Aug 2002 | A1 |
20020103597 | Takayama 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 |
20020156692 | Squeglia et al. | Oct 2002 | A1 |
20020161495 | Yamaki | Oct 2002 | A1 |
20020161841 | Kinnunen | Oct 2002 | A1 |
20020165662 | Maruyama et al. | Nov 2002 | A1 |
20020165665 | Kim | Nov 2002 | A1 |
20020176494 | Zhao et al. | Nov 2002 | A1 |
20020177926 | Lockwood et al. | Nov 2002 | A1 |
20020193923 | Toyama et al. | Dec 2002 | A1 |
20020193926 | Katagishi et al. | Dec 2002 | A1 |
20020198632 | Breed et al. | Dec 2002 | A1 |
20020198637 | Shibata | Dec 2002 | A1 |
20030006912 | Brescia | Jan 2003 | A1 |
20030028297 | Iihoshi et al. | Feb 2003 | A1 |
20030028312 | Matsuoka et al. | Feb 2003 | A1 |
20030051239 | Hudspeth | Mar 2003 | A1 |
20030060977 | Jihina | Mar 2003 | A1 |
20030063628 | Marko et al. | Apr 2003 | A1 |
20030069683 | Lapidot et al. | Apr 2003 | A1 |
20030069978 | Cherry et al. | Apr 2003 | A1 |
20030081587 | Ichiyoshi | May 2003 | A1 |
20030083813 | Park | May 2003 | A1 |
20030093476 | Syed | May 2003 | A1 |
20030095038 | Dix | May 2003 | A1 |
20030098782 | Eastman et al. | May 2003 | A1 |
20030109972 | Tak | Jun 2003 | A1 |
20030117982 | Minnick | Jun 2003 | A1 |
20030125866 | Mori et al. | Jul 2003 | A1 |
20030158640 | Pillar et al. | Aug 2003 | A1 |
20030167110 | Smith et al. | Sep 2003 | A1 |
20030169182 | Wilhelm et al. | Sep 2003 | A1 |
20030182034 | Katagishi et al. | Sep 2003 | A1 |
20030191583 | Uhlmann et al. | Oct 2003 | A1 |
20030195695 | Maruyama et al. | Oct 2003 | A1 |
20030195814 | Striemer | Oct 2003 | A1 |
20030216859 | Martell et al. | Nov 2003 | A1 |
20030225516 | DeKock et al. | Dec 2003 | A1 |
20030229441 | Pechatnikov et al. | Dec 2003 | A1 |
20030236613 | Satoh et al. | Dec 2003 | A1 |
20040010366 | Videtich | Jan 2004 | A1 |
20040012501 | Mazzara et al. | Jan 2004 | A1 |
20040024753 | Chane et al. | Feb 2004 | A1 |
20040043760 | Rosenfeld et al. | Mar 2004 | A1 |
20040044605 | Bodin et al. | Mar 2004 | A1 |
20040059613 | Ford et al. | Mar 2004 | A1 |
20040059781 | Yoakum et al. | Mar 2004 | A1 |
20040068362 | Maekawa et al. | Apr 2004 | A1 |
20040068363 | Goto | Apr 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 |
20040085198 | Saito et al. | May 2004 | A1 |
20040093243 | Bodin et al. | May 2004 | A1 |
20040102898 | Yokota et al. | May 2004 | A1 |
20040104842 | Drury et al. | Jun 2004 | A1 |
20040110515 | Blumberg et al. | Jun 2004 | A1 |
20040117113 | Friedrichs et al. | Jun 2004 | A1 |
20040119612 | Chen | Jun 2004 | A1 |
20040148099 | Kim | Jul 2004 | A1 |
20040150534 | Linn | Aug 2004 | A1 |
20040158392 | Choi | Aug 2004 | A1 |
20040167707 | Bragansa et al. | Aug 2004 | A1 |
20040172192 | Knutson | Sep 2004 | A1 |
20040198217 | Lee et al. | Oct 2004 | A1 |
20040203630 | Wang | Oct 2004 | A1 |
20040203909 | Koster | Oct 2004 | A1 |
20040204821 | Tu | Oct 2004 | A1 |
20040204842 | Shinozaki | Oct 2004 | A1 |
20040208204 | Crinon | Oct 2004 | A1 |
20040233070 | Finnern | Nov 2004 | A1 |
20040233101 | Kim | Nov 2004 | A1 |
20040239526 | Nakajima | Dec 2004 | A1 |
20040239531 | Adamczyk | Dec 2004 | A1 |
20040246147 | von Grabe | Dec 2004 | A1 |
20040249529 | Kelly et al. | Dec 2004 | A1 |
20040249530 | Kelly et al. | Dec 2004 | A1 |
20040249531 | Kelly et al. | Dec 2004 | A1 |
20040249532 | Kelly et al. | Dec 2004 | A1 |
20040252197 | Fraley et al. | Dec 2004 | A1 |
20040260786 | Barile | Dec 2004 | A1 |
20050001743 | Haemerle | Jan 2005 | A1 |
20050015186 | Kelly et al. | Jan 2005 | A1 |
20050015197 | Ohtsuji et al. | Jan 2005 | A1 |
20050015199 | Lokshin et al. | Jan 2005 | A1 |
20050021197 | Zimmerman et al. | Jan 2005 | A1 |
20050021199 | Zimmerman et al. | Jan 2005 | A1 |
20050024236 | Gosdin et al. | Feb 2005 | A1 |
20050027436 | Yoshikawa et al. | Feb 2005 | A1 |
20050027442 | Kelley et al. | Feb 2005 | A1 |
20050027447 | Hirose et al. | Feb 2005 | A1 |
20050027449 | Marsh | Feb 2005 | A1 |
20050033511 | Pechatnikov et al. | Feb 2005 | A1 |
20050038581 | Kapolka et al. | Feb 2005 | A1 |
20050038596 | Yang et al. | Feb 2005 | A1 |
20050043880 | Yamane et al. | Feb 2005 | A1 |
20050046594 | Taylor | Mar 2005 | A1 |
20050060070 | Kapolka et al. | Mar 2005 | A1 |
20050065678 | Smith et al. | Mar 2005 | A1 |
20050065717 | Meuller et al. | Mar 2005 | A1 |
20050068174 | Oesterling et al. | Mar 2005 | A1 |
20050075095 | Dillon | Apr 2005 | A1 |
20050080519 | Oesterling et al. | Apr 2005 | A1 |
20050090951 | Good | Apr 2005 | A1 |
20050093720 | Yamane et al. | May 2005 | A1 |
20050096811 | Bodin et al. | May 2005 | A1 |
20050096840 | Simske | May 2005 | A1 |
20050125117 | Breed | Jun 2005 | A1 |
20050131626 | Ignatin | Jun 2005 | A1 |
20050131628 | Peeters | Jun 2005 | A1 |
20050137763 | Watkins et al. | Jun 2005 | A1 |
20050137790 | Yamada et al. | Jun 2005 | A1 |
20050143882 | Umezawa | Jun 2005 | A1 |
20050221876 | Van Bosch et al. | Oct 2005 | A1 |
20050222760 | Cabral et al. | Oct 2005 | A1 |
20050273218 | Breed et al. | Dec 2005 | A1 |
20050288856 | Uyeki et al. | Dec 2005 | A1 |
20060022846 | Tummala | Feb 2006 | A1 |
20060055565 | Kawamata et al. | Mar 2006 | A1 |
20060058037 | Kenyon | Mar 2006 | A1 |
20060058950 | Kato et al. | Mar 2006 | A1 |
20060161347 | Charlot et al. | Jul 2006 | A1 |
20060178807 | Kato et al. | Aug 2006 | A1 |
20060200302 | Seko | Sep 2006 | A1 |
20060217849 | Obradovich et al. | Sep 2006 | A1 |
20080088480 | Rozum et al. | Apr 2008 | A1 |
20080106436 | Breed | May 2008 | A1 |
Number | Date | Country |
---|---|---|
10 2004 017091 | Oct 2005 | DE |
0973299 | Jan 2000 | EP |
1276088 | Jan 2003 | EP |
6276056 | Sep 1994 | JP |
8149029 | Jun 1996 | JP |
10-150477 | Jun 1998 | JP |
2000201104 | Jul 2000 | JP |
2000293788 | Oct 2000 | JP |
2001168743 | Jun 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 |
2003042797 | Feb 2003 | JP |
WO 9701940 | Jan 1997 | WO |
Number | Date | Country | |
---|---|---|---|
20080300775 A1 | Dec 2008 | US |