CN111553491A

CN111553491A - Vehicle maintenance record generation method and related device

Info

Publication number: CN111553491A
Application number: CN202010332125.XA
Authority: CN
Inventors: 刘均; 杜武洲
Original assignee: Shenzhen Launch Technology Co Ltd
Current assignee: Shenzhen Launch Technology Co Ltd
Priority date: 2020-04-24
Filing date: 2020-04-24
Publication date: 2020-08-18

Abstract

The embodiment of the application discloses a method for generating a vehicle maintenance record and a related device, wherein the method comprises the following steps: obtaining at least two diagnostic reports for the vehicle; the diagnostic report includes a fault code; and generating a maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports. Through the embodiment of the application, the electronic equipment can generate the maintenance record of the vehicle, and the reliability of the maintenance record is improved.

Description

Vehicle maintenance record generation method and related device

Technical Field

The present disclosure relates to the field of vehicle maintenance, and in particular, to a method and a related device for generating a vehicle maintenance record.

Background

The vehicle maintenance record is a detailed archive of each maintenance condition of the vehicle, and comprises basic information of the vehicle, maintenance organization information, maintenance place, maintenance duration, maintenance personnel, fault conditions, maintenance results and the like. The maintenance record is important data, and has great reference value for the assessment of maintenance technicians, the performance statistics of maintenance organizations, the maintenance payment of vehicle owners and the vehicle maintenance insurance.

In the prior art, a maintenance mechanism usually records the vehicle maintenance condition manually, certain manpower is consumed in the mode, and meanwhile, the generated maintenance record has more human factors, so that the real reliability is difficult to guarantee.

Disclosure of Invention

The embodiment of the application provides a vehicle maintenance record generation method and a related device.

In a first aspect, an embodiment of the present application provides a method for generating a vehicle repair record, including: obtaining at least two diagnostic reports for the vehicle; the diagnostic report includes a fault code; and determining the maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnostic reports.

Based on the first aspect, in one possible implementation manner, the diagnostic report includes a diagnostic device identifier, a vehicle identifier, and a generation time, and the obtaining at least two diagnostic reports of a vehicle includes: selecting M diagnostic reports with the same vehicle identification from the N diagnostic reports; selecting at least two diagnostic reports based on the generation times of the M diagnostic reports, the at least two diagnostic reports including a first diagnostic report and a second diagnostic report; wherein M and N are integers of 2 or more.

In one possible implementation form of the first aspect, an absolute value of a difference between generation times of the first diagnostic report and the second diagnostic report is not less than a threshold time.

Based on the first aspect, in one possible implementation manner, if the generation time of the first diagnostic report is less than the generation time of the second diagnostic report, the first fault code is greater than the second fault code; or if the generation time of the first diagnosis report is longer than that of the second diagnosis report, the first fault code is smaller than the second fault code.

Based on the first aspect, in one possible implementation manner, before the selecting M diagnostic reports with the same vehicle identifier from the N diagnostic reports, the method further includes: receiving the N diagnosis reports sent by the diagnosis equipment; the diagnostic equipment is equipment for generating a diagnostic report after the vehicle is diagnosed.

Based on the first aspect, in one possible implementation manner, the determining the service record of the vehicle according to the difference between the fault codes of the at least two diagnostic reports includes: and confirming the maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports under the condition that the difference of the fault codes meets the preset standard.

Based on the first aspect, in one possible implementation manner, the maintenance record includes one or more of a maintenance record ID, a self-increment ID, a vehicle VIN code, a vehicle brand, a vehicle type, a vehicle year, a diagnostic equipment serial number, a maintenance organization name, a maintenance organization address, a maintenance organization contact, a maintenance technician name, a maintenance technician contact, a number of fault codes before maintenance, fault code details before maintenance, a number of fault codes after maintenance, fault code details after maintenance, a maintenance start time, a maintenance end time, a maintenance elapsed time, and a maintenance record generation time.

In a second aspect, an embodiment of the present application provides an apparatus for generating a vehicle maintenance record, including:

an acquisition unit for acquiring at least two diagnostic reports of a vehicle; the diagnostic report includes a fault code;

