Source: http://www.google.com/patents/US20050143882?dq=6175559
Timestamp: 2014-03-08 13:03:11
Document Index: 240090555

Matched Legal Cases: ['art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 42', 'art 42', 'art 42', 'art 42', 'Application No. 2003']

Patent US20050143882 - Maintenance service supporting terminal, maintenance service supporting ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA maintenance service supporting terminal for supporting a maintenance service for a vehicle by using an OBD code is disclosed. The maintenance service supporting terminal includes: an OBD code obtaining unit for obtaining the OBD code from the vehicle, a vehicle diagnosing unit for diagnosing the vehicle...http://www.google.com/patents/US20050143882?utm_source=gb-gplus-sharePatent US20050143882 - Maintenance service supporting terminal, maintenance service supporting method, maintenance service supporting program, and OBD history dataAdvanced Patent SearchPublication numberUS20050143882 A1Publication typeApplicationApplication numberUS 10/934,860Publication dateJun 30, 2005Filing dateSep 3, 2004Priority dateSep 4, 2003Also published asEP1513108A2, EP1513108A3Publication number10934860, 934860, US 2005/0143882 A1, US 2005/143882 A1, US 20050143882 A1, US 20050143882A1, US 2005143882 A1, US 2005143882A1, US-A1-20050143882, US-A1-2005143882, US2005/0143882A1, US2005/143882A1, US20050143882 A1, US20050143882A1, US2005143882 A1, US2005143882A1InventorsHiroyuki UmezawaOriginal AssigneeHiroyuki UmezawaExport CitationBiBTeX, EndNote, RefManReferenced by (15), Classifications (11), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetMaintenance service supporting terminal, maintenance service supporting method, maintenance service supporting program, and OBD history dataUS 20050143882 A1Abstract A maintenance service supporting terminal for supporting a maintenance service for a vehicle by using an OBD code is disclosed. The maintenance service supporting terminal includes: an OBD code obtaining unit for obtaining the OBD code from the vehicle, a vehicle diagnosing unit for diagnosing the vehicle according to the obtained OBD code, and an estimating unit for estimating a fee for repairing the vehicle according to the diagnosis of the vehicle diagnosing unit. Images(18) Claims(29)
Next, in Step S109, it is decided whether to conduct vehicle inspection. This decision may be executed, for example, by allowing an operator to input whether to perform vehicle inspection via a display on a screen. The process proceeds to Step S113 if it is decided not to conduct the vehicle inspection (NO in Step S109). If it is decided to conduct the vehicle inspection (YES in Step S109), an OBD code related to the register is transmitted to the mechanic PDA. Accordingly, items to be input to the register, and code information corresponding to OBD codes are displayed in the mechanic PDA 9, as shown in FIG. 19. FIG. 19 shows check-boxes for marking inspection items and spaces for inputting OK or NG as the results. For example, the state of exhaust gas, which is one of the inspection items in the register, is shown in correspondence with the OBD code P0169 detected in the inspection, and its code information (here, air/fuel ratio defect). A mechanic inputs register information to the mechanic PDA 9 by referring to the displayed information, and transmits the register information to the maintenance service support terminal 10. After the maintenance service support terminal 10 receives the register information in Step S111, the register shown in FIG. 20 is printed (Step S112). The register shown in FIG. 20 is simplified by indicating the items shown in FIG. 20 and omitting other remaining items. The state of the exhaust gas corresponding to the detected OBD code is shown with a triangle mark for indicating �repair�. Then, the maintenance service support terminal 10 transfers the OBD code to the management server (Step S113), thereby completing the process. Next, the operation of obtaining (and printing) an estimate (see Step S107 in FIG. 14) is described in more detail with reference to a flowchart of FIG. 21. In Step S201, the maintenance estimating part 40 reads a received OBD code. In Step S202, the maintenance estimating part 40 extracts a repair procedure and component corresponding to the OBD code from the procedure/component database. In Step S203, the maintenance estimating part 40 extracts a repair procedure fee corresponding to the repair procedure from the repair procedure database. In Step S204, the maintenance estimating part 40 extracts a component fee corresponding to an extracted component from the component database. In Step S205, the maintenance estimating part 40 adds the total of the repair procedure fee and the component fee extracted in the Steps S203 and S204 to the estimate. The steps of S202 to S205 are repeated in correspondence with the number of received OBD code(s). In Step S206, the maintenance estimating part 40 determines whether there is any unprocessed OBD codes remaining. The Step S201 is executed if there is an unprocessed OBD code. In Step S207, the maintenance estimating part 40 prints out an estimate based on the OBD code(s) and the computed estimate. Next, the operation of printing a diagnosis sheet (see Step S108 in FIG. 14) is described in more detail with reference to a flowchart of FIG. 22. In Step S301 (corresponding to a diagnosis information generation step), the diagnosing part 42 extracts a comment corresponding to an OBD code from a comment database. The extracted comment is used for the malfunction information space 66 and the explanation space 67 (see FIG. 18). In Step S302, the diagnosing part 42 extracts history from a history database, and displays the extracted history to the operator. In Step S303, the diagnosing part 42 receives input of the information to be displayed in the history information space 68 from the operator. As an alternative of the input of the operator, a fixed format may be prepared beforehand to allow information read out from the history database to be inserted into the fixed format. In Step S304, the diagnosing part 42 prints the comment and input information from the operator to the diagnosis sheet, thereby completing the process. In consequence, according to the above-described embodiment of the present invention, regardless of manufacturer, a suitable repair procedure and/or component can be obtained, and applied to an estimate or an electronic register or the like. Furthermore, a static(s) of proportion defective for each vehicle type or component can be obtained by using an analyzing tool, to thereby serve to improve vehicle safety. Furthermore, since the management server 19 continuously stores history (lifelong history) of a vehicle, engine related components can be diagnosed in accordance with the history. Furthermore, the management server 19 is able to store vehicle data of various automobile manufacturers by connecting to respective automobile repair (e.g. maintenance, sheet metal) factories via a network. The vehicle data of the various automobile manufacturers has information of various vehicles uniformly expressed with OBD codes, and is based on the vehicles that are actually used. This information can be of valuable data for automobile manufacturers and automobile component manufacturers. For example, although an automobile manufacturer may be able to obtain data information of its own automobiles from its affiliated automobile dealers or the like, it is difficult for the automobile manufacturer to obtain such information of other automobile manufacturers. Furthermore, performance comparison with rival manufacturers can be performed by applying the OBD codes stored in the management server 19 to a commercially available analyzing tool (e.g. �Dr. Sum� by Tsubasa System Co. Ltd.). Furthermore, property analysis of vehicles can be performed, for example, analyzing failure rate of an automobile of a same type of a same manufacturer used in different regions. Furthermore, since the data is obtained from actually used automobiles, the data is more useful analysis data compared to data obtained merely from, for example, inspections of an automobile plant and test-drives on a circuit. Furthermore, a more efficient analysis can be performed by further obtaining data, such as, engine speed, engine load, coolant temperature, and/or speed of the vehicle. Further, the present invention is not limited to these embodiments, but various variations and modifications may be made without departing from the scope of the present invention. The present application is based on Japanese Priority Application No. 2003-312345 filed on Sep. 4, 2003, with the Japanese Patent Office, the entire contents of which are hereby incorporated by reference. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7263417 *Sep 29, 2004Aug 28, 2007International Truck Intellectual Property Company, LlcUser adaptive automated pre-trip inspection systemUS7945358Aug 18, 2006May 17, 2011Environmental Systems Products Holdings Inc.System and method for testing the integrity of a vehicle testing/diagnostic systemUS8019503 *Jun 28, 2007Sep 13, 2011Innova Electronics CorpAutomotive diagnostic and remedial processUS8032419 *Sep 11, 2009Oct 4, 2011Innova Electronics CorporationMethod of providing diagnostic information in connection with the sale of pre-owned vehiclesUS8068951 *Mar 21, 2008Nov 29, 2011Chen Ieon CVehicle diagnostic systemUS8166353Aug 4, 2008Apr 24, 2012Denso CorporationMemory management apparatusUS8306687Nov 10, 2009Nov 6, 2012Innova Electronics, Inc.Method of diagnosing a vehicle having diagnostic dataUS8355837May 16, 2011Jan 15, 2013Envirotest Systems Holdings Corp.System and method for testing the integrity of a vehicle testing/diagnostic systemUS8370018 *Mar 1, 2010Feb 5, 2013Innova Electronics, Inc.Automotive diagnostic processUS20090276115 *Jul 13, 2009Nov 5, 2009Chen Ieon CHandheld Automotive Diagnostic Tool with VIN Decoder and Communication SystemUS20100174446 *Mar 1, 2010Jul 8, 2010Keith AndreasenAutomotive diagnostic processUS20110015815 *Sep 23, 2010Jan 20, 2011Bertness Kevin IBattery tester for electric vehicleUS20120143787 *Dec 22, 2011Jun 7, 2012Aaron David Trent NeedhamSystem and method for creating and using energy credits derived from the transportation industry while maintaining green certificationUS20120290106 *May 7, 2012Nov 15, 2012Still GmbhMethod for the management of industrial trucks and an industrial truckWO2007001914A2 *Jun 16, 2006Jan 4, 2007Ieon C ChennMethod of providing diagnostic information in connection with the sale of pre-owned vehicles* Cited by examinerClassifications U.S. Classification701/31.4International ClassificationG06Q30/06, G06Q50/10, G06Q50/00, G07C5/08, B60S5/00, G07C5/00Cooperative ClassificationG07C5/008, G07C5/085European ClassificationG07C5/00T, G07C5/08R2Legal EventsDateCodeEventDescriptionSep 3, 2004ASAssignmentOwner name: TSUBASA SYSTEMS CO., LTD., JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UMEZAWA, HIROYUKI;REEL/FRAME:015774/0645Effective date: 20040820RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google