WO2019218419A1 - Method and apparatus for determining vehicle maintenance scheme - Google Patents

Abstract

A method and apparatus for determining a vehicle maintenance scheme, the method comprising: receiving target malfunction information sent by a first terminal device; and matching the target malfunction information to maintenance material in a maintenance material database, and determining a target maintenance scheme, the maintenance material database storing historical malfunction information and historical research schemes. Hence, by using the provided method and apparatus for determining a vehicle maintenance scheme, a server may use the maintenance material database to accurately determine a target maintenance scheme since a large amount of historical malfunction information and historical research schemes corresponding to the historical malfunction information may be stored in the maintenance material database.

Description

Method and device for determining vehicle maintenance plan

The present application claims priority to Chinese Patent Application No. 201810458039.6 filed on May 14, 2018, the entire disclosure of which is incorporated herein by reference. In this application.

Technical field

The present application relates to the field of vehicles, and in particular to a method and apparatus for determining a vehicle maintenance solution.

Background technique

Vehicles such as automobiles are a common means of transportation, which brings great convenience to people's lives.

Understandably, the vehicle will inevitably fail during use. When the vehicle fails, you can usually go to the repair center for repair. However, with the development of vehicle technology, more and more new technologies are applied to vehicles. On the one hand, the maintenance personnel of the repair center may not have a high level of understanding of these new technologies; on the other hand, the maintenance level of the maintenance personnel may be limited, which may result in the maintenance personnel not being able to accurately locate the cause of the failure of the vehicle. A corresponding maintenance plan is available.

Therefore, it is necessary to provide a solution that can accurately give a vehicle maintenance plan.

Summary of the invention

The technical problem to be solved by the present application is that the maintenance personnel may not be able to accurately locate the cause of the failure of the vehicle, thereby providing a corresponding maintenance plan. A method and apparatus for determining a vehicle maintenance program is provided.

In a first aspect, an embodiment of the present application provides a method for determining a vehicle maintenance solution, which is applied to a server, including:

Receiving target fault information sent by the first terminal device;

Matching the target fault information with the maintenance data in the maintenance data database to determine the target maintenance plan;

The historical fault information and the historical maintenance plan are saved in the maintenance data database.

Optionally, the target fault information includes:

Symptom information, and/or diagnostic reports determined by diagnostic tool diagnostics.

Optionally, the method further includes:

Receiving target audio and/or video information related to the target fault information sent by the first terminal device;

Correspondingly, the target fault information is matched with the maintenance data in the maintenance data database to determine a target maintenance plan, including:

The target fault information and the target audio and/or video information are respectively matched with the repair data in the maintenance data database to determine a target maintenance plan.

Optionally, the method further includes:

Obtaining part information of the vehicle to be repaired;

Matching the part information with a maintenance case in the maintenance case database to determine a failure probability of each part of the vehicle to be repaired;

The target maintenance plan is corrected based on the failure probability of the respective parts.

Optionally, the obtaining part information of the vehicle to be repaired includes:

Obtaining the identification of the vehicle to be repaired

Matching the identifier of the vehicle to be repaired with a vehicle configuration database to obtain part information of the vehicle to be repaired.

Optionally, the maintenance case database includes any one or more of the following information:

Historical part failure claims replacement record data, historical vehicle maintenance data, historical part breakpoint information, and historical vehicle operational data.

Optionally, the method further includes:

Receiving maintenance result information sent by the first terminal device;

The maintenance result information is sent to the second terminal device.

Optionally, the method further includes:

Obtaining current operational data of the vehicle;

Using the current running data, predicting fault information of the vehicle that is faulty;

The fault information includes any one or more of the following:

The time range in which the vehicle has failed, the part in which the vehicle has failed, and the type of failure of the failed part.

Optionally, the using the current running data to predict fault information of the fault of the vehicle includes:

Using the current running data as an input of a fault prediction model, and predicting information related to the vehicle failure;

The fault prediction model is obtained by:

Obtaining historical running data; the historical running data is including running data when the vehicle fails;

The fault prediction model is obtained by training based on the historical running data and the fault information corresponding to the historical running data.

Optionally, the method further includes:

Transmitting the fault information to the second terminal device and/or the first terminal device.

Optionally, the method further includes:

Receiving a maintenance reservation request sent by the third terminal device;

Obtaining target information of the reserved vehicle;

Determining a target repair center according to the target information, and transmitting information of the target repair center to the third terminal device;

The target information of the reserved vehicle includes: historical maintenance center information of the reserved maintenance vehicle, and/or location information of the reserved maintenance vehicle.

Optionally, the maintenance reservation request carries a reference repair time; the method further includes:

Obtaining the occupational resource occupation of the target repair center during the reference maintenance period;

Determining a target repair time in conjunction with the reference repair time and resource occupancy of the target repair center during the reference repair period; and transmitting the target repair time to the third terminal device;

Wherein, the maintenance resource includes any one or more of the following:

The number of maintenance personnel, the number of maintenance tools, and the number of maintenance stations.

Optionally, if the target maintenance solution includes multiple maintenance items, the method further includes:

The maintenance sequence of each maintenance item is determined according to the occupation of the maintenance resources required for each maintenance project.

Optionally, the maintenance reservation request includes the fault information, and the method further includes:

A maintenance work order is generated based on the failure information, the identification of the scheduled maintenance vehicle, and the target repair time.

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

a first receiving unit, configured to receive target fault information sent by the first terminal device;

a first determining unit, configured to match the target fault information with the maintenance data in the maintenance data database to determine a target maintenance plan;

The historical fault information and the historical maintenance plan are saved in the maintenance data database.

Optionally, the target fault information includes:

Symptom information, and/or diagnostic reports determined by diagnostic tool diagnostics.