and the determining unit is used for determining the maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnostic reports.

Based on the second aspect, in one possible implementation manner, the obtaining unit is specifically configured to select M diagnostic reports with the same vehicle identifier from the N diagnostic reports;

selecting at least two diagnostic reports based on the generation times of the M diagnostic reports, the at least two diagnostic reports including a first diagnostic report and a second diagnostic report; wherein M and N are integers of 2 or more.

Based on the second aspect, in one possible implementation manner, the determining unit is specifically configured to, in a case that the difference between the fault codes meets a preset standard, confirm the service record of the vehicle according to the difference between the fault codes of the at least two diagnostic reports.

In a third aspect, an embodiment of the present application provides a vehicle maintenance record generation device, which includes a processor, where the processor is configured to invoke a stored program and execute the vehicle maintenance record generation method provided in the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium, which stores program instructions, and when the program instructions are executed by a processor, the processor executes the method for generating a vehicle service record provided in the first aspect.

The method and the device for generating the time difference can obtain at least two diagnostic reports, wherein the at least two diagnostic reports are the same in equipment identification and vehicle identification, and the absolute value of the generated time difference is not less than a threshold value; and the absolute value of the difference in the time of generation of the first diagnostic report and the second diagnostic report is not less than the threshold time; and confirming the maintenance record of the vehicle according to the difference of the fault codes of at least two diagnostic reports. According to the embodiment of the application, the electronic equipment can generate the diagnosis record of the vehicle according to at least the diagnosis report of the vehicle, the possible error caused by manual operation is avoided, the labor cost can be saved, and meanwhile, the authenticity of the diagnosis record can be drafted.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

FIG. 1 is a system architecture diagram illustrating the generation of a vehicle service record provided by an embodiment of the present application;

FIG. 2 is a schematic flow chart diagram illustrating a method for generating a vehicle service record according to an embodiment of the present disclosure;

FIG. 3 is a schematic flow chart diagram illustrating another method for generating a vehicle service record according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of a device for generating a vehicle service record according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a vehicle repair record generation device provided in an embodiment of the present application.

Detailed Description

The embodiments of the present application will be described below with reference to the drawings.

The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

In order to better understand the method, device, apparatus, and readable storage medium for generating a vehicle service record provided in the embodiments of the present application, an architecture diagram of a method for generating a vehicle service record according to an embodiment of the present application is described below. As shown in fig. 1, a system architecture diagram for generating a vehicle service record according to an embodiment of the present application includes a vehicle 100, a diagnostic device 101, and an electronic device 102. The diagnostic device 101 is used to check the vehicle 100 and generate a diagnostic report. It should be noted that the diagnostic apparatus 101 may perform a plurality of inspections on the vehicle 100, and thus may generate a plurality of diagnostic reports. For example, when the vehicle is performing a maintenance operation, the maintenance technology uses the diagnostic device 101 to perform a check on the state of the vehicle 100 before maintenance to obtain basic information and fault conditions of the vehicle 100, and then after the maintenance operation is completed, the state of the vehicle 100 after maintenance can be checked again through the diagnostic device 101. The diagnostic device 101 records the diagnostic report data of each time after the examination operation is completed, and may upload the generated multiple diagnostic reports to the electronic device 102 in real time through network transmission. The electronic device 102 may save the data of the diagnosis report after receiving the diagnosis report uploaded by the diagnosis device 101. The electronic device 102 may obtain at least two diagnostic reports, wherein the diagnostic reports include a fault code, and determine a service record of the vehicle based on a difference between the fault codes of the at least two diagnostic reports. The diagnostic device 101 includes, but is not limited to, various vehicle scanning tools such as handheld, PC, etc., on which a diagnostic database is stored and information related to various vehicles is stored.

The electronic device 102 may include a backend server, a storage server, or an arithmetic server, with computing capability.

A method for generating a vehicle maintenance record according to the present application is described below with reference to fig. 2, which is a schematic flow chart of a method for generating a vehicle maintenance record according to an embodiment of the present application, as shown in fig. 2.

Step S201, the electronic equipment receives N diagnosis reports sent by the diagnosis equipment;

