Maintenance recommendation method, device, electronic device and storage medium based on sharing

Abstract

The present application provides a maintenance recommendation method, device, electronic device and storage medium based on sharing, which relates to the field of maintenance information processing technology. The key points of the technical solution are: when receiving a vehicle maintenance request or a request to generate a vehicle maintenance request, determine whether the target vehicle belongs to a shared group; when the target vehicle belongs to the shared group, determine whether there are other first vehicles undergoing maintenance in the shared group; if there are other first vehicles undergoing maintenance in the shared group, generate a maintenance recommendation result with shared information on the right to use the first vehicle. The maintenance recommendation method, device, electronic device and storage medium based on sharing provided by the present application have the advantages of improving the efficiency of resource utilization during vehicle maintenance and providing car owners with more convenient vehicle selection.

Description

Technical Field

[0001] The present application relates to the technical field of maintenance information processing, and in particular to a maintenance recommendation method, device, electronic device and storage medium based on sharing. Background Art

[0002] In modern urban transportation systems, operating vehicles (such as taxis, online ride-hailing vehicles, etc.) play an increasingly important role. The continued operation of these vehicles is essential to meet the public's travel needs. However, all motor vehicles require regular maintenance and servicing (hereinafter referred to as "maintenance") to ensure their safety and reliability. For operating vehicles, downtime during maintenance directly affects operational efficiency and economic benefits.

[0003] Traditional maintenance management methods for operating vehicles mainly adopt regular maintenance plans and predictive maintenance. Regular maintenance plans pre-arrange maintenance time based on vehicle usage time or mileage. Although this method helps to ensure the vehicle status, it often causes the vehicle to stop operating at non-optimal times, affecting overall operational efficiency. Predictive maintenance uses sensors and data analysis technology to predict possible problems with the vehicle and arrange maintenance in advance. This method can reduce unexpected downtime, but it is still difficult to avoid operational losses during maintenance.

[0004] There are also maintenance options at night or during off-peak hours, when demand is low, to reduce the impact on daily operations. However, this approach may increase maintenance costs and make it difficult to respond to sudden maintenance needs.

[0005] Although the above methods have alleviated the impact of maintenance on operations to a certain extent, there will still be a loss of operational efficiency. Even if the most optimized maintenance plan is adopted, the vehicle will still not generate any revenue during the maintenance period, which has a direct impact on operational efficiency.

[0006] In view of the above problems, a new solution is urgently needed. Summary of the invention

[0007] The purpose of this application is to provide a maintenance recommendation method, device, electronic device and storage medium based on sharing, which has the advantages of improving resource utilization efficiency during vehicle maintenance and providing car owners with more convenient vehicle selection.

[0008] In the first aspect, the present application provides a maintenance recommendation method based on sharing, and the technical solution is as follows:

[0009] Upon receiving a vehicle maintenance request or a request to generate a vehicle maintenance request, determining whether the target vehicle belongs to a shared group;

[0010] When the target vehicle belongs to the shared group, determining whether there is another first vehicle undergoing maintenance in the shared group;

[0011] If there are other first vehicles undergoing maintenance in the sharing group, a maintenance recommendation result having shared information on the right to use the first vehicle is generated.

[0012] Further, in the present application, the step of generating a maintenance recommendation result having shared information for the first vehicle use right includes:

[0013] Acquire first information of the first vehicle and second information of a first maintenance store where the first vehicle is located, wherein the first information at least includes a maintenance status of the first vehicle, and the second information at least includes first location information of the first maintenance store;

[0014] generating a maintenance recommendation result having shared information on the right to use the first vehicle according to the maintenance status of the first vehicle and the first location information;

[0015] The step of generating a maintenance recommendation result having shared information on the use right of the first vehicle according to the maintenance status of the first vehicle and the first location information comprises:

[0016] When the maintenance status of the first vehicle is maintenance completed, a maintenance recommendation result having shared information on the right to use the first vehicle is generated according to the first location information.

[0017] Further, in the present application, when the maintenance status of the first vehicle is maintenance completed, the step of generating a maintenance recommendation result having shared information for the right to use the first vehicle according to the first location information includes:

[0018] When the maintenance status of the first vehicle is maintenance completed, sending a sharing request message to the owner of the first vehicle;

[0019] receiving first feedback information made by the owner of the first vehicle according to the sharing request information;

[0020] When the first feedback information is agreement, a maintenance recommendation result having shared information for the first vehicle use right is generated according to the first location information.

[0021] Furthermore, in the present application, the second information at least includes current work arrangement information of the first maintenance store, and the step of sending the sharing request information to the owner of the first vehicle includes:

[0022] Obtaining estimated maintenance items of the target vehicle according to the vehicle maintenance request or a request to generate a vehicle maintenance request;

[0023] estimating a first estimated completion time of maintenance for the target vehicle according to the current work arrangement information of the first maintenance store and the estimated maintenance items;

[0024] The sharing request information including the first estimated maintenance completion time is sent to the owner of the first vehicle.

[0025] Furthermore, in the present application, the steps of the method also include:

[0026] When the maintenance status of the first vehicle is unfinished maintenance, obtaining the second current position information of the target vehicle and the second estimated completion time of the maintenance of the first vehicle;

[0027] Calculating a first arrival time of the target vehicle at the first maintenance store according to the first location information and the second location information;

[0028] Calculating a first waiting time for the owner of the target vehicle according to the second estimated maintenance completion time and the first arrival time;

[0029] The maintenance recommendation result having the shared information on the first vehicle use right and the first waiting time is generated.

[0030] Furthermore, in the present application, the steps of the method also include:

[0031] Obtaining second feedback information made by the owner of the target vehicle after receiving the maintenance recommendation result;

[0032] When the second feedback information is in agreement, a sharing contract is generated and the sharing contract is sent to the owner corresponding to the target vehicle and the owner corresponding to the first vehicle respectively.

[0033] Furthermore, in the present application, the steps of the method also include:

[0034] If there is no other first vehicle undergoing maintenance in the sharing group, a maintenance recommendation result without vehicle use sharing information is generated according to a preset rule.

[0035] In the second aspect, the present application also proposes a maintenance recommendation device based on sharing, comprising:

[0036] A first determination module, configured to determine whether a target vehicle belongs to a sharing group when receiving a vehicle maintenance request or a request to generate a vehicle maintenance request;

[0037] A second judgment module is used to judge whether there are other first vehicles undergoing maintenance in the shared group when the target vehicle belongs to the shared group;