Optionally, the device further includes:

a second receiving unit, configured to receive target audio and/or video information related to the target fault information that is sent by the first terminal device;

Correspondingly, the first determining unit is specifically configured to:

The target fault information and the target audio and/or video information are respectively matched with the repair data in the maintenance data database to determine a target maintenance plan.

Optionally, the device further includes:

a first acquiring unit, configured to acquire part information of the vehicle to be repaired;

a second determining unit, configured to match the part information with a maintenance case in the maintenance case database, and determine a failure probability of each part of the to-be-maintained vehicle;

a correction unit configured to correct the target maintenance plan according to a failure probability of the respective parts.

Optionally, the first acquiring unit is specifically configured to:

Obtaining an identifier of the vehicle to be repaired;

Matching the identifier of the vehicle to be repaired with a vehicle configuration database to obtain part information of the vehicle to be repaired.

Optionally, the maintenance case database includes any one or more of the following information:

Historical part failure claims replacement record data, historical vehicle maintenance data, historical part breakpoint information, and historical vehicle operational data.

Optionally, the device further includes:

a third receiving unit, configured to receive maintenance result information sent by the first terminal device;

The first sending unit is configured to send the maintenance result information to the second terminal device.

Optionally, the device further includes:

a second acquiring unit, configured to acquire current running data of the vehicle;

a prediction unit, configured to predict, by using the current running data, fault information that the vehicle is faulty;

The fault information includes any one or more of the following:

The time range in which the vehicle has failed, the part in which the vehicle has failed, and the type of failure of the failed part.

Optionally, the prediction unit is specifically configured to:

Using the current running data as an input of a fault prediction model, and predicting information related to the vehicle failure;

The fault prediction model is obtained by:

Obtaining historical running data; the historical running data is including running data when the vehicle fails;

The fault prediction model is obtained by training based on the historical running data and the fault information corresponding to the historical running data.

Optionally, the device further includes:

a second sending unit, configured to send the fault information to the second terminal device and/or the first terminal device.

Optionally, the device further includes:

a fourth receiving unit, configured to receive a maintenance reservation request sent by the third terminal device;

a third obtaining unit, configured to acquire target information of the reserved vehicle;

a third determining unit, configured to determine a target repair center according to the target information, and send information of the target repair center to the third terminal device;

The target information of the reserved vehicle includes: historical maintenance center information of the reserved maintenance vehicle, and/or location information of the reserved maintenance vehicle.

Optionally, the maintenance reservation request carries a reference repair time; the device further includes:

a fourth obtaining unit, configured to acquire a maintenance resource occupation situation of the target repair center during the reference maintenance period;

a fourth determining unit, configured to determine a target maintenance time according to the reference maintenance time and resource occupation status of the target maintenance center in the reference maintenance time period; and send the target maintenance time to the third terminal device;

Wherein, the maintenance resource includes any one or more of the following:

The number of maintenance personnel, the number of maintenance tools, and the number of maintenance stations.

Optionally, if the target maintenance solution includes multiple maintenance items, the device further includes:

The fifth determining unit is configured to determine the maintenance sequence of each maintenance item according to the occupation status of the maintenance resources required for each maintenance item.

Optionally, the maintenance reservation request includes the fault information, and the device further includes:

And a generating unit, configured to generate a maintenance work order according to the fault information, the identifier of the reserved maintenance vehicle, and the target repair time.

Compared with the prior art, the embodiment of the present application has the following advantages:

The method and device for determining a vehicle maintenance solution provided by an embodiment of the present application, the method includes: receiving target failure information sent by a first terminal device; matching the target fault information with maintenance data in a maintenance data database to determine target maintenance The program includes a historical fault information and a historical research plan in the maintenance data database. It can be seen that, by using the method and device for determining a vehicle maintenance solution provided in the embodiment of the present application, since the maintenance data database can store a large number of historical research plans corresponding to historical fault information and historical fault information, the server can utilize the maintenance data. The database accurately determines the target maintenance plan.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application;

2 is a schematic flowchart of a method for determining a vehicle maintenance solution according to an embodiment of the present application;

3 is a schematic flowchart of modifying a target maintenance solution according to an embodiment of the present application;

4 is a schematic flowchart of a method for predicting fault information of a vehicle fault according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of a method for recommending a target repair center for an appointment maintenance vehicle according to an embodiment of the present application; FIG.

FIG. 6 is a flowchart of a method for determining a vehicle maintenance solution according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of an apparatus for determining a vehicle maintenance scheme according to an embodiment of the present application.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

The inventors of the present application have found through research that a vehicle may inevitably fail during use. When the vehicle fails, you can usually go to the repair center for repair. However, with the development of vehicle technology, more and more new technologies are applied to vehicles. On the one hand, the maintenance personnel of the repair center may not have a high level of understanding of these new technologies; on the other hand, the maintenance level of the maintenance personnel may be limited, which may result in the maintenance personnel not being able to accurately locate the cause of the failure of the vehicle. A corresponding maintenance plan is available.

In view of this, embodiments of the present application provide a method and apparatus for determining a vehicle maintenance solution, the method comprising: receiving target failure information sent by a first terminal device; and matching the target fault information with maintenance data in a maintenance data database Determining a target maintenance plan; wherein the maintenance information database stores historical failure information and a historical research plan. It can be seen that, by using the method and device for determining a vehicle maintenance solution provided in the embodiment of the present application, since the maintenance data database can store a large number of historical research plans corresponding to historical fault information and historical fault information, the server can utilize the maintenance data. The database accurately determines the target maintenance plan.

For the sake of understanding, the application scenario of the embodiment of the present application is first introduced.

FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application.

The first terminal device 110 may be a mobile terminal terminal device, for example, the first terminal device 110 may be a mobile terminal such as a smart phone or a tablet computer. For example, the first terminal device 110 may be a terminal device such as a desktop computer.

