Vehicle information history management method and vehicle information history management system

The vehicle information history management system addresses the issue of erased diagnostic codes by associating vehicle information with a chassis number for comprehensive storage and retrieval, improving the accuracy of vehicle condition assessment.

JP7869549B2Active Publication Date: 2026-06-03S BRAND MANAGEMENT CO LTD

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
S BRAND MANAGEMENT CO LTD
Filing Date
2020-12-11
Publication Date
2026-06-03

AI Technical Summary

Technical Problem

Existing vehicle appraisal systems face challenges in accurately obtaining vehicle information due to the erasure of trouble codes from on-board diagnostic devices, making it difficult to assess the repair history and condition of vehicles.

Method used

A vehicle information history management system that receives, stores, and retrieves vehicle information via a network from multiple service providers, associating it with a unique chassis number for cumulative storage and retrieval, allowing for comprehensive vehicle history tracking.

Benefits of technology

Enhances the accuracy of vehicle information retrieval, enabling improved assessment of vehicle malfunctions and conditions by maintaining a historical record of services and fault information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007869549000001
    Figure 0007869549000001
  • Figure 0007869549000002
    Figure 0007869549000002
  • Figure 0007869549000003
    Figure 0007869549000003
Patent Text Reader

Abstract

To provide a vehicle information history management method configured to easily improve the accuracy of obtaining information on a failure, or the like, of a vehicle, and a vehicle information history management system.SOLUTION: A vehicle information history management system 1 includes: a receiving processing unit 211 which receives a frame number N of an automobile C to be subjected to a service, and vehicle information D which is information on the automobile C or information on the service in association with each other, from terminal devices T disposed in stores S which provide the automobile-related service, via a network 3; a storage unit 22; a storage processing unit 212 which stores the received frame number N and the vehicle information D in association with each other in a cumulative manner on the storge unit 22; and a browsing processing unit 213 which transmits, on receipt of a request for the vehicle information D corresponding to the frame number N from one of the terminals T over the network 3, the vehicle information D cumulatively stored in association with the frame number N, to the one terminal T over the network 3.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a vehicle information history management method and a vehicle information history management system for managing the history of vehicle information of automobiles.

Background Art

[0002] Conventionally, a used car appraisal support system that obtains an appraisal deduction value based on failure information read from a failure diagnosis device mounted on an appraisal target vehicle is known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] By the way, the trouble code (DTC) stored in the on-board diagnostic (OBD) device is erased after necessary maintenance or repair is performed. In addition, there is a possibility that the trouble code (DTC) may be erased by removing the battery or using a scan tool (see, for example, Non-Patent Document 1). Therefore, past failure information that has been erased cannot be read from the failure diagnosis device of the appraisal target vehicle, and the failure information read from the failure diagnosis device is insufficient as information for appraising the appraisal target vehicle. In addition to used car appraisals, there may be cases where it is desired to know the repair history of an automobile, etc.

[0006] The object of the present invention is to provide a vehicle information history management method and a vehicle information history management system that facilitate the improvement of the accuracy of obtaining information regarding vehicle malfunctions and other related issues. [Means for solving the problem]

[0007] The vehicle information history management method according to the present invention includes a receiving process step of receiving vehicle information, which is the chassis number of an automobile subject to a service and information relating to the automobile or the service, from terminal devices installed in each of a plurality of stores that provide automobile-related services, via a network; a storage process step of associating the received chassis number and the vehicle information and accumulating them in a storage unit; and a viewing process step of, when a request for the vehicle information corresponding to the chassis number is received via the network from any of the plurality of terminal devices, transmitting the vehicle information accumulated and associated with the chassis number to any of the terminal devices via the network.

[0008] Furthermore, the vehicle information history management system according to the present invention includes a receiving processing unit that receives vehicle information, which is information relating to the vehicle or the service, from terminal devices installed in each of a plurality of stores that provide automobile-related services, via a network, associating the chassis number of the vehicle subject to the service with the vehicle information; a storage unit; a storage processing unit that cumulatively stores the received chassis number and the vehicle information in association with each other in the storage unit; and a browsing processing unit that, when a request for the vehicle information corresponding to the chassis number is received via the network from any of the plurality of terminal devices, transmits the cumulatively stored vehicle information associated with the chassis number to any of the terminal devices via the network.