[0038] A generating module is used to generate a maintenance recommendation result with shared information on the right to use the first vehicle if there are other first vehicles undergoing maintenance in the sharing group.

[0039] In a third aspect, the present application further proposes an electronic device, comprising a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps in the above method are executed.

[0040] In a fourth aspect, the present application further proposes a storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above method are executed.

[0041] From the above, it can be seen that the present application provides a maintenance recommendation method, device, electronic device and storage medium based on sharing. When a vehicle maintenance request or a request to generate a vehicle maintenance request is received, it is determined whether the target vehicle belongs to a shared group; when the target vehicle belongs to the shared group, it is determined whether there are other first vehicles undergoing maintenance in the shared group; if there are other first vehicles undergoing maintenance in the shared group, a maintenance recommendation result with shared information on the right to use the first vehicle is generated. By determining whether the target vehicle belongs to a shared group and searching for other vehicles undergoing maintenance in the shared group, a maintenance recommendation result including shared information on the right to use the vehicle is generated, thereby realizing vehicle sharing during the maintenance period, which has the advantages of improving resource utilization efficiency during vehicle maintenance and providing car owners with more convenient vehicle options. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A flow chart of a sharing-based maintenance recommendation method provided for this application.

[0043] Figure 2 A schematic diagram of the structure of a sharing-based maintenance recommendation device provided in this application.

[0044] Figure 3 A schematic diagram of the structure of an electronic device provided in this application.

[0045] In the figure: 210, a first judgment module; 220, a second judgment module; 230, a generation module; 310, a processor; 320, a memory. DETAILED DESCRIPTION

[0046] The technical solutions in the present application will be clearly and completely described below in conjunction with the drawings in the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The components of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the present application for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0047] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0048] In fleet operation management, vehicle maintenance management within the fleet is a very important and critical issue. When a vehicle is undergoing maintenance, it is in an inoperable state, which will result in reduced operational efficiency and economic benefits.

[0049] In this regard, in order to improve operational efficiency and reduce damage to economic benefits, existing improvement ideas usually focus on how to increase the speed of vehicle maintenance. This improvement idea tends to enable technical personnel in the field to improve and improve maintenance processes, maintenance tools, and the proficiency of maintenance personnel.

[0050] However, this is not the case with the present application. This application breaks out of the existing conventional thinking framework and no longer focuses on the maintenance of a single vehicle. Instead, from a more macro perspective of fleet operation management, it reframes the traditional issue of how to reduce the downtime of operating vehicles due to maintenance as a problem of how to ensure operational continuity while ensuring vehicle maintenance. Under this reframed technical problem, the approach to solving the problem has been changed. It is no longer limited to the maintenance time of a single vehicle, but turns attention to the operational continuity of the entire fleet, breaking through the traditional thinking mode of independent vehicle maintenance and transforming a single maintenance problem into a fleet resource optimization problem.

[0051] In order to solve this problem, this application introduces the concept of sharing vehicle usage rights in vehicle maintenance for the first time. Based on this, a new maintenance recommendation method is proposed, the core of which is to determine whether the target vehicle belongs to the sharing group and perform subsequent processing on this basis.

[0052] Specifically, refer to Figure 1, this application proposes a maintenance recommendation method based on sharing, the steps of which include:

[0053] S110, upon receiving a vehicle maintenance request or a request to generate a vehicle maintenance request, determining whether the target vehicle belongs to a sharing group;

[0054] S120, when the target vehicle belongs to a shared group, determining whether there is another first vehicle undergoing maintenance in the shared group;

[0055] S130: If there are other first vehicles undergoing maintenance in the sharing group, generate a maintenance recommendation result having shared information on the right to use the first vehicle.

[0056] Among them, the vehicle maintenance request can specifically be a request initiated by the car owner. Specifically, there is a maintenance recommendation system in advance, which can recommend the car owner to go to a suitable maintenance store for maintenance based on the real-time location of the target vehicle and the usage time of each component. It can also collect the current workload of each maintenance store and provide maintenance suggestions to the car owner based on the principle of shortest maintenance time.

[0057] Among them, the request for generating a vehicle maintenance request is a request generated based on active suggestions. The above-mentioned vehicle maintenance request can be a request actively initiated by the car owner. In addition, the maintenance recommendation system can actively initiate suggestions for requesting maintenance. Specifically, it can be based on the real-time location of the vehicle and the usage time of each component to generate a suggestion for requesting maintenance. For example, when the usage time of a component reaches a preset value, the usage time is a trigger condition, that is, it can be regarded as a request for generating a vehicle maintenance request. After the request is verified, a vehicle maintenance request will be generated to suggest the car owner to perform maintenance.

[0058] Specifically, when a maintenance request is received, the vehicle information of the corresponding target vehicle in the maintenance request is first checked. Through a preset database or algorithm, it can quickly determine whether the vehicle belongs to a certain sharing group. This judgment can be based on the vehicle's ownership information or a pre-defined sharing group setting.

[0059] If the target vehicle is confirmed to belong to a shared group, the system will further query the status of other vehicles in the shared group. This query may involve real-time database access or interaction with other system modules. The system will pay special attention to first vehicles that are undergoing maintenance, as these first vehicles may provide opportunities for sharing.

[0060] When it is found that other first vehicles are undergoing maintenance, detailed information of these first vehicles will be collected, such as the maintenance location, estimated completion time, etc. Based on this information, the system generates a maintenance recommendation result containing shared information about the right to use the first vehicle. For example, the maintenance recommendation result may suggest that the user of the target vehicle go to the location where the first vehicle is being maintained for maintenance.

[0061] Among them, the shared information about the right to use the first vehicle may specifically include whether there is a first vehicle that can be shared. If there is a first vehicle that can be shared, it may also include information such as the vehicle model and age of the first vehicle. The maintenance recommendation results may include the recommended maintenance store, maintenance items of the target vehicle, and maintenance time.

[0062] The core innovation of this application is to introduce the concept of vehicle sharing into the maintenance recommendation process. By identifying the shared group and utilizing the maintenance status of other vehicles in the group, the system can provide a more flexible and efficient maintenance solution. This not only improves the efficiency of vehicle use, but also reduces the waiting time of users, while optimizing the allocation of maintenance resources.

[0063] Furthermore, the method can be extended and optimized according to actual needs. For example, a priority system can be introduced to adjust the sharing recommendation according to the importance of the vehicle or the urgency of the user. Geographical location factors can also be considered to ensure that the recommended sharing vehicles are within a reasonable distance.