specifically, the electronic device may receive N diagnostic reports sent by the diagnostic device, where N ≧ 1. It should be noted that the N diagnostic reports may be generated and sent to the electronic device by the diagnostic device after the vehicle is diagnosed at different times. For example, the following steps: when a vehicle is maintained, the maintenance technology can utilize the vehicle diagnosis equipment to perform one diagnosis operation on the state of the vehicle before maintenance to generate a 1 st diagnosis report, and the 1 st diagnosis report is uploaded to the electronic equipment; then after the maintenance work is finished, the state of the vehicle after maintenance is diagnosed again to generate a 1 st diagnosis report, and the 2 nd diagnosis report is uploaded to the electronic equipment; so that the electronic device can receive at least 2 diagnostic reports uploaded by the diagnostic device. The vehicle identifier may be a Vehicle Identification Number (VIN), a diagnostic device identifier, and a generation time of the diagnostic report. The vehicle identification code of the vehicle is a group of seventeen English numbers, is used for a group of unique numbers on the vehicle, and can identify the manufacturer of the vehicle, the engine, the chassis serial number and other performance data.

Step S202, the electronic equipment saves the N diagnosis reports into a diagnosis report table;

specifically, after the electronic device receives N diagnostic reports sent by the diagnostic device, the data in the N diagnostic reports may be stored in a diagnostic report table of a relational database management system (MySQL). It should be noted that the storage according to the embodiment of the present application is not limited to the storage service type, and the storage service may be any of the following: MySQL, a database based on distributed file storage (such as MongoDB), an Oracle database, Microsoft's SQLServer database electronic device (msSQL), and so on. The structural design of the diagnosis report table diagnoserecrd table is shown in table 1:

TABLE 1

Name of field	Type (B)	Note
			diagnose_record_id	Int	Diagnostic report record ID, self-increment ID
vin	String	Vehicle VIN code
			car_brand	String	Vehicle brand
car_model	String	Vehicle model
			car_year	String	Annual vehicle model
device_sn	String	Diagnostic device serial number
			repair_shop_name	String	Name of maintenance organization
repair_shop_address	String	Maintenance organization address
			repair_shop_phone	String	Maintenance organization contact way
technician_name	String	Name of service technician
			technician_phone	String	Service technician contact details
dtc_num	Int	Number of fault codes
			dtc_detail	String	Details of fault codes
upload_time	Int	Report upload time

It should be noted that, the table structure of the diagnosis report table is not limited in this embodiment.

Step S203, the electronic equipment acquires at least two diagnosis reports of the vehicle;

specifically, at least two diagnostic reports meeting a preset rule need to be acquired, wherein the diagnostic reports report fault codes.

Optionally, the diagnostic report includes a diagnostic device identifier, a vehicle identifier, and a generation time, and the obtaining at least two diagnostic reports of the vehicle includes: selecting M diagnostic reports with the same vehicle identification from the N diagnostic reports; selecting at least two diagnostic reports based on the generation times of the M diagnostic reports, the at least two diagnostic reports including a first diagnostic report and a second diagnostic report; wherein M and N are integers of 2 or more. Furthermore, the screening of the diagnosis report can also consider the diagnosis equipment identification factor, namely the diagnosis equipment identification of the diagnosis equipment of the same type can be considered as the diagnosis judgment basis before and after one-time maintenance.

Specifically, the vehicle identifier is a unique identifier when the vehicle leaves a factory, and may be a vehicle VIN code; the diagnostic equipment identifier is the only identifier of the diagnostic equipment when the diagnostic equipment leaves a factory, and can be a serial number of the diagnostic equipment; the diagnostic report with the same diagnostic equipment identifier and the same vehicle identifier is generated after the same diagnostic equipment diagnoses the same vehicle. Because the diagnosis report table stores many diagnosis reports generated after different diagnosis devices diagnose different vehicles, M diagnosis reports with the same vehicle identifier need to be inquired from N diagnosis reports in the diagnosis report table according to the vehicle identifier and the diagnosis device identifier; wherein M and N are integers of 2 or more. Since the diagnostic record is a sum record of the vehicle pre-repair situation and the vehicle post-repair situation, the acquired M diagnostic reports may be M of the N diagnostic reports that are newly uploaded. The M diagnostic reports can be screened according to the generation time of the diagnostic reports, and at least two diagnostic reports can be selected from the M diagnostic reports. Wherein the at least two diagnostic reports include a first diagnostic report and a second diagnostic report.