The first terminal device 110 can interact with the server 130 over a network. Specifically, the maintenance personnel may send the target fault information to the server 130 through the first terminal device 110, so that the server 130 determines the target maintenance plan according to the target fault information, and sends the target maintenance solution to the first terminal device 110 for maintenance. The personnel are repaired according to the target maintenance program.

The second terminal device 120 is a mobile terminal device. For example, the second terminal device 120 may be a mobile terminal such as a smart phone or a tablet computer. For example, the second terminal device 120 may be an on-board computer.

The second terminal device 110 can interact with the server 130 over the network. Specifically, the server 130 may acquire the current running data of the vehicle by using the second terminal device 110, and predict the fault information of the vehicle failure, and send the fault information to the second terminal device 120 to prompt the user that the vehicle may be faulty. The server 130 may further receive a maintenance reservation request sent by the second terminal device 120, acquire target information of the vehicle to be repaired, and send the target repair center to the second terminal device 120, thereby recommending the target repair center for the user.

Various non-limiting embodiments of the present application are described in detail below with reference to the accompanying drawings.

Exemplary method

Referring to FIG. 2 , it is a schematic flowchart of a method for determining a vehicle maintenance solution according to an embodiment of the present application.

The method for determining a vehicle maintenance solution provided by the embodiment of the present application may be applied to a server. The embodiment of the present application does not specifically limit the server.

The method for determining a vehicle maintenance solution provided by the embodiment of the present application can be implemented, for example, by the following steps S201-S202.

S201: Receive target fault information sent by the first terminal device.

As described above, the first terminal device is a maintenance center terminal device.

The target failure information mentioned in the embodiment of the present application refers to information that may be related to the failure of the vehicle to be repaired.

The target fault information is not specifically limited in the embodiment of the present application. As an example, the target fault information may include: fault phenomenon information, and/or a diagnostic report determined by a diagnostic tool diagnosis.

The fault phenomenon information refers to the abnormal phenomenon information of the vehicle to be repaired, and may include, for example, an abnormal sound of the engine, an abnormal flashing of the vehicle lamp, and the like. The fault phenomenon information may be information that the user verbally describes to the maintenance personnel, or may be information discovered by the maintenance personnel when checking the vehicle to be repaired.

It can be understood that, for the description of the vehicle fault phenomenon, the fault of the vehicle to be repaired is often not fully reflected by observation or simple inspection, and the fault information of each module on the vehicle to be repaired can also be read by using the diagnostic tool to generate a diagnosis report.

S202: Match the target fault information with the maintenance data in the maintenance data database to determine a target maintenance plan. The historical fault information and the historical maintenance plan are saved in the maintenance data database.

It should be noted that the maintenance data database mentioned in the embodiment of the present application can store a large amount of historical fault information and a historical maintenance plan. Specifically, the historical maintenance plan may include a parts disassembly manual, a principle manual, a Diagnostic Trouble Code (DTC) manual, a circuit diagram, and a connector. Other information may be included, which is not specifically limited in the embodiment of the present application.

It can be understood that the maintenance data database stores a historical research plan corresponding to a large amount of historical fault information and historical fault information. Therefore, the target fault information can be matched with the historical fault information in the maintenance data database. If the target fault information is successfully matched with a certain historical fault information, the historical maintenance scheme corresponding to the historical fault information may be used as the target maintenance scheme.

It should be noted that, in the embodiment of the present application, the target maintenance solution may include, for example, a maintenance item, a repair time, a maintenance personnel level, a maintenance tool, a maintenance station, and the like. For example, the target maintenance plan can be as shown in Table 1 below.

Table 1

The server may also transmit operational video and/or operational audio associated with the target maintenance plan to the first terminal device to assist the maintenance personnel in performing the repair.

It can be seen that, by using the method and device for determining a vehicle maintenance solution provided in the embodiment of the present application, since the maintenance data database can store a large number of historical research plans corresponding to historical fault information and historical fault information, the server can utilize the maintenance data. The database accurately determines the target maintenance plan.

Considering the actual application, the utilization of the target fault information may not well reflect the current state of the vehicle to be repaired, and therefore, in order to better reflect the current state of the vehicle to be repaired, thereby making the determined target The maintenance plan is more accurate. In a possible implementation state of the embodiment of the present application, the server may further combine the audio and/or video information related to the target fault information sent by the first terminal device, and the target fault information and The audio and/or video information is respectively matched with the maintenance data in the maintenance data database to determine a target maintenance plan.

It should be noted that the maintenance personnel can record the audio and/or video information of the vehicle to be repaired on site, and send the audio and/or video information to the server through the first terminal device.

It can be understood that historical audio information and/or video information may be included in the historical fault information in the maintenance data database. Therefore, after receiving the target audio and/or video information, the server may The target audio and/or video information is respectively matched with the maintenance data in the maintenance data database to determine a target maintenance plan.

It should be noted that, in order to further improve the accuracy of the target maintenance solution, in a possible implementation manner of the embodiment of the present application, the method for determining a vehicle maintenance solution may further include the following steps S301-S303.

S301: Obtain part information of the vehicle to be repaired.

It should be noted that the part information of the vehicle to be repaired mentioned in the embodiment of the present application may be part information of all parts included in the vehicle to be repaired, and may also include parts of the parts included in the target maintenance plan. information. The embodiment of the present application is not specifically limited.

Specifically, when the part information is part information of a part included in the target maintenance plan, the server may extract the part information from the target maintenance plan.

When the part information is the part information of all the parts included in the vehicle to be repaired, the part information of the to-be-maintained vehicle may be acquired by using the following steps A-B.

Step A: obtaining an identifier of the vehicle to be repaired;

