A trip data management and display system for a vehicle. The system includes a processor, a memory, a user-interface and a display. During a trip traveled by the vehicle, the processor receives data from one or more systems or components. The processor receives input via the user-interface to associate a category and a filename with the received data for storage in the memory. The stored data may then be retrieved for display upon the display of the vehicle. The trip traveled by the vehicle is predefined according to user-settable parameters or is automatically determined based on vehicle characteristics. Instantaneous data corresponding to a trip currently being traveled by the vehicle may also be displayed on the display adjacent to the stored data from memory. The data stored may be managed by a user to associate it with different or multiple categories or to delete particular stored data.
|
10. A method for managing data corresponding to a vehicle, the method comprising:
receiving, by a processor, first trip data that was measured during a first trip of the vehicle until a desired end-of-trip parameter has been met for the first trip, and a second trip data that was measured during a second trip of the vehicle until the desired end-of-trip parameter has been met for the second trip;
storing, in a memory coupled to the processor, the first trip data and the second trip data;
automatically categorizing, by the processor, the first trip data that was measured during the first trip into a respective category of a plurality of categories, each category of the plurality of categories having a s plurality of trips, the plurality of trips having a same trip parameter, the same trip parameter corresponding to at least one of a distance traveled, a redetermined amount of time measured for a trip or a predetermined vehicle seed;
associating, by the processor, a first filename with the first trip data;
determining, by the processor, that the second trip data corresponds to the respective category;
associating, by the processor, a second filename with the second trip data;
determining, by the processor, output data based on at least a portion of the first trip data or the second trip data; and
displaying, on a display coupled to the processor, the output data.
16. A system for management of trip data for a vehicle, comprising:
an input device configured to receive data indicating a desired end-of-trip parameter;
a processor coupled to the input device and configured to:
receive first trip data that was measured from a start location of a first trip until the desired end-of-trip parameter has been met for the first trip and second trip data that was measured from a start location of the second trip until the desired end-of-trip parameter has been met for the second trip,
automatically categorize the first trip data that was measured from the start location of the first trip into a respective category of a plurality of categories, each category of the plurality of categories having a plurality of trips, the plurality of trips having a same trip parameter, the same trip parameter corresponding to at least one of a distance traveled, a predetermined amount of time measured from the start location to desired end-of-trip parameter or a predetermined vehicle speed,
assign the category and a first filename to the first trip data,
assign the category and a second filename to the second trip data, and
calculate output data based on at least one of the first trip data or the second trip data;
a memory coupled to the processor and configured to store the first trip data and the second trip data; and
a display coupled to the processor and configured to display the output data.
1. A method for managing data of a vehicle, the method comprising:
acquiring, by a processor, first trip data that was measured from a start location of a first trip until an end location of the first trip, and second trip data that was measured from a start location of a second trip until an end location of the second trip;
automatically categorizing, by the processor, the first trip data that was measured from the start location of the first trip until the end location of the first trip into a respective category of a plurality of categories, each category of the plurality of categories having a plurality of trips, the plurality of trips having a same trip parameter, the same trip parameter corresponding to at least one of a distance traveled, a predetermined amount of time measured from a start location to an end location or a predetermined vehicle speed;
determining, by the processor, a first filename for the first trip data;
determining, by the processor, that the second trip data corresponds to the respective category;
determining, by the processor, a second filename for the second trip data;
storing, in a memory coupled to the processor, a first association of the first trip data, the respective category and the first filename;
storing, in the memory, a second association of the second trip data, the respective category and the second filename; and
displaying, on a display coupled to the processor, information corresponding to at least a portion of the first trip data or the second trip data based on a selection of the respective category and at least one of the first association or the second association.
2. The method of
3. The method of
4. The method of
determining, by the processor, that the second trip has concluded when a desired end-of-trip parameter has been met for the second trip; and
stopping, by the processor, the acquiring of the second trip data when the second trip has been determined to be concluded.
5. The method of
6. The method of
7. The method of
8. The method of
disregarding the first trip data if a distance of the first trip is less than a predetermined distance, or
disregarding the second trip data if a distance of the second trip is less than the predetermined distance.
9. The method of
11. The method of
12. The method of
13. The method of
14. The method of
receiving, from the input device, data requesting that the respective category be created,
receiving, by the processor, the data requesting that the respective category be created, and
adding, by the processor, the respective category to the list of available categories in response to receiving the data requesting that the respective category be created.
15. The method of
17. The system of
18. The system of
19. The system of
|
|||||||||||||||||||||||||||
This application claims the benefit and priority of U.S. Provisional Application No. 61/624,007, filed on Apr. 13, 2012, the entire contents of which are hereby incorporated by reference herein.
1. Field
The present invention relates generally to data management systems and improvements thereof. More particularly, the present invention relates to travel or trip data management systems and methods for use in an automobile or other vehicle and improvements thereof.
2. Description of the Related Art
As vehicle systems become increasingly computerized and electronically controlled, vehicle performance and driving characteristics have become progressively more obscured from the drivers operating them. For example, performance tuning and other operational features for such vehicles are now difficult for the average consumer to understand and tweak or modify since underlying software or electronic-based systems can significantly impact these processes. Many times, only enthusiasts with compatible computer hardware and software are able to interpret and understand the specific settings (e.g., fuel maps, etc.) or characteristics of an automobile in order to modify vehicle parameters and to merely gain additional insight on efficient manners for operating the vehicle. Further exacerbating this issue is the recent increase in popularity of hybrid vehicles or other alternative fuel source vehicles with complex interrelationships among a variety of onboard vehicle systems.
Automobile consumers are also becoming increasingly more cost-conscious when purchasing vehicles, particularly in regards to fuel or energy efficiency, due in large part to the rapidly growing cost of vehicle fuel. Similarly, many drivers are becoming more interested in maximizing their distance traveled at a minimum of fuel consumed, but oftentimes have limited manners in which to modify or ascertain efficient driving habits to achieve such goals. Even outside the realm of fuel efficiency, automobile drivers appreciate feedback on vehicle performance without requiring extensive knowledge about the vehicle systems or manual and time-consuming calculations based on available vehicle data. A system or method for storing vehicle data that can be easily and simply provided to users of automobiles or other vehicles would thus be desired.
Ideally, such a system or method would be inexpensive to manufacture and integrate with systems or components of the vehicle. In addition, such a system or method would ideally allow for a variety of performance or other vehicle characteristics to be shared with the user of the vehicle. The system or method would ideally be flexible to allow users the ability to customize or manipulate data or statistical information to only that information desired by that particular user. Moreover, since such performance or other vehicle characteristics can be skewed as a result of limited data sets, resulting in information that may be unreliable, such a system or method would ideally be capable of discerning which data should be used for particular user showcases or statistic generation such that users are not presented with inaccurate or misleading information.
A system or method for managing and/or displaying data or statistical information relating to a vehicle or automobile is described. In one embodiment, a method for managing data of a vehicle may include the steps of acquiring, using a processor of the vehicle, trip data corresponding to the vehicle, determining, using the processor, a category for the trip data, determining, using the processor, a filename for the trip data, storing the trip data in a memory of the vehicle, the stored trip data associated with the category and the filename, determining, using the processor, a viewing format for information based on at least a portion of the trip data, and displaying the information on a display of the vehicle in the viewing format.
In another embodiment, a method for managing data corresponding to a vehicle may include the steps of receiving first trip data at a processor of the vehicle, the first trip data corresponding to at least one characteristic of the vehicle during a first trip made by the vehicle, storing the first trip data in a memory of the vehicle, associating, using the processor, a category with the first trip data, associating, using the processor, a filename with the first trip data, determining, using the processor, at least a portion of the first trip data to be displayed on a display of the vehicle, receiving second trip data at the processor, the second trip data corresponding to at least one characteristic of the vehicle during a second trip currently being made by the vehicle, and displaying the at least a portion of the first trip data and at least a portion of the second trip data adjacent to one another on a display of the vehicle.
In still another embodiment, a system for management of trip data for a vehicle may include a processor configured to receive data relating to the vehicle and assign a category and a filename to the received data. A memory is connected with the processor and configured to store the received data. A user-interface component is connected with the processor and is configured to be manipulated by a user of the vehicle. A display is connected with the processor and configured to display a statistic relating to the vehicle in a display format selected by the user of the vehicle via manipulation of the user-interface component, the statistic calculated by the processor based upon the received data.
In another embodiment, a method for automatically providing a filename for a second trip based on information collected from a first trip. The method includes enabling, using a processor of the vehicle, an on-board user-activated GPS feature for tracking a starting location and an ending location of a vehicle, and storing a first trip data in a memory of the vehicle, the first trip data corresponding to at least one characteristic of the vehicle during a first trip made by the vehicle. The method also includes determining, using the processor, a first category for the first trip data, determining, using the processor, a first filename for the first trip data, and automatically determining, using the processor, a second filename based on the starting location and the ending location of a second trip, the first category, and the first filename.
Other systems, methods, features, and advantages of the present invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present invention, and be protected by the accompanying claims. Component parts shown in the drawings are not necessarily to scale, and may be exaggerated to better illustrate the important features of the present invention. In the drawings, like reference numerals designate like parts throughout the different views, wherein:
Referring to
In step 110, the trip management system 100 determines whether to operate in a trip data generation mode or a trip data viewing mode. This may involve querying a user of the vehicle via a message or indicator on a display within a cabin of the vehicle. The user may respond by interfacing with one or more components of the trip management system 100 (e.g., pressing a corresponding location of a touch-sensitive display, utilizing knobs or buttons, speaking to a microphone connected with voice-recognition software, etc.). Depending upon the user's response, the trip management system 100 will either begin data generation or data viewing, as discussed in greater detail herein. In certain embodiments, the trip management system 100 may be capable of both displaying trip data and generating trip data simultaneously. In an alternative embodiment, the trip management system 100 may automatically begin trip data generation or trip data viewing as a default mode upon start-up of the vehicle. In yet another alternative embodiment, the trip management system 100 may not generate trip data or display trip data, thus operating in an OFF or sleep mode. Such a mode may be desirable for a user of the vehicle who does not wish to store any data regarding a particular trip and does not wish to view trip data at that time.
If the trip management system 100 determines trip data generation is desired, operation proceeds to step 115. In step 115, the trip management system 100 operates by acquiring trip data for the vehicle. The trip management system 100 may interface with one or more sensors or other electronics coupled with the vehicle for determining a variety of vehicle characteristics. For example, the processor of the trip management system 100 may communicate with an engine control unit (“ECU”) of the vehicle for acquiring the vehicle fuel efficiency (e.g., miles per gallon), speed, etc. as the vehicle travels from one location to another. Any of a variety of vehicle characteristics may be acquired by the trip management system 100 for a particular vehicle trip.
The acquisition of trip data in step 115 continues until the trip management system 100 determines that a particular trip for the vehicle has concluded. In step 120, if the trip management system 100 determines that the particular trip for the vehicle has not yet concluded, acquisition of trip data via step 115 continues. This may occur, for example, until a user indicates to the trip management system 100 that the vehicle has arrived at the desired destination, such as by pressing a trip reset button or by manipulating any of a variety of other user-interface components (e.g., an element of a touch screen display). In another example, if the vehicle is equipped with a navigation system or components, the trip management system 100 may automatically determine that the particular trip for the vehicle has concluded once the vehicle has arrived at a destination of the navigation system. In still another example, the trip management system 100 may automatically determine that the particular trip for the vehicle has concluded based on a characteristic of the vehicle, such as shutdown of the engine, removal of a key from an ignition switch, remaining in a parked position or gear for a predetermined period of time, etc.
The conclusion of the particular trip for the vehicle in step 120 may also be based upon one or more user-defined parameters. For example, the user may interface with the trip management system 100 to set a specific time period for the acquisition of trip data. Such acquisition may be useful for determining fuel efficiency (e.g., miles per gallon, miles per kilowatt-hour, kilometers per liter, etc.), maximum speed, maximum torque, distance traveled, etc., for example, at a drag strip or while on a dynamometer. A variety of user-defined parameters may be utilized or combined, for example, data acquisition may occur until a particular speed is obtained or a particular number of miles are traversed.
Once the trip management system 100 determines the particular vehicle trip has completed, operation continues to step 125 where the trip data acquired in step 115 is analyzed or otherwise utilized by the processor of the trip management system 100. In step 125, a variety of statistics or information regarding the trip data is determined. The processor of the trip management system 100 utilizes the trip data acquired in step 115 to determine such statistics or information. For example, this may include a maximum vehicle speed for the vehicle trip, an average miles-per-gallon value for the trip, an average vehicle speed for the vehicle trip, a maximum amount of torque or horsepower for a particular engine RPM, etc.
In step 130, the trip management system 100 determines a trip category and a trip name for the trip data acquired in step 115 and the trip statistics determined in step 125. In one embodiment, the trip category may be selected from among a plurality of predetermined categories or may be a newly generated category. In one example, the trip management system 100 may have already stored default categories titled “Work Trips,” “Fun Trips,” “Long Trips,” and “Short Trips.” In step 130, a user of the vehicle may select the category “Fun Trips” from a drop-down menu or other listing of available categories already stored in the memory of the trip management system 100 for the particular trip determined to be concluded in step 120. In certain embodiments, a user may be permitted to assign multiple categories to a single set of trip data. Categories may also have particular parameters assigned to them such that trip data meeting those particular parameters are automatically associated with such categories. For example, if a category titled “Short Trips” has a parameter defining a trip less than 10 miles, then acquired trip data for a trip less than 10 miles in length will be automatically associated with the category “Short Trips.” Any of a variety of parameters may be established (e.g., time of day, day of week, particular user of the vehicle, etc).
The titles of the various categories for selection by a user may be predetermined and stored in the memory of the trip management system 100. The trip management system 100 may also allow the user of the vehicle to edit stored categories, delete certain categories or create new categories and title them as desired. For example, the trip management system 100 may not have any predetermined categories stored in the memory or may not have a particular category desired by the user. Thus, the user of the vehicle may instead interface with the trip management system 100 to create a new category (e.g., Trips to Grandparents House) and associate the trip data acquired in step 115 with the newly created category. In one embodiment, a default category may be determined or assigned for the trip data unless otherwise specified by the user of the vehicle. Such automatic categorizing provides increased ease-of-use for the user of the vehicle who would otherwise be required to manually categorize every set of acquired trip data.
In addition to determination of a trip category for the trip data, the trip management system 100 also determines a trip name for the set of trip data, since a particular category of trip data in the trip management system 100 may have a number of different sets of trip data associated with the category (e.g., there may be multiple different trips categorized as “short trips”). The trip management system 100 may use the trip data or the navigation system (i.e., the GPS data), the trip date and/or the time of day to determine or suggest an appropriate trip name. Example 1: Trip from user defined “home” to “work”=“Morning Commute”. Example 2: Trip from user defined “home” to input address=“Home to <street, city>”. Example 3: Driving at race track defined in the navigation system “<race track location>”. Example 4: Aug. 1, 2012 Trip. The use of the GPS data is enabled by the user of the vehicle to respect privacy concerns. In one embodiment, a default name may be determined or assigned for the trip data unless otherwise determined by the trip management system 100 or specified by the user of the vehicle. This default name may automatically choose the category determined and append a sequentially assigned numeral to the end. Thus, each trip data assigned to a particular category would be automatically assigned a name with a different numeral (e.g., category1_trip1, category1_trip2, etc.) unless otherwise specified by the user of the vehicle. The default name can also be the date at the start of the trip. Such automatic naming or automatic determination provides increased ease-of-use for the user of the vehicle who would otherwise be required to manually assign names for every set of acquired trip data.
After a category and name is determined for the trip data, the trip data acquired in step 115 and any associated data statistics determined in step 125 is stored in the memory of the trip management system 100 in step 135 with association to the category and name. In an alternative embodiment, only the trip data acquired in step 115 may be stored in the memory in step 135 without any trip data statistics from step 125. For example, step 125 may be eliminated in an alternative embodiment and any statistics or information regarding a particular set of trip data stored in memory may be determined from the stored trip data just prior to viewing of the trip data, as discussed in greater detail herein. In one embodiment, the trip management system 100 may permit external access to the data stored in step 135 (e.g., via a USB or wireless interface) so that such data can be exported to a device separate from the vehicle, such as a personal computer or diagnostics system. This data may be exported in a variety of file formats, for example as plain text, as a spreadsheet, as a database, etc.
After storage with category and name association in step 135 is complete, operation returns to step 110 where the trip management system 100 may again determine whether generating new trip data or viewing of previously stored trip data is desired, as previously discussed. If the trip management system 100 determines that trip data viewing is desired, operation continues to step 150. The processor of the trip management system 100 may thus interface with the memory of the trip management system 100 in order to display all or a portion of trip data stored as part of the trip management system 100, as described in greater detail herein.
In step 150, the trip management system 100 determines the particular trip data desired for display to the user of the vehicle. This determination may be made by requiring user input, as discussed in greater detail herein, or may initially display default data to the user. The desired trip data may be data previously acquired in step 115 of the trip management system and/or trip data statistics determined in step 125 of the trip management system. In certain embodiments, the trip management system 100 may determine various trip data statistics based upon trip data acquired in step 115 at the time a user wishes to view the data instead of determining such statistics in step 125 and previously storing such statistics in step 135. In step 155, the trip management system 100 determines the viewing format for display of the desired trip data/statistics, for example, a bar graph, a numerical indicator, etc. In step 160, the trip management system 100 displays the trip data/statistics to the user of the vehicle based on the determined desired data for viewing in step 150 and the determined viewing format in step 155. The display may be any of a variety of appropriate viewing devices, for example, a liquid crystal display (“LCD”) screen positioned in a dash compartment of the vehicle. The display may show only previously stored data on the display of the vehicle or may display both previously stored data and instantaneous (i.e. current) data for the vehicle adjacent or side-by-side with one another, as discussed in greater detail herein. After the user is done viewing the data, they may interface with the trip management system 100 in order to return operation to step 110.
For example, for the first stored category 210, the trip data files 215 have been associated therewith. For the second stored category 220, the trip data files 225 have been associated therewith. For the third stored category 230, the trip data files 235 have been associated therewith. Any number of categories may be created and stored as part of the trip management system 200. Although only three stored categories (210, 220, 230) are shown on the screen in
The trip management screen of the trip management system 200 also includes a category entry box 250 for allowing a user to type or otherwise select a trip category for a current set of trip data (e.g., trip data acquired in step 115 of
In addition to selecting a category for a current set of trip data, the trip management screen of the trip management system 200 also includes a name entry box 270 for allowing a user to type a name for the particular set of trip data. In certain embodiments, the user may leave the name entry box 270 blank and the trip management system 200 will automatically define a name for the trip data, for example, as previously discussed for
The trip display screen of the trip management system 300 includes a category selection box 310 and an associated drop-down button 315. The user of the vehicle may press or manipulate the drop-down button 315 to see a list of some or all of the previously stored categories for trip data of the trip management system 300. A scroll bar may be utilized for displaying stored categories that exceed the available screen space of the list. In addition, in one embodiment, a grouping of all categories together (e.g., “All Categories”) may be selected for viewing overall travel characteristics for the vehicle without being specifically narrowed to a particular category. The display screen also includes a data type selection box 320 and an associated drop-down button 325. The user of the vehicle may press or manipulate the drop-down button 325 to see a list of some or all of the available types of data or information they may receive visual feedback on (e.g., miles per gallon, speed, time of travel, etc). Similar to the above, a scroll bar may be utilized for displaying data types that exceed the available screen space of the list. The trip management system 300 looks up trip data corresponding to the category selected in the category selection box 310 and the data type selected in the data type selection box 320 for display to the user, as discussed below. This trip data may be trip data acquired directly during travel (e.g., step 115 of
For example, if the user selects “All Categories” to be displayed in the category selection box 310 and selects fuel efficiency (e.g. “MPG”) information in the data type selection box 320, a first graph 330 showing fuel efficiency data for “All Categories” 335 combined is displayed. In addition, fuel efficiency information for each stored category may also be displayed separately when choosing “All Categories.” For example, graph 340 corresponds to fuel efficiency data for “Category 1” 345 and graph 350 corresponds to fuel efficiency information for “Category 2” 355. A next page button 360 allows a user to page across multiple display pages if more categories or data exist than can fit on one display screen. The user of the vehicle can also select the desired display or viewing format for the graphs (330, 340, 350) by pressing or manipulating the drop-down button 375 associated with a display or viewing format selection box 370. Any of a variety of display or viewing formats may be chosen, for example, bar graphs, line graphs, numerals, pie charts, etc. In certain embodiments, trip data that does not exceed a predetermined threshold for trip length (e.g., a trip less than 0.01 km) may be ignored or disregarded and thus not shown or utilized for trip data statistics or calculations. For example, if fuel economy data or statistics would misrepresent or would inaccurately demonstrate vehicle fuel efficiency if trips of less than 0.01 km were factored in, data associated with such trips may be ignored by the trip management system 300 and not displayed or otherwise utilized.
Steps described for one of the embodiments above may additionally or alternatively be incorporated into any of the other embodiments. Various steps may be performed or executed in different orders or removed entirely in an alternative embodiment. An alternative embodiment may add new steps. The various illustrative logical blocks, modules, and algorithm steps described in connection with the examples disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed apparatus and methods. Likewise, management screens or display screens may be configured or oriented differently from the specific embodiments shown above in order to perform the same, similar, different, reduced, or additional functions or features.
The steps of a method or algorithm described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). The ASIC may reside in a wireless modem. In the alternative, the processor and the storage medium may reside as discrete components in the wireless modem.
Exemplary embodiments of the invention have been disclosed in an illustrative style. Accordingly, the terminology employed throughout should be read in a non-limiting manner. Although minor modifications to the teachings herein will occur to those well versed in the art, it shall be understood that what is intended to be circumscribed within the scope of the patent warranted hereon are all such embodiments that reasonably fall within the scope of the advancement to the art hereby contributed, and that that scope shall not be restricted, except in light of the appended claims and their equivalents.
Sitarski, Nicholas S., Gregg, Christopher
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 3983372, | Feb 03 1975 | Chevron Research Company | Apparatus and method for a digital readout of distance traveled, fuel consumed and miles per gallon of a moving motor vehicle |
| 6111498, | Dec 09 1997 | THOR INVESTMENTS, LLC | Trip computer read-out on rearview camera screen |
| 6278921, | Sep 16 1996 | Minorplanet Limited | Transferring accumulated data from vehicles |
| 6691025, | May 04 1999 | SSI Technologies, Inc. | Fuel optimization system with improved fuel level sensor |
| 6988033, | Aug 06 2001 | Verizon Patent and Licensing Inc | Internet-based method for determining a vehicle's fuel efficiency |
| 7512486, | Jun 29 2005 | Intel Corporation | Fuel efficient navigation system |
| 7889063, | Jan 09 2008 | Toyota Motor Corporation | Customizable vehicle information display |
| 7954579, | Feb 04 2008 | TURNTIDE TECHNOLOGIES INC | Adaptive control strategy and method for optimizing hybrid electric vehicles |
| 8099208, | Aug 01 2008 | Denso Corporation; Toyota Jidosha Kabushiki Kaisha | Driving diagnosis apparatus and driving diagnosis system |
| 20040008109, | |||
| 20040093155, | |||
| 20060200309, | |||
| 20070106468, | |||
| 20080125958, | |||
| 20100063721, | |||
| 20100318293, | |||
| 20110112717, | |||
| 20110118976, | |||
| 20110153175, | |||
| 20110205044, | |||
| 20110238257, | |||
| 20110251782, | |||
| 20110264317, | |||
| 20120130630, | |||
| EP2343208, | |||
| JP11064171, | |||
| JP2003331380, | |||
| JP2004045180, | |||
| JP2006003147, | |||
| JP2009129074, | |||
| JP2010083276, | |||
| JP2011117838, | |||
| JP58020538, | |||
| KR100591043, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Jul 31 2012 | SITARSKI, NICHOLAS S | TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028788 | /0972 | |
| Aug 13 2012 | GREGG, CHRISTOPHER | TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028788 | /0972 | |
| Aug 14 2012 | Toyota Motor Engineering & Manufacturing North America, Inc. | (assignment on the face of the patent) | / | |||
| Jul 17 2017 | TOYOTA MOTOR ENGINEERING & MANUFACTURING NORTH AMERICA, INC | Toyota Jidosha Kabushiki Kaisha | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 043048 | /0010 |
| Date | Maintenance Fee Events |
| Sep 30 2020 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Dec 18 2024 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Date | Maintenance Schedule |
| Jul 25 2020 | 4 years fee payment window open |
| Jan 25 2021 | 6 months grace period start (w surcharge) |
| Jul 25 2021 | patent expiry (for year 4) |
| Jul 25 2023 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Jul 25 2024 | 8 years fee payment window open |
| Jan 25 2025 | 6 months grace period start (w surcharge) |
| Jul 25 2025 | patent expiry (for year 8) |
| Jul 25 2027 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Jul 25 2028 | 12 years fee payment window open |
| Jan 25 2029 | 6 months grace period start (w surcharge) |
| Jul 25 2029 | patent expiry (for year 12) |
| Jul 25 2031 | 2 years to revive unintentionally abandoned end. (for year 12) |