[0058] In order to explain the overall concept of the present application more clearly, the following detailed description is given by way of example in conjunction with the accompanying drawings.
[0059] The embodiment of the present application discloses a real-time maintenance method for a shared car, such as figure 1 shown, including the following steps:
[0060] Step 101, the server receives a fault maintenance request message from the terminal.
[0061] In the embodiment of the present application, the fault repair request message includes the geographic location information of the target shared car corresponding to the end user, the vehicle model of the target shared car, and the first fault data of the target shared car; wherein, the first fault data is generated by the end user. Confirmed failure data. For example, the user sends texts such as "vehicle damaged", "vehicle does not turn off", "tire abnormal", "unable to start" to the server through the mobile phone, and at the same time sends the corresponding photo to the server as the first fault data. In addition, the user can send the license plate number of the target shared car to the server, so that the server can determine the geographic location information of the target shared car and the vehicle model of the target shared car.
[0062] Step 102, the server collects the second fault data of the target shared car through the on-board diagnostic equipment of the target shared car.
[0063] In the embodiment of the present application, the on-board diagnostic equipment can enter the electronic control unit of the engine, gearbox, anti-lock braking system, etc. to read the fault code and other related data, and use the on-board communication system, such as GPS (Global Positioning System, Global Positioning System, system) navigation system or wireless communication to automatically send the vehicle's identity code, fault code and location information to the server.
[0064] The second fault data includes, but is not limited to: vibration signal of each bearing in the vehicle powertrain, fuel consumption parameter, throttle valve temperature parameter, intake pipe pressure parameter, intake air temperature parameter, intake air flow, and one or more of coolant temperature indivual. Among them, the vibration signal of each bearing is used to indicate the degree of wear of the bearing. This is because the bearing surface will be damaged to varying degrees due to fatigue after long-term operation, such as cracks and surface peeling, and the damage of the bearing surface can cause the bearing to vibrate. .
[0065] Step 103, the server determines the fault type of the target shared vehicle according to the first fault data and/or the second fault data in the fault repair request message.
[0066] Usually, the main control device on a shared car will prompt a fault in a certain part of the vehicle, but cannot indicate the cause of the failure. Maintenance personnel are required to conduct a comprehensive inspection, which reduces the real-time maintenance efficiency of the shared car. In order to solve the above problem, in the embodiment of the present application, the server determines the fault type of the target shared vehicle according to the first fault data and/or the second fault data, so that the maintenance personnel can judge the fault cause according to the fault type.
[0067] According to step 102, the data type of the first fault data may be text and pictures, and the data type of the second fault data may be vibration signals, fault codes, and signals corresponding to other sensors. Therefore, the server cannot directly use the first fault data and/or the second fault data for data processing, and needs to extract a plurality of fault characteristic data from the first fault data and/or the second fault data.
[0068] In order to more accurately determine the fault type, it is necessary to obtain fault feature data of multiple dimensions. However, multi-dimensionality will greatly increase the difficulty of data processing. Therefore, in the embodiment of the present application, it is necessary to reduce the dimension by merging the fault data set to reduce the difficulty of data processing. The specific steps are as follows:
[0069] First, each fault feature data is regarded as a fault data set, and the server determines the Euclidean distance between multiple fault data sets. For example, if there are fault data sets A, B, and C, then the server determines A and B respectively. The Euclidean distance of , the Euclidean distance between B and C, and the Euclidean distance between A and C. Then merge the two fault data sets with the smallest Euclidean distance.
[0070] The server repeatedly performs the step of determining the Euclidean distance and the step of merging the sets, until the Euclidean distance between any two fault data sets reaches a preset threshold. In the above loop process, only two fault data sets are merged in each loop process, and the Euclidean distance between the two merged fault data sets is the smallest, so as to ensure the unity of elements in the fault data set. For example, there are four fault characteristic data 1, 2, 3, and 4 corresponding to four fault data sets a, b, c, and d, respectively. If the Euclidean distance between set a and set b is the smallest and does not reach the preset threshold , then three sets of e, c, and d are obtained after merging, where the elements in set e are 1 and 2. At this time, if the Euclidean distance between set c and set e is the smallest and does not reach the preset threshold, then two sets f and d are obtained after merging, wherein the elements in set f are 1, 2, and 3.
[0071] Through the above method, the corresponding relationship between each fault characteristic data and the fault type is converted into the corresponding relationship between the fault data set and the fault type, thereby reducing the dimension of data processing. Finally, the server determines the fault type corresponding to each fault data set by using the fault feature data in each of the combined fault data sets. For example, the training vector of the artificial neural network is constructed by using the fault data set, so that the artificial neural network can determine the fault type according to the fault data set. After the training is completed, the artificial neural network will automatically determine the fault type corresponding to the target shared car when the artificial neural network will input vectors corresponding to the received first fault data and/or the second fault data.
[0072] Step 104, the server determines the corresponding target shared car according to one or more of the fault type of the target shared car, the geographic location information of the target shared car in the fault repair request message, and the vehicle model of the target shared car in the fault repair request message. maintenance node.
[0073] In the embodiment of this application, if only the geographic location information of the target shared vehicle is considered, the server can select the nearest maintenance node, which includes but is not limited to: individuals, enterprises, and 4S shops that provide vehicle maintenance services. In addition, the embodiments of the present application also provide two other methods for determining maintenance nodes:
[0074] In the first method, the server determines the preset area identifier corresponding to the target shared vehicle according to the geographic location information of the target shared vehicle, wherein the area identifier can be set by itself, such as areas A, B, and C, or it can be an administrative area. Logos corresponding to regions, such as logos corresponding to provinces, prefecture-level cities, and districts and counties.
[0075] According to the fault type of the target shared car and/or the vehicle model of the target shared car, the server determines a maintenance node set consisting of a plurality of maintenance nodes in the area corresponding to the preset area identifier. The server determines the selection range of a maintenance node in a specific area, so as to reduce the amount of data processing and improve the efficiency of vehicle maintenance. For example, if the target car-sharing vehicle model is Beijing Hyundai, if the search area is not limited, the server will search for Hyundai 4S stores across the country; if the search area is limited to Beijing, the server will only search for Hyundai 4S stores within Beijing, which greatly reduces the The workload of the server is reduced.
[0076] The server determines the geographic location information of each maintenance node in the maintenance node set, and then determines the maintenance node closest to the target shared vehicle according to the geographic location information of the target shared vehicle and the geographic location information of each maintenance node in the maintenance node set.
[0077] Compared with the first method, in the second method, the server also needs to define the region, and determine the set of maintenance nodes according to the fault type of the target shared vehicle and/or the vehicle model of the target shared vehicle. After that, the server will not specify the maintenance node according to the distance, but select the maintenance node in the way of order grabbing. For example, there are three maintenance nodes A, B, and C in the maintenance node set. The server broadcasts the maintenance order to the three maintenance nodes A, B, and C. If the maintenance node A receives the maintenance order and sends the order data to the server first, Then the server will choose A to repair the node.
[0078] It is understandable that the first method focuses on saving the time of sending the target shared car to the maintenance node, and the second method focuses on letting the maintenance node choose whether to accept the order according to its own busy business situation, so as to reduce the maintenance process of the shared car. waiting time in . In practical applications, the server can use the first method or the second method to select maintenance nodes according to actual scenarios, thereby improving maintenance efficiency.
[0079] Step 105, the server sends one or more of the fault type of the target shared car, the geographic location information of the target shared car, and the vehicle model of the target shared car to the maintenance node.
[0080] To sum up, the technical solutions provided by the embodiments of the present application improve maintenance efficiency from the aspects of fault diagnosis, maintenance node selection, and the like.
[0081] In order to facilitate the maintenance node to quickly receive the target shared car, in this embodiment of the present application, the server navigates the car pickup route of the maintenance node. For example, the server determines the geographic location information of the repair shop A after determining that the repair shop A is the maintenance node; and then determines the location information of the repair shop A to the target according to the geographic position information of the repair shop A and the geographic location information of the target shared car. The route data of the shared car; finally, the server sends the route data to A car repair shop.
[0082] Sometimes the failure of the shared car is caused by the user. In order to facilitate the determination of the responsible party, in the embodiment of the present application, the server obtains multiple travel route data and the travel time corresponding to each travel route data from the driving recording device on the target shared car. , that is, to obtain the driving trajectory of the target shared vehicle in each time period, and each time period can be divided by the parking time node; The information is stored correspondingly, that is, the first fault data and/or the second fault data, the driving route data, and the driving time are bound to the driver's identity information to clarify the responsible party; the server sends the corresponding stored data according to the driver's information. To the corresponding terminal, and receive the user signature data from the corresponding terminal, let the user confirm the stored data, and further clarify the responsible party.
[0083] After the shared vehicle is repaired, the shared car operating company usually sends maintenance personnel to the repair shop or 4S shop to check whether the vehicle is repaired, which takes up the maintenance personnel's work time. In order to solve the above problems, in the embodiment of the present application, After the server receives the vehicle maintenance completion information from the maintenance node, the server collects the status data of the target shared vehicle through the on-board diagnostic equipment on the target shared vehicle; the server determines the target according to the status data and the first fault data and/or the second fault data Share the maintenance results of the car and send the maintenance results to the maintenance node. It can be seen that the technical solutions proposed in the embodiments of the present application can realize remote online detection of the maintenance results of the shared vehicle, thereby improving the work efficiency of maintenance personnel.
[0084] In the embodiment of the present application, before the user uses the shared car, the server will recommend vehicle insurance and additional insurance to the user, for example, vehicle damage insurance, excluding deductible insurance. After the shared vehicle is repaired, the server will receive the repair bill data from the repair node. At this time, the server determines whether the end user purchases the corresponding insurance; after determining that the user purchases the insurance transaction, the server calculates the maintenance cost of the target shared car according to the failure type, maintenance bill data and the type of insurance.
[0085] like figure 2 As shown, the embodiment of the present application provides a real-time maintenance device for a shared car, including: a receiving module 201, a collection module 202, a data processing module 203, and a sending module 204;
[0086]The receiving module 201 is configured to receive a fault maintenance request message from the terminal, where the fault maintenance request message includes the geographic location information of the target shared car corresponding to the terminal user, the vehicle model of the target shared car and the first fault data of the target shared car; a fault data is the fault data determined by the end user;
[0087] The collection module 202 is used for collecting the second fault data of the target shared car through the on-board diagnostic equipment of the target shared car;
[0088] The data processing module 203 is configured to determine the fault type of the target shared vehicle according to the first fault data received by the receiving module 201 and/or the second fault data collected by the acquisition module 202;
[0089] The data processing module 203 is further configured to determine the maintenance node corresponding to the target shared car according to one or more of the fault type of the target shared car, the geographic location information of the target shared car, and the vehicle model of the target shared car;
[0090] The sending module 204 is configured to send one or more of the fault type of the target shared car, the geographic location information of the target shared car, and the vehicle model of the target shared car to the maintenance node.
[0091] like image 3 As shown, the embodiment of the present application provides a real-time maintenance system for a shared car, including: at least one terminal 301, at least one shared car 302, at least one maintenance node 303, and the real-time maintenance device 304 described in the above embodiments.
[0092] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for related parts, please refer to the partial descriptions of the method embodiments.
[0093] The above descriptions are merely examples of the present application, and are not intended to limit the present application. Various modifications and variations of this application are possible for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the scope of the claims of this application.