It should be noted that each vehicle has a unique identifier, and the identifier of the vehicle to be repaired is used to uniquely identify the vehicle to be repaired.

It should be noted that the embodiment of the present application does not specifically limit the identifier of the vehicle to be repaired. As an example, the identifier of the vehicle to be repaired may be a feature code of the vehicle to be repaired. As another example, the The identification of the maintenance vehicle may be a Vehicle Identification Number (VIN) of the vehicle to be repaired.

The embodiment of the present application does not specifically limit the specific implementation manner of obtaining the identifier of the vehicle to be repaired. As an example, the target fault information may include the identifier of the vehicle to be repaired, so the server may be from the target. The identification of the vehicle to be repaired is extracted from the fault information.

Step B: Matching the identifier of the vehicle to be repaired with a vehicle configuration database to obtain part information of the vehicle to be repaired.

It should be noted that a plurality of vehicle identifiers may be stored in the vehicle configuration database with configuration information corresponding to the vehicle identifier, and the configuration information may include part information.

Therefore, after determining the identification of the vehicle to be repaired, the vehicle configuration database may be used to determine part information of the vehicle to be repaired.

S302: Match the part information with a maintenance case in the maintenance case database to determine a failure probability of each part of the to-be-maintained vehicle.

S303: Correct the target maintenance plan according to the failure probability of each component.

Regarding S302-S303, it should be noted that the maintenance case database includes a plurality of historical maintenance cases, and the historical maintenance case may include information such as fault parts.

Specifically, the maintenance case database may include any one or more of the following information:

Historical part failure claims replacement record data, historical vehicle maintenance data, historical part breakpoint information, and historical vehicle operational data.

The historical vehicle maintenance data may include specific data of the maintenance, and specifically includes any one or more of maintenance items, maintenance tools, maintenance time, maintenance location, maintenance personnel level, and the like.

Among them, the historical part breakpoint information refers to the time information for optimizing the part.

Therefore, in conjunction with the maintenance case database, it is possible to determine the probability of failure of each part of the vehicle to be repaired. Thereby the target maintenance plan is corrected according to the failure probability of each part.

The embodiment of the present application does not specifically limit the specific implementation manner of the target maintenance scheme by using the failure probability of the respective parts. As an example, the failure probability of each component may be sorted from high to low to determine the maintenance sequence. Parts with high probability correspond to the maintenance sequence.

It should be noted that, after the repair is performed according to the target maintenance information, the fault is still not solved. For this case, the maintenance personnel may send the repair data in the repair process to the server through the first terminal device, so that the server according to the The repair data during the repair process further identifies the new target repair plan.

It should be noted that, in the embodiment of the present application, after the maintenance of the vehicle to be repaired is completed, the maintenance data of the to-be-maintained vehicle may be stored in the maintenance case database, and the target failure information and the target maintenance may be performed. The program stores values in the maintenance data database.

It is to be understood that in a practical application, the user may wish to know the maintenance progress. Therefore, in a possible implementation manner of the embodiment of the present application, the server may further receive the service result information sent by the first terminal device, where The maintenance result information is sent to the second terminal device.

As described above, the second terminal device is a client terminal device, and details are not described herein again.

It can be understood that, in the embodiment of the present application, when the maintenance personnel completes a maintenance project, the maintenance result may be sent to the server through the first terminal device, so that the server sends the maintenance result to the second terminal device, thereby This allows users to understand the progress of the repair in real time and enhance the user experience.

Understandably, in practical applications, the vehicle is likely to malfunction during driving, which brings inconvenience to the user.

Therefore, in a possible implementation manner of the embodiment of the present application, the fault information of the vehicle failure may also be predicted, so as to remind the user that the vehicle may be faulty, so that the user prepares for maintenance in advance.

Referring to FIG. 4 , it is a schematic flowchart of a method for predicting fault information of a vehicle fault according to an embodiment of the present application.

The method of predicting failure information of a vehicle failure may be implemented, for example, by the following steps S401-S402.

S401: Acquire current running data of the vehicle.

It should be noted that the specific implementation manner of acquiring current running data of the vehicle is not specifically limited in the embodiment of the present application. As an example, the onboard monitoring device on the vehicle can transmit the monitored current operational data to the server.

S402: Using the current running data, predicting fault information that the vehicle is faulty.

It should be noted that the fault information mentioned in the embodiment of the present application may include any one or more of the following:

The time range in which the vehicle has failed, the part in which the vehicle has failed, and the type of failure of the failed part.

The time range in which the vehicle fails may include, for example, the next 7 days to 9 days.

The part in which the vehicle has failed may, for example, include an engine, and may include, for example, a battery.

Correspondingly, the fault type of the faulty component may include, for example, an abnormal sound from the engine, and may include a battery failure, such that the vehicle fails to start.

It can be understood that the fault information of the vehicle failure has a certain relationship with the current running data of the vehicle. Therefore, the current operating data can be utilized to predict the fault information of the vehicle that is faulty.

The specific implementation of the step S402 is not specifically limited in the embodiment of the present application. As an example, in the specific implementation, the current running data may be used as an input of a fault prediction model to predict information about a fault of the vehicle. .

The fault prediction model can be obtained by the following steps C-D:

Step C: Acquire historical running data; the historical running data includes running data when the vehicle fails.

As described above, the historical vehicle operating data may be included in the maintenance case database, and thus the historical operational data may be obtained from the maintenance case database.

Step D: Training based on the historical running data and the fault information corresponding to the historical running data to obtain the fault prediction model.

It can be understood that, after the historical running data is trained according to the fault information corresponding to the historical running data, the parameters of the fault prediction model may be determined, thereby obtaining the fault prediction model.