[0064] As a preferred implementation, the system can automatically generate a detailed shared use agreement, including usage time, cost sharing, etc., to further simplify the sharing process. At the same time, a real-time communication function can be integrated so that the user of the target vehicle and the user of the corresponding first vehicle can directly coordinate the specific handover details.

[0065] Therefore, the maintenance recommendation method based on sharing proposed in this application not only solves the problem of low resource utilization in traditional methods, but also provides a new intelligent direction for fleet management systems. By effectively identifying sharing opportunities and integrating them into the maintenance process, this method significantly improves the efficiency and flexibility of vehicle maintenance, providing users with a more convenient and economical maintenance experience.

[0066] Specifically, the system will give priority to recommending the user of the target vehicle to go to the maintenance store where the first vehicle that can be shared is located for maintenance. In this case, when the user drives the target vehicle to the corresponding maintenance store for maintenance, the first vehicle can be used to continue operation, thereby reducing the losses caused by the traditional existing method where each user has to stop operating due to vehicle maintenance.

[0067] It is worth noting that when the first vehicle does not exist, the target vehicle needs to go to a maintenance store for maintenance. At this time, the corresponding vehicle owner can use a spare vehicle for operation, and the spare vehicle can be provided by the fleet operation manager.

[0068] In addition, when the vehicle is confirmed to be maintained, a message indicating that it has entered the maintenance status will be uploaded.

[0069] The sharing-based maintenance recommendation method proposed in this application can be implemented in a variety of ways. For example, determining whether a target vehicle belongs to a sharing group can be achieved by querying a preset vehicle database, which stores the sharing group information of each vehicle. Another implementation method is to dynamically determine whether it belongs to a certain sharing group by analyzing the vehicle's usage history and user information. Both methods can effectively identify the sharing attributes of the target vehicle, thereby providing a basis for subsequent maintenance recommendations.

[0070] Determining whether there are other first vehicles in the shared group that are undergoing maintenance can be achieved by querying the maintenance management system in real time. The system can maintain a real-time updated maintenance status list to record the current maintenance status of each vehicle. Another method is to directly obtain maintenance information of vehicles belonging to the same shared group by connecting with the systems of various maintenance stores. Both methods can accurately identify possible sharing opportunities and provide necessary information for generating maintenance recommendation results.

[0071] Generating maintenance recommendation results with shared information for the first vehicle use right can be achieved through an intelligent algorithm. The algorithm comprehensively considers factors such as maintenance time, location, and vehicle condition to generate the optimal sharing plan. Another implementation method is to generate recommendation results based on the priority of different situations through a preset rule system. Both methods can provide appropriate sharing suggestions based on specific circumstances and achieve efficient use of resources.

[0072] Specifically, the technical solution of the present application can be implemented in the following ways: First, a vehicle management system is established, which includes a vehicle information database, a maintenance status tracking module and a recommendation generation module. The vehicle information database stores the basic information of each vehicle, including vehicle ID, sharing group, usage history, etc. The maintenance status tracking module monitors and updates the maintenance status of each vehicle in real time, including whether it is being maintained, the estimated completion time, etc. The recommendation generation module is responsible for generating the final maintenance recommendation results based on the input maintenance request and the data in the system.

[0073] When the system receives a maintenance request, it first checks the vehicle information database to determine whether the target vehicle belongs to the shared group. If it does, the system will further query the maintenance status tracking module to check the maintenance status of other vehicles in the same group. If it finds vehicles under maintenance, the system will collect detailed information about these vehicles, such as the maintenance location, estimated completion time, etc.

[0074] The recommendation generation module will comprehensively analyze this information, taking into account factors including but not limited to: the distance to the maintenance location, the matching degree between the maintenance completion time and the target vehicle's estimated arrival time, the vehicle model, etc. Based on these factors, the system generates a maintenance recommendation result containing sharing suggestions. For example, the recommendation result may suggest that the user of the target vehicle use the first vehicle that is about to complete maintenance or has completed maintenance while waiting for maintenance, and provide a specific time period for use and the handover location.

[0075] Furthermore, when there are multiple first vehicles distributed in different maintenance stores, recommendations can be made based on vehicle models, with the first vehicle with the highest similarity being prioritized as a shared vehicle, so that the corresponding vehicle owners can become more accustomed to its operation when using it.

[0076] Compared with the prior art, the innovations of this application are mainly reflected in the following aspects: First, this application introduces the concept of shared groups, which is ignored by traditional maintenance systems. Second, this application realizes the intelligent matching of maintenance needs and vehicle sharing, which greatly improves resource utilization. Third, the recommendation results of this application are dynamically generated and can adapt to real-time changes, rather than relying on preset fixed solutions.

[0077] Specifically, if we compare this application with the traditional vehicle maintenance management system, we can find that the traditional system usually only focuses on the maintenance arrangement of a single vehicle, while ignoring the possible sharing relationship between vehicles. This leads to inefficiency in handling vehicles belonging to the shared group and inability to fully utilize the resources of vehicles that have completed maintenance. In contrast, the technical solution of this application realizes efficient allocation of resources by identifying the shared group, judging the maintenance status of other vehicles in the group, and generating recommendation results containing shared information.

[0078] Therefore, this application not only solves the problem of low resource utilization in traditional methods, but also provides a new intelligent direction for fleet operation management systems. By effectively identifying sharing opportunities and integrating them into the maintenance process, the method of this application significantly improves the efficiency and flexibility of vehicle maintenance, providing users with a more convenient and economical maintenance experience.

[0079] In some of the above-mentioned embodiments, during the implementation of the present application, there is still a problem of how to generate a maintenance recommendation result with shared information for the right to use the first vehicle.

[0080] In this regard, the present application further proposes that the steps of generating a maintenance recommendation result having shared information for the first vehicle use right include:

[0081] Acquire first information of a first vehicle and second information of a first maintenance store where the first vehicle is located, wherein the first information at least includes a maintenance status of the first vehicle, and the second information at least includes first location information of the first maintenance store;

[0082] Generating a maintenance recommendation result having shared information on the right to use the first vehicle according to the maintenance status of the first vehicle and the first location information;

[0083] The step of generating a maintenance recommendation result having shared information on the right to use the first vehicle according to the maintenance status of the first vehicle and the first location information includes:

[0084] When the maintenance status of the first vehicle is maintenance completed, a maintenance recommendation result having shared information on the right to use the first vehicle is generated according to the first location information.

[0085] This application obtains key information of the first vehicle and the first maintenance store, and generates maintenance recommendation results containing shared information about the right to use the first vehicle based on this information. This method not only takes into account the maintenance status of the first vehicle, but also uses the location information of the first maintenance store, so as to provide more accurate and practical maintenance recommendations. In particular, after the first vehicle completes maintenance, generating recommendation results using its first location information can improve the utilization efficiency of vehicle resources.

[0086] In the technical solution of the present application, obtaining the first information of the first vehicle can be achieved in a variety of ways. For example, the maintenance status of the first vehicle can be obtained in real time through the on-board diagnostic system (OBD), or the maintenance record of the first vehicle can be obtained through the management system of the first maintenance store. The second information of the first maintenance store, especially the first location information, can be obtained through a GPS positioning system or a pre-stored geographic information database.

[0087] In specific implementation, the present application may adopt the following method: First, the maintenance status of the first vehicle is obtained through the vehicle system or the management system of the first maintenance store. Assume that the first vehicle has just completed a comprehensive maintenance, and the maintenance status is marked as "maintenance completed". At the same time, the system obtains the location information of the first maintenance store, such as the longitude and latitude coordinates (x°E, y°N).

[0088] In some of the above-mentioned embodiments, during the implementation of the present application, there is still a technical problem of how to solve the technical problem of ensuring that the owner of the first vehicle agrees to share when generating a maintenance recommendation result with shared information for the right to use the first vehicle.

[0089] It should be noted that joining a sharing group is itself an agreement to agree to share, but in actual scenarios, there will be many practical factors that affect whether it needs to be shared. For example, when a first vehicle is undergoing maintenance, if the owner of the first vehicle is already waiting at the first maintenance store, or has gone to the first maintenance store to pick up the vehicle, it is obviously unreasonable to forcibly share the first vehicle with the owner of the target vehicle. Therefore, further measures are needed to solve this problem.

[0090] In this regard, the present application further proposes:

[0091] When the maintenance status of the first vehicle is maintenance completed, sending a sharing request message to the owner of the first vehicle;

[0092] receiving first feedback information made by the owner of the first vehicle according to the sharing request information;

[0093] When the first feedback information is agreement, a maintenance recommendation result having shared information for the right to use the first vehicle is generated according to the first location information.

[0094] The technical solution of the present application solves the problem of ensuring that the owner of the first vehicle agrees to share by seeking the consent of the owner of the first vehicle before generating shared information. Specifically, when the first vehicle completes maintenance, the system sends a sharing request message to its owner, asking whether he is willing to include the vehicle in the sharing scope. Only with the owner's consent will the system generate shared information containing the right to use the vehicle. This method not only protects the rights and interests of the owner, but also effectively utilizes the resources of vehicles that have completed maintenance, thereby improving the efficiency of vehicle use.

[0095] In the present application, sending the sharing request information to the owner of the first vehicle can be achieved in a variety of ways. For example, a mobile application can be used to push a notification, or a text message, an email, etc. The content of the sharing request information can include information such as the purpose of sharing, the estimated sharing time, and the possible benefits, so that the owner of the first vehicle can make a decision.

[0096] Receiving the first feedback information made by the owner of the first vehicle can be achieved by setting a simple "agree" or "reject" button, or more detailed options can be provided, such as "agree and set a sharing time range", "disagree temporarily, ask again later", etc. These options can perform corresponding functions. This can give the owner of the first vehicle more control and flexibility.

[0097] When the first feedback information is "agree", the system will generate a maintenance recommendation result with shared information for the first vehicle use right based on the first location information. The first location information here may include the geographic coordinates, city or region of the first maintenance store, etc. The system can calculate the optimal sharing solution based on this information and the location of the target vehicle.

[0098] In the process of solving the problem of ensuring that the owner of the first vehicle agrees to sharing, the technical solution of the present application first respects the owner's wishes and rights by sending a sharing request message to the owner. This step avoids the situation where the first vehicle is included in the sharing without consent, and effectively protects the interests of the owner. Secondly, by receiving the first feedback information from the owner of the first vehicle, the system can accurately understand the owner's decision and will only proceed to the next step with explicit consent. Finally, after obtaining consent, the system generates maintenance recommendation results based on the first location information, which ensures the accuracy and practicality of the shared information.

[0099] In this way, the application not only solves the problem of ensuring the consent of the car owner, but also improves the credibility and user satisfaction of the entire sharing system. Car owners can feel that their rights and interests are respected, and are more willing to participate in the sharing system. At the same time, this method also provides the system with more reliable sharing resources, because only the first vehicles that are truly willing to share will be included in the system, which improves the quality and efficiency of sharing.

[0100] As a preferred implementation, the above method can be implemented in a vehicle maintenance system. For example, when generating maintenance recommendation results, for the first vehicle (referred to as vehicle A), the system can automatically send a message to the owner of vehicle A: "Dear owner, your vehicle has completed maintenance. We noticed that there are other vehicles currently waiting for repair. Are you willing to temporarily share your vehicle with other owners in need? This will help them solve traffic problems more quickly, and you can also obtain certain sharing benefits. If you agree, please reply 'Agree'; if you disagree, please reply 'Reject'."

[0101] Among them, the car owner can set a default response, for example, the default response is agreement.

[0102] If the owner replies "Agree", the system will immediately generate a shared information containing the right to use vehicle A. This information may include the current location of vehicle A (i.e. the location of the first maintenance store), available time, model, etc. Then, the system will use this shared information as part of the maintenance recommendation results.

[0103] This implementation method not only ensures the car owner's right to know and right to choose, but also improves the efficiency of the entire maintenance system. The owner of the target vehicle can choose to use the first vehicle that has been repaired or is ready to complete maintenance without having to wait for his own vehicle to be repaired. This reduces waiting time, improves customer satisfaction, and also improves vehicle utilization.

[0104] This application not only protects the rights and interests of car owners, but also improves the flexibility and pertinence of sharing by obtaining the consent of car owners in real time. In addition, the solution of this application also takes into account the special scenarios of vehicle maintenance, combining the sharing mechanism with the maintenance system, which not only improves the efficiency of the maintenance system, but also provides car owners with additional income opportunities.

[0105] In some of the above-mentioned embodiments, during the implementation of the present application, there is still a problem of how to provide a more accurate maintenance time estimate when sending sharing request information.