[0009] According to these methods and systems, when an automobile-related service is received at a store, the vehicle identification number (VIN) and vehicle information of the vehicle being serviced are received via the network, and the VIN and vehicle information are associated and cumulatively stored in a memory unit. When a request for vehicle information corresponding to a VIN is received via the network, the cumulatively stored vehicle information associated with the VIN is transmitted via the network to the requesting terminal device. Since the VIN does not change for a single vehicle, the vehicle information obtained from terminal devices at multiple stores is stored in the memory unit in association with the VIN, thereby accumulating a history of past vehicle information for the vehicle. Furthermore, since this accumulated history of vehicle information is transmitted upon request, it becomes easier to improve the accuracy of obtaining information regarding vehicle malfunctions, etc.

[0010] Furthermore, it is preferable that the automobile is equipped with a fault diagnosis device, the terminal device is capable of acquiring fault information stored in the fault diagnosis device of the automobile, and the vehicle information includes the fault information.

[0011] This configuration allows for the storage of fault information history obtained from the fault diagnostic device, associated with the vehicle identification number, and to retrieve it as needed upon request.

[0012] Furthermore, the service preferably includes at least one of the following: the sale of automotive parts, the sale of automotive consumables, and the sale of automotive repair supplies. The terminal device is capable of accepting orders for at least one of the following items: automotive parts, automotive consumables, and automotive repair supplies. Preferably, the vehicle information includes information indicating an order for the at least one item received by the terminal device.

[0013] With this configuration, when an order is placed for automotive parts, automotive consumables, or automotive repair supplies in connection with the sale of automotive parts, automotive consumables, or automotive repair supplies, information indicating the order of those items can be cumulatively stored as vehicle information. Since information indicating the order of automotive parts, automotive consumables, or automotive repair supplies can be used as information to infer vehicle malfunctions, etc., it can be used as information related to vehicle malfunctions, etc.

[0014] Furthermore, it is preferable to further include an order processing step that performs order processing based on the order information received in the receiving processing step.

[0015] With this configuration, stores can cumulatively store vehicle information of the target automobile in the storage unit by ordering goods using a terminal device.

[0016] Furthermore, it is preferable that the memory processing step further stores date information indicating the date in association with the chassis number and the vehicle information in the memory unit.

[0017] This configuration allows us to know the date on which the vehicle information was obtained, thus providing clues about the vehicle's condition.

[0018] Furthermore, the aforementioned services preferably include at least one of the following: automobile maintenance, automobile repair, automobile inspection, automobile inspection and registration system inspection, and automobile appraisal, and the aforementioned vehicle information preferably includes information indicating the results of the aforementioned services.

[0019] Information showing the results of automobile maintenance, automobile repair, automobile inspection, automobile inspection and registration system inspections, and automobile appraisals is suitable as vehicle information because it provides important clues for evaluating the condition of an automobile.

[0020] In addition, it is preferable that at least one of a service station, an automobile supplies store, an automobile dealership, a repair shop, an automobile inspection and registration office, and a used car dealership is included in the plurality of stores.

[0021] A service station, an automobile supplies store, an automobile dealership, a repair shop, an automobile inspection and registration office, and a used car dealership are suitable as stores where a terminal device is provided because they are places where it is easy to obtain important vehicle information for evaluating the condition of an automobile.

Advantages of the Invention

[0022] With a vehicle information history management method and a vehicle information history management system having such a configuration, it is easy to improve the accuracy of obtaining information regarding malfunctions and the like of an automobile.

Brief Description of the Drawings

[0023] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a vehicle information history management system using a vehicle information history management method according to an embodiment of the present invention. [Figure 2] FIG. 2 is a flowchart showing an example of the operation of the vehicle information history management system shown in FIG. 1. [Figure 3] FIG. 3 is a flowchart showing an example of the operation of the browsing processing unit shown in FIG. 1. [Figure 4] FIG. 4 is an explanatory diagram in tabular form showing an example of data stored in the storage unit.

Modes for Carrying Out the Invention

[0024] Hereinafter, embodiments according to the present invention will be described based on the drawings. In each figure, components denoted by the same reference numerals are the same components, and their description will be omitted. FIG. 1 is a block diagram showing an example of the configuration of a vehicle information history management system using a vehicle information history management method according to an embodiment of the present invention.

[0025] The vehicle information history management system 1 shown in FIG. 1 includes a server device 2 and terminal devices T1~T5 and includes。

[0026] Terminal device T1 is located at service station S1, terminal device T2 is located at auto parts store S2, terminal device T3 is located at car dealership S3, terminal device T4 is located at repair shop S4, terminal device T5 is located at vehicle inspection and registration office S5, and terminal device T6 is located at used car dealership S6.