It should be noted that, in a possible implementation manner of the embodiment of the present application, the fault prediction model may include multiple sub-models, and each sub-model corresponds to one or more parts. For example, the failure prediction model includes an engine failure prediction submodel, a battery failure prediction submodel, and the like.

In a possible implementation manner of the embodiment of the present application, after the server predicts the fault information, the fault information may be sent to the first terminal device and/or the second terminal device. It can be understood that sending the fault information to the first terminal device may prompt the maintenance personnel to prepare for maintenance. Sending to the second terminal device can prompt the user for a possible malfunction of the vehicle, so that the user can arrange the vehicle maintenance in advance.

It should be noted that, in a possible implementation manner of the embodiment of the present application, after determining the part in which the vehicle is faulty, the server may query, from the historical maintenance case database, a part corresponding to the part in which the vehicle is faulty. If the part breakpoint information does not query the part breakpoint information corresponding to the part in which the vehicle has failed, it indicates that the part in which the vehicle has failed is likely to malfunction. Therefore, the server can generate corresponding alarm information, and send the alarm information to the terminal device of the vehicle manufacturer to remind the relevant personnel of the vehicle manufacturer to monitor the part.

It should be noted that after receiving the fault information and/or the alarm information sent by the server, the first terminal device may reserve the repair center to perform maintenance on the vehicle. In the following embodiments, the vehicle scheduled to be repaired is referred to as an appointment maintenance vehicle.

In view of this, in the embodiment of the present application, the server may also recommend a target repair center for the scheduled maintenance vehicle.

Referring to FIG. 5, it is a schematic flowchart of a method for recommending a target repair center for an appointment maintenance vehicle according to an embodiment of the present application.

A schematic flowchart of a method for recommending a target repair center for an appointment maintenance vehicle is provided in the embodiment of the present application.

The method for recommending a target repair center for an appointment maintenance vehicle provided by the embodiment of the present application can be implemented, for example, by the following steps S501-S503.

S501: Receive a maintenance reservation request sent by the third terminal device.

It should be noted that the third terminal device mentioned in the embodiment of the present application is a user terminal device, which is similar to the second terminal device, and the third terminal device may be a mobile terminal such as a smart phone or a tablet computer; For example, the third terminal device can be an onboard computer.

It should be noted that the second terminal device and the third terminal device may be the same terminal device or different terminal devices. For example, the user uses the onboard computer to receive the fault information and/or alarm information sent by the server, and then uses the tablet computer to make a maintenance appointment. For another example, the user uses the tablet to receive the fault information and/or alarm information sent by the server, and then uses the tablet to make a maintenance appointment.

The specific content of the maintenance reservation request is not specifically limited in the embodiment of the present application. The third terminal device sends the maintenance reservation request, for example, a button may be clicked on a certain interaction interface of the third terminal device.

S502: Acquire target information of the reserved vehicle.

It should be noted that the target information of the reserved vehicle includes: historical maintenance center information of the reserved maintenance vehicle, and/or location information of the reserved maintenance vehicle.

The embodiment of the present application does not specifically limit the specific manner of obtaining the target information of the reserved vehicle. As an example, the target information of the reserved vehicle may be queried from the maintenance case database.

S503: Determine a target repair center according to the target information, and send information of the target repair center to the third terminal device.

Considering that a historical repair center may be a familiar repair center, users are more likely to prefer to go to the historical repair center to repair the vehicle. In addition, the distance to the repair center is another factor that the user considers. Therefore, the target repair center can be determined based on the target information.

In step S503, in combination with the historical maintenance center information of the user, and the distance between the location of the scheduled maintenance vehicle and the historical maintenance center, the target maintenance center may be determined. As an example, a historical service center in which the number of times the user repairs the vehicle is greater than a first threshold and the distance from the reserved service vehicle is greater than a second threshold may be selected as the target service center.

As described above, the embodiment of the present application does not specifically limit the specific content of the maintenance reservation request. In a possible implementation manner of the embodiment of the present application, the maintenance reservation request carries a reference repair time. The reference repair time can be understood as the user's idle time, that is, the user can send the scheduled maintenance vehicle to the target repair center for repair at the reference repair time.

It should be noted that the reference repair time may include several times. For example, the reference repair time may be 2018-05-03 9:00 am to 5:00 pm and 2018-05-04 9:00 am to 4 pm :00.

Considering that the maintenance service of the target service center is limited, after receiving the service reservation request, the server further determines whether the target service center has sufficient maintenance resources for the reservation within the reference repair time range. Repair the vehicle for repair.

In view of this, the method may further include the following steps E-F.

Step E: Obtain the occupational resource occupation of the target repair center during the reference maintenance period.

It should be noted that the target repair center can send its resource occupancy to the server. Therefore, the server can obtain the maintenance resource occupancy of the target repair center during the reference maintenance period.

Step F: determining a target maintenance time according to the reference maintenance time and the resource occupation status of the target maintenance center in the reference maintenance time period; and transmitting the target maintenance time to the third terminal device.

Wherein, the maintenance resource includes any one or more of the following:

The number of maintenance personnel, the number of maintenance tools, and the number of maintenance stations.

If the target maintenance is in the first time period and there is sufficient maintenance resources to repair the scheduled maintenance vehicle, the first time period is taken as the target maintenance time. The first time period may be a certain time period of the scheduled maintenance time.

It can be understood that, by using the method provided by the embodiment of the present application, since the target maintenance time is determined according to the resource occupation condition of the target maintenance center, it can be ensured that the scheduled maintenance vehicle is in the target maintenance time period. service. Avoiding the problem of user queuing caused by limited maintenance resources when the maintenance vehicle is scheduled to be repaired at the target service center improves the user experience.