[0106] In this regard, the present application further proposes:

[0107] The second information at least includes current work arrangement information of the first maintenance store, and the step of sending the sharing request information to the owner of the first vehicle includes:

[0108] Obtain estimated maintenance items for a target vehicle according to a vehicle maintenance request or a request to generate a vehicle maintenance request;

[0109] Estimate the first estimated maintenance completion time of the target vehicle based on the current work schedule information of the first maintenance store;

[0110] The sharing request information including the first estimated maintenance completion time is sent to the owner of the first vehicle.

[0111] The technical solution of the present application can more accurately estimate the time to complete maintenance by obtaining the work schedule information of the maintenance store and the estimated maintenance items of the target vehicle. This method can provide the owner of the first vehicle with more detailed and accurate information to help him decide whether to agree to share.

[0112] This application combines the work schedule information of the first maintenance store with the estimated maintenance items of the target vehicle to generate a more accurate maintenance time estimate. Compared with simple time estimates, this method takes into account more practical factors and can provide more reliable time estimates, thereby improving the practicality and credibility of the shared maintenance system.

[0113] Specifically, the technical solution of this application includes the following key features:

[0114] First, the second information includes the current work schedule information of the first maintenance store. This information can be obtained in a variety of ways, for example: directly obtain the current work schedule in real time from the management system of the maintenance store. Update the work schedule information of the maintenance store at regular intervals (such as every hour or every day) through regular synchronization. Predict the work schedule of the maintenance store based on historical data and the characteristics of the current time period (such as weekdays / weekends, seasons, etc.).

[0115] Secondly, obtain the estimated maintenance items of the target vehicle based on the vehicle maintenance request or the generation request of the vehicle maintenance request. This step can be achieved by analyzing the description information in the vehicle maintenance request and extracting keywords to match the preset maintenance item library. Based on the vehicle's usage time, mileage and other information, combined with the vehicle model characteristics, predict the maintenance items that may be required. Use machine learning algorithms to predict the maintenance items that may be required for the target vehicle based on historical maintenance data.

[0116] Then, the first estimated maintenance completion time of the target vehicle is estimated based on the current work schedule information of the first maintenance store. This step can take into account the following factors: The current workload of the maintenance store, including ongoing maintenance projects and scheduled maintenance projects. The average completion time of various maintenance projects. The number of available maintenance technicians and workstations. Special circumstances, such as the insertion of emergency maintenance tasks.

[0117] Finally, a sharing request message containing the first estimated maintenance completion time is sent to the owner of the first vehicle. This information may include: the estimated maintenance start time and end time. A description of uncertain factors that may affect the maintenance time. A real-time update mechanism during the maintenance process so that the owner can be notified in a timely manner when the situation changes.

[0118] By obtaining the work schedule information of the maintenance store, this application can more accurately assess the current workload of the maintenance store. Combined with the estimated maintenance items of the target vehicle, the first estimated maintenance completion time required can be more accurately calculated. These two factors work together to make the estimated maintenance completion time more accurate and reliable.

[0119] For example, suppose that a maintenance shop currently has one station undergoing maintenance, which is expected to take another 2 hours to complete. The target vehicle needs to have its tires replaced and its oil changed. According to historical data, these two tasks take an average of 1.5 hours. Considering the current work schedule, the system may estimate that the target vehicle will be completed in 3.5 hours (2 hours of waiting + 1.5 hours of maintenance).

[0120] This application first provides accurate basic data for estimation by obtaining real-time work schedule information from maintenance stores. This step avoids the errors that may be caused by relying solely on static or outdated information. Then, by analyzing the maintenance requests or generating requests for the target vehicle, the system can accurately identify the maintenance items that may be required for the target vehicle. This step ensures that the time estimate takes into account specific maintenance needs rather than using general averages.

[0121] The system then combines the work schedule information of the first maintenance store with the estimated maintenance items of the target vehicle to calculate a more accurate first estimated completion time. This process takes into account multiple factors, such as the current workload, the average duration of each maintenance task, and available resources, to produce a time estimate that is closer to the actual situation.

[0122] Finally, the system sends the sharing request information containing a more accurate estimated time to the owner of the first vehicle, which enables the owner of the first vehicle to decide whether to agree to sharing based on more reliable information, thereby improving the efficiency and user satisfaction of the entire shared maintenance system.

[0123] The technical solution of the present application has the following advantages: it improves the accuracy of time estimation, reduces user dissatisfaction and resource waste caused by inaccurate time estimation, enhances the transparency of the system, enables users to make decisions based on more detailed information, enhances user experience, and reduces negative emotions caused by overtime in retrieving one's car.

[0124] As a preferred implementation, the present application can be implemented through the following steps:

[0125] After receiving the maintenance request of the target vehicle, the system first obtains the work schedule information of the first maintenance store in real time through the API interface. This information includes the maintenance projects currently in progress, the scheduled maintenance projects, and the estimated idle time of each workstation.

[0126] The system analyzes the description information in the maintenance request, extracts keywords using natural language processing technology, and matches them with the preset maintenance project library. At the same time, the system also considers information such as vehicle usage time and mileage, combines vehicle model characteristics, and uses machine learning algorithms to predict additional maintenance items that may be required.

[0127] Based on historical data, the system calculates the average completion time for each maintenance item. For example, a tire change takes an average of 45 minutes, and an oil change takes an average of 30 minutes.

[0128] The system calculates the earliest time that maintenance can start based on the work schedule information of the first maintenance store. For example, if all workstations are currently working, the system will find the next available time slot.

[0129] The system combines the estimated time required for the maintenance project with the available start time to calculate the estimated first estimated time to complete the maintenance project. For example, if the earliest time you can start the repair is 2 hours later, and the maintenance project is estimated to take 1.5 hours, the system will calculate the estimated completion time as 3.5 hours later.

[0130] The system generates a shared request containing these details, including the estimated maintenance start time, estimated completion time, a list of possible maintenance items, etc. At the same time, the system also explains factors that may affect the actual completion time, such as the insertion of emergency maintenance tasks.

[0131] The system sends the detailed sharing request information to the owner of the first vehicle via push notification or text message.

[0132] The system also has a real-time update mechanism. If there are any changes that may affect the completion time during the waiting or maintenance process, the system will immediately calculate the new estimated completion time and notify the relevant car owners.