Optionally, the absolute value of the difference in the time of generation of the first diagnostic report and the second diagnostic report is not less than a threshold time.

Specifically, the threshold time may be specifically set according to actual conditions, and may be one week, one month, and the like, which is not limited in this embodiment.

Optionally, the first diagnostic report includes a first fault code and the second diagnostic report includes a second fault code; if the generation time of the first diagnosis report is less than that of the second diagnosis report, the first fault code is greater than the second fault code; or if the generation time of the first diagnosis report is longer than that of the second diagnosis report, the first fault code is smaller than the second fault code.

Specifically, for example, the generation time of the first diagnostic report is 2019, 10 and 14, and the generation time of the second diagnostic report is 2019, 11 and2, so that the generation time of the first diagnostic report is less than that of the second diagnostic report, and the number of the first fault codes is greater than that of the second fault codes.

And step S204, the electronic equipment determines the maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports.

In particular, the diagnostic report contains fault codes, which may be indicative of a fault condition of the vehicle. The change in the number of trouble codes reflects whether the vehicle has been effectively serviced, so that a service record for the vehicle can be determined based on the difference between at least two of the trouble codes from the diagnostic reports.

Optionally, the determining the service record of the vehicle according to the difference of the fault codes of the at least two diagnostic reports comprises: and confirming the maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports under the condition that the difference of the fault codes meets the preset standard.

Specifically, the at least two diagnostic reports include a pre-diagnostic report and a post-diagnostic report, and if the number of fault codes in the post-diagnostic report is less than the number of fault codes in the pre-diagnostic report, it is determined that the vehicle has fewer faults and the faults are resolved, and the vehicle is considered to have undergone one effective diagnostic maintenance. A service record for the vehicle may thus be determined based on the difference in the fault codes of at least two diagnostic reports.

Optionally, the service record of the vehicle may include: one or more of a maintenance record ID, a self-increment ID, a vehicle VIN code, a vehicle brand, a vehicle model, a vehicle year, a diagnostic equipment serial number, a maintenance organization name, a maintenance organization address, a maintenance organization contact, a maintenance technician name, a maintenance technician contact, a number of fault codes before maintenance, a number of fault code details before maintenance, a number of fault codes after maintenance, a fault code detail after maintenance, a start maintenance time, an end maintenance time, a maintenance elapsed time, and a maintenance record generation time. Finally, the vehicle's service record may be stored in the service record table repair _ record _ table of the mysql database. It should be noted that the storage according to the embodiment of the present application is not limited to the storage service type, and the storage service may be any of the following: MySQL, a database based on distributed file storage (such as MongoDB), Oracle database, microsoft's SQLServer database electronics (ms SQL), and so on.

The table structure design of the repair record table repair _ record _ table is shown in table 2:

TABLE 2

Name of field	Type (B)	Note
			repair_record_id	Int	Maintenance record ID, self-increment ID
vin	String	Vehicle VIN code
			car_brand	String	Vehicle brand
car_model	String	Vehicle model
			car_year	String	Annual vehicle model
device_sn	String	Diagnostic device serial number
			repair_shop_name	String	Name of maintenance organization
repair_shop_address	String	Maintenance organization address
			repair_shop_phone	String	Maintenance organization contact way
technician_name	String	Name of service technician
			technician_phone	String	Service technician contact details
dtc_num_before_repair	Int	Number of trouble codes before maintenance
			dtc_detail_before_repair	String	Fault code details before repair
dtc_num_after_repair	Int	Number of fault codes after maintenance
			dtc_detail_after_repair	String	Post-repair trouble code details
start_repair_time	Int	Time to start maintenance
			end_repair_time	Int	End of maintenance time
consuming_time	Int	Time consuming maintenance
			create_time	Int	Maintenance record generation time

It should be noted that the table structure of the maintenance record table is not limited in any way in the embodiments of the present application.