In a possible implementation manner of the embodiment of the present application, if the target maintenance solution includes multiple maintenance items, the maintenance sequence of each maintenance item may also be determined according to the occupation status of the maintenance resources required for each maintenance item.

For example, the target maintenance plan is shown in Table 1. At present, the occupancy rate of primary service technicians and elevator stations is 90% and 70% respectively, and the occupancy rate of primary service technicians and elevator stations is expected to decrease after 1 hour. However, the occupancy rate of senior service technicians and open space stations is only 30% and 0%. Therefore, the senior maintenance technicians with the highest historical repair rate for engine faults are screened and assigned to the open space station, and the maintenance of work 2/3/4/5 is started.

In order to facilitate the management of the maintenance data in the maintenance center, in a possible implementation manner of the embodiment of the present application, the requesting the maintenance reservation request may include the fault information, and the server may The identification of the vehicle and the target repair time generate a repair work order.

It can be understood that, for the scheduled maintenance vehicle, the method for determining the vehicle maintenance scheme described above can be employed to determine the target maintenance plan. In the embodiment of the present application, part or all of the content included in the target maintenance plan may also be added to the maintenance work order, and the content of the maintenance work order is updated in real time according to the maintenance progress.

The above describes the method for determining a vehicle maintenance solution provided by the embodiment of the present application, and the method is introduced in combination with a specific scenario.

In this scenario, the user finds that the engine is making an abnormal sound and the fault light is on, so the user drives the vehicle to the repair center for repair.

Referring to FIG. 6 , it is a flowchart of a method for determining a vehicle maintenance solution according to an embodiment of the present application.

The method for determining a vehicle maintenance solution provided by the embodiment of the present application can be implemented, for example, by the following steps S601-S612.

S601: The maintenance personnel introduces the target fault information through the first terminal device.

S602: The first terminal device prompts the maintenance personnel to supplement the fault sound/video information, and gives a reference example of the supplementary information. The service technician obtains the relevant audio/video information as required and inputs it through the first terminal device.

S603: The server matches the maintenance data database according to the target fault information and the fault sound/video information, and obtains a target maintenance plan.

For example, the target maintenance program consists of two maintenance items, namely: 1. Check the turbocharger solenoid valve line. 2. Check/replace the turbocharger solenoid valve.

S604: The server acquires part information of the vehicle to be repaired; and matches the part information with the maintenance case in the maintenance case database to determine a failure probability of each part of the to-be-maintained vehicle.

For example, the server identified four component failures, namely: 1. The turbocharger solenoid valve line failure rate was 29%. 2. The turbocharger solenoid valve failure rate is 38%.

S605: Correct the target maintenance plan according to the failure probability of each component.

For example, the revised target maintenance plan is: 1. Check/replace the turbocharger solenoid valve. 2. Check the turbocharger solenoid valve circuit.

The server may send the corrected target maintenance plan to the first terminal device, and the maintenance personnel may view the corrected target maintenance plan through the display screen of the first terminal device.

S606: The server sends information about the function principle of the turbocharger solenoid valve, the disassembly and assembly guide, the connector information, the inspection measurement method, the measurement standard data, and the like to the first terminal device.

The maintenance personnel can view the functional principle introduction, disassembly and assembly guidance, connector information, inspection measurement method, measurement standard data and the like related to the turbocharger solenoid valve through the display screen of the first terminal device.

S607: The maintenance personnel completed the inspection according to the instructions, and the inspection result showed no abnormality. And using the first terminal device to send the inspection result to the server by voice/text/click.

S608: The server sends information about the functional principle of the components related to checking the turbocharger solenoid valve line, the disassembly and assembly guide, the connector information, the inspection measurement method, the measurement standard data, and the like to the first terminal device.

The maintenance personnel can view the functional principle introduction, disassembly and assembly guide, connector information, inspection measurement method, measurement standard data and the like related to the turbocharger solenoid valve line through the display screen of the first terminal device.

S609: The maintenance personnel completed the inspection according to the instructions, and no abnormalities were found in the inspection results. And using the first terminal device to send the inspection result to the server by voice/text/click.

S610: The maintenance personnel sends the maintenance data during the maintenance process to the server through the first terminal device.

S611: The server obtains a new target maintenance plan according to the maintenance data in the maintenance process, and sends a new target maintenance plan to the first terminal device. The relevant circuit diagram, connector information, disassembly instructions, inspection measurement methods, measurement standard data and other information are sent to the first terminal device.

The new maintenance plan can be, for example: 1. Check the engine computer network communication line. 2. Check/replace the gateway module.

S612: After the maintenance personnel check according to the guidance, the internal fault of the gateway module is found, which causes the abnormal fluctuation of the communication line voltage to affect the engine computer control module, and the fault is eliminated after replacing the gateway module. Send the repair results to the server.

Exemplary device

Referring to FIG. 7, the figure is a schematic structural diagram of an apparatus for determining a vehicle maintenance solution according to an embodiment of the present application. The device 700 may specifically include, for example, a first receiving unit 710 and a first determining unit 720.

The first receiving unit 710 is configured to receive target fault information sent by the first terminal device.

The first determining unit 720 is configured to match the target fault information with the maintenance data in the maintenance data database to determine a target maintenance plan;

The historical fault information and the historical maintenance plan are saved in the maintenance data database.

Optionally, the target fault information includes:

Symptom information, and/or diagnostic reports determined by diagnostic tool diagnostics.

Optionally, the device 700 further includes:

a second receiving unit, configured to receive target audio and/or video information related to the target fault information that is sent by the first terminal device;

Correspondingly, the first determining unit 720 is specifically configured to:

The target fault information and the target audio and/or video information are respectively matched with the repair data in the maintenance data database to determine a target maintenance plan.

Optionally, the device 700 further includes:

a first acquiring unit, configured to acquire part information of the vehicle to be repaired;