[0027] Hereinafter, terminal devices T1 to T5 will be collectively referred to as terminal device T, and service station S1, auto parts store S2, car dealership S3, repair shop S4, vehicle inspection and registration office S5, and used car dealership S6 will be collectively referred to as store S. Note that there may be multiple terminal devices T, and is not limited to five. Also, stores are not limited to service station S1, auto parts store S2, car dealership S3, repair shop S4, vehicle inspection and registration office S5, and used car dealership S6, but may be shopping centers or various other types of stores.

[0028] It is preferable that stores S be distributed across as wide an area as possible, such as being located throughout Japan, and that there be a large number of them.

[0029] Network 3 may be various communication methods such as the Internet, public telephone lines, mobile communication networks, LANs (Local Area Networks), Wi-Fi (registered trademark), etc., and these communication methods may be combined, and may be wired, wireless, or a combination of wired and wireless.

[0030] Terminal device T is capable of communicating with server device 2, for example, via network 3. Terminal device T can include, for example, a tablet device, a personal computer, or a smartphone.

[0031] The terminal device T allows input of vehicle information D, such as the chassis number N of the vehicle C to be serviced, and information about the vehicle C or information about the service, using an operation input device such as a touch panel display or keyboard (not shown in the diagram).

[0032] The terminal device T may be connectable to a scan tool (not shown in the diagram). The scan tool is a reading device capable of reading fault codes (DTCs), which are examples of fault information, from the on-board diagnostic (OBD) system installed in the vehicle C. The terminal device T may acquire the fault codes read by the scan tool as vehicle information D from the scan tool.

[0033] Furthermore, the terminal device T may, for example, be equipped with a camera and read the chassis number N from a two-dimensional code such as a QR code (registered trademark) written on the vehicle registration certificate of automobile C, or it may read the chassis number N from an IC chip.

[0034] Terminal device T may receive information indicating orders for, for example, automotive parts, automotive consumables, and automotive repair supplies as vehicle information D. Examples of services include the sale of automotive parts, automotive consumables, automotive repair supplies, automotive maintenance, automotive repair, automotive inspection, automotive inspection and registration system inspection, and automotive appraisal.

[0035] Terminal device T transmits the chassis number N of automobile C, which was obtained as described above, the vehicle information D related to automobile C, and the source information A to server device 2 via network 3. Source information A is the identification information of the source terminal device T, or information indicating the store where terminal device T is located. Source information A is stored in terminal device T in advance. Terminal device T is not required to transmit source information A.

[0036] The server device 2 comprises a control unit 21 and a storage unit 22. The control unit 21 is configured to include, for example, a CPU (Central Processing Unit) that performs predetermined arithmetic processing, a non-volatile storage unit such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) that stores predetermined programs, RAM (Random Access Memory) that temporarily stores data, a communication circuit that can be connected to the network 3, an RTC (Real Time Clock), and peripheral circuits thereof.

[0037] The control unit 21 functions as a receiving processing unit 211, a storage processing unit 212, a browsing processing unit 213, and an order processing unit 214, for example, by executing the program described above.

[0038] The memory unit 22 is, for example, a non-volatile storage device such as an HDD or SSD.

[0039] The receiving processing unit 211 receives the chassis number N, vehicle information D, and source information A from the terminal device T via the network 3.

[0040] The memory processing unit 212 associates the chassis number N, vehicle information D, source information A, and date information B indicating the date of reception received by the receiving processing unit 211, and stores them cumulatively in the storage unit 22. The date information B may be generated by the RTC of the control unit 21, or it may be transmitted by the terminal device T to the server device 2 along with the chassis number N and vehicle information D. The memory processing unit 212 does not have to store the source information A in the storage unit 22.

[0041] When the browsing processing unit 213 receives a request for vehicle information D corresponding to chassis number N from any of the multiple terminal devices T via the network 3, it transmits the cumulatively stored vehicle information D and date information B associated with chassis number N to one of the terminal devices T via the network 3. The source information A may or may not be transmitted.

[0042] If the vehicle information D received by the receiving processing unit 211 is information indicating an order as described above, the order processing unit 214 executes order processing based on that information indicating an order.

[0043] Next, we will explain the operation of the vehicle information history management system 1 configured as described above. Figure 2 is a flowchart showing an example of the operation of the vehicle information history management system 1 shown in Figure 1. First, we will explain the operation when the storage unit 22 is used to store vehicle information D cumulatively.