[0133] In this way, this application can provide car owners with more accurate and transparent maintenance time estimates, thereby helping them make better decisions and improving the efficiency and user satisfaction of the entire shared maintenance system.

[0134] In some of the above-mentioned embodiments, during the implementation of the present application, there is still a problem of how to provide a suitable maintenance recommendation result for the target vehicle when the maintenance of the first vehicle is not completed.

[0135] In this regard, the present application further proposes:

[0136] When the maintenance status of the first vehicle is unfinished maintenance, obtaining the second current position information of the target vehicle and the second estimated completion time of the maintenance of the first vehicle;

[0137] Calculating a first arrival time of the target vehicle at the first maintenance store according to the first location information and the second location information;

[0138] Calculate a first waiting time for the owner of the target vehicle according to the second estimated maintenance completion time and the first arrival time;

[0139] A maintenance recommendation result having shared information on the first vehicle use right and a first waiting time is generated.

[0140] This application obtains the second location information of the target vehicle, combines the maintenance status of the first vehicle and the first location information of the first maintenance store, and calculates the first arrival time of the target vehicle at the first maintenance store and the first waiting time that the owner may need. Such a design can provide car owners with more comprehensive and practical information, helping them to better plan their time and make decisions on whether to accept shared maintenance. By providing the first waiting time, car owners can better evaluate whether it is worth waiting for the first vehicle to complete maintenance before using it, thereby improving the practicality and acceptability of maintenance recommendations.

[0141] Specifically, the technical solution of this application includes the following key features:

[0142] Obtaining the current second location information of the target vehicle: This step can be achieved in a variety of ways, such as obtaining the real-time location information of the target vehicle through a vehicle-mounted GPS system, mobile phone positioning, or manual input by the owner.

[0143] Calculate the first arrival time of the target vehicle at the first maintenance store: Based on the acquired second location information and the known first location information of the first maintenance store, the system can use the navigation algorithm to calculate the optimal route and estimated arrival time. This calculation can take into account factors such as current traffic conditions and road type to provide a more accurate time estimate.

[0144] Calculate the first waiting time of the owner of the target vehicle: The system compares and calculates the second estimated maintenance completion time with the first arrival time. If the first arrival time is later than the second estimated maintenance completion time, the first waiting time may be zero; otherwise, the first waiting time is the difference between the two.

[0145] Generate maintenance recommendation results including shared information and first waiting time: The system integrates the information obtained from the above calculations to generate a recommendation result including shared information of the first vehicle use right and the first waiting time. This result can be presented to the owner of the target vehicle in the form of text, chart or interactive interface.

[0146] By providing an accurate first waiting time, car owners can better evaluate whether to accept the shared maintenance plan, thereby improving the practicality and acceptability of maintenance recommendations.

[0147] In practical application, the technical solution of this application can be operated as follows:

[0148] First, the system detects that the maintenance status of the first vehicle is not completed. At this time, the system will immediately trigger the process of obtaining the current location of the target vehicle. Assume that the target vehicle is currently located in the city center, about 15 kilometers away from the first maintenance store.

[0149] Next, the system uses the navigation algorithm and takes into account the current road conditions to calculate that the target vehicle is expected to arrive at the first maintenance store in 30 minutes. At the same time, the system finds that the estimated time to complete the maintenance of the first vehicle is another 45 minutes.

[0150] The system then calculates that the first waiting time for the owner of the target vehicle is 15 minutes (45 minutes - 30 minutes).

[0151] Finally, the system generates a maintenance recommendation result, which may be as follows: "Dear car owner, we found that a car in the shared group is undergoing maintenance. If you choose to go to the maintenance store, you will need to wait 15 minutes before you can use the vehicle. Do you accept this shared maintenance plan?"

[0152] In this way, car owners can clearly understand the specific waiting time if they choose shared maintenance, so as to make more informed decisions. This not only improves the user experience, but also optimizes the utilization efficiency of maintenance resources.

[0153] Compared with the prior art, the technical solution of this application has significant advantages. Traditional maintenance recommendation systems usually only provide the location of maintenance stores without considering the actual situation of users and possible waiting time. This application provides users with more personalized and practical recommendation results by introducing real-time location information of the target vehicle and accurate time calculation. This method not only improves the decision-making efficiency of users, but also may reduce user dissatisfaction caused by insufficient information, thereby improving the overall service quality.

[0154] In some of the above-mentioned embodiments, during the implementation of the present application, there is still the problem of how to realize the generation and distribution of vehicle sharing contracts in the sharing-based maintenance recommendation method.

[0155] In this regard, the present application further proposes:

[0156] Obtaining second feedback information from the owner of the target vehicle after receiving the maintenance recommendation result;

[0157] When the second feedback information is agreed, a sharing contract is generated and sent to the owner of the target vehicle and the owner of the first vehicle respectively.

[0158] This technical solution of the present application solves the technical problem of how to realize the generation and distribution of vehicle sharing contracts in the sharing-based maintenance recommendation method by obtaining feedback from the owner of the target vehicle and automatically generating and distributing the sharing contract after obtaining consent. This method not only simplifies the sharing process, but also ensures the legality and traceability of the sharing behavior. Through automated contract generation and distribution, the complexity of manual operations is reduced and the efficiency and accuracy of the entire sharing process are improved. At the same time, this method also provides clear legal protection for vehicle sharing, which is conducive to resolving possible disputes and promoting the healthy development of the sharing economy.

[0159] The technical solution of this application involves the following key features:

[0160] Obtaining the second feedback information from the owner of the target vehicle: This step can be achieved in a variety of ways. For example, the maintenance recommendation results can be sent to the owner through mobile applications, text messages, emails, or voice calls, and a simple feedback mechanism can be set up, such as "agree" or "disagree" buttons. The system can monitor the owner's feedback in real time and proceed to the next step once the feedback is received.

[0161] Determine whether the second feedback information is consent: The system needs to parse and judge the second feedback information received. A judgment logic can be set. If the feedback is "consent", the subsequent contract generation process is triggered; if it is "disagree" or no feedback is received within the specified time, the sharing process can be terminated or a reminder can be sent.

[0162] Generate a sharing contract: When the car owner agrees, the system will automatically generate a formal sharing contract. The contract generation can be based on a preset template and automatically fill in relevant information according to the specific sharing situation, such as vehicle information, sharing time, and responsibilities of both parties. The system can also integrate smart contract technology to ensure the accuracy and legal effect of the contract content.