Referring to fig. 3, fig. 3 is a schematic flowchart of another method for generating a vehicle service record according to an embodiment of the present disclosure.

Step S301, the diagnostic equipment sends a diagnostic report to the electronic equipment;

specifically, the diagnostic device may record a diagnostic report of a time after performing a diagnostic operation on the vehicle, and transmit the diagnostic report to the electronic device in real time through network transmission. The diagnostic device may perform N diagnoses on the vehicle to generate N diagnostic reports, and may transmit the N diagnostic reports to the electronic device. The contents of the diagnostic report may include: service factory information, diagnostic equipment information (serial number, equipment hardware information, equipment software information), vehicle service base (brand, model, year), diagnostic time and location, diagnostic results (system, trouble code, data stream), and the like.

Step S302, the electronic equipment stores the diagnosis report to a diagnosis report table;

specifically, please refer to step S202 for detailed description.

Step S303, the electronic equipment acquires two latest diagnosis reports;

specifically, the electronic device obtains two newly generated diagnostic reports from the diagnostic report table.

Step S304, judging whether the number of the diagnosis reports is less than or equal to 1;

specifically, the electronic device judges the number of the two latest uploaded diagnosis reports, and if the number of the two latest uploaded diagnosis reports is less than or equal to 1, the electronic device ends the relevant operation of generating the vehicle maintenance record; if the number of inquired diagnosis reports is equal to 2, the process proceeds to step S305.

Step S305, judging whether the generation time difference of the diagnosis report is less than one month;

specifically, the electronic device may determine whether a difference between generation times of two newly uploaded diagnosis reports is less than one month, where the two diagnosis reports include a first diagnosis report and a second diagnosis report, the electronic device compares the generation time of the first diagnosis report with the generation time of the second diagnosis report, and if an absolute value of the difference between the generation times of the first diagnosis report and the second diagnosis report exceeds one month, the electronic device ends a related operation of generating a vehicle maintenance record; if the absolute value of the generation time difference does not exceed one month, step S306 is performed.

Step S306, judging whether the number of fault codes in the diagnosis report is reduced or not;

specifically, the electronic device may compare a first number of faults of the first diagnostic report with a second number of fault codes of the second diagnostic report, and on the premise that the generation time of the first diagnostic report is shorter than the generation time of the second diagnostic report, if the first number of fault codes of the first diagnostic report is greater than the second number of fault codes of the second diagnostic report; or, on the premise that the generation time of the first diagnostic report is longer than that of the second diagnostic report, if the first fault code quantity of the first diagnostic report is smaller than the second fault code quantity of the second diagnostic report; the vehicle failure is reduced and the failure is resolved, and the vehicle is considered to have undergone an effective vehicle maintenance, and step S307 is performed. If the first and second diagnostic reports are opposite to the above case, the flow ends.

In step S307, the electronic device generates a maintenance record.

Specifically, if the first diagnostic report is a diagnostic report before maintenance, the second diagnostic report is a diagnostic report after maintenance. Respectively extracting data in the first diagnosis report, and adding '1' to a suffix of a field name of the data in the first diagnosis report, wherein the data comprises the following specific components: diagnosese _ record _ id1, vin1, car _ brand1, car _ model1.. upload _ time 1. The suffix of the field name of the data of the repaired diagnosis report (second diagnosis report) is added with "2", and specifically, the method comprises the following steps: diagnosese _ record _ id2, vin2, car _ brand2, car _ model2.

Since both reports are generated by diagnostic equipment of the same vehicle and the same maintenance facility, the vehicle information, the maintenance facility information, the equipment information, and the maintenance personnel information of both reports are the same. And the vehicle information, the maintenance organization information, the equipment information and the maintenance personnel information in the maintenance record can be obtained from any one of the two reports. The diagnostic report record data after maintenance can be taken as a default, and the diagnostic report record data before maintenance can also be taken, and the embodiment of the application is not limited at all.

The data in the maintenance record table is calculated as follows:

the repair _ record _ ID is a database self-increment ID and does not need to be calculated.

vin＝vin2

car_brand＝car_brand2

car_model＝car_model2

car_year＝car_year2

device_sn＝device_sn2

repair_shop_name＝repair_shop_name2