a second determining unit, configured to match the part information with a maintenance case in the maintenance case database, and determine a failure probability of each part of the to-be-maintained vehicle;

a correction unit configured to correct the target maintenance plan according to a failure probability of the respective parts.

Optionally, the first acquiring unit is specifically configured to:

Obtaining an identifier of the vehicle to be repaired;

Matching the identifier of the vehicle to be repaired with a vehicle configuration database to obtain part information of the vehicle to be repaired.

Optionally, the maintenance case database includes any one or more of the following information:

Historical part failure claims replacement record data, historical vehicle maintenance data, historical part breakpoint information, and historical vehicle operational data.

Optionally, the device 700 further includes:

a third receiving unit, configured to receive maintenance result information sent by the first terminal device;

The first sending unit is configured to send the maintenance result information to the second terminal device.

Optionally, the device 700 further includes:

a second acquiring unit, configured to acquire current running data of the vehicle;

a prediction unit, configured to predict, by using the current running data, fault information that the vehicle is faulty;

The fault information includes any one or more of the following:

The time range in which the vehicle has failed, the part in which the vehicle has failed, and the type of failure of the failed part.

Optionally, the prediction unit is specifically configured to:

Using the current running data as an input of a fault prediction model, and predicting information related to the vehicle failure;

The fault prediction model is obtained by:

Obtaining historical running data; the historical running data is including running data when the vehicle fails;

The fault prediction model is obtained by training based on the historical running data and the fault information corresponding to the historical running data.

Optionally, the device 700 further includes:

a second sending unit, configured to send the fault information to the second terminal device and/or the first terminal device.

Optionally, the device 700 further includes:

a fourth receiving unit, configured to receive a maintenance reservation request sent by the third terminal device;

a third obtaining unit, configured to acquire target information of the reserved vehicle;

a third determining unit, configured to determine a target repair center according to the target information, and send information of the target repair center to the third terminal device;

The target information of the reserved vehicle includes: historical maintenance center information of the reserved maintenance vehicle, and/or location information of the reserved maintenance vehicle.

Optionally, the maintenance reservation request carries a reference repair time; the device 700 further includes:

a fourth obtaining unit, configured to acquire a maintenance resource occupation situation of the target repair center during the reference maintenance period;

a fourth determining unit, configured to determine a target maintenance time according to the reference maintenance time and resource occupation status of the target maintenance center in the reference maintenance time period; and send the target maintenance time to the third terminal device;

Wherein, the maintenance resource includes any one or more of the following:

The number of maintenance personnel, the number of maintenance tools, and the number of maintenance stations.

Optionally, if the target maintenance solution includes multiple maintenance items, the device 700 further includes:

The fifth determining unit is configured to determine the maintenance sequence of each maintenance item according to the occupation status of the maintenance resources required for each maintenance item.

Optionally, the service reservation request includes the fault information, and the apparatus 700 further includes:

And a generating unit, configured to generate a maintenance work order according to the fault information, the identifier of the reserved maintenance vehicle, and the target repair time.

For a description of each unit of the apparatus 700, reference may be made to the description part of the above method embodiment, and details are not described herein again.

It can be seen that, by using the device for determining the vehicle maintenance scheme provided in the embodiment of the present application, since the maintenance data database can store a large amount of historical research information corresponding to the historical fault information and the historical fault information, the server can use the maintenance data database to be accurate. Determine the target maintenance plan.

The above description is only a preferred embodiment of the present application, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present application. It should be considered as the scope of protection of this application.

Claims (28)

1. A method for determining a vehicle maintenance solution, characterized by being applied to a server, comprising:

   Receiving target fault information sent by the first terminal device;

   Matching the target fault information with the maintenance data in the maintenance data database to determine the target maintenance plan;

   The historical fault information and the historical maintenance plan are saved in the maintenance data database.
2. The method according to claim 1, wherein the target failure information comprises:

   Symptom information, and/or diagnostic reports determined by diagnostic tool diagnostics.
3. The method of claim 1 further comprising:

   Receiving target audio and/or video information related to the target fault information sent by the first terminal device;

   Correspondingly, the target fault information is matched with the maintenance data in the maintenance data database to determine a target maintenance plan, including:

   The target fault information and the target audio and/or video information are respectively matched with the repair data in the maintenance data database to determine a target maintenance plan.
4. The method of claim 1 further comprising:

   Obtaining part information of the vehicle to be repaired;

   Matching the part information with a maintenance case in the maintenance case database to determine a failure probability of each part of the vehicle to be repaired;

   The target maintenance plan is corrected based on the failure probability of the respective parts.
5. The method according to claim 4, wherein the obtaining part information of the vehicle to be repaired comprises:

   Obtaining the identification of the vehicle to be repaired

   Matching the identifier of the vehicle to be repaired with a vehicle configuration database to obtain part information of the vehicle to be repaired.
6. The method of claim 4 wherein said repair case database includes any one or more of the following:

   Historical part failure claims replacement record data, historical vehicle maintenance data, historical part breakpoint information, and historical vehicle operational data.
7. The method of claim 1 further comprising:

   Receiving maintenance result information sent by the first terminal device;

   The maintenance result information is sent to the second terminal device.
8. The method of claim 1 further comprising:

   Obtaining current operational data of the vehicle;

   Using the current running data, predicting fault information of the vehicle that is faulty;

   The fault information includes any one or more of the following:

   The time range in which the vehicle has failed, the part in which the vehicle has failed, and the type of failure of the failed part.
9. The method according to claim 8, wherein the predicting failure information of the vehicle by using the current running data comprises:

   Using the current running data as an input of a fault prediction model, and predicting information related to the vehicle failure;

   The fault prediction model is obtained by:

   Obtaining historical running data; the historical running data is including running data when the vehicle fails;

   The fault prediction model is obtained by training based on the historical running data and the fault information corresponding to the historical running data.