[0163] Distribute the sharing contract: The system sends the generated contract to the target vehicle and the owner of the first vehicle respectively. This step can be achieved through a variety of channels, such as email, encrypted messaging system or a dedicated contract management platform. The system can also set up a confirmation mechanism to require both parties to confirm after receiving the contract to ensure the effective delivery of the contract.

[0164] Through the above solution, the automatic generation and distribution process of vehicle sharing contracts is realized, which improves the efficiency and standardization of sharing operations. In particular, the automatic generation and distribution of contracts is closely integrated with the aforementioned maintenance recommendation system to form a complete shared maintenance process. This integration not only simplifies user operations, but also ensures the coherence and consistency of the entire process.

[0165] In the process of solving the technical problem of how to realize the generation and distribution of vehicle sharing contracts, the system first obtains the feedback of the owner of the target vehicle on the maintenance recommendation results. This step ensures that the sharing behavior is based on the owner's explicit consent and avoids unauthorized sharing operations.

[0166] Secondly, the system determines whether the feedback is consent. This judgment process is the key to triggering the subsequent contract generation, ensuring that the contract will only be generated with explicit consent, thereby protecting the rights and interests of the car owner.

[0167] Thirdly, the system automatically generates a shared contract. This step greatly simplifies the traditional contract formulation process, reduces the time and possible errors of manual operations, and ensures the standardization and integrity of the contract content.

[0168] Finally, the system sends the generated contracts to the relevant car owners. This step ensures the timely delivery of the contract and the right to know of both parties, providing a clear legal basis for subsequent sharing behaviors.

[0169] Through this series of steps, the technical solution of the present application realizes the automatic generation and distribution of sharing contracts, significantly improving the efficiency and standardization of the sharing process.

[0170] As a preferred implementation, the technical solution of the present application can be implemented as follows:

[0171] When the system sends the maintenance recommendation results to the target vehicle owner, it will also provide a simple feedback interface. This interface can be a pop-up window with two options: "Agree" and "Disagree". The owner can directly click to make a choice.

[0172] When the car owner clicks "Agree", the system will immediately trigger the contract generation module. The module will call the preset contract template and extract relevant information from the database, such as vehicle information, maintenance information, sharing time, etc., and automatically fill it into the template.

[0173] The generated contract will contain the following key information: identity information of both parties involved in the sharing, detailed information of the shared vehicle, time frame for sharing, rights and obligations of both parties, insurance and liability clauses, and methods for handling breach of contract.

[0174] After the contract is generated, the system will immediately send the contract to both car owners through a preset communication channel (such as an encrypted messaging system). At the same time, the system will ask both parties to confirm after receiving the contract.

[0175] During the entire process, the system will record the timestamp and operation content of each step to ensure the traceability of the entire process.

[0176] Through this implementation method, the technical solution of the present application can complete the entire process from car owner feedback to contract distribution within a few minutes, greatly improving the efficiency and convenience of shared maintenance.

[0177] In some of the above-mentioned embodiments, during the implementation of the present application, there is still a problem of how to solve the maintenance recommendation problem when there are no other vehicles to be maintained in the shared group.

[0178] In this regard, the present application further proposes:

[0179] If there is no other first vehicle to be maintained in the sharing group, a maintenance recommendation result without vehicle use sharing information is generated according to a preset rule.

[0180] This method determines whether there are sharable vehicle resources by judging whether there are other vehicles under maintenance in the sharing group. When there are no other vehicles under maintenance, the system will generate a maintenance recommendation result that does not include vehicle usage sharing information according to the preset rules. This method solves the problem of how to make maintenance recommendations when there are no sharable vehicles in the sharing group, ensuring the continuity and reliability of the maintenance recommendation service.

[0181] In the specific implementation process, when the system determines that there is no other first vehicle for maintenance in the shared group, a variety of preset rules can be used to generate maintenance recommendation results without vehicle use sharing information. For example:

[0182] Based on recommendations from historical data, the system can analyze the historical maintenance records of the target vehicle and generate personalized maintenance recommendations based on factors such as vehicle usage and mileage.

[0183] Based on the standard maintenance plan of the vehicle model, the system can generate corresponding maintenance recommendations according to the model of the target vehicle and the standard maintenance plan recommended by the manufacturer.

[0184] Based on geographic location recommendations, the system can recommend nearby maintenance stores according to the current location of the target vehicle and provide corresponding maintenance project suggestions.

[0185] Based on seasonal maintenance recommendations, the system can recommend corresponding seasonal maintenance items according to the characteristics of the current season, such as antifreeze inspection in winter and air conditioning system inspection in summer.

[0186] These preset rules can be used individually or in combination to generate more comprehensive and accurate maintenance recommendation results. At the same time, the system can also continuously optimize these rules based on user feedback and maintenance results to improve the accuracy and practicality of recommendations.

[0187] The technical solution of the present application solves the maintenance recommendation problem when there are no other vehicles undergoing maintenance in the sharing group. First, it is determined whether there are other first vehicles undergoing maintenance in the sharing group. If not, a preset rule is triggered to generate a maintenance recommendation result without vehicle use sharing information. This method ensures that the system can still provide users with valuable maintenance suggestions even when there are no vehicles available for sharing.

[0188] The use of preset rules enables the system to flexibly respond to different situations and provide users with personalized and timely maintenance suggestions. For example, recommendations based on historical data can make full use of vehicle usage records to provide more accurate maintenance suggestions; recommendations based on geographic location can help users find the most convenient maintenance store and improve user experience.

[0189] In addition, this method can also be seamlessly connected with other maintenance recommendation methods. When a shareable vehicle appears in the sharing group again, the system can immediately switch back to the sharing-based maintenance recommendation mode, ensuring the continuity and consistency of the recommendation service.

[0190] In this way, even when there are no shared vehicles, users can still get high-quality maintenance recommendation services, thereby improving user satisfaction and vehicle maintenance efficiency. At the same time, this approach also provides the system with the ability to provide continuous service, providing users with valuable maintenance suggestions regardless of the status of the shared group.

[0191] Compared with the prior art, the technical solution of this application has obvious advantages. Traditional maintenance recommendation systems usually rely only on fixed maintenance cycles or mileage, lacking flexibility and personalization. However, this application not only takes into account the situation of vehicle sharing, but also provides intelligent recommendations based on multiple factors when sharing is not possible. This method takes into account the actual needs of users and the specific conditions of the vehicle more comprehensively, and can provide more accurate and practical maintenance suggestions.