[0044] First, terminal device T acquires the chassis number N and vehicle information D, and transmits them to server device 2 via network 3 along with source information A (step ST1). Specifically, for example, at service station S1, terminal device T1 may acquire the chassis number N of automobile C, and an operator may input service details such as oil change or tire change as vehicle information D into terminal device T1, or the order information for oil, tires, etc., may be acquired as vehicle information D by terminal device T1 when an order is placed using terminal device T1.

[0045] For example, at an auto parts store S2, the vehicle identification number N of automobile C may be obtained using a terminal device T2, and when an employee orders automobile parts such as batteries, automobile consumables such as oil, or automobile repair supplies such as paint and putty using the terminal device T2, the order information may be obtained by the terminal device T2 as vehicle information D.

[0046] For example, at a car dealership S3 or a repair shop S4, the vehicle identification number N of a car C may be obtained using a terminal device T at each store S, and the worker may input records of repair services or maintenance services as vehicle information D into terminal devices T3 and T4.

[0047] For example, at a car dealership S3, a repair shop S4, or a vehicle inspection and registration office S5, the vehicle identification number N of the vehicle C may be obtained using terminal devices T3, T4, and T5 at each store S, and the worker may input, for example, the vehicle inspection record as vehicle information D into terminal devices T3, T4, and T5.

[0048] For example, at a used car dealership S6, when an appraisal, purchase, or sale service is performed for automobile C, the terminal device T6 may be used to obtain the vehicle identification number N of automobile C, and the worker may input the details of the service as vehicle information D into the terminal device T6.

[0049] Furthermore, at any of the service station S1, auto parts store S2, car dealership S3, repair shop S4, vehicle inspection and registration office S5, or used car dealership S6, when providing service to vehicle C, fault information such as fault codes read from the fault diagnostic device installed in vehicle C may be acquired as vehicle information D by terminal devices T1 to T6.

[0050] Next, the receiving processing unit 211 receives the chassis number N, vehicle information D, and source information A transmitted as described above from the terminal device T via the network 3 (step ST2: receiving processing step).

[0051] Next, the memory processing unit 212 stores the chassis number N, vehicle information D, and source information A received as described above, along with the date information B, in the memory unit 22 in an associated manner (step ST3: memory processing step).

[0052] Figure 4 is a tabular explanatory diagram showing an example of data stored in the storage unit 22. According to steps ST2 and ST3, for example, the chassis number N, vehicle information D, date information B, and source information A can be stored in the storage unit 22 in association with each other, as shown in the history information H in Figure 4.

[0053] History information H records that for vehicle C with chassis number N AAAA, it was sold as a new car on 2015.1.15, had its oil changed on 2016.3.10, and that the battery was replaced on 2017.5.5 as a battery was ordered at that time. It also records vehicle inspection information showing the results of the vehicle inspection conducted on 2018.1.15, was purchased as a used car on 2018.6.20, sold as a used car on 2018.8.30, meaning the ownership changed, and that repairs were carried out on 2019.9.1.

[0054] Vehicle inspection information is an example of information that shows the results of a service. Information that shows the results of a service is not limited to vehicle inspection information; it could also be maintenance records, repair records, or inspection records.

[0055] Furthermore, the history information H records the vehicle information D, which contains the failure information of vehicle C acquired at the following times: January 15, 2015, March 10, 2016, May 5, 2017, January 15, 2018, June 20, 2018, August 30, 2018, and September 1, 2019.

[0056] Thus, according to steps ST2 and ST3, vehicle information D obtained by various stores S distributed throughout Japan for one automobile C with chassis number N AAAA can be cumulatively stored in the storage unit 22.

[0057] For example, if the vehicle number (license plate number) is used instead of the chassis number N, the vehicle number may change even for the same vehicle if the registration area changes due to relocation or the owner changes. Therefore, if vehicle information D is recorded in association with the vehicle number, it will become impossible to retrieve the vehicle information D from before the vehicle number change if the vehicle number changes.

[0058] However, the chassis number N is a number that is required to be stamped on vehicles under the Road Transport Vehicle Act, and the number does not change until the vehicle is scrapped. Therefore, by associating vehicle information D with chassis number N, it becomes possible to cumulatively store the history of automobile C since its manufacture in the storage unit 22, making it easy to improve the accuracy of obtaining information regarding malfunctions, etc., of automobile C.

[0059] Furthermore, as mentioned above, fault codes stored in the fault diagnostic device are erased after necessary maintenance or repairs are performed. For example, in the case of automobile C with chassis number N of AAAA in history information H, the fault codes stored in the fault diagnostic device are erased when it is repaired on 2019.9.1. Therefore, according to the technology described in Patent Document 1, it is only possible to obtain fault information after the fault codes have been erased on 2019.9.1.