repair_shop_address＝repair_shop_address2

repair_shop_phone＝repair_shop_phone2

technician_name＝technician_name2

technician_phone＝technician_phone2

dtc_num_before_repair＝dtc_num_before_repair1

dtc_detail_before_repair＝dtc_detail_before_repair1

dtc_num_after_repair＝dtc_num_after_repair2

dtc_detail_after_repair＝dtc_detail_after_repair2

start_repair_time＝upload_time1

end_repair_time＝upload_time2

consuming_time＝upload_time2-upload_time1

create _ time is the current time of the electronic device.

Referring to fig. 4, fig. 4 is a schematic structural diagram of an apparatus 400 for generating a vehicle maintenance record according to an embodiment of the present application, where the apparatus 400 may be an electronic device or a component in the electronic device in the foregoing method embodiment, and the apparatus 400 may include: an acquisition unit 401 and a generation unit 402, wherein,

an acquisition unit 401 for acquiring at least two diagnostic reports of a vehicle; the diagnostic report includes a fault code;

a generating unit 402, configured to generate a maintenance record of the vehicle according to a difference between the fault codes of the at least two diagnostic reports.

The diagnosis report includes a diagnosis device identifier, a vehicle identifier, and a generation time, and the obtaining unit 401 is specifically configured to select M diagnosis reports with the same vehicle identifier from the N diagnosis reports; selecting at least two diagnostic reports based on the generation times of the M diagnostic reports, the at least two diagnostic reports including a first diagnostic report and a second diagnostic report; wherein M and N are integers of 2 or more.

The acquisition unit 401 includes a receiving unit 403, specifically configured to receive N diagnostic reports sent by the diagnostic device before the acquisition unit 401 selects M diagnostic reports with the same vehicle identifier from the N diagnostic reports; the diagnostic equipment is equipment for generating a diagnostic report after the vehicle is diagnosed.

The generating unit 402 is specifically configured to generate a maintenance record of the vehicle according to the difference between the fault codes of the at least two diagnosis reports when the difference between the fault codes meets a preset standard.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a vehicle repair record generating device 500 according to an embodiment of the present application, where the electronic device 500 may include: one or more processors 501, one or more memories 502, and one or more communication interfaces 503. These components may be connected by a bus 504 or otherwise, as illustrated in FIG. 5 by a bus connection. Wherein:

the communication interface 503 may be used for the electronic device 500 to communicate with other communication devices, such as other electronic devices. In particular, the communication interface 503 may be a wired interface.

The memory 502 may be coupled to the processor 501 via the bus 504 or an input/output port, and the memory 502 may be integrated with the processor 501. The memory 502 is used to store various software programs and/or sets of instructions or data. In particular, Memory 502 may be a Read-Only Memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to. The memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 502 may store an operating system (hereinafter, referred to as a system), such as an embedded operating system like uCOS, VxWorks, RTLinux, etc. The memory 502 may also store a network communication program that may be used to communicate with one or more additional devices, one or more user devices, one or more electronic devices. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 502 is used for storing application program codes for executing the above scheme, and is controlled by the processor 501 for execution. The processor 501 is used to execute the application code resources stored in the memory 502.

The processor 501 may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, transistor logic, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of certain functions, including for example one or more microprocessors, a combination of digital signal processors and microprocessors, or the like.

The processor 501 may be configured to call an application program stored in the memory 502 to implement the corresponding steps of the block chain based advertisement data processing method in any corresponding embodiment of fig. 2 or fig. 3; in particular implementations, one or more instructions in the computer storage medium are loaded by processor 501 and perform the following steps:

obtaining at least two diagnostic reports for the vehicle; the diagnostic report includes a fault code;

and generating a maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports.

In yet another embodiment, the diagnostic report includes a diagnostic device identifier, a vehicle identifier, and a generation time, and the obtaining at least two diagnostic reports for a vehicle includes: selecting M diagnostic reports with the same vehicle identification from the N diagnostic reports; selecting at least two diagnostic reports based on the generation times of the M diagnostic reports, the at least two diagnostic reports including a first diagnostic report and a second diagnostic report; wherein M and N are integers of 2 or more.