10. The method of claim 8 further comprising:

    Transmitting the fault information to the second terminal device and/or the first terminal device.
11. The method of claim 1 further comprising:

    Receiving a maintenance reservation request sent by the third terminal device;

    Obtaining target information of the reserved vehicle;

    Determining a target repair center according to the target information, and transmitting information of the target repair center to the third terminal device;

    The target information of the reserved vehicle includes: historical maintenance center information of the reserved maintenance vehicle, and/or location information of the reserved maintenance vehicle.
12. The method according to claim 11, wherein the maintenance reservation request carries a reference repair time; the method further comprises:

    Obtaining the occupational resource occupation of the target repair center during the reference maintenance period;

    Determining a target repair time in conjunction with the reference repair time and resource occupancy of the target repair center during the reference repair period; and transmitting the target repair time to the third terminal device;

    Wherein, the maintenance resource includes any one or more of the following:

    The number of maintenance personnel, the number of maintenance tools, and the number of maintenance stations.
13. The method of claim 12, wherein if the target maintenance plan comprises a plurality of maintenance items, the method further comprises:

    The maintenance sequence of each maintenance item is determined according to the occupation of the maintenance resources required for each maintenance project.
14. The method of claim 12, wherein the maintenance reservation request includes the fault information, the method further comprising:

    A maintenance work order is generated based on the failure information, the identification of the scheduled maintenance vehicle, and the target repair time.
15. An apparatus for determining a vehicle maintenance solution, comprising:

    a first receiving unit, configured to receive target fault information sent by the first terminal device;

    a first determining unit, configured to match the target fault information with the maintenance data in the maintenance data database to determine a target maintenance plan;

    The historical fault information and the historical maintenance plan are saved in the maintenance data database.
16. The device according to claim 15, wherein the target failure information comprises:

    Symptom information, and/or diagnostic reports determined by diagnostic tool diagnostics.
17. The device according to claim 15, wherein the device further comprises:

    a second receiving unit, configured to receive target audio and/or video information related to the target fault information that is sent by the first terminal device;

    Correspondingly, the first determining unit is specifically configured to:

    The target fault information and the target audio and/or video information are respectively matched with the repair data in the maintenance data database to determine a target maintenance plan.
18. The device according to claim 15, wherein the device further comprises:

    a first acquiring unit, configured to acquire part information of the vehicle to be repaired;

    a second determining unit, configured to match the part information with a maintenance case in the maintenance case database, and determine a failure probability of each part of the to-be-maintained vehicle;

    a correction unit configured to correct the target maintenance plan according to a failure probability of the respective parts.
19. The device according to claim 18, wherein the first obtaining unit is specifically configured to:

    Obtaining an identifier of the vehicle to be repaired;

    Matching the identifier of the vehicle to be repaired with a vehicle configuration database to obtain part information of the vehicle to be repaired.
20. The apparatus according to claim 18, wherein said maintenance case database contains any one or more of the following information:

    Historical part failure claims replacement record data, historical vehicle maintenance data, historical part breakpoint information, and historical vehicle operational data.
21. The device according to claim 15, wherein the device further comprises:

    a third receiving unit, configured to receive maintenance result information sent by the first terminal device;

    The first sending unit is configured to send the maintenance result information to the second terminal device.
22. The device according to claim 15, wherein the device further comprises:

    a second acquiring unit, configured to acquire current running data of the vehicle;

    a prediction unit, configured to predict, by using the current running data, fault information that the vehicle is faulty;

    The fault information includes any one or more of the following:

    The time range in which the vehicle has failed, the part in which the vehicle has failed, and the type of failure of the failed part.
23. The device according to claim 22, wherein the prediction unit is specifically configured to:

    Using the current running data as an input of a fault prediction model, and predicting information related to the vehicle failure;

    The fault prediction model is obtained by:

    Obtaining historical running data; the historical running data is including running data when the vehicle fails;

    The fault prediction model is obtained by training based on the historical running data and the fault information corresponding to the historical running data.
24. The device of claim 22, wherein the device further comprises:

    a second sending unit, configured to send the fault information to the second terminal device and/or the first terminal device.
25. The device according to claim 15, wherein the device further comprises:

    a fourth receiving unit, configured to receive a maintenance reservation request sent by the third terminal device;

    a third obtaining unit, configured to acquire target information of the reserved vehicle;

    a third determining unit, configured to determine a target repair center according to the target information, and send information of the target repair center to the third terminal device;

    The target information of the reserved vehicle includes: historical maintenance center information of the reserved maintenance vehicle, and/or location information of the reserved maintenance vehicle.
26. The device according to claim 25, wherein the maintenance reservation request carries a reference repair time; the device further comprises:

    a fourth obtaining unit, configured to acquire a maintenance resource occupation situation of the target repair center during the reference maintenance period;

    a fourth determining unit, configured to determine a target maintenance time according to the reference maintenance time and resource occupation status of the target maintenance center in the reference maintenance time period; and send the target maintenance time to the third terminal device;

    Wherein, the maintenance resource includes any one or more of the following:

    The number of maintenance personnel, the number of maintenance tools, and the number of maintenance stations.
27. The apparatus of claim 26, wherein if the target maintenance plan comprises a plurality of maintenance items, the apparatus further comprises:

    The fifth determining unit is configured to determine the maintenance sequence of each maintenance item according to the occupation status of the maintenance resources required for each maintenance item.
28. The device according to claim 26, wherein the maintenance reservation request includes the failure information, and the device further comprises:

    And a generating unit, configured to generate a maintenance work order according to the fault information, the identifier of the reserved maintenance vehicle, and the target repair time.

Images