[0060] However, with the vehicle information history management system 1, fault information before it is erased can be cumulatively stored in the storage unit 22, making it easy to improve the accuracy of obtaining information regarding faults of the automobile C.

[0061] Next, the order processing unit 214 checks whether the vehicle information D received by the receiving processing unit 211 is order information (step ST4). If it is not order information (NO in step ST4), the process ends. On the other hand, if it is order information (YES in step ST4), the order processing unit 214 executes order processing based on the order information in the vehicle information D (step ST5), and then the process ends.

[0062] Order processing involves tasks such as instructing the shipment of ordered goods based on order information, requesting suppliers or agents handling the ordered goods to place orders and ship them, and performing accounting procedures to settle charges.

[0063] According to steps ST1 to ST5, store S can place an order for goods and record vehicle information D related to the target automobile C simply by using terminal device T, thus improving the convenience of store S.

[0064] Next, we will explain the operation of the browsing processing unit 213 when using history information H. Figure 3 is a flowchart showing an example of the operation of the browsing processing unit 213 shown in Figure 1. For example, we will explain using the case where a used car dealership S6 is conducting a purchase appraisal for car C.

[0065] First, an employee at the used car dealership S6 obtains the chassis number N of the target vehicle C using the terminal device T6, and then operates the terminal device T6 to request vehicle information D. The terminal device T6 then sends a request for vehicle information D corresponding to chassis number N to the server device 2 via the network 3 (step ST11).

[0066] Next, the browsing processing unit 213 receives a request from the terminal device T6 for vehicle information D corresponding to chassis number N (step ST12). Then, the browsing processing unit 213 reads the vehicle information D and date information B associated with the received chassis number N from the storage unit 22 and transmits them to the requesting terminal device T6 (step ST13: browsing processing step).

[0067] For example, if the chassis number N is AAAA, according to the history information H shown in Figure 4, all vehicle information D and date information B for the period from 2015.1.15 to 2019.9.1 will be sent to the requesting terminal device T6.

[0068] Next, the requesting terminal device T6 receives the vehicle information D and date information B transmitted from the browsing processing unit 213 and displays them on the display device (not shown in the figure) (step ST14).

[0069] This allows used car dealership S6 to check all of the past vehicle information D accumulated in the memory unit 22 for vehicle C with chassis number N AAAA, along with the date information B. As a result, a lot of information related to past malfunctions, repairs, inspections, and maintenance of vehicle C can be obtained, improving the accuracy of the appraisal of vehicle C at used car dealership S6.

[0070] Even if a store S is not the used car dealership S6, if it can obtain a lot of information related to the past breakdowns, repairs, inspections, and maintenance of car C, it will be easier to accurately understand the condition of car C. As a result, it will be easier for store S to provide appropriate service for car C.

[0071] Furthermore, the vehicle information history management system 1 does not necessarily have to include an order processing unit 214, and steps ST4 and ST5 do not need to be executed. Also, the storage processing unit 212 does not necessarily need to store date information B in the storage unit 22, nor does it need to store source information A in the storage unit 22. [Explanation of Symbols]

[0072] 1. Vehicle Information History Management System 2 Server devices 3 Network 21 Control Unit 22 Memory section 211 Receiving Processing Unit 212 Memory Processing Unit 213 Browsing Processing Unit 214 Order Processing Unit A Sender Information B Date information C car D Vehicle Information H History Information N Chassis number S Store S1 Service Station (Store) S2 Automotive parts store (store) S3 Car Dealership (Store) S4 Repair shop (store) S5 Vehicle Inspection and Registration Office (Store) S6 Used Car Dealership (Store) T,T1~T6 Terminal device

Claims

[Claim 1] This includes terminal devices installed in each of the multiple stores that provide automotive-related services, A receiving processing unit receives from the terminal device via the network, associating the chassis number of the vehicle subject to the service with vehicle information including fault information of the vehicle. Memory unit and, A storage processing unit that associates the received chassis number with the vehicle information and stores it cumulatively in the storage unit, The server device includes a browsing processing unit that, when it receives a request for vehicle information corresponding to the chassis number from any of the aforementioned terminal devices via the network, transmits the vehicle information, which has been cumulatively stored in association with the chassis number, to any of the aforementioned terminal devices via the network. The aforementioned automobile is equipped with a fault diagnosis device, The terminal device is a vehicle information history management system capable of acquiring the fault information stored in the fault diagnosis device of the automobile.