In yet another embodiment, the absolute value of the difference in the time of generation of the first diagnostic report and the second diagnostic report is not less than a threshold time.

In yet another embodiment, the first diagnostic report includes a first fault code and the second diagnostic report includes a second fault code; if the generation time of the first diagnosis report is less than that of the second diagnosis report, the first fault code is greater than the second fault code; or if the generation time of the first diagnosis report is longer than that of the second diagnosis report, the first fault code is smaller than the second fault code.

In another embodiment, before the selecting M diagnostic reports with the same vehicle identifier from the N diagnostic reports, the method further includes: receiving the N diagnosis reports sent by the diagnosis equipment; the diagnostic equipment is equipment for generating a diagnostic report after the vehicle is diagnosed.

In yet another embodiment, said generating a service record of said vehicle based on a difference between said fault codes of said at least two diagnostic reports comprises: and generating a maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports under the condition that the difference of the fault codes meets a preset standard.

In embodiments of the present application, the processor 501 may be configured to read and execute computer readable instructions. Specifically, the processor 501 may be configured to call a program stored in the memory 502, for example, an implementation program of a method for generating a vehicle service record provided by one or more embodiments of the present application on the electronic device 500 side, and execute instructions included in the program.

It should be noted that the electronic device 500 shown in fig. 5 is only one implementation manner of the embodiment of the present application, and in practical applications, the electronic device 500 may further include more or less components, which is not limited herein. For specific implementation of the electronic device 500, reference may be made to the foregoing description in the method embodiments shown in fig. 1 to fig. 4, and details are not repeated here.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, and may specifically be a processor in the computer device) to execute all or part of the steps of the above-mentioned method of the embodiments of the present application. The storage medium may include: a U-disk, a removable hard disk, a magnetic disk, an optical disk, a Read-Only Memory (ROM) or a Random Access Memory (RAM), and the like.

One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.

Claims

1. A method of generating a vehicle service record, comprising:

acquiring at least two diagnostic reports of a vehicle, wherein the diagnostic reports comprise fault codes;

2. The method of claim 1, wherein the diagnostic report includes a diagnostic device identification, a vehicle identification, and a generation time, and wherein obtaining at least two diagnostic reports for a vehicle comprises:

selecting M diagnostic reports with the same vehicle identification from the N diagnostic reports;

3. The method of claim 2, wherein an absolute value of a difference in generation time of the first diagnostic report and the second diagnostic report is not less than a threshold time.

4. A method according to claim 2 or 3, wherein the first diagnostic report comprises a first fault code and the second diagnostic report comprises a second fault code;

if the generation time of the first diagnosis report is less than that of the second diagnosis report, the first fault code is greater than the second fault code; or

And if the generation time of the first diagnosis report is longer than that of the second diagnosis report, the first fault code is smaller than the second fault code.

5. The method of claim 2, wherein prior to said selecting M diagnostic reports having the same vehicle identification from among N diagnostic reports, further comprising:

receiving the N diagnosis reports sent by the diagnosis equipment; the diagnostic equipment is equipment for generating a diagnostic report after the vehicle is diagnosed.

6. The method of claim 1, wherein generating a service record for the vehicle based on the difference in the fault codes of the at least two diagnostic reports comprises:

and generating a maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports under the condition that the difference of the fault codes meets a preset standard.

7. The method of claim 1, wherein the service record comprises one or more of a service record ID, a self-increment ID, a vehicle VIN code, a vehicle brand, a vehicle model, a vehicle year, a diagnostic device serial number, a service facility name, a service facility address, a service facility contact, a service technician name, a service technician contact, a number of fault codes before service, fault code details before service, a number of fault codes after service, fault code details after service, a start service time, an end service time, a elapsed service time, and a service record generation time.

8. A vehicle service record generation apparatus, comprising:

and the generating unit is used for generating a maintenance record of the vehicle according to the difference of the fault codes of the at least two diagnosis reports.

9. A vehicle service record generation device comprising a processor, wherein the processor is configured to invoke a stored program to perform the method of any of claims 1-7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores program instructions that, when executed by a processor, cause the processor to perform the method of any of claims 1-7.