[0192] Second, refer to Figure 2 , the present application also proposes a maintenance recommendation device based on sharing, including:

[0193] A first determination module 210 is used to determine whether the target vehicle belongs to a sharing group when receiving a vehicle maintenance request or a request to generate a vehicle maintenance request;

[0194] The second judgment module 220 is used to judge whether there are other first vehicles undergoing maintenance in the shared group when the target vehicle belongs to the shared group;

[0195] The generating module 230 is used to generate a maintenance recommendation result with the shared information on the use right of the first vehicle if there are other first vehicles undergoing maintenance in the sharing group.

[0196] By determining whether the target vehicle belongs to a shared group and searching for other vehicles under maintenance within the shared group, maintenance recommendation results are generated that include shared information on vehicle usage rights, thereby enabling vehicle sharing during the maintenance period. This has the advantage of improving resource utilization efficiency during vehicle maintenance and providing car owners with more convenient vehicle options.

[0197] In addition, in some preferred embodiments, a sharing-based maintenance recommendation device proposed in the present application can perform any step of the above method.

[0198] Thirdly, refer to Figure 3 The present application also proposes an electronic device, including a processor 310 and a memory 320, wherein the memory 320 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 310, the steps in the above method are executed.

[0199] Through the above technical solution, the processor 310 and the memory 320 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanisms (not marked), and the memory 320 stores computer-readable instructions executable by the processor 310. When the electronic device is running, the processor 310 executes the computer-readable instructions to execute the method in any optional implementation of the above embodiment to achieve the following functions: when a vehicle maintenance request or a request to generate a vehicle maintenance request is received, it is determined whether the target vehicle belongs to a shared group; when the target vehicle belongs to a shared group, it is determined whether there are other first vehicles undergoing maintenance in the shared group; if there are other first vehicles undergoing maintenance in the shared group, a maintenance recommendation result with shared information on the right to use the first vehicle is generated.

[0200] In a fourth aspect, the present application further proposes a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the above method are executed.

[0201] Through the above technical solution, when the computer program is executed by the processor, the method in any optional implementation method of the above embodiment is executed to achieve the following functions: when a vehicle maintenance request or a request to generate a vehicle maintenance request is received, it is determined whether the target vehicle belongs to a shared group; when the target vehicle belongs to a shared group, it is determined whether there are other first vehicles undergoing maintenance in the shared group; if there are other first vehicles undergoing maintenance in the shared group, a maintenance recommendation result with shared information on the right to use the first vehicle is generated.

[0202] Among them, the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable red-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0203] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0204] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, and may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0205] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0206] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A maintenance recommendation method based on sharing, characterized in that: The steps of the method include: Upon receiving a vehicle maintenance request or a request to generate a vehicle maintenance request, determining whether the target vehicle belongs to a shared group; When the target vehicle belongs to the shared group, determining whether there is another first vehicle undergoing maintenance in the shared group; If there are other first vehicles undergoing maintenance in the sharing group, generating a maintenance recommendation result having shared information on the right to use the first vehicle; The step of generating a maintenance recommendation result having shared information for the first vehicle use right comprises: Acquire first information of the first vehicle and second information of a first maintenance store where the first vehicle is located, wherein the first information at least includes a maintenance status of the first vehicle, and the second information at least includes first location information of the first maintenance store; generating a maintenance recommendation result having shared information on the right to use the first vehicle according to the maintenance status of the first vehicle and the first location information; The step of generating a maintenance recommendation result having shared information on the use right of the first vehicle according to the maintenance status of the first vehicle and the first location information comprises: When the maintenance status of the first vehicle is maintenance completed, generating a maintenance recommendation result having shared information on the use right of the first vehicle according to the first location information; When the maintenance status of the first vehicle is maintenance completed, the step of generating a maintenance recommendation result having shared information on the use right of the first vehicle according to the first location information comprises: When the maintenance status of the first vehicle is maintenance completed, sending a sharing request message to the owner of the first vehicle; receiving first feedback information made by the owner of the first vehicle according to the sharing request information; When the first feedback information is agreement, a maintenance recommendation result having shared information for the first vehicle use right is generated according to the first location information.

2. A maintenance recommendation method based on sharing according to claim 1, characterized in that: The second information at least includes current work arrangement information of the first maintenance store, and the step of sending the sharing request information to the owner of the first vehicle includes: Obtaining estimated maintenance items of the target vehicle according to the vehicle maintenance request or a request to generate a vehicle maintenance request; estimating a first estimated completion time of maintenance for the target vehicle according to the current work arrangement information of the first maintenance store and the estimated maintenance items; The sharing request information including the first estimated maintenance completion time is sent to the owner of the first vehicle.

3. A maintenance recommendation method based on sharing according to claim 2, characterized in that: The method also includes the steps of: When the maintenance status of the first vehicle is unfinished maintenance, obtaining the second current position information of the target vehicle and the second estimated completion time of the maintenance of the first vehicle; Calculating a first arrival time of the target vehicle at the first maintenance store according to the first location information and the second location information; Calculating a first waiting time for the owner of the target vehicle according to the second estimated maintenance completion time and the first arrival time; The maintenance recommendation result having the shared information on the first vehicle use right and the first waiting time is generated.

4. The maintenance recommendation method based on sharing according to claim 1, characterized in that: The method also includes the steps of: Obtaining second feedback information made by the owner of the target vehicle after receiving the maintenance recommendation result; When the second feedback information is in agreement, a sharing contract is generated and the sharing contract is sent to the owner corresponding to the target vehicle and the owner corresponding to the first vehicle respectively.

5. The maintenance recommendation method based on sharing according to claim 1, characterized in that: The method also includes the steps of: If there is no other first vehicle undergoing maintenance in the sharing group, a maintenance recommendation result without vehicle use sharing information is generated according to a preset rule.

6. A maintenance recommendation device based on sharing, characterized in that: The steps applied in the method according to any one of claims 1 to 5 include: A first determination module, configured to determine whether a target vehicle belongs to a sharing group when receiving a vehicle maintenance request or a request to generate a vehicle maintenance request; A second judgment module is used to judge whether there are other first vehicles undergoing maintenance in the shared group when the target vehicle belongs to the shared group; A generating module is used to generate a maintenance recommendation result with shared information on the right to use the first vehicle if there are other first vehicles undergoing maintenance in the sharing group.

7. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps in the method according to any one of claims 1 to 5 are executed.

8. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are executed.

Images